-
Notifications
You must be signed in to change notification settings - Fork 106
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
"Internal Server Error" while adding new project #845
Comments
The project is created https://release-monitoring.org/project/27539/ but it is not fetching versions as expected. |
This issue is caused by semantic versioning scheme, I will look at it more closely to find what exactly is causing this, for now you can switch to rpm versioning, which is working. |
I looked at it more closely and now I knew, what is going wrong, you checked, that you want to watch releases, which is fine, but releases aren't using semantic versioning at all, they are using strange names. This is why the check for versions is crashing. |
Because GitHub allows name of the release to be anything. It will be better to use tags associated with the releases instead of using the release names. Fixes fedora-infra#845 Signed-off-by: Michal Konečný <[email protected]>
Nice error message will definitely help. If the interface could query tags without reloading that page, and show which were ok and which were failed - that will be helpful too. |
This will be nice enhancement for Anitya, but it needs changes in how the checking is handled right now. It either recover versions or not. We should do some validations of the retrieved versions before working with it for this to work. |
Does checking occur in a separate job queue and message passed as a result doesn't contain necessary details? |
Checking is done in separate thread on web interface and there is service running as separate pod which does the heavy work in check. The message is sent after new version is discovered when checking. |
Where is the place to modify the message passed from service to web thread, to include the tags discovered? |
There is no message communication between those service and web. Both of them only communicate with database when changing project or adding discovered version. |
Because GitHub allows name of the release to be anything. It will be better to use tags associated with the releases instead of using the release names. Fixes #845 Signed-off-by: Michal Konečný <[email protected]>
I am trying to add https://github.com/watchexec/watchexec
This submission fails with internal server error.
The text was updated successfully, but these errors were encountered: