search

codecov / feedback

A place to discuss feedback about the pull request and web product experience.
38 stars 9 forks source link

[Self-hosted] Coverage Alert: All Seats Taken error #523

Open nikosatwork opened 2 months ago

nikosatwork commented 2 months ago

Describe the bug We are using self hosted and have generated a license which allows for more users than currently activated. However, when having the 'Auto-activate members' option enabled and a non-activated user lands on a private repo they get a 'Coverage Alert: All Seats Taken' message

Environment (please complete the following information):

We use version 24.7.1

To Reproduce Steps to reproduce the behavior:

  1. Deactivate your seat
  2. Go to a private repo
  3. The error is shown:

Coverage Alert: All Seats Taken Your organization is on the Developer free plan, limited to one seat, which is currently occupied. You can add any amount of seats by upgrading for more flexibility. manage members

Expected behavior The seat should be auto activated, as there are available seats

Screenshots Image

nikosatwork commented 2 months ago

cc @drazisil-codecov @rohan-at-sentry

drazisil-codecov commented 2 months ago

Hi @nikosatwork

We added license logging back to startup a few weeks ago. Can you test rolling and make sure it still says your license is not expired?

drazisil-codecov commented 2 months ago

I'm told the 1 September calver release should also have the logging.

nikosatwork commented 1 month ago

@drazisil-codecov help

In 24.10.1 I get Anauthorized if just having 'Activation Status: False' and visiting a private repo in Codecov

Image

Which should be

Image

Am I missing something perhaps? guest_access: true by the way

Thanks!

drazisil-codecov commented 1 month ago

Hi @nikosatwork Are you logged in at the time, or browsing as a guest? :)

nikosatwork commented 1 month ago

Logged in

nikosatwork commented 1 month ago

I would also want to be able to set guest_access: false and it would still work

drazisil-codecov commented 1 month ago

@aj-codecov We might have to call this a regressed bug. What do you think?

nikosatwork commented 2 weeks ago

Hi @eliatcodecov. Thank you for looking at the login issues. I wanted to note that this case is also related to the others I raised (https://github.com/codecov/feedback/issues/536, https://github.com/codecov/feedback/issues/554, https://github.com/codecov/feedback/issues/555)