Skip to content

Conversation

@nibasbackbase
Copy link
Contributor

Description

A few sentences describing the overall goals of the pull request's commits.

Checklist

  • I made sure, I read CONTRIBUTING.md to put right branch prefix as per my need.
  • I made sure to update CHANGELOG.md.
  • I made sure to update Stream Wiki(only valid in case of new stream module or architecture changes).
  • My changes are adequately tested.
  • I made sure all the SonarCloud Quality Gate are passed.

@nibasbackbase nibasbackbase requested a review from a team as a code owner November 12, 2025 13:15
@nibasbackbase nibasbackbase changed the title Update AccessGroupService.java Added loggers for debugging MAINT-38931 Nov 12, 2025
public Mono<BatchProductGroupTask> assignPermissionsBatch(BatchProductGroupTask task,
Map<User, Map<BusinessFunctionGroup, List<BaseProductGroup>>> usersPermissions) {

log.info("Assigning permissions batch for task: {}, usersPermissions: {}",
Copy link
Collaborator

Choose a reason for hiding this comment

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

should be log all permissions on INFO level?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

we will revert everything after debugging is complete

Copy link
Contributor

Choose a reason for hiding this comment

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

Don't develop for reverting. Change it to debug and set your log levels at runtime.


log.info("Assigning permissions batch for task: {}, usersPermissions: {}",
task, usersPermissions);
System.out.println("Assigning permissions batch for task: " + task + ", usersPermissions: " + usersPermissions);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why use a system output? It's a super weird solution for logging

Copy link
Contributor Author

Choose a reason for hiding this comment

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

we will revert everything after debugging is complete

Copy link
Contributor Author

Choose a reason for hiding this comment

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

system output is to make sure logs are printed without fail and to save some time

Copy link
Contributor

Choose a reason for hiding this comment

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

log.debug will also print when the appropriate level is set in configuration.

@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
B Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

public Mono<BatchProductGroupTask> assignPermissionsBatch(BatchProductGroupTask task,
Map<User, Map<BusinessFunctionGroup, List<BaseProductGroup>>> usersPermissions) {

log.info("Assigning permissions batch for task: {}, usersPermissions: {}",
Copy link
Contributor

Choose a reason for hiding this comment

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

Don't develop for reverting. Change it to debug and set your log levels at runtime.


log.info("Assigning permissions batch for task: {}, usersPermissions: {}",
task, usersPermissions);
System.out.println("Assigning permissions batch for task: " + task + ", usersPermissions: " + usersPermissions);
Copy link
Contributor

Choose a reason for hiding this comment

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

log.debug will also print when the appropriate level is set in configuration.

.collect(Collectors.toList())))
.collect(Collectors.toList());
log.info("Assigned permissions request: {}", request);
System.out.println("Assigned permissions request: " + request);
Copy link
Contributor

Choose a reason for hiding this comment

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

No.

@nibasbackbase
Copy link
Contributor Author

Closing the PR as the issue is Resolved .

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants