gs://codelab-elements no longer accessible?

[Wu-chang Feng]

Hi,

It looks like something has changed in the permissions of the codelab-elements storage bucket.  The bucket has the stylesheets my codelabs utilize.  Is this intentional?  Are there any workarounds?

Thanks,

Wu-chang

[Marc Cohen]

Hi Wu-chang,

Thanks for catching this. I'm looking into it.

Marc

--
You received this message because you are subscribed to the Google Groups "codelab-authors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codelab-autho...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/codelab-authors/CAGV4%3DhansAtYZa%2Bm1kyjPgqmFATMBHFi6b0tn2HLOA_oa9-jrg%40mail.gmail.com.

[Timotei-Vlad Cipariu]

I'm having the same problem, I noticed there's an auth param, I ran claat -h, however I'm not sure how to generate it or if it helps.

[Marc Cohen]

Thanks Tim, we're working on it.  This is due to some clean up of legacy resources but we missed the dependency on this bucket. We're trying to restore it. Will keep you and others posted on this thread.

To view this discussion on the web, visit https://groups.google.com/d/msgid/codelab-authors/899d5902-5491-4b59-b63e-3255c0f7f931n%40googlegroups.com.

--

Marc Cohen

Web: mco.dev

Email: ma...@mco.dev

Q: Why is this email three sentences or less?

A: three.sentenc.es

[Khalil Hammami]

Hi Marc,

is Google going to keep hosting those files in the future? (honestly we're taking advantage of Google CDN)

as work around, you may host them to your own CDN/hosting provider and then update your codelabs with claat by adding the option "-prefix"

https://github.com/googlecodelabs/tools/blob/main/claat/main.go

Khalil Hammami

[Marc Cohen]

Hi Khalil,

I'd like to continue serving them from Google Cloud Storage as a public service, but you're right that people can serve their own copies, which would avoid the dependency that just broke. I'm now regenerating the resources from the public codelab-elements repo and running into some versioning challenges. Will let you know when I have a new copy available.

To view this discussion on the web, visit https://groups.google.com/d/msgid/codelab-authors/bb448b45-71bf-4447-97f6-fcffeb105694n%40googlegroups.com.

[Marc Cohen]

p.s. If anyone has a copy of those codelab-elements resources they can share publicly, that may unblock some folks on this list.

To view this discussion on the web, visit https://groups.google.com/d/msgid/codelab-authors/CAAZnQAQ-F4bXxci1q8YGENFjAy17evp20_iy1omWwt4g3EgNPg%40mail.gmail.com.

[Phạm Xuân Lâm]

Here you are:

https://codelabs-preview.appspot.com/libs/codelab-elements.css

https://codelabs-preview.appspot.com/libs/prettify.css

https://codelabs-preview.appspot.com/libs/codelab-elements.js

https://codelabs-preview.appspot.com/libs/prettify.js

https://codelabs-preview.appspot.com/libs/custom-elements.min.js

https://codelabs-preview.appspot.com/libs/native-shim.js

To view this discussion on the web, visit https://groups.google.com/d/msgid/codelab-authors/CAPmrbqrB%3DUCbz7PU2DyZ38bDz-2W7PEWFnvNMr5QQA%3DppBR68w%40mail.gmail.com.

[Marc Cohen]

Awesome, thanks!  I'll drop those in a bucket and test them now.

Marc Cohen

Web: mco.dev

Email: m...@google.com

[Marc Cohen]

Those seem to be working, I've put them in a new bucket gs://codelab-elements-tmp. To work around this problem, in your index.html file, change occurrences of:

https://storage.googleapis.com/codelab-elements

to 

https://storage.googleapis.com/codelab-elements-tmp

 

Note the "-tmp" suffix is the only change.

Let me know if that doesn't work. I'll keep working on getting the non-tmp bucket restored but this should hopefully unblock some folks.

[Marc Cohen]

And, per Khalil's point, you can also work around this by serving those resource files using your own method, and either hacking your index.html files to reference your location, or use the --prefix option to regenerate your labs with the alternate source. Serving your own copy, of course, reduces your dependencies. :)

[Tamimi Ahmad]

Thanks for the update on this folks! 

@Marc - we'll be waiting on your updated fix. In the meantime we'll use the -temp location and see this fixes our issue

To view this discussion on the web, visit https://groups.google.com/d/msgid/codelab-authors/CAAZnQARQwj2cFBoua1UytZbzZB-tHcGxWe1FkZyhdnsVxEqYrw%40mail.gmail.com.

--

Best Regards,

Tamimi, Ahmad

[Marc Cohen]

 Looks like I've lost access to the codelab-elements bucket so I've created a new one (claat-public) and am in the process of changing the claat code to use that new bucket name. I'm not planning on removing the work-around bucket (codelab-elements-tmp) any time soon but if you prefer to switch to something more permanent you could edit your generated code to use claat-public or use the updated claat, once available, to regenerate your labs. Of course, your best bet long-term will be to serve these assets yourself.

I'll ping this thread when the fix is merged. Btw, this PR also fixes the oob oauth problem, which you will see if you try to claat export a codelab source file from Google Docs.

To view this discussion on the web, visit https://groups.google.com/d/msgid/codelab-authors/CAMAqEEkPGhv3EkmzPiJLzR-9NOWmjmz5yjyVX4o3Qoa5vaQuFA%40mail.gmail.com.

[Marc Cohen]

This is merged into the github repo. So you can "git pull" if you have a local copy of the repo and re-built/re-install it, or you can follow the install instructions in the repo readme, or you can download a binary release from this page.

Marc

[Paul Eldridge]

Hey folks! This might be a different topic than this thread, LMK. But since this would be my first "Update" of my claat binary, is there a way to make that a dedicated claat command? Something like "$claat version update" that triggers a download and install of the latest version?

Otherwise I suppose I just overwrite the old claat binary with the new one from the release page or re-run $go install github.com/googlecodelabs/tools/claat@latest and it'll overwrite?

[Axel Thevenot]

Hello Marc, 

Thank you for your temporary bucket. 
I tried to replace the `https://storage.googleapis.com/codelab-elements` with `https://storage.googleapis.com/codelab-elements-tmp` yet I am facing a new issue. 

It indicates a fail to load `https://storage.googleapis.com/codelab-elements-tmp/google_codelab_scss_bin.css.map` (404 ERROR) when I tried to change the:
<link rel="stylesheet" href="https://storage.googleapis.com/codelab-elements/codelab-elements.css"><style>
into:
<link rel="stylesheet" href="https://storage.googleapis.com/codelab-elements-tmp/codelab-elements.css"><style>

Did you faced this issue too ? 

[Marc Cohen]

Two things:

- use claat-public instead of codelab-elements-tmp, since the latter is temporary

- if that doesn't help, can you send me your index.html (privately, and please anything proprietary)

Marc

To view this discussion on the web, visit https://groups.google.com/d/msgid/codelab-authors/ce6fd320-c211-43aa-b06d-c8212b6c0939n%40googlegroups.com.

[Erik Fredericks]

Hi Marc,

I'm actually having the same issue as Axel, though I see a 403: Forbidden error.  

All I tried to do was modify the CSS link in my index.html file - I can send the whole thing if you want but the error appears to be with the link:

<!doctype html>
<html>
<head>
  <meta name="viewport" content="width=device-width, minimum-scale=1.0, initial-scale=1.0, user-scalable=yes">
  <meta name="theme-color" content="#4F7DC9">
  <meta charset="UTF-8">
  <title>CIS680 - Google Cloud Account/Project Setup</title>
  <link rel="stylesheet" href="//fonts.googleapis.com/css?family=Source+Code+Pro:400|Roboto:400,300,400italic,500,700|Roboto+Mono">
  <link rel="stylesheet" href="//fonts.googleapis.com/icon?family=Material+Icons">

  <!-- <link rel="stylesheet" href="https://storage.googleapis.com/codelab-elements/codelab-elements.css"> -->
  <link rel="stylesheet" href="https://storage.googleapis.com/claat-public/codelab-elements.css">

  ...

Note: I also tried with codelab-elements-tmp and received the same error.  Do I need to actually rebuild with claat or can I just modify the HTML?

Thanks!

Erik

To view this discussion on the web, visit https://groups.google.com/d/msgid/codelab-authors/CAPmrbqrs6x5XfogF4_io62Eok2XtLN%2Bgnr19VQ9B_vVDZHLJoQ%40mail.gmail.com.

[Marc Cohen]

Hi Erik,

Looks like a permissions issue. I've just refreshed the perms on those object. Can you try it again?

Marc

To view this discussion on the web, visit https://groups.google.com/d/msgid/codelab-authors/CAPrr24F8cVUoZb-cz9nEPjfQFoqcghMHd4OyUd0Ra1E9GC9AxA%40mail.gmail.com.

[Paul Eldridge]

Hey folks -- was this fixed? I'm still having the rendering issue with 'claat -export' producing a raw markdown object rather than Codelabs formatting. 

[Nick Comeau]

I had success with making sure I was using the newest version of claat:

` go install github.com/googlecodelabs/tools/claat@latest`

and the folder rename here:

https://github.com/googlecodelabs/tools/issues/796#issuecomment-1311052822

I'm not sure both are needed, try the newest claat first and see if `codelab-elements` is replaced with `claat-public` in your index upon a fresh export.