Skip to content

Fixed merged conflicts of 2973th pull request#5003

Open
keyboardNinjaWarrior wants to merge 11 commits intotermux:masterfrom
keyboardNinjaWarrior:sixel
Open

Fixed merged conflicts of 2973th pull request#5003
keyboardNinjaWarrior wants to merge 11 commits intotermux:masterfrom
keyboardNinjaWarrior:sixel

Conversation

@keyboardNinjaWarrior
Copy link
Copy Markdown

Merged Pull Request: Add graphics in terminal support: - Sixel and iTerm2 protocols #2973 into the main branch and did my best to resolve the conflicts.

Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 6 to 7.
- [Release notes](https://github.com/actions/upload-artifact/releases)
- [Commits](actions/upload-artifact@v6...v7)

---
updated-dependencies:
- dependency-name: actions/upload-artifact
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Comment on lines 85 to 131
fi

- name: Attach universal APK file
uses: actions/upload-artifact@v6
uses: actions/upload-artifact@v7
with:
name: ${{ env.APK_BASENAME_PREFIX }}_universal
path: |
${{ env.APK_DIR_PATH }}/${{ env.APK_BASENAME_PREFIX }}_universal.apk
${{ env.APK_DIR_PATH }}/output-metadata.json

- name: Attach arm64-v8a APK file
uses: actions/upload-artifact@v6
uses: actions/upload-artifact@v7
with:
name: ${{ env.APK_BASENAME_PREFIX }}_arm64-v8a
path: |
${{ env.APK_DIR_PATH }}/${{ env.APK_BASENAME_PREFIX }}_arm64-v8a.apk
${{ env.APK_DIR_PATH }}/output-metadata.json

- name: Attach armeabi-v7a APK file
uses: actions/upload-artifact@v6
uses: actions/upload-artifact@v7
with:
name: ${{ env.APK_BASENAME_PREFIX }}_armeabi-v7a
path: |
${{ env.APK_DIR_PATH }}/${{ env.APK_BASENAME_PREFIX }}_armeabi-v7a.apk
${{ env.APK_DIR_PATH }}/output-metadata.json

- name: Attach x86_64 APK file
uses: actions/upload-artifact@v6
uses: actions/upload-artifact@v7
with:
name: ${{ env.APK_BASENAME_PREFIX }}_x86_64
path: |
${{ env.APK_DIR_PATH }}/${{ env.APK_BASENAME_PREFIX }}_x86_64.apk
${{ env.APK_DIR_PATH }}/output-metadata.json

- name: Attach x86 APK file
uses: actions/upload-artifact@v6
uses: actions/upload-artifact@v7
with:
name: ${{ env.APK_BASENAME_PREFIX }}_x86
path: |
${{ env.APK_DIR_PATH }}/${{ env.APK_BASENAME_PREFIX }}_x86.apk
${{ env.APK_DIR_PATH }}/output-metadata.json

- name: Attach sha256sums file
uses: actions/upload-artifact@v6
uses: actions/upload-artifact@v7
with:
name: ${{ env.APK_BASENAME_PREFIX }}_sha256sums
path: |
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Must be removed from the PR, not related to the change.

@twaik
Copy link
Copy Markdown
Member

twaik commented Mar 9, 2026

Removing debug_build.yml is not acceptable. Dependabot change is out of scope of PR, you should rebase your changes against master branch.

@twaik
Copy link
Copy Markdown
Member

twaik commented Mar 9, 2026

Merge commits are not acceptable as well, even though it is not filed this way. You should use git rebasing feature, which effectively means history rewrite.

@twaik
Copy link
Copy Markdown
Member

twaik commented Mar 9, 2026

You still have the "rebased pull requeat" commit.

@keyboardNinjaWarrior
Copy link
Copy Markdown
Author

I am confused. What do you want me to do? Remove that commit?

@robertkirkman
Copy link
Copy Markdown
Member

I think that what is meant is, that the commits should all be re-typed and re-committed so that these 2 commits disappear:

image

@keyboardNinjaWarrior
Copy link
Copy Markdown
Author

I think that what is meant is, that the commits should all be re-typed and re-committed so that these 2 commits disappear.

I have squashed the commits together. Let's see, if there is anything wrong, I'll try my best to fix it.

@robertkirkman
Copy link
Copy Markdown
Member

Ok, now try to remove these 2 commits next:

image

Nadeem Anwar and others added 9 commits March 15, 2026 11:18
Add missing {} that change the logic.
- For iterm2 images - catch the error, and cancel the image.
- For sixels - if it happens when resizing the bitmap, than ignore drawing
  outside of the current image.
- Move working bitmap code (drawing current bitmap) to
  WorkingTerminalBitmap class.
- Move bitmap handling code to TerminalBitmap class.
To avoid removing elements from the map while iterating over it.
This should solve the Concurrent Modification Exception in the bitmap
garbage collection.
Avoid crash when BitmapFactory cannot decode image
…last column.

This creates a zero length text run, so skip it.
@keyboardNinjaWarrior
Copy link
Copy Markdown
Author

This bot's commit message is strange. I am unable to view it in my local repository.

image

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.

4 participants