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
I use snowflake connector through Pycall in Rails application.
Throwing queries asynchronously to Snowflake and then retrieving the status of the queries.
After updating pycall to 1.5.2, the screen froze when retrieving the status of the query.
However, looking at the logs, it appears that the retrieving of the query status completes successfully, and even the subsequent rendering of the view completes successfully.
Fixed Pycall version to 1.5.1 and did a bundle update and confirmed that it works correctly.
On the other hand, when I did a bundle update pycall, it didn't work properly.
No particular errors in the logs, even if they do not work properly.
What could be the cause?
Versions:
ruby: 3.1.2
rails: 7.0.8.1
The text was updated successfully, but these errors were encountered:
we also saw hanging after updating to 1.5.2 using pycall in the context of ruby-spacy gem. We had to revert as well. Haven't had time to dig into what was happening.
These were all single threaded workers that just froze up and stopped processing anything, but without any errors or hints as to why.
I use snowflake connector through Pycall in Rails application.
Throwing queries asynchronously to Snowflake and then retrieving the status of the queries.
After updating pycall to 1.5.2, the screen froze when retrieving the status of the query.
However, looking at the logs, it appears that the retrieving of the query status completes successfully, and even the subsequent rendering of the view completes successfully.
Fixed Pycall version to 1.5.1 and did a
bundle update
and confirmed that it works correctly.On the other hand, when I did a
bundle update pycall
, it didn't work properly.No particular errors in the logs, even if they do not work properly.
What could be the cause?
Versions:
The text was updated successfully, but these errors were encountered: