| 01:49 | <annevk> | "into document" is the bit you omitted from your quote that's rather key there |
| 02:42 | <MikeSmith> | astearns: so about the github/w3c perms, if I understand correctly, the thing that blocks you is that you can’t on your own add people to github/w3c teams unless they’re already members of the w3c org? |
| 02:50 | <MikeSmith> | I think for any repo where you have Admin perms, you can still add anybody you want as a CollaboratorーI mean without adding them to a Team |
| 02:51 | <MikeSmith> | to me, using github teams seems like overkill unless you have multiple repos that you want to give the same set of people write access to (like we do with web-platform-tests) |
| 02:54 | <annevk> | They have multiple repos though |
| 02:55 | <annevk> | Less than I’d like, but more than one |
| 03:02 | <astearns> | MikeSmith: You are correct. I can add random people as collaborators, but the current set are official CSSWG members, so I think it makes sense to add them to the org |
| 03:03 | <MikeSmith> | astearns: OK |
| 03:06 | <MikeSmith> | annevk: you mean web-platform-tests has multiple repos? and it should have more? |
| 03:06 | <annevk> | MikeSmith: I meant CSS |
| 03:06 | <MikeSmith> | ah |
| 03:06 | <MikeSmith> | yeah |
| 03:07 | <annevk> | Might have missed some context |
| 03:07 | <MikeSmith> | no |
| 03:07 | <MikeSmith> | that was the original context |
| 03:07 | <MikeSmith> | but IMHO too yeah CSS should have more repos |
| 03:09 | <MikeSmith> | anyway as far as the thing about giving perms for a repo Admin adding members to the w3c org, as far as I can see the only way to do that is by giving Admin (Owner?) perms for the entire w3c org |
| 03:10 | <MikeSmith> | and one reason for not being able to do that is, there are some private repos in the org, so it would also mean exposing those to them |
| 03:11 | <MikeSmith> | but I guess one way to deal with that particular part would be to move those private repos to a different org, e.g., w3c-private or whatever |
| 03:12 | <MikeSmith> | but even if we did that, the other people would still have complete owner/admin perms for changing whatever they wanted in org config, and blocking users org-wide, etc. |
| 03:13 | <MikeSmith> | summary: it’s complicated :) |
| 03:13 | <astearns> | MikeSmith: if associating a W3C account with a github handle would automatically invite people to the W3C github org, then I think my particular problem would be solved. Tab suggested this on sysreq |
| 03:13 | <MikeSmith> | yes |
| 03:13 | <MikeSmith> | I will follow up with the systeam about that |
| 03:14 | <MikeSmith> | since it’s their tool that does the W3C-account association |
| 09:46 | <zcorpan> | ok folks, which text editor should I switch to (on macOS)? |
| 09:47 | <MikeSmith> | vim |
| 09:48 | <zcorpan> | I like rectangular selection and multiple cursors, multi-file regexp search & replace |
| 09:49 | <MikeSmith> | vim has rectangular selection built in |
| 09:50 | <MikeSmith> | multi-file regexp search & replace I reckon it either has built in or there’s some plugin |
| 09:50 | <MikeSmith> | multiple cursors I dunno |
| 09:51 | <MikeSmith> | personally for multi-file regexp search & replace I just use perl from the shell |
| 10:23 | <zcorpan> | https://github.com/w3c/payment-request/pull/715 seems like a useful template we could use for PRs |
| 10:23 | <zcorpan> | https://blog.github.com/2016-02-17-issue-and-pull-request-templates/ |
| 10:23 | <zcorpan> | annevk: Domenic: foolip: thoughts? |
| 10:25 | <zcorpan> | https://github.com/w3c/payment-request/blob/gh-pages/.github/PULL_REQUEST_TEMPLATE.md is the template |
| 10:30 | <annevk> | zcorpan: might be worth considering |
| 10:31 | <annevk> | zcorpan: if we make it a little clearer they don't all have to be completed before the PR is created that might be better |
| 10:32 | <annevk> | zcorpan: but we also get a lot of editorial contributions, for which a lot of this would be noise |
| 10:32 | <annevk> | so hmm |
| 10:43 | <annevk> | zcorpan: I use Sublime Text, but no idea if it has all those features |
| 10:43 | <annevk> | I used to use TextWrangler, but it couldn't handle "source" very well |
| 10:59 | <zcorpan> | annevk: yeah I want to switch away from TextWrangler/BBEdit |
| 11:00 | <zcorpan> | https://www.sublimetext.com/ demos multiple selections |
| 11:04 | <zcorpan> | I'll give this a try |
| 11:38 | <zcorpan> | MikeSmith: vim seems intimidating but several people recommend it. I just never feel like hitting a steep learning curve, but maybe sometime I'll give it a try |
| 11:45 | <MikeSmith> | zcorpan: GVim can help make it less intimidating |
| 11:46 | <MikeSmith> | it’s a GUI program that runs outside the shell |
| 11:47 | <MikeSmith> | with default settings for easier use with a mouse instead of keyboard shortcuts |
| 11:47 | <MikeSmith> | e.g., normal simple visual selection with a mouse |
| 11:48 | <MikeSmith> | which is something that’s not such a great feature that you actually want if you’re running in a shell instead |
| 12:02 | <JakeA> | With WPT, I find myself writing a lot of code to get information about a request the browser made (using the stash). Am I missing an easier way? It'd be nice if I could just query the server log, or use EventSource to get information about requests to a particular URL. |
| 12:05 | <JakeA> | Currently I stash it (https://github.com/jakearchibald/web-platform-tests/blob/accept-encoding-range/fetch/range/resources/long-wav.py#L57) then create an endpoint to read from the stash (https://github.com/jakearchibald/web-platform-tests/blob/accept-encoding-range/fetch/range/resources/stash-take.py) |
| 12:08 | <JakeA> | I'd love to just monitorRequest(url) and get a stream of requests to that URL |
| 12:11 | <Ms2ger> | Better hope that nobody else is using that URL in parallel |
| 12:12 | <JakeA> | Same problem exists with the stash |
| 12:13 | <JakeA> | I guess you could enforce something like a token in the URL |
| 12:14 | <annevk> | JakeA: you're supposed to mint a token for stash |
| 12:14 | <annevk> | JakeA: token() from /common/utils.js is what's typically used |
| 12:16 | <JakeA> | annevk: yeah, that's what I do. monitorRequest could enforce a similar thing if needed. Or: const [urlWithToken, stream] = createMonitoredUrl(url) |
| 12:17 | <annevk> | JakeA: I guess if we abuse the path bit of a stash and use a token as the path as well we could write a get_stash.py and have some kind of JavaScript utility on top |
| 12:18 | <annevk> | JakeA: so the user has to write a Python script that takes a token and stores the stuff they care about, but doesn't need to have retrieval logic |
| 12:18 | <annevk> | JakeA: not sure how much that ends up simplifying though |
| 12:18 | <JakeA> | annevk: A generic retrieval endpoint would be great, but that's usually the easy part |
| 12:19 | <annevk> | JakeA: https://github.com/web-platform-tests/wpt/pull/11164/files is my first stash thingy |
| 12:19 | <annevk> | JakeA: I'm not sure how much can be abstracted there, other than doing the second request and getting the stash value |
| 12:21 | <annevk> | Oh, and I forgot I retrieve the stash value as JSON, that wouldn't work as a generic |
| 12:21 | <annevk> | Well, maybe it would, if everyone obeyed |
| 12:23 | <JakeA> | annevk: with aborting & the range request stuff, I keep wanting to answer questions like: What headers did the browser send? Did the browser actually make a request? Did it follow the redirect? A stream from the server would make this a lot easier. I agree I'd have to make the monitored URLs unique for the test. |
| 12:24 | <annevk> | JakeA: it seems we could do that, by dumping all the request data in the stash |
| 12:24 | <annevk> | JakeA: I guess one question there is when can you retrieve it |
| 12:25 | <JakeA> | annevk: yeah, that's a problem I have today. |
| 12:25 | <annevk> | JakeA: but when the request / response finishes or errors that's probably good enough? |
| 12:26 | <annevk> | My script does the redirect thing btw and it does store data from the request, just not that much |
| 12:26 | <JakeA> | annevk: yeah, although each API has a different way of telling you that. And with media, "finished" is a bit late. |
| 12:26 | <JakeA> | annevk: to clarify, I've done what I need to do. I just feel it's a pain each time I need to do it. |
| 12:28 | <annevk> | JakeA: we could file an issue I suppose |
| 12:28 | <JakeA> | I can write it up |
| 12:28 | <JakeA> | It might only be a problem I've had because of the kind of fetch tests I've been writing recently |
| 12:28 | <annevk> | JakeA: basically what you want is having a handle on an EventSource/WebSocket endpoint to write data to as requests come in |
| 12:29 | <JakeA> | annevk: that's what I said 😀 |
| 12:29 | <JakeA> | It'd be easy to create a stream from either, which would work better in promise tests |
| 12:29 | <annevk> | Yeah sorry, was trying to restate it |
| 12:31 | <annevk> | That kind of setup would greatly simplify a lot of CORS tests too I think |
| 12:31 | <annevk> | E.g., did the preflight happen, did it have the right headers, etc. |
| 12:32 | <JakeA> | Ohh yeah, I imagine they have exactly the same issues. |
| 12:32 | <JakeA> | With redirects you want to monitor more than one url, but I guess you can create multiple monitors |
| 12:33 | <JakeA> | Although there may be cases where it's difficult to make sure the same token is in each URL |
| 12:34 | <annevk> | JakeA: you can redirect to the same path on a different server and forward the token (that's what I do) |
| 12:34 | <annevk> | JakeA: if the EventSource/WebSocket handle is token-based that would work |
| 12:34 | <JakeA> | annevk: Yeah, I was wondering about cases where the token might be stripped, but I can't think of any |
| 12:35 | <annevk> | As long as you can put it in the URL it's okay |
| 12:35 | <annevk> | I guess that means you can't quite test /favicon.ico and such with this |
| 12:36 | <JakeA> | Hmm yeah. Maybe you want a monitorUrl(url, { noTokenIKnowWhatImDoing: true }) for cases where having a token just wouldn't work |
| 12:47 | <annevk> | Well, the problem with that is that you cannot have multiple requests |
| 12:48 | <annevk> | Maybe instead the setup could be that register a set of paths to monitor and you just get all the request objects handed to you |
| 12:49 | <JakeA> | Allowing an array of URLs is important for determining order I suppose |
| 12:52 | <JakeA> | annevk: https://github.com/web-platform-tests/wpt/issues/11298 |
| 14:43 | <devsnek> | is the filesystem api expected to gain traction |
| 15:04 | <devsnek> | oh heh it died like 5 years ago |
| 16:57 | <TabAtkins> | MikeSmith: Command-line support for highlighter should be working now. Just execute highlighter/__init__.py. Run it with -h flag to get information on the arguments you can pass. Basic usage is `__init__.py webidl < input_file.json > highlighted_output.json`. |
| 16:57 | <TabAtkins> | The output will be a JSON object with `html` and `css` keys. |
| 22:20 | <Domenic> | Is there a way to stop getting email about a bug I reported to Firefox Bugzilla? |
| 22:21 | <Domenic> | Watching patches and reviews fly by is not that interesting |
| 22:38 | <MikeSmith> | Domenic: only way I know of is to go into https://bugzilla.mozilla.org/userprefs.cgi?tab=email and uncheck some stuff under Reporter |
| 22:39 | <MikeSmith> | but of course that will affect notifications on all bugs you reported, no just that one |
| 22:40 | <Domenic> | Hmm OK :-/. I guess email-client-level filtering is probably the way to go. |
| 22:40 | <MikeSmith> | TabAtkins: yee-hahー will try it again this weekend |
| 22:43 | <MikeSmith> | Domenic: yeah, though this case makes me think the e-mail preferences could be enhanced with by adding a new row with "A comment is added for a patch" or whatever |
| 23:17 | <MikeSmith> | devsnek: https://wicg.github.io/entries-api/ is the replacement for that |
| 23:17 | <MikeSmith> | File and Directory Entries API |
| 23:18 | <MikeSmith> | I think that’s actually implemented in all four browser engines |
| 23:18 | <devsnek> | hype |
| 23:18 | <devsnek> | does that have writing files too |
| 23:18 | <MikeSmith> | no |
| 23:18 | <MikeSmith> | well not as far as I know |
| 23:18 | <devsnek> | hmm |
| 23:18 | <MikeSmith> | jsbell would be the one to ask for details |
| 23:19 | <devsnek> | i suppose i'll read through it |
| 23:19 | <devsnek> | i want to do something spec-ish for file operations in my runtime |
| 23:20 | <devsnek> | why does the spec include engine-specific properties |
| 23:22 | <MikeSmith> | devsnek: dunno but jsbell can certainly shed some light when he’s around |
| 23:22 | <MikeSmith> | but there’s also https://github.com/WICG/entries-api/blob/gh-pages/EXPLAINER.md |
| 23:24 | <devsnek> | thx |
| 23:52 | <devsnek> | Domenic: if it isn't too much trouble could i bother you about my url implementation? |