Contributor cannot visualize the namespace in UI
See original GitHub issueI’m a contributor of timonwong
namespace. However, it does not show up in the namespaces list:
But when @timonwong changes my role to Owner, then it shows up.
I already verified that I have the proper role, because I tried to publish an extension on his namespace.
By the way, this is one example where ovsx verify-pat
(https://github.com/eclipse/openvsx/issues/313) would come in handy.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Project members cannot create namespace in the UI ... - GitHub
As the admin, create a new namespace in project1, the Create Namespace button immediately show up in user1's view. Expected Result
Read more >The type or namespace name 'UI' cannot be found for using ...
I have tried to add System.Web as Reference but that still doesn't resolve the stuff. I can't see System.Web.UI and System.Web.UI.
Read more >Namespace or type specified in the project-level Imports ...
Open the Project Designer and switch to the Reference page. · In the Imported namespaces section, verify that the containing element is ...
Read more >Projects and Kubernetes Namespaces with Rancher
Providing a scope for names: Names of resources need to be unique within a namespace, but not across namespaces. Namespaces can not be ......
Read more >Introducing Hierarchical Namespaces - Kubernetes
Let's see HNC in action. Imagine that I do not have namespace creation privileges, but I can view the namespace team-a and create ......
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
@felipecrs PR #437 is running in production.
@amvanbaren I think your implementation makes sense! 😃