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

Edge rebase @ 0.25.1-edge.7 #463

Merged
merged 21 commits into from
Sep 8, 2023
Merged

Edge rebase @ 0.25.1-edge.7 #463

merged 21 commits into from
Sep 8, 2023

Conversation

kingdonb
Copy link
Collaborator

The changes in the edge branch, rebased here so we don't lose any.

As of this posting we have published 0.25.1-edge.2 or 0.25.1690828203 as it would be called on the Marketplace

@kingdonb
Copy link
Collaborator Author

kingdonb commented Sep 6, 2023

573fd62 is even with d624667, but based on the current main: 2ca5aec

@kingdonb
Copy link
Collaborator Author

kingdonb commented Sep 6, 2023

We should probably squash this entire branch now, then divide it into parts and merge the parts into main branch with some review. (CI is passing)

@kingdonb kingdonb changed the title Edge rebase @ 0.25.1-edge.2 Edge rebase @ 0.25.1-edge.7 Sep 8, 2023
@kingdonb
Copy link
Collaborator Author

kingdonb commented Sep 8, 2023

This has been rebased and is even with edge

0.25.1-edge.7 - even with this as of 0e0c7d9

I think we can still squash a bunch of these commits, but at least the edge branch has been lifted up out of the muck and rebased cleanly on the current main. Recommend we use this branch over merging edge back to main. We can start a new edge branch for the minor release after our next patch, planned for tomorrow.

@kingdonb
Copy link
Collaborator Author

kingdonb commented Sep 8, 2023

I have squashed a bunch of commits and rebased out all of the haphazard looking release merges from the edge branch. Cleaned up the version bumps that were executed on the edge release branches. We can put together a nice changelog and roll the release from this branch, 0e0c7d9 from the prior rebase is nearly equivalent to 0f38454 except for the package.json.

Kingdon Barrett and others added 21 commits September 8, 2023 10:28
When I tested it locally it looked like we're calling `flux check` a bit
more often than we should. This may have been fixed by now, but the flag
remains so users who are experiencing issues from `flux check` can
disable it entirely.

* allow users to additionally suppress debugging messages

Emits some debugging messages that are meant for the other authors of
the extension to notice (and users won't be as interested in how many
times we were apparently going to call flux check)

Signed-off-by: Kingdon Barrett <[email protected]>
timeout kill all exec processes. default time is 10s
flux check with async cluster treeview

proper async sources treeview

correct expand all
* preserve collapsible states

safer execs

realtime namespace icons

* 60 seconds exec kill
* namespace UI better
* namespace ui improvements
* module tree-kill

* node 20

missing npm packages

npm audit fix

fully qualify types

my cluster has HelmReleases.cluster.loft.sh and it is wreaking all kinds
of havoc here, let's fix this in the prerelease/edge channel ASAP

Signed-off-by: Kingdon Barrett <[email protected]>

simplify treeview states WIP

api-resources loader WIP

revert Kind.APIGroup

gitops.editor.openKubeconfig

api-resource loader and views

Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
Signed-off-by: Kingdon Barrett <[email protected]>
(Prerelease) Fix fully qualified Flux API names
@kingdonb kingdonb merged commit 289cd1e into main Sep 8, 2023
1 check passed
@kingdonb kingdonb deleted the patch-rebase branch September 8, 2023 14:31
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.

2 participants