Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: cherry pick PRs for 2.17#15339

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
stirby merged 10 commits intorelease/2.17fromcherry-217
Nov 1, 2024
Merged

chore: cherry pick PRs for 2.17#15339

stirby merged 10 commits intorelease/2.17fromcherry-217
Nov 1, 2024

Conversation

Emyrkand others added10 commitsNovember 1, 2024 16:31
…5305)The subquery on the users table was incorrectly using the username fromthe `workspaces` table, not the `users` table.This passed `sqlc-vet` because the column did exist in the query, itjust was not the correct one.(cherry picked from commit9d03e04)
…15307)Related to[https://github.com/coder/coder/issues/15297](https://github.com/coder/coder/issues/15297#issuecomment-2450052538)- Clearly display this as Daily Active Users- Remove the user limit bar at the top for licensed deployments- Explain in the tooltip that this is for measuring user activity andhas no connection to license consumption(cherry picked from commit4849b4d)
…orgs (#15261)The failure condition being fixed is `w1` and `w2` could belongto different users, organizations, and templates and still cause aserializable failure if run concurrently. This is because the old querydid a `seq scan` on the `workspace_builds` table. Since that is thetable being updated, we really want to prevent that.So before this would fail for any 2 workspaces. Now it only fails if`w1` and `w2` are owned by the same user and organization.(cherry picked from commit854044e)
…15296)closes#14858- [x] TODO: update `build-timeline.png`- [x] TODO: `Best practices` doesn't show up in the sidebar until you'reactually in the doc 🤔[preview](https://coder.com/docs/@bp-speed-up-templates/tutorials/best-practices/speed-up-templates)---------Co-authored-by: EdwardAngert <17991901+EdwardAngert@users.noreply.github.com>Co-authored-by: Muhammad Atif Ali <atif@coder.com>Co-authored-by: Ben Potter <ben@coder.com>(cherry picked from commit18ef954)
These docs were overwritten in the restructure merge.(cherry picked from commit2573838)
…set (#15294)Added example custom roles for admin inspiration, mention of headlessauthentication use case, and user-activated password reset.(cherry picked from commite9fbfcc)
Adds information on workspace build timings in workspace lifecycle andtemplate troubleshooting docs.(cherry picked from commit399c830)
@stirbystirby changed the titlechore(release): Cherry pick PRs for 2.17chore(release): cherry pick PRs for 2.17Nov 1, 2024
@stirbystirby changed the titlechore(release): cherry pick PRs for 2.17chore: cherry pick PRs for 2.17Nov 1, 2024
@stirbystirby merged commit9a444b3 intorelease/2.17Nov 1, 2024
35 of 36 checks passed
@stirbystirby deleted the cherry-217 branchNovember 1, 2024 18:39
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsNov 1, 2024
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers

@sreyasreyasreya approved these changes

@bpmctbpmctAwaiting requested review from bpmct

@matifalimatifaliAwaiting requested review from matifali

Assignees

@stirbystirby

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

7 participants
@stirby@sreya@Emyrk@BrunoQuaresma@DanielleMaywood@coadler@EdwardAngert

[8]ページ先頭

©2009-2025 Movatter.jp