Seth Nickell

# Papercuts On http://studio.code.org.localhost:3000/home: - [x] Font Awesome: what is https://dsco.code.org/assets/font-awesome-pro, an S3 bucket? CORS policy blocks it - [ ] banner-progress-launch.png: old-style url => 403 - [ ] New...

# It's Alive! Basic "mostly works" has been achieved. There's still broken URLs, missing assets, etc, but its mostly functional. ## Pegasus works: ## Dashboard works: ### Cross-pegasus dashboard cookies...

## One failed unit test from ruby, its about shared cookies: ``` test_shared_cookie_domain FAIL (0.00s) Minitest::Assertion: Expected: "code.org" Actual: "code.org.localhost" /drone/src/pegasus/test/test_request.rb:22:in `block in test_shared_cookie_domain' /drone/src/pegasus/test/test_request.rb:20:in `each' /drone/src/pegasus/test/test_request.rb:20:in `test_shared_cookie_domain' ``` I...

@cat5inthecradle I've tried to come up with substantive reasons, because it feels like it should be important, but I think in the end its partially a style question, but I...

Per @carl-codeorg , we'll need to update OAuth callback urls with our providers, see: https://codedotorg.slack.com/archives/C0T0PNTM3/p1726010223653949?thread_ts=1726005210.839339&cid=C0T0PNTM3

Getting drone test failures on UI tests (but not unit tests), I think they're from the sauce connect tunnel, but the traceback doesn't fit. Might need to debug them on...

It looks like the core issue is that: 1) docker containers use a simple `/etc/host` for resolution (unlike most full distros which use a fancier resolver with caching and support...

This works with Sauce Connect v5, but not with Sauce Connect v4, so this PR is now blocking on: https://github.com/code-dot-org/code-dot-org/pull/60333

I just tested http://studio.code.org.localhost:8080/ : - Chrome: gives a secure context - Firefox: gives a secure context - Safari: doesn't work until you add an entry to /etc/hosts, then it...

I found the problem, this is a straight up bug in grunt-webpack: grunt-webpack never calls compiler.close(), see a description of the issue in webpack's issue tracker https://github.com/webpack/webpack/issues/12342#issuecomment-754869202 If you look...