| 06:28 | <falken> | I just get an error message "There were errors. Stopping." from html-build/build.sh. Is there a way to debug? |
| 06:30 | <MikeSmith> | falken: I can help now |
| 06:30 | <falken> | Great! |
| 06:31 | <MikeSmith> | I think that indicates a parse error |
| 06:32 | <domfarolino> | falken: Any output difference when trying verbose? |
| 06:32 | <domfarolino> | `-v`, that is |
| 06:35 | <MikeSmith> | domfarolino: DMed falken about it but apparently I/we may have recently regressed the error-reporting behavior |
| 06:35 | <MikeSmith> | in case of errors, the build should cat the .temp/wattsi-output file |
| 06:36 | <MikeSmith> | but it seems it might not be doing that in, at least in some cases |
| 06:37 | <domfarolino> | ahh I see. That would be difficult to debug indeed. |
| 06:37 | <MikeSmith> | yup |
| 06:58 | <annevk> | At the end of this year Web Forms 2.0 will have existed for 15 years... |
| 06:59 | <annevk> | September 5 the first draft got shared in private |
| 07:00 | <Ms2ger> | Maybe we can try to get it implemented by then |
| 07:00 | <annevk> | I initially wrote "Still has bugs" as subsequent sentence, but thought that'd be too negative |
| 07:00 | <annevk> | Fortunately there's Ms2ger 😃 |
| 07:01 | Ms2ger | takes a bow |
| 07:02 | <MikeSmith> | heh |
| 07:04 | <MikeSmith> | I guess we probably now have some 20-year milestones of interest at https://www.w3.org/html/wg/wiki/History |
| 07:04 | <MikeSmith> | doctype sniffing, 1998-07 |
| 07:59 | <MikeSmith> | falken: I’ve not been able to reproduce the problem you ran into |
| 07:59 | <falken> | MikeSmith: hummm |
| 08:00 | <MikeSmith> | yeah I get the expected error report emitted to the console |
| 08:01 | <falken> | If it matters I'm not using local wattsi: "Local wattsi is not present; trying the build server..." |
| 08:01 | <MikeSmith> | but if you’re still able to reproduce it can file an issue with a test case, I can look |
| 08:01 | <MikeSmith> | oh |
| 08:01 | <falken> | I also often get "socket.error: [Errno 98] Address already in use" but even after killing the server the same error happened |
| 08:01 | <MikeSmith> | ah |
| 08:02 | <MikeSmith> | yeah the socket error happens if you ^C kill the build before it completes |
| 08:02 | <MikeSmith> | it’s because of the support for syntax-highlighting that I added recently |
| 08:03 | <MikeSmith> | that support relies on the build starting up a local web server |
| 08:04 | <MikeSmith> | if you have pkill or such installed, you can do `pkill python; ./build.sh` to kill that web server before you build again |
| 08:04 | <falken> | yea.. it didn't seem to matter if the socket error happened or not |
| 08:04 | <MikeSmith> | well, assuming you don’t have any other python process running (because that pkill invocation would kill them all) |
| 08:04 | <MikeSmith> | yeah |
| 08:05 | <MikeSmith> | yeah so I didn’t test the remote-wattsi case yet |
| 08:05 | <MikeSmith> | I will |
| 08:55 | <MikeSmith> | falken: so yeah thanks I can reproduce it with remote wattsi |
| 09:23 | <MikeSmith> | falken: https://github.com/whatwg/html-build/pull/181 has the fix |
| 09:23 | <MikeSmith> | thanks again for catching that |
| 15:04 | <Domenic> | MikeSmith: we should also use tricks to catch ^Cs and kill the server anyway |
| 16:14 | <MikeSmith> | Domenic: true |
| 20:45 | <rixx> | hi, I noticed that Request.credentials is now (as of https://github.com/whatwg/fetch/commit/811575d6889026c68d55a327f79198dccfea403c in April) supposed to default to "same-origin" instead of "omit". This is not reflected in the living standard document for fetch: https://fetch.spec.whatwg.org/ |
| 20:46 | <rixx> | The relevant line is https://github.com/whatwg/fetch/blob/master/review-drafts/2018-06.bs#L1057 -- what's the best way forward? Submitting an issue? Direct PR? |
| 20:54 | <Domenic> | rixx: why do you say it's not reflected in the living standard? (Also, why are you pointing to the review draft instead of the living standard?) |
| 20:55 | <Domenic> | rixx: the change in https://github.com/whatwg/fetch/commit/811575d6889026c68d55a327f79198dccfea403c appears in the living standard at https://fetch.spec.whatwg.org/#dom-request step 6.6. |
| 20:58 | <rixx> | it does, but in the standard document it says 'Unless stated otherwise, it is "omit".', which sounds to me like it doesn't match that change |
| 20:59 | <Domenic> | But it is stated otherwise, on step 6.6. |
| 21:03 | <rixx> | it does say that, thank you for pointing it out. I'd argue finding the valid value for credentials is a bit convoluted, then |
| 21:03 | <rixx> | Thank you for clearing that up, sorry for the noise |
| 21:04 | <Domenic> | np! |
| 22:51 | <MikeSmith> | https://developer.mozilla.org/en-US/docs/Web/API/Request/credentials$compare?from=1403797&to=1403836 |
| 22:52 | <MikeSmith> | > even though the living standard document currently does not reflect it, same-origin is the default value as of.. |