Wattsi is not re-run about html-build HOT 6 CLOSED

I am able to get this to reliably work. Can you give an example of an edit you made? Are you using local Wattsi, or the build server? You're absolutely sure Wattsi is updated and the updated version is the one in your path?

from html-build.

E.g., a misspelled start tag. I use local Wattsi. I ran git pull, ./build.sh, which is how I've updated Wattsi thus far successfully I think. @Ritsyy ran into this as well.

from html-build.

Is there a simple way to check the version number of Wattsi?

from html-build.

Is there a simple way to check the version number of Wattsi?

There isn’t. There’s actually no version number to show, currently. Going forward, I guess we should start versioning it, and add a command-line option to display the version number. But for now, there isn’t even a build date or any other kind of stamp/ID stored in the binary.

from html-build.

I am able to get this to reliably work.

Me too. I can’t reproduce the problem. If I leave a start tag open (which, based on the Parse Error: (120773,9) unexpected body end tag error message that @ritsyy mentioned on IRC is probably what caused the problem ritsyy ran into), the build script reports the correct line number from the source (117357). And if I run wattsi manually, it does in fact exit with 65 when it hits that parse error:

$ wattsi ../html/source .temp/wattsi-raw-source-output \
    .cache/caniuse.json .cache/w3cbugs.csv || echo $?
Parsing caniuse.com data...
Processing caniuse.com data...
Parsing bugs data...
Parsing...
Parse Error: (117357,9) unexpected body end tag
65

So if you run wattsi ../html/source .temp/wattsi-raw-source-output .cache/caniuse.json .cache/w3cbugs.csv || echo $? in your environment and it doesn’t return 65 (but instead 1 or 0), then I would think the only thing that could cause that is, the wattsi you’re calling wasn’t actually built from the latest sources. I guess you might want to do which wattsi to check which one it’s running.

@Ritsyy ran into this as well.

If the only line number reported was 120773 then yeah, that’s not the line number in the source (which currently has only 117356 lines on master) but instead in the intermediate file the build script generates.

But I think if ritsyy hadn’t pulled and rebuilt wattsi yet, that’s the expected behavior (because before the recent changes, wattsi didn’t return 65 but now it does, and the build script is now checking for 65).

from html-build.

Seems like this is my problem after all. Something with how things were linked is messed up.

from html-build.