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

fix connection crash bug #579

Merged
merged 1 commit into from
Aug 27, 2024
Merged

fix connection crash bug #579

merged 1 commit into from
Aug 27, 2024

Conversation

nkdengineer
Copy link
Contributor

Details

Related Issues

Expensify/App#48070

Automated Tests

Manual Tests

  1. Open the a chat with user B
  2. Right click or long press on the message of user B
  3. Click on Flag as offensive
  4. Verify that the flag page opens

Author Checklist

  • I linked the correct issue in the ### Related Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android / native
    • Android / Chrome
    • iOS / native
    • iOS / Safari
    • MacOS / Chrome / Safari
    • MacOS / Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
Screen.Recording.2024-08-27.at.18.56.55.mov
iOS: Native
iOS: mWeb Safari
Screen.Recording.2024-08-27.at.18.55.32.mov
MacOS: Chrome / Safari
Screen.Recording.2024-08-27.at.18.54.10.mov
MacOS: Desktop
Screen.Recording.2024-08-27.at.18.59.30.mov

Copy link
Contributor

github-actions bot commented Aug 27, 2024

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@nkdengineer
Copy link
Contributor Author

I have read the CLA Document and I hereby sign the CLA

@nkdengineer nkdengineer marked this pull request as ready for review August 27, 2024 12:01
@nkdengineer nkdengineer requested a review from a team as a code owner August 27, 2024 12:01
@melvin-bot melvin-bot bot requested review from bondydaa and removed request for a team August 27, 2024 12:02
@@ -227,7 +227,7 @@ class OnyxConnectionManager {
* Adds the connection to the eviction block list. Connections added to this list can never be evicted.
* */
addToEvictionBlockList(connection: Connection): void {
const connectionMetadata = this.connectionsMap.get(connection.id);
const connectionMetadata = this.connectionsMap.get(connection?.id);
Copy link

Choose a reason for hiding this comment

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

why not just return early above if connection is undefined before trying to access the key?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@getusha We already have a check to return early if connectionMetadata so I think we can do this and no need to add a new if condition

Copy link

@getusha getusha left a comment

Choose a reason for hiding this comment

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

do we need to update this?

expect(connectionsMap.has(connection.id)).toBeTruthy();

@nkdengineer
Copy link
Contributor Author

@getusha I think we don't need to update this case because the data will be available in the test.

Copy link
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

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

Looks good to me, @fabioh8010 would you like to weigh in?

@mountiny
Copy link
Contributor

@fabioh8010 will handle this later but since this is a blocker going to move ahead

@mountiny mountiny merged commit a1a4851 into Expensify:main Aug 27, 2024
5 checks passed
@melvin-bot melvin-bot bot added the Emergency label Aug 27, 2024
Copy link

melvin-bot bot commented Aug 27, 2024

@mountiny looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

Copy link
Contributor

🚀Published to npm in v2.0.66

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

Successfully merging this pull request may close these issues.

None yet

3 participants