DTL (Test > Levelbuilder): 8817b219 #58302
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…r consistenncy) (#58209) **CheckboxDropdown**: * minor styles updates for consistency (for disabled state) * fix and update documentation * added `className` prop **IconDropdown**: * minor styles and stories updates for consistency (for disabled state) * added `className` prop **SimpleDropdown**: * minor story update
DTT (Staging > Test) [robo-dtt]
DTS (Levelbuilder > Staging) [robo-dts]
* Add more folders to ESLint import order rule * Stop unrelated change
* [Google Blockly] resize main workspace svg after finished loading * always resize after inject * use fireUiEvent again
* added eyes test * added some UI tests too * "add ui label" * refactored tests * modified name if selector * modified logic
DTT (Staging > Test) [robo-dtt]
feat(lms): improve LMS iframe ux
Specifically, go up from the smallest current generation memory-optimized node size (`cache.r7g.large`) to the second-smallest current generation memory-optimized node size (`cache.r7g.xlarge`). This should effectively double both costs and total storage capacity. At current usage rates, we are [consuming ~2-3% of total storage space per day](https://us-east-1.console.aws.amazon.com/cloudwatch/home?region=us-east-1#metricsV2?graph=~(metrics~(~(~'AWS*2fElastiCache~'DatabaseMemoryUsagePercentage~'CacheClusterId~'ausxf3ubdbzebgu-001~'CacheNodeId~'0001)~(~'...~'ausxf3ubdbzebgu-002~'.~'.)~(~'...~'ausxf3ubdbzebgu-003~'.~'.))~region~'us-east-1~title~'Database*20Memory*20Usage*20Percentage~stat~'Average~view~'timeSeries~start~'-PT168H~end~'P0D)), so doubling that should allow us to comfortably store multiple months worth of session data before we begin expiring. Note that our sessions are currently configured to last at most 200 days, at which point they will be expired regardless of database capacity. This new size does not quite allow us to store a full 200 days worth of sessions, however, so in practice sessions that have not been used recently will end up getting expired before then. We could consider either further increasing database size or configuring a shorter expiration period, which would grant us a bit of a buffer and might be desirable. Not required for initial implementation, though. One other thing to note about this change is that I'm not 100% certain we can change the size of these nodes without disruption to the service; based on [some initial reading](https://repost.aws/knowledge-center/elasticache-redis-minimize-time-scaling), it seems likely that our existing data will be preserved but there's a chance the IP address of the write instance will change, which would require a DTP (or possibly just a cycling of frontends) in order to pick up. In any case, disruption is not actually a problem for us at this point; we are not yet relying on this service for any user-facing functionality, so the worst-case scenario is we lose a bit of metrics data. If anything, this is a nice experiment so we can get a good sense of what a potential upgrade will look like in the future once we have started to rely on these servers.
[LABS-654] Music: Play page pt.1
* Update production welcome email template id * Update other environments too
* AI Chat: hide customization panel when all settings are hidden * PR feedback
DTT (Staging > Test) [robo-dtt]
* add artist strings * add music lab string with ability to add icon on strong part * remove oxford comma * update string so music lab isn't translated
add function to create sagemaker client
Lab2: enable share mode
DTT (Staging > Test) [robo-dtt]
* show deprecation page for calc and eval projects * deprecate algebra game projects (#58168) * deprecate algebra game projects * Delete big_game_remix.feature * Delete big_game_versions.feature * show deprecated course page for script levels with deprecated levels (#58163) * show deprecated course page for deprecated levels * safely check whether level exists and is deprecated * Deprecate contract match levels (#58191) * show deprecated course page for deprecated levels * deprecate algebra game projects * Delete big_game_remix.feature * safely check whether level exists and is deprecated * deprecate contract match levels * Delete big_game_versions.feature * Update allthethings.script_json * Update and remove tests
DTT (Staging > Test) [robo-dtt]
* Update monitor_projects * HOTFIX - Force Reload StatSig Secrets (#57478) * Empty commit * Empty commit to force building new production servers to trigger restart to pick up new StatSig secrets. * Use Lowercase Value for `ClusterMode` (#58292) During the DTP which attempted to upsize the Redis cluster we use for session storage (see #58262), the CloudFormation stack update [failed with the error message "Cluster mode updates are not supported while attempting to update additional properties"](https://codedotorg.slack.com/archives/C03CK8FGX/p1714167673511629) According to [this answer](https://repost.aws/questions/QUj6IF3l-qSsKKkD3yxY_EDw/elasticache-cluster-mode-updates-are-not-supported-while-attempting-to-update-additional-properties#ANrtmd6mpHRYaDBcihifZyhg) on AWS re:Post, it seems like this is an issue with CFN documentation. Specifically, the documentation claims that the `ClusterMode` property should have a value starting with an uppercase letter; either `Enabled` or `Disabled`, but in reality it expects an entirely lowercase value; either `enabled` or `disabled`. Because of that discrepancy, CloudFormation thinks we are attempting to update `ClusterMode` when we're really just trying to update `CacheNodeType` To resolve, simply use the expected rather than documented value. --------- Co-authored-by: Mario Gil Correa <66776217+mgc1194@users.noreply.github.com> Co-authored-by: wilkie <david.wilkinson@code.org> Co-authored-by: Nick Lathe <nick.lathe@code.org> Co-authored-by: Turner Riley <56283563+TurnerRiley@users.noreply.github.com> Co-authored-by: Kaitie O <kaitie@code.org> Co-authored-by: Dave Bailey <davidsbailey@users.noreply.github.com> Co-authored-by: Elijah Hamovitz <elijahhamovitz@gmail.com> Co-authored-by: Vijaya Manohararaj <124813947+vijayamanohararaj@users.noreply.github.com> Co-authored-by: Eric Aderhold <eric.aderhold@code.org> Co-authored-by: Sanchit Malhotra <85528507+sanchitmalhotra126@users.noreply.github.com> Co-authored-by: carl-codeorg <131809324+carl-codeorg@users.noreply.github.com> Co-authored-by: Emily Eastlake <emily.eastlake@code.org> Co-authored-by: bencodeorg <ben@code.org> Co-authored-by: Hannah Bergam <hannah.bergam@code.org> Co-authored-by: Jim Thomason <jim@japanesewartuba.com> Co-authored-by: Dayne <dayne@code.org> Co-authored-by: D Buchanan <146779710+unlox775-code-dot-org@users.noreply.github.com> Co-authored-by: Ryan Shipp <1382374+rshipp@users.noreply.github.com> Co-authored-by: Brendan Reville <breville@users.noreply.github.com> Co-authored-by: fisher-alice <107423305+fisher-alice@users.noreply.github.com> Co-authored-by: Bethany Connor <46464143+bethanyaconnor@users.noreply.github.com> Co-authored-by: Liam Frye-Mason <liam.fryemason@code.org> Co-authored-by: Pablo M <108825710+pablo-code-org@users.noreply.github.com> Co-authored-by: Seth Nickell <snickell@gmail.com> Co-authored-by: Cassi Brenci <cassi.brenci@code.org> Co-authored-by: cearachew <ceara.chewning@code.org> Co-authored-by: Darin Webb <darin@code.org> Co-authored-by: Molly Moen <molly@code.org> Co-authored-by: Mark Barnes <mark.barnes@code.org> Co-authored-by: Mike Harvey <43474485+mikeharv@users.noreply.github.com> Co-authored-by: juanmanzojr <137838584+juanmanzojr@users.noreply.github.com> Co-authored-by: Jessica Kulwik <jessica@code.org> Co-authored-by: Code.org Deploy Systems <dev@code.org>
DTT (Staging > Test) [robo-dtt]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.