We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description the slack link is broken in the CONTRIBUTING.rst file: https://github.com/newrelic/newrelic-python-agent/blob/main/CONTRIBUTING.rst#slack
Expected Behavior I'd be able to join a slack and ask some questions about work related to #952
Steps to Reproduce visit the link in the description above and click the slack link
Your Environment safari
Additional context trying to run the tests in the devcontainer does not work, and I'm wondering if I'm missing some setup instructions:
> docker exec -it --workdir /workspaces/newrelic-python-agent 35a3a60c14cd /bin/bash
vscode@linuxkit-66f0adc78c76:/workspaces/newrelic-python-agent/tests$ tox -c tox.ini -e datastore_aiomysql /home/vscode/.pyenv/shims/tox: line 8: /root/.pyenv/libexec/pyenv: Permission denied
The text was updated successfully, but these errors were encountered:
That workspace looks like it's been deleted, I'm not sure why it's gone.
As far as the devcontainer goes, looks like the permissions issue wasn't fixed all the way. I'll fix that.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Description
the slack link is broken in the CONTRIBUTING.rst file: https://github.com/newrelic/newrelic-python-agent/blob/main/CONTRIBUTING.rst#slack
Expected Behavior
I'd be able to join a slack and ask some questions about work related to #952
Steps to Reproduce
visit the link in the description above and click the slack link
Your Environment
safari
Additional context
trying to run the tests in the devcontainer does not work, and I'm wondering if I'm missing some setup instructions:
The text was updated successfully, but these errors were encountered: