Israel Fruchter

meanwhile I've decided to disable it in #10491, and backport to all releases. once we'll have the fixes in place, we can enable it back

I think it's a good idea I myself am not using this package anymore for years, so looking for a maintainer that uses it, is the way to go. I'm...

The issue seems like Unicode escape sequences. The code should be taking them out, if it works as expected

> The issue seems like Unicode escape sequences. > > The code should be taking them out, if it works as expected > > Also see https://superuser.com/a/1785495/1256163 The best thing...

Don't know if to call expected behavior, it a known issue in SCT, that never got fixed

> What we can do is to stream cores to s3 via curl and pick them up form there something like this: https://gist.github.com/hashbrowncipher/57dd3a52103cae02290ac65fae9f3422

@juliayakovlev seems like that node run of disk space, and the files are getting cleared before we have chance to upload them: ``` 9440150:< t:2022-05-26 13:34:28,424 f:db_log_reader.py l:113 c:sdcm.db_log_reader p:DEBUG...

@juliayakovlev upload failed: ``` 9446413:< t:2022-05-26 13:36:42,519 f:base.py l:228 c:RemoteLibSSH2CmdRunner p:DEBUG > The requested URL /core.scylla.113.14c3edeca8594ea09fbe11bc49b1d7ae.2709.16535 71792000000000000/core.scylla.113.14c3edeca8594ea09fbe11bc49b1d7ae.2709.1653571792000000000000.gz was not found on this server. 9446414-< t:2022-05-26 13:36:42,519 f:base.py l:228 c:RemoteLibSSH2CmdRunner p:DEBUG...

Julia, I've found the issue, it's not related to what's describe in this issue seem like we need to change the url we are using and yes we should fail...

We've seen lots of issues like those, but I'm not sure it's connected to other stress commands running. I think that we are using centos7 with some specific old docker...