Crash occur when multiple teams exist in App Store Connect

New Regression Checklist

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

Regression Information

Breaking version: 2.205.0
Last working version: 2.204.3

Regression Description

fastlane deliver crashed.
It seems to be caused by having multiple App Store Connect teams.
Note that the crash did not occur when the team id was specified in the environment variable FASTLANE_ITC_TEAM_ID.
<EMAIL_ADDRESS>bundle exec fastlane deliver // NG
<EMAIL_ADDRESS>bundle exec fastlane deliver download_metadata // NG
<EMAIL_ADDRESS>FASTLANE_ITC_TEAM_ID=ZZZZ bundle exec fastlane deliver // OK
<EMAIL_ADDRESS>FASTLANE_ITC_TEAM_ID=ZZZZ bundle exec fastlane deliver download_metadata // OK

Complete output when running fastlane, including the stack trace and command used

✅ fastlane deliver download_metadata output ✅
<EMAIL_ADDRESS>bundle exec fastlane deliver download_metadata
[✔] 🚀
[11:45:01]: Successfully loaded '/Users/XXXX/Develop/tp/fastlane/Deliverfile' 📄

+-----------------------+-----------------------+
| Detected Values from './fastlane/Deliverfile' |
+-----------------------+-----------------------+
| app_identifier        | com.tp                |
| languages             | ["ja", "en-US"]       |
| submit_for_review     | false                 |
| force                 | true                  |
| skip_screenshots      | true                  |
| skip_metadata         | false                 |
| skip_binary_upload    | true                  |
+-----------------------+-----------------------+

[11:45:01]: Login to App Store Connect<EMAIL_ADDRESS>Multiple App Store Connect teams found, please enter the number of the team you want to use:
Note: to automatically choose the team, provide either the App Store Connect Team ID, or the Team Name in your fastlane/Appfile:
Alternatively you can pass the team name or team ID using the `FASTLANE_ITC_TEAM_ID` or `FASTLANE_ITC_TEAM_NAME` environment variable

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

➡  [supply] added support for refresh tokens as an authentication method
    https://github.com/fastlane/fastlane/pull/16414 [open] 10 💬
    23 May 2020

➡  Undefined method shellscape for nil:NilClass
    https://github.com/fastlane/fastlane/issues/19709 [closed] 1 💬
    4 weeks ago

➡  snapshot doesn't seem to work for macOS apps
    https://github.com/fastlane/fastlane/issues/18709 [open] 8 💬
    3 weeks ago

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

🔗  You can ⌘ + double-click on links to open them directly in your browser.
bundler: failed to load command: fastlane (/Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/bin/fastlane)
Traceback (most recent call last):
	34: from /Users/XXXX/.rbenv/versions/2.6.5/bin/bundle:23:in `<main>'
	33: from /Users/XXXX/.rbenv/versions/2.6.5/bin/bundle:23:in `load'
	32: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/exe/bundle:37:in `<top (required)>'
	31: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/friendly_errors.rb:130:in `with_friendly_errors'
	30: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/exe/bundle:49:in `block in <top (required)>'
	29: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/cli.rb:24:in `start'
	28: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	27: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/cli.rb:30:in `dispatch'
	26: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	25: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	24: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	23: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/cli.rb:474:in `exec'
	22: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/cli/exec.rb:28:in `run'
	21: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/cli/exec.rb:63:in `kernel_load'
	20: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/cli/exec.rb:63:in `load'
	19: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/bin/fastlane:23:in `<top (required)>'
	18: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/bin/fastlane:23:in `load'
	17: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/bin/fastlane:23:in `<top (required)>'
	16: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/fastlane/lib/fastlane/cli_tools_distributor.rb:114:in `take_off'
	15: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/deliver/lib/deliver/commands_generator.rb:18:in `start'
	14: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/deliver/lib/deliver/commands_generator.rb:187:in `run'
	13: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in `run!'
	12: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in `run!'
	11: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in `run_active_command'
	10: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:157:in `run'
	 9: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:187:in `call'
	 8: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/deliver/lib/deliver/commands_generator.rb:164:in `block (2 levels) in run'
	 7: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/deliver/lib/deliver/commands_generator.rb:164:in `new'
	 6: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/deliver/lib/deliver/runner.rb:23:in `initialize'
	 5: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/deliver/lib/deliver/runner.rb:43:in `login'
	 4: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/spaceship/lib/spaceship/connect_api/spaceship.rb:85:in `login'
	 3: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/spaceship/lib/spaceship/connect_api/client.rb:69:in `login'
	 2: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/spaceship/lib/spaceship/tunes/tunes_client.rb:91:in `select_team'
	 1: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/spaceship/lib/spaceship/tunes/tunes_client.rb:91:in `loop'
/Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/spaceship/lib/spaceship/tunes/tunes_client.rb:98:in `block in select_team': undefined method `[]' for nil:NilClass (NoMethodError)
	34: from /Users/XXXX/.rbenv/versions/2.6.5/bin/bundle:23:in `<main>'
	33: from /Users/XXXX/.rbenv/versions/2.6.5/bin/bundle:23:in `load'
	32: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/exe/bundle:37:in `<top (required)>'
	31: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/friendly_errors.rb:130:in `with_friendly_errors'
	30: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/exe/bundle:49:in `block in <top (required)>'
	29: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/cli.rb:24:in `start'
	28: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	27: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/cli.rb:30:in `dispatch'
	26: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	25: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	24: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	23: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/cli.rb:474:in `exec'
	22: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/cli/exec.rb:28:in `run'
	21: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/cli/exec.rb:63:in `kernel_load'
	20: from /Users/XXXX/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bundler-2.2.19/lib/bundler/cli/exec.rb:63:in `load'
	19: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/bin/fastlane:23:in `<top (required)>'
	18: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/bin/fastlane:23:in `load'
	17: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/bin/fastlane:23:in `<top (required)>'
	16: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/fastlane/lib/fastlane/cli_tools_distributor.rb:114:in `take_off'
	15: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/deliver/lib/deliver/commands_generator.rb:18:in `start'
	14: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/deliver/lib/deliver/commands_generator.rb:187:in `run'
	13: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in `run!'
	12: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in `run!'
	11: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in `run_active_command'
	10: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:157:in `run'
	 9: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/commander-4.6.0/lib/commander/command.rb:187:in `call'
	 8: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/deliver/lib/deliver/commands_generator.rb:164:in `block (2 levels) in run'
	 7: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/deliver/lib/deliver/commands_generator.rb:164:in `new'
	 6: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/deliver/lib/deliver/runner.rb:23:in `initialize'
	 5: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/deliver/lib/deliver/runner.rb:43:in `login'
	 4: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/spaceship/lib/spaceship/connect_api/spaceship.rb:85:in `login'
	 3: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/spaceship/lib/spaceship/connect_api/client.rb:69:in `login'
	 2: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/spaceship/lib/spaceship/tunes/tunes_client.rb:91:in `select_team'
	 1: from /Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/spaceship/lib/spaceship/tunes/tunes_client.rb:91:in `loop'
/Users/XXXX/Develop/tp/vendor/bundle/ruby/2.6.0/gems/fastlane-2.205.0/spaceship/lib/spaceship/tunes/tunes_client.rb:98:in `block in select_team': [!] undefined method `[]' for nil:NilClass (NoMethodError)

Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
12.2.1

Ruby
2.6.5

Bundler?
true

Git
git version 2.32.0 (Apple Git-132)

Installation Source
~/Develop/tp/vendor/bundle/ruby/2.6.0/bin/fastlane

Host
macOS 12.2.1 (21D62)

Ruby Lib Dir
~/.rbenv/versions/2.6.5/lib

OpenSSL Version
OpenSSL 1.1.1k  25 Mar 2021

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
13.2.1

Swift Version
5.5.2

System Locale

Variable
Value

LANG
ja_JP.UTF-8
✅

LC_ALL

LANGUAGE

fastlane gems

Gem
Version
Update-Status

fastlane
2.205.0
✅ Up-To-Date

generated on: 2022-03-18

The issue description include the output of fastlane env.

We got the same issue #20086


Fix indentation

Description
Adjusts the indentation of the source files to a more modern and easy to read style
Changes Made
Tweaked a bit of the formatting
Related Issues
N/A
Additional Notes
:3

lbtm


Adding metadata_body to SAML config

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Would be good if we have some concrete description of the code change/addition?

@palashhedau updated the description.


Game browsing should open in new tab

There are a bunch of clicks right now to get back to https://ldjam.com/games so I think either we need a link at the top like My Game or we need the games feeds to open in new tabs when you click on them. I get that this breaks the logic of internal pages open in same tab, but I think it will be helpful. We want retain people voting and commenting on games as long as possible so they need to end up in game selection as quickly and easily as possible.

Why not Ctrl+left-click or middle-click or right-click or long-press on mobile. This is a built in feature of every browser i've ever used. I don't think it's some thing we need to duplicate.

Well it is too easy to simply click and then it is a bit of a hassle to get back to the game list and really I see it as our job to make the site so people keep rating game when they've started. Previous site you automatically got back to games list after voting. That doesn't work now, but we need something that makes transition to next game really easy.
But if #952 is implemented and perhaps adds a banner at the very bottom too, especially on game pages, then this is a non-issue.

A Back To Games button at the bottom of the game post seems like a reasonable idea.
It could appear once you've rated > 1 catogorey.

That would be nice, especially if we deal with pagination and that link actually sends you back to where in the feed you were.


Update textarea component for window events

Fix for issue #7620.
Added 'load' and 'resize' window event listeners to the textarea component. These changes are to ensure that, when using autosize, the textarea height is correct when the window is loaded or resized. This improves the responsiveness of the textarea component in different window sizes.

[x] Changes have been thoroughly tested to not break existing functionality.
[x] New functionality has been documented or existing documentation has been updated to reflect changes.
[x] Visual changes are explained in the PR description using a screenshot/recording of before and after.

This is are the examples of how the textarea appears before the fix:

when typing and firing the 'input' event that calls the render() function that correctly updates the height

when the page is reloaded the textarea goes back to the default height

when changing windows width the textarea does not update

After the fix the height is always correct in both cases.

Thanks!

As @zepfietje suggested x-init can indeed be used, one problem is that after saving the text area returns to default height. This can be fixed by adding wire:ignore. Plus idk why x-on:resize.window="render()" was added since it only works when you resize the browser's window.

@qrasa1 you are correct wire:ignore fixes height reset on save. I added the event on browser resize for the times like when you have the browser in full screen and then you split in half to copy some data from another window. I think this is a common behavior for single monitor users.


Updates for bamboo_phoenix

Issue
Better local preview for text-only emails #5
Changes in this PR

Updates its dependencies
Fix a bug
Updates docs

This PR also applies the same changes from another PR.

@germsvel just in case you didn't receive a notification I comment your name here.

Hi @silvagustin, thanks for the work here! I no longer work at thoughtbot or maintain Bamboo. And unfortunately, I don't have write access to this repo.

Hi @silvagustin, thanks for the work here! I no longer work at thoughtbot or maintain Bamboo. And unfortunately, I don't have write access to this repo.

Oh, sorry to bother you 😬.

No bother at all! Just sorry I can't help.


Update to mobile-detect version 2.8.33 (2019-02-2018)

Made some updates to pull in latest tablets/phones, etc. based on v. 2.8.33 of mobile-detect: https://github.com/serbanghita/Mobile-Detect/blob/master/Mobile_Detect.php

@hgoebl


TrustedHostsNetworkResolver - Private network IPs should not be a valid result

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For

When choosing the X-Forwarded-For client IP address closest to the client (untrustworthy and not for security-related purposes), the first IP from the leftmost that is a valid address and not private/internal should be selected. ("Valid" because spoofed values may not be IP addresses at all; "not internal/private" because clients may have used proxies on their internal network, which may have added addresses from the private IP space.)

A test cases could be:
'private networks IPv4 are invalid' => [
  'remoteAddr' => '<IP_ADDRESS>',
  'trustedHosts' => [
     'hosts' => ['<IP_ADDRESS>'],
     'ipHeaders' => [[TrustedHostsNetworkResolver::IP_HEADER_TYPE_RFC7239, 'forwarded']],
  ],
  'headers' => ['forwarded' => ['for=<IP_ADDRESS>']],
  'expectedClientIp' => '<IP_ADDRESS>',
],
'private networks IPv6 are invalid' => [
  'remoteAddr' => '<IP_ADDRESS>',
  'trustedHosts' => [
     'hosts' => ['<IP_ADDRESS>'],
     'ipHeaders' => [[TrustedHostsNetworkResolver::IP_HEADER_TYPE_RFC7239, 'forwarded']],
  ],
  'headers' => ['forwarded' => ['for=fd12:3456:789a:1::1']],
  'expectedClientIp' => '<IP_ADDRESS>',
]

Both <IP_ADDRESS> and fd12:3456:789a:1::1 are from private network so we consider these are invalid.

@samdark Is it required for 1.0?

Yes.

@samdark Does it apply to X-Forwarded-For only? Seems it contradicts with https://datatracker.ietf.org/doc/html/rfc7239#section-6.1:

6.1.  IPv4 and IPv6 Identifiers
...
Note that the IP address may be one from the internal nets, as defined in RFC1918 and RFC4193.


Fix bug in sending email

Coverage increased (+0.04%) to 53.927% when pulling 0a80d7fee2ad8a7521d1abc9499e9c38a5246d3e on ywk253100:170303_bugfix into ac6c26d6dbe6456eb0ed20b8d5c852fe2f61801b on vmware:dev.


[SPARK-15046] When running hive-thriftserver with yarn on a secure

What changes were proposed in this pull request?
Changed it so when you ask for the variable
"spark.yarn.token.renewal.interval" from sparkConf you get it as Time
instead of Long as thats how its stored.
How was this patch tested?
Built from source and ran Hive-thriftserver against a secure cluster.

Can one of the admins verify this patch?

I ran into the same exception. I use 2.0.0-preview releases. And I ran  spark-shell on yarn.

@trystanleftwich  to clarify you get this exception because you are specifying the config in ms, or the default value is causing this exception?

Jenkins, test this please

Test build #59397 has started for PR 12824 at commit 1c48d07.

Test build #59397 has finished for PR 12824 at commit 1c48d07.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59397/
Test PASSed.

@tgravescs This was the default value that was causing this error.

Could you update the title to match what the change is about? It doesn't say anything currently.

sorry I haven't gotten back to this to understand it. do you know if something changed such that it now comes out with the ms (86400079ms) in 2.0?  When I did a quick look it didn't look like (24 hours).toMillis would return that.

@tgravescs the problem is this code in Client.scala:
sparkConf.set(TOKEN_RENEWAL_INTERVAL, renewalInterval)

That will write the value to the config with the ms suffix. I think it would be better to move the TOKEN_RENEWAL_INTERVAL definition to the core module's config list, so that the code that reads it can also just use the constant instead of using its own parsing code. It shouldn't need a default either, since that config is set when it's needed (which why the config entry is defined as optional).

@trystanleftwich could you make the changes suggested above? thx

@trystanleftwich are you planning to update this PR? Otherwise I'll fix this up and send a separate PR. If I don't hear from you until tomorrow I'll do that, since we need to fix this for 2.0.

@vanzin please take it, I don't have time to finish this off. Apologies.


Could not open page

I'm testing Mobile Web using selendroid with Java. What i want is to open a web page, the page is:
https://admin.mycompany.com/login/

I can go there ONLY if I'm connected to the internal company network, and when I'm connected to my company network and open the browser I can see the page.
The page has a certificate, self-signed and even if I set capabilities to "acceptSslCerts" I can't go to that page.
The webview of selendroid shows me "Web page not available".
In the same session I can go to other pages, like www.google.com and also to https pages (because this are not self-signed?? Don't know..).
The server log shows me nothing, returned value from selendroid server is void, example:
Jan 15, 2014 12:44:10 PM io.selendroid.server.handler.RequestRedirectHandler handle
INFO: return value from selendroid android server:
Here is the code snippet:
SelendroidLauncher selendroidServer = null;
SelendroidConfiguration config = new SelendroidConfiguration();
config.setShouldKeepAdbAlive(false);
config.setVerbose(true);
config.setRestartAdb(false);
config.setSelendroidServerPort(5555);
config.setServerHost("http://localhost:5555/wd/hub");
WebDriver driver = null;
SelendroidServer = new SelendroidLauncher(config);
selendroidServer.lauchSelendroid();

DesiredCapabilities caps = SelendroidCapabilities.android();
//caps.setCapability("acceptSslCerts", true);
driver = new SelendroidDriver("http://localhost:5555/wd/hub", caps);
driver.get("https://admin.mycompany.com/login/");

Any idea? What I can do the understand the problem? Seems that
    config.setVerbose(true);

Doesn't write more information than INFO level

I'm closing this issue due to inactivity.
If is a question rather than an issue, please send questions to the selendroid user group.
If you think it's an actual problem with selendroid and still experience the issue described on the latest release of selendroid feel free to file a new issue. If you do please provide a concise reproducible test case and describe what results you are seeing and what results you expect.


fix: change get workflow to return 404 on non-existent workflow

fixes #107
updated changelog with hacktoberfest changes

Codecov Report

Merging #408 (61f1c49) into main (a16fc22) will increase coverage by 0.07%.
The diff coverage is 100.00%.

:exclamation: Current head 61f1c49 differs from pull request most recent head e7427fa. Consider uploading reports for the commit e7427fa to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #408      +/-   ##
==========================================
+ Coverage   70.11%   70.18%   +0.07%
==========================================
  Files          11       11
  Lines        2048     2053       +5
==========================================
+ Hits         1436     1441       +5
  Misses        510      510
  Partials      102      102

Impacted Files
Coverage Δ

service/handlers.go
62.22% <100.00%> (+0.18%)
:arrow_up:

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 a16fc22...e7427fa. Read the comment docs.


Code command line add a --list-enabled-extensions

Currently you can only list all extensions. It would be useful to only list the enabled extensions.

@egamma
trolling around for things to help out on... I think this is still open, I don't see it on the command line options yet.
Shall I do a PR on this ?

This cannot be help wanted unless we provide SQLite storage access for CLI which is something to build with care.

Just ran into this problem, would love this feature, but I have no idea how to upvote this, do I do it here on this issue?


MAINT: Use PyBIDS 0.9.x via niworkflows PR

Closes #776.

Travis failure is just whining about the URL in setup. Will be resolved once niworkflows has a release.

@oesteban I suspect this is something you'll know more about:
Traceback (most recent call last):
  File "/usr/local/miniconda/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
    self.run()
  File "/usr/local/miniconda/lib/python3.7/multiprocessing/process.py", line 99, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/local/miniconda/lib/python3.7/site-packages/mriqc/bin/mriqc_run.py", line 418, in init_mriqc
    wf_list.append(build_workflow(dataset[mod], mod, settings=settings))
  File "/usr/local/miniconda/lib/python3.7/site-packages/mriqc/workflows/core.py", line 25, in build_workflow
    workflow = fmri_qc_workflow(dataset, settings=settings)
  File "/usr/local/miniconda/lib/python3.7/site-packages/mriqc/workflows/functional.py", line 111, in fmri_qc_workflow
    ema = epi_mni_align(settings)
  File "/usr/local/miniconda/lib/python3.7/site-packages/mriqc/workflows/functional.py", line 718, in epi_mni_align
    template_resolution=2, ),
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/mixins/reporting.py", line 32, in __init__
    super(ReportCapableInterface, self).__init__(**kwargs)
  File "/usr/local/miniconda/lib/python3.7/site-packages/niworkflows/interfaces/mni.py", line 100, in __init__
    super(RobustMNINormalization, self).__init__(**inputs)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 175, in __init__
    self.inputs = self.input_spec(**inputs)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/specs.py", line 67, in __init__
    super(BaseTraitedSpec, self).__init__(**kwargs)
  File "/usr/local/miniconda/lib/python3.7/site-packages/traits/trait_handlers.py", line 172, in error
    value )
traits.trait_errors.TraitError: The 'moving' trait of a RobustMNINormalizationInputSpecRPT instance must be 'T1w' or 'boldref', but a value of 'bold' <class 'str'> was specified.

We can naively replace bold with boldref here:
https://github.com/poldracklab/mriqc/blob/f38b344655e37b25e7e8f6af373f8c361874a7b8/mriqc/workflows/functional.py#L710
But I'm not sure if that's actually appropriate.

It is actually necessary - https://github.com/poldracklab/niworkflows/pull/368
I forgot to check on MRIQC when merged that PR.

It is actually necessary - poldracklab/niworkflows#368
I forgot to check on MRIQC when merged that PR.

To be clear, I should change that to boldref, or we need to restore bold to the interface options?

It is boldref now, you have to change it. Sorry for the confusion
On Fri, Jul 12, 2019, 10:15 Chris Markiewicz<EMAIL_ADDRESS>wrote:

It is actually necessary - poldracklab/niworkflows#368
https://github.com/poldracklab/niworkflows/pull/368
I forgot to check on MRIQC when merged that PR.
To be clear, I should change that to boldref, or we need to restore bold
to the interface options?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/mriqc/pull/796?email_source=notifications&email_token=AAESDRTQJO5VTNQLOOVLKNTP7C325A5CNFSM4H7F2ZEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ2LDRY#issuecomment-510964167,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAESDRV2BRBM3VQ4WWGTJC3P7C325ANCNFSM4H7F2ZEA
.


Update compose-version to 1.24.0

https://github.com/docker/compose/releases/tag/1.24.0
ping @ulyssessouza @chris-crone PTAL

Deploy preview for docsdocker ready!
Built with commit 7bbff2a2ee0a82228ad452aa0b2a7633426a433d
https://deploy-preview-8544--docsdocker.netlify.com

LGTM

Thank you, @thaJeztah and @ulyssessouza .


pose_data.py throws an error because it needs the data used for the evaluation step.

The following line in pose_data.py assumes data that is downloaded  in the evaluation section. I think the README.md should be updated accordingly.
https://github.com/mentian/object-deformnet/blob/a2dcdb87dd88912c6b51b0f693443212fde5696e/preprocess/pose_data.py#L298-L304

hi，how did you deal with error about obj_models/val/02876657/d3b53f56b4a7b3b3c9f016d57db96408/model.obj？


is C:\Users\acer\AppData\Roaming\Microsoft\Internet Explorer\UserData\Low safe?

i saw a file named "internet explorer" which had a thing called "screen sharer" my apps on my hotbar. and some more info about me

This is an artifacts path used by the Internet Explorer browser. If you have concerns about it I suggest scanning it with an Antivirus software.
In any case the tool doesn't consider it a suspicious path


WSL2 reports incorrect root storage size (1007G)

Windows Version
Microsoft Windows [Version 10.0.22635.4291]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-2
Distro Version
Ubuntu 24.04
Other Software
No response
Repro Steps
Inside Ubuntu 24.04 (or any other distribution),
run the following:
df -h /

then
df -h /mnt/<letter> [/mnt/<letter2> ...] # (All the accessible *internal* drives)

Expected Behavior
The output ideally should have the Size column with data matching the size of my disk.
Actual Behavior
Output of df -h /
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdc       1007G  2.7G  954G   1% /

Output of df -h /mnt/c /mnt/d (all the available internal drives of my laptop)
Filesystem      Size  Used Avail Use% Mounted on
C:\             477G  126G  351G  27% /mnt/c
D:\              75G  7.7G   68G  11% /mnt/d

The size of the SSD (the only one) on my laptop is, according to WSL2, more than 512G (the actual size)
and this piece of information almost fooled me.
Diagnostic Logs
No response

Duplicate of #10824


Error Involving the PsychLua Folder

Describe your bug here.
Mind you, if you are modding, please try testing your bug in a clean version of the engine instead, this ensures the bug is actually caused by the engine itself.
I was busy trying to compile a build of Psych Engine 0.7.2, when all of a sudden, I got this error.

Command Prompt/Terminal logs (if existing)
C:\Users\l7910\Downloads\FNF-PsychEngine-0.7.2\FNF-PsychEngine-0.7.2>lime test windows
source/psychlua/CallbackHandler.hx:54: characters 18-33 : Class<llua.Lua_helper> has no field sendErrorsToLua

Are you modding a build from source or with Lua?
Lua and Source
Which branch of the engine are you using?
Latest (main)
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Yes. I simply changed the name of the window title in the Project.xml file. Other than that, no.

do haxelib remove linc_luajit then haxelib git linc_luajit https://github.com/superpowers04/linc_luajit.git


connect command should not be case sensitive

Describe the bug

I tried to run the dbt-meshify connect command on two projects connected via the "source hack".
I got this message:

After investigating, it was because my target schema in my upstream project was ALL CAPS which my source definition in my downstream project was lower case.

good eye goheen

do all warehouses have case-insensitive database, schema, and table name?


Alignment of icon on home page

Need to align icon with Title

Done.

Completed

Not resolved in  2.4.1 (631)

Put a word limit in description.


Add Router Test

Which issue this PR addresses:

Fixes https://issues.redhat.com/browse/ARO-7346
What this PR does / why we need it:

This PR adds a smoke test that tests the router functionality.
Test plan for issue:

Run E2E_LABEL=smoke make test-e2e locally.
Is there any documentation that needs to be updated for this PR?

This is a test. N/A
How do you know this will function as expected in production?

This is a test.

/azp run ci, e2e

/azp run ci, e2e


Rename load command to merge

Rename load command to merge (Deepak rightly suggested this a while ago)

@justaddcoffee Thanks for the PR 👍


[CELEBORN-666][FOLLOWUP] Unify all blacklist related code and comment

What changes were proposed in this pull request?
Unify all blacklist related code and comment
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?

ping @pan3793 @waitinfuture


Added user and logo for new user "Schréder Hyperion"

Schréder hereby grants Partner a non-exclusive right to use Schréder’s trade names, trademarks or logos (the “Schréder Trademarks”) in connection with the execution of this Agreement, provided that Partner obtains Schréder’s prior written approval of any materials prepared by Partner that contain Schréder’s trade names, trademarks or logos and provided further that Partner’s right to use and display Schréder Trademarks is solely in connection with and to the extent necessary for the execution of this Agreement. Partner’s use shall be in accordance with Schréder’s trademark guidelines as may be issued by Schréder to Partner in writing from time to time. All goodwill associated with the use of Schréder Trademarks shall inure exclusively to Schréder. Partner shall not remove or alter Schréder products copyright notices, trademarks, or logos or attempt to use or register any trademark similar to any Schréder Trademark. If Schréder notifies Partner of an objectionable use of the Schréder Trademarks, Partner shall immediately cease such use. Schréder retains all rights in the Schréder Trademarks except as specifically granted to Partner in this section.

done @tomkerkhove !


SSL Removal & Reinstallation

SSL Certificate Removed from the plugin.
SSL Cert and Key deleted from cPanel.
Install SSL again.
Error: The domain xxx.com is already having an active ssl certificate.

How did you remove the SSL certificate? please update to latest version and let me know.


fix: Reference links

Fix reference links in README and remove extraneous index.html references.

all looks ok to me, but will let @bms63 approve and merge to be sure

Is this an issue?


Made the drawing tool a bit easier to use

Pull Request Test Coverage Report for Build 282

6 of 10 (60.0%)  changed or added relevant lines in 1 file are covered.
17 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.4%) to 45.408%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

clifford/tools/g3c/GAOnline.py
6
10
60.0%

Files with Coverage Reduction
New Missed Lines
%

clifford/tools/g3c/model_matching.py
1
36.62%

clifford/tools/g3c/GAOnline.py
1
64.22%

clifford/init.py
15
63.65%

Totals

Change from base Build 280:
-0.4%

Covered Lines:
1770

Relevant Lines:
3898

💛  - Coveralls


liquid

https://github.com/connext/nxtp/blob/d8a6161af1ec1d837fd48bbedcc8737d51479340/packages/router/src/adapters/contract/index.ts

What's the issue here?


Update backup util appsmithctl docs with new changes

Is there an existing issue for this?

[X] I have searched the existing issues

Engineering Ticket Link
https://github.com/appsmithorg/appsmith/pull/22229
Release Date
15/4/2023
Release Number
v1.9.14
First Draft
No response
Loom video
No response
Discord/slack/intercom Link if needed
No response
PRD
No response
Test plan/cases
No response
Use cases or user requests
Going forward the util cmd appsmithctl backup does not stop the backend and rts processes. Essentially there will be no down time when running a manual backup on an Appsmith instance.
It will be the responsibility of the Admin to make sure that a manual backup is really a desired snapshot when done via
the appsmithctl backup util command
To ensure this, Admins may require to stop the backend and rts processes in the container before a manual backup.

Done.


fix(TDI-42892):remove endpoint restraint azure

What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
https://jira.talendforge.org/browse/TDI-42892
Please check if the PR fulfills these requirements

[ ] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: failure :x:

Pull request test result: success :star:
Sonar results

Pull request test result: success :star:
Sonar results

Pull request test result: success :star:
Sonar results


gazebo exited with undefined symbol error: _ZN8mav_msgs4msgs10MotorSpeedC1Ev

Problem
When I tried to launch the posix_sitl.launch, the gazebo exited with the error message shown below.
Screenshot of the error message

I'm wondering if it is a gazebo version issue.
System Information
Ubuntu: 18.04
ROS: Melodic
Gazebo: 9.10.0
PX4: 1.9.2
Fresh Install: Yes.

Are you sure this happens after a clean build?
Can you copy and paste the commands that you use to build?

How do you use that launch file? And do you also rebuild everything in the catkin workspace?

@lguanrui you are not sourcing the config file for the Gazebo plugins and models:
$source Firmware/Tools/setup_gazebo.bash Firmware/build/px4_sitl/ Firmware/

@TSC21 I did this before the launching. Sorry I didn't mention it.

Do you have Gazebo installed from both OSRF sources and ROS? It may result in some issues. Otherwise, I would say you have conflictson the LD_LIBRARY_PATH. I would make sure that you are able to run the sim first using make px4_sitl gazebo.

@TSC21 I did this before the launching. Sorry I didn't mention it.

Do you have Gazebo installed from both OSRF sources and ROS? It may result in some issues. Otherwise, I would say you have conflictson the LD_LIBRARY_PATH. I would make sure that you are able to run the sim first using make px4_sitl gazebo.

I just double checked. the project itself has install gazebo from OSRF sources and I installed gazebo from ROS too. However, I was able to run the make px4_sitl gazebo before running the sim.

So does make px4_sitl gazebo start Gazebo with the Iris model spawned and the PX4 daemon running?

I would uninistall and reinstall Gazebo just to be sure. I am not sure what's causing that error at this stage. Try to alo unsource the ROS path from bashrc and rerun the make command.

Hi all! After removing the OSRF sources, the simulator works! Thanks for helping! Closing this issue.

Hi @lguanrui can you tell how did you remove OSRF sources? I'm getting a similar error.

Please don't necro bump. And the tinyxml2 linking issue should be resolved if you do brew upgrade and make clean


Fix URLs generation

fix URLs generation for prod environment (used in Astarte triggers)
update docker-compose.yml

Pull Request Test Coverage Report for Build a54c4a0021c540093428d07f25a4a66d633c5159-PR-436

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+84.6%) to 84.635%

Totals

Change from base Build<PHONE_NUMBER>:
84.6%

Covered Lines:
1647

Relevant Lines:
1946

💛  - Coveralls


Write access logs to cluster

Write access logs to cluster to allow for adding them to Elastic.

ping


Using pytorch then using tfrecords reading data

This is really rediculus when I saw this:

train_input_reader: {
  record_file_path: "/media/yy/960evo/datasets/kitti/kitti_train.tfrecord"

tfrecord with pytorch ........................

Actually there is a complete tensorflow implementation of this project which shares all code except ./pytorch and contains a faster sparse convnet implementation. I have no plan to release tf code because of two reasons:

tf sparseconv is done in a company.
due to limitations of tensorflow input (it uses c++ multi-thread rather than multiprocessing in pytorch) which isn't compatible with python pre-processing function, the training speed of tensorflow code is very slow (~1.5x-2x slower).

@traveller59 So that it actually didn't used in this project? I think pytorch official SparseConvNet should be reliable and fast though

@jinfagang some opinions are only for tensorflow and aren't used in pytorch code. the official SparseConvNet actually has some performance problems (rule generation, hand-written gemm).


Feat/asset nft

Closes #1366

Lets push this in first, that will come as second PR, Easier to gauge the PR since that is mostly only scripts @mikiquantum


The generated chart doesn't handle well environment variables created by the quarkus kubernetes extension for init tasks

When adding quarkus-flyway to my project, quarkus-kubernetes creates an init task (see https://quarkus.io/guides/flyway#flyway-on-kubernetes). This init task comes with an environment variable QUARKUS_FLYWAY_ENABLED. It seems the type of the environment variable is incorrect, since when installing the chart generated with quarkus-helm, I end up with:
Error: Deployment in version "v1" cannot be handled as a Deployment: json: cannot unmarshal bool into Go struct field EnvVar.spec.template.spec.containers.env.value of type string

Looking into the resources generated by quarkus-kubernetes, I can see that the type looks correct:
    spec:
      containers:
        - env:
            - name: KUBERNETES_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
            - name: QUARKUS_FLYWAY_ENABLED
              value: "false"

In the chart generated by quarkus-helm I see:
    spec:
      containers:
        - env:
            - name: KUBERNETES_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
            - name: QUARKUS_FLYWAY_ENABLED
              value: {{ .Values.app.envs.QUARKUS_FLYWAY_ENABLED }}

With the following in the values file:
app:
  envs:
    QUARKUS_FLYWAY_ENABLED: "false"

(which looks good to me).
Finally the schema also looks good:
        "envs" : {
          "type" : "object",
          "properties" : {
            "QUARKUS_FLYWAY_ENABLED" : {
              "type" : "string"
            }
          }
        },

I tried overwriting the value when installing the chart with --set-string, with no luck...
I managed to reproduced on a minimal example:

generate a project with the 4 extensions selected in this link https://code.quarkus.io/?e=kubernetes&e=kind&e=flyway&e=container-image-docker
setup your kubectl context to a test cluster
run mvn package && helm upgrade --install bug target/helm/kubernetes/<artifact>

For convenience I uploaded a reproducer: https://github.com/PierreBtz/quarkus-flyway-helm-bug.
Upon installing the chart, you should see:
Release "quarkus-flyway-helm-bug" does not exist. Installing it now.
Error: Deployment in version "v1" cannot be handled as a Deployment: json: cannot unmarshal bool into Go struct field EnvVar.spec.template.spec.containers.env.value of type string

Unfortunately, this is a limitation of the Helm client by Go.
From the Quarkus Helm extension, there is no way to improve this situation since we can't know if the env var value is a string or a boolean.
The only workaround I came up with is to add the following configuration that adds the quotes:
quarkus.helm.expressions.0.path=*.env.(name == QUARKUS_FLYWAY_ENABLED).value
quarkus.helm.expressions.0.expression={{ .Values.app.envs.QUARKUS_FLYWAY_ENABLED | quote }}

I confirm the suggested solution works properly.
What I had in mind, was that for "well-known" environment variables generated by other extensions, quarkus helm could force the type.
It would introduce an indirect coupling with the quarkus-flyway extension (and other extensions in the future) so perhaps you do not want to go down this road (and I totally understand)!
Thanks for your work on this extension!

I totally understand :) In fact, I need to dig a bit deeper when I have some time, but I think there is a problem with this approach, since quarkus.flyway.enabled is a build time property, so I have a hard time figuring out what it can do at the deployment/statefulset level.
Back to the issue at hand, as far as I'm concerned, you're proposed workaround is alright!

quarkus.flyway.enabled

I had not noticed that "quarkus.flyway.enabled" was a build-time property, then the env var seems wrong for sure. Actually, in Quarkus 3.2, this property was not a build-time property, so maybe this is a leftover.
Thanks for digging into this!

Link https://github.com/quarkusio/quarkus/issues/37040

Link quarkusio/quarkus#37040

Great, thanks!

@Sgitario I just hit this as well.
I don't get why there was mention of handling well-known environment variables. All environment variables must be strings anyway, that's what the error message is telling us.
With that in mind, can't the Helm extension at least force quoting for all environment variables?
What I mean is that it currently replaces this:
    spec:
      containers:
        - env:
            - name: QUARKUS_HIBERNATE_SEARCH_ORM_ELASTICSEARCH_HOSTS
              value: search-backend-0.search-backend:9200
            - name: INDEXING_QUEUE_COUNT
              value: "12"
            - name: HOME
              value: /tmp
            - name: INDEXING_BULK_SIZE
              value: "20"

with this:
    spec:
      containers:
        - env:
            - name: QUARKUS_HIBERNATE_SEARCH_ORM_ELASTICSEARCH_HOSTS
              value: {{ .Values.app.envs.QUARKUS_HIBERNATE_SEARCH_ORM_ELASTICSEARCH_HOSTS }}
            - name: INDEXING_QUEUE_COUNT
              value: {{ .Values.app.envs.INDEXING_QUEUE_COUNT }}
            - name: HOME
              value: {{ .Values.app.envs.HOME }}
            - name: INDEXING_BULK_SIZE
              value: {{ .Values.app.envs.INDEXING_BULK_SIZE }}

Can't it replace it with this instead?
    spec:
      containers:
        - env:
            - name: QUARKUS_HIBERNATE_SEARCH_ORM_ELASTICSEARCH_HOSTS
              value: {{ .Values.app.envs.QUARKUS_HIBERNATE_SEARCH_ORM_ELASTICSEARCH_HOSTS | quote }}
            - name: INDEXING_QUEUE_COUNT
              value: {{ .Values.app.envs.INDEXING_QUEUE_COUNT | quote }}
            - name: HOME
              value: {{ .Values.app.envs.HOME | quote }}
            - name: INDEXING_BULK_SIZE
              value: {{ .Values.app.envs.INDEXING_BULK_SIZE | quote }}

Or are you saying the Helm extension doesn't have the context it needs to detect, upon replacement, that it's replacing an environment variable?

@yrodiere the Quarkus Helm extension is already adding the | quote only when the value is not a string, and looking at:
- name: INDEXING_BULK_SIZE
              value: "20"

The "20" is a string, so that's why the quote is not added. However, the Helm client (again) interprets "20" as a number and hence we have the problem.
I was reluctant to always add the quote for env vars because (1) this is a limitation of the Helm client that we don't hit if we don't use it and (2) users might add a non-string env var and then it won't work as they expect.
But since this is being a pain for a lot of users, I think we can do it and for the users from (2), they can always provide a custom expression. Wdyt?

(1) this is a limitation of the Helm client that we don't hit if we don't use it

Do you mean there are other ways to use Helm charts than through the Helm client? :confused:

(2) users might add a non-string env var and then it won't work as they expect.

Are you sure they can? Environment variables are always strings as far as I can tell... the Kubernetes YAML schema just doesn't allow anything other than strings there. See https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/pod-v1/#environment-variables

But since this is being a pain for a lot of users, I think we can do it and for the users from (2), they can always provide a custom expression. Wdyt?

+1 from me, because I don't think users from (2) even exist :D

+1 from me, because I don't think users from (2) even exist :D

About (2), the problem I foresee is that users using boolean or integers would expect to inject types as such. Before adding the | quote, this is spotted before installing the chart. Now, they will realise that these types are now strings.
Having said that, I also expect (2) is not even a concern!
https://github.com/quarkiverse/quarkus-helm/pull/319 should fix this issue.


TCP Check doesn't gracefully fail

Output of the info page (if this is a bug)
===============
Agent (v7.22.0)
===============

  Status date: 2020-09-26 19:42:08.763137 UTC
  Agent start: 2020-09-22 21:01:40.644554 UTC
  Pid: 2276
  Go Version: go1.13.11
  Python Version: 3.8.5
  Build arch: amd64
  Agent flavor: agent
  Check Runners: 4
  Log Level: info
<<SNIP>>
 Check Initialization Errors
  ===========================

      tcp_check (2.5.0)
      -----------------

      instance 0:

        could not invoke 'tcp_check' python check constructor. New constructor API returned:
Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 73, in __init__
    self.resolve_ip()
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 79, in resolve_ip
    self.addr = socket.gethostbyname(self.url)
socket.gaierror: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 76, in __init__
    raise ConfigurationError(msg)
datadog_checks.base.errors.ConfigurationError: URL: <<censored>> is not a correct IPv4, IPv6 or hostname
Deprecated constructor API returned:
__init__() got an unexpected keyword argument 'agentConfig'

      instance 1:

        could not invoke 'tcp_check' python check constructor. New constructor API returned:
Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 73, in __init__
    self.resolve_ip()
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 79, in resolve_ip
    self.addr = socket.gethostbyname(self.url)
socket.gaierror: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 76, in __init__
    raise ConfigurationError(msg)
datadog_checks.base.errors.ConfigurationError: URL: <<censored>> is not a correct IPv4, IPv6 or hostname
Deprecated constructor API returned:
__init__() got an unexpected keyword argument 'agentConfig'

      instance 2:

        could not invoke 'tcp_check' python check constructor. New constructor API returned:
Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 73, in __init__
    self.resolve_ip()
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 79, in resolve_ip
    self.addr = socket.gethostbyname(self.url)
socket.gaierror: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 76, in __init__
    raise ConfigurationError(msg)
datadog_checks.base.errors.ConfigurationError: URL: <<censored>> is not a correct IPv4, IPv6 or hostname
Deprecated constructor API returned:
__init__() got an unexpected keyword argument 'agentConfig'

      instance 3:

        could not invoke 'tcp_check' python check constructor. New constructor API returned:
Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 73, in __init__
    self.resolve_ip()
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 79, in resolve_ip
    self.addr = socket.gethostbyname(self.url)
socket.gaierror: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 76, in __init__
    raise ConfigurationError(msg)
datadog_checks.base.errors.ConfigurationError: URL: <<censored>> is not a correct IPv4, IPv6 or hostname
Deprecated constructor API returned:
__init__() got an unexpected keyword argument 'agentConfig'

      instance 4:

        could not invoke 'tcp_check' python check constructor. New constructor API returned:
Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 73, in __init__
    self.resolve_ip()
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 79, in resolve_ip
    self.addr = socket.gethostbyname(self.url)
socket.gaierror: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 76, in __init__
    raise ConfigurationError(msg)
datadog_checks.base.errors.ConfigurationError: URL: <<censored>>.com is not a correct IPv4, IPv6 or hostname
Deprecated constructor API returned:
__init__() got an unexpected keyword argument 'agentConfig'
  Loading Errors
  ==============
    tcp_check
    ---------
      Core Check Loader:
        Check tcp_check not found in Catalog

      JMX Check Loader:
        check is not a jmx check, or unable to determine if it's so

      Python Check Loader:
        could not configure check instance for python check tcp_check: could not invoke 'tcp_check' python check constructor. New constructor API returned:
Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 73, in __init__
    self.resolve_ip()
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 79, in resolve_ip
    self.addr = socket.gethostbyname(self.url)
socket.gaierror: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/tcp_check/tcp_check.py", line 76, in __init__
    raise ConfigurationError(msg)
datadog_checks.base.errors.ConfigurationError: URL: <<censored>>.com is not a correct IPv4, IPv6 or hostname
Deprecated constructor API returned:
__init__() got an unexpected keyword argument 'agentConfig'

Check Config:
init_config:

instances:

  - name: <<censored>>
    host: <<censored>>.com
    port: 443
    collect_response_time: true
    # 5 min
    min_collection_interval: 300

  - name: <<censored>>
    host: <<censored>>.com
    port: 443
    collect_response_time: true
    # 5 min
    min_collection_interval: 300

  - name: <<censored>>
    host: <<censored>>.com
    port: 80
    collect_response_time: true
    # 5 min
    min_collection_interval: 300

  - name: <<censored>>
    host: <<censored>>.com
    port: 80
    collect_response_time: true
    # 5 min
    min_collection_interval: 300

  - name: <<censored>>
    host: <<censored>>.com
    port: 443
    collect_response_time: true
    # 5 min
    min_collection_interval: 300

Describe what happened:
TCP check is failing/crashed and isn't running (running datadog-agent check tcp_check works)
Describe what you expected:
I would expect to have the failure reported up (it isn't, no checks are being published)
Steps to reproduce the issue:
Im not sure how the host got into this state.
Additional environment details (Operating System, Cloud provider, etc):
Debian 10, bare-metal IoT device

This just hit me now, bare metal Debian with Minikube on Docker. Do you know about solution to this?


Workspace rules do not work as expected.

Regression?
No
System Info and Version
 System/Version info
Hyprland, built from branch  at commit 918d8340afd652b011b937d29d5eea0be08467f5  (flake.lock: update).
Date: Tue Jun 25 12:06:02 2024
Tag: v0.41.2, commits: 4886

flags: (if any)

System Information:
System name: Linux
Node name: archlinux
Release: 6.9.6-arch1-1
Version: #1 SMP PREEMPT_DYNAMIC Fri, 21 Jun 2024 19:49:19 +0000

GPU information:
07:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1002:67ef] (rev e5) (prog-if 00 [VGA controller])

os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

plugins:

======Config-Start======

Config File: /home/musicfan/.config/hypr/hyprland.conf: Read Succeeded
#Monitor set up.
monitor=DP-1,3840x2160@60,0x0,2
monitor=DVI-D-1,1920x1080@60,1920x0,1

#Extra settings.
misc {
disable_hyprland_logo = true
}

#keyboard layout.
input {
    kb_layout = us,gr
    kb_options = grp:alt_shift_toggle
}

#Commands to execute at start up.
exec-once = waybar &
exec-once = corectrl -m main --minimize-systray &
exec-once = xrdb -load /home/musicfan/.Xresources &
exec-once = exec exec openrgb -p cyan.orp --startminimized &
exec-once = openrgb -p cyan.orp --startminimized &
exec-once = nm-applet &
exec-once = playerctld daemon &
exec-once = dbus-update-activation-environment --systemd WAYLAND_DISPLAY XDG_CURRENT_DESKTOP
#exec-once = wlsunset
exec-once = lxqt-policykit-agent &
exec-once = $HOME/.config/scripts/SelectWallpeper.sh &
exec-once = radeontop -d gpu.txt -l 0 > /dev/null &
exec-once = blueman-applet &
exec-once = pactl load-module module-native-protocol-tcp auth-anonymous=true &
exec-once = hypridle &

#XWayland scale.
xwayland {
  force_zero_scaling = true
}

#Some default env vars.
env = XCURSOR_SIZE,24
env = GDK_SCALE,2
env = QT_QPA_PLATFORMTHEME,qt5ct
env = GTK_THEME,Nordic

#Window Rules.

#Floating
windowrulev2 = float,class:(lxqt-policykit-agent)
windowrulev2 = float,size 20%,noborder,class:(mpv)

#Workspace 1
windowrulev2 = workspace 1 ,class:(discord)
windowrulev2 = workspace 1 ,class:(Skype)
windowrulev2 = workspace 1 ,class:(Element)
windowrulev2 = workspace 1 ,class:(thunderbird)
windowrulev2 = workspace 1 ,class:(FAMP)

#Workspace 2
windowrulev2 = workspace 2 ,class:(FM)

#Workspace 3
windowrulev2 = workspace 3 ,class:(FS)

#Worksapce 4
windowrulev2 = workspace 4 ,class:(FN)
windowrulev2 = workspace 4 ,class:(pcmanfm-qt)

#Workspace 5
windowrulev2 = workspace 5 ,class:(kitty)

#Workspace 6
windowrulev2 = workspace 6 ,class:(virt-manager)

#Workspace 7
windowrulev2 = workspace 7 ,class:(Emacs)

#Workspace 8
windowrulev2 = workspace 8 ,class:(com.obsproject.Studio)

#Workspace 9
windowrulev2 = workspace 9 ,class:(FP)

#Workspace 10
windowrulev2 = workspace 10 ,class:(steam)

#Workspace 11
windowrulev2 = workspace 11 ,class:(org.kde.kdenlive)
windowrulev2 = workspace 11 ,class:(blender)
windowrulev2 = workspace 11 ,class:(fr.handbrake.ghb)

#Workspace 12
windowrulev2 = workspace 12 ,class:(libreoffice-writer)
windowrulev2 = workspace 12 ,class:(libreoffice-calc)
windowrulev2 = workspace 12 ,class:(libreoffice-impress)
windowrulev2 = workspace 12 ,class:(libreoffice-draw)
windowrulev2 = workspace 12 ,class:(libreoffice-math)
windowrulev2 = workspace 12 ,class:(libreoffice-base)

#Workspace special
windowrulev2 = workspace special ,class:(ch.proton.bridge-gui)
windowrulev2 = workspace special ,class:(org.pulseaudio.pavucontrol)
windowrulev2 = workspace special ,class:(org.rncbc.qpwgraph)
windowrulev2 = workspace special ,class:(blueman-manager)

general {
    # See https://wiki.hyprland.org/Configuring/Variables/ for more
    gaps_in = 0
    gaps_out = 0
    border_size = 4
    col.active_border = rgba(33ccffee) rgba(00ff99ee) 45deg
    col.inactive_border = rgba(59595900)
    layout = dwindle
}

decoration {
    # See https://wiki.hyprland.org/Configuring/Variables/ for more

    rounding = 0

    blur {
        enabled = false
        size = 3
        passes = 1
    }

    drop_shadow = yes
    shadow_range = 4
    shadow_render_power = 3
    col.shadow = rgba(1a1a1aee)
}

animations {
    enabled = yes

    # Some default animations, see https://wiki.hyprland.org/Configuring/Animations/ for more

    bezier = myBezier, 0.05, 0.9, 0.1, 1.05

    animation = windows, 1, 7, myBezier
    animation = windowsOut, 1, 7, default, popin 80%
    animation = border, 1, 10, default
    animation = borderangle, 1, 8, default
    animation = fade, 1, 7, default
    animation = workspaces, 1, 6, default
}

dwindle {
    # See https://wiki.hyprland.org/Configuring/Dwindle-Layout/ for more
    pseudotile = yes # master switch for pseudotiling. Enabling is bound to mainMod + P in the keybinds section below
    preserve_split = yes # you probably want this
}

#master {
#    # See https://wiki.hyprland.org/Configuring/Master-Layout/ for more
#    new_is_master = true
#}

gestures {
    # See https://wiki.hyprland.org/Configuring/Variables/ for more
    workspace_swipe = off
}

# See https://wiki.hyprland.org/Configuring/Keywords/ for more
$mainMod = SUPER

# Example binds, see https://wiki.hyprland.org/Configuring/Binds/ for more
bind = $mainMod, w,exec,$HOME/.config/scripts/SelectWallpeper.sh
bind = $mainMod, P,exec,$HOME/.config/scripts/power.sh
bind = $mainMod, U,movecurrentworkspacetomonitor, DVI-D-1
bind = $mainMod, I,movecurrentworkspacetomonitor, DP-1
bind = $mainMod, Y,swapactiveworkspaces,current +1
bind = $mainMod, F, workspaceopt, allfloat
bind = $mainMod, Return, exec, kitty
bind = $mainMod, M, exit,
bind = $mainMod, P, pseudo, # dwindle
bind = $mainMod, q, togglesplit, # dwindle
bind = $mainMod, A, exec,passrofi
bind = ALT_L, SPACE, exec,rofi -show drun
bind = ALT_L, W, exec, $HOME/.config/scripts/search.sh
bind = ALT_L, E, exec, $HOME/.config/scripts/sites.sh
bind = ALT_L, 5, fullscreen
bind = ALT_L, T, togglefloating,
bind = ALT_L, f4, killactive,
bind = ALT_L, j, exec ,rofi -show emoji -theme $HOME/.config/rofi/arthur.rasi
bind = CTRL_L_SHIFT, W,exec, $HOME/.config/scripts/media.sh
bind = ,Print,exec, $HOME/.config/scripts/screenshot.sh
bind = ALT_L, q ,exec, $HOME/.config/scripts/runScript.sh

bind=$mainMod_SHIFT,s,movetoworkspace,special
bind=$mainMod,s,togglespecialworkspace,

#Media buttons
bind =, XF86AudioMute, exec, $HOME/.config/scripts/volumeMeter.sh -m
binde =, XF86AudioLowerVolume, exec, $HOME/.config/scripts/volumeMeter.sh -d
binde =, XF86AudioRaiseVolume, exec, $HOME/.config/scripts/volumeMeter.sh -u
bind =, XF86AudioPlay, exec, $HOME/.config/scripts/mediaNotification.sh -p
bind =, XF86AudioPause, exec, $HOME/.cofnig/scripts/mediaNotification.sh -p
bind =, XF86AudioNext, exec, $HOME/.config/scripts/mediaNotification.sh -n
bind =, XF86AudioPrev, exec, $HOME/.config/scripts/mediaNotification.sh -b
bind =, XF86AudioStop, exec, $HOME/.config/scripts/mediaNotification.sh -t

#Move focus with mainMod + arrow keys
bind = $mainMod, L, movefocus, l
bind = $mainMod, H, movefocus, r
bind = $mainMod, K, movefocus, u
bind = $mainMod, J, movefocus, d

# Switch workspaces with mainMod + [0-9]
bind = CONTROL_L, F1, workspace, 1
bind = CONTROL_L, F2, workspace, 2
bind = CONTROL_L, F3, workspace, 3
bind = CONTROL_L, F4, workspace, 4
bind = CONTROL_L, F5, workspace, 5
bind = CONTROL_L, F6, workspace, 6
bind = CONTROL_L, F7, workspace, 7
bind = CONTROL_L, F8, workspace, 8
bind = CONTROL_L,  F9, workspace, 9
bind = CONTROL_L, F10, workspace, 10
bind = CONTROL_L, F11, workspace, 11
bind = CONTROL_L, F12, workspace, 12

# Move active window to a workspace with mainMod + SHIFT + [0-9]
bind = CONTROL_L SHIFT, F1, movetoworkspace, 1
bind = CONTROL_L SHIFT, F2, movetoworkspace, 2
bind = CONTROL_L SHIFT, F3, movetoworkspace, 3
bind = CONTROL_L SHIFT, F4, movetoworkspace, 4
bind = CONTROL_L SHIFT, F5, movetoworkspace, 5
bind = CONTROL_L SHIFT, F6, movetoworkspace, 6
bind = CONTROL_L SHIFT, F7, movetoworkspace, 7
bind = CONTROL_L SHIFT, F8, movetoworkspace, 8
bind = CONTROL_L SHIFT, F9, movetoworkspace, 9
bind = CONTROL_L SHIFT, F10, movetoworkspace, 10
bind = CONTROL_L SHIFT, F11, movetoworkspace, 11
bind = CONTROL_L SHIFT, F12, movetoworkspace, 12

# Scroll through existing workspaces with mainMod + scroll
bind = $mainMod, mouse_down, workspace, e+1
bind = $mainMod, mouse_up, workspace, e-1

# Move/resize windows with mainMod + LMB/RMB and dragging
bindm = $mainMod, mouse:272, movewindow
bindm = $mainMod, mouse:273, resizewindow

#Lock the screen
bind = $alt, l, exec, hyprlock

# Submaps
bind = ALT,R,submap,resize

submap = resize

binde = ,right,resizeactive,10 0
binde = ,left,resizeactive,-10 0
binde = ,up,resizeactive,0 -10
binde = ,down,resizeactive,0 10
bind = ,escape,submap,reset

submap=reset

======Config-End========

Description
This is a continuum of this. I created a script that launch FireFox with custom window class name.
I notice something...
When a class name exist with more than 2 characters identical then rules do not work properly
For example.
If i have a rule. windowrulev2 = workspace 1 ,class:(FMP)
And a rule windowrulev2 = workspace 2 ,class:(FM)
The window with the class FMP it will open on the workspace 2. The expected reaction in my opinion it will be to open to the workspace 1.
If we now change the FMP name to FAMP. Now it works.
My thinking is that Hyprland reads the FMP and FM as the same thing.
I do not know if that is indented or not. If it is never mind. But for my brain is strange.
How to reproduce

use my Hyprland config
Chane line 55 with windowrulev2 = workspace 1 ,class:(FMP)
Run firefox --name FMP

Crash reports, logs, images, videos
None.

Try windowrulev2 = workspace 2,class:(^FM$) to match whole string

So... I try windowrulev2 = workspace 1 ,class:(^FMP$). And then. I run.
firefox --name FMP
And the window spawn on the workspace 2.
So this is not working.

FMP still matches (FM). Your second rule needs to be more specific. (FM) will match anything containing FM.

I understand, so this is working as indented ? I am of the opinion that Hyprland should check the whole string... If it is a match.
I was thinking that this was a BUG.

https://wiki.hyprland.org/Configuring/Window-Rules/
The second part of a rule is a RegEx. ^ mathes the start of string, $ - the end. Take a look at https://cheatography.com/davechild/cheat-sheets/regular-expressions/

I know what RegEx is. I just did not expect to need to use them when i have the whole string i want to match.
For example when i want to delete a file i can do rm name_of_the_file (no RegEx). Only when i do not know the name but i know some of it. I need use RegEx like rm *.mp3 or something like that.
Any way, as far as i understand this is the indented response from Hyprland.
Thanks for the help and for the knowledge.
I will close this issue. Because terns out this is not an issue.


Poly Transform

can you tell me  where can get the output of Poly Transform,look forward your response

We get the output from the authors of Poly Transform. You can contact them by email.

Thank you for your reply.


Cufon not working on Wordpress v. 3.3.1

Today I've upgraded my version of Wordpress to 3.3.1: http://codex.wordpress.org/Version_3.3.1
"This maintenance release fixes 15 issues with WordPress 3.3, as well as a fix for a cross-site scripting vulnerability that affected version 3.3".
Unfortunately, Cufon is not working anymore in all browsers. Can you help, please?

Hi,
Are you using the WP plugin? If yes, maybe it's no longer active in your plugin manager. In any case, it's a 3rd party plugin, so you'd be better off by mailing the author of the plugin instead.
Simo
On Jan 4, 2012, at 6:23 PM, lospaziodiugosan wrote:

Today I've upgraded my version of Wordpress to 3.3.1: http://codex.wordpress.org/Version_3.3.1
""This maintenance release fixes 15 issues with WordPress 3.3, as well as a fix for a cross-site scripting vulnerability that affected version 3.3".
Unfortunately, Cufon is not working anymore in all browsers. Can you help, please?

Reply to this email directly or view it on GitHub:
https://github.com/sorccu/cufon/issues/226


[YUNIKORN-2615] Remove named returns from predicate_manager.go

What is this PR for?
Remove named returns, decrease calls to get plugin name. Simplify skip map used in runPreFilterPlugins and runFilterPlugins to a boolean map
What type of PR is it?

[X] - Refactor

What is the Jira issue?

https://issues.apache.org/jira/browse/YUNIKORN-2615

How should this be tested?
No functional change existing tests should cover

Codecov Report
Attention: Patch coverage is 66.66667% with 6 lines in your changes are missing coverage. Please review.

:exclamation: No coverage uploaded for pull request base (master@d884f19). Click here to learn what that means.
Report is 3 commits behind head on master.

Files
Patch %
Lines

pkg/plugin/predicates/predicate_manager.go
66.66%
6 Missing :warning:

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #834   +/-   ##
=========================================
  Coverage          ?   66.03%
=========================================
  Files             ?       69
  Lines             ?     7534
  Branches          ?        0
=========================================
  Hits              ?     4975
  Misses            ?     2347
  Partials          ?      212

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


CASM-4669 Include image signatures in csm tarball

Summary and Scope
We already sign images during build with one of 3 keys:

Images built with Github actions: gcpkms://projects/sdlc-ops/locations/global/keyRings/csm-builds/cryptoKeys/github-cray-hpe/versions/1
Images built with Jenkins: gcpkms://projects/sdlc-ops/locations/global/keyRings/csm-builds/cryptoKeys/jenkins-csm/versions/1
New GCP key infrastructure, established with CASM-4667 (stage only ATM, prod instance planned): gcpkms://projects/hpe-stage-csm-security/locations/global/keyRings/cosign/cryptoKeys/csm-images/versions/1

This PR provides the following changes:
During CSM tarball packaging:

Image signatures are verified with provided set of keys
Images packaged with signatures included
Public keys are packaged

During CSM install / upgrade

Images are uploaded into PIT Nexus and Kubernetes Nexus together with respective signatures
Public keys are injected into Helm customizations under spec.kubernetes.services.kyverno-policy.checkImagePolicy.publicKeys key - so that they can be consumed by kyverno-policy chart in this manner: https://github.com/Cray-HPE/cray-kyverno-policies/blob/feature/image-signatures/charts/kyverno-policy/templates/cluster/cluster-check-image.yaml#L29-L36

Issues and Related PRs

Resolves CASM-4669
Relates to CASM-4667

Testing
Tested on:

Virtual Shasta
Jenkins build
Local testing

Test description:
During build:

Tested that all images participating build are properly signed, by executing new stage during build:

Performed false positive test - injected unsigned image into build, ensured that cosign verify step failed

After installing temporary build on vShasta system, ensured that:

Images are available in both PIT Nexus and Cloud Nexus together with signatures:

Kyverno policy chart, updated to consume public keys from customization, can be installed with proper public keys configuration, which is provided via customizations:
ncn-m001:~ # helm -n kyverno get values kyverno-policy
USER-SUPPLIED VALUES:
checkImagePolicy:
  publicKeys:
  - |-
    -----BEGIN PUBLIC KEY-----
    MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAERxLYOVq/kBeE05mUZqTk85CaOpSC
    CdYeLlCt+K941eQgNWQLBdMiDPnicw5i9o278apo/OLD5AZVSX8ZXPYkKQ==
    -----END PUBLIC KEY-----
  - |-
    -----BEGIN PUBLIC KEY-----
    MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEhEQ9X1j2d7qDHEXJRbYnAcYMhGop
    OBhknIvSWQYhOpiH74CtJX4/KKPOQJxmb+ZHdZjC9GQZzxyayp2EvLF2Og==
    -----END PUBLIC KEY-----
  - |-
    -----BEGIN PUBLIC KEY-----
    MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEArrdSOxAr5Pn/WgxSvrcU
    ufjL2aGknFOPeNSkQiI5s4etVlWz5Om21zgBSgatf4PrKPSv4wjG3ujKZqSJ6o8k
    jTO/ycNcsJnkqRROS158tOwGeMy5OQQaH4n+0tEYFvRp3asVqCe8jU4jsAZw3+CY
    eIGMgzbNVoZlvjCl9DQQeMBqrjLefsqUUcc2HwL+PiBIi8pzhGvWfgDpHMkH4GeU
    vdfVkKGW27azhUFj9HbI6njDIvpNaGIBh47hnM+dAdi/9/c/Rs6nx2rpaq3OPR19
    2fxNN7rvReJIE8Ce5HMccp62ihS8F5WGDMlNdmZ2BR8h/DIoSxZ1iySUD1gqlTnb
    EVLJrMU5m/yS3fVAxG2oub29bcvj4r4qwmpBXQT1impoqw4wQZO7nFPOUfW9SIXW
    668sN6khTRbPQBXB6BBZYOTVibpXxl61D9WuBf/bs7epxbViFr2DgxGfebYb+wlw
    AfPzoJ5gX6f0r7Ob5PK7exLbf66XWClxvZ9nr6EYN3x3IQCdYDa2pcLU59wBygzM
    5qBsTOuePJnq+MeYWoJmSmodah5NxLkZjIPBncz5NPWgJC0sI/pTx4X/8Uh7w74D
    MhH5NnfxQu5FQQ1bSyicbH0pJAgPITflcMvyeKU0pZgLKJRi6xUHMFm6tQIsj2Y8
    +KI4ZSRDM5psovIlaqOm+hUCAwEAAQ==
    -----END PUBLIC KEY-----
global:
  chart:
    name: kyverno-policy
    version: 1.4.3

[!WARNING]
I noticed that Kyverno seems to have issues with verification with public keys in our system, at least in version 1.9.5. It does not support concept of mirroring, so it tries to download image manifests directly from artifactory.algol60.net, rather then trying mirrors configured in /etc/containerd/config.toml on Kubernetes nodes. Also, even with failurePolicy set to Ignore and validationFailureAction set to Audit Kyverno seems to be blocking some network communication during pod deployment.

Performed upgrade from last 1.5.1 build to temporary build on vShasta:
https://jenkins.algol60.net/blue/organizations/jenkins/Cray-HPE%252Fcsm-vshasta-deploy/detail/feature%252Fimage-signatures/9/pipeline
Risks and Mitigations
Low - new feature
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] Testing is appropriate and complete, if applicable
[x] HPC Product Announcement prepared, if applicable

approved


store biom qza during analysis

currently we only store/generate biom but a qza will be useful

Prioritizing this since it directly impacts Q2 users.

I think this should be done after having Q2 load automatically in Qiita ...

Gotcha; I thought that both this and the Q2 automatic loading would be targeted to complete with/in time for the Q2 paper submission. Is the loading automatically delayed until after the Q2 paper is submitted instead? And if so, is a target of the Nov 2018 update reasonable?

This is not a single place solution as plugins needed to change; however, the required changes are done and were demo on today's meeting; thus, moving to a new milestone.

Closed in the qiita 4.19 release to be deployed on May 15, 2019.


Improve Windows time zone guidance

Add a copy of zoneinfo.zip to our docs site. We'll have to keep it up-to-date until a more official version is available for download, etc.
Add more explicit workaround steps to the known limitation.
Add tip about this to the windows install, local cluster, and common error docs.

Fixes #6676.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c155cac360ce121fbbe6426ce9cc18d8a67c14fe/
Edited pages:

v19.1/common-errors.md
v19.1/install-cockroachdb-windows.html
v19.1/known-limitations.md
v19.1/recommended-production-settings.md
v19.1/secure-a-cluster.md
v19.1/start-a-local-cluster.md
v19.2/common-errors.md
v19.2/install-cockroachdb-windows.html
v19.2/known-limitations.md
v19.2/recommended-production-settings.md
v19.2/secure-a-cluster.md
v19.2/start-a-local-cluster.md
v20.1/common-errors.md
v20.1/install-cockroachdb-windows.html
v20.1/known-limitations.md
v20.1/recommended-production-settings.md
v20.1/secure-a-cluster.md
v20.1/start-a-local-cluster.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/eda8ccf6de4f106fb35b82e5776517b1c89c04b9/
Edited pages:

v19.1/common-errors.md
v19.1/install-cockroachdb-windows.html
v19.1/known-limitations.md
v19.1/recommended-production-settings.md
v19.1/secure-a-cluster.md
v19.2/common-errors.md
v19.2/install-cockroachdb-windows.html
v19.2/known-limitations.md
v19.2/recommended-production-settings.md
v20.1/common-errors.md
v20.1/install-cockroachdb-windows.html
v20.1/known-limitations.md
v20.1/recommended-production-settings.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/bf34ec00f9732acdb0d6db2ed523f984735fb062/
Edited pages:

v19.1/common-errors.md
v19.1/install-cockroachdb-windows.html
v19.1/known-limitations.md
v19.1/recommended-production-settings.md
v19.1/secure-a-cluster.md
v19.2/common-errors.md
v19.2/install-cockroachdb-windows.html
v19.2/known-limitations.md
v19.2/recommended-production-settings.md
v20.1/common-errors.md
v20.1/install-cockroachdb-windows.html
v20.1/known-limitations.md
v20.1/recommended-production-settings.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/9551aec790bc3908154c77e24b83cd59a658d04f/
Edited pages:

v19.1/common-errors.md
v19.1/install-cockroachdb-windows.html
v19.1/known-limitations.md
v19.1/recommended-production-settings.md
v19.1/secure-a-cluster.md
v19.2/common-errors.md
v19.2/install-cockroachdb-windows.html
v19.2/known-limitations.md
v19.2/recommended-production-settings.md
v20.1/common-errors.md
v20.1/install-cockroachdb-windows.html
v20.1/known-limitations.md
v20.1/recommended-production-settings.md


Launch Exercise 1

Here is exercise 1.

This looks like the assignment we intended!

This is the first exercise, final code example.


Error with run weekly feature

Hello,
I am setting up a cronjob that is supposed to run on some weekdays using the example below.
class MyCronJob(CronJobBase):
    RUN_WEEKLY_ON_DAYS = [0, 6]
    RUN_AT_TIMES = ['6:30']
    schedule = Schedule(run_weekly_on_days=RUN_WEEKLY_ON_DAYS, run_at_times=RUN_AT_TIMES)

but I get this error "unexpected keyword argument 'run_weekly_on_days" when I try to run the cronjobs.
any help?

any help @JedrzejMaluszczak

It's run_on_days not run_weekly_on_days.

It's run_on_days not run_weekly_on_days.

Maybe it used to be, but not anymore. It's run_weekly_on_days: https://github.com/Tivix/django-cron/blob/master/django_cron/core.py#L22


Upgrade to 1.8

Planed release for 1.8 is Sept 27th (Weds): v1.8.0 release!
Uhm, tomorrow. It's still in v1.8.0-rc1 but we can start upgrading already. Let's upgrade before we go Beta.

Clarify the development workflow with @databus23. This can be done using helm only without going full integration through the stack. The required values can be generated using kubernikus helm values.

Remember to remove this: https://github.com/sapcc/kubernikus/commit/e9fb5890f7e01179eb2082b074df39dd0f98ca16


Post extension install starter page

[ ] should only show once
[ ] should introduce it's limits and capabilities

Extension code for this should be relatively straightforward. Offhand I think this is all you need.
chrome.runtime.onInstalled(reason => {
  if (reason !== 'install') { return; }
  chrome.tabs.create({ url: STARTER_PAGE_PATH });
})

Good onboard docs are a bit more of a challenge.


Incorrect rounding with format '(0,0)' (?)

Shouldn't the second example round to (48) as well?
// Correct
numeral('47.5').format('(0,0)') => 48

// Incorrect?
numeral('-47.5').format('(0,0)') => (47)

Actually this round is right because negative numbers is roll down

It depends on which rules or standards have been followed/implemented.
http://www.wolframalpha.com/input/?i=round(-47.5)
For commercial rounding -48 is correct as well.
https://math.stackexchange.com/questions/3448/rules-for-rounding-positive-and-negative-numbers


use dpf installation action rather than starting the dpf server

Attempt to use the dpf server github action

@ansjhajjar do you know why the action clones the dpf github repo? Woudln't it be more efficient to get the files it needs?

@ansjhajjar do you know why the action clones the dpf github repo? Woudln't it be more efficient to get the files it needs?

Hello @koubaa, the action clones the branch it needs based on the input parameters given, and clones with depth=1. It does need everything in the branch.


No Main branch

Brief Description
All other Unity repos have a main branch and it could be confusing to not have that for this repo as well.
Expected Behavior
A new branch called main
Current Behavior
This repository is missing a main branch.
Suggested Ideas on Resolution
It's fine to make the default branch develop but maybe final releases be sent to a new main branch?

main branch has been created and is set to default branch
@wphyojpl Please update the github actions pipeline accordingly before closing this ticket. Thank you!

Release from main branch: https://github.com/unity-sds/unity-data-services/releases/tag/v1.5.13


AAVE liquidations causing crash

./mev inspect 12605671 crashes due to a problem in the AAVE liquidator module. Rolling back to commit dcdb4e4 seems to resolve the problem.

#223 addresses this


Fixed issue with regenerator when using pawn editors

Pawn editors should now be able to see the implant as a Hediff_Level, like the armor implant.

Published in 2592b41, nice work!


[7.x] Guzzle-like request body summary added to HttpClient RequestException

Small addition to PR https://github.com/laravel/framework/pull/31720
Illuminate\Http\Client\RequestException now contains a short truncated summary of failed response body content.
The code is similar to how Guzzle handles exceptions (e.g. GuzzleHttp\Exception\RequestException).
It may be useful in debugging or log collecting purposes (in Sentry for example). In current iteration of this exception the only way to understand why request failed is to reproduce it manually.

Thanks for the PR. but my feeling is that this is overkill. This component is meant to be a simple API for the 95% of the use cases. It is intended that everyone else simply should just use Guzzle.

Hm, I didn't change the component logic and its API, just made it simpler to trace errors for 95% of use cases 😄
I replaced Guzzle almost everywhere in my projects so you did a great job. That's probably the only missing feature that I face almost daily.

I think that what @Salmondx wrote for the Illuminate\Http\Client\RequestException in this pull-request is a good improvement to handle the Http exceptions.
Currently, in most cases, the class just returns 401 or 403 in logs without any deeper explanation or trace that would help the developers to reproduce the bug.
And in my opinion, add the Guzzle package just to have a simpler debug experience wouldn't be such an elegant use case, once the built-in HttpClient solves most api requests scenarios

Why did you not use Guzzle's \GuzzleHttp\Psr7\get_message_body_summary($response); function directly?

Why did you not use Guzzle's \GuzzleHttp\Psr7\get_message_body_summary($response); function directly instead of duplicating the code?

As I saw laravel have only dev dependency on guzzle and in general as I understand you prefer not to use Guzzle dependencies whenever it is possible. If it is not true and I can use Guzzle functions - will be glad to update 👍

It's impossible to use the Laravel HttpClient without installing Guzzle so I think it's safe to use it here.

Does anybody have any ideas why this change fails on php 7.2-lowest? I don't see any special requirements to php env in guzzle package, may be its some test environment misconfiguration?

@Salmondx guess that function didn't exist for that guzzle version? In which version was it introduced? We might need to bump the minimum version.

@driesvints  As I can see, this function was added to guzzle/psr7 in version 1.5.0: https://github.com/guzzle/psr7/releases/tag/1.5.0
Looks that guzzle 6.4.0 should be safe to use: https://github.com/guzzle/guzzle/blob/6.4.0/composer.json
Should I update it in composer.json from "guzzlehttp/guzzle": "^6.3.1|^7.0" to "guzzlehttp/guzzle": "^6.4.0|^7.0"?

Please don't change the Guzzle version constraint. You need to add the PSR7 Guzzle package to the composer.json, actually.

@GrahamCampbell hm, currently guzzle dependencies are in require-dev. If I add explicit dependency on guzzle/psr7 in require-dev section it will fix broken tests, but can affect someone in "production", don't you think?

but can affect someone in "production", don't you think?

No.

Looks that it should be good now, thanks for advises.

So if someone has 6.3.1 of Guzzle installed this will break?

Looks like it will, but as I understand Graham thinks that it is not the problem? As I can see we should either update minimum guzzle version or copy paste code from guzzle?

@GrahamCampbell was there a big reason you didn't want to up the constraint to 6.4.0?

I don't think we can make use of that function on a stable release. Like Taylor said, people on a lower Guzzle version will see their apps break and we can't enforce them to upgrade since Guzzle isn't a dependency in "require". This will need to be done on master for 8.0

Yeah, I think probably best to resend this to master branch. Sorry.