- From: Gerald Oskoboiny via RT <sysreq@w3.org>
- Date: Thu, 10 Feb 2022 22:34:07 +0000
- CC: jfontana@yubico.com, nadalin@prodigy.net, public-webauthn@w3.org, wseltzer@w3.org
Hi Jeff, The pr-preview service is run by someone else and we don't have access to the server it's running on. Could you please report these issues in the pr-preview issue tracker? https://github.com/tobie/pr-preview/issues Thanks, sorry we can't be more helpful. * Jeff Hodges via RT <sysreq@w3.org> [2022-02-09 23:21+0000] ><https://www.w3.org/Help/Requests/Ticket/Display.html?id=15869> > Requestors: jdhodges@google.com > CCs: jfontana@yubico.com, nadalin@prodigy.net, public-webauthn@w3.org, wseltzer@w3.org > AdminCCs: > >back on 18-Jan-2022, I pushed two new commits to >https://github.com/w3c/webauthn/pull/1663 (131d68 and e1e6d94). > >However, the PR preview links in the PR's original post continue to use the >earlier commit (41ffcbf) from 14-Jan-2022, even though it got the new date >correct: > >``` ><a href="https://pr-preview.s3.amazonaws.com/w3c/webauthn/pull/1663.html" >title="Last updated on Jan 18, 2022, 11:00 PM UTC (41ffcbf)">Preview</a> | ><a href=" >https://pr-preview.s3.amazonaws.com/w3c/webauthn/1663/bc87207...41ffcbf.html" >title="Last updated on Jan 18, 2022, 11:00 PM UTC (41ffcbf)">Diff</a> >``` >How do we fix this? > >Also, I've noticed some other PR-preview weirdness where it may not >overwrite a prior pr-preview block in a PR's original post and instead add >the new one below the old one, so one ends up with a double set of "Preview >| Diff" links in the PR's original post. unfortunately I presently do not >have an example I can point to for this. > >thanks for any help you can provide, > >=JeffH > > -- Gerald Oskoboiny <gerald@w3.org> http://www.w3.org/People/Gerald/ tel:+1-604-906-1232 (mobile)
Received on Thursday, 10 February 2022 22:34:10 UTC