custom tap with ssh proxy not working on brew update

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)

I have a custom tap used internally in our company, and we use ssh config like following to proxy the repository:
Host gitlab.example.com
  HostName gitlab.example.com
  user git
  port 22
  ProxyCommand socat - PROXY:{hostname}:%h:%p,proxyport={port},proxyauth={username}:{password}

And it worked with brew tap x/x<EMAIL_ADDRESS>But it will stop working on running brew update.
What happened (include command output)

Command output

brew update                                                                                17:00:00 ⇣80%
zsh:1: command not found: socat
kex_exchange_identification: Connection closed by remote host
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

What you expected to happen

It should just work as brew tap
Step-by-step reproduction instructions (by running brew commands)

See above.
Output of brew config and brew doctor commands

brew config

HOMEBREW_VERSION: 2.4.5-69-g8175e40
ORIGIN: https://github.com/Homebrew/brew
HEAD: 8175e404ea0bdb1cdfd74dba63aee153761f0c3f
Last commit: 10 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 099b6530feeae680ff90cc60de154605d7f8908e
Core tap last commit: 23 minutes ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_EDITOR: code
HOMEBREW_MAKE_JOBS: 16
CPU: 16-core 64-bit kabylake
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
Clang: 11.0 build 1103
Git: 2.27.0 => /usr/local/bin/git
Curl: 7.64.1 => /usr/bin/curl
Java: 14.0.1
macOS: 10.15.5-x86_64
CLT: <IP_ADDRESS>.1.1588476445
Xcode: 11.5

brew doctor

Your system is ready to brew.

What's the output of ls -l $(which socat)?

@gromgit
ls -l $(which socat)                                                                                17:12:52 ⇣76%
lrwxr-xr-x  1 JounQin  admin  33  6 24 00:59 /usr/local/bin/socat -> ../Cellar/socat/<IP_ADDRESS>/bin/socat

It works well when I clone internal repositories.

Try using the full path to socat in your ssh_config, i.e.:
  ProxyCommand /usr/local/bin/socat - PROXY:{hostname}:%h:%p,proxyport={port},proxyauth={username}:{password}

It seems work with full path like /usr/local/bin/socat, but should it be fixed by homebrew also.

It looks more like your own setup needs fixing. ProxyCommand in ssh inherits the environment of whatever ssh is run in, and since a fully-qualified path worked, /usr/local/bin is not in ssh's $PATH for some reason.
Try changing your ProxyCommand back to:
  ProxyCommand socat - PROXY:{hostname}:%h:%p,proxyport={port},proxyauth={username}:{password}

then show us the output of brew update --verbose --debug.

Also, please post the output of brew doctor, as instructed in the issue template.

brew update --verbose --debug                                                                               11:36:59 •100%
+ [[ -z '' ]]
+ [[ -z '' ]]
+ [[ -n '' ]]
+ [[ -n 1 ]]
+ export HOMEBREW_NO_UPDATE_CLEANUP=1
+ HOMEBREW_NO_UPDATE_CLEANUP=1
+ [[ -z '' ]]
+ HOMEBREW_AUTO_UPDATE_SECS=300
+ [[ -e /usr/local/Cellar ]]
+ [[ ! -w /usr/local/Cellar ]]
+ [[ ! -w /usr/local/Homebrew ]]
+ [[ -n '' ]]
+ git --version
+ [[ -n '' ]]
+ export GIT_TERMINAL_PROMPT=0
+ GIT_TERMINAL_PROMPT=0
+ export 'GIT_SSH_COMMAND=ssh -oBatchMode=yes'
+ GIT_SSH_COMMAND='ssh -oBatchMode=yes'
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -z 1 ]]
+ QUIET_ARGS=()
+ [[ -z '' ]]
+ CURL_DISABLE_CURLRC_ARGS=(-q)
+ lock update
+ local name=update
+ local lock_dir=/usr/local/var/homebrew/locks
+ local lock_file=/usr/local/var/homebrew/locks/update
+ [[ -d /usr/local/var/homebrew/locks ]]
+ [[ -w /usr/local/var/homebrew/locks ]]
+ exec
+ exec
+ _create_lock 200 update
+ local lock_fd=200
+ local name=update
+ local ruby=/usr/bin/ruby
+ local python=/usr/bin/python
+ [[ -x /usr/bin/ruby ]]
+ [[ -x /usr/bin/python ]]
+ [[ -x /usr/bin/ruby ]]
+ /usr/bin/ruby -e 'exit(RUBY_VERSION >= '\''1.8.7'\'')'
+ /usr/bin/ruby -e 'File.new(200).flock(File::LOCK_EX | File::LOCK_NB) || exit(1)'
+ git_init_if_necessary
+ safe_cd /usr/local/Homebrew
+ cd /usr/local/Homebrew
+ [[ ! -d .git ]]
+ [[ -d /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core ]]
+ safe_cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core
+ cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core
+ [[ ! -d .git ]]
+ [[ https://github.com/Homebrew/brew != \h\t\t\p\s\:\/\/\g\i\t\h\u\b\.\c\o\m\/\H\o\m\e\b\r\e\w\/\b\r\e\w ]]
+ [[ https://github.com/Homebrew/homebrew-core != \h\t\t\p\s\:\/\/\g\i\t\h\u\b\.\c\o\m\/\H\o\m\e\b\r\e\w\/\h\o\m\e\b\r\e\w\-\c\o\r\e ]]
+ safe_cd /usr/local/Homebrew
+ cd /usr/local/Homebrew
+ [[ -n '' ]]
+ trap '{ /usr/bin/pkill -P $$; wait; exit 130; }' SIGINT
+ local update_failed_file=/usr/local/Homebrew/.git/UPDATE_FAILED
+ rm -f /usr/local/Homebrew/.git/UPDATE_FAILED
+ for DIR in '"$HOMEBREW_REPOSITORY"' '"$HOMEBREW_LIBRARY"/Taps/*/*'
+ [[ -d /usr/local/Homebrew/.git ]]
+ cd /usr/local/Homebrew
+ [[ -n 1 ]]
+ echo 'Checking if we need to fetch /usr/local/Homebrew...'
Checking if we need to fetch /usr/local/Homebrew...
++ repo_var /usr/local/Homebrew
++ local repo_var
++ repo_var=/usr/local/Homebrew
++ [[ /usr/local/Homebrew = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
++ repo_var=
++ echo ''
+ TAP_VAR=
++ upstream_branch
++ local upstream_branch
+++ git symbolic-ref refs/remotes/origin/HEAD
++ upstream_branch=refs/remotes/origin/master
++ [[ -z refs/remotes/origin/master ]]
++ upstream_branch=master
++ [[ -z master ]]
++ echo master
+ UPSTREAM_BRANCH_DIR=master
+ declare UPSTREAM_BRANCH=master
++ git rev-parse -q --verify refs/remotes/origin/master
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git rev-parse -q --verify refs/remotes/origin/master
+ declare PREFETCH_REVISION=bc4a10804586c8f7a55505923dc1c627b66735d4
+ [[ /usr/local/Homebrew = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
++ git tag --list
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git tag --list
+ [[ -z 0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.7.1
0.8
0.8.1
0.9
0.9.1
0.9.2
0.9.3
0.9.4
0.9.5
0.9.8
0.9.9
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7
1.0.8
1.0.9
1.1.0
1.1.1
1.1.10
1.1.11
1.1.12
1.1.13
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.1.9
1.2.0
1.2.1
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.3.0
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.1
1.4.2
1.4.3
1.5.0
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.14
1.5.2
1.5.3
1.5.4
1.5.5
1.5.6
1.5.7
1.5.8
1.5.9
1.6.0
1.6.1
1.6.10
1.6.11
1.6.12
1.6.13
1.6.14
1.6.15
1.6.16
1.6.17
1.6.2
1.6.3
1.6.4
1.6.5
1.6.6
1.6.7
1.6.8
1.6.9
1.7.0
1.7.1
1.7.2
1.7.3
1.7.4
1.7.5
1.7.6
1.7.7
1.8.0
1.8.1
1.8.2
1.8.3
1.8.4
1.8.5
1.8.6
1.9.0
1.9.1
1.9.2
1.9.3
2.0.0
2.0.1
2.0.2
2.0.3
2.0.4
2.0.5
2.0.6
2.1.0
2.1.1
2.1.10
2.1.11
2.1.12
2.1.13
2.1.14
2.1.15
2.1.16
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.1.8
2.1.9
2.2.0
2.2.1
2.2.10
2.2.11
2.2.12
2.2.13
2.2.14
2.2.15
2.2.16
2.2.17
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.2.7
2.2.8
2.2.9
2.3.0
2.4.0
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5 ]]
+ [[ -z '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ for DIR in '"$HOMEBREW_REPOSITORY"' '"$HOMEBREW_LIBRARY"/Taps/*/*'
+ [[ -d /usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda/.git ]]
+ cd /usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda
+ [[ -n 1 ]]
+ echo 'Checking if we need to fetch /usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda...'
Checking if we need to fetch /usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda...
++ git config remote.origin.url
++ repo_var /usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git config remote.origin.url
++ local repo_var
++ repo_var=/usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda
++ [[ /usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
++ repo_var=/alauda/homebrew-alauda
+++ echo -n /alauda/homebrew-alauda
+++ tr -C A-Za-z0-9 _
+++ tr '[:lower:]' '[:upper:]'
++ repo_var=_ALAUDA_HOMEBREW_ALAUDA
++ echo _ALAUDA_HOMEBREW_ALAUDA
+ TAP_VAR=_ALAUDA_HOMEBREW_ALAUDA
++ upstream_branch
++ local upstream_branch
+++ git symbolic-ref refs/remotes/origin/HEAD
+ UPSTREAM_REPOSITORY_URL=https://github.com/Homebrew/brew
+ [[ https://github.com/Homebrew/brew = \h\t\t\p\s\:\/\/\g\i\t\h\u\b\.\c\o\m\/* ]]
+ UPSTREAM_REPOSITORY=Homebrew/brew
+ UPSTREAM_REPOSITORY=Homebrew/brew
+ [[ /usr/local/Homebrew = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
+ [[ -n '' ]]
++ git rev-parse refs/remotes/origin/master
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git rev-parse refs/remotes/origin/master
++ upstream_branch=refs/remotes/origin/master
++ [[ -z refs/remotes/origin/master ]]
++ upstream_branch=master
++ [[ -z master ]]
++ echo master
+ UPSTREAM_BRANCH_DIR=master
+ declare UPSTREAM_BRANCH_ALAUDA_HOMEBREW_ALAUDA=master
++ git rev-parse -q --verify refs/remotes/origin/master
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git rev-parse -q --verify refs/remotes/origin/master
+ GITHUB_API_ETAG=bc4a10804586c8f7a55505923dc1c627b66735d4
+ GITHUB_API_ACCEPT=application/vnd.github.v3.sha
+ GITHUB_API_ENDPOINT=commits/master
++ curl -q --silent --max-time 3 --location --output /dev/null --write-out '%{http_code}' --dump-header /usr/local/Homebrew/.git/GITHUB_HEADERS --user-agent 'Homebrew/2.4.5-86-gbc4a108 (Macintosh; Intel Mac OS X 10.16) curl/7.64.1' --header 'Accept: application/vnd.github.v3.sha' --header 'If-None-Match: "bc4a10804586c8f7a55505923dc1c627b66735d4"' https://api.github.com/repos/Homebrew/brew/commits/master
+ declare PREFETCH_REVISION_ALAUDA_HOMEBREW_ALAUDA=c45d0f73a32c13dbf35d973d8eda4e6b83b4a43a
+ [[ /usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
+ [[ -z '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ for DIR in '"$HOMEBREW_REPOSITORY"' '"$HOMEBREW_LIBRARY"/Taps/*/*'
+ [[ -d /usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/.git ]]
+ cd /usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade
+ [[ -n 1 ]]
+ echo 'Checking if we need to fetch /usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade...'
Checking if we need to fetch /usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade...
++ repo_var /usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade
++ git config remote.origin.url
++ local repo_var
++ repo_var=/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade
++ [[ -z /usr/local/bin/git ]]
++ [[ /usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
++ /usr/local/bin/git config remote.origin.url
++ repo_var=/buo/homebrew-cask-upgrade
+++ echo -n /buo/homebrew-cask-upgrade
+++ tr -C A-Za-z0-9 _
+++ tr '[:lower:]' '[:upper:]'
++ repo_var=_BUO_HOMEBREW_CASK_UPGRADE
++ echo _BUO_HOMEBREW_CASK_UPGRADE
+ TAP_VAR=_BUO_HOMEBREW_CASK_UPGRADE
++ upstream_branch
++ local upstream_branch
+++ git symbolic-ref refs/remotes/origin/HEAD
+ UPSTREAM_REPOSITORY_URL=git@gitlab-ce.alauda.cn:alauda/homebrew-alauda.git
+ [[ git@gitlab-ce.alauda.cn:alauda/homebrew-alauda.git = \h\t\t\p\s\:\/\/\g\i\t\h\u\b\.\c\o\m\/* ]]
+ [[ -n '' ]]
+ [[ -n 1 ]]
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda...'
Fetching /usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda...
+ [[ -n '' ]]
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ [[ -z /usr/local/bin/git ]]
+ /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
++ upstream_branch=refs/remotes/origin/master
++ [[ -z refs/remotes/origin/master ]]
++ upstream_branch=master
++ [[ -z master ]]
++ echo master
+ UPSTREAM_BRANCH_DIR=master
+ declare UPSTREAM_BRANCH_BUO_HOMEBREW_CASK_UPGRADE=master
++ git rev-parse -q --verify refs/remotes/origin/master
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git rev-parse -q --verify refs/remotes/origin/master
+ declare PREFETCH_REVISION_BUO_HOMEBREW_CASK_UPGRADE=f61ca8c408de4f758c7d28e0db687126795c1b30
+ [[ /usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
+ [[ -z '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ for DIR in '"$HOMEBREW_REPOSITORY"' '"$HOMEBREW_LIBRARY"/Taps/*/*'
+ [[ -d /usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart/.git ]]
+ cd /usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart
+ [[ -n 1 ]]
+ echo 'Checking if we need to fetch /usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart...'
Checking if we need to fetch /usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart...
++ repo_var /usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart
++ git config remote.origin.url
++ local repo_var
++ repo_var=/usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart
++ [[ -z /usr/local/bin/git ]]
++ [[ /usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
++ /usr/local/bin/git config remote.origin.url
++ repo_var=/dart-lang/homebrew-dart
+++ echo -n /dart-lang/homebrew-dart
+++ tr -C A-Za-z0-9 _
+++ tr '[:lower:]' '[:upper:]'
++ repo_var=_DART_LANG_HOMEBREW_DART
++ echo _DART_LANG_HOMEBREW_DART
+ TAP_VAR=_DART_LANG_HOMEBREW_DART
++ upstream_branch
++ local upstream_branch
+++ git symbolic-ref refs/remotes/origin/HEAD
zsh:1: command not found: socat
kex_exchange_identification: Connection closed by remote host
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
+ [[ '' = \4\0\4 ]]
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda failed!'
+ UPSTREAM_REPOSITORY_URL=https://github.com/buo/homebrew-cask-upgrade
+ [[ https://github.com/buo/homebrew-cask-upgrade = \h\t\t\p\s\:\/\/\g\i\t\h\u\b\.\c\o\m\/* ]]
+ UPSTREAM_REPOSITORY=buo/homebrew-cask-upgrade
+ UPSTREAM_REPOSITORY=buo/homebrew-cask-upgrade
+ [[ /usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
++ git rev-parse refs/remotes/origin/master
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git rev-parse refs/remotes/origin/master
++ upstream_branch=refs/remotes/origin/master
++ [[ -z refs/remotes/origin/master ]]
++ upstream_branch=master
++ [[ -z master ]]
++ echo master
+ UPSTREAM_BRANCH_DIR=master
+ declare UPSTREAM_BRANCH_DART_LANG_HOMEBREW_DART=master
++ git rev-parse -q --verify refs/remotes/origin/master
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git rev-parse -q --verify refs/remotes/origin/master
+ GITHUB_API_ETAG=f61ca8c408de4f758c7d28e0db687126795c1b30
+ GITHUB_API_ACCEPT=application/vnd.github.v3.sha
+ GITHUB_API_ENDPOINT=commits/master
++ curl -q --silent --max-time 3 --location --output /dev/null --write-out '%{http_code}' --dump-header /usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/.git/GITHUB_HEADERS --user-agent 'Homebrew/2.4.5-86-gbc4a108 (Macintosh; Intel Mac OS X 10.16) curl/7.64.1' --header 'Accept: application/vnd.github.v3.sha' --header 'If-None-Match: "f61ca8c408de4f758c7d28e0db687126795c1b30"' https://api.github.com/repos/buo/homebrew-cask-upgrade/commits/master
+ declare PREFETCH_REVISION_DART_LANG_HOMEBREW_DART=3a50b337efeeacc505ec40e1d6def44b18913347
+ [[ /usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
+ [[ -z '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ for DIR in '"$HOMEBREW_REPOSITORY"' '"$HOMEBREW_LIBRARY"/Taps/*/*'
+ [[ -d /usr/local/Homebrew/Library/Taps/github/homebrew-gh/.git ]]
+ cd /usr/local/Homebrew/Library/Taps/github/homebrew-gh
+ [[ -n 1 ]]
+ echo 'Checking if we need to fetch /usr/local/Homebrew/Library/Taps/github/homebrew-gh...'
Checking if we need to fetch /usr/local/Homebrew/Library/Taps/github/homebrew-gh...
++ repo_var /usr/local/Homebrew/Library/Taps/github/homebrew-gh
++ git config remote.origin.url
++ local repo_var
++ repo_var=/usr/local/Homebrew/Library/Taps/github/homebrew-gh
++ [[ /usr/local/Homebrew/Library/Taps/github/homebrew-gh = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
++ repo_var=/github/homebrew-gh
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git config remote.origin.url
+++ echo -n /github/homebrew-gh
+++ tr -C A-Za-z0-9 _
+++ tr '[:lower:]' '[:upper:]'
++ repo_var=_GITHUB_HOMEBREW_GH
++ echo _GITHUB_HOMEBREW_GH
+ TAP_VAR=_GITHUB_HOMEBREW_GH
++ upstream_branch
++ local upstream_branch
+++ git symbolic-ref refs/remotes/origin/HEAD
+ UPSTREAM_REPOSITORY_URL=https://github.com/dart-lang/homebrew-dart
+ [[ https://github.com/dart-lang/homebrew-dart = \h\t\t\p\s\:\/\/\g\i\t\h\u\b\.\c\o\m\/* ]]
+ UPSTREAM_REPOSITORY=dart-lang/homebrew-dart
+ UPSTREAM_REPOSITORY=dart-lang/homebrew-dart
+ [[ /usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
++ git rev-parse refs/remotes/origin/master
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git rev-parse refs/remotes/origin/master
++ upstream_branch=refs/remotes/origin/master
++ [[ -z refs/remotes/origin/master ]]
++ upstream_branch=master
++ [[ -z master ]]
++ echo master
+ UPSTREAM_BRANCH_DIR=master
+ declare UPSTREAM_BRANCH_GITHUB_HOMEBREW_GH=master
++ git rev-parse -q --verify refs/remotes/origin/master
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git rev-parse -q --verify refs/remotes/origin/master
+ GITHUB_API_ETAG=3a50b337efeeacc505ec40e1d6def44b18913347
+ GITHUB_API_ACCEPT=application/vnd.github.v3.sha
+ GITHUB_API_ENDPOINT=commits/master
++ curl -q --silent --max-time 3 --location --output /dev/null --write-out '%{http_code}' --dump-header /usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart/.git/GITHUB_HEADERS --user-agent 'Homebrew/2.4.5-86-gbc4a108 (Macintosh; Intel Mac OS X 10.16) curl/7.64.1' --header 'Accept: application/vnd.github.v3.sha' --header 'If-None-Match: "3a50b337efeeacc505ec40e1d6def44b18913347"' https://api.github.com/repos/dart-lang/homebrew-dart/commits/master
+ declare PREFETCH_REVISION_GITHUB_HOMEBREW_GH=da6737971c8c4d96d0e63ab035bcfddd96584e62
+ [[ /usr/local/Homebrew/Library/Taps/github/homebrew-gh = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
+ [[ -z '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ for DIR in '"$HOMEBREW_REPOSITORY"' '"$HOMEBREW_LIBRARY"/Taps/*/*'
+ [[ -d /usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases/.git ]]
+ cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases
+ [[ -n 1 ]]
+ echo 'Checking if we need to fetch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases...'
Checking if we need to fetch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases...
++ repo_var /usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases
++ git config remote.origin.url
++ local repo_var
++ repo_var=/usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases
++ [[ /usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git config remote.origin.url
++ repo_var=/homebrew/homebrew-aliases
+++ echo -n /homebrew/homebrew-aliases
+++ tr -C A-Za-z0-9 _
+++ tr '[:lower:]' '[:upper:]'
++ repo_var=_HOMEBREW_HOMEBREW_ALIASES
++ echo _HOMEBREW_HOMEBREW_ALIASES
+ TAP_VAR=_HOMEBREW_HOMEBREW_ALIASES
++ upstream_branch
++ local upstream_branch
+++ git symbolic-ref refs/remotes/origin/HEAD
+ UPSTREAM_REPOSITORY_URL=https://github.com/github/homebrew-gh
+ [[ https://github.com/github/homebrew-gh = \h\t\t\p\s\:\/\/\g\i\t\h\u\b\.\c\o\m\/* ]]
+ UPSTREAM_REPOSITORY=github/homebrew-gh
+ UPSTREAM_REPOSITORY=github/homebrew-gh
+ [[ /usr/local/Homebrew/Library/Taps/github/homebrew-gh = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
++ git rev-parse refs/remotes/origin/master
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git rev-parse refs/remotes/origin/master
++ upstream_branch=refs/remotes/origin/master
++ [[ -z refs/remotes/origin/master ]]
++ upstream_branch=master
++ [[ -z master ]]
++ echo master
+ UPSTREAM_BRANCH_DIR=master
+ declare UPSTREAM_BRANCH_HOMEBREW_HOMEBREW_ALIASES=master
++ git rev-parse -q --verify refs/remotes/origin/master
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git rev-parse -q --verify refs/remotes/origin/master
+ GITHUB_API_ETAG=da6737971c8c4d96d0e63ab035bcfddd96584e62
+ GITHUB_API_ACCEPT=application/vnd.github.v3.sha
+ GITHUB_API_ENDPOINT=commits/master
++ curl -q --silent --max-time 3 --location --output /dev/null --write-out '%{http_code}' --dump-header /usr/local/Homebrew/Library/Taps/github/homebrew-gh/.git/GITHUB_HEADERS --user-agent 'Homebrew/2.4.5-86-gbc4a108 (Macintosh; Intel Mac OS X 10.16) curl/7.64.1' --header 'Accept: application/vnd.github.v3.sha' --header 'If-None-Match: "da6737971c8c4d96d0e63ab035bcfddd96584e62"' https://api.github.com/repos/github/homebrew-gh/commits/master
+ declare PREFETCH_REVISION_HOMEBREW_HOMEBREW_ALIASES=f78bcabfe65eb628925fd042ccf321b8c6211a14
+ [[ /usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
+ [[ -z '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ for DIR in '"$HOMEBREW_REPOSITORY"' '"$HOMEBREW_LIBRARY"/Taps/*/*'
+ [[ -d /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/.git ]]
+ cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle
+ [[ -n 1 ]]
+ echo 'Checking if we need to fetch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle...'
Checking if we need to fetch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle...
++ repo_var /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle
++ git config remote.origin.url
++ local repo_var
++ repo_var=/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle
++ [[ -z /usr/local/bin/git ]]
++ [[ /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
++ /usr/local/bin/git con++ repo_var=/homebrew/homebrew-bundle
fig remote.origin.url
+++ echo -n /homebrew/homebrew-bundle
+++ tr -C A-Za-z0-9 _
+++ tr '[:lower:]' '[:upper:]'
++ repo_var=_HOMEBREW_HOMEBREW_BUNDLE
++ echo _HOMEBREW_HOMEBREW_BUNDLE
+ TAP_VAR=_HOMEBREW_HOMEBREW_BUNDLE
++ upstream_branch
++ local upstream_branch
+++ git symbolic-ref refs/remotes/origin/HEAD
+ UPSTREAM_REPOSITORY_URL=https://github.com/Homebrew/homebrew-aliases
+ [[ https://github.com/Homebrew/homebrew-aliases = \h\t\t\p\s\:\/\/\g\i\t\h\u\b\.\c\o\m\/* ]]
+ UPSTREAM_REPOSITORY=Homebrew/homebrew-aliases
+ UPSTREAM_REPOSITORY=Homebrew/homebrew-aliases
+ [[ /usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
++ git rev-parse refs/remotes/origin/master
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git rev-parse refs/remotes/origin/master
++ upstream_branch=refs/remotes/origin/master
++ [[ -z refs/remotes/origin/master ]]
++ upstream_branch=master
++ [[ -z master ]]
++ echo master
+ UPSTREAM_BRANCH_DIR=master
+ declare UPSTREAM_BRANCH_HOMEBREW_HOMEBREW_BUNDLE=master
++ git rev-parse -q --verify refs/remotes/origin/master
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git rev-parse -q --verify refs/remotes/origin/master
+ GITHUB_API_ETAG=f78bcabfe65eb628925fd042ccf321b8c6211a14
+ GITHUB_API_ACCEPT=application/vnd.github.v3.sha
+ GITHUB_API_ENDPOINT=commits/master
++ curl -q --silent --max-time 3 --location --output /dev/null --write-out '%{http_code}' --dump-header /usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases/.git/GITHUB_HEADERS --user-agent 'Homebrew/2.4.5-86-gbc4a108 (Macintosh; Intel Mac OS X 10.16) curl/7.64.1' --header 'Accept: application/vnd.github.v3.sha' --header 'If-None-Match: "f78bcabfe65eb628925fd042ccf321b8c6211a14"' https://api.github.com/repos/Homebrew/homebrew-aliases/commits/master
+ declare PREFETCH_REVISION_HOMEBREW_HOMEBREW_BUNDLE=d0b6e3d53d42b266e34ee09a8522b55640032dfc
+ [[ /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
+ [[ -z '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ for DIR in '"$HOMEBREW_REPOSITORY"' '"$HOMEBREW_LIBRARY"/Taps/*/*'
+ [[ -d /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask/.git ]]
+ cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask
+ [[ -n 1 ]]
+ echo 'Checking if we need to fetch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask...'
Checking if we need to fetch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask...
++ repo_var /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask
++ git config remote.origin.url
++ local repo_var
++ repo_var=/usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask
++ [[ /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask = \/\u\s\r\/\l\o\c\a\l\/\H\o\m\e\b\r\e\w ]]
++ [[ -z /usr/local/bin/git ]]
++ /usr/local/bin/git config remote.origin.url
++ repo_var=/homebrew/homebrew-cask
+++ echo -n /homebrew/homebrew-cask
+++ tr -C A-Za-z0-9 _
+++ tr '[:lower:]' '[:upper:]'
++ repo_var=_HOMEBREW_HOMEBREW_CASK
++ echo _HOMEBREW_HOMEBREW_CASK
+ TAP_VAR=_HOMEBREW_HOMEBREW_CASK
++ upstream_branch
++ local upstream_branch
+++ git symbolic-ref refs/remotes/origin/HEAD
^C+ UPSTREAM_BRANCH_DIR=
++ /usr/bin/pkill -P 93848
+ GITHUB_API_ETAG=d0b6e3d53d42b266e34ee09a8522b55640032dfc
+ GITHUB_API_ACCEPT=application/vnd.github.v3.sha
+ GITHUB_API_ENDPOINT=commits/master
++ curl -q --silent --max-time 3 --location --output /dev/null --write-out '%{http_code}' --dump-header /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/.git/GITHUB_HEADERS --user-agent 'Homebrew/2.4.5-86-gbc4a108 (Macintosh; Intel Mac OS X 10.16) curl/7.64.1' --header 'Accept: application/vnd.github.v3.sha' --header 'If-None-Match: "d0b6e3d53d42b266e34ee09a8522b55640032dfc"' https://api.github.com/repos/Homebrew/homebrew-bundle/commits/master
+ UPSTREAM_SHA_HTTP_CODE=000
+ [[ -f /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask-fonts/.git/FETCH_HEAD ]]
+ touch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask-fonts/.git/FETCH_HEAD
+ UPSTREAM_SHA_HTTP_CODE=000
+ UPSTREAM_SHA_HTTP_CODE=000
+ UPSTREAM_SHA_HTTP_CODE=000
+ [[ -f /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask-versions/.git/FETCH_HEAD ]]
+ UPSTREAM_SHA_HTTP_CODE=000
+ UPSTREAM_SHA_HTTP_CODE=000
+ UPSTREAM_SHA_HTTP_CODE=000
+ UPSTREAM_SHA_HTTP_CODE=000
+ UPSTREAM_SHA_HTTP_CODE=000
+ [[ -f /usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart/.git/FETCH_HEAD ]]
+ [[ -f /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/.git/FETCH_HEAD ]]
+ touch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask-versions/.git/FETCH_HEAD
+ UPSTREAM_SHA_HTTP_CODE=000
+ [[ -f /usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases/.git/FETCH_HEAD ]]
+ [[ -f /usr/local/Homebrew/Library/Taps/github/homebrew-gh/.git/FETCH_HEAD ]]
+ UPSTREAM_SHA_HTTP_CODE=000
+ [[ -f /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask/.git/FETCH_HEAD ]]
+ [[ -f /usr/local/Homebrew/Library/Taps/homebrew/homebrew-command-not-found/.git/FETCH_HEAD ]]
+ touch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/.git/FETCH_HEAD
+ [[ -f /usr/local/Homebrew/.git/+ [[ -f /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/.git/FETCH_HEAD ]]
+ touch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-command-not-found/.git/FETCH_HEAD
+ touch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases/.git/FETCH_HEAD
+ touch /usr/local/Homebrew/Library/Taps/github/homebrew-gh/.git/FETCH_HEAD
FETCH_HEAD ]]
+ touch /usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart/.git/FETCH_HEAD
+ touch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask/.git/FETCH_HEAD
+ [[ -f /usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/.git/FETCH_HEAD ]]
+ UPSTREAM_SHA_HTTP_CODE=000
+ UPSTREAM_SHA_HTTP_CODE=000
+ UPSTREAM_SHA_HTTP_CODE=000
+ touch /usr/local/Homebrew/.git/FETCH_HEAD
+ touch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/.git/FETCH_HEAD
+ [[ -f /usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/.git/FETCH_HEAD ]]
+ touch /usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/.git/FETCH_HEAD
+ [[ -f /usr/local/Homebrew/Library/Taps/thoughtbot/homebrew-formulae/.git/FETCH_HEAD ]]
+ [[ -f /usr/local/Homebrew/Library/Taps/jounqin/homebrew-x/.git/FETCH_HEAD ]]
+ touch /usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/.git/FETCH_HEAD
+ touch /usr/local/Homebrew/Library/Taps/thoughtbot/homebrew-formulae/.git/FETCH_HEAD
+ touch /usr/local/Homebrew/Library/Taps/jounqin/homebrew-x/.git/FETCH_HEAD
+ [[ -z '' ]]
+ [[ -z '' ]]
+ [[ -z '' ]]
+ [[ 000 = \3\0\4 ]]
+ [[ 000 = \3\0\4 ]]
+ [[ -z '' ]]
+ [[ 000 = \3\0\4 ]]
+ [[ 000 = \3\0\4 ]]
+ [[ -n 1 ]]
+ [[ -n 1 ]]
+ [[ -n 1 ]]
+ [[ -n 1 ]]
+ [[ -z '' ]]
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask-versions...'
Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask-versions...
+ [[ 000 = \3\0\4 ]]
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask-fonts...'
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-command-not-found...'
+ [[ -n '' ]]
Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask-fonts...
Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-command-not-found...
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -n 1 ]]
+ [[ -z '' ]]
+ [[ -z '' ]]
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases...'
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-aliases...
+ [[ 000 = \3\0\4 ]]
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ [[ -z '' ]]
+ [[ 000 = \3\0\4 ]]
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core...'
+ [[ -z '' ]]
+ [[ -z '' ]]
+ [[ -z '' ]]
+ [[ -z '' ]]
+ [[ -z /usr/local/bin/git ]]
+ [[ -z '' ]]
+ [[ -z '' ]]
Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core...
+ [[ 000 = \3\0\4 ]]
+ [[ -n '' ]]
+ [[ 000 = \3\0\4 ]]
+ [[ 000 = \3\0\4 ]]
+ [[ -n '' ]]
+ [[ -n 1 ]]
+ [[ 000 = \3\0\4 ]]
+ [[ -n 1 ]]
+ [[ 000 = \3\0\4 ]]
+ [[ -n 1 ]]
+ [[ 000 = \3\0\4 ]]
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart...'
+ [[ -n 1 ]]
+ [[ -z /usr/local/bin/git ]]
Fetching /usr/local/Homebrew/Library/Taps/dart-lang/homebrew-dart...
+ [[ 000 = \3\0\4 ]]
+ [[ -n 1 ]]
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask...'
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade...'
+ [[ -n 1 ]]
+ [[ -n 1 ]]
+ [[ -n '' ]]
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/github/homebrew-gh...'
+ /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
Fetching /usr/local/Homebrew/Library/Taps/github/homebrew-gh...
Fetching /usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade...
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ echo 'Fetching /usr/local/Homebrew...'
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-services...'
+ [[ -n 1 ]]
+ [[ -n 1 ]]
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-cask...
+ /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ [[ -n '' ]]
+ [[ -z /usr/local/bin/git ]]
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/jounqin/homFetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-services...
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ [[ -n '' ]]
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle...'
+ [[ -n '' ]]
+ [[ -z /usr/local/bin/git ]]
ebrew-x...'
+ echo 'Fetching /usr/local/Homebrew/Library/Taps/thoughtbot/homebrew-formulae...'
Fetching /usr/local/Homebrew...
+ [[ -z /usr/local/bin/git ]]
Fetching /usr/local/Homebrew/Library/Taps/jounqin/homebrew-x...
Fetching /usr/local/Homebrew/Library/Taps/thoughtbot/homebrew-formulae...
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ [[ -n '' ]]
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ /usr/local/bin/git fetch --tags + /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
--force origin refs/heads/master:refs/remotes/origin/master
+ [[ -z /usr/local/bin/git ]]
+ [[ -z /usr/local/bin/git ]]
Fetching /usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle...
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ [[ -z /usr/local/bin/git ]]
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ [[ -z /usr/local/bin/git ]]
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ [[ -z /usr/local/bin/git ]]
+ /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ [[ -z /usr/local/bin/git ]]
+ /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ [[ -z /usr/local/bin/git ]]
+ /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ [[ -n '' ]]
+ /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ [[ -z /usr/local/bin/git ]]
+ git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ [[ -z /usr/local/bin/git ]]
+ /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master
+ /usr/local/bin/git fetch --tags --force origin refs/heads/master:refs/remotes/origin/master

Also, please post the output of brew doctor, as instructed in the issue template.

It's simple Your system is ready to brew.

There's nothing obviously wrong with your setup, so you might have been bit by a little-known aspect of SSH itself (I certainly didn't know about it, till I started digging). From man ssh:
ENVIRONMENT
     ssh will normally set the following environment variables:
[...]
     PATH                  Set to the default PATH, as specified when compiling ssh.

If you're not already using Homebrew's own ssh, try that and see if there's any difference; if I remember correctly, the build PATH for all Homebrew formulae should include /usr/local/bin. If not, then I'm out of ideas, and you'll just have to use fully-qualified paths with ProxyCommand.

where ssh                                                                                17:52:30 •100%
/usr/bin/ssh

where socat                                                                                17:57:37 •100%
/usr/local/bin/socat

man ssh displays same content as yours.
I'm still confused what command causes the final error.

Sorry, I had a very bad night, and I'm not thinking straight. The passage I quoted from the ssh man page describes what is set at the remote end of a connection, so it's not relevant to your issue.
But my recommendation still stands: Since the Apple ssh isn't working for you, try installing and using the Homebrew ssh instead. If that doesn't work, you're stuck with using full paths for your ProxyCommand setting.
Regardless, I can't replicate your issue despite everything you've revealed thus far, so it's highly likely there's a problem with your own setup, and there's nothing for Homebrew to fix here.

it's highly likely there's a problem with your own setup, and there's nothing for Homebrew to fix here.

But it works with brew tap and other git commands (clone, push) but fails with brew update.

So if you now brew untap alauda/alauda, then does brew tap alauda/alauda ... work?
If you can re-tap your repo, then there's no reason brew update wouldn't work, since all remote Git operations on that repo would be affected by the same SSH settings.

I tried to untap and then tap, it did throw error, although it did work before...
brew untap alauda/alauda                                                                      16:45:23 ⇣44%
Untapping alauda/alauda...
Untapped 1 formula (36 files, 739.5KB).

brew tap alauda/alauda git@gitlab-ce.alauda.cn:alauda/homebrew-alauda.git --debug             16:56:36 ⇣35%
Updating Homebrew...
==> Tapping as full clone
==> Tapping alauda/alauda
Cloning into '/usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda'...
zsh:1: command not found: socat
kex_exchange_identification: Connection closed by remote host
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Error: Failure while executing; `git clone git@gitlab-ce.alauda.cn:alauda/homebrew-alauda.git /usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda` exited with 128.
/usr/local/Homebrew/Library/Homebrew/utils.rb:265:in `safe_system'
/usr/local/Homebrew/Library/Homebrew/tap.rb:273:in `install'
/usr/local/Homebrew/Library/Homebrew/cmd/tap.rb:65:in `tap'
/usr/local/Homebrew/Library/Homebrew/brew.rb:111:in `<main>'

However, according to the error message, it is caused by git clone git@gitlab-ce.alauda.cn:alauda/homebrew-alauda.git /usr/local/Homebrew/Library/Taps/alauda/homebrew-alauda, and I tried to execute this command manually, it does work...
I still can't believe that there is nothing related to homebrew.

Are you using Zsh as your shell? In which shell startup file did you put your eval $(brew shellenv) line?

Also, are you running git clone and brew update in the same terminal session, or is brew update running in a different environment, like a cron job?

Are you using Zsh as your shell? In which shell startup file did you put your eval $(brew shellenv) line?

Yes, I'm using zsh, but eval $(brew shellenv) does not work too, and I don't find why should I do that.

Also, are you running git clone and brew update in the same terminal session, or is brew update running in a different environment, like a cron job?

Same session.

Well, something's getting lost in the Homebrew -> git -> ssh transition.
Please set up a diagnostic wrapper script as follows:

Create the file /tmp/mycat with the following contents:

#!/usr/bin/env zsh
declare -p > /tmp/mycat.out
exec socat "$@"

chmod +x /tmp/mycat
Edit your ~/.ssh/config and replace socat with /tmp/mycat, i.e.:

Host gitlab.example.com
  HostName gitlab.example.com
  user git
  port 22
  ProxyCommand /tmp/mycat - PROXY:{hostname}:%h:%p,proxyport={port},proxyauth={username}:{password}

Now clone your repo manually, and save the results:
git clone git@gitlab-ce.alauda.cn:alauda/homebrew-alauda.git /tmp/alauda.git
mv /tmp/mycat.out /tmp/mycat.out.git_clone

Then tap your repo via Homebrew, and save the results:
brew tap alauda/alauda git@gitlab-ce.alauda.cn:alauda/homebrew-alauda.git --debug
mv /tmp/mycat.out /tmp/mycat.out.brew_tap

Now upload /tmp/mycat.out.git_clone and /tmp/mycat.out.brew_tap to a GitHub gist, and post the URL. Also capture the output of the git clone and brew tap steps.

Please cheeck https://gist.github.com/JounQin/bc191bdeac74c6d374d1ee3347e0461c

I chatted with the Homebrew maintainers, and it turns out what you're experiencing is intentional: $PATH is sanitized to include only system binary directories (/usr/bin:/bin:/usr/sbin:/sbin) to prevent unintended linkages or dependencies between formulae. Therefore, the only solution to your issue is to use a fully-qualified path to socat in your ssh config.

That's OK, should it be documented or could it caught with a friendly advice message?

We'd accept a pull request to document this but I don't think any maintainers will be working on detecting this case since it's pretty niche.


support marathon event stream OR make hostname in callback configurable

Currently the event subscriptions rely on the os.hostname where goji runs being resolvable from marathon, which may not be the case if running marathon in a container with bridge networking, goji in a container with bridge networking, or both.
This can be alleviated by either:

rely only on the event stream api, where there is a long poll request that is responded only when events happen (in this case marathon never makes a request to goji so the hostname is irrelevant)
OR specify the hostname/IP to use when registering the callback via -server option

If time permits I will create a PR.

Awesome, great point! Id love to support this use case. I would love a PR, either direction you choose to go. It looks like the event stream API was added in 0.9.0, so in order to facilitate backwards compatibility, making the callback URL configurable in addition to adding a flag opting for the stream API would be preferable.
Have you been finding goji useful?


Change regression.py unit test based on change in statsmodels 0.8

Addresses #185. Statsmodels 0.8, released in February, changes the behavior of the predict() method when a DataFrame is passed to the exog argument: it used to drop a row from the returned prediction column if any of the inputs for that row were nan, it now returns that row with nan.
The new behavior is more intuitive than before, and since most urbansim models are probably set up to drop nans before passing to predict() anyway, we'll just change the unit test here to make sure the appropriate nan is returned.

Coverage decreased (-0.05%) to 94.259% when pulling 2b9db0e216853696028346facb7840f8a194bc11 on pksohn:statsmodels into 35f036e6675c0a1508e4e9857ffdd72067093775 on UDST:master.


⚠ Samsung has degraded performance

In 8b6f893, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2371 ms

Resolved: Samsung performance has improved in 997b0d0.


Update Cloud9 Setup Instructions

I have completed some work on Case Manager that's ready for review!
This pull request makes the following changes:

updates the setup instructions to get the page working on a Cloud9 workspace

It relates to the following issue #s:

Fixes #534

[Current coverage][cc-pull] is 99.49% (diff: 100%)

Merging [#544][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master       #544   diff @@
==========================================
  Files            24         24
  Lines           395        395
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            393        393
  Misses            2          2
  Partials          0          0

Powered by Codecov. Last update [427c6c7...3891f3e][cc-compare]
[cc-base-branch]: https://codecov.io/gh/colinxfleming/dcaf_case_management/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/colinxfleming/dcaf_case_management/compare/427c6c7245416e7115a94f11032c2e6a6a6ce9c1...3891f3e6b979ac531ceebd1875d963d6159e8706?src=pr
[cc-pull]: https://codecov.io/gh/colinxfleming/dcaf_case_management/pull/544?src=pr

Thanks a ton, @benjamincrane ! Really appreciate your keeping the readme up to date and strong.
@ewiggins I'm tagging you in to review. Can you replicate these steps in a new cloud9 environment? Let me know if you need a hand.

@colin Yep! I'll work on it tomorrow evening.

Ah crud. I should have done a different branch or something for this commit. What's the git approved way to fix this? Close my pull request?

Okay, I reverted my other commit and will commit that in a separate branch.

Thanks @benjamincrane -- really appreciate your working thru that to keep
the PRs separate.
On Tue, Jul 26, 2016 at 11:45 AM Benjamin Crane<EMAIL_ADDRESS>wrote:

Okay, I reverted my other commit and will commit that in a separate branch.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/colinxfleming/dcaf_case_management/pull/544#issuecomment-235310388,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADsA9G0evEY68gnrIZQJrPoL-B3TbfEcks5qZit_gaJpZM4JUVd2
.

@colinxfleming This is good to go! The commands worked. Good job @benjamincrane!!! This issue reminded me that I wanted to add additional steps to the Cloud9 instructions for complete beginners so the process to get up and running on the project isn't such a pain for them. I'll work on that once issues #544 and #534 are closed in #549.

Thanks a ton @benjamincrane and @ewiggins !

It looks like my revert commit ended up overwriting this commit so I am submitting another pull request to fix that.


Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

Hi,
I've been using styled-components with success (for a react-beautiful-dnd part of my project) for a week or so, then I tried to integrate it to my whole project. Then I got this error that I can't understand :

Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

I went to the conclusion that it was likely to be because of my babel configuration, but this is too obscure for me... could someone help me ?

Updating package react-scripts to v2 solved the problem :)


Ft reset password #4

Description
To test visit
/reset-password
/confirm-password
All pull requests should be related to open issues. Indicate the issue(s) bellow and remove this line:
Fixes #4
How Has This Been Tested?
yarn test
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added necessary inline code documentation
[x] I have added tests that prove my fix is effective and that this feature works
[x] New and existing unit tests pass locally with my changes

@wadleo review required here


Remove openapi.yml in favor of api folder

openapi.yml is marked obsolete but still causing confusion.
https://github.com/CDCgov/prime-reportstream/pull/4742 modified the reports endpoint in this obsolete openapi.yml.
Note that proposals/0004-settings-api/openapi.yml has diverged significantly from the version of openapi.yaml used to created the docs/api folder.
Also re-delete restored obsolete programmers guide.
This PR ...
If you are suggesting a fix for a currently exploitable issue, please disclose the issue to the prime-reportstream team directly outside of GitHub instead of filing a PR, so we may immediately patch the affected systems before a disclosure. See SECURITY.md/Reporting a Vulnerability for more information.
Test Steps:

Include steps to test these changes

Changes

Include a comprehensive list of changes in this PR
(For web UI changes) Include screenshots/video of changes

Checklist
Testing

[ ] Tested locally?
[ ] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[ ] (For Changes to /frontend-react/...) Ran npm run lint:write?
[ ] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Fixes

#issue - List GitHub issues this PR fixes

To Be Done
Create GitHub issues to track the work remaining, if any

#issue

Specific Security-related subjects a reviewer should pay specific attention to

Does this PR introduce new endpoints?

new endpoint A
new endpoint B

Does this PR include changes in authentication and/or authorization of existing endpoints?
Does this change introduce new dependencies that need vetting?
Does this change require changes to our infrastructure?
Does logging contain sensitive data?
Does this PR include or remove any sensitive information itself?

If you answered 'yes' to any of the questions above, conduct a detailed Review that addresses at least:

What are the potential security threats and mitigations? Please list the STRIDE threats and how they are mitigated

Spoofing (faking authenticity)

Threat T, which could be achieved by A, is mitigated by M

Tampering (influence or sabotage the integrity of information, data, or system)
Repudiation (the ability to dispute the origin or originator of an action)
Information disclosure (data made available to entities who should not have it)
Denial of service (make a resource unavailable)
Elevation of Privilege (reduce restrictions that apply or gain privileges one should not have)

Have you ensured logging does not contain sensitive data?
Have you received any additional approvals needed for this change?

Pull reviewers stats
Stats for the last 30 days:

User
Total reviews
Time to review
Total comments

carlosfelix2
16
3h 21m
46

MauriceReeves-usds
15
1h 1m
8

cwinters-usds
15
3d 14h 34m
9

jimduff-usds
13
5h 1m
16

TomNUSDS
13
1h 44m
44

kevinhaube
11
30m
5

jbiskie
11
1h 52m
0

clediggins-usds
11
2h 29m
4

TurkeyFried
9
2h
3

brick-green-agile6
8
2h
4

ahay-agile6
7
48m
0

sethdarragile6
7
54m
2

JosiahSiegel
5
24m
0

snesm
5
5h 53m
2

bgantick
4
2h 27m
3

oslynn
4
14m
0

jh765
4
2h 53m
10

whytheplatypus
3
13m
4

RickHawesUSDS
3
3d 8h 47m
2

jorg3lopez
3
27m
0

rhood23699
3
15m
0

acoushawk
1
1h 10m
0

jeremy-page
1
2m
0

meckila
1
3h 35m
2

@TurkeyFried FYI


SNMP keys don't match config file

It looks like there are a few places in the v3 conditional that reference improperly-cased keys.
EG
https://github.com/arista-eosext/rphm/blob/master/rphm/app.py#L857
In short, the keys in the code don't match the keys in the config file.

ConfigParser converts all keys to lower-case.  rphm --test=parse_only dumps the parsed configs for confirmation.


DynamicBlurView 5.0: crash on convertToARGB8888()

Hi ! First of all I would like to thank you for this library. After upgrading from 4.1 to 5.0 I get a crash from time to time. I'm using it along with PopupDialog. This is the stack trace. Thank you !

Hi @LaurentiuUngur
Could you tell me Device details and os version?
Thanks.

iPhone 11 Pro iOS 13.4.1 Thanks !

please check 5.0.1.

I'll come back soon with a feedback. Thanks for the fast support !

Hi @KyoheiG3 ! It's not crashing anymore, but for whatever reason it seems the blur is not working anymore.

I don't have iPhone 11 Pro Device, So I can't try it.
Could you try the new version? 5.0.2 has released.

Hi @KyoheiG3 . It seems it's fixed. Thanks !


Fix prepaid tag condition

Hello @robert-stanciu,
This PR does a lot more than "fix prepaid tag condition", it targets the main branch instead of develop, has no unit tests, and changes CI/CD configuration.
I think we've also discussed this before, but you cannot add the change of having multiple payments per invoice as the EN 16931 doesn't allow it. I get that your CIUS might do it regardless, but you simple cannot break backwards compatibility for everyone by removing the Invoice::setPayment() method.


Enhanced card border and h5 heading text decoration of cards inside Buy Now section

Is your feature request related to a problem? Please describe.
yes, it'll enhance the user experience.
Describe the solution you'd like
Enhanced card border and h5 heading text-decoration of cards inside Buy Now section
Additional context

Not needed.
Look for some other issues.


US01: pon failure, an error is displayed, and the user is redirected (back) to the register screen.

#125


Fix for issue 3298

If merged, this commit will:

Provide comparative analysis of Data Structures
time/profile performance of parseCommand function
declare commands array as constexpr

@scottschurr  @nbougalis  let me know if this looks okay.

Okay, I have done the suggested changes 👍


Some missing prefixed symbols

In the style file there are some commented out prefixed symbols (e.g. some of the \b... symbols). I imagine this is because of a clash with some base latex command.
We should figure out what to do about these -- ideally keep the super short prefixes we have now and get rid of the preceding definition, if it doesn't muck anything basic up...

I'm also not super attached to the "bold or bar" functionality. I think having \b... will be a problem if we want consistency since, e.g., \bf is not something to overwrite (Right now the bold or bar f command is \bbf.) So, we could do \bb... for all the bolds, \bar... for bars, and \b?... for bolds combined with other things (e.g., \bi... for bold italics).

I believe this has been addressed by #7, so closing for now.


Arming delay slider

It appears that the missile's arming delay slider doesn't always initialise when spawning an ammo crate. This causes the missiles to have no arming delay at all.
Here's how to reproduce the issue:

click on an ammo type from the ACF menu (HE, HEAT, smoke)
if your round type is one of the custom missile/bomb types, scroll down to the arming delay slider. Otherwise, select a missile type first (AGM, BGM, FFAR, bombs, etc...), then proceed to scroll down.
the slider should look like this:

A temporary in-game fix is to select an item from either use the fuse package or round type selections. It seems like this will reload the ACF menu's page, and will fix the arming delay slider. It is also possible to pick the item from the drop-down lists that is already currently selected.
Whatever it is that the drop-down lists do, it fixes the slider. So maybe we could take whichever method they're using and implement it in the ACF menu, so that whenever it is opened/loaded the slider is initialised properly.

This causes the missiles to have no arming delay at all.
It does?  I'll need to check that as I'm sure I made it check for a minimum.  If it doesn't then this is a pretty big bug...

I did everything I could find to make the slider appear properly when it loads.  It still doesn't appear properly when it loads.  I'm basically 'hacking into' the tool at this point to make it show anything at all - I'd love to make it work but it might be more effort than it's worth.

I remember testing this with 2 ammo crates, one spawned with the slider bugged and one after I manually fixed it (and set it to the minimum delay). Using the first crate, I could fire missiles into the ground at point blank range and they'd instantly blow up, while with the latter one, they would bounce off as expected. This is the only reason that I'm mentionning this at all, because it renders the dudding system pretty much useless at the moment.

Turns out the ACF missile's init.lua is using the wrong variable at line 428. It is using:
Round.armdelay
whereas it should be using:
GunData.armdelay
This will make it use the minimum arming delays that are set in the missile definitions, however, it will no longer take the delay that was set with the slider into account. Should be a simple fix.

Finally fixed the data issue with 0153025e9bd893632f30b448158b78d1e3c205fa
The graphical issue remains, but can be fixed by toggling the package types.

Closing as the bug is no longer affecting gameplay. The UI bug remains but can be fixed by cycling guidance packages once (back and forth).


Possible features

Hello, I have tried your application and I love the idea! I have some ideas that I would like to share.

Do you think that it would be possible to warn the user before closing the application or on closing, just minimize the application to tray?
Would it be possible to add an option to "Rest" until turned on, regardless of which window(s) are active?

Hello, we tried to solve the issue.
This is what we did:
Add a confirmation dialog before closing the application and implement minimize to tray functionality. Also add an option for indefinite rest mode.
You can review changes in this commit: https://github.com/mnmnk43434/szr2001-WorkLifeBalance-2/commit/b13fcabb94fa40baf098e1189182fffedc0ad99d.

[!CAUTION]
Disclaimer: The concept of solution was created by AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.

Tf is this bot :)))
To answer your questions, yes.
With the warning thing, it does warn the user by making that BEEP sound, you can increase how many Beeps (warnings) it gives you before closing the apps, I think by default is 3, but you can increase it to 12 if you want, and so you will hear 12 beeps until the applications get minimized. This option is in the Force Work menu, named "Max Warnings"
Which represents how many Beeps the app makes before minimizing the background apps.
And I could add the force rest option, it wouldn't take much, but the bigger problem would be where to have the option, some users might turn it on and forget abut it and think the app is bugged when it doesn't switch to working anymore.

@mnmnk43434 your commit is full of obvious compilation errors!

All I can say is that we won't be replaced by AI anytime soon!

With the warning thing, it does warn the user by making that BEEP sound ...

I think I was unclear 😃. I was thinking about a confirmation whether the user would like to close the application or not. Often times I accidentally click on the Close button and forget about it. Then at the end of the day when I want to see the summary I realize the application was not running for half of the time.
In regards to the minimizing I was thinking about minimizing the WorkLifeBalance application to tray (where one usually finds their background applications like some anti virus application discord etc), instead of the taskbar. This could also fix the idea above, just by minimizing the application to the tray instead of closing.
Anyhow, happy to help out whenever I have got some time to do so.

Ohh yea I understand now :))
sorry for the misunderstanding, those will be an easy thing to add.
I will probably add them in the next update, when I come back to this project because for now I'm working on something else.
My app will notify you when the new update comes, it will display you a pop-up to download the new version.
I will probably gather more feedback and then when I come to this app implement each of them in a new update.

Actually, I will implement these 2 features now, expect an update tomorrow or after a day.

I've made the update, it's live, you should get an update popup when you start the app.
I've added:

You will now have a popup warning when you close the app, the minimizing to tray was more complex than I thought and the popup thing was faar much easier to add
SecondWindow will no longer get hidden behind other windows, so it remains visible
You can now specify another directory for the database, in appsettings.json
If the database gets corrupted, it no longer gets deleted and regenerated, but it's marked as corrupted, and then we generate a new one, this way the data is not lost, it can be recovered.

I may have some time to look into the code and perhaps give a solution to the minimize to tray feature. If I succeed at any time I will open a PR for you to review. ;-)

If you manage to add it, I will probably add a setting in the settings that, once enabled, the app will minimize to tray instead of the toolbar. I had problems with how exactly to implement it using MVVM, and if the user will try to close the app from there then it might not save anymore, because the close button first saves the data, and then shutsdown the app
With the settings thing, people can choose where they want it to be minimized, toolbar or tray.
I've started adding the force state option, so probably later or tomorrow I'll launch the update with it.

I've implemented the new Force State feature, you should get an update popup.
I'll go back and work on my other project.
The Force State option is pretty useful, oftentimes I would just watch movies or shows, and I would appear as AFK because I'm not moving my mouse, now In those moments I can just force the Rest state as active.
Thank you for your feedback!


Question:  Works with Chromecast?

Hey, has anyone tried Freeboard with a Chromecast?
Considering a Chromecast approach rather than HDMI on our tv panels.
Cheers, JB

I don't see why it wouldn't work since Chromecast is just streaming from your phone/tablet/computer.

Casting the tab from Chrome works great.

I haven't had any issues w/chromecast.
Airplay to an Apple TV looks great, too.


Make a map out of the Gazebo simulation

The following tutorial provides a video which explains how to simulate the ROS navigation stack.
http://moorerobots.com/blog/post/3
One of the issues with the tutorial is that they use turtlebot teleoperation to build their map and then the robot uses this map to drive autonomously. However, you can't sudo apt-get install ros-lunar-turtlebot because turtlebot is not in lunar.
Goal: Find a way to get this map, either by using a different teleoperation node, coding a really simple one yourself (an arrow-key press publishes a cmd_vel command) or try to find a different solution!


Extension recommendation for .git files appearing when no .git file is opened

Issue Type: Bug

Open any git repo in VS Code
Open any file in the repo

I get the below prompt:

One would expect this prompt if a .git file was manually opened in the editor and no VS Code extension was installed that could serve .git files. But in my case, no such file was opened.
VS Code version: Code - Insiders 1.41.0-insider (bbf00d8ea6aa7e825ca3393364d746fe401d3299, 2019-12-05T06:56:28.532Z)
OS version: Windows_NT x64 10.0.18363

I could reproduce, let me look at it and I will try to make a PR soon :)

Great catch, this will go into candidate.

Reopening, the PR is not merged yet.

Follow up issue - https://github.com/microsoft/vscode/issues/86676

What about this commit into master? Do we want it to stay there?

Steps to verify:

Start with fresh user data and extensions dir
Open any git repo
Open any file in the repo
Make sure recommendations pop up for .git files is not shown

What about this commit into master? Do we want it to stay there?

No, I will merge into master also because this impacts our insiders.


get a11y-only Hybris instance

dev3 will be able for a11y development purposes

currently we cannot establish a stable, dev-17-like instance of hybris. we'll continue with dev17 then


To further Crop the cropped image would fail all the time

I use the cropper in my project. When I crop the image, I draw the selected area to a canvas and then convert the canvas to a Blob. Then I use URL.createObjectURL to conver the Blob to a url and feed it to the cropper, so that I can further crop it. But when I try to crop it a second time, it would fail all the time. I either got a totally black image or a image that is not the area I selected.
Does anyone know how to solve it? Or am I doing it incorrectly? Thanks!

@adjourn Thanks. I double checked and I'm sure the pixelCrop is correct. One thing I found is that it seems the image I got in the second crop is not a crop of the first crop, but a crop of the original image, even though the original image is replaced by the first crop. There must be a bug in my code and I will try to debug it. Thanks!

I think I found the issue. But I don't know how to fix it. The issue is that, when I get the cropped image, I set the src of the ImageCropper to the new cropped image. Then when I try to use document.getElementsByClassName("ReactCrop__image")[0] to get the image element for cropping, I still get the old image element whose src is the old image. Does anyone have any thought? Thanks!

@bhao-speedline can you post that part of the code?

I found the issue. There was one line of code which I thought was commented turned out to be not. That line reset the src of the HTMLImageElement back to the original uploaded image, and that caused failure of the second crop. Thanks! @adjourn @DominicTobias

Ok glad you found the issue, closing this now


news

i set my country to PH
then run the application smartmirror.py
and then US news displayed </3

Sometimes you have to prepend a language code. en_ph should work.


Text Layout change

Please move the section under "Check if users already have the OneDrive sync client" to a separate purple "Note" box to make it more noticeable? ... "Office is installed per machine, whereas OneDrive needs to be installed per user. If you plan on deploying Office to your organization, you will need to deploy OneDrive.exe separately for additional users on individual machines."

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b65a307a-4572-7255-eaad-34a0884cb93d
Version Independent ID: 976efb44-bf8a-ed55-c854-6c49ecdea722
Content: Deploy OneDrive apps using SCCM
Content Source: OneDrive/deploy-on-windows.md
Service: one-drive
GitHub Login: @kaarins
Microsoft Alias: kaarins

@Skatterbrainz Thank you for this feedback
I will get these suggestions over to the SharePoint team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@Skatterbrainz  Thank you for submitting this feedback.
From our understanding the issue has been resolved. If you feel it hasn't been resolved please re-open this issue.

@officedcosbot close

Thank you!  Sorry I'm slow to reply.


Updated the "Most recent stable version"

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[x ] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR in an attempt to attempt to break out of the Travis build pending status.

Congrats @storrence88 on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Appstudio update test-component-pac-ceyj

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-ceyj-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
23 seconds
init

✅ Succeeded
29 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
56 seconds
sanity-inspect-image

✅ Succeeded
26 seconds
deprecated-base-image-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
22 seconds
sbom-json-check

✅ Succeeded
33 seconds
sanity-label-check

✅ Succeeded
33 seconds
sanity-optional-label-check

✅ Succeeded
7 seconds
show-summary

Pipelines as Code CI/test-component-pac-ceyj-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
18 seconds
clone-repository

✅ Succeeded
34 seconds
build-container

✅ Succeeded
18 seconds
deprecated-base-image-check

✅ Succeeded
18 seconds
sanity-inspect-image

✅ Succeeded
12 seconds
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
1 minute
sanity-optional-label-check

✅ Succeeded
1 minute
sanity-label-check

✅ Succeeded
7 seconds
show-summary


Auto TK Warn Victim

Added a plugin that will warn the TK Victim that they've been TK'd with the default message of "INFO: You were Teamkilled." This plugin is set to false by default in the config.json file.
I know it could be controversial to warn the TK Victim about being TK'd, but we at PSG are using this and haven't seen any difference in retaliatory TKs. It seems most blueberries get more satisfaction out of knowing that they were TK'd over wondering what possible enemy they missed in the treeline that just dunked on them when it was a TK all along.
Because of how some Servers may decide to not warn the TK Victim, that is the reason this is defaulted to be disabled.
It also does not tell the TK Victim who TK'd them, just that they were TK'd.
Updated the original TK Warn to Auto TK Warn Attacker to remove any possible confusion of this addition.

It's an amazing idea but isn't better adding an option for warn filter such as
warnAttacker: true,
warnVictim: true

or putting into array
instead of making a whole another plugin

It's an amazing idea but isn't better adding an option for warn filter such as
warnAttacker: true,
warnVictim: true

or putting into array instead of making a whole another plugin

I'm not super great at coding, this method of a new plugin was easiest for me to accomplish while getting the desired result. I'm all for it if someone else would like to make it into one plugin.


Why can rotary embeddings not be used with cu_seqlen ?

These seem like orthogonal features to me?
Code link

Yes, they're orthogonal.
cu_seqlen is for cases where sequences in the same batch have different lengths, and we remove all the padding tokens and only store the regular tokens (e.g. BERT training).
To apply rotary embedding it'll take a bit more work to figure out the right indices. It's not necessarily hard, but I just never implemented it.
If you play with it and figure out something, let me know!

Sorry I don't understand. Orthogonal to me means unrelated, meaning one can toggle them (cu_seqlen / rotary) any way one wants without affecting the other.

To apply rotary embedding it'll take a bit more work to figure out the right indices. It's not necessarily hard, but I just never implemented it.

But rotary embeddings are applied before the flash attention kernel, so why should that matter for whether or not the kernel operates on sequences of different length (by ignoring padding tokens or not)?

Let's say we have 2 sequences [A B ] and [C D E] in the same batch.
Normally we would store them as [[A B ], [C D E]].
If cu_seqlen is passed, we instead expect the input to be [A B C D E], with cu_seqlen = [0, 2, 5] (indicating that there are 2 sequences, one from index 0 to 2 and one from index 2 to 5).
If we want to apply rotary, the implementation has to be aware that [A B C D E] consists of 2 sequences, one of length 2 and one of length 3.
That's the more complicated indexing that I mentioned, and that is not implemented right now.

Ah! Ok I think I understand. Thank you so much for taking the time to explain!

have a follow up question @tridao
What if I apply rotary to [[A B pad], [C D E]], and then convert it to [A B C D E], with cu_seqlen = [0, 2, 5], and then use that with flash attention? wouldnt that work?

Yes that would work. However, we'd need to convert between the "padded" and "unpadded" formats for each layer.
I think the more efficient way is to implement a version of rotary that can deal with "unpadded" format directly. It might not be that hard, we just have to adjust the indices in the rotary implementation.

Right right! Makes sense, thank you! :)
I might take a look at that in the future we'll see

Just to double check that I understand the code correctly, this has been implemented here: https://github.com/Dao-AILab/flash-attention/commit/b28ec236df49cb57c213a9a4f29beb727adbf65b
correct?


Route middleware prevents route change in case of error

Environment
clean setup
Nuxt project info:

Operating System: Linux
Node Version:     v16.14.2
Nuxt Version:     3.3.2
Nitro Version:    2.3.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-dnrwod?file=middleware/page.global.ts
Describe the bug
We use dynamic pages and route middleware to fetch content for dynamic routes.

In the middleware, we check the to.path in order to fetch content for the current path.
In the case of a 404 error from the API, we want to show an error page.
To display the error page, we use the showError function within a try-catch block.
The error page is shown correctly, but there is a major issue: the route path is not changed.
In the case of a try-catch block with a return statement in the middleware, the location path is not changed.

This leads to a strange behavior where, if you are on the home page and click on a link that returns a 404 error and shows the error page, you cannot navigate back to the previous page using the "back" history button. This behavior differs from that of Nuxt2.
We used to show an error page on the page that really doesn't exist.
Additionally for the SSR, it works ok.
example middleware:
const fakeApiCall = (to) => {
  return new Promise((resolve, reject) => {
    if (to.path !== '/not-existing-page') {
      resolve({ data: 'ok' });
    }
    reject({ data: 'error' });
  });
};
export default defineNuxtRouteMiddleware(async (to) => {
  try {
    await fakeApiCall(to);
  } catch (err) {
    throw showError({
      statusCode: 404,
      fatal: true,
      unhandled: false,
    });
  }
});

Additional context
Similar issue was here: https://github.com/nuxt/nuxt/pull/18978
Logs
No response

I faced the same problem, because of this I have to use functions with showError. This feature is definitely is not UX friendly


Return self when controlling an operation with no controls

@dabacon I think tests exists and are in fact failing due to this change. Probably sufficient to update them to cover the changed code.


Web Content Filtering Policy Refresh seems more than 2 hours

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d6d1d825-ab12-2f37-b692-5266487ef16f
Version Independent ID: fef750ac-311b-28b4-1661-16385997815b
Content: Web content filtering - Windows security
Content Source: windows/security/threat-protection/microsoft-defender-atp/web-content-filtering.md
Product: m365-security
Technology: mde
GitHub Login: @levinec
Microsoft Alias: ellevin

I recently have enabled the web content filtering policy for some of my workstations, and have noticed its taking much more than 2 hours to get it refreshed and applied to required devices. almost a day.
I have noticed the time lag in both Microsoft Edge and Chrome, and in Chrome its even more, suspicious sites remained unblocked for more than a day.
If the policy refresh is dependent on some factors please advise on that and same can also be updated on this article's page.

@Shwet88 Thank you for providing feedback.
The issues section of this repository is intended for product documentation issues only.
Please consider opening a product support ticket by the following link below for your problem so that it gets resolved quickly.
Windows 10 Support
Thank you.


it seems there is certificate issue with this website as this doesnot work for me

it seems there is certificate issue with this website as this does not work for me, i wish you can tell me other such type of secured core api websites/endpoint/url

It should work, have you tried cors?

Ok thanks


Mat-dialog-actions not at the bottom

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Actions to be at the bottom of the dialog
What is the current behavior?
Actions right after content
What are the steps to reproduce?
Providing a StackBlitz reproduction is the best way to share your issue.
StackBlitz starter: https://stackblitz.com/edit/angular-cuikyx
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
<EMAIL_ADDRESS><EMAIL_ADDRESS>any browser and any OS

Closing as duplicate of #4609


ROS2 foxy install FAILS tries to install hirsute

In the section "And then add the repository to your sources list:" the command
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/ros-archive-keyring.gpg] http://packages.ros.org/ros2/ubuntu $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/ros2.list > /dev/null
creates a /etc/apt/sources.list.d/ros2.list file:
deb [arch=arm64 signed-by=/usr/share/keyrings/ros-archive-keyring.gpg] http://packages.ros.org/ros2/ubuntu hirsute  main
instead of foxy.  If corrected to foxy, the command
sudo apt update
gives the errors:
Ign:1 http://packages.ros.org/ros2/ubuntu foxy InRelease Err:2 http://packages.ros.org/ros2/ubuntu foxy Release   404  Not Found [IP: <IP_ADDRESS> 80] Reading package lists... Done E: The repository 'http://packages.ros.org/ros2/ubuntu foxy Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.
This was reported previously this year and attributed to an outdated key and supposedly fixed.  But it's back and seems to be new within the last week as I installed foxy ok within the last month.

The output of lsb_release -c is the codename of the Ubuntu / Debian release, not the name of the ROS 2 version.
The error is expected, as foxy is not a valid Ubuntu release codename.

The error is expected, as foxy is not a valid Ubuntu release codename.

That's exactly right.  At the end of the day, the line in /etc/apt/sources.list.d/ros2.list is saying "fetch ROS packages from this URL that target a specific Ubuntu version".  In this case, it looks like you are running on Ubuntu 21.04, which is why "hirsute" is added.
With all of that said, we don't ship Foxy pre-packaged for Ubuntu 21.04; we only ship it packaged for Ubuntu 20.04.  So this setup won't work out-of-the-box.  Your options are:

Do your development in an Ubuntu 20.04 container (this is what I do)
Build ROS 2 from source (though we don't officially target hirsute with any ROS distribution, so you may have to fix some things along the way).
Downgrade your machine to Ubuntu 20.04.

Regardless, this doesn't look like a bug, so I'm going to close this.  If you still need help with this, please ask a question on https://answers.ros.org.


whether it support z/x/y style tile map service?

This is a duplicate of https://github.com/google/earthenterprise/issues/172 and should be closed.


remove the isConnected() method from device

Remove the isConnected() method from device. We now only create a Device instance if there's a real device associated w/ it (we had previously speculatively created one for android, ios device, and ios simulator).
@yjbanov

L! G! T! M! Love seeing PR deleting code :)


Add year based layout #4

Please note, this is just a HTML + CSS mockup. Things marked with TODO:.

Took the liberty of adding a bit more readable font:


convert to esm

What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[ ] Bug fix
[ ] New feature
[x] Other, please explain:
What changes did you make? (Give an overview)

Switch from cjs to esm.
bumped lowest supported node version

Which issue (if any) does this pull request address?
standard-engine is holding back on some esm stuff...

it would offer a smoother transition to migrate to ESM only for packages like standard, ts-standard etc, before migrating this one (standard-engine). https://github.com/standard/standard-engine/issues/251#issuecomment-913229242

Is there anything you'd like reviewers to focus on?

Could we change the Node versions in the test-external and test-internal workflow to the minimum supported versions?
        node-version: [12.20.0, 14.13.1, 16.0.0]

I think that this is a better approach than testing on latest releases (e.g. 12.x) since we could otherwise accidentally use something introduced in a later patch version which would then be a breaking change to our consumers...

Could we change the Node versions in the test-external and test-internal workflow to the minimum supported versions?

fixed

ready for a 2nd wave of reviews now :)

tried helping out in ts-standard also... but oh god what i hate typescript :P
sry, but someone else needs to take on that responsibility.
i support typing but only with proper jsdoc + vanila js

tried helping out in ts-standard also... but oh god what i hate typescript :P
sry, but someone else needs to take on that responsibility.
i support typing but only with proper jsdoc + vanila js
i utilize typing with checkjs + allowjs but i don't use the typescript syntax that needs a compiler

@jimmywarting I updated https://github.com/standard/standard-engine/issues/251#issue-972660122 with the current status of the migration to ESM and I created an issue for each package that depends on standard-engine, when all engines like ts-standard etc will be migrated, we will be able to migrate standard-engine itself.
Concerning ts-standard, here's the issue: https://github.com/standard/ts-standard/issues/171
It is mainly blocked by jest.


Support for Android RISC-V

Use case
Google recently announced the android risc-v porting (article here)
and dart already has beta support for risc-v
Proposal
Support flutter on android-riscv
Related issues

https://github.com/flutter/flutter/issues/99963
https://github.com/dart-lang/sdk/issues/38587

I would love to see support RISC-V and starting with Android would probably be the best approach given Android's recently announced roadmap for support and that there is already Dart on Linux RISC-V (experimental) support.
I'd also like to chime in that even Android emulator support for RISC-V is still an unknown time away (but on roadmap) so it would also be great if there could be initial support for Flutter Linux (custom embedder not desktop) on RISC-V.
The main blocker with that though is unlike say a RPI4, the current cost-effective and widely available Allwinner D1 based boards are just too slow for on board development as I found out, so having remote development support for Flutter Linux I think would be essential to be able to do this in practical manner. Actually I think would be useful in many other embedded Flutter usecase, eg. for the flutter-pi project
Which makes me wonder how people at Toyota do this? surely they have some sort of remote debugging facility for their embedded Flutter projects, though perhaps its proprietary?

@exaby73 triage me :)

I'd also like to chime in that even Android emulator support for RISC-V is still an unknown time away (but on roadmap) so it would also be great if there could be initial support for Flutter Linux (custom embedder not desktop) on RISC-V.

you can build a minimal qemu environment --- https://github.com/google/android-riscv64/blob/main/README.md
as for speed, yeah, we're currently finding that qemu is the least worst choice (if you have a fast x86-64 machine to run it on!). we cross-compile from the x86-64 host and sync across. presumably you can do similar?

@enh-google Thanks for the pointer to Android's RISC-V doc, very useful! 👍🏻
On:

we cross-compile from the x86-64 host and sync across

could you please elaborate a touch more on that? I was under the impression that Flutter SDK currently only supports Arm Android & iOS cross compiling, ie. the "standard" way we do mobile dev with Flutter on x86-64 hosts: Flutter compiles the Dart code for the app (to ARM machinecode) on the host and then pushes that across to a mobile device to run (eg. Android Emu or real hardware). So is this actually possible already with RISC-V too?

we cross-compile from the x86-64 host and sync across

could you please elaborate a touch more on that? I was under the impression that Flutter SDK currently only supports Arm Android & iOS cross compiling, ie. the "standard" way we do mobile dev with Flutter on x86-64 hosts: Flutter compiles the Dart code for the app (to ARM machinecode) on the host and then pushes that across to a mobile device to run (eg. Android Emu or real hardware). So is this actually possible already with RISC-V too?

oh, yeah, Android doesn't have any flutter/dart code --- i just meant for c/c++ we're cross-compiling.

android sdk 34v7 has ndk 26.1.10909125 version uploaded.
https://chrome-infra-packages.appspot.com/p/flutter/android/sdk/all/linux-amd64/+/version:34v7


Do not delete coffeescript files for debugging purposes

Since sourcemaps still refer to .coffee files after build, we shouldn't be deleting those from final output directory. Debugging from devtools with latest builds is practically impossible without them.
cc @as-cii

CI has trouble retranspiling source map references to files, so I don't know if compile-cache.js needs to contain the change it currently has or if the Windows specific block should be omitted. Locally both seem work, though.

There is still trouble with getting devtools to load .coffee files from asar. It will pretty much break as soon as the person building deletes their build directory.

There is still trouble with getting devtools to load .coffee files from asar.

Yeah, to make this work we would probably need to modify Electron to make the dev tools aware of .asar files. I think that instead, we should just remove the source map URLs from the transpiled files that we ship. Eventually, we will stop using coffee-script. Though we may still use Babel to transpile our source files, the output will be pretty easy to debug compared to the output of the coffee-script compiler.

I'm not keen on losing the source maps entirely as they're pretty essential for debugging in our current Coffeescript world and even with Babel without them setting breakpoints etc. will be wrong.
One compromise might be to only include them in local dev builds and not include them in production/release versions.

One compromise might be to only include them in local dev builds and not include them in production/release versions.

I think this is the route we should take, at least until we can find a better solution (which will likely require changes in Electron as @maxbrunsfeld has mentioned).

I'm not keen on losing the source maps entirely as they're pretty essential for debugging in our current Coffeescript world

They already don't work, right? AFAIK, the only time you'd see coffee-script files are when the coffee-script has been compiled dynamically, e.g. non-bundled packages, or Atom's source code when running in dev or test mode.

Some of them do work now but not all it would seem. I need to investigate.
On Thu, Sep 22, 2016, 5:50 PM Max Brunsfeld<EMAIL_ADDRESS>wrote:

I'm not keen on losing the source maps entirely as they're pretty
essential for debugging in our current Coffeescript world
They already don't work, right? AFAIK, the only time you'd see
coffee-script files are when the coffee-script has been compiled
dynamically, e.g. non-bundled packages, or Atom's source code when
running in dev or test mode.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/pull/12713#issuecomment-248961110, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAHQp3sYxmeqWeB96FxlqRjGkr2uHphSks5qsrHCgaJpZM4J_rUV
.

I've found that commenting out the unlink of coffeescript files, one of the changes in this PR, has made debugging e.g. pane.coffee work as expected. What about adding a build arg to leave those in place for when you're building locally for dev/debug purposes? Certainly I agree it makes sense to leave them out of the released installers.

I've found that commenting out the unlink of coffeescript files, one of the changes in this PR, has made debugging e.g. pane.coffee work as expected.

It will pretty much break as soon as the person building deletes their build directory.

:+1: I just reproduced both of these behaviors and am understanding this a little better now. So in our new build scripts, coffee-script files are compiled with source maps, but the source map paths point to a temporary location in the out folder of the Atom repository, where the coffee-script files were copied to before being transpiled.
So as long as you keep those temporary files around, the coffee-script files will load correctly in the dev tools. If you remove the temporary files, or run another build (even without installing), the source maps will either stop working or will start pointing to the wrong files.
We could add a build flag to opt into this behavior, but it's a pretty fragile and hard-to-explain behavior. And seeing as how it would mostly get used during development, it seems like the existing Dev mode is a better solution to this problem.
Thoughts?

Conveniently coffee-script 1.11.0 was released two days ago, which adds support for inline source maps, which should solve problems with referencing source files from asar.

I tried coffee-script 1.11.0 and inline sourcemaps do seem to work as intended. Made appropriate changes to this PR, requires #12780 to be merged first.

@Ingramz it looks like one CompileCache test is failing:
CompileCache
  addPathToCache(filePath, atomHome)
    when the given file is coffee-script
      it compiles the file with coffee-script and caches it
        TypeError: output.replace is not a function
          at Object.exports.compile (/Users/distiller/atom/src/coffee-script.js:44:17)
          at compileFileAtPath (/Users/distiller/atom/src/compile-cache.js:77:31)
          at .<anonymous> (/Users/distiller/atom/spec/compile-cache-spec.coffee:67:24)

Could you take a look at that?

@maxbrunsfeld should be good now.

Thanks so much for investigating this @Ingramz!

@maxbrunsfeld for this to kick in, I suspect that compile-cache needs to be cleared on CI.

Great point @Ingramz. Done.


UI Esthetic, White boxes around things since I think last 2-3 updates, Windows 11

Can't repro, win11.

Never seen this behavior on macOs as well. Must be some GPU stuff

I have this only on Qubes OS (since forever), can't repro on bare linux machine

If you see this on a linux machine, you need to install/run a desktop compositor. Most desktop linux distros come with one by default, but stripped down versions like Qubes might not by default.
Don't know about Windows though, never seen that.

Can't be fixed on the Wasabi side, it's likely an issue in the user's configuration.


Add Access Control, CORS (Cross Origin Request Sharing) header methods

This should make it a little easier to get and set access control headers as it ensures the types and naming is correct. It is also intentionally very minimal like the other header accessors.
closes #131

Similar to the CSP implementation, I'm wondering if we should have a single access_control property that returns an AccessControl object instead. Or maybe we need some sort of equivalent to EtagMixin.make_conditional that adjusts the response based on the request, since that's where the complexity lies.
I checked out Flask-CORS, somewhat discouraging to see that they're using str.split instead of the Werkzeug header parsing utilities already. While I'm fine with adding the header properties, I'm not sure how useful on its own that will be.

I went for a single access_control property and object in Quart, however I don't think it is the right decision as it isn't consistent with how I think Werkzeug works (headers are only combined within a wrapper object, including CSP which is a single header) and the AccessControl instance itself isn't very useful on its own (Quart usage is always [wrapper].access_control.[header]).
The correct header parsing and setting is in itself useful (in my view). Whilst I like something like make_cors, I don't think it fits with Werkzeug. I think make_conditional is possible using the information in the wrappers alone whereas cors needs some application decisions/inputs.


[Android] Fix the mismatch issue.

In newer crosswalk, the parameter nums for loadXWalkLibrary() is
increased, this leads to older crosswalk can not invoke the right
function to load library in shared mode.
Keep the single parameter function to preserve backward compatibility.
Related to XWALK-5796

@axinging @fujunwei @wuhengzhi @xzhan96 @XiaosongWei PTAL, thanks.

This bug leads to major issues on the store. We should have a test.

Maybe we need a approach to make API compatibility

LGTM
@fujunwei  Agree. We should run compatibility test.

LGTM
For "compatibility test", I think when upgrade a API, please keep the old API and also keep the old test cases instead of changing them.

@wuhengzhi Please also cherry pick this patch to Crosswalk-16

And please add tests that are run part of the test suite. Thanks.

@darktears Yes, I am considering how to add test case. Thanks.


Add R doc-site link to Python doc-site and vice versa

In the interim of spinning up Quarto, please add links to each doc-site pointing to the other one

[x] Add link in R doc-site pointing to Python doc-site.
[x] Add link in Python doc-site pointing to R doc-site.

Done


Move __CFAllocatorRespectsHintZeroWhenAllocating

Move __CFAllocatorRespectsHintZeroWhenAllocating to a CF-internal header to avoid confusion over its linkage. Resolves #5125

@swift-ci test

LGTM :)


"import" is a reserved word in Java

All AWS constructs have a static import method to allow bringing-in resources defined externally. However, import is reserved in Java (and possibly in other languages).
In the interim the jsii compiler will simply add an _ at the end of the method name, but we need to find a new name for the method and rename across the codebase.

That's something we should probably do before 1.0

Superseded by #2273


Add some telemetry for feature usage in datascience

For #7908

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[x] Title summarizes what is changing
[x] Has a news entry file (remember to thank yourself!)
[n/a] Appropriate comments and documentation strings in the code
[n/a] Has sufficient logging.
[x] Has telemetry for enhancements.
[n/a] Unit tests & system/integration tests are added/updated
[n/a] Test plan is updated as appropriate
[n/a] package-lock.json has been regenerated by running npm install (if dependencies have changed)
[n/a] The wiki is updated with any design decisions/details.

Codecov Report

Merging #7914 into master will decrease coverage by 0.34%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #7914      +/-   ##
==========================================
- Coverage   58.94%   58.59%   -0.35%
==========================================
  Files         498      498
  Lines       22299    21944     -355
  Branches     3576     3576
==========================================
- Hits        13144    12858     -286
+ Misses       8333     8264      -69
  Partials      822      822

Impacted Files
Coverage Δ

src/client/telemetry/index.ts
86.13% <ø> (ø)
:arrow_up:

src/client/datascience/constants.ts
100% <100%> (ø)
:arrow_up:

...ience/interactive-common/interactiveWindowTypes.ts
100% <100%> (ø)
:arrow_up:

...nt/datascience/jupyter/invalidNotebookFileError.ts
0% <0%> (-75%)
:arrow_down:

.../client/datascience/jupyter/jupyterConnectError.ts
0% <0%> (-66.67%)
:arrow_down:

...science/jupyter/jupyterKernelPromiseFailedError.ts
0% <0%> (-50%)
:arrow_down:

...ent/datascience/jupyter/jupyterWaitForIdleError.ts
0% <0%> (-50%)
:arrow_down:

src/client/language/characters.ts
12% <0%> (-18.77%)
:arrow_down:

src/client/constants.ts
75% <0%> (-5%)
:arrow_down:

src/client/datascience/cellFactory.ts
72.34% <0%> (-3.53%)
:arrow_down:

... and 28 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b6ce843...c03d86c. Read the comment docs.