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

Factory.c less than 0 entry object extensions in existence #1863

Closed
389-ds-bot opened this issue Sep 13, 2020 · 5 comments
Closed

Factory.c less than 0 entry object extensions in existence #1863

389-ds-bot opened this issue Sep 13, 2020 · 5 comments
Labels
closed: won't fix Migration flag - Issue
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48803

  • Created at 2016-04-27 04:47:38 by firstyear (@Firstyear)
  • Closed at 2020-04-01 16:19:09 as wontfix
  • Assigned to nobody

There may be a case where it is possible to cause

l217 factory.c
if(ft->existence_count<0)

To be true. This isn't critical, but it should be investigated as it may highlight another unknown issue.

@389-ds-bot 389-ds-bot added the closed: won't fix Migration flag - Issue label Sep 13, 2020
@389-ds-bot 389-ds-bot added this to the FUTURE milestone Sep 13, 2020
@389-ds-bot
Copy link
Author

Comment from nhosoi (@nhosoi) at 2016-05-12 02:48:25

Hi William,

Since the priority is rather low, is it okay to set the milestone to FUTURE?

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2016-05-12 04:33:29

Yes, if I manage to reproduce it, or someone else does, we can get the info here.

@389-ds-bot
Copy link
Author

Comment from nhosoi (@nhosoi) at 2016-05-13 02:22:08

Setting the target milestone to FUTURE.

William, whenever you complete the task, please reset it to the next version at the time.

Thanks!

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-02-11 22:50:18

Metadata Update from @Firstyear:

  • Issue set to the milestone: FUTURE

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2020-04-01 16:19:10

Metadata Update from @mreynolds389:

  • Custom field reviewstatus adjusted to None
  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: won't fix Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant