Plugin import: invalid URL reported when it's valid
See original GitHub issueDescribe the bug Trying to import a plugin with the repository url for the second time (after failing once) reports invalid repository URL on a valid URL.
To Reproduce Steps to reproduce the behavior:
- Try importing a plugin with invalid
package.json
- Close import window, and open it again (url is still there)
- Import the same link again
- “Invalid repository URL shown”
Expected behavior Trying to import again the plugin should import successfully or show error message.
Screenshots
Desktop (please complete the following information):
- OS: MacOS
- Version 1.5.1
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Issue with eslint-plugin-import with eslint 8.2.0 #1448 - GitHub
Failed to load plugin 'import' declared in '.eslintrc.js': Invalid URL: eslintrc.cjs. Atom version: 1.58.0 linter-eslint version: 9.0.0 ...
Read more >Failed to load plugin 'import' declared in '... » eslint-config ...
js This can happen for a couple of reasons: - The plugin name is spelled incorrectly in an ESLint configuration file (e.g. ....
Read more >Node.js Client TypeError [ERR_INVALID_URL]: Invalid URL
I managed to get the vault id via 1Password CLI. it is a string with twenty-six characters. TypeError [ERR_INVALID_URL]: Invalid ...
Read more >Plugin installing error “Download failed. Invalid URL entered.”
You are here: ... This issue usually happens because there are multiple TGMPA libraries loaded and they conflict. This internal library is used...
Read more >Articles How do I resolve the errors "Invalid CSV file" or "the ...
When importing a CSV file containing user information, you may encounter the error "Invalid CSV ... Ensure that the file does not have...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
hey @aabedraba It was a cache issue - The input wasn’t showing the same error message for the next tries - Here it is solved
https://github.com/kubeshop/monokle/pull/1440
Thanks @erdkse !!