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
Hello!
I've found out that stmx integration got broken after lparallel bt2 migration (the latest functional lparallel commit was 80fc2952a074776abd343d6b5d3ab157f0e1df7a)
Does anyone have any idea on fixing that?
Thought that simply switching bt to api v2 in stmx source code would help, but it doesn't seem to be that straightforward.
that works fine before 80fc2952a074776abd343d6b5d3ab157f0e1df7a, but fails with (FORMAT NIL "stmx:*current-thread* contains a stale value:~& found ~S~& expecting ~S" #<BT2:THREAD "main thread" {1004AFD8C3}> #<BT2:THREAD "lparallel" {10039C5CD3}>) afterwards.
@sionescu, maybe you can help here? since you're the expert in bt obviously 🥲
The text was updated successfully, but these errors were encountered:
Hello!
I've found out that stmx integration got broken after lparallel bt2 migration (the latest functional lparallel commit was
80fc2952a074776abd343d6b5d3ab157f0e1df7a
)Does anyone have any idea on fixing that?
Thought that simply switching bt to api v2 in stmx source code would help, but it doesn't seem to be that straightforward.
minimal reproduceable example:
that works fine before
80fc2952a074776abd343d6b5d3ab157f0e1df7a
, but fails with(FORMAT NIL "stmx:*current-thread* contains a stale value:~& found ~S~& expecting ~S" #<BT2:THREAD "main thread" {1004AFD8C3}> #<BT2:THREAD "lparallel" {10039C5CD3}>)
afterwards.@sionescu, maybe you can help here? since you're the expert in bt obviously 🥲
The text was updated successfully, but these errors were encountered: