Move this repository to the jupyterhub account?

Most of the work in repo2docker happens in the jupyterhub account. Now that we have a nifty JupyterHub cauldron page, it'd be nice if repo2docker were a part of the same org so we can track activity here too.
WDYT @yuvipanda ?

it's generally useful outside of just JupyterHub, but I don't have strong
opinions either way.
On Sun, Feb 11, 2018 at 8:43 AM, Chris Holdgraf<EMAIL_ADDRESS>wrote:

Most of the work in repo2docker happens in the jupyterhub account. Now
that we have a nifty JupyterHub cauldron page
https://cauldron.io/dashboards/jupyterhub, it'd be nice if repo2docker
were a part of the same org so we can track activity here too.
WDYT @yuvipanda https://github.com/yuvipanda ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jupyter/repo2docker/issues/232, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB23vi2JRwRer_yf6_j7YQs9v_d43K7ks5tTxifgaJpZM4SBZ7g
.

--
Yuvi Panda T
http://yuvi.in/blog

I agree that from a "what does this repo do" standpoint, it could be useful outside of jupyterhub...from my perspective this is purely from a pragmatic standpoint to make it easier to track activity across the repos that broadly make up the JupyterHub ecosystem.
Do other folks have thoughts on this? @betatim @minrk or @willingc ?

alternatively, can somebody make a 'cauldron' out of the jupyter org?

While it's technically useful outside jupyterhub, I think the question is more about what is this intended for/etc. i.e. is it a generic package for any possible repo->docker Jupyter application? Or is it really driven by Binder's needs, and a separate component.
So if it's first a generic tool that Binder happens to use, then it belongs on jupyter. If it's first Binder's implementation that's reusable outside Binder, then I think it belongs on jupyterhub.
configurable-http-proxy is an example - it is the proxy we wrote for jupyterhub, so it lives there. That doesn't mean it's only useful for jupyterhub, but that's the target application.
So I'm +0.5 to putting it on jupyterhub, but ultimately the distinctions should be communicated in the repo and its docs, rather than based on where it lives. Where it lives is just one signal.

It sounds like we have lots of +0.5s here, so I am inclined to close this and do nothing, as in general I think we should tend towards not rockin' the boat unless there's a clear reason to do so...

If it's first Binder's implementation that's reusable outside Binder, then I think it belongs on jupyterhub.

I lean toward moving it to JupyterHub. Currently, it's primary use is for Binder. While it could be used outside of Binder, it's not clear to me this is happening now. For efficiency and monitoring it, it may be better served in the JupyterHub org. Jupyter tends to have more protocol definition, notebook ui, and user facing things (i.e. website).
Having it in one org would also keep users deploying their own binderhubs from having to bounce back and forth between orgs.
Overall, I'm fine with leaving as is, but long-term it may be better served in the jupyterhub org.

FWIW I agree with @willingc :-)
so it sounds like we're at roughly
+.5 - @yuvipanda @minrk
+1 - @willingc @choldgraf
I do find myself just naturally looking for the repo2docker repository under github.com/jupyterhub...the number of times I get an error the nhave to go back and delete the hub is fairly high haha

Currently the docker image lives at 'jupyter/repo2docker' so if this gets
moved that should be moved (and all relevant places updated) too. JFYI. I'm
decidely a +0, only because my autocomplete takes me to
github.com/jupyterhub/repo2docker but that already redirects here ;)
On Mon, Feb 12, 2018 at 8:58 AM, Chris Holdgraf<EMAIL_ADDRESS>wrote:

FWIW I agree with @willingc https://github.com/willingc :-)
so it sounds like we're at roughly
+.5 - @yuvipanda https://github.com/yuvipanda @minrk
https://github.com/minrk
+1 - @willingc https://github.com/willingc @choldgraf
https://github.com/choldgraf
I do find myself just naturally looking for the repo2docker repository
under github.com/jupyterhub...the number of times I get an error the
nhave to go back and delete the hub is fairly high haha
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jupyter/repo2docker/issues/232#issuecomment-364988563,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB23hrfOmuRysssq8aysBVBH5rODhX8ks5tUG2rgaJpZM4SBZ7g
.

--
Yuvi Panda T
http://yuvi.in/blog

I'm a +1 on the basis of its intended purpose and scope.

My two cents: I don't care enough to do the clean up work this would require. If someone else feels like doing it that would be Ok with me :)

what are the things we'd need to do in order for this to live in JupyterHub? Would it require changing a lotta code?

(feel free to edit this list as new things come up)
Things to do if we move:

[ ] move dockerhub image to new name
[ ] update travis deploy scripts to push to new location on docker hub
[ ] update helm chart to pull from new dockerhub location

[ ] binderhub chart
[ ] mybidner.org deployment meta chart

[ ] check the docs don't mention the image/repo location

considering the fact that @betatim's list is a bit sizeable, and since nobody feels super strongly about moving the repo, I'm gonna close this issue since it doesn't seem something we need to act on soon. If somebody disagrees, feel free to re-open the issue!

Reopening this related to recent discussions regarding adoption of repos in the jupyterhub org (https://github.com/jupyterhub/team-compass/issues/315 , https://github.com/jupyterhub/team-compass/issues/313).
I will note that we don't need to update the dockerhub image to move the repo, which is the source of most of the friction. It's not a requirement that docker hub repos must match github ones. Since updating the image is the most costly part, I'd vote for moving the repo back to jupyterhub, but leaving the docker image alone. That leaves only these tasks:

[ ] update .travis.yml config triggers for deploy.on.repo
[ ] maybe update travis config, if secret values are lost after migration? Not sure if that will happen.
[ ] checking for links to the github repo in the docs, which is also low-impact, since there will be a redirect in place already.

I LIKE IT

update: added henchbot to task list

I'm definitely +1 on this, this conceptually trips me up every time I navigate to the r2d repo :-)

I wish we had moved this years ago to jupyterhub org. Going forward it makes good sense. Thanks!


Upload to play store error - NoMethodError: [!] undefined method `each_with_index' for nil:NilClass

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Good evening!
I'm trying to send one. aab for the track alpha.
However, when I try to send the file to the play store, through the "upload_to_play_store" it returns an error in ruby.
Just yesterday I sent a version and today the lane didn't work anymore.
Attachments:

Best Regards!
Command executed
upload_to_play_store
Complete output when running fastlane, including the stack trace and command used
See more
bundler: failed to load command: fastlane (/Users/vagrant/.rbenv/versions/2.6.5/bin/fastlane)
NoMethodError: [!] undefined method `each_with_index' for nil:NilClass
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:38:in `call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:18:in `evaluate'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:10:in `block in call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `each'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `inject'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/binding.rb:32:in `compile_fragment'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:53:in `block in call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:51:in `each'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:51:in `call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:70:in `representable_map!'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:45:in `create_representation_with'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/hash.rb:34:in `to_hash'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/serializer.rb:44:in `block in <module:Representable>'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:18:in `evaluate'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:10:in `block in call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `each'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `inject'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:39:in `block in call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:38:in `each'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:38:in `each_with_index'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:38:in `call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:18:in `evaluate'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:10:in `block in call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `each'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `inject'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/binding.rb:32:in `compile_fragment'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:53:in `block in call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:51:in `each'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:51:in `call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:70:in `representable_map!'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:45:in `create_representation_with'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/hash.rb:34:in `to_hash'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/json.rb:44:in `to_json'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/google-apis-core-0.3.0/lib/google/apis/core/api_command.rb:81:in `prepare!'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/google-apis-core-0.3.0/lib/google/apis/core/http_command.rb:99:in `execute'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/google-apis-core-0.3.0/lib/google/apis/core/base_service.rb:377:in `execute_or_queue_command'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/google-api-client-0.38.0/generated/google/apis/androidpublisher_v3/service.rb:1540:in `update_edit_track'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/supply/lib/supply/client.rb:389:in `block in update_track'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/supply/lib/supply/client.rb:81:in `call_google_api'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/supply/lib/supply/client.rb:388:in `update_track'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/supply/lib/supply/uploader.rb:412:in `update_track'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/supply/lib/supply/uploader.rb:22:in `perform_upload'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/actions/upload_to_play_store.rb:33:in `run'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
  Fastfile:34:in `block (2 levels) in parsing_binding'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/lane.rb:33:in `call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/commands_generator.rb:352:in `run'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in `take_off'
  /Users/vagrant/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/fastlane-2.176.0/bin/fastlane:23:in `<top (required)>'
  /Users/vagrant/.rbenv/versions/2.6.5/bin/fastlane:23:in `load'
  /Users/vagrant/.rbenv/versions/2.6.5/bin/fastlane:23:in `<top (required)>'

Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
11.2.2

Ruby
2.6.3

Bundler?
false

Git
git version 2.24.3 (Apple Git-128)

Installation Source
/usr/local/bin/fastlane

Host
macOS 11.2.2 (20D80)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib

OpenSSL Version
LibreSSL 2.8.3

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
12.4

System Locale

Variable
Value

LANG
pt_BR.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
default_platform(:android)

platform :android do
   desc 'Push a new build to Play Store as Beta'
  lane :beta do
    download_from_play_store(
      package_name: ENV['PACKAGE_NAME'],
    )

    upload_to_play_store(
      package_name: ENV['SUPPLY_PACKAGE_NAME'],
      track: 'alpha',
      aab: ENV['BITRISE_AAB_PATH'],
      metadata_path: "./fastlane/metadata/android"
    )
  end

end

`./fastlane/Appfile`

fastlane gems

Gem
Version
Update-Status

fastlane
2.178.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

slack-notifier
2.3.2

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

public_suffix
4.0.6

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

artifactory
3.0.15

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

gh_inspector
1.1.3

rubyzip
2.3.0

security
0.1.3

dotenv
2.7.6

bundler
2.1.4

simctl
1.6.8

jwt
2.2.2

uber
0.1.0

declarative
0.0.20

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

httpclient
2.8.3

google-api-client
0.38.0

nanaimo
0.3.0

colored2
3.1.2

claide
1.0.3

CFPropertyList
3.0.3

atomos
0.1.3

xcodeproj
1.19.0

plist
3.6.0

babosa
1.0.4

excon
0.79.0

ruby2_keywords
0.0.4

faraday-net_http
1.0.1

faraday
1.3.0

fastimage
2.2.3

json
2.5.1

mini_magick
4.11.0

naturally
2.2.1

xcpretty-travis-formatter
1.0.1

declarative-option
0.1.1

multi_json
1.15.0

signet
0.15.0

os
1.1.1

memoist
0.16.2

googleauth
0.16.0

rake
13.0.3

digest-crc
0.6.3

webrick
1.7.0

rexml
3.2.4

google-apis-core
0.3.0

google-apis-storage_v1
0.3.0

google-apis-iamcredentials_v1
0.2.0

google-cloud-errors
1.1.0

google-cloud-env
1.5.0

google-cloud-core
1.6.0

google-cloud-storage
1.31.0

emoji_regex
3.2.2

aws-eventstream
1.1.1

aws-sigv4
1.2.3

aws-partitions
1.433.0

jmespath
1.4.0

aws-sdk-core
3.113.0

aws-sdk-kms
1.43.0

aws-sdk-s3
1.91.0

forwardable
1.2.0

logger
1.3.0

date
2.0.0

stringio
0.0.2

zlib
1.0.0

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

strscan
1.0.0

fileutils
1.1.0

etc
1.0.1

io-console
0.4.7

libxml-ruby
3.1.0

psych
3.1.0

mutex_m
0.1.0

generated on: 2021-03-16

I'm also experiencing this issue.

I'm also experiencing this issue.

I'm also experiencing this issue.

#METOO

I'm also experiencing this issue.

I'm also experiencing this issue.

me too

I'm also experiencing this issue.

Does anyone have more information on why this issue is happening?

I am also experiencing this issue

Same here.
upload_to_play_store(track: 'internal') in GitHub Actions throws an error since a few hours.
|             fastlane summary              |
+------+----------------------+-------------+
| Step | Action               | Time (in s) |
+------+----------------------+-------------+
| 1    | clean                | 49          |
| 2    | assembleRelease      | 333         |
| 💥   | upload_to_play_store | 5           |
+------+----------------------+-------------+

[20:58:54]: fastlane finished with errors

Looking for related GitHub issues on fastlane/fastlane...

➡  Upload to play store error - NoMethodError: [!] undefined method `each_with_index' for nil:NilClass
    https://github.com/fastlane/fastlane/issues/18403 [open] 10 💬
    7 minutes ago

➡  "Could not store password in keychain"
    https://github.com/fastlane/fastlane/issues/18223 [open] 2 💬
    4 weeks ago

➡  Error running `screenshots` command - latest_simulator_version_for_device: undefined method `os_version' for nil:NilClass
    https://github.com/fastlane/fastlane/issues/17894 [closed] 2 💬
    a week ago

and 7 more at: https://github.com/fastlane/fastlane/search?q=undefined%20method%20%60each_with_index%27%20for%20nil&type=Issues&utf8=✓

/opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:38:in `call': [!] undefined method `each_with_index' for nil:NilClass (NoMethodError)
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:18:in `evaluate'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:10:in `block in call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `each'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `inject'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/binding.rb:32:in `compile_fragment'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:53:in `block in call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:51:in `each'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:51:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:70:in `representable_map!'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:45:in `create_representation_with'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/hash.rb:34:in `to_hash'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/serializer.rb:44:in `block in <module:Representable>'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:18:in `evaluate'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:10:in `block in call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `each'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `inject'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:39:in `block in call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:38:in `each'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:38:in `each_with_index'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:38:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:18:in `evaluate'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:10:in `block in call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `each'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `inject'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/binding.rb:32:in `compile_fragment'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:53:in `block in call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:51:in `each'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:51:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:70:in `representable_map!'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:45:in `create_representation_with'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/hash.rb:34:in `to_hash'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/json.rb:44:in `to_json'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/google-api-client-0.38.0/lib/google/apis/core/api_command.rb:69:in `prepare!'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/google-api-client-0.38.0/lib/google/apis/core/http_command.rb:99:in `execute'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/google-api-client-0.38.0/lib/google/apis/core/base_service.rb:360:in `execute_or_queue_command'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/google-api-client-0.38.0/generated/google/apis/androidpublisher_v3/service.rb:1540:in `update_edit_track'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/supply/lib/supply/client.rb:389:in `block in update_track'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/supply/lib/supply/client.rb:81:in `call_google_api'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/supply/lib/supply/client.rb:388:in `update_track'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/supply/lib/supply/uploader.rb:412:in `update_track'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/supply/lib/supply/uploader.rb:22:in `perform_upload'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/actions/upload_to_play_store.rb:33:in `run'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
	from Fastfile:252:in `block (2 levels) in parsing_binding'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/commands_generator.rb:352:in `run'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in `take_off'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/bin/fastlane:23:in `<top (required)>'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/bin/fastlane:23:in `load'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/bin/fastlane:23:in `<main>'
/opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:38:in `call': undefined method `each_with_index' for nil:NilClass (NoMethodError)
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:18:in `evaluate'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:10:in `block in call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `each'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `inject'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/binding.rb:32:in `compile_fragment'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:53:in `block in call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:51:in `each'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:51:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:70:in `representable_map!'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:45:in `create_representation_with'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/hash.rb:34:in `to_hash'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/serializer.rb:44:in `block in <module:Representable>'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:18:in `evaluate'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:10:in `block in call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `each'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `inject'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:39:in `block in call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:38:in `each'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:38:in `each_with_index'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:38:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:18:in `evaluate'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:10:in `block in call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `each'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `inject'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/pipeline.rb:9:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/binding.rb:32:in `compile_fragment'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:53:in `block in call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:51:in `each'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:51:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:70:in `representable_map!'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable.rb:45:in `create_representation_with'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/hash.rb:34:in `to_hash'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/representable-3.0.4/lib/representable/json.rb:44:in `to_json'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/google-api-client-0.38.0/lib/google/apis/core/api_command.rb:69:in `prepare!'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/google-api-client-0.38.0/lib/google/apis/core/http_command.rb:99:in `execute'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/google-api-client-0.38.0/lib/google/apis/core/base_service.rb:360:in `execute_or_queue_command'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/google-api-client-0.38.0/generated/google/apis/androidpublisher_v3/service.rb:1540:in `update_edit_track'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/supply/lib/supply/client.rb:389:in `block in update_track'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/supply/lib/supply/client.rb:81:in `call_google_api'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/supply/lib/supply/client.rb:388:in `update_track'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/supply/lib/supply/uploader.rb:412:in `update_track'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/supply/lib/supply/uploader.rb:22:in `perform_upload'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/actions/upload_to_play_store.rb:33:in `run'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
	from Fastfile:252:in `block (2 levels) in parsing_binding'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/commands_generator.rb:352:in `run'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in `take_off'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/lib/ruby/gems/2.6.0/gems/fastlane-2.178.0/bin/fastlane:23:in `<top (required)>'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/bin/fastlane:23:in `load'
	from /opt/hostedtoolcache/Ruby/2.6.6/x64/bin/fastlane:23:in `<main>'
Error: Process completed with exit code 1.```

Same here.

I also get this when I try to bundle exec fastlane supply --aab build_output/release/app-release.aab --track internal.
This has been driving me crazy, as it was working earlier.

Don't see any red flags here but has to be regression.
Google Release notes for March 15, 2021
Updates the Google Mobile Ads Android SDK and Firebase Ads SDK. For more information, refer to the product release notes.
Artifacts released on maven.google.com
com.google.android.gms:play-services-ads:19.8.0
com.google.android.gms:play-services-ads-lite:19.8.0
com.google.firebase:firebase-ads:19.8.0
com.google.firebase:firebase-ads-lite:19.8.0
19.8.0 | 2021‑03‑15 | Added a dependency on the User Messaging Platform SDK.Added the onAdImpression() callback to FullScreenContentCallback.Deprecated the InstreamAd format.Mediation Adapters:Deprecated MediationBannerAdapter, MediationInterstitialAdapter, and MediationNativeAdapter. New adapters should implement the Adapter class to load these formats.Note: These deprecated mediation adapter classes won't be removed in version 20.0.0 in order to give mediation adapters time to transition to the new API.Open Bidding adapters can now implement distinct load methods in the Adapter class for RTB-specific formats.

It happened to me after updating fastlane to the latest:
Installing fastlane 2.178.0 (was 2.177.0)
I could upload to the internal lane 15 minutes ago with version 2.177.0, I cannot any more with version 2.178.0

I'm also experiencing this issue :(

Same here :/

I have found the culprit.
I have been looking at dependencies updated today, and since everything seemed to revolve around representable, I discovered that declarative-option had an update today from 0.1.0 to 0.1.1.
I am guessing that those who experience this does not use a Gemfile.lock and possibly not a Gemfile.
The solution is to create a Gemfile with the following content:
source "https://rubygems.org"

gem "fastlane"

Install with the following commands:
$ gem install bundler
$ bundle install

Then open Gemfile.lock and change declarative-option (0.1.1) to declarative-option (0.1.0) and run bundle install again.

I have found the culprit.
I have been looking at dependencies updated today, and since everything seemed to revolve around representable, I discovered that declarative-option had an update today from 0.1.0 to 0.1.1.
I am guessing that those who experience this does not use a Gemfile.lock and possibly not a Gemfile.
The solution is to create a Gemfile with the following content:
source "https://rubygems.org"

gem "fastlane"

Install with the following commands:
$ gem install bundler
$ bundle install

Then open Gemfile.lock and change declarative-option (0.1.1) to declarative-option (0.1.0) and run bundle install again.
Add Gemfile.lock to your repository so others don't have to create it again.

I just create a Gemfile with the content:
source "https://rubygems.org"

gem "declarative-option", "0.1.0"
gem "fastlane", "2.177.0"

It worked as a workaround for now.

I also get this when I try to bundle exec fastlane supply --aab build_output/release/app-release.aab --track internal.
This has been driving me crazy, as it was working earlier.

Same here. I did not update anything. This was working fine since long time ago. Locally it works fine but in my CI, fails with this error.

Ran into the same issue as well. Ironically, immediately after resolving an iOS build issue, the Android build issue promptly broke. Builds, eh? 🙄
Same issue as everyone else. Seems to be rooted in the representable library. We tried a Gemfile...but, for some reason we still seem to be having the same error in our CircleCI build environment.

I have found the culprit.
I have been looking at dependencies updated today, and since everything seemed to revolve around representable, I discovered that declarative-option had an update today from 0.1.0 to 0.1.1.
I am guessing that those who experience this does not use a Gemfile.lock and possibly not a Gemfile.
The solution is to create a Gemfile with the following content:
source "https://rubygems.org"

gem "fastlane"

Install with the following commands:
$ gem install bundler
$ bundle install

Then open Gemfile.lock and change declarative-option (0.1.1) to declarative-option (0.1.0) and run bundle install again.
It should be obvious, but: Add Gemfile.lock to your repository so installation is just the above two commands henceforth.

For me this worked, seems the issue was as you described.

@jrista Read my comment above. You also need Gemfile.lock

JoseFMP for the win! Downgrade declarative-option gem to 0.1.0 and all is good. If there is a bug logged with that gem repo maintainer please cross link here.

The solution up there didnt work for me :(

The solution listed above did not work for me as I already had a Gemfile.lock - however on re running my CI pipeline this morning with no changes, it successfully uploaded to the play store without issue.

The solution listed above did not work for me as I already had a Gemfile.lock - however on re running my CI pipeline this morning with no changes, it successfully uploaded to the play store without issue.

Hi @AlexHooperDev,
Try to add in Gemfile the content:
source "https://rubygems.org"

gem "declarative-option", "0.1.0"
gem "fastlane", "2.177.0"

It worked for me as a workaround.

This solution didnt work too

@

This solution didnt work too

Hi @goxodev,
Please, try to remove the old Gemfile.lock before run the command bundle install

Again the same error...

Any solution more?

Again the same error...

@goxodev
Show us the bundle install console output, please.

Same issue happening with me. Console output for bundle install is as follows:

Using rake 13.0.3

Using CFPropertyList 3.0.3

Using concurrent-ruby 1.1.8

Using i18n 1.8.9

Using minitest 5.14.4

Using thread_safe 0.3.6

Using tzinfo 1.2.9

Using activesupport <IP_ADDRESS>

Using public_suffix 4.0.6

Using addressable 2.7.0

Using httpclient 2.8.3

Using json 2.5.1

Using algoliasearch 1.27.5

Using rubyzip 2.3.0

Using apktools 0.7.4

Using artifactory 3.0.15

Using atomos 0.1.3

Using aws-eventstream 1.1.1

Using aws-partitions 1.433.0

Using aws-sigv4 1.2.3

Using jmespath 1.4.0

Using aws-sdk-core 3.113.0

Using aws-sdk-kms 1.43.0

Using aws-sdk-s3 1.91.0

Using babosa 1.0.4

Using bundler 2.2.8

Using claide 1.0.3

Using fuzzy_match 2.0.4

Using nap 1.1.0

Using netrc 0.11.0

Using ffi 1.15.0

Using ethon 0.12.0

Using typhoeus 1.4.0

Using cocoapods-core 1.10.1

Using cocoapods-deintegrate 1.0.4

Using cocoapods-downloader 1.4.0

Using cocoapods-plugins 1.0.0

Using cocoapods-search 1.0.0

Using cocoapods-trunk 1.5.0

Using cocoapods-try 1.2.0

Using colored2 3.1.2

Using escape 0.0.4

Using fourflusher 2.3.1

Using gh_inspector 1.1.3

Using molinillo 0.6.6

Using ruby-macho 1.4.0

Using nanaimo 0.3.0

Using xcodeproj 1.19.0

Using cocoapods 1.10.1

Using colored 1.2

Using highline 1.7.10

Using commander-fastlane 4.4.6

Using declarative 0.0.20

Using declarative-option 0.1.1

Using digest-crc 0.6.3

Using unf_ext <IP_ADDRESS>

Using unf 0.1.4

Using domain_name 0.5.20190701

Using dotenv 2.7.6

Using emoji_regex 3.2.2

Using excon 0.79.0

Using faraday-net_http 1.0.1

Using multipart-post 2.0.0

Using ruby2_keywords 0.0.4

Using faraday 1.3.0

Using http-cookie 1.0.3

Using faraday-cookie_jar 0.0.7

Using faraday_middleware 1.0.0

Using fastimage 2.2.3

Using jwt 2.2.2

Using memoist 0.16.2

Using multi_json 1.15.0

Using os 1.1.1

Using signet 0.15.0

Using googleauth 0.16.0

Using mini_mime 1.0.2

Using uber 0.1.0

Using representable 3.0.4

Using retriable 3.1.2

Using google-api-client 0.38.0

Using rexml 3.2.4

Using webrick 1.7.0

Using google-apis-core 0.3.0

Using google-apis-iamcredentials_v1 0.2.0

Using google-apis-storage_v1 0.3.0

Using google-cloud-env 1.5.0

Using google-cloud-errors 1.1.0

Using google-cloud-core 1.6.0

Using google-cloud-storage 1.31.0

Using mini_magick 4.11.0

Using naturally 2.2.1

Using plist 3.6.0

Using security 0.1.3

Using simctl 1.6.8

Using slack-notifier 2.3.2

Using terminal-notifier 2.0.0

Using unicode-display_width 1.7.0

Using terminal-table 1.8.0

Using tty-screen 0.8.1

Using tty-cursor 0.7.1

Using tty-spinner 0.9.3

Using word_wrap 1.0.0

Using rouge 2.0.7

Using xcpretty 0.3.0

Using xcpretty-travis-formatter 1.0.1

Using fastlane 2.178.0

Using mime-types-data 3.2021.0225

Using mime-types 3.3.1

Using fastlane-plugin-aws_s3 1.8.0

Using fastlane-plugin-firebase_app_distribution 0.2.5

Using fastlane-plugin-unity 1.1.2

Using fastlane-plugin-update_provisioning_profile_specifier 1.3.1

Bundle complete! 6 Gemfile dependencies, 112 gems now installed.

Use `bundle info [gemname]` to see where a bundled gem is installed.

@galalmounir your output states that you get declarative-option version 0.1.1 and you need to force version 0.1.0. If you didn't already make a Gemfile.lock, read my comment above on how to.

Using declarative-option 0.1.1
Using fastlane 2.178.0

Hi, @galalmounir
Did you run the bundle installcommand in the Gemfile's path and removed the Gemfile.lock file?

Update: The faulty version has been removed and they are working on a fix. See https://github.com/apotonick/declarative-option/issues/6#issuecomment-801098877.

Using declarative-option 0.1.1
Using fastlane 2.178.0

Hi, @galalmounir
Did you run the bundle installcommand in the Gemfile's path and removed the Gemfile.lock file?

I did, yes.
I think I got it to work after also forcing the fastlane version to 2.177.0

Having the same issue. The solution above didn't work for me

@galalmounir how did you force it to turn back to 2.177?
I changed the version in my Gemfile
source 'https://rubygems.org'
gem 'fastlane', '= 2.177'
Then I did bundle install. It said that fastlane 2.177 was installed. But when I run my lane it still uses 2.178

@galalmounir how did you force it to turn back to 2.177?
I changed the version in my Gemfile and Gemfile.lock
source 'https://rubygems.org'
gem 'fastlane', '= 2.177'
Then I did bundle install. It said that fastlane 2.177 was installed. But when I run my lane it still uses 2.178

I deleted the Gemfile.lock and change the fastlane version in the Gemfile to 2.177.0. Then ran bundle install.
I would say when running your lane, make sure you are running the correct fastlane version.
Are you using fastlane directly or bundle exec fastlane?

@galalmounir I run fastlane directly

@galalmounir I followed your advice and ran the lane with bundle exec fastlane and it helped to solve fastlane version issue.
But I am getting this error now

@galalmounir I followed your advice and ran the lane with bundle exec fastlane and it helped to solve fastlane version issue.
But I am getting this error now

@galalmounir we ran into this same issue just a little bit ago, and we had to log into the google developer console and let google know that our app was not a news app (they are preventing releases until they have this knowledge).
There should be an alert once you are logged into the google play console. Once we resolved that, our release worked!
I hope this helps.

@galalmounir I followed your advice and ran the lane with bundle exec fastlane and it helped to solve fastlane version issue.
But I am getting this error now

@nbaryshev we ran into this same issue just a little bit ago, and we had to log into the google developer console and let google know that our app was not a news app (they are preventing releases until they have this knowledge).
There should be an alert once you are logged into the google play console. Once we resolved that, our release worked!
I hope this helps.

The same thing happened to us. I wish I had seen your answer 3 hours ago. 😄
Telling google that the app is not a news app should do the trick.

The solution listed above did not work for me as I already had a Gemfile.lock - however on re running my CI pipeline this morning with no changes, it successfully uploaded to the play store without issue.

Hi @AlexHooperDev,
Try to add in Gemfile the content:
source "https://rubygems.org"

gem "declarative-option", "0.1.0"
gem "fastlane", "2.177.0"

It worked for me as a workaround.

I tried this earlier this morning, and it worked for me. Specifically adding the declarative-option package at the right version did the trick. I had a Gemfile.lock before as well, and until I specifically set the version for declarative-option, it seemed to keep locking 0.1.1.

any more solutions? I have changed the fastlane version and the declarative option with the Gemfile.lock removed.
This doesnt work for me

Doesn't work for me too...

Shout out to @beruic and everyone else that helped figuring things out! 💪 🎉
Since they reverted the release back to 0.1.0 https://github.com/apotonick/declarative-option/issues/6#issuecomment-801098877 as you can check here https://github.com/apotonick/declarative-option/releases, this issue has likely been resolved. Just make sure you update your environment dependencies so the latest version reverts from 0.1.1 to 0.1.0 properly.
I'm closing this issue as I confirmed locally that the broken dependency version is no longer being installed or fetched  👍

This is still broken

I am still having the issue too. I fixed declarative-option to 0.1.1 and reverted this but the problem is still the same...
My CI does bundle update fastlane and while inspecting... I still see
...
Using declarative-option 0.1.1 (was 0.1.0)
...

How is this possible?

@MoOx You need to delete the gem cache from your machine as well by running gem uninstall declarative-option --version 0.1.1

This solution is working for me:
touch Gemfile
with:
source "https://rubygems.org"
gem "declarative-option", "0.1.0"
gem "fastlane", "2.177.0"

bundle install
Run fastlane upload (my example):
bundle exec fastlane supply --apk *.apk --track internal --package_name you.id.here --rollout 1.0 --json_key you.file.here.json

Thanks @b3hni4 this helped me resolving my problem.
Pinning the version in the Gemfile wasn't enough in my case, it always picked up declarative-option 0.1.1!


Peer review picture blank in limited connection mode

Limited mode should either remove peer review from the menu, or load the pic under review (it is not that big)

can i work on this issue

@nicolas-raoul  can i work on this issue

@nicolas-raoul I'm new to contributing to wikimedia and would love to take this up as my first issue. Can this issue be assigned to me?

Prince, Ankita: This issue is quite hard, it will require some policy decisions. I would suggest finding another issue at https://github.com/commons-app/apps-android-commons/issues?utf8=✓&q=is%3Aopen+is%3Aissue+no%3Aassignee+-label%3Aassigned+-label%3Adebated+label%3Abug ? Thanks!

I think removing Peer Review from the menu during limited connection mode would be the best solution, what do you think @sivaraam @nicolas-raoul ?

In my personal opinion, loading a miniature of 1 picture (I mean 1 by 1) is OK in limited connection, especially since opening Peer Review is voluntary.
But I totally agree with removing the menu entry until someone wants to implement that :-)

@nicolas-raoul Can I work on this?

@mrudultora It is yours, thanks!
What approach will you take?

@nicolas-raoul I am removing peer review from bottom sheet menu if the user is in limited connection mode. Is it fine ?

@mrudultora Sounds good :-)


Property value incorrectly if using both of static properties() and @property decorator

Description
Lit-Element handle properties value incorrectly if using both of static properties() and @property decorator for create element extends from abstract class.
I think this problem is related with

abstract class no need to use @customElement
use static properties() in abstract class
use @property in child class

Live Demo
https://stackblitz.com/edit/lit-element-properties-problem?file=my-element.ts
Steps to Reproduce by using TypeScript

Create abstract class BaseElement

// not define element @customElement because this is abstract class
abstract class BaseElement extends LitElement {

  public foo = false;

  // (I don't use  @property because I have to import properties from share properties)
  static get properties() {
    return {
      foo: { type: Boolean, reflect: true }
    };
  }

  render(){
    return html`<p>${this.foo}</p>`;
  }
}

Create MyElement

@customElement('my-element')
export class MyElement extends BaseElement {
  /**
   * Create new property with @property
   * Using this make a problem with static properties().
   * Remove this property and reload by click refresh button to get correct value
   */
  @property() bar = 'bar';
}

Use element and set foo attribute is true

<my-element foo></my-element>

Expected Results
foo property value and element render should be true
Actual Results
foo property value and element render is false
Browsers Affected

[x] Chrome
[x] Firefox
[x] Edge
[x] Safari 13
[x] IE 11

Versions

lit-element: v2.2.1
webcomponents: v2.4.1

+1

Status: This has been fixed in the lit-next branch, but is still an open bug on master (lit-element 2.x).


Push new version with fixes?

Will you push a new version to npm with the new commits? The last push to npm was February 25, 2016.
Thank you.

Also, when installing the library from npm, we get the below issue. It will be great if you can fix the version of the peer-dependencies.
├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  ├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>

Just update a version with peer dependency on latest react (v15.1.0)

react-month-picker 1.0.10 is not compatible with react 15.1.0.
In our project we had required month-picker with ^10.0.8, so we found out the hard way.

Can confirm what severlsw says.  Right now there is no version of the latest code that works with React 15.x that I could determine.  Chrome complains 'cannot read property createClass (month-picker.js: 78) of undefined.
I got:
react-month-picker 1.0.3
react-tapper 0.1.3
to work with react 0.14.x but this lacks many of the recent fixes.

I'm using react v15.1.0 and react-month-picker v1.0.10 in my project, and it works fine. Can I ask what exactly error shown in your browser, @severisv ?

@alee8  line 70 in lib/month-picker.js:
var MonthPicker = _react2.default.createClass({...
The relevant code line in original JSX file:
let MonthPicker = React.createClass({..
If you include react.js in your project correctly, I don't think there will be a problem here. Actually, you can see the example page of react-month-picker works fine also.

Or can you give more specific details of the problem?

I tried something more basic.  I pulled a copy of the code.
I did a 'npm install' and this is what I got at the end of this.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

Are you using<EMAIL_ADDRESS>or lower version?
You can use<EMAIL_ADDRESS>which doesn’t warn your to require packages as peer dependencies.
OR, you may install<EMAIL_ADDRESS>&<EMAIL_ADDRESS>by yourself with npm to stop the warning.

When I ran npm, it was version 3.8.8.
I can install<EMAIL_ADDRESS>and<EMAIL_ADDRESS>in the source directory. How would you suggest running react-month-picker standalone (say your example)? This was what I was aiming for when I downloaded and did the npm install.
When I included react-month-picker in my React app, I needed to add browserify-shim (v3.8.12) because it was not installed.  Other than that, I just included react-month-picker.  Note, I referenced month-picker.js:78 because my react app loaded lib/month-picker.js via require('react-month-picker"').default  My react app uses babelify and react-month-picker uses browserify-shim (any potential of conflict?).

@alee8
no no no, react-month-picker does not require browserify-shim, and it's optional. Besides, I do not use browserify-shim either, and there is no warning for browserify-shim when I install the package by npm.
React-month-picker is compiled by babel, not browserify. It's not wrong if you load the component via requires('...').default, and I tried it too.
Can I ask how you include react and react-dom into your app? I don't know if there is any issue here, just ask, since I tried everything you mentioned before, and all work fine.
The error you listed, "cannot read property createClass (month-picker.js: 78) of undefined", apparently, refers to your React component not loaded correctly.
Just FYI:
In my app, I usually load react components via es6 syntax 'import', but 'require' syntax also works, and load react & react-dom in separate files instead of packing all stuff into one file. Then, I pack the app.js with webpack. Since react & react-dom are external components in my app, my webpack config must include a setting a following:
    ...
    ,externals: {
        'react': 'React'
        , 'react-dom': 'ReactDOM'
    }
   ...

@alee8
I figured out one.
Yes, if you include react-month-picker in dependencies or devDependencies of your project, you have to include react & react-dom in dependencies or devDependencies too, or install them manually, coz react-month-picker requires a peer dependency on react & react-dom.
BUT, it's not the cause for the error you mentioned ('cannot read property createClass (month-picker.js: 78) of undefined'). That error is caused by loading react & react-dom unsuccessfully.

I have the same error ('cannot read property createClass of undefined').
package.json:
"dependencies": {
.......
"react": "^15.1.0",
"react-dom": "^15.1.0",
"react-month-picker": "1.0.10",
},
We are build our bundle with browserify and we are also running babel with presets: ["es2015", "react"] and plugins: ["transform-object-rest-spread", "jsx-control-statements"].
We have separate bundles for our libraries and our own code, and react-month-picker is not in the same bundle as react and react-dom, which might be the cause. I will try to put them in the same bundle and see if it helps, but I don't have time to verify right now.
Our setup works with react 15 and month-picker 1.0.8.

@severisv
I haven't used browserify before. That patch in package.json for browserify came from @bcherny.
The patch configuration as following:
"browserify": {
    "transform": [
      "browserify-shim"
    ]
  },
  "browserify-shim": {
    "react": "global:React"
  },

But the patch wasn't published to npm until 1.0.10.
I wonder if there is any conflict configuration here with yours. If there is, please notify me.

We are using browserify-shim, but we haven't shimmed React, and we don't see a good reason to do it either.
This is our setup:
gulp js
package.json

Sorry to disappear from the grid.  Had something else that was more pressing to deal with.
Now that I return to this, I can add:
a) My app that includes your component does not build bundles.
b) My app includes your component in my package.json's dependencies.
c) My app included react and react-dom in my package.json's dependencies
d) My app uses browserify with babelify transform.  Your component has browserify-shim which may clash with my app's browserify transform.  As detailed above, I have to add browserify-shim my package.json's dependencies; otherwise the app does not load.
e) As indicated above, the only version that will work with react 0.14.x is<EMAIL_ADDRESS>with<EMAIL_ADDRESS> I have tried to switch my app to react 15.1.0 and include 1.0.8/1.0.10 and get error 'Uncaught TypeError: Cannot read property 'createClass' of undefined'.
If you can produce a version 1.1.0 that does not have the following, I can try to see if the react 15.1.0 version of my app can use this 1.1.0 of your component.
"browserify": {
"transform": [
"browserify-shim"
]
},
"browserify-shim": {
"react": "global:React"
},
It also appears that the versioning of react-tapper is not properly sync'ed with react-month-picker so that my react 0.14.x can use an earlier version of react-month-picker (but later than 1.0.3) without the browserify-shim add-ins.
Let me know if you would be willing to explore a 1.1.0 version (matched properly with react-tapper version) for use with react 15.1.0 app.

@alee8 removed browserify-shim configuration from package.json and publish v1.0.11. Please test it.
Next time I will test it before merging.

Would be happy to try it once it publishes?  Don't see it yet.

This is my bad -- sorry it took so long to comment. @nickeljew please roll back my PR https://github.com/nickeljew/react-month-picker/commit/7b38d6bc3622b7f91183f208dc30cb4788838bfb.
I was trying to get React-Month-Picker working with a CDN'd React. However, the code in that PR prevents React-Month-Picker from working with a non-CDN'd React if the project uses browserify-shim!
The fix is to revert that commit and publish a new version.
I also made a demo repo for anyone that wants to get React-Month-Picker working with CDN'd (or non-CDN'd React) with browserify in the future: https://github.com/bcherny/react-month-picker-demo/blob/master/package.json.

I can confirm that v1.0.11 works correctly.


Deployment fails on Azure Database for PostgreSQL flexible server

Observed Behaviour
The deployment fails/hangs for the external DB specified over https://github.com/eclipse-tractusx/sldt-digital-twin-registry/blob/366970100962a3532f1d8dd2bb4be1ecdaea5674/charts/registry/values.yaml#L54C1-L61C17
with log patern like below:
2023-09-13T13:50:52.704Z  INFO 1 --- [           main] o.e.t.semantics.RegistryApplication      : Starting RegistryApplication vDEV-SNAPSHOT using Java <IP_ADDRESS> with PID 1 (/service/app.jar started by spring in /service)
2023-09-13T13:50:52.707Z  INFO 1 --- [           main] o.e.t.semantics.RegistryApplication      : The following 1 profile is active: "local"
2023-09-13T13:50:57.993Z  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
2023-09-13T13:50:58.302Z  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 287 ms. Found 3 JPA repository interfaces.
2023-09-13T13:51:01.493Z  INFO 1 --- [           main] o.s.b.w.e.j.JettyServletWebServerFactory : Server initialized with port: 4243
2023-09-13T13:51:01.498Z  INFO 1 --- [           main] org.eclipse.jetty.server.Server          : jetty-11.0.15; built: 2023-04-11T18:37:53.775Z; git: 5bc5e562c8d05c5862505aebe5cf83a61bdbcb96; jvm <IP_ADDRESS>+1
2023-09-13T13:51:01.709Z  INFO 1 --- [           main] o.e.j.s.h.ContextHandler.application     : Initializing Spring embedded WebApplicationContext
2023-09-13T13:51:01.710Z  INFO 1 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 8720 ms
2023-09-13T13:51:03.707Z  INFO 1 --- [           main] o.e.j.s.session.DefaultSessionIdManager  : Session workerName=node0
2023-09-13T13:51:03.789Z  INFO 1 --- [           main] o.e.jetty.server.handler.ContextHandler  : Started o.s.b.w.e.j.JettyEmbeddedWebAppContext@aa21042{application,/,[file:///tmp/jetty-docbase.4243.12607937777430990090/, jar:file:/service/app.jar!/BOOT-INF/lib/swagger-ui-4.15.5.jar!/META-INF/resources],AVAILABLE}
2023-09-13T13:51:03.799Z  INFO 1 --- [           main] org.eclipse.jetty.server.Server          : Started Server@77b7ffa4{STARTING}[11.0.15,sto=0] @15523ms
2023-09-13T13:51:04.202Z  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
2023-09-13T13:51:05.592Z  INFO 1 --- [           main] com.zaxxer.hikari.pool.HikariPool        : HikariPool-1 - Added connection org.postgresql.jdbc.PgConnection@328902d5
2023-09-13T13:51:05.595Z  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
2023-09-13T13:51:06.406Z  INFO 1 --- [           main] liquibase.database                       : Set default schema name to public
2023-09-13T13:51:07.792Z  INFO 1 --- [           main] liquibase.changelog                      : Reading from public.databasechangelog
2023-09-13T13:51:07.802Z  INFO 1 --- [           main] liquibase.executor                       : Changelog query completed.
2023-09-13T13:51:08.599Z  INFO 1 --- [           main] liquibase.executor                       : Changelog query completed.
2023-09-13T13:51:08.603Z  INFO 1 --- [           main] liquibase.executor                       : Changelog query completed.
2023-09-13T13:51:08.610Z  INFO 1 --- [           main] liquibase.lockservice                    : Waiting for changelog lock....
2023-09-13T13:51:18.621Z  INFO 1 --- [           main] liquibase.executor                       : Changelog query completed.
2023-09-13T13:51:18.624Z  INFO 1 --- [           main] liquibase.executor                       : Changelog query completed.
2023-09-13T13:51:18.636Z  INFO 1 --- [           main] liquibase.executor                       : Changelog query completed.
2023-09-13T13:51:18.640Z  INFO 1 --- [           main] liquibase.lockservice                    : Successfully acquired change log lock
2023-09-13T13:51:18.712Z  INFO 1 --- [           main] liquibase.executor                       : Changelog query completed.
2023-09-13T13:51:18.778Z  INFO 1 --- [           main] liquibase.changelog                      : Reading from public.databasechangelog
2023-09-13T13:51:18.781Z  INFO 1 --- [           main] liquibase.executor                       : Changelog query completed.
2023-09-13T13:51:18.788Z  INFO 1 --- [           main] liquibase.executor                       : Changelog query completed.

Cause of the Problem
The application requires additional extension https://www.postgresql.org/docs/12/uuid-ossp.html which is by some means part of the bitnami chart/image. This extension is not part out-of-the box for "Azure Database for PostgreSQL flexible server"
Solution
Activation of the extension  for "Azure Database for PostgreSQL flexible server" as described in https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-extensions
Documentation
A list of required PostgreSQL extensions has to be part of the documentation

Thanks for pointing out this. We will check this.

PR is created.
https://github.com/eclipse-tractusx/sldt-digital-twin-registry/pull/453

Done. Issue will be closed.


Kabanero namespace left hanging in terminating state

I installed a Kabanero 0.6.0 operator from https://github.com/kabanero-io/kabanero-operator/releases and deployed Codeready for playing around with Codewind. If you're curious, you can refer to docs https://kabanero.io/docs/ref/general/installation/installing-codeready-and-codewind.html on how to do this.
When I was done with the namespace, I wanted to take down Codeready. So I just went ahead and deleted the namespace like oc delete project kabanero but it was left in a terminating state.
# kubectl get ns kabanero
NAME       STATUS        AGE
kabanero   Terminating   19d

I made sure no Kube resources were holding the deletion back with oc get all -n kabanero
# oc get all -n kabanero
No resources found.

Is there a way to list all the CRDs that the kabanero operator is using, to see what is holding the deletion of the namespace?
FWIW my Kabanero resource says
# oc get kabanero -n kabanero
NAME       AGE       VERSION   READY
kabanero   19d       0.6.0     False

Hi @maysunfaisal - in general, just deleting a project is a bad idea.  Some of the objects in there may have finalizers, that some other object removes.  If the object that removes the finalizer stops before the object with the finalizer, then you are stuck doing manual cleanup.
In this case, it's probably the kabanero instance that's holding things up.  It requires the kabanero-operator pod to remove its finalizer.  You can do oc get kabanero -n kabanero -o yaml and check the metadata section for any finalizers.  If there are any there, you can delete them using oc edit, deleting the finalizers section, and then saving.
The namespace should go away after that's gone.  If it doesn't, you could look at the yaml for the namespace and see if it has a finalizer too:  oc get namespace kabanero -o yaml.
For the future, please delete your Kabanero CR instances before you delete the project.  Or use the uninstall.sh script for the kabanero-operator.

@maysunfaisal I am going to close this issue - please re-open if you continue to have trouble with the uninstall script.  Thanks!


added documentation

I had to debug the framework just to find out that for proper scheduling the player may not be in the paused state.
Just added some comments

Thank you, every bit helps and I love documentation pull requests!


Fixes Terra-UI Build issues and linter warnings

Summary

Fixes terra-ui build issue : https://github.com/cerner/terra-ui/actions/runs/4758810667/jobs/8457428665
What was changed:
Change log title was corrected in terra-pills to match the existing change log formats and Added missing dependency of terra-worklist-data-grid is added 😆
Why it was changed:
Because of Typo in terra-pills/CHANGELOG.md this file was not bundled with package and it was missing from node_modules/@cerner/terra-pills/ folder. Since change log was not part of component folder terra-ui build started to fail with module not found error while running npm run build:production command.

Testing

Tested with tar.gz file terra-pills ( after typo correction ) in terra-ui to ensure<EMAIL_ADDRESS>is available.
This change was tested using:

[ ] WDIO
[ ] Jest
[ ] Visual testing (please attach a screenshot or recording)
[X] Other (please describe below)
[ ] No tests are needed

By running npm run build:production command on terra-ui
Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[ ] Accessibility review
[ ] Functional review

Additional Details

This PR resolves:
UXPLATFORM-XXXX

Thank you for contributing to Terra.
@cerner/terra

FYI, the terra-pills release should be fixed by https://github.com/cerner/terra-framework/pull/1666. We currently have https://github.com/cerner/terra-ui/pull/592 out to fix the build of terra-ui. The other changes in this PR look good though so we can keep it.

FYI, the terra-pills release should be fixed by #1666. We currently have cerner/terra-ui#592 out to fix the build of terra-ui. The other changes in this PR look good though so we can keep it.

is the build passing ?? and I don't think removing files from pills package.json will fix the build issue. have you tested terra-pill changes on terra-ui before merging PR #1666 ..??

is the build passing ?? and I don't think removing files from pills package.json will fix the build issue. was the code changes made on terra-pill tested on terra-ui before merging PR #1666 ..??

Yeah, here is a link to the build:
https://github.com/cerner/terra-ui/actions/runs/5223078737/jobs/9429612354
Here is a link to Terra UI with a new component that was introduced last week
https://engineering.cerner.com/terra-ui/components/cerner-terra-framework-docs/worklist-data-grid/about
The build failure was caused by the terra-pills CHANGELOG no longer being packaged upon release (like here in v1.5.0) so #1666 fixes it with the latest release.

is the build passing ?? and I don't think removing files from pills package.json will fix the build issue. was the code changes made on terra-pill tested on terra-ui before merging PR #1666 ..??

Yeah, here is a link to the build: https://github.com/cerner/terra-ui/actions/runs/5223078737/jobs/9429612354
Here is a link to Terra UI with a new component that was introduced last week https://engineering.cerner.com/terra-ui/components/cerner-terra-framework-docs/worklist-data-grid/about
The build failure was caused by the terra-pills CHANGELOG no longer being packaged upon release (like here in v1.5.0) so #1666 fixes it with the latest release.

Thank you for sharing the info will close this PR !!

Thank you for sharing the info will close this PR !!

We can still merge this PR for the linter fixes! Just need to remove the CHANGELOG entires.

Thank you for sharing the info will close this PR !!

@supreethmr We can still merge this PR for the linter fixes! Just need to remove the CHANGELOG entires.


Website broke again

fix ur shite

Why was this assigned to me?

I'm in the process of moving all my stuff to AWS. I'll get this put over soon™

day 3, still not done

Now it's day 11.

No internet till Wednesday boys

He never specified which Wednesday. False alarm.

Alright, since this is never going to get done™, i just made a mirror
https://Δ.thebit.link/

@TheBITLINK ty

Fixed it....
after a year.
http://rabrennie.com/anything.js.


Update wiki entry on C, C++ language servers

In release v9.0.0 the default language server for C and C++ was changed from cquery to clangd. This change is now yet reflected on the related wiki page.

Done, thanks for reporting! The wiki is world-writable, so don't hesitate to fix things there.


Verify Links being created in OpenAPI document

Check options on the OData.OpenAPI reader library to see if we need to enable options to generate links.  What work needs to be done to enable generating links?

Sam advised that this feature is currently not available in the OpenAPI.NET.OData lib.


Installing x2js with npm

I'm installing x2js with the npm command npm install x2js, but I don't know why the contents are different. Even when installing using the url instead of the module name, I don't have (for example) the same package.json, nor the type definition interface (x2js.d.ts.). Is there a reason for it ?

It may be that you are looking in the development branch of the codebase, which may contain changes that are not yet published to npm. Can you confirm whether the state you see when installing via npm matches the state of the master branch in GitHub?
You can expect the latest changes currently in the development branch to be pushed to npm in December.

After looking at the state it seems you are right. The branch used is the master by comparing the files it contains. Should I wait until your next push before going further with x2js in my project or can I download and work with the type definition interface from DefinitelyTyped ?
Thank you very much for your answer !

Feel free to work with the contents of the development branch. There are no open issues, so to the best of my knowledge it is in a good state. I do not currently expect any more changes to take place before it is published to npm - the delay is merely a matter of scheduling.

Okay, thank you very much for your answers @sandersaares !


feat!: replaced getPssPublicKey with getNodeAddresses

@agazso  This brings us again to the discussion of having tests that run against both the modules and the Bee/BeeDebug class itself #38 . Because we do test this function in the module :) https://github.com/ethersphere/bee-js/blob/master/test/modules/debug/connectivity.spec.ts#L54-L62


How to reduce RAMB utilization

Dear doonny,
I'm trying to test PipeCNN framework on some Xilinx's FPGA embedded boards for take some power measurement. Actually I would like to compile the framework for Digilent ZedBoard but the synthetized program is too large for this FPGA platform, the XOCC compiler returns this error:
297 RAMB18 and RAMB36/FIFO required but only 280
Could you give me some hints for reducing the BRAM utilization?
Thank You

SDoC is not fully supported yet.
Use small value of VEC_SIZE and LANE_NUM can reduce the RAM costs.

Thanks for the reply,
I have tried to reduce VEC_SIZE to 4 and LANE_NUM to 8 and it compiles perfectly!
But when I try to run the executable on ZedBoard it doesn't work at clEnqueueNDRangeKernel invocation for knl_lrn[i], the error is the following:
Launching kernel lrn with local size: 1, 1, 24  (global size: 27, 27, 24) ERROR: ClEnqueueNDRangeKernel : CL_INVALID_WORK_GROUP_SIZE case 6 ERROR: CL_INVALID_WORK_GROUP_SIZE  Location: ../src/host/main.cpp:958 Failed to launch kernel lrn WARNING: Profiling may contain incomplete information. Please ensure all OpenCL objects are released by your host code (e.g., clReleaseProgram()). terminate called after throwing an instance of 'std::runtime_error'   what():  software scheduler stopping while there are active commands Aborted
probably I need to update some other parameters like LRN_MAX_LOCAL_SIZE or something related? could you give me some hints, I am not used OpenCL before
Thank You

Sorry, we have not used SDSoC yet.

Ok thank you very much anyway doonny.
I will keep trying to make it works with SDSoC, unfortunately I don't have a SDAccel license.


CSV export is missing some columns

CSV Export does not include the transaction HASH

would also be useful to include the then current oracle price in each line of the export, as requested here: https://discord.com/channels/404106811252408320/750533049623773304/798668544384434217

would also be useful to include the then current oracle price in each line of the export, as requested here: https://discord.com/channels/404106811252408320/750533049623773304/798668544384434217

Would it be possible to add an export CSV feature for individual Hotspots? I've seen this requested a few times and think it would be useful, not sure how difficult it would be @danielcolinjames.

Would it be possible to add an export CSV feature for individual Hotspots? I've seen this requested a few times and think it would be useful, not sure how difficult it would be @danielcolinjames.

Looking forward to the Oracle price column.

Looking forward to the Oracle price column.

I'll take a shot at this one. Is there an exhaustive list of missing fields? Should I only add hash and oracle price?

I'll take a shot at this one. Is there an exhaustive list of missing fields? Should I only add hash and oracle price?

Would it be possible to add an export CSV feature for individual Hotspots? I've seen this requested a few times and think it would be useful, not sure how difficult it would be @danielcolinjames.

Addressed in PR-175: https://github.com/helium/explorer/pull/175

hash was added, and it was decided that we won't add oracle / market price for now


[RPC Endpoints]

Something went wrong with PR preview build please check

Preview is available here:http://laboratory-pr897.previews.kube001.services.stellar-ops.com/

Something went wrong with PR preview build please check

Something went wrong with PR preview build please check

Something went wrong with PR preview build please check

Something went wrong with PR preview build please check

Something went wrong with PR preview build please check

Something went wrong with PR preview build please check

Something went wrong with PR preview build please check

I'm getting this error when submitting. Not sure if you're still working on it. Or maybe I'm missing something on my end?

Updated @quietbits

Preview is available here:http://laboratory-pr897.previews.kube001.services.stellar-ops.com/

Preview is available here:http://laboratory-pr897.previews.kube001.services.stellar-ops.com/

Preview is available here:http://laboratory-pr897.previews.kube001.services.stellar-ops.com/

Preview is available here:http://laboratory-pr897.previews.kube001.services.stellar-ops.com/


.net core SmsRequest FormData empty

Hi,
First time using Twilio in a while, and trying to use .net core 5 with Twilio.Aspnet.Core is giving me some trouble. I am testing locally using ngrok and for whatever reason the form data passed is empty. This is causing my SmsRequest object to have null properties.
Any ideas? Could it be something with ngrok?

Nevermind, i think this is Ngrok


mutex issue

many of these types of errors: note: ‘std::mutex’ is defined in header ‘’; did you forget to ‘#include ’?
this was helpful.
Use POSIX threading model for MINGW:
$ sudo update-alternatives --config i686-w64-mingw32-gcc

$ sudo update-alternatives --config i686-w64-mingw32-g++
<choose i686-w64-mingw32-g++-posix from the list>
$ sudo update-alternatives --config x86_64-w64-mingw32-gcc

$ sudo update-alternatives --config x86_64-w64-mingw32-g++
<choose x86_64-w64-mingw32-g++-posix from the list>

sorry already documented.

sorry already documented.


Vet Clinic #4: Add join table for visits

In this pull request I've done the following:

Create a add-join-table-for-visits branch

Create vets table

Create specializations and visits tables as link a.k.a join tables

Add data to vets, specializations, and visits tables

Overview of all the tables:

Who was the last animal seen by William Tatcher?

How many different animals did Stephanie Mendez see?

List all vets and their specialties, including vets with no specialties

List all animals that visited Stephanie Mendez between April 1st and August 30th, 2020.

What animal has the most visits to vets?

Who was Maisy Smith's first visit?

Details for most recent visit: animal information, vet information, and date of visit

How many visits were with a vet that did not specialize in that animal's species?

What specialty should Maisy Smith consider getting? Look for the species she gets the most

Update schema, data, and queries files

Thanks for the approval dear @topeogunleye and extremely grateful for the OPTIONAL suggestion, I didn't know that. I will name my branches in the past tense from now.


Fixing Variable Shadowing in Solidity: uint256 Redeclaration Error

The issue arises because the variable a is already declared as a parameter of the arithmeticError function:
function arithmeticError(uint256 a) public {
    uint256 a = a - 100; // Error: `a` is already declared as a parameter
}

When you redeclare a with uint256 a = a - 100;, the compiler throws an error because you're trying to shadow the parameter a by declaring a new variable with the same name. This is not allowed in Solidity.

To fix this, simply remove the type declaration (uint256) and use the parameter a directly:

solidity
Code kopieren

function arithmeticError(uint256 a) public {
    a = a - 100; // Correct: modifies the existing parameter `a`
}

@DaniPopes Hello! Can someone take a look at this pull request and merge it if everything looks good? Let me know if any adjustments are needed. Appreciate it!


Add Chicago

List of emails of elected officials in Chicago:
Cook County Directory of Elected Officials.xlsx

We are currently processing a lot of requests--it would greatly speed up our addition of Chicago if you could draft a detailed (but succinct) message! Feel free to use existing messages ( defund12.org )
Thank you!

Subject: Commit to Defunding and Reforming CPD
Emails<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Message:
Hello,
My name is [NAME] and I am a resident of [NEIGHBORHOOD/CITY]. I am extremely concerned with the City of Chicago’s inordinate investment in the Chicago Police Department (CPD) at the expense of critical youth, education, and health services. As demonstrated by ongoing peaceful protests and a 2019 Gallup poll, a majority of individuals living in Chicago view the police negatively.
I am therefore writing to demand that the City Council vote to reapportion funds allocated to the CPD to support evidence-based programs and services that, unlike increased police presence, promote the well-being of citizens and reduce crime. It is morally reprehensible to dedicate 40% of the City’s operating budget (approximately $4 million per day) towards policing while thousands of citizens are homeless and many more lack access to essential services, including clean running water and necessary mental health resources.
I also urge the City Council to enact legislation that holds police accountable and to overturn policies that allow police to engage in unlawful behavior with impunity. As set forth by Black Lives Matter of Chicago, I ask that Homan Square be immediately closed (a site where extrajudicial police interrogations are known to occur), that an elected Civilian Police Accountability Council be established with real reform powers, and that abusive cops be fired and criminally charged. Ending the unfair and secretive internal CPD grievance review process would be a good first step in achieving this goal.
People are marching in the streets because they know that these actions will result in a healthier, more just society. I implore you to please listen to the needs of your constituents and take immediate action to address their concerns.
Thank you,
[NAME]

Beautiful. We will add this ASAP!
Thanks for your contribution.

One minor issue<EMAIL_ADDRESS>should be changed to<EMAIL_ADDRESS>Thanks all for your dedication and fast work on this.


Split samples from the project root parent pom.xml

All samples will now refer to parent pom spring-boot-starter-parent.
fixes #1643.

I think this should be good to go now. You are now able to take any sample and copy its directory to a location outside the project, then run mvn spring-boot:run. It should work.

Ok I think we should be good now - I've put the checkstyle configuration in the parent-sample and all children samples correctly inherit from it: https://github.com/spring-cloud/spring-cloud-gcp/pull/1728/files#diff-50e7c6073821905e7b9c6c95f86067a1
The reason why I got stuck was because I realized we forgot to add a groupId and version on the samples parent, so the children samples were never inheriting correctly from the parent sample. But it should be good now; checkstyle works and users can also just copy a sample outside of the project to run it by changing its parent to spring-boot-starter-parent.


Add 'asciidoctor' to list of things to install (necessary to run kythe.io locally). [phab:D1577]

Created by danielmoy-google at 2017-04-25 21:35:03:

schroederc accepted this revision at 2017-04-26 16:21:59

danielmoy-google closed via commit fdcb325111ae5fdbd560311a4ee710722bc80279 at 2017-04-26 16:26:05


No export template found at the expected path

Godot version
4.0 beta (mono)
System information
win11 x64
Issue description
When update proyect from beta7.

verything seems fine

I tried to download the templates again but it keeps giving errors.
Steps to reproduce
create new proyect. add windows template (for example) and errors appear.
Minimal reproduction project
null

I tried to download the templates again but it keeps giving errors.

Did you downloading the editor again? AFAIK beta8 had a bug at first, which was later fixed.

confirmed. working well. good job


Add a SwiftSyntax511 version indicator module

@swift-ci Please test

So not Swift 6.0? 😢

The compiler currently also uses 5.11 on the main branch.
https://github.com/apple/swift/blob/7781af523e12e6e89f5f1c9e86b525f16b370cdd/utils/build_swift/build_swift/defaults.py#L49


free(): invalid pointer:

hi!
I've compiled the project in linux mint for codeblocks, but I get a pointer error. In "stb_image.c" the free() funcions is giving an error. what can i do?
thanks have a good day.

I had to copy "res" folder located in the build dir to Debug/Release folder. That worked for me.

I am also getting same error:
free(): invalid pointer
Aborted (core dumped)
on building from the terminal in Ubuntu 18.04
What should I do?

Hello, I know that this is old repo, but I also have the same issue like shivamprasad99 with free(): invalid pointer
Aborted (core dumped). Maybe someone resolve this issue already?

Fixes to prevent Policy warnings from syntax errors in CMake code files.

File: ./cmake/FindGLEW.cmake

    insert: SET(PROGRAMFILESX86 "PROGRAMFILES(X86)")
    before: SET( GLEW_SEARCH_PATHS
    and
    change: "$ENV{PROGRAMFILES(X86)}/GLEW"   # WINDOWS
        to: "$ENV{${PROGRAMFILESX86}}/GLEW"     # WINDOWS

File: ./cmake/FindSDL2.cmake

    insert: SET(PROGRAMFILESX86 "PROGRAMFILES(X86)")
    before: SET( SDL2_SEARCH_PATHS
    and
    change: "$ENV{PROGRAMFILES(X86)}/SDL2"     # WINDOWS
        to: "$ENV{${PROGRAMFILESX86}}/SDL2"   # WINDOWS

File: ./cmake/FindASSIMP.cmake

    insert: SET(PROGRAMFILESX86 "PROGRAMFILES(X86)")
    before: SET( ASSIMP_SEARCH_PATHS
    and
    change: "$ENV{PROGRAMFILES(X86)}/ASSIMP"	# WINDOWS
        to: "$ENV{${PROGRAMFILESX86}}/ASSIMP"	# WINDOWS

Fixes to prevent program execution abort on free(): invalid pointer.

File: ./src/rendering/texture.h, line 60

    from: void operator=(Texture texture);
      to: Texture& operator=(Texture other) noexcept;

File: ./src/rendering/texture.cpp, lines 207-213
replace:

    void Texture::operator=(Texture texture)
    {
        char* temp[sizeof(Texture)/sizeof(char)];
        memcpy(temp, this, sizeof(Texture));
	memcpy(this, &texture, sizeof(Texture));
        memcpy(&texture, temp, sizeof(Texture));
    }

  with:

    Texture& Texture::operator=(Texture other) noexcept
    {
        //Implemented using move assignment.

        //Guard self assignment
        if (this == &other)
            return *this;

        if(m_textureData && m_textureData->RemoveReference())
	{
            if(m_fileName.length() > 0)
                s_resourceMap.erase(m_fileName);

	        delete m_textureData;
	}
	m_fileName = other.m_fileName;
        m_textureData = other.m_textureData;
        m_textureData->AddReference();
        return *this;
    }


[ENH] - Open VS Code within JupyterLab tab

Feature description
This but done properly:

And "open in (VS) Code" to context menu over files (maybe in existing "Open with..." submenu?).
We need:

a custom widget tracker to restore the tab on refresh
an icon
determine sandbox rules
possibly customise which Code UI elements are shown by default to avoid confusion from double statusbar and double sidebar?

Value and/or benefit
Simpler experience
Anything else?
For reference with activity bar and status bar hidden:

icons for code-server - https://github.com/coder/code-server/tree/main/src/browser/media


Lightning section

Is your content request related to a problem? Please describe.
All articles related to LND should be part of the Lightning section
Describe the solution you'd like

[ ] Overview
[ ] Setup
[x] LND Connect
[ ] LND Hub
[ ] RTL
[x] Thunderhub
[ ] LNbits
[ ] Connecting external mobile/desktop apps
[ ] Troubleshooting

Additional context
It should be one stop shop for all things lightning related.

Request a page/short article with instructions on finding the initial credentials for Lightning Terminal login under the lightning "Wallet" button > Show Password.

Added.
https://mynodebtc.github.io/lightning/lightning-terminal.html

Beautiful!