App creation fails on heroku when using 2 step verification

Hi, The app fails deploying because of 2 step verification. I read the README but does this mean I need to clone the boarding project instead of deploying it right away in order to get an app key? Im lost a bit in the docs. Even using an app specific password the app fails to create. This is the log trace
Output
```
-----> Installing node-v6.10.0-linux-x64
-----> Detecting rake tasks
-----> Preparing app for Rails asset pipeline
       Running: rake assets:precompile
       rake aborted!
       Spaceship::Client::InvalidUserCredentialsError: Invalid username and password combination. Used<EMAIL_ADDRESS>as the username.
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/client.rb:403:in `rescue in send_shared_login_request'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/client.rb:374:in `send_shared_login_request'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/tunes/tunes_client.rb:161:in `send_login_request'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/client.rb:585:in `do_login'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/client.rb:346:in `login'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/client.rb:119:in `login'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/tunes/spaceship.rb:22:in `login'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/app/services/boarding_service.rb:79:in `ensure_values'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/app/services/boarding_service.rb:35:in `initialize'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/config/initializers/services.rb:1:in `new'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/config/initializers/services.rb:1:in `'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in `load'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in `block in load'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:240:in `load_dependency'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in `load'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:652:in `block in load_config_initializer'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:166:in `instrument'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:651:in `load_config_initializer'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:616:in `block (2 levels) in '
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:615:in `each'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:615:in `block in '
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:30:in `instance_exec'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:30:in `run'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:55:in `block in run_initializers'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:44:in `each'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:44:in `tsort_each_child'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:54:in `run_initializers'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:352:in `initialize!'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/config/environment.rb:5:in `'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:328:in `require'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:328:in `require_environment!'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:457:in `block in run_tasks_blocks'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/sprockets-rails-3.2.0/lib/sprockets/rails/task.rb:62:in `block (2 levels) in define'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/rake-12.0.0/exe/rake:27:in `'
       Spaceship::Client::UnauthorizedAccessError: Unauthorized Access
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/client.rb:624:in `block in send_request'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/client.rb:463:in `with_retry'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/client.rb:618:in `send_request'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/client.rb:507:in `request'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/client.rb:394:in `send_shared_login_request'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/tunes/tunes_client.rb:161:in `send_login_request'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/client.rb:585:in `do_login'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/client.rb:346:in `login'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/client.rb:119:in `login'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/fastlane-2.28.4/spaceship/lib/spaceship/tunes/spaceship.rb:22:in `login'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/app/services/boarding_service.rb:79:in `ensure_values'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/app/services/boarding_service.rb:35:in `initialize'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/config/initializers/services.rb:1:in `new'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/config/initializers/services.rb:1:in `'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in `load'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in `block in load'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:240:in `load_dependency'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in `load'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:652:in `block in load_config_initializer'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:166:in `instrument'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:651:in `load_config_initializer'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:616:in `block (2 levels) in '
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:615:in `each'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:615:in `block in '
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:30:in `instance_exec'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:30:in `run'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:55:in `block in run_initializers'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:44:in `each'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:44:in `tsort_each_child'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:54:in `run_initializers'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:352:in `initialize!'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/config/environment.rb:5:in `'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:328:in `require'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:328:in `require_environment!'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:457:in `block in run_tasks_blocks'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/sprockets-rails-3.2.0/lib/sprockets/rails/task.rb:62:in `block (2 levels) in define'
       /tmp/build_129e607e3ae530fc84a4784a29354d9d/fastlane-boarding-6bd8d28/vendor/bundle/ruby/2.3.0/gems/rake-12.0.0/exe/rake:27:in `'
       Tasks: TOP => environment
       (See full trace by running task with --trace)
 !
 !     Precompiling assets failed.
 !
 !     Push rejected, failed to compile Ruby app.
 !     Push failed

Hey @reshadf, no, you can directly publish the server on Heroku. You can generate a 2 factor key here https://docs.fastlane.tools/best-practices/continuous-integration/#two-step-or-two-factor-auth

I tried using an app specific password but it says the credentials are invalid.. I am 100% certain they are correct :/

App Specific passwords only work for the transporter for binary uploads, not for managing testers. Please use your real user/password and then generate the session token using spaceauth

Where do I put that key in heroku while using the heroku installer on the github page?

You can set that on Heroku.com when you access your app's environment variables 👍

I have tried setting the variable FASTLANE_SESSION but it seems like its ignored, all the other variables work just fine. (ITC_USER etc .. ) It keeps asking for a way to verify through 2 step verification Is that the correct key to use? FASTLANE_SESSION ?

@KrauseFx - I don't have an option to set the application's environment variable for FASTLANE_SESSION because the application creation fails due to 2 factor auth. Below is the screen shot of the only settings I have to choose from because I can't get beyond the "New App" screen on Heroku.

Here are my error logs:

rake aborted!
Spaceship::Client::UnauthorizedAccessError: Unauthorized Access
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/fastlane-2.33.0/spaceship/lib/spaceship/client.rb:627:in block in send_request'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/fastlane-2.33.0/spaceship/lib/spaceship/client.rb:466:in with_retry'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/fastlane-2.33.0/spaceship/lib/spaceship/client.rb:621:in send_request'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/fastlane-2.33.0/spaceship/lib/spaceship/client.rb:510:in request'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/fastlane-2.33.0/spaceship/lib/spaceship/client.rb:410:in send_shared_login_request'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/fastlane-2.33.0/spaceship/lib/spaceship/tunes/tunes_client.rb:161:in send_login_request'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/fastlane-2.33.0/spaceship/lib/spaceship/client.rb:588:in do_login'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/fastlane-2.33.0/spaceship/lib/spaceship/client.rb:346:in login'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/fastlane-2.33.0/spaceship/lib/spaceship/client.rb:119:in login'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/fastlane-2.33.0/spaceship/lib/spaceship/tunes/spaceship.rb:22:in login'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/app/services/boarding_service.rb:139:in ensure_values'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/app/services/boarding_service.rb:35:in initialize'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/config/initializers/services.rb:1:in new'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/config/initializers/services.rb:1:in <top (required)>'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in load'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in block in load'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:240:in load_dependency'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/dependencies.rb:268:in load'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:652:in block in load_config_initializer'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.8/lib/active_support/notifications.rb:166:in instrument'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:651:in load_config_initializer'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:616:in block (2 levels) in class:Engine'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:615:in each'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/engine.rb:615:in block in class:Engine'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:30:in instance_exec'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:30:in run'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:55:in block in run_initializers'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:44:in each'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:44:in tsort_each_child'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/initializable.rb:54:in run_initializers'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:352:in initialize!'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/config/environment.rb:5:in <top (required)>'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:328:in require'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:328:in require_environment!'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/railties-4.2.8/lib/rails/application.rb:457:in block in run_tasks_blocks'        /tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/sprockets-rails-3.2.0/lib/sprockets/rails/task.rb:62:in block (2 levels) in define'
/tmp/build_5fe3ccc3e916375bb284848678b04799/fastlane-boarding-80201eb/vendor/bundle/ruby/2.3.0/gems/rake-12.0.0/exe/rake:27:in `<top (required)>'
Tasks: TOP => environment
(See full trace by running task with --trace)
!
!     Precompiling assets failed.
!
!     Push rejected, failed to compile Ruby app.
!     Push failed

@beyerss I eventually created a new Apple ID just for this. It wouldn't work with 2 step verification. I even tried cloning Boarding and create a rails application on heroku, add config variables and then deploy but new errors were coming up all the time all related to verification. I think the best solution would be to create a new Apple ID to do stuff like this on.

Similar issue I am facing even I have set up in a local machine it works with login but no luck with the session.

I think handling the two factor authentication in a more streamlined way would be interesting, since Apple seems to enforce two factor more and more. I was stuck the whole morning to get it working again. Actually adding the session token worked for me in the end, but it was a long journey to get there. And the session expiring every month is not too smooth. Is there a way to generate a persistent token (You can set tust computer in the web interface to always trust that device if I'm correct).
Maybe an additional field for the deployment script would be a good first move, but a more persistent solution would be great in the long run.


Nfts aren't showing in wallet but show in wallet on pool.pm

Hi my nfts aren't show in my wallet, but show on jpg and on pool.pm. i have a trans showing from 3 weeks age where the assets look the move, but i don't know whats going on.

addr1q8yqvlplyrm6yqepdjq47l460p7nj9q6z2heljvwkrqvgxls52a5s8eq8dj64cm3lz2dx670fh4kr9lhhq59w0afpr4sm3ly99

@Wideloadc51 Make use of the Nami web app click here  to connect and import


DataGridValueConverter: fix processing of nullable values

What does the pull request do?
Fixes regression introduced in 36cfc43a596c2181278b1a86b00fb4761dca0fc8
What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues
Fixes #9650

You can test this PR using the following package version. 11.0.999-cibuild0027672-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0027676-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


Merge dev into main before 2021-12-20

A merge of our bi-weekly sprint work from dev into main.

CI is failing only because sandbox.zenodo.org is down (again).


Update to support Kubernetes 1.14

The controller-runtime  has been updated to Kubernetes 1.14, which moves scheme under /pkg instead of /pkg/runtime now. The import in register.go is no longer valid so it will not compile.

Seems the same problem happens on "controller-tools" as well.
go run vendor/sigs.k8s.io/controller-tools/cmd/controller-gen/main.go all
vendor/sigs.k8s.io/controller-tools/cmd/controller-gen/main.go:25:2: cannot find package "sigs.k8s.io/controller-tools/pkg/crd/generator" in any of:
	/snap/go/3947/src/sigs.k8s.io/controller-tools/pkg/crd/generator (from $GOROOT)
	/home/ubuntu/go/src/sigs.k8s.io/controller-tools/pkg/crd/generator (from $GOPATH)
vendor/sigs.k8s.io/controller-tools/cmd/controller-gen/main.go:26:2: cannot find package "sigs.k8s.io/controller-tools/pkg/generate/rbac" in any of:
	/snap/go/3947/src/sigs.k8s.io/controller-tools/pkg/generate/rbac (from $GOROOT)
	/home/ubuntu/go/src/sigs.k8s.io/controller-tools/pkg/generate/rbac (from $GOPATH)
Makefile:41: recipe for target 'manifests' failed
make: *** [manifests] Error 1

~/go/src/sigs.k8s.io/controller-tools/pkg/crd$ ls generator
ls: cannot access 'generator': No such file or directory


Site Details text isn't right

From Bert:

'Site Details' needs to be something else...my fault. Maybe "Properties"  ???

Superseded by #48


Pin Administrate below 0.20.0

0.20.0 introduces a change relating to attribute grouping and makes it incompatible. We'll pin this here and release a new version with this change so that a future breaking change can be marked as such.
https://github.com/nickcharlton/administrate-field-nested_has_many/issues/65

I can't be bothered to fix this on EOL Rubies, so Trust Me Bro™ it is passing locally.


Question (bug?): possible to set new refresh rate with mv command?

I'm trying to have the user input a new refresh rate for a plugin, e.g. change 30m to 60m. The main BitBar script is then renamed from old-basename to new-basename with the mv command. Then the plugin needs to be refreshed, but since it's already loaded, the old-basename needs to be refreshed. (Using new-basename wouldn't work.) Until this point, everything works fine. Then, however, the plugin goes into an endless "Updating…" state, from which it doesn't wake up. It seems that it wants to reload old-basename, but doesn't find it anymore, since it has been renamed to new-basename. Any way to get around this problem?

Yeah, I've seen this problem too. I would be really interested to see if there's a solution.

BitBar currently needs a reset (command + R), not a refresh, when renaming plugins. AFAIK the only way to reset externally would be to killall and open BitBar.

It's probably better to do it as gentle as possible
/usr/bin/osascript -e 'tell application "BitBar" to quit' &>/dev/null && sleep 1
/usr/bin/open -b com.matryer.BitBar

PS: Maybe there's a solution to either make BitBar scriptable, so you could do something like
/usr/bin/osascript  << EOT
tell application "BitBar" to activate
tell application "System Events"
	tell process "BitBar"
		click menu 1
		keystroke "r" using command down
	end tell
end tell
EOT

… or simply extend the URL scheme to /usr/bin/open "bitbar://reset". (This would be the most elegant solution.)

More elegant than that would be that if BitBar sees the script doesn't exist anymore (e.g. my_script.30s.sh) it would look for anything that matches my_script.*.sh and reload.
Or better, a new way to specify refresh timeouts.
Quick idea: instead of coding the interval in the script name, the interval is printed to the stdout, so the script can decide a new timeout at each refresh.


Load decision maker based on the responsible ministry chosen in the work to show the staff dropdown in the events grid

Overview
There are certain milestones which involves decision to made. For such milestones, it should be possible to choose who is going to take that decision and this should be modifiable later.
It is possible to choose the responsible person from the list of staffs and also can be filtered based on the responsible ministry chosen in the work.

List of names is too long / not filtered enough. Tried by Geoff, need walk through on behaviors with a dev.

Decision event completely disappearred

List is now filters to only ministers, but doesn't limit the list to just the minister of selected ministry


[v1.x] Mkldnn header fix v1x for nightly binaries

Description
Nightly binaries available at https://dist.mxnet.io/python with the label 1.7.0 are built from 1.x branch.
So to fix the MKLDNN header missing issue in Nightly binaries, we need to cherry-pick it into 1.x branch
@MoisesHer @mseth10 @leezu @szha

I think when enabling the branch protection, we accidentally turned on "Require branches to be up to date before merging". I'm requesting to disable it in https://issues.apache.org/jira/browse/INFRA-20616. Don't worry about updating the branch in this PR for now.

Sure. Thanks Sheng for jumping in. I'll wait until the branch protection is fixed.

@MoisesHer since this is merged, nightly binary of 4th Aug should have mkldnn. Can you verify?

I can confirm mkldnn headers exist
wget https://repo.mxnet.io/dist/python/cpu/mxnet-1.7.0b20200803-py2.py3-none-manylinux2014_x86_64.whl
unzip mxnet-1.7.0b20200803-py2.py3-none-manylinux2014_x86_64.whl -d 17_check_mkl
cd 17_check_mkl
find . -name "*mkl*"

Output
./mxnet/include/mkldnn
./mxnet/include/mkldnn/mkldnn_debug.h
./mxnet/include/mkldnn/mkldnn_types.h
./mxnet/include/mkldnn/mkldnn.h
./mxnet/include/mkldnn/mkldnn_version.h
./mxnet/include/mkldnn/mkldnn_config.h
./mxnet/include/mkldnn/mkldnn_dnnl_mangling.h
./mxnet/include/mkldnn/mkldnn.hpp


Override IsDebuggerPresent and FormatMessageW [Draft PR]

Testing a very basic change.
Will i get a new nugget version?  How do i test this out with a client.

Will i get a new nugget version

No....


Issue number

Hi,
great project! It would be useful to have the issue number for the code list, for example codelist 196 was updated on issue 46: https://ns.editeur.org/onix/en/196
Gregorio

I've seen that issue are displayed for single code, but it would be useful to know the last issue at code-list level

Thank you for the feedback. I just noticed that I haven't updated for a while, so I updated now to the latest issue 46.
Did I understand your question correctly, you would like to see the latest codelist issue number when any of the values was last updated?

I think that near the code-list title it would be useful to have the last issue number when it has ben updated.
Something like:

I've now added it under the codelist name as a notice. Is this OK?

Yes, great!
Thank you


chromium 48.0.2548 configure error

I was using the latest 48.0.2548 recipe and encountered such error:
ERROR: Function failed: do_configure ERROR: Logfile of failure stored in:  Log data follows: | DEBUG: Executing python function sysroot_cleansstate | DEBUG: Python function sysroot_cleansstate finished | DEBUG: Executing shell function do_configure | Updating projects from gyp files... | Exception: Failed to open test/data/webui/i18n_process_css_test.html while trying to flatten test/data/webui/i18n_process_css_test.html. (No such file or directory) | Traceback (most recent call last): |   File "~/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-3.14-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/tools/gyp/pylib/gyp/input.py", line 491, in CallLoadTargetBuildFile |     includes, depth, check, False) |   File "~/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-3.14-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/tools/gyp/pylib/gyp/input.py", line 412, in LoadTargetBuildFile |     build_file_data, PHASE_EARLY, variables, build_file_path) |   File "~/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-3.14-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/tools/gyp/pylib/gyp/input.py", line 1287, in ProcessVariablesAndConditionsInDict |     build_file) |   File "~/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-3.14-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/tools/gyp/pylib/gyp/input.py", line 1302, in ProcessVariablesAndConditionsInList |     ProcessVariablesAndConditionsInDict(item, phase, variables, build_file) |   File "~/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-3.14-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/tools/gyp/pylib/gyp/input.py", line 1287, in ProcessVariablesAndConditionsInDict |     build_file) |   File "~/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-3.14-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/tools/gyp/pylib/gyp/input.py", line 1302, in ProcessVariablesAndConditionsInList |     ProcessVariablesAndConditionsInDict(item, phase, variables, build_file) |   File "~/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-3.14-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/tools/gyp/pylib/gyp/input.py", line 1287, in ProcessVariablesAndConditionsInDict |     build_file) |   File "~/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-3.14-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/tools/gyp/pylib/gyp/input.py", line 1306, in ProcessVariablesAndConditionsInList |     expanded = ExpandVariables(item, phase, variables, build_file) |   File "~/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-3.14-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/tools/gyp/pylib/gyp/input.py", line 886, in ExpandVariables |     replacement = str(py_module.DoMain(parsed_contents[1:])).rstrip() |   File "~/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-3.14-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/tools/grit/grit_info.py", line 150, in DoMain |     options.target_platform) |   File "~/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-3.14-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/tools/grit/grit_info.py", line 97, in Inputs |     files.update(node.GetHtmlResourceFilenames()) |   File "~/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-3.14-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/tools/grit/grit/node/include.py", line 118, in GetHtmlResourceFilenames |     allow_external_script=allow_external_script) |   File "~/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-3.14-linux-gnueabi/chromium/48.0.2548.0-r0/chromium-48.0.2548.0/tools/grit/grit/format/html_inline.py", line 412, in GetResourceFilenames |     (e.filename, filename, e.strerror)) | Exception: Failed to open test/data/webui/i18n_process_css_test.html while trying to flatten test/data/webui/i18n_process_css_test.html. (No such file or directory) |  | Error processing node <?xml version="1.0" encoding="UTF-8"?> | <include allowexternalscript="true" file="webui/i18n_process_css_test.html" flattenhtml="true" name="IDR_WEBUI_TEST_I18N_PROCESS_CSS_TEST" type="BINDATA" /> | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_configure ERROR: Task 7 (~/sources/meta-browser/recipes-browser/chromium/chromium_48.0.2548.0.bb, do_configure) failed with exit code '1'
It seems that files are missing from the Chromium source package.

Oops. The issue doesn't belong to this repo. Sorry...


Enable Helm chart default tolerations override

<
What would you like to be added:
The ability to remove the default tolerations in the Helm chart which schedule pods onto master nodes.
https://github.com/splunk/splunk-connect-for-kubernetes/blob/develop/helm-chart/splunk-connect-for-kubernetes/charts/splunk-kubernetes-metrics/values.yaml#L166
# This default tolerations allow the daemonset to be deployed on master nodes,
# so that we can also collect metrics from those nodes.
tolerations:
  - key: node-role.kubernetes.io/master
    effect: NoSchedule

Replacing the above with
tolerations: {}
still results in the default tolerations set in the daemonset.
https://github.com/splunk/splunk-connect-for-kubernetes/blob/develop/helm-chart/splunk-connect-for-kubernetes/charts/splunk-kubernetes-metrics/templates/daemonset.yaml#L43
It is not quite clear how this default is getting rendered in the daemonset template from an empty value.
Why is this needed:
To allow enabling/disabling of the SCK pods on master nodes

it should be an empty array.
tolerations: []
but when i test it, both of them works.

Interesting.  I tried the empty {} and I tried empty [].   Sounds like both {} and [] work but not for me.  I will need to look into this some more.

@amehub should I close the ticket?

Closing the issue. Feel free to reopen or create a new one if needed.


FCVTMOD.W.D Instruction in Zfa

@aswaterman
I have a question regarding to the instruction, Modular Convert-to-Integer Instruction.

What Javascript function does this instruction emulate?
In one of the paragraph, it states
Bits 31:0 are taken from the rounded, unbounded two's complement result, then sign-extended to XLEN bits and written to integer register {\em rd}. $\pm\infty$ and NaN are converted to zero.

If my understanding of the above is correct, this instruction converts the double precision input into 2's complement signed number with unlimited precision (on both the integer and fraction parts). Since the rounding mode is RTZ, if the intermediate 2's complement signed number is a negative number, we actually need to "increment" on the integer part to get the rounded integer. In other words, we can have a case when the input is a very small negative value, it can be rounded "up" to positive zero. Are we sure we really want RTZ instead of RNI?
And for the next question. After the rounded integer is obtained, we then take bit 31 to 0 of the rounded result with infinite "integer" precision. So what this means is, a negative number may become positive, and vice versa. Are we sure this is the expected behavior

I can understand why you'd look askance at the semantics, but the answer to both of your questions is: yes, that was deliberate.  ARMv8's similar instruction, FJCVTZS, does indeed round towards zero.  And, in the event of overflow, it also discards the MSBs, even if doing so changes the sign of the result.
cc @gfavor @ptomsich, who had more of a hand in the definition of this instruction than me.

On Thu, Apr 27, 2023 at 11:14 PM Andrew Waterman @.***>
wrote:

I can understand why you'd look askance at the semantics, but the answer
to both of your questions is: yes, that was deliberate. ARMv8's similar
instruction, FJCVTZS, does indeed round towards zero. And, in the event of
overflow, it also discards the MSBs, even if doing so changes the sign of
the result.
cc @gfavor https://github.com/gfavor @ptomsich
https://github.com/ptomsich, who had more of a hand in the definition
of this instruction than me.

All I would add on is simply that the semantics of this and ARM's similar
instruction are driven by the desired semantics for efficiently supporting
JavaScript's convert operation.  This link provides some more what and why
info about this instruction and also answers your question:
https://stackoverflow.com/questions/50966676/why-do-arm-chips-have-an-instruction-with-javascript-in-the-name-fjcvtzs
Greg

Please refer to the ECMAscript (a.k.a. JavaScript) standard for semantics required in JavaScript:

https://262.ecma-international.org/13.0/#sec-toint32
https://262.ecma-international.org/13.0/#sec-touint32

For the To(U)?Int{16,8} semantics, the decision was to not provide a dedicated instruction and rather defer to a FCVTMOD.W.D and a subsequent extension operation.
--Philipp.

Thank you all for the prompt response. Let me dig into this to gain some
background knowledge. This is an "interesting" instruction and I would love
to know how many people depend on that feature when the input is going
out-of-bound.
Liang-Kai
On Fri, Apr 28, 2023 at 3:17 AM Philipp Tomsich @.***>
wrote:

Please refer to the ECMAscript (a.k.a. JavaScript) standard for semantics
required in JavaScript:

https://262.ecma-international.org/13.0/#sec-toint32
https://262.ecma-international.org/13.0/#sec-touint32

For the To(U)?Int{16,8} semantics, the decision was to not provide a
dedicated instruction and rather defer to a FCVTMOD.W.D and a subsequent
extension operation.
--Philipp.
—
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-isa-manual/issues/1027#issuecomment-1527171901,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGWBFSTJ3ALD4LSGUVN3XFDXDN4JTANCNFSM6AAAAAAXOWDKGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
thanks,
Liang-Kai

Yeah, it’s certainly an odd duck.
On Fri, Apr 28, 2023 at 7:13 AM liangkaiwang @.***>
wrote:

Thank you all for the prompt response. Let me dig into this to gain some
background knowledge. This is an "interesting" instruction and I would love
to know how many people depend on that feature when the input is going
out-of-bound.
Liang-Kai
On Fri, Apr 28, 2023 at 3:17 AM Philipp Tomsich @.***>
wrote:

Please refer to the ECMAscript (a.k.a. JavaScript) standard for semantics
required in JavaScript:

https://262.ecma-international.org/13.0/#sec-toint32
https://262.ecma-international.org/13.0/#sec-touint32

For the To(U)?Int{16,8} semantics, the decision was to not provide a
dedicated instruction and rather defer to a FCVTMOD.W.D and a subsequent
extension operation.
--Philipp.
—
Reply to this email directly, view it on GitHub
<
https://github.com/riscv/riscv-isa-manual/issues/1027#issuecomment-1527171901
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AGWBFSTJ3ALD4LSGUVN3XFDXDN4JTANCNFSM6AAAAAAXOWDKGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
thanks,
Liang-Kai
—
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-isa-manual/issues/1027#issuecomment-1527636001,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH3XQTQRWM3PABSBKBMCATXDPF7ZANCNFSM6AAAAAAXOWDKGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Just wonder, I think this instruction was proposed as a scalar instruction as of now. What's the odd of this getting added into the Vector Extension?

@liangkaiwang Could you provide some background on the use-cases for a SIMD version of this instruction?

I actually don't have one. But given what I have seen so far, it appears to me that several of the arithmetic instructions end up getting promoted into the Vector ISA and that's why I wonder if there has been push by someone else to get this into the Vector ISA.

If we're sharing our vector Zfa Christmas lists, I want vector versions of fround.*, for use in vector transcendentals.

@nick-knight Please start new issues for new features.

@liangkaiwang This is instruction is intended for use by the Javascript JIT engine, which is unlikely to ever do auto-vectorization.  If that ever happens, we could be motivated to add a vector variant.

Agreed on both counts.
Closing this issue, as I believe it's resolved, but please feel free to reopen if need be.


To csv

#7

Pull Request Test Coverage Report for Build 382

0 of 47 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-2.4%) to 68.135%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

scripts/to_csv.py
0
47
0.0%

Totals

Change from base Build 380:
-2.4%

Covered Lines:
928

Relevant Lines:
1362

💛  - Coveralls


xwm: end transfers when the requestor is destroyed

This improves the failure cases when incremental transfers fail to complete successfully for one reason or another. In particular it should vastly improve the failure case seen at https://github.com/swaywm/sway/issues/4007, especially because QXcb uses a special temporary window for its requestor, that gets always destroyed in the case that the error happens.

QXcb uses a special temporary window for its requestor

As a side note, we should probably do that in wlroots too, instead of having a queue of transfers.


travis builds failing

https://travis-ci.org/GoogleCloudPlatform/gcloud-golang/builds
Are you still using travis for CI, or are you using something else?

Yes, we are.  I'll investigate.

It looks like one commit broke the Go:tip build and another commit broke the Go:1.4 build.
I've asked the authors of those commits to investigate.

Travis appears to be using a broken tip, over two weeks old. The real tip works fine and doesn't break in those ways.

Now locally I get this error:
--- FAIL: TestACL-12 (3.31s)
	integration_test.go:310: Cleanup deletion of acl1
	integration_test.go:310: Cleanup deletion of acl2
	integration_test.go:251: Writing acl1
	integration_test.go:251: Writing acl2
	integration_test.go:292: Expected to find an ACL rule for<EMAIL_ADDRESS>user, but not found
	integration_test.go:295: Error while deleting bucket ACL rule: storage: error deleting bucket ACL rule for bucket "bucketname", entity<EMAIL_ADDRESS>googleapi: Error 404: Not Found, notFound
FAIL
FAIL	google.golang.org/cloud/storage	11.666s

I'll work on it.

This error appears to be a regression in the Cloud Storage API.  Filed a bug with the Storage team.

Travis Go 1.4 tests are now passing.  I filed a separate issue for the commented-out PutBucketACLRule test.  Closing issue.


Upgrade to Jakarta Mail 2.x.x

Jakarta Mail 2.0.0 release is the first release with package namespace changed to jakarta.mail. The main jar file is located at com.sun.mail:jakarta.mail.
This release contains no other enhancements nor bug fixes, except for the minimal required Java SE version which is now Java SE 8. This is also the release included in Jakarta EE 9. Applications are able to switch to this new version by just changing all imports that use javax.mail.* to instead use jakarta.mail.*.

Will have to update jakarta.activation too.
I think that these dependencies will have to update to new namespace before:

 net.markenwerk:utils-mail-dkim
 net.markenwerk:utils-mail-smime
org.simplejavamail:smtp-connection-pool (because of com.github.bbottema:clustered-object-pool)

I have avoided switching to Java8 until now as Java7 still had a market share of around 5-10% until recently (off the top of my head). I'll do a new survey and see if a switch can be made more safely now...

Could you please consider removing the low priority label from this?
An upgrade to version 2.0.0 or higher would be great, as other libraries already made that change, which leads to incompatibility for the following reason (illustrated in steps):

the other library has version 2.0.0 as a dependency, SimpleJavaMail has a lower version as a dependency
the buildsystem now chooses the higher version automatically, meaning that the lower version won't be available as a library
now due to the change in the package structure, SimpleJavaMail can't access the required parts of jakarta mail anymore, as it expects them to be at javax.mail (where they aren't)

This means, that it currently is impossible to use SimpleJavaMail together with other libraries which implement a newer version of jakarta mail.

I started migrating to Jakarta Mail 2.0.0. As https://github.com/markenwerk/java-utils-mail-smime is archived, I'm forking it so I can update the dependencies to Jakarta Mail 2.0.0 as well. I'll go ahead and merge some of my ignore pull requests as well, so I can clean up Simple Java Mail a bit finally.

I'm in talks with the developers (both last one and original ones) to obtain permissions to relicense S/MIME under ApacheV2 and have procured 2 out of 3 permissions. When that's done, I'll start upgrading those projects.

@bbottema, any news on this?

Yes, I've obtained all permissions and started migrating to Java 8 and Jakarta new version some time ago, but I put it on hold for some time to catch some breath. I've recently started picking up some maintenance work again to get back into the flow so I hope to pick this up again soon.

Alright, things are looking up. I've upgraded everything to Java 8, Jakarta 2.0.1 and latest log4j version due to the recent security issues there. I've forked and migrated markenwerk DKIM and S/MIME to the Simple Java Mail space, with permissions of all parties involved and everything is not up to day and under ApacheV2 license.

7.0.0 just released with the upgrade to Jakarta Mail 2.0.1


Adding testing with Travis CI

This setup includes almost all features mentioned in the discussion thread, at least those that could be integrated easily:

Builds for all combinations of (Windows, macOS, Linux) and (stable, beta, nightly).
Building and testing
Audits, clippy linting and rustfmt formating
I also fixed all warnings by rustfmt and clippy and therefore, all tests should pass.

However, I did not add (codecov)[https://codecov.io/] since it requires a bit more setup work.

It looks like someone has to setup Travis CI for rust-dsp. Is someone in charge willing to grant Travis CI access to the repos?

I've found out how to activate Travis for rust-dsp/rust-lv2 but however, it doesn't seem to recognize this PR. I will merge it and hope that the profile will be detected then.


Transfer did not complete

See the logs here:
https://app.datadoghq.com/logs?query=host:ip-172-17-1-249.us-east-2.compute.internal service:sequencer-subscriber container_id:8f4b9fc426fa4b8587b7946bffe479ac-1604345690 @requestContext.transferId:0xda13c836a5a00d9415ef2888b4a18efe2024f5bdab2411afb42e7225aeda96cd&cols=service&context_event=AYYWCD35AABB74td-ofGTQAA&index=mainnet-production&messageDisplay=inline&saved-view-id=1285114&stream_sort=time,desc&viz=&from_ts=1675406584345&to_ts=1675406944345&live=false
It looks like this transfer, the sequencer subscriber threw an error reading from the subgraph: Store error: database unavailable. But in this case we didn't see a retry, which I would have expected. Very concerning.

This was fixed after subgraph came back up, and retries were properly added.


On Device activity

The node returns no information from AWS servers for routine execution or voice queries

Works for me...
Just tested and routine execution returns msg with msg.payload.success true ok
And separate on device activity returns payload with details of the action the routine just took.
Sure it’s initialised ok when you are testing?
UK emea based account.
PS hi watch your YT :)

Oh Hi!
I'm on the UK settings too. I get the media queue changes but I cannot get
the information about the voice commands or routines triggered.
I'm triggering from mobile Alexa app.
Innit is ok as other things were fine.
I also had issues passing speech to Alexa devices with screens. No speech
occurred.
On Thu, 11 Mar 2021, 11:32 Peter Stevenson, @.***>
wrote:

Works for me...
Just tested and routine execution returns msg with msg.payload.success
true ok
And separate on device activity returns payload with details of the action
the routine just took.
Sure it’s initialised ok when you are testing?
UK emea based account.
PS hi watch your YT :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cakebake/node-red-contrib-alexa-remote-cakebaked/issues/7#issuecomment-796670785,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKDRL26GMSGXUDABCUXVXFDTDCS3LANCNFSM4ZABDHXA
.


python310Packages.teamcity-messages: 1.31 -> 1.32

Description of changes
https://github.com/JetBrains/teamcity-messages/releases/tag/v1.32

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 198565 run on x86_64-linux 1

1 package marked as broken and skipped:

pgadmin

10 packages failed to build:

sourcehut.buildsrht
sourcehut.dispatchsrht
sourcehut.gitsrht
sourcehut.hgsrht
sourcehut.hubsrht
sourcehut.listssrht
sourcehut.mansrht
sourcehut.metasrht
sourcehut.pastesrht
sourcehut.todosrht

23 packages built:

apache-airflow (python310Packages.apache-airflow)
borgmatic
pgadmin4
python310Packages.flask-admin
python310Packages.flask-appbuilder
python310Packages.flask-security-too
python310Packages.flexmock
python310Packages.ihatemoney
python310Packages.sqlalchemy-continuum
python310Packages.sqlalchemy-i18n
python310Packages.sqlalchemy-utils
python310Packages.teamcity-messages
python39Packages.apache-airflow
python39Packages.flask-admin
python39Packages.flask-appbuilder
python39Packages.flask-security-too
python39Packages.flexmock
python39Packages.ihatemoney
python39Packages.sqlalchemy-continuum
python39Packages.sqlalchemy-i18n
python39Packages.sqlalchemy-utils
python39Packages.teamcity-messages
sourcehut.coresrht


Layout issue on text string with image attachment

Bottom of text note on attachment is getting cropped.

similar issue is happening with paid attachments

fixed in latest APK

Please close the bugs that was already fixed. Thanks.


Remove font-smoothing on body

-webkit-font-smoothing is non-standard and makes text look worse on light backgrounds—which I think we more commonly see than dark backgrounds—graying the text slightly. I think it’s bad to apply this in such a global manner (on the body).
I purposely left -webkit-font-smoothing on the button, because it has a darker background and the text renders better with it on, in this use.
Some comparisons (all screenshots from my retina MacBook Pro):

I'm fine with this

:+1:
Thanks for doing the side-by-side, I think it illustrates the color effect really well.

Sweet


fixed #1860,#1892,#1907 - [closed]

In GitLab by @liyanq528 on Dec 26, 2018, 08:07
Merges 20181006 -> dev

In GitLab by @wknet123 on Nov 13, 2019, 11:35
The test coverage for backend is 22.7%  39.24%  , check  console log

In GitLab by @wknet123 on Nov 13, 2019, 11:35
The test coverage for backend is %  39.25%  , check  console log

In GitLab by @wknet123 on Nov 13, 2019, 11:35
closed


buildDotnetModule: misc fixes, support ReadyToRun and native binaries inside nuget files

Description of changes
Closes https://github.com/NixOS/nixpkgs/issues/230848
Closes https://github.com/NixOS/nixpkgs/issues/181373
This adds crossgen2 nugets to the per-sdk nuget source, allowing them to be found
by the dotnet build process.
Also, we iterate over the entire .nuget folder after restore, and perform patchelf on any native binaries found, allowing them to run properly during the build process. This allows dotnet packages that use crossgen2 (PublishReadyToRun flag), and other nugets using native binaries, like protoc or minver, to work properly without any hacks.
This PR also contains small changes to how the --runtime flag is set, so that hopefully some errors can be avoided automatically (ie. running PublishReadyToRun may require the --runtime flag). The flag is now set when building a .csproj file or when selfContainedBuild is on (as before).
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2257

Updated, should be ready to merge

35 packages built:
ArchiSteamFarm BeatSaberModManager alttpr-opentracker audiobookshelf boogie btcpayserver btcpayserver-altcoins dafny denaro depotdownloader discordchatexporter-cli eventstore formula galaxy-buds-client inklecate jackett jellyfin kavita marksman msbuild nbxplorer netcoredbg omnisharp-roslyn opentabletdriver osu-lazer pinta ps3-disc-dumper roslyn ryujinx scarab slskd space-station-14-launcher tone wasabibackend xivlauncher
Result of nixpkgs-review run on x86_64-linux 1

35 packages built:

ArchiSteamFarm
BeatSaberModManager
alttpr-opentracker
audiobookshelf
boogie
btcpayserver
btcpayserver-altcoins
dafny
denaro
depotdownloader
discordchatexporter-cli
eventstore
formula
galaxy-buds-client
inklecate
jackett
jellyfin
kavita
marksman
msbuild
nbxplorer
netcoredbg
omnisharp-roslyn
opentabletdriver
osu-lazer
pinta
ps3-disc-dumper
roslyn
ryujinx
scarab
slskd
space-station-14-launcher
tone
wasabibackend
xivlauncher

I confirmed that R2R works fine.
Thanks!

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2356


[BBPBGLIB-556] Full estimate of memory consumption

Introduce full memory estimation capabilities for dry run as detailed in https://bbpteam.epfl.ch/project/issues/browse/BBPBGLIB-556.
When running in dry run mode, neurodamus will now provide a full estimate of the memory usage for both cells and synapses.
The synapse workflow is mostly untouched from the previous version with just a small bug fix.
For the cells estimate workflow we now perform full calculation of the estimate with the following workflow:

Finding all unique combinations of METypes and taking only the first 50 elements of each combination
Instantiating these combinations. Each set of maximum 50 elements is allocated in a different rank.
Getting the total memory consumption and then average it per cells.
Use the above average to calculate total memory usage for any combination with more than 50 elements.
Combine the cells memory total with the synapse one to get a full estimate.

The MR also introduces exporting the cells memory estimate to json file. Since this phase is the most time consuming one, by default the dry run workflow will automatically export the results for cell memory usage to a memory_usage.json file. It will also try to load this file on any subsequent run and just perform instantiation for METype combinations that are not already present in the file.
To do/to check:

[x] etype coming from SONATA files don't have any numerical suffix, while etypes taken from the cells_info internal object have a numerical suffix. This suffix is currently eliminated from any checks but should be clarified why they are different and if it's safe to eliminate the suffix.
[x] check behaviour in more circuits or in case of multiple circuits
[ ] add full dry run workflow test

Review

[x] PR description is complete
[x] Coding style (imports, function length, New functions, classes or files) are good
[ ] Unit/Scientific test added
[x] Updated Readme, in-code, developer documentation

Thanks for the review @ferdonline!
Yeah, since this MR is getting very long and it's properly working already, we can leave any further development to another branch/MR.
Having fixed the issue you signaled, If you have nothing against it, I would merge it when the test pass.


Triggered Kotsadm version update 2021.10.29-2-nightly

Automated changes by the auto-kotsadm-update GitHub action

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


sanity check: theta vs. theta_round on trackerdict

is theta_round being used throughout all gendaylit1axis set1axis angle = 1 rounded?
If roundtrackingAngle boolean option is set to False, theta is rounded to 1 degree.
However, is theta_round or theta the one used forever down the line? The trackerdictionary entries are based on theta_round, but what about content and geometry creation? it should be theta_round overall.

theta_round is only used for gencumsky tracking version. when doying gendaylit tracking version, theta is used to genreate the tracker at the right angle. Implemented a rounding to 0.01 degrees for this though. All's good.


Reputation System

Should we create a reputation system similar to Stack Overflow?

I like this idea, but I don't like how StackOverflow prohibits you from doing certain things if you don't have a high enough reputation.

Yeh, I've heard this complaint before about SO -- but the thing is, reputation is SO's method of automatically granting priviledges to people. You might imagine the situation where a former student decides to vandal the site by down voting good answers, deleting tags etc. So if you don't want a reputation based system of priviledges, how do you want them assigned?


Write a Swift program to find volume of a cone

Description
Write a Swift program to find volume of a cone
Volume of cone = 1/3 × π × Radius^2 × Height
Radius : 2
Height : 3

Volume : 12.566370614359

How to contribute

Save the solution in program/FindVolumeOfACone.swift file
Add FindVolumeOfACone.swift file in find-volume-of-a-cone folder

!assign


fix:full score on score analysis

Description of the change
This resolves https://github.com/TimefoldAI/timefold-quickstarts/issues/272
Checklist
Development

[ ] The changes have been covered with tests, if necessary.
[ ] You have a green build, with the exception of the flaky tests.
[ ] UI and JS files are fully tested, the user interface works for all modules affected by your changes (e.g., solve and analyze buttons).
[ ] The network calls work for all modules affected by your changes (e.g., solving a problem).
[ ] The console messages are validated for all modules affected by your changes.

Code Review

[ ] This pull request includes an explanatory title and description.
[ ] The GitHub issue is linked.
[ ] At least one other engineer has approved the changes.
[ ] After PR is merged, inform the reporter.

@pieterdeschepper Score analysis is now on more quickstarts than just the one. Please update the others too. (Until we discuss in Brno how to share all of this code under one roof.)


Bratseth/rank type information

@lesters please review
I did not get to the type information, this is just refactoring + allow "function" instead of "macro" in rank profiles. It's possible to follow the individual commits.

Merging to get a system test run off hours

LGTM! System tests passes successfully as well.


Remove source-built buildah from CI

Signed-off-by: Chris Evich<EMAIL_ADDRESS>

/hold

I am fine with doing this.  Did we ever use buildah in testling podman?

@rhatdan At one point, I believe building/installing buildah was required though I can't recall whatfor.  I made this PR at the request of @baude so I'll let him answer on the details.

***Note: *** leaving this as a WIP, since only the cache-image build workflow ran.  I want to run the normal workflow with the new images.  Since master is currently broken, will need to rebase this anyway, so it's on hold for now.

@cevich Any update on this?

/hold cancel

@haircommander FYI - this PR will clash with your #3143

@haircommander actually worse, it could silently clash - there are no checks that verify the currently running VM images match the code which produced them...which would be an interesting trick if it could be done somehow.

@cevich is this only an issue if it gets merged, or are we both creating competing VMs that effect each other while the PRs are in flight?

@haircommander I was thinking around merge-time it could be a problem...if the second-to-merge didn't rebuild + update the VM image names, but only fixes the build code.

mine should be second, so I'll just have to remember to rebuild :) thanks for the warning

Ref: Mr. @baude asked for this PR

/approve

LGTM

/lgtm


(maint) json_pure in 1.9.x

json_pure just released 2.0.2 on July 26th, restricting to at least
Ruby v2. Unfortunately DSC building requires 1.9.3 and testing on
older versions of Puppet also requires 1.9.x to be able to install
Puppet, which depends on json_pure.
Restrict to json_pure 2.0.1 or less when running Ruby 1.x.

Typically I would prefer to use the optional setting not required but as this module is already using required I'm happy for it to stay

Optional?

still waiting...

@puppetlabs/windows please review and merge - this holds up another PR

Is superseded by https://github.com/puppetlabs/puppetlabs-dsc/pull/222


403 | Permission denied. Failed to verify the URL ownership.

My domain name has been in the webmaster console before. After adding the service account and downloading the key, I added the user again in the webmaster console. However, I can get the sitemap in gis but cannot submit it. The error is:
Response was: 403
{
  "error": {
    "code": 403,
    "message": "Permission denied. Failed to verify the URL ownership.",
    "status": "PERMISSION_DENIED"
  }
}

I see that the error rate of Web Search Indexing API is 100

I found reason.
When binding the service account to the search console, the added user permissions must be set to owner instead of the default full.


Optional .babelrc

Similar to webpack in #2 but with babel

Will use babel-preset-graphpack by default


Feature/notifications design

I think this looks good and I can see better now what you were talking about with regard to the drop down. I do think the short term solution is fine, to just throw the buttons side by side in there.
Another thing you may have noticed is I'm trying to remove all the instances where I've had to do (this: any) in the Vue components, so if you're working on a file feel free to do the same as I am. It basically amounts to just adding types to data, return values and arguments.


APT whitelist request for libkyotocabinet-dev

This replaces travis-ci/travis-ci#3613.
The original text by @marshall-lee follows

Required for building good old kyotocabinet-ruby.

Thanks!


Specifying a gid when creating a user does not work

The following did not set the gid correctly:
users:

username: james_
name: James Beal
gid: 4000
uid: 5001

I will do a pull request so the following is accepted and works correctly.
users:

username: james_
name: James Beal
group: systems
uid: 5001

I realise that this is not supported, I did find a bug in my time looking at it and I will open another issue for it.


Fix SAP XSA Deployment

There was a small typo in the XSA deployment. Now it should fit.

i'll take a look at the failing tests later - reason seems to be that there's a pointer to an internal SAP repo in package-lock.json.
change is minimal and wording-only, so will bypass CI and merge


Unable to Load Myaccount in safari

Describe the issue:
Getting an empty page when accessing My account via Safari
How to reproduce:

Start up the server
Try to access my account via the safari browser
2.1 Direct access  https://localhost:9443/myaccount
2.2. Access the console and try to SSO to my account

Expected behavior:
There shouldn't any issues when accessing my account via Safari
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: wso2is-6.0.0-beta2-SNAPSHOT
OS: MACOS Monterey 12.4 (21F79)
Database: H2
-Browse - Safari Version 15.5 (176<IP_ADDRESS>.8)
java 11.0.14 2022-01-18 LTS
Apple M1 Pro

I was not able to reproduce this issue in Safari.


Update org mgt and org mgt core versions

Purpose
$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/3386066085


FindView in RC2 vs RC1

Using Microsoft.AspNet.TestHost in RC1 I was able to return a view from an action with:
return View("~/Test");
After upgrading to Microsoft.AspNetCore.TestHost in RC2 that no longer worked, I had to use:
return View("~/Test.cshtml");
Normally when a view name is given (or not specified) it would use the following locations:
public virtual IEnumerable<string> ViewLocationFormats { get; } = new[]
{
    "/Views/{1}/{0}" + ViewExtension,
    "/Views/Shared/{0}" + ViewExtension,
};

But when a path is included like "/Test" or "~/Test" is any location searching performed?  In RC1 it seems to try the path provided and if not found it then appended ".cshtml" (ViewExtension).
I know that a custom IViewLocationExpander could be used (https://github.com/aspnet/Mvc/issues/4122), but I was curious as to why this worked in RC1 and not RC2.

We improved the view lookup process to support relative paths in RC2. One of the minor changes in that process was that absolute paths (those starting w/ '/ or ~/) no longer get the view extension added automatically -- it's an absolute path and must be complete.


Github api response limited error with correct personal access token

I'm running
docker-machine --debug --github-api-token=mytokenhere create --driver vmwarefusion default
And this is the error I'm getting, I'm not sure it even recognizes the token to begin with.
Docker Machine Version:  0.6.0, build e27fb87
Found binary path at /usr/local/bin/docker-machine
Launching plugin server for driver vmwarefusion
Plugin server listening at address <IP_ADDRESS>:50161
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(flag-lookup) Calling .GetMachineName
(flag-lookup) Calling .DriverName
(flag-lookup) Calling .GetCreateFlags
Found binary path at /usr/local/bin/docker-machine
Launching plugin server for driver vmwarefusion
Plugin server listening at address <IP_ADDRESS>:50165
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(default) Calling .GetMachineName
(default) Calling .DriverName
(default) Calling .GetCreateFlags
(default) Calling .SetConfigFromFlags
Running pre-create checks...
(default) Calling .PreCreateCheck
(default) No default Boot2Docker ISO found locally, downloading the latest release...
Error with pre-create check: "Error getting a version tag from the Github API response.\nYou may be getting rate limited by Github."
open : no such file or directory
notifying bugsnag: [Error with pre-create check: "Error getting a version tag from the Github API response.\nYou may be getting rate limited by Github."]

Closing. Seems like it needs a couple of minutes to propagate on github's side.


[To_new_mpp] add IDataBlockManager

Coverage increased (+0.03%) to 65.32% when pulling 461665b91f090f405150d6399fbb40cc39413314 on cornmonster:new_mpp into b3e564a1fb715a8a56a8bb4fcda379d7f64dec16 on apache:new_mpp.


Add options class to configure the client

Also adds ability to use test environment

I see a lot of new
using JetBrains.Annotations;
do we really need that?

I see a lot of new using JetBrains.Annotations; do we really need that?

They are compile time only. It's so Rider won't suggest refactoring to remove types because it thinks they are unused.


⚠ Bofrost.de has degraded performance

In 4a6405e, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1677 ms

Resolved: Bofrost.de performance has improved in a498951 after 55 minutes.


Fix potential crash when stack is resized

Fix a rare bug discovered in Tasmota.
When calling a virtual method or virtual member, GETMBR and GETMET indirectly call a function (native or Berry). This calls checks the stack size and may in rare circumstances resize the stack; hence relocates the stack at a different address.
Unfortunately in such case, RA() address is no more valid and still points to the old stack location. This patch stores the result to a temporary location on the C stack, and defers the computation of RA() until after the call to the function was made.

I removed the gcc warning by adding an assignment that is actually never reached. This avoids a useless initialization that would negatively impact performance.


WBC-940 Remove pause(); play() from Bitmovin setup

Coverage remained the same at 100.0% when pulling feec64c9b0f6a6bca8e177585c3651ec85e7e537 on WBC-940 into 1a049a97f5f936b9dbf08528a0b2c20cf98e8d66 on master.


Opt-in for non-nullability for org.gradle.execution.plan

Let's address this in a more general way.


”Târlișua” is listed in the drop-down menu

Description:
"Târlișua" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Târlișua" in the search bar.

Expected results
The location is listed in the drop-down menu as "Târlișua, Bistrița-Năsăud".


Put location object in store

I have a share component that needs to know when the queryString has been updated. It would be nice if there was a location object in the store or maybe even just dispatching an accessible action-type when the permalink updates (maybe there already is one?), would do the trick.
Currently doing this workaround:
history.listen((location) => {
    const newString = location.search;
    if (queryString !== newString) {
      queryString = newString;
      store.dispatch(updateQueryString(queryString)); // Keep queryString in redux-store
    }
});

Hi, we had the similar issue recently, maybe that could help: https://github.com/spotify/redux-location-state/issues/29

Thanks @tsufiev . I don't think LOCATION_POP will work for my use case since we don't want to retain the history. Ideally we would need a new action type e.g. LOCATION_REPLACE to fire every time history.replace(nextLocation) is going to be changed.

That could be tricky, since history.replace() is fired each time a store value tracked by RLS is updated - you can end up in a loop here, i.e. store changed -> histore.replace() -> LOCATION_REPLACE action is fired -> store changed -> ...

Wont fix

yeah sorry for the super late response on this (I was moving across the country), but it sounds like this was resolved :+1:


can't rip instagram

Ripme version:most recent1.7.83
Java version:  8.192
Operating system: win 10

Exact URL you were trying to rip when the problem occurred: https://www.instagram.com/theellenshow/

Expected Behavior
Detail the expected behavior here.
should rip without issue
Actual Behavior
JSONObject["rhx_gis"] not found.
any instagram link does this.

Seeing the same issue in v1.7.83

same issue v 7.83 tried only with instagram

same issue v1.7.83

Loaded log4j.properties
Initialized ripme v1.7.83
Setting locale to en_US
Loading history from /Users/xxxxx/Library/Application Support/ripme/history.json
Retrieving https://raw.githubusercontent.com/ripmeapp/ripme/master/ripme.json
This version (1.7.83) is the same or newer than the website's version (1.7.83)
Running latest version: 1.7.83
sanitized URL is https://www.instagram.com/xxxxxxxxxx/
Found album ripper: com.rarchives.ripme.ripper.rippers.InstagramRipper
sanitized URL is https://www.instagram.com/xxxxxxxxxx/
Found album ripper: com.rarchives.ripme.ripper.rippers.InstagramRipper
Using album title 'instagram_xxxxxxxxxx'
[+] Creating directory: ./rips/instagram_xxxxxxxxxx
Set working directory to: /Users/xxxxx/Desktop/rips/instagram_xxxxxxxxxx
Initializing Main thread pool with 5 threads
Retrieving https://www.instagram.com/xxxxxxxxxx/
{urlgen="{\"<IP_ADDRESS>\": 16509}:1hRix1:-saPjOmXouu-43Ru_EpCakoNRSM", mid=XN8RswALAAHX8O47213c26-BpBm8, rur=PRN, csrftoken=nhZjbvXNStXUZ38xzrGbOYUwZoP7O7zG}
https://www.instagram.com/static/bundles/metro/ProfilePageContainer.js/5a832fed3cc1.js
Got exception while running ripper:
org.json.JSONException: JSONObject["rhx_gis"] not found.
	at org.json.JSONObject.get(JSONObject.java:473)
	at org.json.JSONObject.getString(JSONObject.java:654)
	at com.rarchives.ripme.ripper.rippers.InstagramRipper.getURLsFromJSON(InstagramRipper.java:246)
	at com.rarchives.ripme.ripper.AbstractJSONRipper.rip(AbstractJSONRipper.java:58)
	at com.rarchives.ripme.ripper.AbstractRipper.run(AbstractRipper.java:616)
	at java.base/java.lang.Thread.run(Thread.java:834)
Waiting for threads to finish
   Rip completed!
Deleting empty directory /Users/xxxxx/Desktop/rips/instagram_xxxxxxxxxx
^CSaved window position (x=291, y=154, w=854, h=518)

same issue, latest version

Confirmed

+1
Getting same issue.


Refactorings around CaptureRef

Builds on #20566
Breaks out CaptureRef into a separate file and concentrates all operations on CaptureRef in it.
Moves extension methods on CaptureRef into CaptureRef itself or into CaptureOps.

I integrated this PR in #20566


Move graph struct for reuse for curation

[ ] All tests passed. If this feature is not already covered by the tests, I added new tests.
[ ] All static analysis checks passed.
[ ] This pull request is on the dev branch.
[ ] I used gofmt for formatting the code before submitting the pull request.

I have read the CLA Document and I hereby sign the CLA


Several suggestions on the release version available for production

Several suggestions for reaching the release version available for production.
I forked the envoy gateway project one month ago and successfully put it into production. But there are many problems。
1、Data efficiency：Optimize data synchronization efficiency, reconstruct the code of provider/kubernetes, match different processing logic for different k8s resources, and use different informers and queues to subscribe to data
2、Support Eds：In the past, most of the ingress/gateway projects support direct connection to endpoints.  Using service as lbEndpoint will increase 1-hop NAT request and will be limited to the number of five tuple ports And cannot setting the weight of special endpoints
3、Data validation：When the data structure of httproute is translator to the data structure of xds, the pushed data will be rejected by the envoy if necessary checks are not made. There are many existing validate, unique validate, route weights validate, which require to do a lot of work
4、Transmission queue：The watchablemap currently used by the eg project is a map structure, which determines that val will be overwritten and data will be out of order. The data synchronization process generally requires FIFO
5、Common  capabilities：Websocket, retry, and timeout are commonly used functions of the http gateway and need to be implemented quickly,  I use the route configuration yaml fragment as annotation，It is recommended to use the simplest way
6、Ingress compatibility:  There are a large number of data using the ingress API in production, and translation compatibility is required to achieve smooth replacement
7、Envoy Deployment： Allow User  modify the yaml of envoy deployment, including replicas, scheduling rules, labels, etc... Optional generate service load balancer
8、 XDS Incremental update: In the case of very much data, it is very slow to generate a full amount of data each time and submit it to XDS. XDS requires an incremental update of data. For example, the change push of endpoints will be fast
9、XDS SSL： The eg uses a self signed SSL certificate, but does not provide an upgrade method. By default, it only expires in one year. The best way is to let users customize the expiration time
10、IR Data: The translation of intermediate fields will result in the loss of a large number of XDS useful configurations. It is recommended to give up
My simple datapath：
HTTPRoute deps serivce、endpoints、geteway Has Synced

informer-> gateway watch-> addListenerIndex
informer-> service watch-> addServiceIndex
informer-> endpoints watch-> notifyEDS -> XDS Incremental update
informer-> HTTPRoute watch-> notifyCDS、notifyRDS、notifyEDS -> queue.length == 0 notifyLDS -> XDS
informer-> Ingress watch-> translator -> create/patch HTTPRoute

thanks for spending the cycles to test out Envoy Gateway @zhshw, responded to individual issues


Add make as an option for running tests

Codecov Report

Merging #144 (e313604) into main (7f2d4c6) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #144   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          668       668
=========================================
  Hits           668       668

Continue to review full report at Codecov.

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


WPF app start failed when host custom control with xaml islands

I try to this https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/host-custom-control-with-xaml-islands, but the exe will start failed when Add a control from the WinUI 2 library to the custom control,  not any error report when build, I try downgrade to 2.7 2.6 2.5, but problem still exists.
I tried to search in google and issues, but didn't find any solution, is there any way to solve this problem?
env:
WinOS: Win10 21H2
VS: vs2022
microsoft-ui-xaml: 2.8.2
full start log:
'WpfApp1.exe' (CoreCLR: DefaultDomain): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Private.CoreLib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'F:\Desktop\bkcode\BKTrans\WpfApp1\bin\x64\Debug\netcoreapp3.1\WpfApp1.dll'. Symbols loaded.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Runtime.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'F:\Desktop\bkcode\BKTrans\WpfApp1\bin\x64\Debug\netcoreapp3.1\App1.exe'. Symbols loaded.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'F:\Desktop\bkcode\BKTrans\WpfApp1\bin\x64\Debug\netcoreapp3.1\Microsoft.Toolkit.Win32.UI.XamlHost.winmd'. Module was built without symbols.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\windows\system32\WinMetadata\Windows.UI.Xaml.winmd'. Module was built without symbols.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\mscorlib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Runtime.InteropServices.WindowsRuntime.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.32\PresentationFramework.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.32\WindowsBase.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.32\System.Xaml.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'D:\Microsoft Visual Studio\2022\Community\Common7\IDE\PrivateAssemblies\Runtime\Microsoft.VisualStudio.Debugger.Runtime.NetCoreApp.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\netstandard.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Runtime.InteropServices.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Threading.ThreadPool.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Collections.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Diagnostics.TraceSource.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Text.RegularExpressions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Runtime.Extensions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Threading.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Buffers.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\Microsoft.Win32.Registry.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Diagnostics.Debug.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'F:\Desktop\bkcode\BKTrans\WpfApp1\bin\x64\Debug\netcoreapp3.1\Microsoft.UI.Xaml.winmd'. Module was built without symbols.
Exception thrown: 'System.TypeLoadException' in App1.exe
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Diagnostics.StackTrace.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Reflection.Metadata.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.IO.FileSystem.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Collections.Immutable.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\windows\system32\WinMetadata\Windows.Foundation.winmd'. Module was built without symbols.
'WpfApp1.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.32\System.Diagnostics.Tools.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The program '[25816] WpfApp1.exe' has exited with code<PHONE_NUMBER> (0xc000027b).

oh, my fault, I need to install prerelease
Note

If your desktop app is packaged in an [MSIX package](https://learn.microsoft.com/en-us/windows/msix), you can use either a prerelease or release version of the [Microsoft.UI.Xaml](https://www.nuget.org/packages/Microsoft.UI.Xaml) NugGet package.
If your desktop app is not packaged using MSIX, you must install a prerelease version of the [Microsoft.UI.Xaml](https://www.nuget.org/packages/Microsoft.UI.Xaml) NuGet package.


Add Error Handling to Execution Context

Pull Request Description

close #732
PR adds error handling. Execution Context catches the errors when executing the stack and notifies the user.
Changelog:

update: add error handling to the Execution Context
add: ExectuionFailedError to Language Server API

Changelog
Important Notes

Language Server API is extended with:
ExecutionFailedError
Signals that execution of a context failed.
"error" : {
  "code" : 2009,
  "message" : "Execution failed"
}

Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the Scala, Java, Rust or Haskell style guides as appropriate.
[x] All code has been tested where possible.

Changelog:

update: return more specific errors


fix(entity): Refactored to remove padding

base64.StdEncoding (default): Adds padding characters (=) during encoding for compatibility with standard base64. It removes padding during decoding.
base64.RawStdEncoding: Omits padding characters during encoding and expects the input string to not have any padding during decoding (throws error if present).

@NSSPKrishna please take a look at the lint failures


Adding PenguBot

Prefix is customizable and also works if you tag the bot instead of the prefix :)
This pull request was created using the https://discordbots.co.uk/edit menu.

Thanks :)


Add getting started

Could you elaborate what would be the purpose of getting started?? there is a CODETOUR.md and CONTRIBUTION.md already.


Table collapsed data should open when we click on row instead of arrow.

Hi, I would like report UX issue of table with collapsed data feature.
Right now in vuesax if we want to open collpased data then I have to click on arrow on right but UX wise that collapsed data should open if I click anywhere in that table row.
https://lusaxweb.github.io/vuesax/components/table.html#expandable-data

The functionality was added in the latest version

it should be possible to choose, because when you want to use inside vs-td custom component to edit inline, there is a confllict with expandable slot
TypeError: Cannot read property 'classList' of null
at VueComponent.clicktd (vuesax.common.js?fb9a:10384)

I can no more combine select checkbox and expanded table now. On click on the row, expanded table does not appear, instead the checkbox is checked. Please provide a fix to permit both to be used at the same time.

En el ejemplo al hacer click, el area expandible no muestra nada


Add PNPM to the list of supported package managers.

NB: PNPM support hasn't landed just yet. The PR is just about ready. I've marked this PR as "do not merge", but I'd like to put it through the review cycle presently while we're finishing up the engine change.
Description
Pulumi is adding official support for PNPM as a Node package manager. This commit updates the docs with instructions on using PNPM, and explains the precedence order between our officially supported package managers.
Checklist:

[x] I have reviewed the style guide.
[ ] If blogging, I have reviewed the blogging guide.
[x] I have manually confirmed that all new links work.
[ ] I added aliases (i.e., redirects) for all filename changes.
[ ] If making css changes, I rebuilt the bundle.

For reference, here's the PR for the code change. Once this is in, we can remove the DNM label.
https://github.com/pulumi/pulumi/pull/13055


Version Packages

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Patch Changes

Updated dependencies [721425b3]:

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

#2664 721425b3 Thanks @acao! - This reverts the bugfix for .graphqlrc.ts users, which broke the extension for schema url users

<EMAIL_ADDRESS>Patch Changes

#2664 721425b3 Thanks @acao! - This reverts the bugfix for .graphqlrc.ts users, which broke the extension for schema url users

Updated dependencies [721425b3]:

<EMAIL_ADDRESS>

I still have problems with v0.7.4 version of graphql-vscode and  .graphqlrc.ts is that still an issue? I couldn't find issue with tracking this bug, should I create one? 🤔
Failed to compile TypeScript: Debug Failure. False expression: Non-string value passed to `ts.resolveTypeReferenceDirective`, likely by a wrapping package working with an outdated `resolveTypeReferenceDirectives` signature. This is probably not a problem in TS itself.
for more information on using 'graphql-config' with 'graphql-language-service-server',
see the documentation at https://www.npmjs.com/package/graphql-language-service-server#user-content-graphql-configuration-file


AuthorizationStrategy returns the wrong HTTP status code for certain auth failure cases

This is a bit of a nitpick, but some clients might take different actions depending on what 40X code was returned due to an authorization failure.
Try the example included in the docs:

@auth("admin")
@get("/admin")
async def only_for_administrators():
    # This method requires "admin" role in user's claims
    return ok("example")

If you attempt to access this endpoint as a logged in but non-admin user, the request fails with 401 Unauthorized when it perhaps should have returned a 403 Forbidden.
Documentation for 401 Unauthorized says:

The HyperText Transfer Protocol (HTTP) 401 Unauthorized response status code indicates that the client request has not been completed because it lacks valid authentication credentials for the requested resource.
This status code is sent with an HTTP WWW-Authenticate response header that contains information on how the client can request for the resource again after prompting the user for authentication credentials.

In other words, 401 Unauthorized is returned when a client hasn't provided valid credentials (no or invalid auth token, not logged in, etc.). If a client receives this error code, it might show a login prompt (as with HTTP Basic auth) or redirect the user to a login page.
Documentation for 403 Forbidden says:

The HTTP 403 Forbidden response status code indicates that the server understands the request but refuses to authorize it.
This status is similar to 401, but for the 403 Forbidden status code, re-authenticating makes no difference. The access is tied to the application logic, such as insufficient rights to a resource.

Meaning the user has provided valid credentials, but they aren't permitted to access the resource. A client might show an error message, but wouldn't prompt the user to log in.
The AuthorizationStrategy always seems to return a 401 Unauthorized error when it fails. It could be improved by providing a way to specify the manner in which the authorization failed, whether it be from missing credentials vs insufficient permissions.
This would allow a client to know the difference between having no permissions (403) vs the login being invalid or the session being expired (401) so it can take some action to re-authenticate.
Some users might want to even override the status code returned for either case: for some endpoints, if a user has insufficient permissions, they might want to return a 404 Not Found to deny the existence of the resource instead of revealing that a resource exists, but a user is not allowed to access it.
I am currently working around this by raising Forbidden in my Requirement class, but this short-circuits the processing of the rest of the policy.

@waweber again, very good feedback. You are right (I was considering this in the past, too, when I came across a conversation on this subject on StackOverflow). I will wrap my mind around this and prioritize to improve the feature.

Fixed at 1.2.17.


OCPBUGS-11395: Remove stale kubeconfigs

Remove any kubeconfig that is not part of the hostname or SAN values in configuration.

Which issue(s) this PR addresses:

Closes #

/retest

This is a good candidate for an automated test. Do we have the parts in place to add a test like that in this PR, or is the work to make that possible still in progress?

This is a good candidate for an automated test. Do we have the parts in place to add a test like that in this PR, or is the work to make that possible still in progress?

We could make it but not on this PR until https://github.com/openshift/microshift/pull/1557 merges. That way we can include it in a new e2e test that does not need another VM in CI.

This is a good candidate for an automated test. Do we have the parts in place to add a test like that in this PR, or is the work to make that possible still in progress?

We could make it but not on this PR until #1557 merges. That way we can include it in a new e2e test that does not need another VM in CI.

If the cleanup function took a directory name as argument, we could have some tests for it in the unit test framework.

This is a good candidate for an automated test. Do we have the parts in place to add a test like that in this PR, or is the work to make that possible still in progress?

We could make it but not on this PR until #1557 merges. That way we can include it in a new e2e test that does not need another VM in CI.

If the cleanup function took a directory name as argument, we could have some tests for it in the unit test framework.

Done

/test e2e-loadbalancer-smoke-test


Start migrating "MapConfigService" to State Tree

The MapConfigService needs to be deprecated and replaced with a dedicated part of the state tree which holds the critical map information.
This is a start on that in order to support some of the work being done by @CarlyLanglois .

With @bartvde 's approval, i'm merging this in since we're using the improvements in other components.


OHRI-1992 OHRI-1993 Enrol and disenrol client from TB program upon saving of TB enrolment form

Requirements

[ ] This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes the ticket number in the format OHRI-123 My PR title.
[ ] My work includes tests or is validated by existing tests.

Summary
This PR introduces a post submission handler that adds a client to the TB program upon successful submission of the TB enrolment form.
It also removes the client from the program when the outcome date is filled.
Screenshots
Addition to the program
https://github.com/UCSF-IGHS/openmrs-esm-ohri/assets/12844964/9e5b92f7-de29-4236-9b42-4e8d0344a465
Removal/Completion of the program
https://github.com/UCSF-IGHS/openmrs-esm-ohri/assets/12844964/71a23899-621b-4164-9fc4-6fff8eb19ed0
Related Issue

Other

Closing this as it was resolved by https://github.com/openmrs/openmrs-form-engine-lib/pull/160