Bundler won't update to 1.16.1

Hello, I am trying to run gem install bundler, and update my current 1.16.0 version to 1.16.1

I start with this

~
$ bundle version
fatal: Not a git repository (or any of the parent directories): .git
Bundler version 1.16.0 (2018-02-07 commit )

I attempt to update bundler

~
$ gem install bundler
Successfully installed bundler-1.16.1
Parsing documentation for bundler-1.16.1
Done installing documentation for bundler after 8 seconds
1 gem installed

I try running bundle version again to confirm bundler has been updated, and get the same response I did in step 0)

~
$ bundle version
fatal: Not a git repository (or any of the parent directories): .git
Bundler version 1.16.0 (2018-02-07 commit )

when I try gem install --default bundler, I get even an even stranger result

~
$ gem install --default bundler
Successfully installed bundler-1.16.1 as a default gem
Done installing documentation for bundler after 0 seconds
1 gem installed

~
$ bundle version
/Users/ga/.rbenv/versions/2.4.2/bin/bundle:23:in `load': cannot load such file -- /Users/ga/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/bundler-1.16.1/exe/bundle (LoadError)
	from /Users/ga/.rbenv/versions/2.4.2/bin/bundle:23:in `<main>'

I can resolve the error and get back to where I started by running gem install bundler again

~
$ gem install  bundler
Successfully installed bundler-1.16.1
Parsing documentation for bundler-1.16.1
Done installing documentation for bundler after 6 seconds
1 gem installed

~
$ bundle version
fatal: Not a git repository (or any of the parent directories): .git
Bundler version 1.16.0 (2018-02-07 commit )

Here is some additional information to help troubleshoot the issue:
~
$ bundle env
fatal: Not a git repository (or any of the parent directories): .git
## Environment

\```
Bundler       1.16.0
  Platforms   ruby, x86_64-darwin-16
Ruby          2.4.2p198 (2017-09-14 revision 59899) [x86_64-darwin16]
  Full Path   /Users/ga/.rbenv/versions/2.4.2/bin/ruby
  Config Dir  /Users/ga/.rbenv/versions/2.4.2/etc
RubyGems      2.7.2
  Gem Home    /Users/ga/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0
  Gem Path    /Users/ga/.gem/ruby/2.4.0:/Users/ga/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0
  User Path   /Users/ga/.gem/ruby/2.4.0
  Bin Dir     /Users/ga/.rbenv/versions/2.4.2/bin
Tools
  Git         2.15.1
  RVM         not installed
  rbenv       rbenv 1.1.1

  chruby      not installed
\```

## Bundler Build Metadata

\```
Built At          2018-02-07
Git SHA
Released Version  false
\```

~
$ gem query --local

*** LOCAL GEMS ***

actioncable (5.1.4)
actionmailer (5.1.4)
actionpack (5.1.4)
actionview (5.1.4)
activejob (5.1.4)
activemodel (5.1.4)
activerecord (5.1.4)
activesupport (5.1.4)
arel (8.0.0)
bcrypt (3.1.11)
bigdecimal (default: 1.3.0)
bindex (0.5.0)
builder (3.2.3)
bundler (default: 1.16.1, default: 1.16.0)
byebug (9.1.0)
coderay (1.1.2)
concurrent-ruby (1.0.5)
crass (1.0.2)
did_you_mean (1.1.0)
diff-lcs (1.2.5)
erubi (1.7.0)
ffi (1.9.18)
globalid (0.4.1)
i18n (0.9.1)
io-console (default: 0.4.6)
json (default: 2.0.4)
loofah (2.1.1)
mail (2.7.0)
method_source (0.9.0)
mini_mime (1.0.0)
mini_portile2 (2.3.0)
minitest (5.10.1)
net-telnet (0.1.1)
nio4r (2.1.0)
nokogiri (1.8.1)
openssl (default: 2.0.5)
pg (0.21.0)
pkg-config (1.2.8)
power_assert (0.4.1)
pry (0.11.3)
psych (default: 2.2.2)
puma (3.10.0)
rack (2.0.3)
rack-test (0.7.0)
rails (5.1.4)
rails-dom-testing (2.0.3)
rails-html-sanitizer (1.0.3)
railties (5.1.4)
rake (12.0.0)
rdoc (default: 5.0.0)
rspec (3.7.0, 3.3.0)
rspec-core (3.7.1, 3.3.2)
rspec-expectations (3.7.0, 3.3.1)
rspec-mocks (3.7.0, 3.3.2)
rspec-support (3.7.1, 3.3.0)
rubygems-update (2.7.2)
sprockets (3.7.1)
sprockets-rails (3.2.1)
test-unit (3.2.3)
thor (0.20.0)
thread_safe (0.3.6)
tzinfo (1.2.4)
websocket-driver (0.6.5)
websocket-extensions (0.1.3)
xmlrpc (0.2.1)

temporary problem.
you can manunally git clone bundler into "/Users/ga/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0/gems/" and change name file bundler into bundler latest version

@segiddins I tried it, doesn't seem to have worked
Last login: Wed Feb  7 17:41:47 on ttys000

~
$ gem install rubygems-update -v 2.7.4
Fetching: rubygems-update-2.7.4.gem (100%)
Successfully installed rubygems-update-2.7.4
Parsing documentation for rubygems-update-2.7.4
Installing ri documentation for rubygems-update-2.7.4
Done installing documentation for rubygems-update after 48 seconds
1 gem installed

~
$ bundle version
fatal: Not a git repository (or any of the parent directories): .git
Bundler version 1.16.0 (2018-02-07 commit )

~
$ gem install bundler
Successfully installed bundler-1.16.1
Parsing documentation for bundler-1.16.1
Done installing documentation for bundler after 6 seconds
1 gem installed

~
$ bundle version
fatal: Not a git repository (or any of the parent directories): .git
Bundler version 1.16.0 (2018-02-07 commit )

~
$ bundle env
fatal: Not a git repository (or any of the parent directories): .git
## Environment

\```
Bundler       1.16.0
  Platforms   ruby, x86_64-darwin-16
Ruby          2.4.2p198 (2017-09-14 revision 59899) [x86_64-darwin16]
  Full Path   /Users/ga/.rbenv/versions/2.4.2/bin/ruby
  Config Dir  /Users/ga/.rbenv/versions/2.4.2/etc
RubyGems      2.7.2
  Gem Home    /Users/ga/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0
  Gem Path    /Users/ga/.gem/ruby/2.4.0:/Users/ga/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0
  User Path   /Users/ga/.gem/ruby/2.4.0
  Bin Dir     /Users/ga/.rbenv/versions/2.4.2/bin
Tools
  Git         2.15.1
  RVM         not installed
  rbenv       rbenv 1.1.1

  chruby      not installed
\```

## Bundler Build Metadata

\```
Built At          2018-02-07
Git SHA
Released Version  false
\```

~
$ gem query --local

*** LOCAL GEMS ***

actioncable (5.1.4)
actionmailer (5.1.4)
actionpack (5.1.4)
actionview (5.1.4)
activejob (5.1.4)
activemodel (5.1.4)
activerecord (5.1.4)
activesupport (5.1.4)
addressable (2.5.2)
arel (8.0.0)
bcrypt (3.1.11)
bigdecimal (default: 1.3.0)
bindex (0.5.0)
builder (3.2.3)
bundler (default: 1.16.1, default: 1.16.0)
byebug (10.0.0, 9.1.0)
capybara (2.17.0)
childprocess (0.8.0)
coderay (1.1.2)
coffee-rails (4.2.2)
coffee-script (2.4.1)
coffee-script-source (1.12.2)
concurrent-ruby (1.0.5)
crass (1.0.3, 1.0.2)
did_you_mean (1.1.0)
diff-lcs (1.3, 1.2.5)
erubi (1.7.0)
execjs (2.7.0)
ffi (1.9.21, 1.9.18)
globalid (0.4.1)
i18n (0.9.3, 0.9.1)
io-console (default: 0.4.6)
jbuilder (2.7.0)
json (default: 2.0.4)
listen (3.1.5)
loofah (2.1.1)
mail (2.7.0)
method_source (0.9.0)
mini_mime (1.0.0)
mini_portile2 (2.3.0)
minitest (5.11.3, 5.10.1)
multi_json (1.13.1)
net-telnet (0.1.1)
nio4r (2.2.0, 2.1.0)
nokogiri (1.8.2, 1.8.1)
nyan-cat-formatter (0.12.0)
openssl (default: 2.0.5)
pg (0.21.0)
pkg-config (1.2.8)
power_assert (0.4.1)
pry (0.11.3)
psych (default: 2.2.2)
public_suffix (3.0.1)
puma (3.11.2, 3.10.0)
rack (2.0.4, 2.0.3)
rack-test (0.8.2, 0.7.0)
rails (5.1.4)
rails-dom-testing (2.0.3)
rails-html-sanitizer (1.0.3)
railties (5.1.4)
rake (12.3.0, 12.0.0)
rb-fsevent (0.10.2)
rb-inotify (0.9.10)
rdoc (default: 5.0.0)
rspec (3.7.0, 3.3.0)
rspec-core (3.7.1, 3.3.2)
rspec-expectations (3.7.0, 3.3.1)
rspec-mocks (3.7.0, 3.3.2)
rspec-support (3.7.1, 3.3.0)
ruby_dep (1.5.0)
rubygems-update (2.7.4, 2.7.2)
rubyzip (1.2.1)
sass (3.5.5)
sass-listen (4.0.0)
sass-rails (5.0.7)
selenium-webdriver (3.9.0)
spring (2.0.2)
spring-watcher-listen (2.0.1)
sprockets (3.7.1)
sprockets-rails (3.2.1)
sqlite3 (1.3.13)
test-unit (3.2.3)
thor (0.20.0)
thread_safe (0.3.6)
tilt (2.0.8)
turbolinks (5.1.0)
turbolinks-source (5.1.0)
tzinfo (1.2.5, 1.2.4)
uglifier (4.1.5)
web-console (3.5.1)
websocket-driver (0.6.5)
websocket-extensions (0.1.3)
xmlrpc (0.2.1)
xpath (3.0.0)

~
$ gem uninstall rubygems-update -v 2.7.2
Successfully uninstalled rubygems-update-2.7.2

~
$ gem query --local

*** LOCAL GEMS ***

actioncable (5.1.4)
actionmailer (5.1.4)
actionpack (5.1.4)
actionview (5.1.4)
activejob (5.1.4)
activemodel (5.1.4)
activerecord (5.1.4)
activesupport (5.1.4)
addressable (2.5.2)
arel (8.0.0)
bcrypt (3.1.11)
bigdecimal (default: 1.3.0)
bindex (0.5.0)
builder (3.2.3)
bundler (default: 1.16.1, default: 1.16.0)
byebug (10.0.0, 9.1.0)
capybara (2.17.0)
childprocess (0.8.0)
coderay (1.1.2)
coffee-rails (4.2.2)
coffee-script (2.4.1)
coffee-script-source (1.12.2)
concurrent-ruby (1.0.5)
crass (1.0.3, 1.0.2)
did_you_mean (1.1.0)
diff-lcs (1.3, 1.2.5)
erubi (1.7.0)
execjs (2.7.0)
ffi (1.9.21, 1.9.18)
globalid (0.4.1)
i18n (0.9.3, 0.9.1)
io-console (default: 0.4.6)
jbuilder (2.7.0)
json (default: 2.0.4)
listen (3.1.5)
loofah (2.1.1)
mail (2.7.0)
method_source (0.9.0)
mini_mime (1.0.0)
mini_portile2 (2.3.0)
minitest (5.11.3, 5.10.1)
multi_json (1.13.1)
net-telnet (0.1.1)
nio4r (2.2.0, 2.1.0)
nokogiri (1.8.2, 1.8.1)
nyan-cat-formatter (0.12.0)
openssl (default: 2.0.5)
pg (0.21.0)
pkg-config (1.2.8)
power_assert (0.4.1)
pry (0.11.3)
psych (default: 2.2.2)
public_suffix (3.0.1)
puma (3.11.2, 3.10.0)
rack (2.0.4, 2.0.3)
rack-test (0.8.2, 0.7.0)
rails (5.1.4)
rails-dom-testing (2.0.3)
rails-html-sanitizer (1.0.3)
railties (5.1.4)
rake (12.3.0, 12.0.0)
rb-fsevent (0.10.2)
rb-inotify (0.9.10)
rdoc (default: 5.0.0)
rspec (3.7.0, 3.3.0)
rspec-core (3.7.1, 3.3.2)
rspec-expectations (3.7.0, 3.3.1)
rspec-mocks (3.7.0, 3.3.2)
rspec-support (3.7.1, 3.3.0)
ruby_dep (1.5.0)
rubygems-update (2.7.4)
rubyzip (1.2.1)
sass (3.5.5)
sass-listen (4.0.0)
sass-rails (5.0.7)
selenium-webdriver (3.9.0)
spring (2.0.2)
spring-watcher-listen (2.0.1)
sprockets (3.7.1)
sprockets-rails (3.2.1)
sqlite3 (1.3.13)
test-unit (3.2.3)
thor (0.20.0)
thread_safe (0.3.6)
tilt (2.0.8)
turbolinks (5.1.0)
turbolinks-source (5.1.0)
tzinfo (1.2.5, 1.2.4)
uglifier (4.1.5)
web-console (3.5.1)
websocket-driver (0.6.5)
websocket-extensions (0.1.3)
xmlrpc (0.2.1)
xpath (3.0.0)

~
$ gem install bundler
Successfully installed bundler-1.16.1
Parsing documentation for bundler-1.16.1
Done installing documentation for bundler after 6 seconds
1 gem installed

~
$ bundle version
fatal: Not a git repository (or any of the parent directories): .git
Bundler version 1.16.0 (2018-02-07 commit )

I also uninstalled the previous 2.7.2 version after installing the 2.7.4, but still no luck

Can you try to upgrade rubygems by gem update --system? It install RubyGems 2.7.5 to your environment.

@hsbt yep, I just realized I didn't update RubyGems correctly the first time 😅
here's what I got. Still seem to have the same issue, but bundle env correctly reflects the latest version of RubyGems (2.7.5)
I did get an error near the end of the installation: Permission denied @ rb_sysopen - /
~
$ gem update --system
Updating rubygems-update
Fetching: rubygems-update-2.7.5.gem (100%)
Successfully installed rubygems-update-2.7.5
Parsing documentation for rubygems-update-2.7.5
Installing ri documentation for rubygems-update-2.7.5
Installing darkfish documentation for rubygems-update-2.7.5
Done installing documentation for rubygems-update after 50 seconds
Parsing documentation for rubygems-update-2.7.5
Done installing documentation for rubygems-update after 0 seconds
Installing RubyGems 2.7.5
ERROR:  While executing gem ... (Errno::EACCES)
    Permission denied @ rb_sysopen - /Users/ga/.rbenv/versions/2.4.2/lib/ruby/site_ruby/2.4.0/rubygems/source.rb

~
$ gem install bundler
Successfully installed bundler-1.16.1
Parsing documentation for bundler-1.16.1
Done installing documentation for bundler after 6 seconds
1 gem installed

~
$ bundler version
fatal: Not a git repository (or any of the parent directories): .git
Bundler version 1.16.0 (2018-02-08 commit )

~
$ bundle env
fatal: Not a git repository (or any of the parent directories): .git
## Environment

\```
Bundler       1.16.0
  Platforms   ruby, x86_64-darwin-16
Ruby          2.4.2p198 (2017-09-14 revision 59899) [x86_64-darwin16]
  Full Path   /Users/ga/.rbenv/versions/2.4.2/bin/ruby
  Config Dir  /Users/ga/.rbenv/versions/2.4.2/etc
RubyGems      2.7.5
  Gem Home    /Users/ga/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0
  Gem Path    /Users/ga/.gem/ruby/2.4.0:/Users/ga/.rbenv/versions/2.4.2/lib/ruby/gems/2.4.0
  User Path   /Users/ga/.gem/ruby/2.4.0
  Bin Dir     /Users/ga/.rbenv/versions/2.4.2/bin
Tools
  Git         2.15.1
  RVM         not installed
  rbenv       rbenv 1.1.1

  chruby      not installed
\```

## Bundler Build Metadata

\```
Built At          2018-02-08
Git SHA
Released Version  false
\```

~
$ gem query --local

*** LOCAL GEMS ***

actioncable (5.1.4)
actionmailer (5.1.4)
actionpack (5.1.4)
actionview (5.1.4)
activejob (5.1.4)
activemodel (5.1.4)
activerecord (5.1.4)
activesupport (5.1.4)
addressable (2.5.2)
arel (8.0.0)
bcrypt (3.1.11)
bigdecimal (default: 1.3.0)
bindex (0.5.0)
builder (3.2.3)
bundler (default: 1.16.1, default: 1.16.0)
byebug (10.0.0, 9.1.0)
capybara (2.17.0)
childprocess (0.8.0)
coderay (1.1.2)
coffee-rails (4.2.2)
coffee-script (2.4.1)
coffee-script-source (1.12.2)
concurrent-ruby (1.0.5)
crass (1.0.3, 1.0.2)
did_you_mean (1.1.0)
diff-lcs (1.3, 1.2.5)
erubi (1.7.0)
execjs (2.7.0)
ffi (1.9.21, 1.9.18)
globalid (0.4.1)
i18n (0.9.3, 0.9.1)
io-console (default: 0.4.6)
jbuilder (2.7.0)
json (default: 2.0.4)
listen (3.1.5)
loofah (2.1.1)
mail (2.7.0)
method_source (0.9.0)
mini_mime (1.0.0)
mini_portile2 (2.3.0)
minitest (5.11.3, 5.10.1)
multi_json (1.13.1)
net-telnet (0.1.1)
nio4r (2.2.0, 2.1.0)
nokogiri (1.8.2, 1.8.1)
nyan-cat-formatter (0.12.0)
openssl (default: 2.0.5)
pg (0.21.0)
pkg-config (1.2.8)
power_assert (0.4.1)
pry (0.11.3)
psych (default: 2.2.2)
public_suffix (3.0.1)
puma (3.11.2, 3.10.0)
rack (2.0.4, 2.0.3)
rack-test (0.8.2, 0.7.0)
rails (5.1.4)
rails-dom-testing (2.0.3)
rails-html-sanitizer (1.0.3)
railties (5.1.4)
rake (12.3.0, 12.0.0)
rb-fsevent (0.10.2)
rb-inotify (0.9.10)
rdoc (default: 5.0.0)
rspec (3.7.0, 3.3.0)
rspec-core (3.7.1, 3.3.2)
rspec-expectations (3.7.0, 3.3.1)
rspec-mocks (3.7.0, 3.3.2)
rspec-support (3.7.1, 3.3.0)
ruby_dep (1.5.0)
rubygems-update (2.7.5, 2.7.4)
rubyzip (1.2.1)
sass (3.5.5)
sass-listen (4.0.0)
sass-rails (5.0.7)
selenium-webdriver (3.9.0)
spring (2.0.2)
spring-watcher-listen (2.0.1)
sprockets (3.7.1)
sprockets-rails (3.2.1)
sqlite3 (1.3.13)
test-unit (3.2.3)
thor (0.20.0)
thread_safe (0.3.6)
tilt (2.0.8)
turbolinks (5.1.0)
turbolinks-source (5.1.0)
tzinfo (1.2.5, 1.2.4)
uglifier (4.1.5)
web-console (3.5.1)
websocket-driver (0.6.5)
websocket-extensions (0.1.3)
xmlrpc (0.2.1)
xpath (3.0.0)

~
$ gem uninstall rubygems-update -v 2.7.4
Successfully uninstalled rubygems-update-2.7.4

~
$ gem install bundler
Successfully installed bundler-1.16.1
Parsing documentation for bundler-1.16.1
Done installing documentation for bundler after 6 seconds
1 gem installed

~
$ bundler version
fatal: Not a git repository (or any of the parent directories): .git
Bundler version 1.16.0 (2018-02-08 commit )

ERROR:  While executing gem ... (Errno::EACCES)
Permission denied @ rb_sysopen - /Users/ga/.rbenv/versions/2.4.2/lib/ruby/site_ruby/2.4.0/rubygems/source.rb

It seems to NOT the same issue. I think it was caused by RubyGems 2.7.2 that was broken version. If you have a few time, Can you try to re-install Ruby 2.4.2 and upgrade RubyGems 2.7.5.

@hsbt I actually just updated to Ruby v 2.5.0 and then upgrade my RubyGems
Good new is that I was successfully updated bundler to version 1.16.1
Bad news is that I still get the error fatal: Not a git repository (or any of the parent directories): .git, even when I'm in a git repo.
This is actually the issue I was trying to solve by updating bundler. Yesterday I was able to update to 1.16.1 and it got rid of the error, but then I must have done something because I had the problem I originally made this issue for.
Does anybody have any insight as why why I am getting the "Not a git repository" error?
~
$ ruby -v
ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-darwin16]

~
$ rbenv install 2.5.0
ruby-build: use openssl from homebrew
Downloading ruby-2.5.0.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.5/ruby-2.5.0.tar.bz2
Installing ruby-2.5.0...
Installed ruby-2.5.0 to /Users/ga/.rbenv/versions/2.5.0

~
$ rbenv init
# Load rbenv automatically by appending
# the following to ~/.bash_profile:

eval "$(rbenv init -)"

~
$ rbenv global 2.5.0

~
$ source ~/.bash_profile

~
$ ruby --version
ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin17]

~
$ gem install rubygems-update bundler
Fetching: rubygems-update-2.7.5.gem (100%)
Successfully installed rubygems-update-2.7.5
Parsing documentation for rubygems-update-2.7.5
Installing ri documentation for rubygems-update-2.7.5
Done installing documentation for rubygems-update after 47 seconds
Fetching: bundler-1.16.1.gem (100%)
Successfully installed bundler-1.16.1
Parsing documentation for bundler-1.16.1
Installing ri documentation for bundler-1.16.1
Done installing documentation for bundler after 5 seconds
2 gems installed

~
$ gem update --system
Updating rubygems-update
Successfully installed rubygems-update-2.7.5
Parsing documentation for rubygems-update-2.7.5
Installing darkfish documentation for rubygems-update-2.7.5
Done installing documentation for rubygems-update after 54 seconds
Parsing documentation for rubygems-update-2.7.5
Done installing documentation for rubygems-update after 0 seconds
Installing RubyGems 2.7.5
Bundler 1.16.1 installed
RubyGems 2.7.5 installed
Regenerating binstubs
Parsing documentation for rubygems-2.7.5
Installing ri documentation for rubygems-2.7.5

------------------------------------------------------------------------------

RubyGems installed the following executables:
	/Users/ga/.rbenv/versions/2.5.0/bin/gem
	/Users/ga/.rbenv/versions/2.5.0/bin/bundle

Ruby Interactive (ri) documentation was installed. ri is kind of like man
pages for Ruby libraries. You may access it like this:
  ri Classname
  ri Classname.class_method
  ri Classname#instance_method
If you do not wish to install this documentation in the future, use the
--no-document flag, or set it as the default in your ~/.gemrc file. See
'gem help env' for details.

RubyGems system software updated

~
$ source ~/.bash_profile

~
$ bundle env
fatal: Not a git repository (or any of the parent directories): .git
## Environment

\```
Bundler       1.16.1
  Platforms   ruby, x86_64-darwin-17
Ruby          2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin17]
  Full Path   /Users/ga/.rbenv/versions/2.5.0/bin/ruby
  Config Dir  /Users/ga/.rbenv/versions/2.5.0/etc
RubyGems      2.7.5
  Gem Home    /Users/ga/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0
  Gem Path    /Users/ga/.gem/ruby/2.5.0:/Users/ga/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0
  User Path   /Users/ga/.gem/ruby/2.5.0
  Bin Dir     /Users/ga/.rbenv/versions/2.5.0/bin
Tools
  Git         2.16.1
  RVM         not installed
  rbenv       rbenv 1.1.1

  chruby      not installed
\```

## Bundler Build Metadata

\```
Built At          2018-02-08
Git SHA
Released Version  false
\```

~
$ bundle version
fatal: Not a git repository (or any of the parent directories): .git
Bundler version 1.16.1 (2018-02-08 commit )

I couldn't reproduce it. ( I'm also maintainer of rbenv/ruby-biild)
~ > rbenv uninstall 2.5.0; and rbenv install 2.5.0
rbenv: remove /Users/hsbt/.rbenv/versions/2.5.0? [yN] y
ruby-build: use openssl from homebrew
Downloading ruby-2.5.0.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.5/ruby-2.5.0.tar.bz2
Installing ruby-2.5.0...
ruby-build: use readline from homebrew
Installed ruby-2.5.0 to /Users/hsbt/.rbenv/versions/2.5.0

~ > rbenv shell 2.5.0
~ > ruby -v
ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin17]
~ > gem update --system
Updating rubygems-update
Fetching: rubygems-update-2.7.5.gem (100%)
Successfully installed rubygems-update-2.7.5
Installing RubyGems 2.7.5
Bundler 1.16.1 installed
RubyGems 2.7.5 installed
Regenerating binstubs

------------------------------------------------------------------------------

RubyGems installed the following executables:
	/Users/hsbt/.rbenv/versions/2.5.0/bin/gem
	/Users/hsbt/.rbenv/versions/2.5.0/bin/bundle

RubyGems system software updated
~ > bundle version
Bundler version 1.16.1 (2018-02-08 commit b943955)
~ >

@hsbt I just went through the same steps you did, and yes it seems that the problem is probably something to do with my machine as I still get the same error.
The big difference I see is that I do not get a commit version when I run bundle version - mine is blank while yours is b943955
Looking at the bottom of the bundle env output, it says that the 'Release Version' is false, and I don't know what Git SHA is supposed to say next to it but it's possible that it shouldn't be blank.
In researching the fatal: Not a git repository (or any of the parent directories): .git came up with this previous bundler issue #2039 so I don't know if that helps. Looking at my Gem Path/Home it could also have to do with my ~/.gem or ~/.rbenv directories (I don't have a ~/.gemrc file)
Last login: Wed Feb  7 20:18:27 on ttys002

~
$ rbenv uninstall 2.5.0; and rbenv install 2.5.0
rbenv: remove /Users/ga/.rbenv/versions/2.5.0? [yN] y
-bash: and: command not found

~
$ rbenv install 2.5.0
ruby-build: use openssl from homebrew
Downloading ruby-2.5.0.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.5/ruby-2.5.0.tar.bz2
Installing ruby-2.5.0...
Installed ruby-2.5.0 to /Users/ga/.rbenv/versions/2.5.0

~
$ rbenv shell 2.5.0

~
$ ruby -v
ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin17]

~
$ gem update --system
Updating rubygems-update
Fetching: rubygems-update-2.7.5.gem (100%)
Successfully installed rubygems-update-2.7.5
Parsing documentation for rubygems-update-2.7.5
Installing ri documentation for rubygems-update-2.7.5
Installing darkfish documentation for rubygems-update-2.7.5
Done installing documentation for rubygems-update after 61 seconds
Parsing documentation for rubygems-update-2.7.5
Done installing documentation for rubygems-update after 0 seconds
Installing RubyGems 2.7.5
Bundler 1.16.1 installed
RubyGems 2.7.5 installed
Regenerating binstubs
Parsing documentation for rubygems-2.7.5
Installing ri documentation for rubygems-2.7.5

------------------------------------------------------------------------------

RubyGems installed the following executables:
	/Users/ga/.rbenv/versions/2.5.0/bin/gem
	/Users/ga/.rbenv/versions/2.5.0/bin/bundle

Ruby Interactive (ri) documentation was installed. ri is kind of like man
pages for Ruby libraries. You may access it like this:
  ri Classname
  ri Classname.class_method
  ri Classname#instance_method
If you do not wish to install this documentation in the future, use the
--no-document flag, or set it as the default in your ~/.gemrc file. See
'gem help env' for details.

RubyGems system software updated

~
$ bundle version
fatal: Not a git repository (or any of the parent directories): .git
Bundler version 1.16.1 (2018-02-08 commit )

~
$ bundle env
fatal: Not a git repository (or any of the parent directories): .git
## Environment

\```
Bundler       1.16.1
  Platforms   ruby, x86_64-darwin-17
Ruby          2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin17]
  Full Path   /Users/ga/.rbenv/versions/2.5.0/bin/ruby
  Config Dir  /Users/ga/.rbenv/versions/2.5.0/etc
RubyGems      2.7.5
  Gem Home    /Users/ga/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0
  Gem Path    /Users/ga/.gem/ruby/2.5.0:/Users/ga/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0
  User Path   /Users/ga/.gem/ruby/2.5.0
  Bin Dir     /Users/ga/.rbenv/versions/2.5.0/bin
Tools
  Git         2.16.1
  RVM         not installed
  rbenv       rbenv 1.1.1

  chruby      not installed
\```

## Bundler Build Metadata

\```
Built At          2018-02-08
Git SHA
Released Version  false
\```

$ ls -la ~
total 224
drwxr-xr-x+  47 ga    staff   1504 Feb  6 15:41 .
drwxr-xr-x    6 root  admin    192 Nov 13 23:17 ..
-rw-r--r--    1 ga    staff    266 Dec 15 13:49 .502478.padl
-r--------    1 ga    staff      7 Nov  8 11:42 .CFUserTextEncoding
-rw-r--r--@   1 ga    staff  24580 Feb  5 14:21 .DS_Store
drwx------    2 ga    staff     64 Feb  7 17:23 .Trash
drwxr-xr-x   11 ga    staff    352 Nov 15 09:48 .atom
-rw-------    1 ga    staff   6298 Feb  7 20:25 .bash_history
-rw-r--r--@   1 ga    staff   3958 Jan 24 11:09 .bash_profile
drwx------  104 ga    staff   3328 Dec 19 08:57 .bash_sessions
drwxr-xr-x    3 ga    staff     96 Feb  6 15:41 .bundle
drwxr-xr-x    4 ga    staff    128 Jan 26 15:47 .config
drwx------    3 ga    staff     96 Jan 26 23:03 .cups
-rw-------    1 ga    staff   9196 Jan 30 16:05 .dbshell
drwx------   12 ga    staff    384 Nov 13 12:03 .dropbox
drwxr-xr-x    3 ga    staff     96 Feb  5 10:25 .gem
-rw-r--r--    1 ga    staff  16223 Nov 28 13:09 .git-prompt.sh
-rw-r--r--    1 ga    staff    309 Jan 25 16:26 .gitconfig
-rw-r--r--    1 ga    staff    687 Nov 13 10:56 .gitignore_global
-rw-r--r--    1 ga    staff   3349 Nov 13 10:18 .installfest
drwxr-xr-x    3 ga    staff     96 Dec 15 13:49 .lightpaper
drwxr-xr-x    3 ga    staff     96 Jan  5 14:58 .local
-rw-------    1 ga    staff      0 Dec 18 11:11 .mongorc.js
drwxr-xr-x    8 ga    staff    256 Jan  7 23:00 .mume
-rw-------    1 ga    staff    197 Jan  5 14:59 .netrc
drwxr-xr-x    4 ga    staff    128 Jan 23 15:11 .node-gyp
-rw-------    1 ga    staff    427 Feb  1 10:55 .node_repl_history
drwxr-xr-x    6 ga    staff    192 Dec  8 15:58 .npm
-rw-------    1 ga    staff   5529 Feb  6 16:22 .pry_history
drwxr-xr-x    5 ga    staff    160 Nov 13 10:33 .rbenv
drwx------    5 ga    staff    160 Nov 28 11:46 .ssh
drwxr-xr-x    6 ga    staff    192 Nov 13 10:29 .subversion
-rw-------    1 ga    staff   1426 Nov 29 17:24 .viminfo
drwxr-xr-x    3 ga    staff     96 Nov 13 10:56 .vscode
drwxr-xr-x    3 ga    staff     96 Dec 13 17:50 .vscode-insiders
-rw-r--r--    1 ga    staff    116 Jan 31 17:23 .yarnrc
drwx------@   5 ga    staff    160 Nov 29 08:46 Applications
drwx------+  11 ga    staff    352 Feb  7 17:23 Desktop
drwx------+  17 ga    staff    544 Dec  8 14:11 Documents
drwx------+  30 ga    staff    960 Feb  6 17:15 Downloads
drwx------@  21 ga    staff    672 Dec 14 08:34 Dropbox
drwx------@  70 ga    staff   2240 Feb  4 14:26 Library
drwx------+   3 ga    staff     96 Nov  8 11:42 Movies
drwx------+   4 ga    staff    128 Nov 14 08:43 Music
drwx------+   9 ga    staff    288 Jan 24 15:16 Pictures
drwxr-xr-x+   5 ga    staff    160 Nov  8 11:42 Public
drwxr-xr-x@   8 ga    staff    256 Feb  4 13:42 dev

I had any combination of these errors, except the git one and "cured" it with the following sequence:
$ sudo apt-get remove ruby
$ sudo rm -rf /var/lib/gems/2.3.0
$ sudo apt-get install vim-nox # pulls in ruby and gives me $EDITOR back
$ sudo gem install bundler
$ sudo apt-get install ruby-dev # for native gems

Something Ubuntu did (best guess) kept linking / referencing bundler 1.15.3 in my case resulting in a plethora of different failures. Hope this helps other, even though it's killing a fly with an axe.

This issue has been fixed in recent releases of Bundler. You should be able to gem install bundler and run bundle env/bundle version without any issues.


Port vara-cs to use click

Basic  port of the functionality of vara-cs to use the click package. For now ext functionality is removed, will be added again in the acctual rework.
resolves se-sic/VaRA#793
related se-sic/VaRA-Tool-Suite#561
related se-sic/VaRA-Tool-Suite#563
related se-sic/VaRA-Tool-Suite#562
Renamed branch for PR History view se-sic/VaRA-Tool-Suite#557

@Sinerum From what I see, the rm stuff was never really tested. If you have a bit of time, adding 1-2 simple tests for the commands would be good I guess.
https://app.codecov.io/gh/se-sic/VaRA-Tool-Suite/compare/569/tree/varats/varats/tools/driver_casestudy.py


fix Statistics inaccurate

Proposed changes
Issue Number: noissue
Problem summary
If a table already been analyzed, then we analyze it again, the new statistics would larger than expected since the incremental would contain the values from table level statistics since the SQL lack the predication for the nullability of part_id
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[x] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[x] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.5 seconds
load time: 496 seconds
storage size:<PHONE_NUMBER>1 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221115072215_clickbench_pr_46199.html


Use rash_alt gem instead of rash gem

Hi!
To update hashie dependency version,  use rash_alt gem!
Because rash gem is not maintained now and it's dependency is 'hashie', '~> 2.0.0'.
Please review!

Thank you!


App.js has updated.

Scroll-style class name added

This is still trying to add nearly 2 million lines:

Also, this issue has been closed. There is no more need to fix it.


MYRIAD-148 Ability to correctly serialize Optional. By default Option…

…al serialized value is just "present" and not a real value (if present). Created custom serializers to serialize value versus state of Optional

Addressed review comments

LGTM. Once the license header is added, I'll merge it in.

Added license to new file


kubernetes-vault not working with Kubernetes 1.8

Due to the deprecation of the alpha and beta annotations for Init Containers, kubernetes-vault is not working for us with Kubernetes 1.8.
They removed the annotation pod.beta.kubernetes.io/init-container-statuses and moved the status to status.initContainerStatuses.  See https://kubernetes.io/docs/concepts/workloads/pods/init-containers/ at the bottom of the document. It wan't obvious in the CHANGELOG so we ran into it.
This annotation ist used to determine which Init Container needs a secret and it's used here: https://github.com/Boostport/kubernetes-vault/blob/master/cmd/controller/client/kube.go#L20
I don't have any Go experience but I'm trying to write a patch. Just want to let you know and maybe someone else has an idea or the skills to make a hotfix. 👍

@chrw Thanks for reporting! I haven't had a chance to try 1.8 yet, but I will release a patch for this one.

This is now released as v0.5.0. The docker images have also been published.

Wow. That was fast! 👍
Thank you so much for the fix. It resolves our problem.


Bump http-proxy-agent

npm audit fix

Coverage remained the same at 65.299% when pulling fd55a3dd0d52a2283e21f26f6e02ca8e0c137fff on corinagum:http-proxy-agent-bump into e3ea73eae871791582bbc9b8a9a803243f45b79a on microsoft:master.


Pretrained Weights of Differential Transformers

Thanks for the great work! Do you plan to release your pretrained weights on Hugging Face? It would be a significant contribution to the community.

looking for this too

Same here


Add example use of logs outputted with trace context

This example shows a sample application foo_library, instrumented with both the Tracing and Logging API. The result is a console output with both Logs and Traces, where the logs are injected with the span context from which they were produced.
cc @MarkSeufert @alolita

Codecov Report

Merging #20 (d9a6818) into master (c8054c5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #20   +/-   ##
=======================================
  Coverage   94.38%   94.38%
=======================================
  Files         185      185
  Lines        8014     8014
=======================================
  Hits         7564     7564
  Misses        450      450

Impacted Files
Coverage Δ

sdk/test/metrics/counter_aggregator_test.cc
98.21% <0.00%> (-1.79%)
:arrow_down:

sdk/test/metrics/gauge_aggregator_test.cc
100.00% <0.00%> (+1.75%)
:arrow_up:


improve output of export command in case of errors

Further improve #11.

Cool. Thanks for the quick response.
Example output:
$ vcs export
repositories:
  Framework:
    type: git
    error: "Could not determine ref: fatal: No upstream configured for branch 'foo'"

Framework: Could not determine ref: fatal: No upstream configured for branch 'foo'

Did you intend for the error to be printed twice?
In any case. For me this is more than good enough. Cheers!

I was still shuffling around code on this PR - now it should be final and only print errors once.

+1
Looks good:
$ vcs export
repositories:
Framework: Could not determine ref: fatal: No upstream configured for branch 'foo'

Thanks for implementing!

Thanks for testing!


Input Chinese part should use the same color as before

https://user-images.githubusercontent.com/41773861/166886728-9db12160-2345-4796-8d46-e549d3070d7f.mov

MacOS: 12.3.1
VSCode: 1.67.0-insider

Steps to Reproduce:

install extension aaron-bond.better-comments
type // !: 我是一只
type as I do in video

@alexdima

@alexdima Is this the extension issue or VSCode itself?

The text is made red through text editor decorations. When doing composition, the <textarea> for input is shown and we cannot render text editor decorations in the native <textarea>. I can't think of a way to support this at this time.

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Fix get_item to support int index and ellipsis

I fixed get_item method to support int and Ellipsis. fix #1369

LGTM!


FW auto land / MAV_CMD_DO_LAND_START

@LorenzMeier @AndreasAntener @DonLakeFlyer @sanderux
I'm looking for input to improve fixed wing auto land as part of return to land.
Questions

Would the proper way to do this be with MAV_CMD_DO_LAND_START marking the portion of the mission that auto lands?

Could we require a proper landing setup, perhaps if RTL_LAND_DELAY is not disabled?

Would this also work for the auto land mode in fixed wing?

Does "return to land" imply "return to launchpoint, then land", or just "return to launch"?

climb to RTL_RETURN_ALT
return to home position
descend to RTL_DESCEND_ALT
loiter for RTL_LAND_DELAY (indefinite if -1)
land at home

if you just entered the planes glide slope then it could back calculate the altitude which it should start to decend to the home point.

@jcooper21 yes I've been thinking about adding that to landing. Something like spiral descend and break  out at the glide slope intersection.

Yes those would be powerful features and also my favourite if implemented.

@dagar this might be helpful: https://github.com/PX4/Firmware/blob/master/src/modules/fw_pos_control_l1/fw_pos_control_l1_main.cpp#L2275-L2278

Fixed.


Added a short explanation how to run devcontainer

Pull Request
Related Issue
#75
Discussion: Benefits and Drawbacks
No Drawbacks. The project/community will benefit from the change as it shows how to use the included tooling, which will only run when installed in a specific way.
Changes to the Documentation
The READMEshould contain a short snippet explaining how to use the .devcontainer setup included in the repository. It should also contain a short explanation on how to use the makefile to this end
Proposed Release Note Entry
None
Double Check

[x] I have explained my PR according to the information in the comments
or in a linked issue.
[x] My PR targets the dev branch.

I really appreciate the PR @jahknem


Fix deprecation on graphql_definition ( Upgrade Graphql to 1.12.x)

Upgrade graphql to address:

https://github.com/rmosolgo/graphql-ruby/pull/3765
https://github.com/rmosolgo/graphql-ruby/pull/3750

Fixes :  #88

Neat. Why the draft PR? It looks good to me.

@gjtorikian the PR is not  a draft.

Ah sorry I was looking quickly and saw the timeline draft in your other repo. Thanks!

Released as 2.1.0.


Re-add loading of Wagtail icon font for userbar. Fix #5397

Fixes #5397, regression from #5215. This adds the userbar’s icons back:

[x] Do the tests still pass?
[x] Does the code comply with the style guide? (Run make lint from the Wagtail root)
~For Python changes: Have you added tests to cover the new/fixed behaviour?~
~[ ] For front-end changes: Did you test on all of Wagtail’s supported browsers?~
~For new features: Has the documentation been updated accordingly?~

Tested in macOS Chrome, Firefox, Safari + Windows IE11.

Thanks @jonnyscholes! This hasn’t been released yet so I won’t write release notes for it.


Empty tags are not considered on filtering

I've been creating AMIs with tags such as RELEASE with an empty value (I just don't add anything on the console or an empty string "" in boto3/moto)
After that, I filter using those tags. The problem I've found is that when using MOTO to mock boto3 calls the describe_iamges() behaves differently compared to boto3.
When I try to filter with a key-value where the value is empty ("") the filter is not taken into account. So instead of filtering only those images that have a RELEASE tag with an empty value, all images are returned whether they have this filter or not.
I've verified that this is not the behavior on boto3 with a real AWS account. And is not. When using boto3 only those AMIs with the value "" are returned. This only happens when using empty values in the filtering, when using any other values the correct AMIs are returned.
Some code to try to reproduce

@pytest.fixture(scope='function')
def aws_credentials():
    os.environ['AWS_ACCESS_KEY_ID'] = 'testing'
    os.environ['AWS_SECRET_ACCESS_KEY'] = 'testing'
    os.environ['AWS_SECURITY_TOKEN'] = 'testing'
    os.environ['AWS_SESSION_TOKEN'] = 'testing'
    os.environ['AWS_DEFAULT_REGION'] = 'eu-west-1'

@pytest.fixture(scope='function')
def ec2(aws_credentials):
    with mock_ec2():
        yield boto3.client('ec2', region_name=os.getenv('AWS_DEFAULT_REGION'))

def fake_images_release_list(ec2):
    fake_images = []

    instances = ec2.run_instances(ImageId='foo', MinCount=1, MaxCount=1)["Instances"]

    # create images from instance
    for i in range(0, 9):
        with freeze_time(f"2021-01-01 08:00:0{i}"):
            image = ec2.create_image(InstanceId=instances[0]["InstanceId"],
                                     Name=f"MyFooAMI{i}",
                                     Description="Test")

            response = ec2.create_tags(Resources=[image["ImageId"]],
                                       Tags=[
                                           {
                                               'Key': 'Base_AMI_Name',
                                               'Value': 'Deep Learning Base AMI (Amazon Linux 2) Version 31.0',
                                           },
                                           {
                                               'Key': 'OS_Version',
                                               'Value': 'AWS Linux 2',
                                           }
                                       ])
            fake_images.append(image)

    # Add release tags to some of the images in the middle
    for image in fake_images[3:6]:
            response = ec2.create_tags(Resources=[image["ImageId"]],
                                       Tags=[{'Key': 'RELEASE', 'Value': ''}])

    return fake_images

def test_get_latest_image_tag_as_release3(ec2):
    fake_images = fake_images_release_list(ec2)

    filter = [{"Name": 'tag:Base_AMI_Name', "Values": ['Deep Learning Base AMI (Amazon Linux 2) Version 31.0']},
              {"Name": 'tag:OS_Version', "Values": ['AWS Linux 2']},
              {"Name": 'tag:RELEASE', "Values": ['']}]

    assert len(ec2.describe_images(Owners=['self'], Filters=filter)["Images"]) == 3

Instead of the 3 images mark as release in the middle, the 9 are amis are returned

This is now fixed as of moto >= 1.3.16.dev213

This is now fixed as of moto >= 1.3.16.dev213


WIP: Initial docs structure

Related: #130

@johnyf  Let me know if you are open to implement this idea.

For a package of the size of pydot, I prefer a single Markdown file for documentation and tutorial.


make vue 3 marquee move vertically

i know this is possible and i've been trying to do it on my end, but i'm not getting it. if possible can someone implement it and i just check the code and learn from it. thanks

Reopening this to keep this option open for development


Test utils more

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 35.12%. Comparing base (ae7535c) to head (29a2be2).
Report is 7 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #29      +/-   ##
==========================================
+ Coverage   32.00%   35.12%   +3.12%
==========================================
  Files          11       11
  Lines         800      800
==========================================
+ Hits          256      281      +25
+ Misses        544      519      -25

Flag
Coverage Δ

unittests
35.12% <100.00%> (+3.12%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


btn-link

the bootstrap-class .btn-link is is destroyed by green. For example: It gives the element a border.
Please add btn-link to the not-section so its not overwritten by green

this is the code I'm using on my side to nullify the css from Green
.use-green .btn-link {
border-width: 0 !important;
&:hover,
&:active,
&.active {
background-color: transparent !important;
color: var(--intent-primary-background) !important;
}
}


Release 0.1

I created a 0.1 milestone as a way to track things that I think are part of a minimum viable first release.

[x] #14
[x] #21
[x] #24
[x] #37

Anything else that could be seen as required to be useful?

Looks great!

(Looked over the other issues and the above list looks like a good goal for a 0.1 release)

Also, I think we should nuke the https://github.com/martinlindhe/wmi_exporter/wiki/TODO wiki, and use issues with milestones & labels instead

Agreed! Wiki page removed :)

Added one more point: Which collectors should be enabled by default (also update README)? I'm assuming everything except IIS should be on by default? Working on a PR for updating exporter.go and the README.

@carlpett I think everything enabled except iis sounds reasonable too

@carlpett regarding version info in binary.. it "should" work properly now with appveyour but i would like to test it out, can we manually trigger builds with appveyor.. or should we keep fingers crossed and hope it works out when we create the 0.1 tag?

@martinlindhe Looking at the latest build from master it looks like it works:
$ ./wmi_exporter.exe -version
wmi_exporter, version 0.1.0 (branch: HEAD, revision: 8974d840d0b96bf9c5c1f912f3c4e2cc6e3bc58f)
  build user:       appvyr-win\appveyor@APPVYR-WIN
  build date:       20161014-07:59:13
  go version:       go1.7.1

One thing I just realized, though - should we overwrite the VERSION file if there is a tag?

dont know.. maybe promu dont require the VERSION file?

tested
wmi_exporter master * = $ promu build
Unable to find project's version missing `VERSION` or `version/VERSION` file
 >   wmi_exporter.exe

ends up with version field being empty in the startup log.

so.. could we fill VERSION with current tag in appveyor.yml maybe?

seems like other projects using promu has to manually bump the VERSION file, example https://github.com/prometheus/prometheus/blob/master/VERSION :-(

Yes, I think I'd prefer just setting it from the tag and not having it checked in at all. But then we'd need to do something at non-release builds. I like this approach: https://github.com/GitTools/GitVersion, what do you think?

Apparently they have some sort of integration with AppVeyor: http://gitversion.readthedocs.io/en/latest/build-server-support/build-server/appveyor/

Seems to suit our needs!
do you want to investigate using gitversion?
also, perhaps we should raise an issue with prometheus/promu if we figure out a way to avoid manually touching VERSION

All boxes checked! :tada:
Good points. I'll give gitversion a look, but let's track that separately and tag 0.1! :cake:

Okay, lets merge govendor bump and update VERSION  before tagging!

hm wait, VERSION is already "0.1.0" so we can keep it i hope

okay, here goes!

got some output from appveyor that looked bad, but release binaries was upload so guess we can ignore it?
Deploying using GitHub provider
Creating "v0.1.0" release for repository "martinlindhe/wmi_exporter" tag "v0.1.0" commit "e0b6bf5b4fbc5ff5a6bf72ed0508b3b61fe78c7b"...Skipped - release with tag "v0.1.0" already exists
Uploading "wmi_exporter-0.1.0-amd64.msi" to release assets...OK
Uploading "wmi_exporter.exe" to release assets...OK
Build success

https://ci.appveyor.com/project/martinlindhe/wmi-exporter/build/161

I think it tries to create the release, but Github automagically created a release for the tag already. So all is well :)

okay, all good then!


Fix build on newer versions of Qt.

Remove setcodec call which is no longer supported. The default is UTF-8 so this is a noop.
Use std::lower_bound instead of qLowerBound which is deprecated.
Use fontMetrics.maxWidth()

Is this about Qt6 support?

Is this about Qt6 support?

Yes, this fixes the build on Qt6.


Special case Annotated when walking annotation expressions

Currently we treat Annotated like any other annotation, but it probably makes sense to at the very least treat the second item in the subscript argument differently, since it is intended to encapsulate arbitrary values, which will likely be accessed at runtime.
So we should treat Annotated itself and the entire expression of the second item as a soft-runtime use. I'm torn about whether we should treat the first item as a soft-runtime use as well. On the one hand it will be necessary to make typing.get_type_hints work, on the other hand, there's less of a reason to use typing.get_type_hints when only trying to retrieve the second item of Annotated. Maybe this should be a setting?
One big caveat of this special casing is, that we may not have a good way of extracting Annotated from quoted annotations, so the special casing would probably be inconsistent between quoted and unquoted annotations, if this causes problems it may provide a compelling reason to actually start parsing the annotation expressions, instead of doing a simplified name extraction.

This was partially implemented in #193 but we probably want to add soft-runtime uses for the names in the value expression and add a couple of additional test cases.


Build service registry 2.2.4

/test jvm-build-service-in-repo-apicurio-e2e

/test jvm-build-service-e2e

Back to those best results with throttling on numbers @stuartwdouglas @dwalluck  :-)
    types.go:25: time: 2022-09-12 00:46:23.884587091 +0000 UTC m=+3651.616980652: dependencybuild FINAL created count: 124 complete count: 92, failed count: 24, contaminated count: 5
and lots of failure logs in https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/redhat-appstudio_jvm-build-service/251/pull-ci-redhat-appstudio-jvm-build-service-main-jvm-build-service-in-repo-apicurio-e2e/1569097553306193920/artifacts/jvm-build-service-in-repo-apicurio-e2e/jvm-build-service-in-repo-apicurio-e2e/build-log.txt to dive into


Issue #1175: Validation For RHEL Subscription Management

Signed-off-by: Rishabhm47<EMAIL_ADDRESS>Issues Resolved by this Pull Request
Validation For RHEL Subscription Management
Suggested Reviewers
@sujit-jadhav

@all-contributors add @Rishabhm47 for test, code


Import employees #41

Reformated EmployeeDashboard Navbar and turned it into a component.
Co-authored-by: Vinicius Okamoto<EMAIL_ADDRESS>

The back-end integrations are still underwork due to supabase local import.

Can you attach the issue number to this PR?

2 Problems that need to be solved before we can merge:
'ImportEmployees' is one word. Please add a space.
Also, in the attached picture, there is no label for why we are uploading a file. Please add a label.


Replace PairWithQRCode/PairWithManualCode with PairWithCode since the setup pairer internaly distinguish both

… setup pairer internaly distinguish both
Problem
While looking at #18454 I noticed that the stack does not throw an error if the manual code starts with "8" or "9", which means that the manual code version is not "0" and which imply that the encoding format has changed (since there is no good way to encode it properly otherwise).
Change overview

Returns CHIP_ERROR_INVALID_ARGUMENT if the first digit is "8" or "9".
Update PairWithQRCode/PairWithManualCode to PairWithCode since the setup code pairer is making the distinction internally.

Testing
./out/debug/standalone/chip-tool pairing code 0x12344321<PHONE_NUMBER>1

This change is much larger - it seems to contain an entire refactor of naming and replacing QRCode to just code.
Summary seems to just say "return invalid argument on manual code starting with 8 or 9".
Please split the PRs and make sure the PR content and summary match.

Makes perfect sense. I did #18606 to cover the parts that are related to the payload validation. In this PR I have only kept the bits that are related to the renaming from qrcode/manualcode to code


Get UIN/VID text box has a not working question mark

Describe the bug
Get UIN/VID text box has a not working question mark in both orange apk and purple apk
To Reproduce

Unlock the app
click on ADD ID button in home page
click on "Don't have your UIN/VID? Get it here " button.

Expected behavior
The question mark ahould show the tutorial funtion or should  not be there
Current behavior
the get UIN/VID text box has a not working question mark in both orange theme apk and purple theme apk
Screenshots

Smartphone (please complete the following information):
Device: android
MOSIP Version: 121
MOSIP server: qa-121.mosip.net
Purple APK link : https://github.com/mosip/inji/actions/runs/3240349594
Orange APK link : https://github.com/mosip/inji/suites/8476299188/artifacts/376688868

Created a duplicate bug by mistake


WIP: Adding TimeAdjustment code.  Takes MSID and returns a modified MSID.

…ith timestamps corrected for START_MINOR_FRAME on a per-sample basis
Description
Testing

[ ] Passes unit tests on MacOS, linux, Windows (at least one required)
[ ] Functional testing

Fixes #

@jmodelcxc - thanks, this looks like a great start. I just skimmed the actual code and see that it should be fine for inclusion.
Eventually this will be a function that typically just gets called within fetch.MSID, but the way you've written it now is good.
First order of business then is to make the code compliant with the Ska Python coding standards. For better or worse, we are fairly strict on following industry best-practices for code formatting, variable naming, documentation style conventions etc as defined in PEP8. This is pretty important for a large production code base. The first thing is that your code should be clean when you run this:
flake8 time_adjust.py --ignore=E402,W503,F541 --max-line-length=100

In order to get you on the right track, I ran autopep8 to fix most of the issues, and then did some edits myself to clean up much of the rest.
The next thing you can do is move the tests that are currently in main() into proper unit tests in Ska/eng_archive/tests/test_fetch.py. After that you can test with something like:
python setup.py test --args='-k test_time_adjust'

Will do on the coding style.  I'm fighting decades of individual coder bad-habits.

The next thing you can do is move the tests that are currently in main() into proper unit tests in Ska/eng_archive/tests/test_fetch.py. After that you can test with something like:
python setup.py test --args='-k test_time_adjust'

OK, that looks straightforward.  Just assert a passing test condition.

I haven't examined the history in detail but our more common practice is to rebase from main/master instead of merging.  Another option is to just rebase the PR when done to squash commits.
And still not sure if we need to remake this PR due to the odd "build" error.

I haven't examined the history in detail but our more common practice is to rebase from main/master instead of merging. Another option is to just rebase the PR when done to squash commits.
And still not sure if we need to remake this PR due to the odd "build" error.
Hi Jean,
What was the "odd build error"?   When that's all resolved  I understand your second technique (i.e.  rebase the PR to squash the commits) but I don't quite get how rebase from main/master would work.
Thanks

With regard to "I don't quite get how rebase from main/master would work.", for a lot of our work, if we're developing in a branch (that started from main) and the branch has commits 1, 2... and in the meantime unrelated commits 3, 4 have ended up in main, if we "git rebase -i origin/main" in the branch, most of the time it will rebase cleanly and the branch history will now have 3, 4, 1, 2 and the branch will only differ from main after commit 4.
But I may be using the wrong language... and there are certainly tons of git branch merge/rebase diagrams and tutorials out there.

With regard to "odd build error", this PR is still stuck at the bottom with "Some checks haven't completed yet" on a "build" that looks stuck.

With regard to "odd build error", this PR is still stuck at the bottom with "Some checks haven't completed yet" on a "build" that looks stuck.
Ah - are those checks run automatically (some kind of CI tool?)  If so is there place to see the logs?  I didn't manually "build" anything, just added/committed my files to my branch.

With regard to "I don't quite get how rebase from main/master would work.", for a lot of our work, if we're developing in a branch (that started from main) and the branch has commits 1, 2... and in the meantime unrelated commits 3, 4 have ended up in main, if we "git rebase -i origin/main" in the branch, most of the time it will rebase cleanly and the branch history will now have 3, 4, 1, 2 and the branch will only differ from main after commit 4.
But I may be using the wrong language... and there are certainly tons of git branch merge/rebase diagrams and tutorials out there.

Got it (I think), that makes sense now.  So I wouldn't need to make a new PR for that, just keep my branch abreast of the changing master

Exactly.  Those are automatic checks, and we think it should be running https://github.com/sot/eng_archive/blob/master/.github/workflows/flake8.yml .  But unfortunately, it looks like github isn't giving us anything for this weird "Waiting for status to be reported" state.  We generally get complete logs for something like a real failure in flake8 (we just saw one while working in cxotime) https://github.com/sot/cxotime/runs/1856064359 .
And I can't find anything in the github help for dealing with a "stuck" automatic check , so was somewhat wondering about making a new PR just to try to get around that issue.
Generally, we update (rebase as needed, review, add new related commits) all in the one PR that is on one conceptual change in the code (as much as that makes sense).  We often don't even need to rebase because the changes in main may not have anything to do with review of the PR... which is why I started with "I haven't examined the history in detail".  I just saw your commit messages with merges from main/master and wondered.
Sometimes, per my previous numbered example, it is necessary to get commits 3, 4 into the branch history while working on the commit 1, 2 changes... if something in 3, 4 is actually related, or just needed to test appropriately etc.

Not likely to get merged. It'll be here if it ever comes up again.


[DUOS-1596][risk=no] Add create user and create user institution to the dar collection queries

Addresses
https://broadworkbench.atlassian.net/browse/DUOS-1596
Minor update to queries so we can display more info about the create user in various DAR Collection displays
Note to reviewer: hide whitespace changes is recommended as I reformatted the reducer class.

Have you read CONTRIBUTING.md lately? If not, do that first.

Label PR with a Jira ticket number and include a link to the ticket
Label PR with a security risk modifier [no, low, medium, high]
PR describes scope of changes
Get a minimum of one thumbs worth of review, preferably two if enough team members are available
Get PO sign-off for all non-trivial UI or workflow changes
Verify all tests go green
Test this change deployed correctly and works on dev environment after deployment

Thanks @JVThomas - the next addition here is to populate the user properties so we can get PI info, etc., but I wanted to tackle that separately.


Add link to installation instructions at the start of each quick-start tutorial

Some beginner users can get confused when trying to follow the quick-start tutorial if they haven't first followed the install instructions, as the quick-start tutorials don't mention installing AutoGluon. We should add a quick 1-liner at the start of each quick-start tutorial reminding the reader to install AutoGluon before beginning the tutorial. This reminder should include a link to the install instructions, as well as any specific details they should be aware of relevant to the specific tutorial requirements (ex: requiring a GPU)

Hello, I'm a new user to autoGluon. When I tried https://auto.gluon.ai/stable/tutorials/timeseries/forecasting-quickstart.html , I found it difficult to install the right libraries version: what python version, what pandas version, what autogluon version... It took me a few days to know the working version combination: python 3.8.13 , autogluon 0.5.2 , pandas 1.4.3 and mxnet 1.9.1 .

It'd also resolve this issue: https://github.com/autogluon/autogluon/issues/2959


"Piscu Vechi" , "Pisculeț" are listed in the drop-down menu

Description:
When user writes ”Piscu Vechi" , "Pisculeț" the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Piscu Vechi"

Expected results
The location appears in the drop-down menu as "Sat Piscu Vechi, DOLJ (Piscu Vechi)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Pisculeț"

Expected results
The location appears in the drop-down menu as "Sat Pisculeț, DOLJ (Pisculeț)".


app Top Shelf Image

http://cl.ly/image/2D022R3V1T46

edit: http://cl.ly/image/2f2D2I3F182K

another option http://cl.ly/image/0h450q0k3o1O

my pref is the "art world" - moved it in, happy to change

in


Kong 0.14.0

Upgrade this app to Kong 0.14.0 using the upgraded buildpack branch.
🚧 Minimally tested so far. Please try it out and give feedback here. 🚧
Try it out

Use this branch's Deploy to Heroku button

Manually set an app's buildpack:
heroku buildpacks:set https://github.com/heroku/heroku-buildpack-kong.git#kong-0.14.0

I've been trying to make this branch work with the example configs from this repo's README, but have hit a blocker where the acl plugin won't load anymore:
2018-09-07T22:51:20.631860+00:00 app[web.1]: Starting Kong 12-factor config
2018-09-07T22:51:20.636854+00:00 app[web.1]: Kong cluster private IP: <IP_ADDRESS>
2018-09-07T22:51:20.640970+00:00 app[web.1]: Configuring as Kong proxy
2018-09-07T22:51:20.640972+00:00 app[web.1]: Wrote Kong config: config/kong.conf
2018-09-07T22:51:20.640973+00:00 app[web.1]: Wrote environment exports: .profile.d/kong-env
2018-09-07T22:51:20.818724+00:00 app[web.1]: 2018/09/07 22:51:20 [error] 42#0: init_by_lua error: /app/.heroku/share/lua/5.1/kong/init.lua:204: acl plugin is in use but not enabled
2018-09-07T22:51:20.818731+00:00 app[web.1]: stack traceback:
2018-09-07T22:51:20.818732+00:00 app[web.1]: [C]: in function 'assert'
2018-09-07T22:51:20.818734+00:00 app[web.1]: /app/.heroku/share/lua/5.1/kong/init.lua:204: in function 'init'
2018-09-07T22:51:20.818734+00:00 app[web.1]: init_by_lua:3: in main chunk

I've tried to track this down, but there's no clear reason or solution.
This branch should be considered non-functional until/unless someone can resolve this issue.

@mars forgive me asking what might be obvious, but is the ACL plugin disabled?

Hi @coopr,
How would we enable/disable or otherwise verify that an included plugin is not disabled?
I've double-checked the instructions for ACL plugin. There's nothing revealed there beyond activating it for a service via REST API call, which is how I activated it.
And with this error occurring, I can no longer even start Kong to debug further 😕

Here are a few things I can think of to double check:

Ensure kong.conf has this plugin enabled (or not disabled) https://docs.konghq.com/0.14.x/configuration/#plugins
Check the enabled flag noted in the Parameters section on https://docs.konghq.com/plugins/acl/

I'm going to ask some colleagues if they can think of anything else...

Have you configured both a Route and a Service? https://docs.konghq.com/0.14.x/proxy/#overview

A colleague pointed out that you need to change plugins = hello-world-header,ndfd-xml-as-json to plugins = bundled,hello-world-header,ndfd-xml-as-json to explicitly enable the bundled plugins that were previously enabled by default - this should probably be further clarified here https://docs.konghq.com/0.14.x/configuration/#plugins

Hey @coopr,
I'm not sure when this changed, but apparently the plugins config directive now requires bundled to be set to enable the included plugins.
By including that, the acl plugin is now available.
We still have more issues to work through for 0.14, but thanks for helping to track down that one!


Getting "NetworkClient: recieved Message was too short"

Describe the bug
When hosting and sending a custom NetworkMessage with strings, the NetworkClient on the host gets
NetworkClient: recieved Message was too short.
[IMPORTANT] How can we reproduce the issue, step by step:
Relevant script for ease (included in the zip as well) https://pastie.io/lkzkfj.cs
MirrorStringMessageError.zip

Add the component StringMessageText to the Tank
Press play and host
Press Space to send the message
Observe error

Expected behavior
The NetworkClient on the host should not error and not do much else since there's no handler registered for that client.
Screenshots

Desktop (please complete the following information):

OS: Windows
Build target: Editor
Unity version: 2020.3.13
Mirror branch: 44.0.2

@MrGadget1024 do the tags mean you were able to reproduce?

Hey I have similar issue (or the same) with NetworkClient: recieved Message was too short
When I got more time I'll try to replicate it on some test project.

+1....also experiencing this now.

+1
I'm randomly getting NetworkClient: received Message was too short which causes the client to disconnect from the server

gonna look into this week

debugging:

client sends string message: 9C-...64-66
client makes a batch with 8 bytes header, 9C-..64-66
server receives exact batch
server reads string message 9C-..64 but last byte it doesn't read
server assumes there's one more message in batch because reader isn't empty

server always receives the same StringMessage.
only the batch timestamp 8 bytes header is different each time:

for some reason, for the last message in the screenshot it didn't read everything

added some logs, now the error appears immediately after connect before even sending StringMessage:

nvm the message that I just deleted. forgot to reset position for logs.

looks like batches are accumulating.
error happens at around 13 batches in our unbatcher.
it should be 0 at the end of processing unless a scene change happened.

looks like the handler for the message id isn't found.
UnpackAndInvoke silently returns false.
Reader is never read to the end.
Batch is never retired because Reader.Remaining is never 0.
Batches keep growing forever.
adding an error log in case this happens ever again..

@vis2k Thank you so much for digging into this! I just tested, got the warning and then realized that my code indeed did not register correct handlers, something I thought I had done right haha. For posterity I'm linking the correct code here

I know I'm late but thank you @vis2k for the quick fix and @eriknielsen for the corrected code. My issue is resolved.


Greepy repair with penalized costs

We currently have the crossover::greedyRepair function to repair incomplete offspring solutions after replacing routes in SREX. This greedy repair operator only naively takes into account (in)feasibility due the time windows.
It would be nice to have a greedy repair operator that uses the Node and Route structures to compute penalized costs, similar to how the local search operators work. This can then be used for developing ruin-and-recreate based algorithms such as (A)LNS.

I think we now mostly have this.

I don't see where we have this already, are you referring to crossover::greedyRepair or LocalSearch::maybeInsert?

crossover::greedyRepair

That also means we should allow Individuals to be constructed without all required customers.
https://github.com/PyVRP/PyVRP/blob/8dc237b47ce515116f1ebd8641da3f29afcff8d1/pyvrp/cpp/Individual.cpp#L128-L135
and maybe add an attribute hasAllRequiredClients which should also be included in Individual::isFeasible.

That also means we should allow Individuals to be constructed without all required customers.

I'm already working on LNS support, so that should be OK now.

From #305: I think we can put greedyRepair or similar in a pyvrp.repair module. That module can then host our LNS repair operators. Another repair operator can be based on our local search. We should be able to make that work with very limited modification.
To make that work we need to decide what a RepairOperator should look like, while taking into account we'll probably want to use greedyRepair in crossover as well.

I'm going to finish up my other open PRs and then try to work on this, because it's somewhat of a blocker for both #305 and #307, both of which I want to see completed soon.


farray's cdelim behaves poorly for large inputs

show([0..1000000]) will consume a massive amount of memory and time.
Moving this down to c++, copying the logic of the existing cdelim makes this work.
On a related note, why is the c++ code for cdelim repeated twice, once in include/hobbes/reflect.H, and again in src/lib/hobbes/util/str.C?

Doh, looks like an entry for Accidentally Quadratic.  >_<
I have found this in a few places, where people write array code as if it was list code.  It might be better to remove the ++ definition for arrays entirely.  :T
Re: reflect.H, that's part of a small set of libraries that work as header only libraries outside of hobbes.  For example, storage.H can be used in plain C/C++ programs to log structured data into shared memory without pulling in the hobbes PL/compiler (or having to link anything).  There are several of these libraries to interact with hobbes with a minimum of overhead (net.H, fregion.H, cfregion.H, convert.H, slmap.H) and they all rely on reflect.H to describe type structures and define "standard layout" reflective types (e.g. reflect.H defines a tuple type whose memory layout matches the equivalent struct type, unlike std::tuple).

Fixed here: https://github.com/Morgan-Stanley/hobbes/pull/323


Disable staticcheck in golangci and add explicit staticcheck on different platforms with merge.

Hi, I have noticed that some lint checks are filing in the repo. It looks it could be related to staticchecker using build tags.
I have attempted to disable the staticchecker in the PR pipeline and replace it with explicit run of staticchecker on different platforms as described in the link.
I am not sure if everything works right now, so creating just a draft PR for now.

@microsoft-github-policy-service agree

@shueybubbles Can anyone please approve the Ci build, if it makes sense to you ?


Create jsonschema from Openconfig yang Model

Hi,
Is there a way to generate a jsonschema from openconfig yang models.
Intent is the below

Generate jsonschema using openconfig yang models.
Get the instance of the data  from switch for the particular model.
Use validate to verify the instance data  with the jsonschema

Thanks,

Hi there. I can't say I know what Openconfig yang is myself. This may be a good topic for either a discussion (and someone else who knows may chime in) or for the JSON Schema slack (where other folks may know what that is)


Fix auth check bug

Fix https://github.com/go-gitea/gitea/pull/24362/files#r1179095324
getAuthenticatedMeta has checked them, these code are duplicated one. And the first invokation has a wrong permission check. DownloadHandle should require read permission but not write.

I will add some tests


After rebooting single-node Microk8s, no pod is actually running but microk8s thinks they are running - so it is completely corrupted

Summary

After rebooting (caused by cloud provider as a failure) my single-node microk8s, no pod is actually running but microk8s thinks they are running - so it is completely corrupted.
More specifically, microk8s.kubectl get pods --all-namespaces yields a hundred pods (that was running before the reboot) and say they are in Running state. But using top or by really examining those pods, we see none is really running.
What Should Happen Instead?

should run normally
Reproduction Steps

have a microk8s running
reboot server

Introspection Report

root@ecs-132723:~# microk8s inspect
Inspecting Certificates
Inspecting services
  Service snap.microk8s.daemon-cluster-agent is running
  Service snap.microk8s.daemon-containerd is running
  Service snap.microk8s.daemon-apiserver-kicker is running
  Service snap.microk8s.daemon-kubelite is running
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
  Copy processes list to the final report tarball
  Copy snap list to the final report tarball
  Copy VM name (or none) to the final report tarball
  Copy disk usage information to the final report tarball
  Copy memory usage information to the final report tarball
  Copy server uptime to the final report tarball
  Copy current linux distribution to the final report tarball
  Copy openSSL information to the final report tarball
  Copy network configuration to the final report tarball
Inspecting kubernetes cluster
  Inspect kubernetes cluster
Inspecting juju
  Inspect Juju
Inspecting kubeflow
  Inspect Kubeflow

WARNING:  Docker is installed.
File "/etc/docker/daemon.json" does not exist.
You should create it and add the following lines:
{
    "insecure-registries" : ["localhost:32000"]
}
and then restart docker with: sudo systemctl restart docker
Building the report tarball
  Report tarball is at /var/snap/microk8s/3202/inspection-report-20220702_055630.tar.gz

Can you suggest a fix?

not know what's happening...
Are you interested in contributing with a fix?

yes

It is now OK... after sit and wait for a few hours it automatically heals.
But hope it can heal faster, not for hours...


fix: error message page

Try out this version of the Hiro Wallet - download extension builds.

This PR creates a generic error page route to use and replaces the current unauthorized error message seen in the tx center popup.

@kyranjamie I noticed your list of help text has a call to action in it, so using a route and passing state might not work overall. I can switch my implementation to use an error slice rather than passing state via the route? Would that work better for you?

cc/ @kyranjamie @fbwoolf @beguene @He1DAr

Discussed with @kyranjamie and will refactor to use a specific route for this error rather than setting up a generic route to handle errors.

@kyranjamie this should be ready for review again.


Import from other similar tools

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Make it possible to migrate from other no-code/low-code tools.
Examples 🌈

https://help.figma.com/hc/en-us/articles/360040514273-Import-Sketch-files
https://docs.nocodb.com/setup-and-usages/import-airtable-to-sql-database-within-a-minute-for-free

Motivation 🔦
It's unclear if this will be frequently required, but I'm creating the issue to leave a place for the community to contribute to what other tools they would like to see Toolpad support.
It can also serve as a great way to discover feature support differences.

Is it possible to write a retool JSON parser that Toolpad can read and show as a app?

Is it possible to write a retool JSON parser that Toolpad can read and show as a app?

I don't think there's enough feature parity to make this useful. Besides, their data format is un(der)documented, and probably frequently changing, we'd be chasing a moving target.
Personally I don't think this is a realistic feature request. At least not until we have reasonable feature parity and are prepared to permanently dedicate a team member to reverse engineer changes to the retool format.

I agree with Jan. I also think that such feature (if we decide to do it) should appear only when we would like to "convert" retool (or other tools) users to Toolpad users, something I imagine happening way later in development, once we have solid userbase already


Feature request: progress bar / value on postgres binary download

https://github.com/Anush008/fastembed-rs does it really well I think how they show a CLI progress bar the first time their binaries (embeddings models) are downloaded. It would be a nice small low-priority UX addition to this project to either show a similar progress bar or otherwise give developers a "download update" event allowing them to visualize the status of the binary download.

This should already be possible by using the tracing events (e.g.: https://github.com/theseus-rs/postgresql-embedded/blob/main/postgresql_archive/src/repository/github/repository.rs#L103).  I use these events in rsql with the indicatif crate to report status to the user:

I updated the axum example to include indicatif as well #124

@brianheineman Appreciate the help. Does that mean the current tracing can be used with indicatif to log a progress bar of the download status on the postgres binary?

@spikecodes I added progress information for archive downloads (#125); these changes are available in release 0.16.1.

@spikecodes I added progress information for archive downloads (#125); these changes are available in release 0.16.1.

Awesome thanks!


add python3.11

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (d60df5e) compared to base (8749e09).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##            master       #10   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         6    -2
  Lines          331       281   -50
  Branches        49        41    -8
=========================================
- Hits           331       281   -50

Impacted Files
Coverage Δ

cabina/parsers/__init__.py

cabina/__init__.py

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Handle Drag is not working in Firefox

Hi,
the Handle bar drag is not working only in Firefox. Works in Chrome and Edge.
Without Handle Drag is working.
Tried with Online Demo https://xieziyu.github.io/angular2-draggable/#/usage/options
also not working in firefox. Any workaround for this?
Thakns,
Naveen.

Looks like this issue has been introduced in v1.4.0. A workaround for now is to use v1.3.2.

@gsknbabu Thanks for reporting this issue. Will fix it soon.

Please update to v1.4.1
@danielgreen487 Yes, you're right~. It was introduced in v1.4.0 🐛


[notifications] add dart-vm entry point which is needed for flutter > 3.1.5

Fixes background execution for flutter > 3.1.5, according to https://github.com/fluttercommunity/flutter_workmanager#how-to-use-the-package

Cool! Thank you


Benchmarks are years out of date

The benchmarks page is in need of an update, many of the libraries you're measuring against are years out of date but they're being compared against the latest version of Chevrotain

I've updated all libraries to the latest version.

Some are no longer maintained...

I don't see much of a difference except
some performance improvements for Antlr4 and Peggy.
But the overall relative performance advantage of Chevrotain does not change.
After

Before


Bug(selectTranslateObject): It doesn't load the file, missing translation

Is there an existing issue for this?

[X] I have searched the existing issues

Which Transloco package(s) are the source of the bug?
Transloco
Is this a regression?
No
Current behavior
Right now if you use selectTranslateObject for a file that has not been loaded yet you get "missing translation".
The doc says:

selectTranslateObject()
Load the translation file (if not loaded yet) and behaves the same as translateObject. The only difference is that this method returns an observable to which you can subscribe.

The subscribe is executed and no translation file is loaded.
Expected behavior
It should load the file if it isn't loaded.
Please provide a link to a minimal reproduction of the bug
https://stackblitz.com/edit/ngneat-transloco-gt9vdw?file=src%2Fapp%2Fapp.module.ts
Transloco Config
No response
Please provide the environment you discovered this bug in
No response
Browser
No response
Additional context
No response
I would like to make a pull request for this bug
No

I also ran into this. I don't get any message about "missing translation", the subscription just returns the object key I requested.

As of 4.3.0 this is still a bug.
If you supply a scope in your providers:
      {
        provide: TRANSLOCO_SCOPE,
        useValue: {
          scope: 'myScope',
          loader: translocoScopeLoader((language: string) => {
            console.log(`loaded language ${language}`);
            return import(`./i18n/${language}.json`);
          }),
        },
      },

It seems that on the first load attempt you get missing translation for XYZ.
Then after a while I get the console log loaded language but I will have to manually retry fetching the translation or use the events$.
I think the expected behaviour of the transloco directive, pipe and selectTranslateObject is that it should wait for importing the language of the specified scope. So when I query for the key myScope.myPage.myTitle you can infer the scope from the first part of the key.
If anyone knows of any workarounds or hacks, that would be great.


Add 'clone node' command

Now that we have support for directly linking control plugs to other control plugs (same node or other node #380), would it be trivial to add a command for cloning nodes?
The command would make a new node of the same type as the currently selected node. Then it would link all the plugs (that are exposed in the NodeEditor) from the original node to the new node.
I've found as I've been building more and more complex networks with shared nodes, I'd like to have the same node exist in multiple places in the graph for organisational purposes (avoiding crossing noodles for example)
Feels like something I could script up myself, but would be good to have support in the core at some point.

For the sake of cleaner layouts, it would still be convenient to have something like a 'teleport' node. For example, Dan tells me that if you duplicate a texture node right now, you have a memory consequence. It would be great to have the ability to create an instance of the texture node so that it can be used in another location in a graph, without having the renderer think it's a different texture. Is this the appropriate ticket to resurrect this request?

What about making a Dot and then hiding the input connection? How far does that get you to what you want?

(Sorry if this ignores previous comments. This is in response to the two last ones.)
You can indeed already do it using dots. This however comes with a couple annoyances :
Once the dot is away from the original texture node, it's kind of hard to know what it was connected to. Would be usefull to get an optional floating label on the dots. This doesn't mean that dots should then look like nodes because a dot unique & minimalistic appearance is key to having a graph that is visually clear.
You still have to manage long connections in the graph at some point of another. I think even with the short experience everyone has with gaffer, we can agree that dragging long connections is one weak point of the node graph (and probably any node graph, not just the gaffer graph)

I think there's two possible interpretations of what a "clone" node is :
It's a node which only purpose is to replicate the appearance of a node (and its UI) so it can exist at multiple locations in the graph. All instances would be considered as being the same node when parsing the graph.
OR...
It's a instance of a node but runs its own data stream. It replicates the effect of a node of a similar type by copying its parameters. It results in separate calculations when running the graph.

These are two different concepts really and I think the later is a more conventional description for a "clone" node (and having that in a node graph can be very usefull). The first concept however is dangerous I think because it allows someone to alter parameters of a node that may affects other parts of the graph without really knowing (unless it's completely locked but then I don't see the point of replicating its UI).
The problem Mark is talking about is one I've had since I started using the gaffer node graph for lookdev. That's why I suggested a while ago to create "teleport" nodes and dots have made things better since. The idea of a "teleport" is not about replicating any behavior or UI appearance of other nodes but is just a convenient way of creating a reference to an output plug in the graph. Ideally the user can browse the scene to find the plug he's after from the "teleport" node itself (so you can also swap it easily), maybe we can even think of adding particular output plugs to a preset list of available plugs for reference so you see just that instead of a huge hierarchy of thousands of plugs.
I understand that there might be a scope limitation here. Teleporting an output plug from a node burried within a box to a teleport node that belongs to another box might be pushing this concept too far. I'm happy to think of it as something that would only work within its local scope, which is where the problem with long connection really exists.
Do that make sense and do you think it's worth creating a ticket for it ?

So I guess one thing I'm not sure of, is what's the difference in behaviour between a teleport and a dot with the input hidden? Particularly if we apply the scope limitation (which I would prefer to), are they not kindof the same thing? Or would you expect selecting a teleport to open the node editor for the input node rather than the teleport? Would that be handy for the dot anyway?
Right now you can figure out where a Dot is coming from by hovering on the input connection (and if that's hidden, it'll be shown automatically when you select the dot). That's a bit unobvious, so perhaps we should just have a little label floating alongside the Dot, showing the name of the input node?
I've been thinking of a small feature that might relate to your "preset list of available plugs for reference" idea. It's quite a simple idea - just the ability to bookmark nodes within the NodeGraph. I was imagining it would just be a "Bookmarked" checkbox on the right click node menu in the NodeGraph. When a node is bookmarked, it would appear in a "Goto" menu that would frame it in the centre of the node graph. And it could also appear in a right click menu on input plugs - so you'd right click on a plug, and then go "Connect Bookmark->MyHandyShaderNodeThatIsFarAway". Any node type could be bookmarked, and any plug could be connected to a bookmark. How does that sound?

I would expect, when selecting the teleport, to see what output plug it's connected to. (maybe as a path, all the way to the output plug name : [...whatever...]/nodename/outputplug) unless we always want to consider nodes as having only one output (but boxes can have several outputs cant they ?)
I don't like the hovering thing for this reason : I often connect back to a texture via a grade node. I still want to display my texture name as part of the dot label, but not the grade name which is likely to be names grade0123 anyway... so a custom name here is necessary
I like your idea of node bookmark and the type of workflow that goes with it. But again, should we ignore the possibility of having multiple output plugs ? so are we talking about plug bookmarks ?

Nodes can have multiple outputs, yes. I had imagined that if you bookmarked a node with multiple outputs, then when we displayed the "Connect Bookmark" menu we'd list all the output plugs compatible to the one we were connecting to. But if you think it would be useful to bookmark specific plugs too then that shouldn't be a problem…

I don't like the hovering thing for this reason : I often connect back to a texture via a grade node. I still want to display my texture name as part of the dot label, but not the grade name which is likely to be names grade0123 anyway... so a custom name here is necessary

So for the dot label, would you prefer simply to give the dot a name in the same way you would other nodes, and have that name appear floating next to the dot? Or do you want some magic that says "skip a few nodes up the chain until you hit a texture node, and use the label from that"?

I would expect, when selecting the teleport, to see what output plug it's connected to.

As some floating text next to the node, or in the NodeEditor somewhere? Will displaying the name of the connected output plug suffer from the same "texture connected via a grade" problem you mentioned for the dot?

For the dot -> custom name, up to the user to give it a convenient name, regardless of what's it's connected to.
Node bookmark exposing appropriate outputs or directly plug bookmarks, I don't really mind. I'm more concerned about how these named plugs will appear to the user. I'd love to see custom names involved anytime we bookmark something for later use. When you bookmark an internet page, you don't want to later access it as "https://www.linkedin.com/pub/john-haddon/1/562/473" but rather "John Haddon - linkedin", right ? I would think the same goes with output plug bookmarks. "grade0123.out0" will not be as informative as "graded_base_color" for instance...

I'm not sure about this internet analogy. The internet is rather large, whereas in Gaffer you already know the scope of your bookmarks (the script or box you're working in in the NodeGraph). The internet is also read-only, whereas in Gaffer you are in control of giving sensible names to nodes already. So to use the details of your analogy, you already know you're in the "https://www.linkedin.com/pub/" domain, and you can call "john-haddon/1/562/473" anything you want. In Gaffer, you can also give a node an additional description using UIEditor. I don't see why you would want to have useless node names you need to use everywhere but then have to make useful bookmark names you can only use in a couple of places.
I do like the idea of bookmarks though, and they seem to address some workflow ideas you have, so I'm rather inclined to code them up using node names and see how they work in practice...

Sure I get your point, once "grade0123" is renamed the output plug name is less of an issue, as long as the node doesn't have too many generically named outputs : out1, out2, out3, ...  but I can't think of a production case where I had to deal with one like that. Let's give that a go and see.
Thanks John !

Cool - I think #849 is close enough that we can use that as the ticket for bookmarks.


Explanation of nerfacto/-big/-huge settings

Going from nerfacto to nerfacto-big to nerfacto-huge, some setting tweaks do not seem intuitive.
I was wondering what the reasoning is for the following:
I will use the format for my explanation:
parameter_name : nerfacto value -> nerfacto-big value -> nerfacto-huge value
I would expect the changed parameters to increase from nerfacto to nerfacto-big to nerfacto-huge (big/bigger/biggest) like done for e.g.:
max_res: 2048 -> 4096 -> 8192
Instead, we find the following parameters changed like:
appearance_embed_dim : 32 -> 128 -> 32
num_nerf_samples_per_ray : 48 -> 128 -> 64
I would expect these nerfacto-huge parameters to be equal or larger than the nerfacto-big parameters, but instead they are smaller.
Why is this the case?

mark

Hm I don't think there's any particular reason for these, I think I just forgot to update nerfacto-big parameters after tuning nerfacto-huge and realizing that some didn't matter as much as I previously thought.


fix: slither not running on v2 contracts

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 61.64%. Comparing base (364c3ef) to head (7c6080a).

Additional details and impacted files
@@              Coverage Diff              @@
##           zrc-20-fixes     #286   +/-   ##
=============================================
  Coverage         61.64%   61.64%
=============================================
  Files                16       16
  Lines               425      425
  Branches             22       22
=============================================
  Hits                262      262
  Misses              160      160
  Partials              3        3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Error: Invalid Name for Prim

I am using these samples
ErrorException:
        Error in 'pxrInternal_v0_19__pxrReserved__::SdfPrimSpec::_New' at line 108 in file /home/ajan_bscs16seecs/temp/USD/pxr/usd/lib/sdf/primSpec.cpp : 'Cannot create prim '' because 'Default-effect' is not a valid name'

Almost all of them give this error

@kcoley Paul from usd interest group provided some more clarity about problems relating to the inconsistency of rigged animations on mcOS/ iOS.
usd interest post relating to inconsistencies of rigged animations on macOS/ iOS

@kcoley @wave-electron
Check out the repository. https://github.com/KhronosGroup/glTF-Sample-Models?files=1
Almost all of the samples make this error. Not just the jigged figure


Latest update crashes Forge 47.2.18

After a bit of troubleshooting (aka. deleting/reinstalling all my mods on curseforge to check for conflicts), turns out that the latest update causes modded minecraft 1.20.1 (+optifine ) to crash on launch! Just wanted to signal that :]

its not from Opti
its just in my end
i released a new update that fixes it


Terminal API: Task terminal won't send data when "reveal" == "never"

Version 1.23.0
Commit 7c7da59c2333a1306c41e6e7b68d7f0caa7b3d45
Date 2018-05-03T16:44:10.813Z
Shell 1.7.12
Renderer 58.0.3029.110
Node 7.9.0
Architecture ia32
Steps to Reproduce

Add a task to a project with "presentation.reveal": "never"

{
    "version": "2.0.0",
    "tasks": [
        {
            "type": "npm",
            "script": "start",
            "problemMatcher": [
                "$eslint-compact"
            ],
            "presentation": {
                "echo": true,
                "reveal": "never",
                "focus": false,
                "panel": "shared"
            },
            "isBackground": true
        }
    ]
}

Run the task in a task terminal with a listener attached to onData

Expected
The listener receives data sent to the terminal.
Actual
No data sent.

@Tyriar adding you as well. Is there something I need to do to make this work ?

I cannot reproduce this with the following steps (terminal panel is never opened):

Run a watch task
Attach a data listener
Trigger a watch change

Outputs fine:
[Extension Host] onData: c (at /home/daniel/dev/Microsoft/vscode-extension-samples/terminal-sample/out/extension.js:87:25)
console.ts:136 [Extension Host] onData: 11:58:33 - File change detected. Starting incremental compilation...

 (at /home/daniel/dev/Microsoft/vscode-extension-samples/terminal-sample/out/extension.js:87:25)
console.ts:136 [Extension Host] onData: 11:58:33 - Compilation complete. Watching for file changes.

 (at /home/daniel/dev/Microsoft/vscode-extension-samples/terminal-sample/out/extension.js:87:25)

Watch task I was using:
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
{
    "version": "2.0.0",
    "tasks": [
        {
            "type": "npm",
            "script": "watch",
            "problemMatcher": "$tsc-watch",
            "isBackground": true,
            "presentation": {
                "echo": true,
                "reveal": "never",
                "focus": false,
                "panel": "shared"
            },
            "group": {
                "kind": "build",
                "isDefault": true
            }
        }
    ]
}


Converting Maria1km benchmark outputs to netCDF

Hello Michael
I've been able to successfully produce ADIOS2 outputs with WRF 4.5.1 and the maria1km benchmark case. Congrats on the work done. It's a really nice development.
Regarding performance, I've been able to reduce from 5.13219s (Synchronous PnetCDF) to 1.07237s (ADIOS2), which is a very good first result. I'm using the following configuration:
 &namelist_adios2
 adios2_compression_enable = .false.,
 adios2_numaggregators = 256,
 /

In case you ask, I have not been able to make compression work.
The issue comes when using this converter (which is really key to potentially consider ADIOS2 a production filetype). I'm not able to produce a working netCDF (it's basically empty).
python convert.py --input ../WRFV4.5.1/run_maria1km/wrfout_d02_2017-09-20_09\:00\:00/ --output converted.nc
ncdump -h converted.nc
netcdf converted {
dimensions:
	Time = 1 ;
}

And BP folder seems to contain valid data...
bpls ../WRFV4.5.1/run_maria1km/wrfout_d02_2017-09-20_09\:00\:00/
  float    ACGRDFLX               {1590, 1660}
  float    ACHFX                  {1590, 1660}
  float    ACLHF                  {1590, 1660}
  float    ACLWDNB                {1590, 1660}
  float    ACLWDNBC               {1590, 1660}
  float    ACLWDNT                {1590, 1660}
  ...

Any ideas?

Hi @kserradell ,
Thanks for reaching out.
If possible can you send me a small dataset that I can debug this, with along with expected output?

Thanks for providing that Kim, it lead to a quick resolution.
It seems that this issue is due to the new format BP5 and extremely large files.
See here: https://github.com/ornladios/ADIOS2/issues/3678
Changing the open mode to rra fixes the issue and I am able to convert the file without issue.
I will work on fixing this here but meanwhile:
diff --git a/convert.py b/convert.py
index 735c06a..5dd42ae 100644
--- a/convert.py
+++ b/convert.py
@@ -1,10 +1,11 @@
-import os, sys
 import argparse
+import os
+import sys
 from collections import defaultdict

+import adios2
 import numpy as np
 from netCDF4 import Dataset
-import adios2

 try:
     from mpi4py import MPI
@@ -42,7 +43,7 @@ def open_files(input_file, output_file, parallel=False, diskless=False):
     if parallel:
         adios2f = adios2.open(input_file, "r", comm=MPI.COMM_WORLD)
     else:
-        adios2f = adios2.open(input_file, "r")
+        adios2f = adios2.open(input_file, "rra")
     netcdff = Dataset(
         output_file,
         "w",

Moving forward, in a production environment it may make sense to port this script c++, which I would assume would reduce the conversion time.

Michael!
It worked and produced a very nice WRF file (with all vars and attributes)!
Even sequentially, it produced the file in 7s.
Awesome! This is really promising!
I will keep you updated.
KiM


H1 header being treated as an H2

In this notebook, jupyter_toc is treating the "Question 1" header as if it were an H2 header. It is actually an H1 header.

Referencing the gist link made me realize that the notebook code was still defining the header as an H2. Restarting VSCode fixed it.


Adding documetation for VSTest Integration

Adding documetation for VSTest Integration. Laying out the details for the user experience and implementation.
contributes to https://github.com/tonerdo/coverlet/issues/395

Workflow is enough clear to me at this point.
Wait for @tonerdo thoughts/question.
I could try to implement collectors with MS guys supervision if we agree on it.

@MarcoRossignoli Sure.
We are willing to contribute to your repo these datacollectors, We will be happy to do so!

We are willing to contribute to your repo these datacollectors, We will be happy to do so!

No problem to me!

@tonerdo before go on with this and let @vagisha-nidhi start to work on collector we should try to merge https://github.com/tonerdo/coverlet/pull/393 so we'll use new contracts.

@vagisha-nidhi can you capitalize folder name Documentation to better adhere to foundation repo guidelines https://github.com/dotnet/foundation/blob/master/guidance/repo-guide.md

@MarcoRossignoli I have addressed the comments here.
Since #393 have contract changes in coverlet.core, it'll be good to prioritize it.
#392 is also related to these datacollector changes. Please look into this as well.

@MarcoRossignoli @tonerdo It'll be really convenient for me if you could provide an ETA on https://github.com/tonerdo/coverlet/pull/393?

Got some review from Toni https://github.com/tonerdo/coverlet/pull/393#issuecomment-491637617, I'll do my best to replace PR with simpler new one in a pair of days...I won't be available between Thursday-Sunday for a fast holiday.

@tonerdo PTAL https://github.com/tonerdo/coverlet/pull/409

@vagisha-nidhi #409 has been merged in

@tonerdo we can merge this...if during developments something change we'll update

@tonerdo This can be merged, right?


pc-api blocked in iOS 9

noticed that version 0.1.0 Bulwell Cat Watch does not render properly on iPad simulator in Xcode. debugging this seems to be an issue with iOS9 restrictions on connections not using TLS (https).

workaround - add following access exception to plist in Xcode
NSAppTransportSecurity

NSAllowsArbitraryLoads

NSExceptionDomains

<IP_ADDRESS>

NSExceptionAllowsInsecureHTTPLoads

@MapNavTom I suggest this is assigned to @jollopre.  I do not have IOS expertise or the time to do this.

will be fixed by https://github.com/edina/fieldtrip-cps/issues/45