-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
simple_kill_streaming_node_while_bootstrapping_test: Startup failed: std::runtime_error ({shard 0: fmt::v6::format_error (invalid type specifier), shard 1: fmt::v6::format_error (invalid type specifier)})']) #6874
Comments
I will take a look. |
I could not reproduce with the exact scylla version. I am building with the dbuild. The fmt version it uses: fmt-devel-6.2.1-1.fc32.x86_64. I suspect it is libfmt related. |
The line in question was: (id is of type repair_uniq_id)
The print function for the repair_uniq_id is:
@avikivity Do you know if there is any limitation on recursive format() usage? |
@asias we don't use format in seastar logger. See |
Also, the following log message indicates that
|
You are correct. The exception comes from somewhere else. |
@bhalevy Do you have a recent "good" commit? |
I think I know what is problem now: throw std::runtime_error(format("repair id {:d} on shard {:d} failed to repair {:d} sub ranges", id, shard, nr_failed_ranges)); |
yes, I just saw it too... |
in |
I'd leave the format specifiers out when not required.... |
Yes, I am working on a patch. |
We recently saw a weird log message: WARN 2020-07-19 10:22:46,678 [shard 0] repair - repair id [id=4, uuid=0b1092a1-061f-4691-b0ac-547b281ef09d] failed: std::runtime_error ({shard 0: fmt::v6::format_error (invalid type specifier), shard 1: fmt::v6::format_error (invalid type specifier)}) It turned out we have: throw std::runtime_error(format("repair id {:d} on shard {:d} failed to repair {:d} sub ranges", id, shard, nr_failed_ranges)); in the code, but we changed the id from integer to repair_uniq_id class. We do not really need to specify the format specifiers for numbers. Fixes scylladb#6874
Patch sent: #6880 |
No vulnerable branches. |
Should be backported along with #6786 if the latter is ever backported. |
Seen several time recently in next runs:
https://jenkins.scylladb.com/view/master/job/scylla-master/job/next/2255/testReport/update_cluster_layout_tests/TestUpdateClusterLayout/dtest___simple_kill_streaming_node_while_bootstrapping_test/
https://jenkins.scylladb.com/view/master/job/scylla-master/job/next/2258/testReport/update_cluster_layout_tests/TestUpdateClusterLayout/dtest___simple_kill_streaming_node_while_bootstrapping_test/
https://jenkins.scylladb.com/view/master/job/scylla-master/job/next/2262/testReport/update_cluster_layout_tests/TestUpdateClusterLayout/dtest___simple_kill_streaming_node_while_bootstrapping_test/
https://jenkins.scylladb.com/view/master/job/scylla-master/job/next/2262/artifact/logs-release.2/1595154166737_update_cluster_layout_tests.TestUpdateClusterLayout.simple_kill_streaming_node_while_bootstrapping_test/node4.log
The text was updated successfully, but these errors were encountered: