Skip to content

regression: Thread file upload#32368

Merged
kodiakhq[bot] merged 8 commits intorelease-6.8.0from
reg/thread-file-upload
May 6, 2024
Merged

regression: Thread file upload#32368
kodiakhq[bot] merged 8 commits intorelease-6.8.0from
reg/thread-file-upload

Conversation

@yash-rajpal
Copy link
Copy Markdown
Member

@yash-rajpal yash-rajpal commented May 3, 2024

Proposed changes (including videos or screenshots)

When the user uploads an image to a thread, it gets sent to the channel instead.

Issue(s)

Introduced here: #32324

Steps to test or reproduce

  1. Open a channel
  2. Send a message
  3. Hover the message → Start a thread
  4. Send a message inside the thread
  5. Inside the thread, send an image

Further comments

CORE-421

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented May 3, 2024

⚠️ No Changeset found

Latest commit: b568c01

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@dionisio-bot
Copy link
Copy Markdown
Contributor

dionisio-bot bot commented May 3, 2024

Looks like this PR is ready to merge! 🎉
If you have any trouble, please check the PR guidelines

@yash-rajpal yash-rajpal marked this pull request as ready for review May 3, 2024 15:07
@codecov
Copy link
Copy Markdown

codecov bot commented May 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.41%. Comparing base (048a977) to head (b568c01).

Additional details and impacted files

Impacted file tree graph

@@                Coverage Diff                @@
##           release-6.8.0   #32368      +/-   ##
=================================================
- Coverage          55.41%   55.41%   -0.01%     
=================================================
  Files               2370     2374       +4     
  Lines              52094    52143      +49     
  Branches           10653    10660       +7     
=================================================
+ Hits               28868    28895      +27     
+ Misses             20707    20697      -10     
- Partials            2519     2551      +32     
Flag Coverage Δ
e2e 54.71% <ø> (+<0.01%) ⬆️
unit 75.37% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

debdutdeb
debdutdeb previously approved these changes May 3, 2024
@debdutdeb debdutdeb dismissed their stale review May 3, 2024 15:27

I know what Marcos will ask

Copy link
Copy Markdown
Member

@debdutdeb debdutdeb left a comment

Choose a reason for hiding this comment

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

possible we get tests written for this?

@yash-rajpal yash-rajpal requested a review from a team as a code owner May 3, 2024 16:25
@yash-rajpal yash-rajpal requested a review from debdutdeb May 3, 2024 16:36
@sampaiodiego
Copy link
Copy Markdown
Member

do you know what caused this regression? just so we can take a look for other possible regressions as well

@yash-rajpal
Copy link
Copy Markdown
Member Author

@sampaiodiego This regression was caused by #32324 - when we reverted the encryption of file description. We missed reverting this one line.

I don't think their are anymore regressions related to this.

@sampaiodiego
Copy link
Copy Markdown
Member

sampaiodiego commented May 3, 2024

thx @yash-rajpal .. I'm bit confused though.. because this code used to add the whole msgData not just the tmid field, like:

const msg = await executeSendMessage(userId, {
   // ...
   ...(msgData as Partial<IMessage>),
   // ...
});

why not make it like it was before?

@sampaiodiego
Copy link
Copy Markdown
Member

We missed reverting this one line.

do you mean you didn't use git revert to revert the other PR? that's scary 🙈

@yash-rajpal
Copy link
Copy Markdown
Member Author

I used git revert but there was a conflict in this file and missed that part 😞

@moimran123

This comment has been minimized.

@debdutdeb

This comment has been minimized.

Copy link
Copy Markdown
Member

@dougfabris dougfabris left a comment

Choose a reason for hiding this comment

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

LGTM!

@dougfabris dougfabris added the stat: QA assured Means it has been tested and approved by a company insider label May 6, 2024
@dougfabris dougfabris added this to the 6.8 milestone May 6, 2024
@dionisio-bot dionisio-bot bot added the stat: ready to merge PR tested and approved waiting for merge label May 6, 2024
@kodiakhq kodiakhq bot merged commit a951502 into release-6.8.0 May 6, 2024
@kodiakhq kodiakhq bot deleted the reg/thread-file-upload branch May 6, 2024 20:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stat: QA assured Means it has been tested and approved by a company insider stat: ready to merge PR tested and approved waiting for merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants