-
Notifications
You must be signed in to change notification settings - Fork 67
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
Example traces on the homepage not available #222
Comments
Those trace files are still in an old, uncompatible format, e.g. the trace for that file is stored at https://oughtinc.github.io/static/traces/01GCZNZ1YC0XRE1QHSAV6MPWJD.jsonl instead of https://oughtinc.github.io/static/traces/01GCZNZ1YC0XRE1QHSAV6MPWJD/trace.jsonl. We've been meaning to rerun the recipes so that ice.ought.org can be updated with new code and viewing e.g. https://ice.ought.org/traces/01GCZNZ1YC0XRE1QHSAV6MPWJD includes the latest features, but we've been lagging. I hadn't really thought about this opposite but equally broken perspective. Maybe we should just hide all those traces in the meantime. |
Haha no worries, though just FYI nothing seems to exist at https://oughtinc.github.io/ , and on top of that the CORS request from |
Yeah, right now we're just using |
Right, I'm just saying, it looks like static files are not being served from |
I edited the first sentence of my comment which had said the wrong thing. There is definitely a file at https://oughtinc.github.io/static/traces/01GCZNZ1YC0XRE1QHSAV6MPWJD.jsonl that exists and is being served, which is what we need. But there's no index page at https://oughtinc.github.io/.
I don't know what you mean. https://ice.ought.org/traces/01GCZNZ1YC0XRE1QHSAV6MPWJD looks fine to me and I see no network or console errors. |
Ohhh my bad, I got that confused with the other trace URL you posted. All good now! |
Hello!
When I try to click on "Placebo classification and description" on the homepage, the JS tries to access
https://oughtinc.github.io/static/traces/01GCZNZ1YC0XRE1QHSAV6MPWJD/trace.jsonl
, which 404's. I assume that this is not intentional? :)The text was updated successfully, but these errors were encountered: