Skip to content

Conversation

@nkomonen-amazon
Copy link
Contributor

@nkomonen-amazon nkomonen-amazon commented Jan 10, 2025

Problem

The CC tests are failing in the auth lambda step, saying that the user_code value is not a string

Solution

See code for solution

NOTE: This part is now fixed, but the auth lambda itself has its own separate issue that needs to first be fixed

Handles issue #6318


  • 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.

@nkomonen-amazon nkomonen-amazon changed the title ignore me fix(blah): ignore me Jan 10, 2025
@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.
  • This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
    • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
    • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

@nkomonen-amazon
Copy link
Contributor Author

nkomonen-amazon commented Jan 10, 2025

/runIntegrationTests

@nkomonen-amazon nkomonen-amazon changed the title fix(blah): ignore me fix(e2e): failing Auth Lambda Jan 10, 2025
@nkomonen-amazon nkomonen-amazon marked this pull request as ready for review January 10, 2025 17:21
@nkomonen-amazon nkomonen-amazon requested a review from a team as a code owner January 10, 2025 17:21
@nkomonen-amazon
Copy link
Contributor Author

nkomonen-amazon commented Jan 10, 2025

/runIntegrationTests

@justinmk3
Copy link
Contributor

justinmk3 commented Jan 13, 2025

 TimeoutError: Waiting for selector `*[data-testid='test-input'] input` failed: Waiting failed: 30000ms exceeded

Signed-off-by: nkomonen-amazon <[email protected]>
@nkomonen-amazon nkomonen-amazon merged commit 39473b7 into aws:master Jan 14, 2025
32 checks passed
@nkomonen-amazon nkomonen-amazon deleted the testAuthUtil branch January 14, 2025 02:07
@justinmk3
Copy link
Contributor

is the failing E2E Tests - stable going to continue?

  1) Test how this codebase uses the CodeCatalyst API
       "before all" hook in "Test how this codebase uses the CodeCatalyst API":
     Error: Error: failed to find element matching selector "*[data-testid='allow-access-button']"

avi-alpert pushed a commit to avi-alpert/aws-toolkit-vscode that referenced this pull request Jan 15, 2025
## Problem

The CC tests are failing in the auth lambda step, saying that the
`user_code` value is not a string

## Solution

See code for solution

NOTE: This part is now fixed, but the auth lambda itself has its own
separate issue that needs to first be fixed

---

- 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.

Signed-off-by: nkomonen-amazon <[email protected]>
karanA-aws pushed a commit to karanA-aws/aws-toolkit-vscode that referenced this pull request Jan 17, 2025
## Problem

The CC tests are failing in the auth lambda step, saying that the
`user_code` value is not a string

## Solution

See code for solution

NOTE: This part is now fixed, but the auth lambda itself has its own
separate issue that needs to first be fixed

---

- 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.

Signed-off-by: nkomonen-amazon <[email protected]>
kevluu-aws pushed a commit to kevluu-aws/aws-toolkit-vscode that referenced this pull request Jan 23, 2025
## Problem

The CC tests are failing in the auth lambda step, saying that the
`user_code` value is not a string

## Solution

See code for solution

NOTE: This part is now fixed, but the auth lambda itself has its own
separate issue that needs to first be fixed

---

- 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.

Signed-off-by: nkomonen-amazon <[email protected]>
s7ab059789 pushed a commit to s7ab059789/aws-toolkit-vscode that referenced this pull request Feb 19, 2025
## Problem

The CC tests are failing in the auth lambda step, saying that the
`user_code` value is not a string

## Solution

See code for solution

NOTE: This part is now fixed, but the auth lambda itself has its own
separate issue that needs to first be fixed

---

- 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.

Signed-off-by: nkomonen-amazon <[email protected]>
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.

3 participants