Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Ember data 4.11.x to 4.12.x #25272

Merged
merged 28 commits into from
Feb 20, 2024
Merged

Conversation

Monkeychip
Copy link
Contributor

@Monkeychip Monkeychip commented Feb 7, 2024

Upgrading Ember data as a step closer to upgrading ember to 5.x.x

Special blog release for 4.12.x.

Label on Ember data's GH that will help us track codemods, etc for upgrading to 5.x.

From the Ember blog, a note about support for ember data 4.12.x

In addition to the commitments above, we are planning on declaring EmberData 4.12 as a special LTS release.

4.12 will remain an actively supported LTS for the entire duration of the 5.x cycle, extending until the first 6.x LTS is released. This is in addition to our regular LTS support policy, and only applies to the EmberData project

This support extends beyond simple bug-fixes. If minor enhancements can be made to better support new presentation class implementations that support the 4.x series we will willingly accept them. Our goal is simple: we want no one left behind.

TODO:

  • Smoke testing for basic workflows.
  • Test should pass after more than one run back to back (e.g. avoiding flakyness).
  • Enterprise tests pass on multiple runs.

Note:

  • The known flaky transit test is maybe more flaky here. I've hit it on CircleCi several times, but it always resolves after another run. Hoping the glimmer PR sets us up to better address that test.
  • If I run yarn run test:quick on main, the same tests fail there as do on this branch. Making this note for posterity so folks don't think changes here are responsible for those failures.

@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Feb 7, 2024
@Monkeychip Monkeychip added ui do-not-merge and removed hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed labels Feb 7, 2024
@github-actions github-actions bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Feb 7, 2024
Copy link

github-actions bot commented Feb 7, 2024

CI Results:
All Go tests succeeded! ✅

Copy link

github-actions bot commented Feb 7, 2024

Build Results:
All builds succeeded! ✅

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this should be resolved after we upgrade mirage, but that's another PR.

@@ -75,7 +75,7 @@ module('Acceptance | auth', function (hooks) {
let included;
if (backend.type === 'token') {
keys = lastRequest.requestHeaders;
included = 'X-Vault-Token';
included = 'x-vault-token';
Copy link
Contributor

@kiannaquach kiannaquach Feb 14, 2024

Choose a reason for hiding this comment

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

Curious why this was changed to all lower case? Also, does this only happen in test?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

only a test thing. and I wish i knew the answer. in a previous ember upgrade it changed to uppercase and here we're changing it back. 🙃

Copy link
Contributor

@kiannaquach kiannaquach left a comment

Choose a reason for hiding this comment

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

Nice! Thanks for tackling this upgrade - there were a ton of new ember improvements in this minor release!

@@ -134,6 +134,7 @@ module('Acceptance | mfa-login-enforcement', function (hooks) {
assert.dom('h1').includesText(enforcement.name, 'Name renders in title');
assert.dom('h1 svg').hasClass('flight-icon-lock', 'Lock icon renders in title');
assert.dom('[data-test-tab="targets"]').hasClass('active', 'Targets tab is active by default');
await waitFor('[data-test-target]', { timeout: 5000 });
Copy link
Contributor

Choose a reason for hiding this comment

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

This is strange that we need to do this, and I'm wondering if it's because we're using @model in the route template, which is known to cause some issues. Maybe try using this.model in app/templates/vault/cluster/access/mfa/enforcements/enforcement/index.hbs and removing this?

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@chelshaw no luck. Though I did learn something new. Removing the waitFors I always hit the timeout issues even with the change you suggested.

@Monkeychip Monkeychip merged commit 3850d41 into main Feb 20, 2024
31 checks passed
@Monkeychip Monkeychip deleted the ui/VAULT-20170/upgrade-ember-data-v3 branch February 20, 2024 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed ui
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants