Skip to content

Conversation

@Will-ShaoHua
Copy link
Contributor

@Will-ShaoHua Will-ShaoHua commented Dec 10, 2024

Problem

Remove client side A/B experiment (control, treatment1, treatment2), move it to service side and always assume treatment1

Solution


  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.

License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@github-actions
Copy link

  • This pull request modifies code in src/* but no tests were added/updated.
    • Confirm whether tests should be added or ensure the PR description explains why tests are not required.

@Will-ShaoHua Will-ShaoHua changed the title change supplemental context configuration to be always repomap config(inline-completion): change supplemental context configuration to be always repomap Dec 10, 2024
@Will-ShaoHua Will-ShaoHua changed the title config(inline-completion): change supplemental context configuration to be always repomap config(inline-completion): change supplemental context configuration to always use repomap Dec 10, 2024
assert.strictEqual(actual.supplementalContextItems[3].content.split('\n').length, 50)
})

it('for t2 group, should return global bm25 context and no repomap', async function () {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

skipping because we don't have t2 group now as we set all users to be t1 group.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will remove not needed tests later once the experiment is fully done

@Will-ShaoHua Will-ShaoHua marked this pull request as ready for review December 11, 2024 20:58
@Will-ShaoHua Will-ShaoHua requested review from a team as code owners December 11, 2024 20:58
Copy link
Contributor

@justinmk3 justinmk3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this approved for the upcoming release?

@Will-ShaoHua
Copy link
Contributor Author

Will-ShaoHua commented Dec 12, 2024

Is this approved for the upcoming release?

@justinmk3 yea, it's requested by the team to ship out with Dec 17th release, but I will double check and get explicit approval for all PRs then turn the PR back to ready state

@Will-ShaoHua Will-ShaoHua marked this pull request as draft December 12, 2024 21:11
@Will-ShaoHua Will-ShaoHua marked this pull request as ready for review December 13, 2024 20:41
@Will-ShaoHua Will-ShaoHua merged commit f87a94b into aws:master Dec 13, 2024
29 of 37 checks passed
@Will-ShaoHua Will-ShaoHua deleted the all-repomap branch December 13, 2024 21:11
karanA-aws pushed a commit to karanA-aws/aws-toolkit-vscode that referenced this pull request Jan 17, 2025
…to always use repomap (aws#6205)

## Problem
Remove client side A/B experiment (control, treatment1, treatment2),
move it to service side and always assume treatment1

## Solution


---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).

License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants