Homebrew installation fails with git errors

brew config output
HOMEBREW_VERSION: 3.2.5-19-gbdc3391
ORIGIN: https://github.com/Homebrew/brew
HEAD: bdc3391a1319f1c40a108d14a077ca0964b33a3f
Last commit: 2 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: (none)
Core tap last commit: never
Core tap branch: HEAD
HOMEBREW_PREFIX: /usr/local
HOMEBREW_AUTO_UPDATE_SECS: 86400
HOMEBREW_CASK_OPTS: ["--no-quarantine"]
HOMEBREW_MAKE_JOBS: 4
HOMEBREW_NO_EMOJI: set
Homebrew Ruby: 2.6.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3_2/bin/ruby
CPU: quad-core 64-bit kabylake
Clang: 12.0.0 build 1200
Git: 2.24.3 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 10.15.7-x86_64
CLT: <IP_ADDRESS>.1.1610135815
Xcode: N/A

brew doctor output
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Homebrew/homebrew-core was not tapped properly! Run:
  rm -rf "/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core"
  brew tap homebrew/core

Warning: Some taps are not on the default git origin branch and may not receive
updates. If this is a surprise to you, check out the default branch with:
  git -C $(brew --repo homebrew/core) checkout

[X] I ran brew update and am still able to reproduce my issue.
[x] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
Install homebrew with the command mentioned in https://docs.brew.sh/Installation#git-remote-mirroring
What happened (include all command output)?
barna@barnas-MacBook-Pro defaults %     /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"

==> Checking for `sudo` access (which may request your password).
Password:
==> This script will install:
/usr/local/bin/brew
/usr/local/share/doc/homebrew
/usr/local/share/man/man1/brew.1
/usr/local/share/zsh/site-functions/_brew
/usr/local/etc/bash_completion.d/brew
/usr/local/Homebrew
==> The following new directories will be created:
/usr/local/bin
/usr/local/etc
/usr/local/include
/usr/local/lib
/usr/local/sbin
/usr/local/share
/usr/local/var
/usr/local/opt
/usr/local/share/zsh
/usr/local/share/zsh/site-functions
/usr/local/var/homebrew
/usr/local/var/homebrew/linked
/usr/local/Cellar
/usr/local/Caskroom
/usr/local/Frameworks
==> The Xcode Command Line Tools will be installed.

Press RETURN to continue or any other key to abort
==> /usr/bin/sudo /bin/mkdir -p /usr/local/bin /usr/local/etc /usr/local/include /usr/local/lib /usr/local/sbin /usr/local/share /usr/local/var /usr/local/opt /usr/local/share/zsh /usr/local/share/zsh/site-functions /usr/local/var/homebrew /usr/local/var/homebrew/linked /usr/local/Cellar /usr/local/Caskroom /usr/local/Frameworks
==> /usr/bin/sudo /bin/chmod u=rwx,g=rwx /usr/local/bin /usr/local/etc /usr/local/include /usr/local/lib /usr/local/sbin /usr/local/share /usr/local/var /usr/local/opt /usr/local/share/zsh /usr/local/share/zsh/site-functions /usr/local/var/homebrew /usr/local/var/homebrew/linked /usr/local/Cellar /usr/local/Caskroom /usr/local/Frameworks
==> /usr/bin/sudo /bin/chmod g-w,o-w /usr/local/share/zsh /usr/local/share/zsh/site-functions
==> /usr/bin/sudo /usr/sbin/chown barna /usr/local/bin /usr/local/etc /usr/local/include /usr/local/lib /usr/local/sbin /usr/local/share /usr/local/var /usr/local/opt /usr/local/share/zsh /usr/local/share/zsh/site-functions /usr/local/var/homebrew /usr/local/var/homebrew/linked /usr/local/Cellar /usr/local/Caskroom /usr/local/Frameworks
==> /usr/bin/sudo /usr/bin/chgrp admin /usr/local/bin /usr/local/etc /usr/local/include /usr/local/lib /usr/local/sbin /usr/local/share /usr/local/var /usr/local/opt /usr/local/share/zsh /usr/local/share/zsh/site-functions /usr/local/var/homebrew /usr/local/var/homebrew/linked /usr/local/Cellar /usr/local/Caskroom /usr/local/Frameworks
==> /usr/bin/sudo /bin/mkdir -p /usr/local/Homebrew
==> /usr/bin/sudo /usr/sbin/chown -R barna:admin /usr/local/Homebrew
==> /usr/bin/sudo /bin/mkdir -p /Users/barna/Library/Caches/Homebrew
==> /usr/bin/sudo /bin/chmod g+rwx /Users/barna/Library/Caches/Homebrew
==> /usr/bin/sudo /usr/sbin/chown -R barna /Users/barna/Library/Caches/Homebrew
==> Searching online for the Command Line Tools
==> /usr/bin/sudo /usr/bin/touch /tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress
==> Installing Command Line Tools for Xcode-12.4
==> /usr/bin/sudo /usr/sbin/softwareupdate -i Command\ Line\ Tools\ for\ Xcode-12.4
Software Update Tool

Downloading Command Line Tools for Xcode
Downloaded Command Line Tools for Xcode
Installing Command Line Tools for Xcode
Done with Command Line Tools for Xcode
Done.
==> /usr/bin/sudo /bin/rm -f /tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress
==> /usr/bin/sudo /usr/bin/xcode-select --switch /Library/Developer/CommandLineTools
==> Downloading and installing Homebrew...
remote: Enumerating objects: 188227, done.
remote: Counting objects: 100% (71/71), done.
remote: Compressing objects: 100% (66/66), done.
remote: Total 188227 (delta 9), reused 63 (delta 4), pack-reused 188156
Receiving objects: 100% (188227/188227), 51.07 MiB | 16.83 MiB/s, done.
Resolving deltas: 100% (139524/139524), done.
From https://github.com/Homebrew/brew
 * [new branch]      automerge-linux                                     -> origin/automerge-linux
 * [new branch]      dependabot/bundler/Library/Homebrew/sorbet-0.5.6519 -> origin/dependabot/bundler/Library/Homebrew/sorbet-0.5.6519
 * [new branch]      master                                              -> origin/master
 * [new tag]             0.1                                                 -> 0.1
 * [new tag]             0.2                                                 -> 0.2
 * [new tag]             0.3                                                 -> 0.3
 * [new tag]             0.4                                                 -> 0.4
 * [new tag]             0.5                                                 -> 0.5
 * [new tag]             0.6                                                 -> 0.6
 * [new tag]             0.7                                                 -> 0.7
 * [new tag]             0.7.1                                               -> 0.7.1
 * [new tag]             0.8                                                 -> 0.8
 * [new tag]             0.8.1                                               -> 0.8.1
 * [new tag]             0.9                                                 -> 0.9
 * [new tag]             0.9.1                                               -> 0.9.1
 * [new tag]             0.9.2                                               -> 0.9.2
 * [new tag]             0.9.3                                               -> 0.9.3
 * [new tag]             0.9.4                                               -> 0.9.4
 * [new tag]             0.9.5                                               -> 0.9.5
 * [new tag]             0.9.8                                               -> 0.9.8
 * [new tag]             0.9.9                                               -> 0.9.9
 * [new tag]             1.0.0                                               -> 1.0.0
 * [new tag]             1.0.1                                               -> 1.0.1
 * [new tag]             1.0.2                                               -> 1.0.2
 * [new tag]             1.0.3                                               -> 1.0.3
 * [new tag]             1.0.4                                               -> 1.0.4
 * [new tag]             1.0.5                                               -> 1.0.5
 * [new tag]             1.0.6                                               -> 1.0.6
 * [new tag]             1.0.7                                               -> 1.0.7
 * [new tag]             1.0.8                                               -> 1.0.8
 * [new tag]             1.0.9                                               -> 1.0.9
 * [new tag]             1.1.0                                               -> 1.1.0
 * [new tag]             1.1.1                                               -> 1.1.1
 * [new tag]             1.1.10                                              -> 1.1.10
 * [new tag]             1.1.11                                              -> 1.1.11
 * [new tag]             1.1.12                                              -> 1.1.12
 * [new tag]             1.1.13                                              -> 1.1.13
 * [new tag]             1.1.2                                               -> 1.1.2
 * [new tag]             1.1.3                                               -> 1.1.3
 * [new tag]             1.1.4                                               -> 1.1.4
 * [new tag]             1.1.5                                               -> 1.1.5
 * [new tag]             1.1.6                                               -> 1.1.6
 * [new tag]             1.1.7                                               -> 1.1.7
 * [new tag]             1.1.8                                               -> 1.1.8
 * [new tag]             1.1.9                                               -> 1.1.9
 * [new tag]             1.2.0                                               -> 1.2.0
 * [new tag]             1.2.1                                               -> 1.2.1
 * [new tag]             1.2.2                                               -> 1.2.2
 * [new tag]             1.2.3                                               -> 1.2.3
 * [new tag]             1.2.4                                               -> 1.2.4
 * [new tag]             1.2.5                                               -> 1.2.5
 * [new tag]             1.2.6                                               -> 1.2.6
 * [new tag]             1.3.0                                               -> 1.3.0
 * [new tag]             1.3.1                                               -> 1.3.1
 * [new tag]             1.3.2                                               -> 1.3.2
 * [new tag]             1.3.3                                               -> 1.3.3
 * [new tag]             1.3.4                                               -> 1.3.4
 * [new tag]             1.3.5                                               -> 1.3.5
 * [new tag]             1.3.6                                               -> 1.3.6
 * [new tag]             1.3.7                                               -> 1.3.7
 * [new tag]             1.3.8                                               -> 1.3.8
 * [new tag]             1.3.9                                               -> 1.3.9
 * [new tag]             1.4.0                                               -> 1.4.0
 * [new tag]             1.4.1                                               -> 1.4.1
 * [new tag]             1.4.2                                               -> 1.4.2
 * [new tag]             1.4.3                                               -> 1.4.3
 * [new tag]             1.5.0                                               -> 1.5.0
 * [new tag]             1.5.1                                               -> 1.5.1
 * [new tag]             1.5.10                                              -> 1.5.10
 * [new tag]             1.5.11                                              -> 1.5.11
 * [new tag]             1.5.12                                              -> 1.5.12
 * [new tag]             1.5.13                                              -> 1.5.13
 * [new tag]             1.5.14                                              -> 1.5.14
 * [new tag]             1.5.2                                               -> 1.5.2
 * [new tag]             1.5.3                                               -> 1.5.3
 * [new tag]             1.5.4                                               -> 1.5.4
 * [new tag]             1.5.5                                               -> 1.5.5
 * [new tag]             1.5.6                                               -> 1.5.6
 * [new tag]             1.5.7                                               -> 1.5.7
 * [new tag]             1.5.8                                               -> 1.5.8
 * [new tag]             1.5.9                                               -> 1.5.9
 * [new tag]             1.6.0                                               -> 1.6.0
 * [new tag]             1.6.1                                               -> 1.6.1
 * [new tag]             1.6.10                                              -> 1.6.10
 * [new tag]             1.6.11                                              -> 1.6.11
 * [new tag]             1.6.12                                              -> 1.6.12
 * [new tag]             1.6.13                                              -> 1.6.13
 * [new tag]             1.6.14                                              -> 1.6.14
 * [new tag]             1.6.15                                              -> 1.6.15
 * [new tag]             1.6.16                                              -> 1.6.16
 * [new tag]             1.6.17                                              -> 1.6.17
 * [new tag]             1.6.2                                               -> 1.6.2
 * [new tag]             1.6.3                                               -> 1.6.3
 * [new tag]             1.6.4                                               -> 1.6.4
 * [new tag]             1.6.5                                               -> 1.6.5
 * [new tag]             1.6.6                                               -> 1.6.6
 * [new tag]             1.6.7                                               -> 1.6.7
 * [new tag]             1.6.8                                               -> 1.6.8
 * [new tag]             1.6.9                                               -> 1.6.9
 * [new tag]             1.7.0                                               -> 1.7.0
 * [new tag]             1.7.1                                               -> 1.7.1
 * [new tag]             1.7.2                                               -> 1.7.2
 * [new tag]             1.7.3                                               -> 1.7.3
 * [new tag]             1.7.4                                               -> 1.7.4
 * [new tag]             1.7.5                                               -> 1.7.5
 * [new tag]             1.7.6                                               -> 1.7.6
 * [new tag]             1.7.7                                               -> 1.7.7
 * [new tag]             1.8.0                                               -> 1.8.0
 * [new tag]             1.8.1                                               -> 1.8.1
 * [new tag]             1.8.2                                               -> 1.8.2
 * [new tag]             1.8.3                                               -> 1.8.3
 * [new tag]             1.8.4                                               -> 1.8.4
 * [new tag]             1.8.5                                               -> 1.8.5
 * [new tag]             1.8.6                                               -> 1.8.6
 * [new tag]             1.9.0                                               -> 1.9.0
 * [new tag]             1.9.1                                               -> 1.9.1
 * [new tag]             1.9.2                                               -> 1.9.2
 * [new tag]             1.9.3                                               -> 1.9.3
 * [new tag]             2.0.0                                               -> 2.0.0
 * [new tag]             2.0.1                                               -> 2.0.1
 * [new tag]             2.0.2                                               -> 2.0.2
 * [new tag]             2.0.3                                               -> 2.0.3
 * [new tag]             2.0.4                                               -> 2.0.4
 * [new tag]             2.0.5                                               -> 2.0.5
 * [new tag]             2.0.6                                               -> 2.0.6
 * [new tag]             2.1.0                                               -> 2.1.0
 * [new tag]             2.1.1                                               -> 2.1.1
 * [new tag]             2.1.10                                              -> 2.1.10
 * [new tag]             2.1.11                                              -> 2.1.11
 * [new tag]             2.1.12                                              -> 2.1.12
 * [new tag]             2.1.13                                              -> 2.1.13
 * [new tag]             2.1.14                                              -> 2.1.14
 * [new tag]             2.1.15                                              -> 2.1.15
 * [new tag]             2.1.16                                              -> 2.1.16
 * [new tag]             2.1.2                                               -> 2.1.2
 * [new tag]             2.1.3                                               -> 2.1.3
 * [new tag]             2.1.4                                               -> 2.1.4
 * [new tag]             2.1.5                                               -> 2.1.5
 * [new tag]             2.1.6                                               -> 2.1.6
 * [new tag]             2.1.7                                               -> 2.1.7
 * [new tag]             2.1.8                                               -> 2.1.8
 * [new tag]             2.1.9                                               -> 2.1.9
 * [new tag]             2.2.0                                               -> 2.2.0
 * [new tag]             2.2.1                                               -> 2.2.1
 * [new tag]             2.2.10                                              -> 2.2.10
 * [new tag]             2.2.11                                              -> 2.2.11
 * [new tag]             2.2.12                                              -> 2.2.12
 * [new tag]             2.2.13                                              -> 2.2.13
 * [new tag]             2.2.14                                              -> 2.2.14
 * [new tag]             2.2.15                                              -> 2.2.15
 * [new tag]             2.2.16                                              -> 2.2.16
 * [new tag]             2.2.17                                              -> 2.2.17
 * [new tag]             2.2.2                                               -> 2.2.2
 * [new tag]             2.2.3                                               -> 2.2.3
 * [new tag]             2.2.4                                               -> 2.2.4
 * [new tag]             2.2.5                                               -> 2.2.5
 * [new tag]             2.2.6                                               -> 2.2.6
 * [new tag]             2.2.7                                               -> 2.2.7
 * [new tag]             2.2.8                                               -> 2.2.8
 * [new tag]             2.2.9                                               -> 2.2.9
 * [new tag]             2.3.0                                               -> 2.3.0
 * [new tag]             2.4.0                                               -> 2.4.0
 * [new tag]             2.4.1                                               -> 2.4.1
 * [new tag]             2.4.10                                              -> 2.4.10
 * [new tag]             2.4.11                                              -> 2.4.11
 * [new tag]             2.4.12                                              -> 2.4.12
 * [new tag]             2.4.13                                              -> 2.4.13
 * [new tag]             2.4.14                                              -> 2.4.14
 * [new tag]             2.4.15                                              -> 2.4.15
 * [new tag]             2.4.16                                              -> 2.4.16
 * [new tag]             2.4.2                                               -> 2.4.2
 * [new tag]             2.4.3                                               -> 2.4.3
 * [new tag]             2.4.4                                               -> 2.4.4
 * [new tag]             2.4.5                                               -> 2.4.5
 * [new tag]             2.4.6                                               -> 2.4.6
 * [new tag]             2.4.7                                               -> 2.4.7
 * [new tag]             2.4.8                                               -> 2.4.8
 * [new tag]             2.4.9                                               -> 2.4.9
 * [new tag]             2.5.0                                               -> 2.5.0
 * [new tag]             2.5.1                                               -> 2.5.1
 * [new tag]             2.5.10                                              -> 2.5.10
 * [new tag]             2.5.11                                              -> 2.5.11
 * [new tag]             2.5.12                                              -> 2.5.12
 * [new tag]             2.5.2                                               -> 2.5.2
 * [new tag]             2.5.3                                               -> 2.5.3
 * [new tag]             2.5.4                                               -> 2.5.4
 * [new tag]             2.5.5                                               -> 2.5.5
 * [new tag]             2.5.6                                               -> 2.5.6
 * [new tag]             2.5.7                                               -> 2.5.7
 * [new tag]             2.5.8                                               -> 2.5.8
 * [new tag]             2.5.9                                               -> 2.5.9
 * [new tag]             2.6.0                                               -> 2.6.0
 * [new tag]             2.6.1                                               -> 2.6.1
 * [new tag]             2.6.2                                               -> 2.6.2
 * [new tag]             2.7.0                                               -> 2.7.0
 * [new tag]             2.7.1                                               -> 2.7.1
 * [new tag]             2.7.2                                               -> 2.7.2
 * [new tag]             2.7.3                                               -> 2.7.3
 * [new tag]             2.7.4                                               -> 2.7.4
 * [new tag]             2.7.5                                               -> 2.7.5
 * [new tag]             2.7.6                                               -> 2.7.6
 * [new tag]             2.7.7                                               -> 2.7.7
 * [new tag]             3.0.0                                               -> 3.0.0
 * [new tag]             3.0.1                                               -> 3.0.1
 * [new tag]             3.0.10                                              -> 3.0.10
 * [new tag]             3.0.11                                              -> 3.0.11
 * [new tag]             3.0.2                                               -> 3.0.2
 * [new tag]             3.0.3                                               -> 3.0.3
 * [new tag]             3.0.4                                               -> 3.0.4
 * [new tag]             3.0.5                                               -> 3.0.5
 * [new tag]             3.0.6                                               -> 3.0.6
 * [new tag]             3.0.7                                               -> 3.0.7
 * [new tag]             3.0.8                                               -> 3.0.8
 * [new tag]             3.0.9                                               -> 3.0.9
 * [new tag]             3.1.0                                               -> 3.1.0
 * [new tag]             3.1.1                                               -> 3.1.1
 * [new tag]             3.1.10                                              -> 3.1.10
 * [new tag]             3.1.11                                              -> 3.1.11
 * [new tag]             3.1.12                                              -> 3.1.12
 * [new tag]             3.1.2                                               -> 3.1.2
 * [new tag]             3.1.3                                               -> 3.1.3
 * [new tag]             3.1.4                                               -> 3.1.4
 * [new tag]             3.1.5                                               -> 3.1.5
 * [new tag]             3.1.6                                               -> 3.1.6
 * [new tag]             3.1.7                                               -> 3.1.7
 * [new tag]             3.1.8                                               -> 3.1.8
 * [new tag]             3.1.9                                               -> 3.1.9
 * [new tag]             3.2.0                                               -> 3.2.0
 * [new tag]             3.2.1                                               -> 3.2.1
 * [new tag]             3.2.2                                               -> 3.2.2
 * [new tag]             3.2.3                                               -> 3.2.3
 * [new tag]             3.2.4                                               -> 3.2.4
 * [new tag]             3.2.5                                               -> 3.2.5
HEAD is now at bdc3391a1 Merge pull request #11793 from Homebrew/revert-11781-remove_homebrew_bottle_domain
==> Tapping homebrew/core
remote: Enumerating objects: 1012208, done.
remote: Counting objects: 100% (15985/15985), done.
remote: Compressing objects: 100% (1278/1278), done.
remote: Total 1012208 (delta 15180), reused 15203 (delta 14707), pack-reused 996223
Receiving objects: 100% (1012208/1012208), 412.08 MiB | 17.50 MiB/s, done.
Resolving deltas: 100% (691684/691684), done.
fatal: bad tree object bd4e945733d4fe6c4f837fb2ddcfc0eb76cd4522
error: https://github.com/Homebrew/homebrew-core did not send all necessary objects

Failed during: git fetch --force origin refs/heads/master:refs/remotes/origin/master
barna@barnas-MacBook-Pro defaults % /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"

==> Checking for `sudo` access (which may request your password).
Password:
==> This script will install:
/usr/local/bin/brew
/usr/local/share/doc/homebrew
/usr/local/share/man/man1/brew.1
/usr/local/share/zsh/site-functions/_brew
/usr/local/etc/bash_completion.d/brew
/usr/local/Homebrew

Press RETURN to continue or any other key to abort
==> /usr/bin/sudo /usr/sbin/chown -R barna:admin /usr/local/Homebrew
==> Downloading and installing Homebrew...
Updating files: 100% (2679/2679), done.
HEAD is now at bdc3391a1 Merge pull request #11793 from Homebrew/revert-11781-remove_homebrew_bottle_domain
error: Not a valid ref: refs/remotes/origin/master
fatal: ambiguous argument 'refs/remotes/origin/master': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Failed during: /usr/local/bin/brew update --force --quiet

What did you expect to happen?
homebrew is installed without an error.
Step-by-step reproduction instructions (by running brew commands)
Run `/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"`, try again a 2nd time.

Running the suggested steps from `brew doctor` seem to have fixed the brew installation, but it would be nice if it worked without those additional steps (I tried not to check the "I have resolved all warnings from brew doctor and that did not fix my problem." point, but then I couldn't send the report).

This is a network issue on your end, and not a bug in brew. Those steps aren't needed when your network is functioning properly, so there's nothing here for us to fix, unfortunately.


merge package from arlac77/npm-package-template

package.json

chore(devDependencies): update nyc:^11.7.2 from template
chore(devDependencies): add rollup-plugin-commonjs:^9.1.3 from template
chore(devDependencies): add rollup-plugin-node-resolve:^3.3.0 from template
chore(devDependencies): add rollup-plugin-babel:^3.0.4 from template
chore(devDependencies): add rollup-plugin-executable:^1.2.0 from template
chore(devDependencies): add babel-preset-env:^1.6.1 from template

.travis.yml

chore(travis): remove node versions 10
chore(travis): add node versions 10.1

:tada: This PR is included in version 2.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Menu of articles works only when user clicks on the name

As you can see with the GIF, when the user clicks beside the menu option the action is not triggered and the page does not move to the selected section.

Thanks! My bad!

The issue was closed but the PR #25 is not merged.

My bad. Sorry for late. I just changed my job . Will return back to China for my new job (For android/ios). So quite busy for the moment to prepare leave a country to another :D


Update due to simple form vuln

Oops, merged this by accident! @jamesjefferies

@jamesalmond that's ok - we need this to stop the builds failing!


Add deployment feedback

I also just need a PR that will exercise the new deployment target :)

Closing in favor of #50


Move Hashbrown to be optional

Description
Moves Hashbrown as optional dependency to allow compiling on systems without atomics. Long story short - unfortunately just making Hashbrown's ahash optional on the workspace will not solve everything as it removes HashMap::new() too, that is used in few places. Here is a variant that moves multivariate commits under feature flag, that were the only part that depends on the Hashbrown. At the moment benchmarks in poly part are broken as they depend on multivariate part. I believe it's possible to fix one way or another, just need to know which one.
Another option would be to try to make hash use explicit (and not use ahash), will be posted in alternative PR
Fixes #812

[x] Targeted PR against correct branch (master)
[x] Linked to GitHub issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[ ] Wrote unit tests
[ ] Updated relevant documentation in the code
[ ] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[ ] Re-reviewed Files changed in the GitHub PR explorer

closed by the alternative solution in https://github.com/arkworks-rs/algebra/pull/825


Add rosdep python rules for defer, kombu, and sortedcontainers

@dirk-thomas sorry about that, didn't realize. I have updated the PR.


CLIMATE-508: added a class 'Downscaling' and histogram plots

Hey @huikyole I was looking into the open issues and I saw this one and I have to agree with @MJJoyce  that example code would be great.  Even a simple example of how the API you defined in the class would be called.
From what I see in the code I "think" it would be something like the following:
the basic way a user would import the Class

from ocw.statistical_downscaling import Downscaling

simple class instantiation

my_downscaler = Downscaling(ref, present, future)

Then we use the defined downscaler to return values

downscaled_present, modeled_future = my_downscaler.Delta_addition()

Am I even close here?  Perhaps a unittest would also help convey how the code would be used.
I am not sure I know enough about Downscaling, but all the return documentation is the same:
:returns: downscaled model_present and model_future

@MJJoyce @cgoodale  @huikyole  @chrismattmann  This is great functionality to have in the code base which been demonstrated to work. It has been outstanding here for quite sometime. As for the most part it is an additional file and a couple updates the plotter class. Would anyone be adverse to merging this code as is, then dev-ing out the outstanding issues in separate issue tickets?

Would have been nice if the requests/questions had been answered, or even just acknowledged in some way, before merging. But if you want to take on the responsibility of cleaning it up and documenting it properly in the code you won't hear much complaining from me! :+1:

I have been waiting for #111 to be merged before working on #112.

Is there some dependency here @huikyole? It doesn't look like it to me, but perhaps I'm overlooking it. Or was there some other reason to wait to address this before looking into the other one? The integration of this one would be way less work since the other breaks the build where as this one doesn't touch anything old in the codebase.

@MJJoyce, there is dependency. Current OCW time parsing module could not properly handle my test data (CMIP5 model output). Once #111 is merged, I will refactor this one and provide an example.

Alrighty. No reason to hold merging this then if it's just the example data not in this PR that wouldn't load. +1 again from me @kwhitehall. Easy enough to integrate the example(s) that @huikyole has later once we fix up and merge #111

@huikyole I looked through this code, but I don't see the dependency to  #111 that you refer.
If it is a dependency that is wrapped up in an example, then I would suggest the following:
(1) we can go ahead and merge this (PR#112) as is.
(2) given the nature of  #111 I wonder if you couldn't leverage the existing function in utils.py called calc_climatology_season to achieve the functionality you desire.
(3) provide an example for how to use this current functionality.

Resolve CLIMATE-508. Merged PR#112.

@huikyole Please close this PR.

I still wonder why we prioritize the changes in #112 over major bug in the time decoding and seasonal average. Some critical bugs in calc_climatology_season in utils.py were discussed and resolved two years ago in one of the subversion hosted on a JPL server. Why does every dataset need to have time dimension whose length is a multiple of 12 to calculate its seasonal average?

That sounds like a question for the relevant pull request @huikyole. I would move that discussion over there and close this pull request since it's been merged.
Thanks much

Everyone it's closed by commiting something saying this closes #112 anyone can close it on the PMC

Ack @chrismattmann. Looks like there was a typo in the merge commit that caused it to not close.

Ack @chrismattmann  and @MJJoyce. Thanks for the advice, still learning!

NP @kwhitehall. We can just include a reference to this in a future merge commit if @huikyole doesn't beat us to closing it. Easy peasy.

Yep no worries I just call them tickle commits change spacing on s text file then add commit msg all good!


Default output to file does not have newline.

All the output is on a single line.

Good catch. Fixed with 1c93eabe58eae71158a9f3627e3ef6ae676d7039


Fixing cqlgen obfuscator filters mapping logic

Related issue

Should there be additional unit tests added here: nb-adapters/adapter-cqld4/src/test/java/io/nosqlbench?


Update instagram login page

Update instagram login page    (#1)

Putted images in a folder
Added meta viewport
Changed footer links color
Changed footer name links to be equal to the website

I came from hacktoberfest :)

Hello @tiagobpires, thanks for your contribution.

Just forgot about the label. Added :)


Updates for hero section

Updates for Hero Section
Content Requirements

Heading: "Start Building Habits."
Text Body: Lorem ipsum text placeholder
Download new hero image for hero section

Questions/suggestions for Design Team

What will be the marketing text?

Added updates to hero section


what error is this

Error at process_tags() at page 4: (<class 'TypeError'>, TypeError('the JSON object must be str, bytes or bytearray, not NoneType'), <traceback object at 0x040DE168>)
Dumping html to: Error page for search tags %E3%83%AD%E3%83%AA at page 4.html
Unknown Error, please check the log file: (<class 'TypeError'>, TypeError('the JSON object must be str, bytes or bytearray, not NoneType'), <traceback object at 0x00D84F08>)
Please answer in easy words so that Google Translator can translate it into Korean

We lack some context to understand the source of the error.
Can you add to your comment the log file pixivutil.log to try to find the origin of your error?
This log file should be in the same place as the script files.

pixivutil.log
Is this enough?

I was able to reproduce your error.
The problem you have seems to be related to an update from Pixiv on their query quotas.
The time needed between two requests was increased a few weeks ago by Pixiv. Also, when searching for an image by tag (which you did), there is no waiting time between two requests.
This led to the error you had because you probably received a 429 error (Too many request) from Pixiv even if it doesn't appear in the logs.

Ok Yuki fixed it with its last commit, it should be fine 👍


I'm not good with coding and I dont recognize this as easily fixable unless I'm just retarded so can someone help

So whenever I click compile it starts going for a second then just stops and says this ///

And I'm kind of an idiot so I'm not sure what any of it means or how to fix and I'm hoping its something as simple as I just forgot to do a step in the preparation, anyways someone please help !!

just wait for about 1 min or two dont delete any files

Hey, just use the ModdedPysilon version, it covers every bug and it make sure your discord account never get banned.
Leave me a star if you like my project ;)


Publish to npm

You've got a great component here. :)  It deserves to be published so people find it easier, and have an easier install path.  Go for it!

It's already published on npm but with a namespace. Currently npm doesn't show search results from namespaced modules, that's why you don't find it. They say they will show these too...eventually. Until then I agree, it's less discoverable than it could be but I don't think renaming to react-popover-the-sixth is that much better.
How did you find it?

Just a google search.  I've looked over some other implementations and in general I like yours a lot.  Much better than the one published as react-popover.  What about a rename to react-pop?

Neah, I am ok waiting till npm manages to make namespaces searchable. Meanwhile word of mouth and google should do ;)


Template X sixcols design regression fix

carousel.js refactor ended up introducing a small regression on template x 'sixcols' design max-width, making it look more like 'fourcols' rather than 'sixcols'. This PR will fix it.
Resolves: MWPW-136432
Test URLs:

Before: https://main--express--adobecom.hlx.page/express/create/logo?martech=off
After: https://template-x-sixcols-fix--express--adobecom.hlx.page/express/create/logo?martech=off

Codecov Report

Merging #450 (6d9a2ac) into stage (04bdf9f) will decrease coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##            stage     #450      +/-   ##
==========================================
- Coverage   30.02%   29.96%   -0.07%
==========================================
  Files         124      124
  Lines       23740    23740
==========================================
- Hits         7129     7113      -16
- Misses      16611    16627      +16

see 1 file with indirect coverage changes
:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!


Notifications

fixes #7
Pops a notification whenever someone @mentions you.

Sweet, this'll be a nice feature. Some thoughts:

Thoughts about requesting notification permission on the chat loading? Maybe there could be a banner at the top of the chat (20-50px ish, full width) - "Would you like to enable notifications? [Yes] [No]"Sweet, this'll be a nice feature. Some thoughts:

Thoughts about requesting notification permission on the chat loading? Maybe there could be a banner at the top of the chat (20-50px ish, full width) - "Would you like to enable notifications? [Yes] [No]" - the result should be stored in localStorage, so the user isn't repeatedly asked

Users should be able to disable notifications all together, as above, and...

It would also be good to provide a command to enable/disable notifications, like /notifications on or /notification off. Again, should go in localStorage so that the preference is "remembered". Eventually I want a settings UI, but that would basically apply to all / commands, and I have plans to integrate this in the new UI design we'll be using when going to Vue

Something else I wanted for #7 was the option for notifications on all messages. The "yes" button on the banner could "drop down" to something like:

--------------------------
... [      Yes    ]    (Banner)
--------------------------
(5-10px margin)
    [      All     ]
(5-10px margin)
    [@mentions only]

And the command could be full and mentions instead of just on

This PR actually works to implement #17 as well as #7. One other piece of that I wasn't explicit about is that the @mention text should be highlighted, similar to how it is in comments on the rest of the Eterna site - might also be a good idea to highlight the entire message kinda like Discord does to make it stand out.
I see you use NICK to generate the mention - in general most users only see the USERNAME. I'd suggest using that. Which would be helped by...
Implementing #18, so you don't need to type any special characters, and
Implementing the other part of #17, custom notification phrases (which should have the same effect as @mentions, i.e. The highlighting) - again, there should be / commands to add/remove keywords to be highlighted (again, in localStorage). Also, as before, this will eventually go in a settings UI

As a note - your original PR is fine, this is all "hey, while you're at it, could you go implement this stuff too?" I just feel that it would make sense to release this all as one package, to provide the best experience to users (configuration, usability, etc).
If you want, I could create a new branch off of dev (notifications or something) instead of just piling everything into one PR, as this is really (or rather, I'm making it!) comprised of a number of different components. Thoughts?


[SCSB] Include subfield I to indicate delivery expectations

We need to include subfield I in 876 https://github.com/pulibrary/bibdata/blob/main/marc_to_solr/lib/princeton_marc.rb#L706
per @kevinreiss: items in Massachusetts will take 3-4 days to come rather than a day so we should tell them in our various labels and notifications related to delivery expectations .
Harvard has items both in Recap and HD (Harvard Depository).
We have a sample record. TODO: Add location of that record.

@kevinreiss when do we want this to be done?

We can move forward with this now.

@kevinreiss what field should it be indexed as? What is the end-user use case?

The end user case is items take 1-2 days longer to come from the HD warehouse instead of ReCAP. We can update the various expected delivery times we cite in the interface and emails to indicate this based on this value. This is new data so we need to create a new field to store it. In SCSB the attribute name used is "storage location". It's kind of long but we could do the name as "storage_location".

I looked in HL_20210716_063500.zip added in SCSB on 07/21/2021 and didnt find a 876$i.

Since this is item information can it be added as an attribute in the holdings1_display like we do for 876$zxh ? Do we need a new field? @kevinreiss

We should add a new field to the item level data that makes it into the solr doc that reside in holdings1_display for the SCSB records. The 876 is intended to represent data at the item so even though it may seem a bit repetitive I think it's best to keep there in our JSON data alongside the other item-level attributes.

Ok so my understanding is that we don't need an extra solr field. Only to include it in the holdings_1display field and only for scsb.


How to run swarm learning in just different systems using a single licence?

I have successfully changed the test example for my application.
The swarm learning in one system with two nodes works good for my application.
Now I have three systems in the organization having different data in the same format. Can I run the whole setup in different systems?
What can I do since I don't have 10 systems as required for the MNIST example?
Can I run the sentinel node and the swarm learning node in a single system?

As your setup is within organization, you don’t need to start second SN node.
You can use one of the PC to run SPIRE, APLS and SN node. Start one SL in this PC.
Use other 2 PCs for SL only and attached to running SPIRE, APLS and SN in first PC.
As the first PC running most of the load, try to select first PC which has good performance out of 3 PCS.
Please follow setup as in swarm-learning/examples/mnist/ without second SN.

Instructions provided to make setup with 3 PCs. This issue will be closed, requesting user to try and re-open/create issue if needed.


org.java_websocket.exceptions.InvalidFrameException：bad rsv 4

How to solve this
org.java_websocket.exceptions.InvalidFrameException: bad rsv 4
at org.java_websocket.drafts.Draft_10.translateSingleFrame(Draft_10.java:309)
at org.java_websocket.drafts.Draft_10.translateFrame(Draft_10.java:286)
at org.java_websocket.WebSocketImpl.decodeFrames(WebSocketImpl.java:312)
at org.java_websocket.WebSocketImpl.decode(WebSocketImpl.java:157)
at org.java_websocket.client.WebSocketClient.interruptableRun(WebSocketClient.java:230)
at org.java_websocket.client.WebSocketClient.run(WebSocketClient.java:188)
at java.lang.Thread.run(Thread.java:748)

Please update to the latest version and if the issue still persists provide clear steps to repeat.

Updated to the latest version，Draft_6455 It doesn't meet my needs，Unable to establish a connection with the other party's service, refuses to shake hands，Can you add a wechat or QQ chat

I just tried the latest version and found that the URL can be escaped to get the information. Otherwise, or ENCODE will report an error

Well then the other party is not a websocket server.
Please provide steps to repeat!

client =  new WebSocketClient(new URI(wsUrl), new Draft_6455(), headerMap, 10000){}

That's not very helpful without access to the server or its source code (or at least more details).
One possibility is that the server is using socket.io, which is not compatible with direct WebSocket clients.


Collaboration is not working after adding a new contact

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
After adding a new contact I can't start a collab session with him ! Even thru it worked in the beginning !
Environment

If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response

Hi Enzime, can you attach what's in your Zed log when you try to collaborate with your contact? You can access it with zed: open log

nothing in there. it was empty


Fix Hints Not Showing for Open Tabs

Summary
This pull request addresses an issue where hints were not visible when viewing open tabs in the Surfingkeys. This doesn't happen in the stock theme but it was occurring here with rose-pine.
Before

After

Overview of changes

Updated the generated content from @rose-pine/build in the readme.md to reflect the current build version
Froze the width and height of the tabs this was to solve an issue where the current tab sizing was inconsistent with the rest of the tabs
Hid random 0 opacity rocket that was taking up space in tabs
Tab hints no longer using fixed positioning
Tabs are now using flex

thanks


Be careful with Import text for Ethereum or Tezos

=> Text should change if a user want to import an Ethereum wallet or a Tezos wallet

Ethereum private key is made up of 64 hex characters
Tezos private key is made up of 54 hex characters


[HOLD for payment 2021-12-27] Growl is not in the center. It's in center in ios & android - Reported by: @thesahindia

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Navigate to profile settings
Makes some changes in profile
Press the save button

Expected Result:
The Growl should be in the center
Actual Result:
Growl is not aligned in the center of the modal
Workaround:
None needed visual issue.
Platform:

Where is this issue occurring?

Web
Desktop

Version Number: 1.1.18-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @thesahindia
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1638794486239900
View all open jobs on GitHub
view this job on upwork

Triggered auto assignment to @luacmartins (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

This can definitely be external. Updating labels.

Triggered auto assignment to @jboniface (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Proposal
https://github.com/Expensify/App/blob/de633f2a3e32157fe396f18cb6803a1968e894c0/src/styles/styles.js#L1993-L1994
decreasing the maxWidth to 375 will solve this

.

Proposal
A slightly different approach than @thesahindia 's proposal
It should be better variables.sideBarWidth not 375
growlNotificationDesktopContainer: {
  // ↓ ↓ ↓ LIKE THIS
  maxWidth: variables.sideBarWidth,
  right: 0,
  position: 'fixed',
},

@kakajann, thanks for pointing out and yes the variable should be used. I did not notice that.

job posted https://www.upwork.com/jobs/~01637ba6d2232cf7fd

Triggered auto assignment to @parasharrajat (Exported)

Triggered auto assignment to @Julesssss (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

Noticed a mistake for the QA team. This issue is raised for the Web and works well on IOS and Android. cc: @isagoico
Form slack

Bug: Growl is not in the center. It's in center in ios & android

I liked @thesahindia 's proposal. He reported the issue and proposed first.
Thanks, @kakajann for posting the proposal but the difference is not significant and both use the same approach.
cc: @Julesssss

I actually think that using the variable is a better solution. @Julesssss up to you to decide!

I agree but I think this can be adjusted during the review but does not require logical change. Let me update the prev comment.

Noticed a mistake for the QA team. This issue is raised for the Web and works well on IOS and Android. cc: @isagoico
Form slack

Bug: Growl is not in the center. It's in center in ios & android

My apologies! I completely mixed them up, thank you so much for the clarification @parasharrajat

I also like @thesahindia's solution. They were the first to point out the solution and also noticed the bug in the first place.
Please submit a PR @thesahindia. And please hire in UpWork @jboniface

hired

on staging

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.1.21-1 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/6665

If no regressions arise, payment will be issued on 2021-12-27. :confetti_ball:

@thesahindia paid 👍🏽


Align indenting to existing codebase and disable ASI

Set indenting to 4 as this should match the existing code base - not change it
Require newlines to prevent ASI - this removes any concern with plusplus so disable that rule
Change the curly braces rule as the previous ones required some confusing formatting at times

Opened on the wrong repository - closed in favour of https://github.com/92green/eslint-config-platypus/pull/3


FLAGS.input returns ""

https://github.com/google/or-tools/blob/ee6f7db8b9c20681fe6c8034ac96c62c28865c40/examples/python/rcpsp_sat.py#L309
FLAGS.input returns an empty string, is that right?

Not an issue.
You need to pass --input  to the command line.


[Feature Request] Ability to disable centering behavior

I was curious how difficult it would be to disable the centering behavior of the circle packing algorithm. The reason for this is that I am somewhat misusing this library, not for packing, but for making sure objects don't overlap in 3D printing application. I notice there is a function to "setCenteringPasses(number)" but that the argument is documented as requiring a number equal to at least one. Would it be possible to allow that to be zero, in which case, only overlapping circles would be moved to not overlap,  while others would remain where they are? I have not tried to set this to zero to see whether the behavior already exists.

So I was able to accomplish what I wanted by changing a single character in the code here and it behaved exactly as I had hoped. It seems to work, but I do not know enough to see whether it may have unintended side effects.
if ( typeof message === 'number' && message >= 0 ) {
   circleManager.numberOfCollisionPasses = message;
}

Not sure whether you consider this use case to be significant enough to include in the mainline code.

hey @marciot thank you for your interest in this library and for feature suggestion. I think it's a great idea and will take a closer look once I have a bit more time on my hands. I hope this is OK.
thanks again!

@snorpey: Thank you for the consideration! No rush on this, but I thought of a possible variant which is slightly more comprehensive.
If it were possible to disable the centering pass on objects but not others, similar to packer.pinCircle(...);, this would give the user even more control.
I think maybe each circle could have flag indicating whether:

Whether it is pinned (i.e. a pinned object will never move, but can affect other objects)
Whether it will be centered (default) or whether it will only move when overlapping another object

This would give the app developer a lot of control over the behavior of individual objects. In my 3D printing app, I would definitely be able to use the feature to give the user more control over how to arrange objects.

@marciot i just published version 1.1.3. have a look at the setCircleCenterPull() and setCenterPull() methods. let me know if you have any questions. thanks again for your feedback!

@snorpey: I just added the new library to Symple Slicer and it works great! With the new feature set, I was able to allow the user to select multiple objects to pack to the center. Works great! Thank you for being so responsive!

@marciot i just published version 1.1.3. have a look at the setCircleCenterPull() and setCenterPull() methods. let me know if you have any questions. thanks again for your feedback!


Add URI section to the pack details page

Changes

Added URI section to the pack details page

Fixes #23


implement close connection

search connection from global by peer name and close it. when send returns an error or when receive mismatched connection, we need to close it explicitly.

use Arc::ptr_eq to judge if two actor is the same


Running multiple queries simoultaneusly

Super cool library!
However, I'm not succeeding at making multiple requests run simultaneously. Here is my (pseudo) code:
        GPT3PROMPT = AsyncGPT3Prompt("Test prompt, answer: ")

        async def answer_question(question):
            r = await GPT3PROMPT(question)
            print("STEP")
            return r

        loop = asyncio.new_event_loop()
        asyncio.set_event_loop(loop)

        pending_questions = []
        for question in self.questions:
            pending_questions.append(loop.create_task(answer_question(question)))

        answers = []
        for answer in loop.run_until_complete(asyncio.gather(*pending_questions)):
            answers.append(answer)

        loop.close()

I can see that the 'STEP' is printed sequentially with a few seconds in between prints, so the requests are not being sent at the same time. I am not super familiar with aiohttp, but I think this may be because the same session needs to be used for all the requests?
Is this not supported by lambdaprompt? Or should I be doing something differently?
(I could also use separate threads but I would prefer to do this concurrently)

hmm... there does seem to be something weird going on. I did a lot of things to fight asyncio when making this so the package had both direct and async calls... maybe somewhere along the way i ended up breaking the whole point of having async functions and didn't even notice! haha
I just reconfirmed with this code
from lambdaprompt import AsyncGPT3Prompt
import asyncio

GPT3PROMPT = AsyncGPT3Prompt("Test {{ question }}, answer: ")

async def answer_question(question):
    print("Enter step")
    r = await GPT3PROMPT(question=question)
    print("STEP")
    return r

answers = await asyncio.gather(*[
    answer_question("What is the answer to life, the universe, and everything?"),
    answer_question("How much wood could a woodchuck chuck if a woodchuck could chuck wood?"),
    answer_question("What is the meaning of life?"),
])

that the "steps" come out roughly uniformly rather than "all at once".
I'll dig around for a little bit soon and see if I can figure this out, hopefully its something simple...
Also, if you look into it (there's not too much code) and notice any glaring errors, shout them out! I'm curious about resolving this asap.

Okay, I figured it out. I was trying to be too clever in the code - i was trying to be very DRY in the __call__ method, but theres just no way around needing to actually use an await. which means that i need to keep ~13 lines of repeated code around.
Here's the diff
https://github.com/approximatelabs/lambdaprompt/commit/3483858aa82e28b3b5d19fd966ca06490e025966
I just pushed it up, it should be (soon) available as lambdaprompt 0.3.5
so if you run a pip install -U lambdaprompt you should get the new version and it should work for exactly your use case.
Please report back if the fix works for you! :)

Thanks a lot!
It works perfectly now :)


DX12 requests that a texture optionally has a clear value associated

D3D12 WARNING: ID3D12CommandList::ClearRenderTargetView: The clear values do not match those passed to resource creation. The clear operation is typically slower as a result; but will still clear to the desired value. [ EXECUTION WARNING #820: CLEARRENDERTARGETVIEW_MISMATCHINGCLEARVALUE]
Add a D3D12_CLEAR_VALUE argument to ID3D12Device_CreateCommittedResource it needs the textureformat, but the one of the rtv not the texture itself.

Probably something for #157

This is one of those weird D3D12-isms that doesn't really make sense in any other backend. I agree that a property for it might make sense but nothing more.

https://github.com/thatcosmonaut/SDL/commit/5b93d39bd990a436c2804b7cb6947602bdeb1cdc


vboxmanage command not found in linux

I was trying to run the example script and it returned with the error vboxmanage command not found. In Linux this command is case sensitive - must be VBoxManage.

@mmumshad got it - will update it ASAP.


maven repo has problem? there's  no jar found @ maven path

MyBatis version
3.3.1
Database vendor and version
Test case or example project
Steps to reproduce
Expected result
Actual result

sorry, I mean generator

As stated in the issue template, we use GitHub Issues only to track bugs and feature requests.
Please post your question to the mailing list.
Thank you!


☂ External Resources

Goals

Indexable / Searchable in some way?

Provide keywords or descriptions of the resources

Easily updated by community members

1 big .mdx maybe ?

Easy to find on side bar

Stretch Goal

Searchable on its own?

have its own section within search bar aka "search external resources"

Indexable by author?

Can see all resources by any one author

ToDos

[x] #78
[x] #77

This is a good idea, we - I - have some notes on this already, will update this issue later.

@alexanderniebuhr Are we tied to the use of the  I feel it makes it harder to read than just a list of links honestly and it takes up a lot more space

I agree with you Oliver

We don't need to use the <Link> card, but we should also not just list them as text. In the feature we will add more meta information to them, like dates, authors, etc. So we need a component, which allows for that design.


update

What kind of change does this PR introduce?

Does this PR introduce a breaking change?

What needs to be documented once your changes are merged?

👷 Deploy Preview for sparkly-lebkuchen-8cd4c3 processing.

Name
Link

🔨 Latest commit
7908eedac7bde6c32a30dbc6a4592535ffc8fda9

🔍 Latest deploy log
https://app.netlify.com/sites/sparkly-lebkuchen-8cd4c3/deploys/62bb04201823ad00083f52be


Docs & training for new context calibration

Use new calibration (from issue #200 ) to create comprehensive tutorial and docs for adding a new context to FPsim.

Done with FPsim 1.0


Best way to switch modes

I'm trying to see if I can have a table set to scrolling, and then via javascript change the container to fullsize, which changes the vertical scroll to on the container instead of the page.  when I try to reinitialize but for inner scrolling.

.destroy() the plugin and re-init it when this happens. There is no other way.

no response, closing


Microsoft Intune PowerShell service principal Application ID.

With the recent announcement from Microsoft that scripts containing the Intune application ID (d1ddf0e4-d672-4dae-b554-9d5bdfd93547) will need to be updated with the new application ID.  Does anyone know if this one or those in PowerShell gallery when using "Install-Script -Name Upload-WindowsAutopilotDeviceInfo"  will be updated?

same here. An update would be very nice

We have switched to Get-WindowsAutoPilotInfo for now. It uses the Graph Api.
Install-Script -Name Get-WindowsAutoPilotInfo -Force
Get-WindowsAutoPilotInfo.ps1 -online

That one work. The original script does not, if application is re-created, all I get is an error:
AADSTS500119: Redirect URIs with urn: schemes are prohibited. Use a different scheme, or https://login.microsoftonline.com/common/oauth2/nativeclient

That one work. The original script does not, if application is re-created (as per this - https://learn.microsoft.com/en-us/answers/questions/1659638/weve-detected-a-microsoft-intune-powershell-script?page=1 ), all I get is an error:
AADSTS500119: Redirect URIs with urn: schemes are prohibited. Use a different scheme, or https://login.microsoftonline.com/common/oauth2/nativeclient

Did not work for me. URL says the version is 3.9 but the file is 3.5.
https://www.powershellgallery.com/packages/Get-WindowsAutoPilotInfo/3.9/Content/Get-WindowsAutopilotInfo.ps1


some integers need to be serialized as strings

<EMAIL_ADDRESS>on 25 Aug 2011 at 9:04:
If the JSON describes an API parameter or property as having type=="string" but
format=="int64", etc, it needs to be un/marshalled as a string.

(This is because JavaScript only has doubles and 52 bits of integer precission)

Until this is fixed, some parameters won't work.  Parameters that go in the URL
are fine, but ones that are in JSON bodies probably won't work.

Related:
http://codereview.appspot.com/4918051/

<EMAIL_ADDRESS>on 25 Aug 2011 at 9:12:
Wherever this is an issue, the auto-generated code now has this comment:

  // WARNING: this field may not work, until this bug is fixed:
  // http://code.google.com/p/google-api-go-client/issues/detail?id=1

<EMAIL_ADDRESS>on 29 Aug 2011 at 9:20:
Fixed by:
http://code.google.com/p/google-api-go-client/source/detail?r=b8d5df551766d42e2a
023c55f7ab9c55b4396ccd

which requires Go change:
http://code.google.com/p/go/source/detail?r=ba6daf799367519ebd5f161bf3b53db3dcbb
3828

<EMAIL_ADDRESS>on 29 Aug 2011 at 9:20:
Status changed to Fixed.


python312Packages.mailchecker: 6.0.11 -> 6.0.13

Changelog: https://github.com/FGRibreau/mailchecker/blob/v6.0.13/CHANGELOG.md

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 361546

x86_64-linux

:white_check_mark: 8 packages built:

python311Packages.mailchecker
python311Packages.mailchecker.dist
python311Packages.python-benedict
python311Packages.python-benedict.dist
python312Packages.mailchecker
python312Packages.mailchecker.dist
python312Packages.python-benedict
python312Packages.python-benedict.dist


fix: Show README.md on crates.io

This goes with the common approach I have seen work.
readme.workspace = true may work - but I am not sure. e.g. https://crates.io/crates/meilisearch & https://crates.io/crates/crane & https://crates.io/crates/yara-x-parser are not showing it.

This is needed


Removing context from metadata when None

Description
PineconeVectorStore doesn't like None values in metadata and so by removing the context that should resolve errors when upserting.
Fixes # (issue)
Type of Change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Added new unit/integration tests
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

Thanks!


Autofill on web is only activated after clicking twice on the TextField

When you create a TextField with autofillHints, at least on web the hint is only activate after you click twice on the TextField. If you have multiple TextFields you can keep on clicking through them all without ever seeing the hints unless you click again once the caret is active in the TextField.
Seeing other sites, this is not the expected behavior, which makes sense... I would expect for the hint to show up as soon as the TextField has focus.
Here is a reproducible code for DartPad:
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            TextFormField(
              autofillHints: [AutofillHints.email],
            decoration: InputDecoration(
            hintText: 'Email',

          ),

            ),
            TextFormField(
              autofillHints: [AutofillHints.telephoneNumber],
            decoration: InputDecoration(
            hintText: 'Phone',

          ),

            ),
          ],
        ),
      ),
    ),
    );
  }
}

At the time of posting, DartPad is Based on Flutter 1.22.0-12.1.pre Dart SDK 2.9.3

I was able to reproduce this on latest master channel. You may need to try few times to reproduce the issue.

flutter doctor -v
[✓] Flutter (Channel master, 1.22.0-10.0.pre.317, on Mac OS X 10.15.6 19G2021 x86_64, locale en)
    • Flutter version 1.22.0-10.0.pre.317 at /Users/pedromassango/dev/SDKs/flutter_master
    • Framework revision 10febea877 (3 hours ago), 2020-09-23 07:22:10 +0200
    • Engine revision 57ee3d4b32
    • Dart version 2.10.0 (build 2.10.0-156.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /Users/pedromassango/Library/Android/sdk
    • Platform android-30, build-tools 30.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0, Build version 12A7209
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] IntelliJ IDEA Community Edition (version 2020.2.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 49.0.4
    • Dart plugin version 202.7319.5

[✓] VS Code (version 1.48.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.14.1

[✓] Connected device (4 available)
    • iPhone 11 Pro Max (mobile) • 7A82F29E-E49E-4B3C-8609-1570361DBC17 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-0 (simulator)
    • macOS (desktop)            • macos                                • darwin-x64     • Mac OS X 10.15.6 19G2021 x86_64
    • Web Server (web)           • web-server                           • web-javascript • Flutter Tools
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 85.0.4183.121

! Doctor found issues in 1 category.
Process finished with exit code 0

Thanks for filing the issue, I'll have look and update the issue. I changed some code path this week it might be related.

I'm not sure that is related to this but i have to make twice change on form to trigger save autofill.
https://imgur.com/a/A0M1wSR
I just copied Build a form with validation and added AutofillGroup and autofillHints. Called TextInput.finishAutofillContext() on button press. On first button press nothing happens, if i don't make a change on fields then press button, still nothing happens. Whenever i make a change on any field then click to the button, save dialog appears but saves previous state.
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    final appTitle = 'Form Validation Demo';

    return MaterialApp(
      title: appTitle,
      home: Scaffold(
        appBar: AppBar(
          title: Text(appTitle),
        ),
        body: MyCustomForm(),
      ),
    );
  }
}

class MyCustomForm extends StatefulWidget {
  @override
  MyCustomFormState createState() {
    return MyCustomFormState();
  }
}

class MyCustomFormState extends State<MyCustomForm> {
  final _formKey = GlobalKey<FormState>();

  @override
  Widget build(BuildContext context) {
    return Form(
      key: _formKey,
      child: Column(
        crossAxisAlignment: CrossAxisAlignment.center,
        children: <Widget>[
          AutofillGroup(
            child: Column(
              children: [
                TextFormField(
                  autofillHints: [AutofillHints.username],
                  validator: (value) {
                    if (value.isEmpty) {
                      return 'Please enter some text';
                    }
                    return null;
                  },
                ),
                TextFormField(
                  autofillHints: [AutofillHints.password],
                  validator: (value) {
                    if (value.isEmpty) {
                      return 'Please enter some text';
                    }
                    return null;
                  },
                ),
              ],
            ),
          ),
          Padding(
            padding: const EdgeInsets.symmetric(vertical: 16.0),
            child: RaisedButton(
              onPressed: () {
                TextInput.finishAutofillContext();
                if (_formKey.currentState.validate()) {
                  // If the form is valid, display a Snackbar.
                  Scaffold.of(context)
                      .showSnackBar(SnackBar(content: Text('Processing Data')));
                }
              },
              child: Text('Submit'),
            ),
          ),
        ],
      ),
    );
  }
}

Flutter 1.22.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision d408d302e2 (2 days ago) • 2020-09-29 11:49:17 -0700
Engine • revision 5babba6c4d
Tools • Dart 2.10.0

Sorry that I understand the issue wrong initially. I initially though for some browser element focus is not called due to a recent change.
The issue is more related to the way we implement text editing functionality for Flutter for Web. Flutter Web engine uses a native DOM element (input element or text area element) for text editing. Flutter Web Engine receives information (ex: location, style, autocomplete info) from the Framework. Using this information, engine creates a form, created input elements and appends them to the dom. Later it calls focus() on the DOM element.
Unfortunately, when element is created on the fly like this, the "autofill context menu" does not appear. The menu only appears a user, clicks on an element.
For example a javascript which (over) simplifies the operations we perform on the DOM, won't also open the "autofill menu". Only after the user clicks on this DOM element, browser shows the menu.
  var form = document.createElement("form");
  var input1 = document.createElement("input");
  var input2 = document.createElement("input");
  input1.name = 'name';
  input2.name = 'organization';
  input1.autocomplete = 'name';
  input2.autocomplete = 'organization';
  input1.text = 'text';
  input2.text = 'text';
  form.appendChild(input1);
  form.appendChild(input2);
  document.body.append(form);
  input1.focus();

Sorry to dig this up, but in my personal experience, a very basic form with autocomplete functonality is inherintly broken and unusable.
It's even annoying to use the autocomplete. It's very unintuitive, doesn't autofill all the fields at once.
IMO this issue makes it yet another bug why you shouldn't be using Flutter to begin with. It's advertised as being super-easy to use for all platforms. It's really not.

To autofill multiple fields at once, you need to wrap them in a AutofillGroup widget. I think, that the current autofill problems can be fixed in near future and then deliver a really good user experience, but for now it's not properly working, at least on web.

Still not fixed. I cant save password on web

As almost every app is having a form, i am surprised this wasn't prioritized for about 2 years :(

this is a very important problem IMO.
The safari autofill icon doesn't show up either. :(

It worked fine in 2.2.3.
Why is this bug still not fixed?

@HideakiSago Define fine
It requires 2 clicks on the field to show any suggestions which is a very unnatural user behavior. It needs to work as on other websites, u press once it show u the autofill options and then fills the whole form group

I am experiencing this bug in 3.10, how is it still not fixed?

Reproduces on the latest versions of flutter
https://github.com/flutter/flutter/assets/88313112/ecc7b92a-2a49-456c-b3a3-54e97b7d752a

code sample
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              TextFormField(
                autofillHints: const [AutofillHints.email],
                decoration: const InputDecoration(
                  hintText: 'Email',
                ),
              ),
              TextFormField(
                autofillHints: const [AutofillHints.telephoneNumber],
                decoration: const InputDecoration(
                  hintText: 'Phone',
                ),
              ),
            ],
          ),
        ),
      ),
    );
  }
}

flutter doctor -v
[!] Flutter (Channel stable, 3.19.4, on macOS 14.3.1 23D60 darwin-arm64, locale en-GB)
    • Flutter version 3.19.4 on channel stable at /Users/nexus/dev/sdks/flutter
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutters/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutter. Consider adding /Users/nexus/dev/sdks/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutters/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutter. Consider adding /Users/nexus/dev/sdks/flutter/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 68bfaea224 (7 days ago), 2024-03-20 15:36:31 -0700
    • Engine revision a5c24f538d
    • Dart version 3.3.2
    • DevTools version 2.31.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Users/nexus/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode-15.3.0.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.14.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.1)
    • Android Studio at /Users/nexus/Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.5)
    • IntelliJ at /Users/nexus/Applications/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 77.2.2
    • Dart plugin version 232.10286

[✓] VS Code (version 1.87.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.84.0

[✓] Connected device (4 available)
    • Nexus (mobile)       • 00008020-001875E83A38002E • ios            • iOS 17.4.1 21E236
    • Dean’s iPad (mobile) • 00008103-000825C811E3401E • ios            • iOS 17.4.1 21E236
    • macOS (desktop)      • macos                     • darwin-arm64   • macOS 14.3.1 23D60 darwin-arm64
    • Chrome (web)         • chrome                    • web-javascript • Google Chrome 123.0.6312.87

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 3.21.0-15.0.pre.20, on macOS 14.3.1 23D60 darwin-arm64, locale en-GB)
    • Flutter version 3.21.0-15.0.pre.20 on channel master at /Users/nexus/dev/sdks/flutters
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 202a3778bd (7 hours ago), 2024-03-27 00:51:31 -0400
    • Engine revision<PHONE_NUMBER>
    • Dart version 3.4.0 (build 3.4.0-275.0.dev)
    • DevTools version 2.34.0-dev.12

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Users/nexus/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode-15.3.0.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.14.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.1)
    • Android Studio at /Users/nexus/Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.5)
    • IntelliJ at /Users/nexus/Applications/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 77.2.2
    • Dart plugin version 232.10286

[✓] VS Code (version 1.87.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.84.0

[✓] Connected device (4 available)
    • Nexus (mobile)                  • 00008020-001875E83A38002E • ios            • iOS 17.4.1 21E236
    • macOS (desktop)                 • macos                     • darwin-arm64   • macOS 14.3.1 23D60 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad     • darwin         • macOS 14.3.1 23D60 darwin-arm64
    • Chrome (web)                    • chrome                    • web-javascript • Google Chrome 123.0.6312.87
    ! Error: Browsing on the local area network for Dean’s iPad. Ensure the device is unlocked and attached with a cable or associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)

[✓] Network resources
    • All expected network resources are available.

• No issues found!

i want to know Flutter team what time will fix this bug


Title not getting set on first app load?

Seems like the site title isn't getting set.

Seems related to https://github.com/DerMambo/ms-seo/issues/50


feat(da-clients): add Celestia client

What ❔
This PR adds a Celestia DA client.
The main complexity of this PR comes from our goal to lower the operational load and not run the Celestia light node (which is a default way of interacting with Celestia blockchain).
This was done by adapting Astria's Celestia client implementation to our codebase and removing unneeded logical components.
Note that Celestia's main communication protocol is gRPC, which means we have to import or maintain the proto definitions. I decided to reuse the generated .rs files from Astria's repo to remove the need to maintain the .proto files in our repo (not the cleanest way, but consider it a rather temporary solution).
There is a celestia-proto crate that has all the codegen that we need, but they don't generate the gRPC client definitions, only the types, so we can't use them atm. I will try to ask the team maintaining it to add such an option, then we would be able to remove all the codegen from our repo, and simply import it from celestia-proto.
Example config:
da_client:
  celestia:
    api_node_url: http://grpc-mocha.pops.one:9090
    namespace:<PHONE_NUMBER>00000000000000000000000000ca1de12a5e2d5beb9ba9
    chain_id: mocha-4
    timeout_ms: 10000

secrets:
da:
  celestia:
    private_key: PRIVATE_KEY_WITHOUT_0x_PREFIX

Why ❔
To enable Celestia DA in ZK stack
Checklist

[ ] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.
[ ] Code has been formatted via zk fmt and zk lint.

There is a celestia-proto crate that has all the codegen that we need, but they don't generate the gRPC client definitions, only the types, so we can't use them atm. I will try to ask the team maintaining it to add such an option, then we would be able to remove all the codegen from our repo, and simply import it from celestia-proto.

Hey, we should be able to add this to celestia-proto, maybe behind some feature flag :thinking:. It would be cool if you could open us an issue providing further details, which grpcs are needed, and how you would want those generated (tonic?)


PusherChannelsFlutter, Pusher Channels already initialized

I'm using this package for the first time... and when i try to init inside a try/catch block i receive this error:
I/flutter ( 7005): PlatformException(PusherChannelsFlutter, Pusher Channels already initialized., null, null)
When i get this error i can handle it.. but my question is: is there a way to check if Pusher Channels are already initialized instead of handle that inside the error method?

And i have another problem... that's my code:
try {
      await pusher.init(
        apiKey: pusherApiKey,
        cluster: pusherCluster,
        onConnectionStateChange: onConnectionStateChange,
        onError: onError,
        onEvent: onEvent,
        onSubscriptionError: onSubscriptionError,
        onDecryptionFailure: onDecryptionFailure,
        onMemberAdded: onMemberAdded,
        onMemberRemoved: onMemberRemoved,
      );

      await pusher.subscribe(channelName: pusherChannelName + user!.deliveryGuyId.toString());
      await pusher.connect();

    } catch (e) {
      print(pusher.channels);
      print(pusher.connectionState);
    }
  }

Because pusher is already initialized i can't connect because it gets an error.
This is the output on my console:
I/flutter ( 7005): {new-order-delivery-260: Instance of 'PusherChannel'}
I/flutter ( 7005): DISCONNECTED

Another test: Even if i try to connect on catch method:
...
 } catch (e) {
      print(pusher.channels);
      print(pusher.connectionState);
      await pusher.connect();
    }

the console prints:
I/flutter ( 7005): {new-order-delivery-260: Instance of 'PusherChannel'}
I/flutter ( 7005): DISCONNECTED
I/flutter ( 7005): Connection: CONNECTING
W/upeats.deliver( 7005): Reducing the number of considered missed Gc histogram windows from 1007 to 100
I/flutter ( 7005): Connection: DISCONNECTING
I/flutter ( 7005): Connection: DISCONNECTED

Hi, we have a known issue https://github.com/pusher/pusher-channels-flutter/issues/38 where hot reloading causes the android client to error with I/flutter ( 6421): Pusher ERR: PlatformException(PusherChannelsFlutter, Pusher Channels already initialized., null, null) There might a workaround in that issue thread, but for now our engineers are aware of the issue and we are prioritising it. It likely they've found it harder than expected to fix it.

any update on this issue?

still waiting for solve

any progress? thanks.

i guess its related to 'Hot restart' , cuz in the situation of "normal restart" every thing goes fine, so the plugin doesn't support the hot restart and of course the hot reload also

We have just merged https://github.com/pusher/pusher-channels-flutter/pull/80 which allow for re-initialization. Does that help in your case?

A fix for this should be present in #80 as per @proggen-com's comment. I will close this now that the fix is applied.


Errors in Django tests aren't being reported

Got a message like the following in a failing test:
 python/services/evaluationservice/dmod/evaluationservice
======================================================================
/home/runner/work/DMOD/DMOD/python/services/evaluationservice/dmod/evaluationservice
No line stating the number of tests run could be found.

That's supposed to state info on what failed. Nothing was found when parsing the output. This needs to be fixed.

Yeah, I stumbled across this in fixing #492. I think I know what is going on. Ill get a PR in here soon.

They will be reported if you throw the verbose flag with ./scripts/run_tests.sh. Otherwise the default behavior of ./scripts/test_django.py hides the output.

I may have fixed it with a PR yesterday. Had something to do with trying to parse the wrong string to find the number of tests, I believe.
Best way to test is to throw a something like self.fail("test") at the top of one of the unit tests and see what happens when you run test_django.py. The output should look as close as possible to the other results in run_tests.sh. It's gonna look strange, but that's the nature of the beast when you using fairly different tools.


Not getting past "gold" build on Mojave.

The script runs the build of binutils fine but just stops at:
Configuring gold (~11s)..
.. building gold (~1m)..
The xt-gold-make.log shows as first error:
gold-threads.cc:288:13: error: expected expression
: once_(PTHREAD_ONCE_INIT)
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include/pthread.h:216:27: note: expanded from macro 'PTHREAD_ONCE_INIT'
#define PTHREAD_ONCE_INIT {_PTHREAD_ONCE_SIG_init, {0}}
Any insights in how to get past this ?

Same / similar issue here.
My script ends as follows:
Unpacking binutils: /tmp/./cache/binutils.tar.gz to /tmp/./tmp_pkgs_G8Drky ..
Configuring binutils in /tmp/./tmp_pkgs_G8Drky (~4s) ..
.. building binutils (~1m) ..
real	0m39.891s
user	1m28.463s
sys	0m36.450s
done.
Configuring gold (~11s)..
.. building gold (~1m)..
The result is that I do have the arm64v8-ubuntu-bionic.sdk and swift.xctoolchain, but am lacking the .json
Any way to resolve this?

Hm, I've seen the : once_(PTHREAD_ONCE_INIT) thing, need to check how we worked around it.

Got it fixed.
Problem was connected to using macOS
Problem is documented at: https://sourceware.org/bugzilla/show_bug.cgi?id=23424
Solution is to patch the batch file by adding:
export CXXFLAGS="-std=c++11 -Wno-c++11-narrowing" (at line 18)
It then compiles and runs

I think this is the thing I did: https://www.jaredwolff.com/cross-compiling-on-mac-osx-for-raspberry-pi/#show1

In ./.build/src/binutils-2.25.1/gold/gold-threads.cc you will need to change the file at line 284. Here is the before and after code blocks:

class Once_initialize
{
 public:
  Once_initialize()
    : once_(PTHREAD_ONCE_INIT)
  { }

  // Return a pointer to the pthread_once_t variable.
  pthread_once_t*
  once_control()
  { return &this->once_; }

 private:
  pthread_once_t once_;
};

change it to

class Once_initialize
{
 public:
  Once_initialize()
  {once_.__sig = _PTHREAD_ONCE_SIG_init; once_.__opaque[0] = 0;}

  // Return a pointer to the pthread_once_t variable.
  pthread_once_t*
  once_control()
  { return &this->once_; }

 private:
  pthread_once_t once_;
};

If you want to provide a PR to fix this, it would be appreciated :-)

Will do as soon as everything is working.
Currently stuck on the next step :/
swift build --destination /tmp/cross-toolchain/arm64v8-ubuntu-bionic-destination.json
ld: unknown option: -rpath=$ORIGIN
:0: error: link command failed with exit code 1 (use -v to see invocation)

Got it fixed.
Problem was connected to using macOS
Problem is documented at: https://sourceware.org/bugzilla/show_bug.cgi?id=23424
Solution is to patch the batch file (build_arm64v8_ubuntu_cross_compilation_toolchain) by adding:
export CXXFLAGS="-std=c++11 -Wno-c++11-narrowing" (at line 18)
It then compiles and runs

Could you please talk about how to patch the file? It might seem silly but I can't find the file you mention. Is it really a file?
Thanks

@xloc to be honest, it's been over a year, and I've since moved to a different project.
Looking at the file I referenced, I suppose it was the file gold-thread.cc, but unfortunately can't be sure.
My goal at the time was running swift on the rpi, something which hopefully has gotten easier since then.
Sorry 'bout my limited usefulness, but I wish you a lot of success getting it to work :)

@FreekSanders Nice to hear from you, Thanks~
I think I've got it right. The problem is indeed from gold-thread.cc, exactly the same place. LOL
However, I don't really know how to update the CXXFLAGS for compilation. But fortunately, I'm able to modify the .cc file by following helje5's answer, and it worked.
Again, thanks a lot for your reply. It is so nice to have somebody discuss with me.

You're welcome

Feel free to do a PR adding additional info the the README, if that makes sense!


can't return object constructor from arrow function

Issues in TS <IP_ADDRESS> with arrow functions that return objects.
var f1=(arg)=>{key:arg}; // this compiles but generates garbage
var f2=(arg)=>{key:arg,key2:'whatever'}; // this won't compile
var f3=(arg)=>{"key":arg}; // this won't compile

When returning an object literal from an arrow function you need to enclose it in parentheses, otherwise the compiler assumes you're using the braces to denote a multi-line function. So your examples need to be:
var f1=(arg)=>({key:arg});
var f2=(arg)=>({key:arg,key2:'whatever'});
var f3=(arg)=>({"key":arg});

This is working as intended, your curly braces are denoting the start and end of the body of the arrow function, not the start of an object literal.  The second is invalid because you can't have a comma separated list of labeled statements. The third is an error because a label can't be a string literal.
This works:
var f1 = (arg) => { return { key: arg }; }
var f2 = (arg) => { return { key: arg, key2: 'whatever' }; }
var f3 = (arg) => { return { "key": arg }; }

Fair enough, thanks.


Add support for pinned/featured posts for pagination

It would be nice for the user to be able to decide for some posts to be pinned during the index pagination and their respective categories.
Preferably, the order of importance is tags -> pinned -> post date. This should not change the order of the search results.

After looking into this more, it isn't viable to implement at the moment. The query needed would add too much complexity. Instead, if a featured post is needed, it is recommended that the link be added in the hamburger menu through the config file described in #52.


(FLK-D403) First word of the first line should be properly capitalized

Description
It is recommended to capitalize the first word of the docstring.
Occurrences
There are 2 occurrences of this issue in the repository.
See all occurrences on DeepSource → deepsource.io/gh/ColinRobbins/scm-helper/issue/FLK-D403/occurrences/

Duplicate


Version 1.0.6 is broken due to minamijoyo/tfupdate 0.6.6+

Somehow on minamijoyo/tfupdate 0.6.6+ the working directory is not recognized by git as a git directory.
This results in fatal error at the first git command in entrypoint.sh, as can be seen below:

This despite the directory correctly contains the .git folder, as seen below:

The simplest fix is to rollback minamijoyo/tfupdate to 0.6.5, which I have created a PR for here #44 .
Need deeper investigation to actually find the actual fix.

Better fix is suggested by Billy here.


Perform heroku stack upgrades

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

What are we trying to do?

Our heroku stack images are heroku-16, and they've since released new ones into production. In the spirit

What feature or behavior is this required for?

Safety, up-to-date-ness

How could we solve this issue? (Not knowing is okay!)

Upgrade sandbox

Make sure everything works

Take DB backups (I have scripts for this)

Upgrade the rest of them one by one, making sure they work

Anything else?

Resolved


Documentation for getImageData() is out of date!

Hi,
I just wanted to start off by saying that I love cropper.
I noticed that the documentation of the getImageData() method is out of date. The documentation states that the method returns an object with the following properties:

left
top
width
height

The method actually returns much more:

aspectRatio
height
left
naturalHeight
naturalWidth
rotate
top
width

Updated! Thanks!