-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make deploy (and make remote) fail when EXTRA_FILES exist #368
Comments
So per https://matrixlogs.bakkot.com/WHATWG/2021-06-02#L81 —
…you mean that causes the image to get used as expected? That seems to suggest the So sounds like some insight from @tabatkins on this might be needed. |
Actually... no. So that's obviously not a great path forward. |
https://tabatkins.github.io/bikeshed/#img-size
I guess the issue here is the fact that bikeshed doesn't know about these EXTRA_FILES, because they're not actually sent. So it bails. whatwg.org/resources.whatwg.org/build/deploy.sh Lines 65 to 81 in dafacf4
|
It seems like you could fix this by adding width="" and height="" attributes to the source, maybe?
…________________________________
From: Mike Taylor ***@***.***>
Sent: Wednesday, June 2, 2021 13:09
To: whatwg/whatwg.org
Cc: Subscribed
Subject: Re: [whatwg/whatwg.org] Make deploy (and make remote) fail when EXTRA_FILES exist (#368)
https://tabatkins.github.io/bikeshed/#img-size
Note: Bikeshed will only successfully detect the size of local images, and will not attempt to fetch resources over the network, as there is no way for Bikeshed to know whether the size it would get is stable. Using local images is generally preferred, but if you need to use a remote one, consider setting the width and height manually.
I guess the issue here is the fact that bikeshed doesn't know about these EXTRA_FILES, because they're not actually sent. So it bails.
https://github.com/whatwg/whatwg.org/blob/dafacf456feb61c1f748ee47ff93e50c99bf053b/resources.whatwg.org/build/deploy.sh#L65-L81
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#368 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEWYCLROC5KD4OEHIRECG3TQZQU5ANCNFSM457CX2WA>.
|
Yeah -- I was just filing an issue to do that as a workaround for the compat spec. |
Yeah, it's good practice to add width/height anyway, so Bikeshed started warning when it couldn't auto-determine them for you. |
Nah, the error message makes it clearer that it's not finding the image at all:
|
@plinss @tabatkins shouldn't the API-based Bikeshed not try to open such an image or are we expected to include the images in the payload somehow? (If so, how?) |
STR:
make remote
I guess the Bikeshed API gets sad because it can't find the
stroked-text.png
image, and then bails.Looking at https://tabatkins.github.io/bikeshed/#curl, if I change
-F die-on=warning
toF die-on=fatal
,make remote
doesn't fail, but I'm not sure if that's what we want.(Another idea might be to upload static assets to something like resources.whatwg.org, and rewrite relative references. But that sounds like more work?)
The text was updated successfully, but these errors were encountered: