-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
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
Regressions with conf.py and error reporting #2963
Comments
@agjohnson I would like to contribute, can you please give me a little guidance? |
@monvilafer hey! I was about to start working on this issue, are you still interested on contributing? Summarizing the steps that you will need:
also, the |
Yes!, I am working on it! |
I think to fix this issue we will need:
Tip: I'm creating local repositories with
then, I import the repository manually and use I think this could help you to clarify what it's needed here, @monvilafer. BTW, were you able to setup the development environment? |
I was able to reproduce this issue, but only in the commit mentioned in the other ticket (italia/anpr@2196e3d).
That produces a not very well handled exception,
... and the build keeps in |
The problem is this section
It finaly raises the exception
So, I think this logic is OK: "If there are more than one conf.py file and none of them has
Instead of saying
BTW, that error is not showed either because nobody handles the |
`pk` exists only for Builds that are retrieved from the database, but when it's retrieved using the API, the `id` must be used. Using the `id` is compatible with both instances. Related to #2963
`pk` exists only for Builds that are retrieved from the database, but when it's retrieved using the API, the `id` must be used. Using the `id` is compatible with both instances. Related to #2963
Our search should be finding
conf.py
files in non-standard paths, but this is not happening automatically. We should be able to find and use aconf.py
at least in any first level path.Additionally, when we aren't finding a conf.py, we were reporting this to the user. This is not happening either now, instead the user receives a message that an unknown error occured.
Ref #2962
The text was updated successfully, but these errors were encountered: