Permission denied (public key) issue in Circle-CI’s checkout phase it shouldn’t be needed otherwise.
please update circle ¶Įntering the above phrase in an issue of a feedstock will update the Circle-CI SSH deploy key. please lint ¶Įntering the above phrase in a PR of a feedstock will lint the PR again. Make sure to look over the changes, and ask for help if you’re not sure about something.
Note that this update command is kind of a hack, and things might go wrong. It can be sent either in an issue or a PR. This command will attempt to update a recipe to the new conda-build 3 format. please add noarch: python ¶Įntering the above phrase in a PR or an issue of a feedstock will add noarch: python to the build and rerender the feedstockįor you. If you enter this phrase in the comment for an issue, the bot will create a new pull request, with the requested Make sure to tick the Allow edits from maintainers button located at the bottom of the right side bar of The webservice also listens to issues and PR comments, so that you can ask for the following services to be done: please rerender ¶Įntering the above phrase in a PR of a feedstock will rerender the feedstock and push the changes to your PR. When maintainers are added to a recipe, each of the maintainers will be added to the team and given push access to the feedstock. It will lint the recipes in the PRs and report back whether the recipe is in excellent condition or not. The following services are run by default on a feedstock: Admin web services ¶Ĭonda-forge is running a webservice on Heroku called conda-forge-webservices. For more details, please refer to Improve the documentation. If you found any typo error, unclear explanations or new topics that can be covered, you can suggest changes to the documentation. The documentation is built with Sphinx and the sources files are located in the src directory of the repository.
The documentation lives in conda-forge/, and is automatically deployed to our online version. For more information on updating globally pinned packages, please refer to Updating package pins. Please open a PR and/or an issue there, if you think a pin needs to be advanced. Package-wide dependency pins are defined in conda_build_config.yaml in the conda-forge/conda-forge-pinning-feedstock.įor more information on conda-forge wide package pins, please refer to Globally pinned packages.
Please note that the code logic provided by the app is in the Smithy repository.īugs or suggestions regarding the service functionality should therefore be opened in conda-forge/conda-smithy’s bug tracker. The Heroku app providing the conda-forge web services lives in conda-forge/conda-forge-webservices. Which could be less expensive to run than permanently active agents.) Web services ¶ (You could also consider using Azure virtual machine scale set agents, For example, it can be used to set up self-hosted Azure agents for non-Conda-Forge infrastructures. Smithy can be used beyond Conda-Forge’s purposes.
See the dedicated page about how to configure OneDrive and Sharepoint: OneDrive and SharePoint.Conda-smithy also contains the command line tool that you should use if you rerender manually from the command line (see Rerendering feedstocks). Issue: Files that are saved on OneDrive or SharePoint cause an error to pop up ¶
(see ) or set the full path to your interpreter in the add-in or your config sheet, e.g. If you get the error 'python' is not recognized as an internal or external command, operable program or batch file., then you have two options: Either add the path of where your python.exe lives to your Windows path Python to start an interactive Python session. If it is empty, then you need to be able to open a windows command prompt and type Reinstall it with pip or conda, see Installation.Ĭheck your Interpreter in the add-in or config sheet. Xlwings32-.dll and xlwings64-.dll are both in the same directory as your python.exe. Toggle table of contents sidebar Troubleshooting ¶ Issue: dll not found ¶