Below uses the latest version of Address on Drupal,

"Shanghai" is not a province or state, and "Huangpu Qu" is not a city.

This is exactly same situation as D.C. in U.S.

So, I imagine if you do the same validation on an address in the D.C., then you would see the same invalidation?

Add gpg

Add a manual run trigger

Bumps docker/build-push-action from 3 to 4.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bump docker/build-push-action from 3 to 4

Bumps docker/build-push-action from 3 to 4.

• Release notes
• Commits

updated-dependencies:

• dependency-name: docker/build-push-action dependency-type: direct:production update-type: version-update:semver-major ...

Signed-off-by: dependabot[bot] support@github.com

Update Drupal 10 image

Merge remote-tracking branch 'origin/dependabot/github_actions/docker/build-push-action-4'

Use the folder name as the label for the vscode status bar

For testing, one would need a proxy server. It could be a remote or at your local. Then, you can up those environment variables, so curl, composer and composer-patches would automatically use proxy.

ALL_PROXY=socks5://host.docker.internal:9999
HTTP_PROXY=socks5://host.docker.internal:9999
HTTPS_PROXY=socks5://host.docker.internal:9999

Above example is to let docker container use a socks5 proxy on the host machine at port 9999

With the current stable composer-patches, one would run into errors like what described at the beginning of this issue, after switching to 1.x-dev, it simply works.

I merged it into 1.x. Since there's no automated tests on 1.x, this needs extensive manual testing. Can the folks in this thread please test and confirm this works as expected on 1.x-dev before we cut a new release?

Yes, I tested it. It is working in 1.x. All I need to do is composer require cweagans/composer-patches 1.x-dev . @danepowell Thanks again

This feature can improve a lot of developers' lives in China and some behind corporate firewall. @danepowell Can you please consider roll a minor release? or merge it to 1.x-dev?

Because most packages who use patches specified "cweagans/composer-patches": "~1.0" in their composer.json, there is no easy way to switch a project to use dev-master branch right now to use proxies.

@noot-to-the-noot Thanks a lot for digging into the details. They are very helpful. I was able to put together a PR to fix the issue.

See https://github.com/cweagans/composer-patches/issues/408

Motivation:

Composer supports socks5 proxy, we want the same support in patching.

Approach:

We are currently using a streamer RemoteFilesystem.php, which doesn't support socks5 or socks5h because of protocol limitation. However, we don't really need a streamer, we simply want to download the patch file and move on. So, using a downloader makes sense.