Bug #13867
closedExecuting `./test.wt` results in the following error: unknown location(0): fatal error: in "chart_test_WDateTimeChartMinutes": Wt::WServer::Exception: Error reading: /home/spack/opt/spack/linux-sles15-aarch64/gcc-7.4.0/wt-4.12.0-vvvczhvsfsrgj7ubzr5lnvrvos
100%
Description
Environmental Information:
OS:
cat /etc/os-release
NAME="SLES"
VERSION="15-SP1"
VERSION_ID="15.1"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP1"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15:sp1"
GCC:
/usr/bin/gcc --version
gcc (SUSE Linux) 7.4.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
VERSION:4.12.0
Operation Steps:
- spack install --keep-stage --no-checksum -y wt@4.12.0
- cmake.. -DBUILD_TESTS=ON -DENABLE_LIBWTTEST=ON -DBUILD_EXAMPLES=ON -DINSTALL_EXAMPLES=ON; make -j96
3../test.wt
Error message is as follows:
./test.wt
Running 366 test cases...
Auth.HashFunction: ASVS recommends using BCrypt with at least 10 iterations.
bcrypted password: $2y$05$RDPhWkTPbSHOWSXYSSzNM.kTiG5eieVwaJkFOBUWDOUUiLGzTC67y
with 5 iterations, verify() took: 2.815ms
Auth.HashFunction: ASVS recommends using BCrypt with at least 10 iterations.
bcrypted password: $2y$06$QhX0cVWwShTwYyTIRFXiWO9lH4QrzDjKEZiMOO5GEgrDC/VjWM1tW
with 6 iterations, verify() took: 5.433ms
Auth.HashFunction: ASVS recommends using BCrypt with at least 10 iterations.
bcrypted password: $2y$07$PxPWLBbTOUqwQ1bpQjbgM.Oe505UqItVshhG8P9/fWSv4csiNg/3a
with 7 iterations, verify() took: 10.737ms
Auth.HashFunction: ASVS recommends using BCrypt with at least 10 iterations.
bcrypted password: $2y$08$biXMLyrDZlT4cjXpYhDRS.IiaXNfI9iKTQpAu3FLncOAzixJuVptu
with 8 iterations, verify() took: 21.182ms
Auth.HashFunction: ASVS recommends using BCrypt with at least 10 iterations.
bcrypted password: $2y$09$YR/IQFH2USbDPyLVWSzhOuoefrfu.J1vym/8cltmN/aLnc4sqAlse
with 9 iterations, verify() took: 42.183ms
bcrypted password: $2y$10$QFb4ZUPfaSzfQSvqThHXOOrEO7QslX1r3YORWNPAryVsYmpQmagVW
with 10 iterations, verify() took: 84.14ms
bcrypted password: $2y$11$Ll/wXy3CYCjmK0zETBCzaOYRbOpvGlwVpPdhlBIY30fiyk8F5s2rC
with 11 iterations, verify() took: 168.093ms
bcrypted password: $2y$12$XELTLjPlLEXlcBSuQVnmUO.GhIjGhFTlbNKOMHVUpKQTddB7XSZCO
with 12 iterations, verify() took: 336.016ms
bcrypted password: $2y$13$TCazX1O2OVXILkDVSiL4Y.tUFTg6453BdtGI2XWk6iwjoX4s4CZ8q
with 13 iterations, verify() took: 671.156ms
bcrypted password: $2y$14$aFTmORTqSUawLkjiOjDNTeV8waB9Tl4JvOAq1j/0FPzOtjyHxpiBK
with 14 iterations, verify() took: 1343.43ms
bcrypted password: $2y$15$QFD0TVK0XiTBZCvIKEK2XejW3P4AFwy1hLJv3c/19VhqzpvFl.DMG
with 15 iterations, verify() took: 2681.49ms
[2025-Jul-28 11:19:36.686] 18391 - [info] "config: reading Wt config file: /home/spack/opt/spack/linux-sles15-aarch64/gcc-7.4.0/wt-4.12.0-vvvczhvsfsrgj7ubzr5lnvrvoslpegut/etc/wt/wt_config.xml (location = '')"
unknown location(0): fatal error: in "chart_test_WDateTimeChartMinutes": Wt::WServer::Exception: Error reading: /home/spack/opt/spack/linux-sles15-aarch64/gcc-7.4.0/wt-4.12.0-vvvczhvsfsrgj7ubzr5lnvrvoslpegut/etc/wt/wt_config.xml: : expecting 'script' or 'all'
/home/stage/root/spack-stage-wt-4.12.0-vvvczhvsfsrgj7ubzr5lnvrvoslpegut/spack-src/test/chart/WChartTest.C(75): last checkpoint: "chart_test_WDateTimeChartMinutes" test entry
[2025-Jul-28 11:19:36.686] 18391 - [info] "config: reading Wt config file: /home/spack/opt/spack/linux-sles15-aarch64/gcc-7.4.0/wt-4.12.0-vvvczhvsfsrgj7ubzr5lnvrvoslpegut/etc/wt/wt_config.xml (location = '')"
unknown location(0): fatal error: in "chart_test_WDateTimeChartHours": Wt::WServer::Exception: Error reading: /home/spack/opt/spack/linux-sles15-aarch64/gcc-7.4.0/wt-4.12.0-vvvczhvsfsrgj7ubzr5lnvrvoslpegut/etc/wt/wt_config.xml: : expecting 'script' or 'all'
/home/stage/root/spack-stage-wt-4.12.0-vvvczhvsfsrgj7ubzr5lnvrvoslpegut/spack-src/test/chart/WChartTest.C(104): last checkpoint: "chart_test_WDateTimeChartHours" test entry
文齐 Updated by 文丽 齐 about 1 year ago
111111
MV Updated by Matthias Van Ceulebroeck about 1 year ago
- Target version set to 4.12.1
Hello,
this is specifically an error on our side. A rename was not properly applied to all values.
MV Updated by Matthias Van Ceulebroeck about 1 year ago
- Related to Improvements #13301: Report all JS errors in Wt added
MV Updated by Matthias Van Ceulebroeck about 1 year ago
- Status changed from New to InProgress
- Assignee set to Matthias Van Ceulebroeck
MV Updated by Matthias Van Ceulebroeck about 1 year ago
- Status changed from InProgress to Review
- Assignee deleted (
Matthias Van Ceulebroeck)
MV Updated by Matthias Van Ceulebroeck about 1 year ago
- Related to Bug #13895: Incorrect default option line 220 of wt_config.xml for <debug-level> in Wt 4.12.0 added
MV Updated by Matthias Van Ceulebroeck about 1 year ago
- Status changed from Review to Implemented @Emweb
- Assignee set to Matthias Van Ceulebroeck
- % Done changed from 0 to 100
MV Updated by Maks Verver 12 months ago
Matthias, can you explain how this bug ended up in the public release?
If I understand correctly, this bug means the 4.12.0 release is just completely unusable with the default configuration, as in: even the most basic "Hello world!" app will fail on startup because the default config file fails to parse.
It sounds like something that would have been caught by the most rudimentary form of release testing. We all make mistakes, so I'm not criticizing the erroroneous code change itself, but I am confused about why it was not detected by any form of testing. Do you just not run any tests before release? Or is the issue that all your release tests use custom/empty config files, so the error in the default config wasn't caught? If it's the latter, could you please add at least one basic test that actually uses the default config file, to ensure it parses correctly?
Also, when you fix an issue like this, could you please push the fix to github so downstream maintainers can incorporate it? Currently, HEAD on Github still points to the broken 4.12.0 release from two months ago, which makes it impossible to add an official patch to a downstream package (which is typically preferred to rolling back to an older version).
MV Updated by Matthias Van Ceulebroeck 12 months ago
- Related to Improvements #13965: Add test for default configuration added
MV Updated by Matthias Van Ceulebroeck 12 months ago
- Status changed from Implemented @Emweb to Implemented @Test
Hello Maks,
I have updated the Github, I apologize for overlooking this. The actual fix has been implemented for a while.
I agree, this should have absolutely been caught in a test. The issue is that either:
- tests used a pre-existing configuration file which did not contain the new configuration item, and thus used a default value
- tests did not use any configuration file, defaulting to a non-existing path, again resulting in default values being used
I have added #13965 to ensure we check the full default configuration.
MV Updated by Maks Verver 12 months ago
Matthias: Thanks for the explanation, and for uploading the fix to Github!
For future reference this is the fix: https://github.com/emweb/wt/commit/fded9ca4ed7d37e036e222098f6d68dc79bca901
I'll submit a proposal to the Arch Linux maintainer to patch that commit into the 4.12.0 package.
MV Updated by Matthias Van Ceulebroeck 11 months ago
- Status changed from Implemented @Test to Closed