Skip to content

Conversation

PRATHAM2002-DS
Copy link

Change description

Description here

Type of change

  • Bug fix (fixes an issue)
  • New feature (adds functionality)

Related issues

Fix #1

Helm Config Changes for Running Tests (Staging PR)

Does this PR require Helm config changes for testing?

  • Tests are NOT required for this commit. (You can proceed with the PR.) ✅
  • No, Helm config changes are not needed. (You can proceed with the PR.) ✅
  • Yes, I have already updated the config-values on enpla9up36. (You can proceed with the PR.) ✅
  • Yes, but I have NOT updated the config-values. (Please update them before proceeding; or, tests will run with default values.)⚠️

Checklists

Development

  • Lint rules pass locally
  • Application changes have been tested thoroughly
  • Automated tests covering modified code pass

Security

  • Security impact of change has been considered
  • Code follows company security practices and guidelines

Code review

  • Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached as necessary
  • "Ready for review" label attached and reviewers assigned
  • Changes have been reviewed by at least one other contributor
  • Pull request linked to task tracker where applicable

@PRATHAM2002-DS PRATHAM2002-DS merged commit 6e2247f into beta Sep 19, 2025
14 of 20 checks passed
public String getValue(String key, String defaultValue) {
return null;
}

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Redis Value Retrieval Ignores Default

The getValue(String key, String defaultValue) method in RedisServiceLocalImpl always returns null. This ignores the defaultValue parameter and violates the method's contract to provide a default when the key is not found or its value is empty, which can lead to NumberFormatException in callers.

Fix in Cursor Fix in Web

int counter = 0;

while (currentSize != expectedFieldKeys && counter++ < totalIterationsAllowed) {
while (currentSize < expectedFieldKeys && counter++ < totalIterationsAllowed) {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Cache Refresh Timing and Loop Condition Issues

The type-def cache refresh now waits for 2.5 seconds instead of the intended 5 seconds due to totalIterationsAllowed being hardcoded to 5, which can cause premature timeouts. Additionally, the loop condition changed from currentSize != expectedFieldKeys to currentSize < expectedFieldKeys, potentially causing early exits if the field key count temporarily exceeds the expected value.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants