Skip to content

[JetBrains] Verify why logic to bypass consent modal fails sometimes #14099

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

Closed
3 tasks
andreafalzetti opened this issue Oct 21, 2022 · 6 comments
Closed
3 tasks
Labels
editor: jetbrains meta: stale This issue/PR is stale and will be closed soon type: bug Something isn't working

Comments

@andreafalzetti
Copy link
Contributor

andreafalzetti commented Oct 21, 2022

Description

Installing third-party plugins in JetBrains IDEs via .gitpod.yml fail sometimes due to the consent modal.

Things to verify:

  • We correctly handle removal of alien_plugins.txt (no false positive caused by os.Remove throwing syscall.EOENT when file does not exist)

  • Check if consent is skipped for plugins installed via a custom registry [1]

  • Verify logic at restart

  • Related code: [1]

  • Relevant chats (internal): [1], [2]

@andreafalzetti andreafalzetti added type: bug Something isn't working editor: jetbrains labels Oct 21, 2022
@andreafalzetti andreafalzetti changed the title [JetBrains] [JetBrains] Verify why logic to bypass consent modal fails sometimes Oct 21, 2022
@andreafalzetti andreafalzetti moved this to Scheduled in 🚀 IDE Team Oct 21, 2022
@andreafalzetti
Copy link
Contributor Author

This could be related or a duplicated of this ticket: #13770

@akosyakov
Copy link
Member

@andreafalzetti I think it is not applicable after #14566 We don't match config folder anymore, but precompute it. Closing?

@andreafalzetti
Copy link
Contributor Author

I am probably missing some context because I am not following what you said.. As far as I understand at the moment, the consent modal could still be an issue sometimes?

The issue were noticed in both prebuild situations or when using a custom registry.

Happy to close if these scenarios are not happening now

@stale
Copy link

stale bot commented Feb 19, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

2 similar comments
@stale
Copy link

stale bot commented May 21, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale
Copy link

stale bot commented Sep 16, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Sep 16, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editor: jetbrains meta: stale This issue/PR is stale and will be closed soon type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants