You can try to change the rules for FMN and see if you'll still receive the blank notifications, I don't think there is anything I could do from the Anitya side. :-(
Michal
On 01. 02. 21 17:56, Vít Ondruch wrote:
Please see the attached JSON.
Thx
Vít
Dne 28. 01. 21 v 10:39 Michal Konecny napsal(a):
Hi Vit,
I didn't change anything regarding the FMN that should create this behavior. So I'm not sure from where is this coming.
I can only think that this could be somewhat related to the new `anitya.project.version.update.v2` topic, but I'm not sure why it's affecting the FMN notifications.
Could you share your notifications settings?
Michal
On 27. 01. 21 12:40, Vít Ondruch wrote:
Recently, I have started to receive notifications such as the one in attachment and I wonder what is their purpose? They don't provide any meaningful information starting by the "fedmsg notification" subject.
Vít
Dne 22. 01. 21 v 10:56 Michal Konecny napsal(a):
Hi everyone,
today I deployed a new version of Anitya on production [0]. I decided that Anitya is mature enough to have version 1.0.0. So here it is.
And what this versions brings? Plenty of changes, here is the list of the most interesting ones:
* Add preview mode
Now you can try your changes before submitting them, on the edit and add project page is a new button "Test check" which will take the fields from the form and do a check for releases above them. Nothing is changed in the database during test check.
* Flag pre-release versions
Yes, you are reading it right. Anitya is now flagging versions that are considered unstable, it uses the version scheme recognition and above that you can add your own filter when editing project.
* Message schema 2.0.0
The Anitya message schema now contains a new topic "anitya.project.version.update.v2". This topic will send message that has "upstream_versions" field which contains all the newly found versions, not only the latest one. And it also contains a "stable_versions" field, so you can look if some of the newly versions is stable or not. With this version "anitya.project.version.update" is now deprecated!
* Add version filter for project
Anitya now allows user to add their own version filter, if you see any bogus version, you can just edit project and add the string to filter (This will not delete any version that was already retrieved, but you can flag a project and ask admin to do it for you and it will never be retrieved again).
* Project archiving
Anitya 1.0.0 allows admins to archive projects if it seems reasonable (project dead upstream) for the sake of history. Archived projects can't be edited and are not checked for new versions, but still could be found in Anitya.
* Projects menu is rewritten
The projects menu now contains items that are more sensible to current state of Anitya, you can see projects that were successfully updated (sorted by the time of update from newest), failed to update (sorted by the number of failed attempts from highest number), never updated (incorrectly set up projects, where update was never successful, sorted by the date of creation from oldest) and archived projects.
* Updated documentation
The documentation was fully rewritten to reflect the current state of Anitya. User guide was added containing use cases that could be done by user. User admin guide was added for users in Anitya with Admin rights. And the Admin guide and Contribution guide was verified that these steps are working with current version of Anitya.
If you want to see whole list of changes, see Anitya 1.0.0 release on GitHub [1].
I hope this release will bring joy to your life and solve at least some of the pain points people had with Anitya.
Michal
Mage from release-monitoring.org
P.S.: If you want to try something in Anitya without the fear of breaking anything, you can try it on staging instance [2].
[0] - https://release-monitoring.org/
[1] - https://github.com/fedora-infra/anitya/releases/tag/1.0.0
[2] - https://stg.release-monitoring.org/
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
