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: handle no-refs response from git-upload-pack for git > 2.41.0 #1862

Conversation

mojavelinux
Copy link
Contributor

closes #1860

@jcubic
Copy link
Contributor

jcubic commented Jan 26, 2024

This can't be merged until Unit Tests for Android are fixed. See #1859

@jcubic
Copy link
Contributor

jcubic commented Apr 2, 2024

Can you rebase (or commit --amend --no-edit) and push force so the tests run again?

@mojavelinux mojavelinux force-pushed the issue-1860-no-refs-upload-pack-response branch from bb5aff2 to 9b5d925 Compare April 4, 2024 07:39
@mojavelinux
Copy link
Contributor Author

Done.

@jcubic
Copy link
Contributor

jcubic commented Apr 4, 2024

Ok, I'm merging the unit tests for this will be added in #1895 (someone provided the same fix, and he added tests).

@jcubic
Copy link
Contributor

jcubic commented Apr 4, 2024

Next time you should create a branch in this repo, the author of that other PR would be able to create add it to your branch (I think it's called stacked PR).

@jcubic jcubic merged commit 112eb7a into isomorphic-git:main Apr 4, 2024
5 checks passed
@jcubic
Copy link
Contributor

jcubic commented Apr 4, 2024

The release failed. Not sure what to do. @seanpoulter can you take a look? The Job take more than 30 minutes and get stopped by Azure. Here is a link:

https://dev.azure.com/isomorphic-git/isomorphic-git/_build/results?buildId=3376&view=results

@seanpoulter
Copy link
Contributor

Is that the first attempt? I'd retry if you can. If you enable timestamps in the logs it seems like our test code was running in the usual amount of time but it stalled after timing out trying to connect to 104.19.163.75 (BrowserStack).

@jcubic
Copy link
Contributor

jcubic commented Apr 4, 2024

I clicked rerun failed jobs, I hope it will run everything.

@isomorphic-git-bot
Copy link
Member

🎉 This PR is included in version 1.25.7 🎉

The release is available on:

Your semantic-release bot 📦🚀

@seanpoulter
Copy link
Contributor

Yay, that looks like it worked and updated the website too.

I'm going on intuition here but I'd assume it's the karma-browserstack-launcher that interacts with BrowserStack. We're using v1.3.0 but v1.6.0 is available, and the repo was archived about a year ago. It's another good signal to rework the test framework.

@mojavelinux
Copy link
Contributor Author

Next time you should create a branch in this repo

I dislike that pattern as it pollutes the upstream repo with branches. The typical workflow is to submit PRs from branches. It should be possible to push to that branch if you are a maintainer of this repository. Otherwise, you can submit a PR to that branch and when it is merged, it will be incorporated into the upstream.

For me, it's no trouble to be asked to rebase and force push. That is all part of the workflow of a PR in my mind.

@jcubic
Copy link
Contributor

jcubic commented Apr 4, 2024

I was only thinking to make PR to PR easier.

modesty pushed a commit to modesty/isomorphic-git that referenced this pull request Apr 9, 2024
jcubic pushed a commit that referenced this pull request Apr 20, 2024
* chore(deps-dev): bump express from 4.17.1 to 4.19.2 (#1891)

Bumps [express](https://github.com/expressjs/express) from 4.17.1 to 4.19.2.
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/master/History.md)
- [Commits](expressjs/express@4.17.1...4.19.2)

---
updated-dependencies:
- dependency-name: express
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* fix: handle no-refs response from git-upload-pack for git > 2.41.0 (#1862)

* ci: Add GitHub Workflow

* Prevent ERR_OSSL_EVP_UNSUPPORTED on Node >= 17

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Dan Allen <dan.j.allen@gmail.com>
@jcubic jcubic mentioned this pull request Apr 20, 2024
16 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cloning empty repository fails if git server uses git >= 2.41.0
4 participants