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
Don't crash when making calls to nodeos in service on an HTTP request. Interactions should be treated as suspect, and a failure should be returned to the client.
We talked with Guillaume. Turn out he was using a build from a fork which had pulled a version post 4.0.3 by mistake:
Checked client repo and indeed they had a change not in our release/4.0 branch, which causes the issue.
They will rebase their repo on the right tag (4.0.3) which will solve the issue for them.
The change causing the leap crash has not been released (it is in our main branch), and I have a fix for it. So in a sense the mistake they made was lucky for us, as it allowed us to catch the leap issue before the code was officially released.
To be 100% clear, no 4.0.x leap release is subject to the crash in http_plugin.
The text was updated successfully, but these errors were encountered:
Don't crash when making calls to nodeos in service on an HTTP request. Interactions should be treated as suspect, and a failure should be returned to the client.
We talked with Guillaume. Turn out he was using a build from a fork which had pulled a version post 4.0.3 by mistake:
![image](https://private-user-images.githubusercontent.com/6685407/251195086-5ed52686-7e5c-4954-91a6-735011b2e857.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1NTk2NzMsIm5iZiI6MTczOTU1OTM3MywicGF0aCI6Ii82Njg1NDA3LzI1MTE5NTA4Ni01ZWQ1MjY4Ni03ZTVjLTQ5NTQtOTFhNi03MzUwMTFiMmU4NTcucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxNCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTRUMTg1NjEzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9N2VkOWQyZDYyZmMwNWQxZTUxNDFlNzk4ZWFhOWY3YzVkNjYzODExMjI2MzE1ZTQzMTVlYzlhNDEwM2QyODAzMCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.ccXPqrW0j1Bo2-qgyA6c-wxrSJi9nHed4y9Yy7oBxIQ)
Checked client repo and indeed they had a change not in our release/4.0 branch, which causes the issue.
They will rebase their repo on the right tag (4.0.3) which will solve the issue for them.
The change causing the leap crash has not been released (it is in our main branch), and I have a fix for it. So in a sense the mistake they made was lucky for us, as it allowed us to catch the leap issue before the code was officially released.
To be 100% clear, no 4.0.x leap release is subject to the crash in http_plugin.
The text was updated successfully, but these errors were encountered: