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.

Sign up for GitHub

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

Jump to bottom

Historysize is not big enough #16213

Closed
CCCAUCHY opened this issue Oct 23, 2023 · 2 comments
Closed

Historysize is not big enough #16213

CCCAUCHY opened this issue Oct 23, 2023 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@CCCAUCHY
Copy link

Description of the new feature/enhancement

Historysize is not big enough. I need unlimit historysize.

Proposed technical implementation details (optional)
@CCCAUCHY CCCAUCHY added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 23, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 23, 2023
@lhecker
Copy link
Member

lhecker commented Oct 23, 2023 •
edited
Loading

In that case, please subscribe to #1410 and give it a thumbs up. 🙂
/dup #1410

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 23, 2023
@microsoft-github-policy-service

This comment was marked as duplicate.

Sign in to view
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lhecker @CCCAUCHY