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

TRUNK-6259: Fixing the NullPointerException and ConcurrentModificationException #4778

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

wikumChamith
Copy link
Member

Description of what I changed

Issue I worked on

see https://issues.openmrs.org/browse/TRUNK-

Checklist: I completed these to help reviewers :)

  • My IDE is configured to follow the code style of this project.

    No? Unsure? -> configure your IDE, format the code and add the changes with git add . && git commit --amend

  • I have added tests to cover my changes. (If you refactored
    existing code that was well tested you do not have to add tests)

    No? -> write tests and add them to this commit git add . && git commit --amend

  • I ran mvn clean package right before creating this pull request and
    added all formatting changes to my commit.

    No? -> execute above command

  • All new and existing tests passed.

    No? -> figure out why and add the fix to your commit. It is your responsibility to make sure your code works.

  • My pull request is based on the latest changes of the master branch.

    No? Unsure? -> execute command git pull --rebase upstream master

Copy link
Member

@ibacher ibacher left a comment

Choose a reason for hiding this comment

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

Are we sure this works? I'm happy if it does, I'm just worried we've uncovered a bug that's always existed and was just missed.

// check user's privileges
notifyPrivilegeListeners(getAuthenticatedUser(), privilege, true);
return true;


Copy link
Member

Choose a reason for hiding this comment

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

Why are we adding a blank line here?

Comment on lines 358 to 359


Copy link
Member

Choose a reason for hiding this comment

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

Ditto for the extra blank lines here

@wikumChamith
Copy link
Member Author

Are we sure this works? I'm happy if it does, I'm just worried we've uncovered a bug that's always existed and was just missed.

I tested this locally and it worked well. Btw I am seeing the build errors on the master too.

@dkayiwa
Copy link
Member

dkayiwa commented Oct 8, 2024

Are we sure this works? I'm happy if it does, I'm just worried we've uncovered a bug that's always existed and was just missed.

It will work, only because we are covering the bug again :)

@ibacher
Copy link
Member

ibacher commented Oct 9, 2024

@wikumChamith Missed this part; are you able to reproduce the test failures locally, because I can't (from master), which makes them hard to track down...

@wikumChamith
Copy link
Member Author

@wikumChamith Missed this part; are you able to reproduce the test failures locally, because I can't (from master), which makes them hard to track down...

Locally, mvn clean install passes without any issues. However, when running the Log4JCompatibilityTest individually, it fails. I also re-ran the GitHub actions on my fork's master branch, which also failed.

https://github.com/wikumChamith/openmrs-core/actions/runs/11257808859/job/31302920542

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.

3 participants