Closed sergii-mamedov closed 1 year ago
Thanks for reporting @sergii-mamedov
Regarding 1. I found the issue a few weeks ago and fixed it here Regarding 3 and 4, I just added a fix here
Regarding 2. Could you provide more information about the error you get that end up triggering raise ex
? Do you get 409? 500? another error from the CE API? or is it not an ApiException
?
Regarding 2. I don't know for sure, it happened when the new runtime was deployed first time. I have seen this exception several times. I tried to add logging but this problem then disappeared.
Couldn't you release a new minor version with all fixes?
In included a few changes in the CE backend that might help preventing the issue you exerienced #1161
@JosepSampe I tested master branch today. Works well. @gilv Could you create a new release?
@gilv can you please release the new version?
@sergii-mamedov @theodev We just released with @gilv the new version (unfortunately, he had no access to his email these weeks)
Thanks @JosepSampe and @gilv !
Thanks a lot
We are upgrading from version 2.7.0 to 3.0.0. I found a few bugs during the update.
runtime
was removed when initializing the instance of the class https://github.com/lithops-cloud/lithops/pull/1140 this change has to be pushed through kwargs. ForServerlessExecutor
, initialization in the formkwargs=kwargs
creates an additional level of dictionary nesting and the following code block does not work correctly.mod_paths
variable tomods_paths
(addeds
) here, here and here.The reason for this is that the
sys
module does not pass validation for this line of code.