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
When I try to use mysql-native 2.2.2 and sdlang 0.10.2 in the same project, it fails because of a conflict between unit-threaded 0.6.28 and 0.7.45. dub goes into an infinite loop every time.
If I allow a downgrade of either package, I end up with bugs or without features that I need.
If I cache the package locally and hack the unit-threaded version to 0.7.45, everything builds and works. Perhaps there are side affects that I don't see.
I am new to 'd' so it is possible that I am missing something. Sorry if that is the case.
Please do whatever you need to in order for sdlang to coexist with the latest mysql-native.
For me, it was hack/upgrading the unit-threaded version to 0.7.45.
Thank you!
The text was updated successfully, but these errors were encountered:
The infinite loop is definitely a dub issue and should be filed here. Even if it only happens with that unit-threaded conflict, it still needs to get looked at and fixed.
When I try to use mysql-native 2.2.2 and sdlang 0.10.2 in the same project, it fails because of a conflict between unit-threaded 0.6.28 and 0.7.45. dub goes into an infinite loop every time.
If I allow a downgrade of either package, I end up with bugs or without features that I need.
If I cache the package locally and hack the unit-threaded version to 0.7.45, everything builds and works. Perhaps there are side affects that I don't see.
I am new to 'd' so it is possible that I am missing something. Sorry if that is the case.
Please do whatever you need to in order for sdlang to coexist with the latest mysql-native.
For me, it was hack/upgrading the unit-threaded version to 0.7.45.
Thank you!
The text was updated successfully, but these errors were encountered: