Last release broke my add-on, even after the fact that API was not changed?

Hello

im writing an addon right now, she worked totally fine on the build of 10 april, 20may, 3june, but on the build of yesterday 6 june, i had some issues.

i calculated a lot of timing related math with the datetime python module, now my time calculation result are all reversed.

i experienced a lot more crashes on this bluid (6 june - blender-2.80.0-git.8b2b79c2108b-windows64) than the 3 other builds up above.

Is this normal ? i will do more analysis of what happend, and also test 7 junes build to see if thoses anomalies stay. This behavior feel really weird to me. Spooky.

Maybe a dev here know something ? did i miss anything ? any changes that may provoque that ?

Itā€™s very hard to respond to ā€œitā€™s not workingā€ without any further information, or any indication of what the problem is.

Best think you can do is If you think you have a bug, post a bug report on developer.blender.org with a concrete way for developers to reproduce your issue.

1 Like

No its all about my python datetime calculation, its not normal that on the 3 june build the result of the calculation is not the same that on the 6 june build. Thatā€™s why im asking here, itā€™s just so weird.

but again the 6 june build is so unstable, it may be resolved this week.

"The result of the calculation it is not correctā€™ "

once more, not sure how to help you here, you gave no information except, ā€˜it used to work, now itā€™s notā€™

Share some code that shows the issue at the very least!

1 Like

If I may suggest, reading these pages, prior to report a bug, can be useful:

https://wiki.blender.org/wiki/Process/Bug_Reports
https://archive.blender.org/development/report-a-bug/
https://developer.blender.org/maniphest/task/edit/form/1/

1 Like

I donā€™t even know if it is a bug or an error,iā€™m not asking to resolve my problem either, im just asking if the dev did some changes that are related to that area. But well i got my response it seems, it must be a bug and iā€™ll dig into it.