You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.
Currently, tor uses the latest version of Blossom wrapper from the master branch. I think this is just waiting for an issue to happen. For larger updates to Blossom wrapper, we will always be forced to immidiately update all of our bots as well. Additionally we might not be able to revert to an old version of the bot, because then the wrapper version doesn't line up anymore.
If the API changes, we will of course have to update the bots anyway. But I am expecting the wrapper interface to change quite a bit in the future and in those cases we have additional effort to try to keep the versions in sync.
This could also lead to "but it works on my device" scenarios if one developer didn't update their dependencies.
The text was updated successfully, but these errors were encountered:
Currently, tor uses the latest version of Blossom wrapper from the master branch. I think this is just waiting for an issue to happen. For larger updates to Blossom wrapper, we will always be forced to immidiately update all of our bots as well. Additionally we might not be able to revert to an old version of the bot, because then the wrapper version doesn't line up anymore.
If the API changes, we will of course have to update the bots anyway. But I am expecting the wrapper interface to change quite a bit in the future and in those cases we have additional effort to try to keep the versions in sync.
This could also lead to "but it works on my device" scenarios if one developer didn't update their dependencies.
The text was updated successfully, but these errors were encountered: