A 504 Gateway time-out error message appeared when uploading to testflight.

Hello,Last week is ok. I have been reporting errors since this week. I can upload with Xcode.
I checked the answers to the questions, but didn't find the right answers.
fastlane version: 2.102.0
Logs:
.........

[14:35:49]: ----------------------------------
[14:35:49]: --- Step: upload_to_testflight ---
[14:35:49]: ----------------------------------
[14:35:49]: Login to App Store Connect<EMAIL_ADDRESS>[14:35:52]: Login successful
+--------------------+--------------------------------------------------------------------------------------------------+
|                                                     Lane Context                                                      |
+--------------------+--------------------------------------------------------------------------------------------------+
| DEFAULT_PLATFORM   | ios                                                                                |
| PLATFORM_NAME      | ios                                                                                |
| LANE_NAME          | ios uptestflight                                                                                |
| IPA_OUTPUT_PATH    | /Users/perry/Documents/MyProject/CoBandForiOS/ImcoWatch.ipa                                      |
| DSYM_OUTPUT_PATH   | /Users/perry/Documents/MyProject/CoBandForiOS/ImcoWatch.app.dSYM.zip                             |
| XCODEBUILD_ARCHIVE | /Users/perry/Library/Developer/Xcode/Archives/2018-08-31/ImcoWatch 2018-08-31 14.33.10.xcarchive |
+--------------------+--------------------------------------------------------------------------------------------------+
[14:36:52]:
<title>504 Gateway Time-out</title>

504 Gateway Time-out

nginx

+------+----------------------+-------------+
|             fastlane summary              |
+------+----------------------+-------------+
| Step | Action               | Time (in s) |
+------+----------------------+-------------+
| 1    | default_platform     | 0           |
| 2    | build_app            | 162         |
| 💥   | upload_to_testflight | 63          |
+------+----------------------+-------------+

[14:36:52]: fastlane finished with errors

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

➡  Version getters
    https://github.com/fastlane/fastlane/pull/504 [closed] 4 💬
    04 Feb 2017

🔗  You can ⌘ + double-click on links to open them directly in your browser.
 (Spaceship::UnexpectedResponse)stlane-2.102.0/spaceship/lib/spaceship/client.rb:602:in `parse_response': [!]
<title>504 Gateway Time-out</title>

504 Gateway Time-out

nginx

	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/spaceship/lib/spaceship/tunes/tunes_client.rb:256:in `applications'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/spaceship/lib/spaceship/tunes/application.rb:67:in `all'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/spaceship/lib/spaceship/tunes/application.rb:73:in `find'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/pilot/lib/pilot/manager.rb:50:in `fetch_app_id'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/pilot/lib/pilot/manager.rb:30:in `app'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/pilot/lib/pilot/build_manager.rb:27:in `upload'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/actions/upload_to_testflight.rb:16:in `run'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:253:in `block (2 levels) in execute_action'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:232:in `block in execute_action'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:227:in `chdir'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:227:in `execute_action'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/fast_file.rb:149:in `method_missing'
	from Fastfile:22:in `block (2 levels) in parsing_binding'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/lane_manager.rb:56:in `cruise_lane'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
	from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:74:in `run!'
	from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/commands_generator.rb:333:in `run'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/cli_tools_distributor.rb:108:in `take_off'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.102.0/bin/fastlane:20:in `<top (required)>'
	from /usr/local/bin/fastlane:22:in `load'
	from /usr/local/bin/fastlane:22:in `'

same problem

We had multiple similar reports in the last few days of "hickups" on Apple's side. One of them for example:
https://github.com/fastlane/fastlane/issues/13241#issuecomment-417173817
Can you share your error message as well @HaloWang? We will try to handle those as well as possible.

@janpio
This is my error message. Using Jenkins, Fastlane and Fabric. Got 503/504 several times. And even once I forgot to add build_app in Fastfile, still got 504. I'm a chinese and my other Macbook with VPN is OK. I afraid its cause by The GFW of China. 😅
Poor English sorry.
Started by user WangCe
Building in workspace /Users/halowang/.jenkins/workspace/LightClassroom_轻课堂
Checking for pre-build
Executing pre-build step
Checking if email needs to be generated
No emails were triggered.
[LightClassroom_轻课堂] $ /bin/bash /var/folders/34/nxmytzwn3wbf239jf2g9zl400000gq/T/jenkins2637724745683564025.sh
✅打包任务开始
Setting version of project LightClassroom to:
    10022.

Also setting CFBundleVersion key (assuming it exists)

Updating CFBundleVersion in Info.plist(s)...

Updated CFBundleVersion in "LightClassroom.xcodeproj/../LightClassroom/Info.plist" to 10022
Cannot find "LightClassroom.xcodeproj/../\"APP_VERSION\"/s/text=\"[^\"]*\"/text=\"Version: $versionNumber Build: $buildNumber\"/" $PROJECT_DIR/$PROJECT_NAME/LaunchScreen.storyboard"

⚠正式环境
fastlane could not check for updates error: execution expired
[15:14:59]: fastlane detected a Gemfile in the current directory
[15:14:59]: however it seems like you don't use `bundle exec`
[15:14:59]: to launch fastlane faster, please use
[15:14:59]:
[15:14:59]: $ bundle exec fastlane ios beta slient:true upload:true
[15:14:59]:
[15:14:59]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[15:14:59]: Driving the lane 'ios beta' 🚀
[15:14:59]: ⏱正在打包中⏱
[15:14:59]: -----------------------
[15:14:59]: --- Step: build_app ---
[15:14:59]: -----------------------
[15:15:00]: $ xcodebuild -showBuildSettings -workspace LightClassroom.xcworkspace -scheme LightClassroom
[15:15:03]: Command timed out after 3 seconds on try 1 of 4, trying again with a 6 second timeout...
[15:15:05]: Detected provisioning profile mapping: {:"com.izhihuidao.lightclassroom"=>"LightClassroom_Release_8.29"}

+-------------------------------------------------------------------+-------------------------------------------------------------+
|                                                     Summary for gym 2.102.0                                                     |
+-------------------------------------------------------------------+-------------------------------------------------------------+
| workspace                                                         | LightClassroom.xcworkspace                                  |
| scheme                                                            | LightClassroom                                              |
| silent                                                            | true                                                        |
| suppress_xcode_output                                             | true                                                        |
| destination                                                       | generic/platform=iOS                                        |
| export_options.provisioningProfiles.com.izhihuidao.lightclassroom | LightClassroom_Release_8.29                                 |
| output_name                                                       | LightClassroom                                              |
| build_path                                                        | /Users/halowang/Library/Developer/Xcode/Archives/2018-08-31 |
| clean                                                             | false                                                       |
| output_directory                                                  | .                                                           |
| skip_package_ipa                                                  | false                                                       |
| result_bundle                                                     | false                                                       |
| buildlog_path                                                     | ~/Library/Logs/gym                                          |
| skip_profile_detection                                            | false                                                       |
| xcode_path                                                        | /Applications/Xcode.app                                     |
+-------------------------------------------------------------------+-------------------------------------------------------------+

[15:15:05]: ▸ --- xcodebuild: WARNING: Using the first of multiple matching destinations:
[15:15:05]: ▸ { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Generic iOS Device }
[15:15:05]: ▸ { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Generic iOS Device }
[15:15:05]: ▸ { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Generic iOS Device }
[15:15:05]: ▸ { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Generic iOS Device }
[15:15:05]: ▸ { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Generic iOS Device }
[15:15:05]: ▸ { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Generic iOS Device }
[15:15:05]: ▸ { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Generic iOS Device }
[15:15:05]: ▸ { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Generic iOS Device }
[15:17:00]: Generated plist file with the following values:
[15:17:00]: ▸ -----------------------------------------
[15:17:00]: ▸ {
[15:17:00]: ▸   "provisioningProfiles": {
[15:17:00]: ▸     "com.izhihuidao.lightclassroom": "LightClassroom_Release_8.29"
[15:17:00]: ▸   },
[15:17:00]: ▸   "method": "app-store",
[15:17:00]: ▸   "signingStyle": "manual"
[15:17:00]: ▸ }
[15:17:00]: ▸ -----------------------------------------

[15:17:06]: Successfully exported and compressed dSYM file
[15:17:06]: Successfully exported and signed the ipa file:
[15:17:06]: /Users/halowang/.jenkins/workspace/LightClassroom_轻课堂/LightClassroom.ipa
[15:17:06]: ----------------------------------
[15:17:06]: --- Step: upload_to_testflight ---
[15:17:06]: ----------------------------------
[15:17:06]: Login to App Store Connect<EMAIL_ADDRESS>[15:17:12]: Login successful
+--------------------+----------------------------------------------------------------------------------------------------------+
|                                                         Lane Context                                                          |
+--------------------+----------------------------------------------------------------------------------------------------------+
| PLATFORM_NAME      | ios                                                                                |
| LANE_NAME          | ios beta                                                                                |
| IPA_OUTPUT_PATH    | /Users/halowang/.jenkins/workspace/LightClassroom_轻课堂/LightClassroom.ipa                              |
| DSYM_OUTPUT_PATH   | /Users/halowang/.jenkins/workspace/LightClassroom_轻课堂/LightClassroom.app.dSYM.zip                     |
| XCODEBUILD_ARCHIVE | /Users/halowang/Library/Developer/Xcode/Archives/2018-08-31/LightClassroom 2018-08-31 15.15.05.xcarchive |
+--------------------+----------------------------------------------------------------------------------------------------------+
[15:18:12]:
<title>504 Gateway Time-out</title>

504 Gateway Time-out

nginx

+------+----------------------+-------------+
|             fastlane summary              |
+------+----------------------+-------------+
| Step | Action               | Time (in s) |
+------+----------------------+-------------+
| 1    | build_app            | 126         |
| 💥   | upload_to_testflight | 66          |
+------+----------------------+-------------+

[15:18:12]: fastlane finished with errors

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

➡  A 504 Gateway time-out error message appeared when uploading to testflight.
    https://github.com/fastlane/fastlane/issues/13259 [open] 0 💬
    12 minutes ago

➡  Version getters
    https://github.com/fastlane/fastlane/pull/504 [closed] 4 💬
    04 Feb 2017

🔗  You can ⌘ + double-click on links to open them directly in your browser.
/Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/spaceship/lib/spaceship/client.rb:602:in `parse_response': [!]
 (Spaceship::UnexpectedResponse)
<title>504 Gateway Time-out</title>

504 Gateway Time-out

nginx

	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/spaceship/lib/spaceship/tunes/tunes_client.rb:256:in `applications'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/spaceship/lib/spaceship/tunes/application.rb:67:in `all'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/spaceship/lib/spaceship/tunes/application.rb:73:in `find'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/pilot/lib/pilot/manager.rb:50:in `fetch_app_id'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/pilot/lib/pilot/manager.rb:30:in `app'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/pilot/lib/pilot/build_manager.rb:27:in `upload'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/actions/upload_to_testflight.rb:16:in `run'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:253:in `block (2 levels) in execute_action'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:232:in `block in execute_action'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:227:in `chdir'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:227:in `execute_action'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/fast_file.rb:149:in `method_missing'
	from Fastfile:22:in `block (2 levels) in parsing_binding'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/lane_manager.rb:56:in `cruise_lane'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:74:in `run!'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/commands_generator.rb:333:in `run'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/fastlane/lib/fastlane/cli_tools_distributor.rb:108:in `take_off'
	from /Users/halowang/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/bin/fastlane:20:in `<top (required)>'
	from /Users/halowang/.fastlane/bin/bundle/bin/fastlane:22:in `load'
	from /Users/halowang/.fastlane/bin/bundle/bin/fastlane:22:in `'
❌[ fastlane ios beta ] 执行产生错误
HEAD is now at e3b79ec build 10022 release
Build step 'Execute shell' marked build as failure
Checking for post-build
Performing post-build step
Checking if email needs to be generated
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
messageContentType = text/plain; charset=UTF-8
Request made to attach build log
Adding recipients from project recipient list
Adding recipients from trigger recipient list
Setting In-Reply-To since last build was not successful
Successfully created MimeMessage
Sending email to<EMAIL_ADDRESS>Finished: FAILURE

same here

I afraid its cause by The GFW of China. 😅

Yep, that is my impression as well for this very generic error message page you are getting:

<title>504 Gateway Time-out</title>

504 Gateway Time-out

nginx

The Apple error message are a bit more descriptive usually.
We should still be able to at least add a retry on those errors. Do you think that would help? Does it sometimes work?

If you meaning Fastlane on the Mac without VPN, it never work, since 20 hours ago.

Oh - then this really seems to the The GFW :(
"Gateway Timeout" messages that look this this one seem to go away on retry, so we can handle that in our code. But if it never works, we have no workaround (besides you using VPN yourself).
Does this affect all Apple APIs used by fastlane or just some?

Just to confirm @max-ott: That exact same html error page?

These are the error messages I got throughout the last couple of days:
Gateway Timeout - In read

Gateway Timeout
The proxy server did not receive a timely response from the upstream server.
Reference #1.4f83d717.1535718142.12315b90

Gateway Timeout - In read

Gateway Timeout
The proxy server did not receive a timely response from the upstream server.
Reference #1.4f83d717.1535707292.11291701

Gateway Timeout - In read

Gateway Timeout
The proxy server did not receive a timely response from the upstream server.
Reference #1.4f83d717.1535702518.10d00338

etc. etc. Basically only the Reference changes

Yes, that's a different "Gateway Timeout" that comes from Apple themselves, see https://github.com/fastlane/fastlane/issues/13241#issuecomment-417173817 What is reported in this issue is a "simpler" nginx  timeout without the "In read" and Reference or Correlation Key.

Same problem was reported in https://github.com/fastlane/fastlane/issues/13260, there it affected deliver which also uses spaceship in the background of course.

i known the reason and how to solve it! easily!

Well, how do you solve it then? Please share. @xudong98

I have developed a tool sets like fastlane, and i known many problems of apple and fastlane, if you have interest in my work ,you  can send email to me<EMAIL_ADDRESS>

@MarkAMcCorkle ,I have developed a tool sets like fastlane, and i known many problems of apple and fastlane, if you have interest in my work ,you can send email to me<EMAIL_ADDRESS>

Sorry, that sounds more like spam than a solution to repository we are currently discussing. For others, after retrying 4 times I was able to submit successfully. It appears to still be an intermittent Apple issue. My suggestion is to add a retry field / delay we can pass. Then I can just set it to a high number with a delay.

@MarkAMcCorkle Did you have the exact same html returned? (Pure nginx gateway timeout, no reference or customization) Otherwise, see https://github.com/fastlane/fastlane/issues/13241#issuecomment-417173817 which is probably what you were experiencing.

For future readers: If your "Gateway Timeout" page also includes "In read" or "Reference # 1.xyz", you have a different problem and should look at https://github.com/fastlane/fastlane/issues/13241#issuecomment-417173817. This issue is really only about problems that manifest themselves in the exact html page mentioned above.

@janpio it is not the menifest, it is problem of fastlane. recently i have write my tool , my tool can solve this and meanwhile have many function which fastlane can not work

@janpio ，it is not the problem of manifest, it is problem of fastlane. recently i have write my tool , my tool can solve this and meanwhile have many function which fastlane can not work

Then post a link to your tool's GitHub page or explain how it works.  Posting your email address for people to contact is not appropriate. Please understand.

@janpio   my tool would be open in github too, no commeercial purpose, please understand! if you have interest, i  can tell you the some detail  solution!

I wrote before:

Then post a link to your tool's GitHub page or explain how it works.

@janpio  sorry,  the tool's link will be open after one month. And you  can try deliver , it will be failed again. fatslane have many bugs,  if you have interest . i can help you ,because lots of code needs to revise. i can give you a guideline, send you zip files and guideline text .   meanwhile , the files give the some bug of fastlane and how to solve. sorry to make you think that is spam , i will remove my email here.  sincerely.

Location china, I got 504.

<title>504 Gateway Time-out</title>

504 Gateway Time-out

nginx

And fix this issues by switch on my VPN.

@xudong98 Thank you for removing your email. This thread should be about finding a way to fix this issue within the current toolset which is fastlane. If you have a valid solution for solution in the future, we would appreciate either a comment on what is broken and how to fix it or a pull request with a solution 👌 We definitely don’t want to stop your from working on your tool and we aren’t saying your tool isn’t a valid solution but the conversation about it does not belong here if it can’t be in usable right now within a fastlane context 🙃
Sent with GitHawk

Same here in

get same problem,chinese

I have made it works as a workaround by set dns server out of china.
it seems the root cause is some old url running over apple cdn does not fully support all api request in china. That's why it works with manually publish by xcode.
Please update all the api addresses as the same as xcode so this problem may dismiss.

Can you help us by listing those old URLs and what it should be replace with @samchang8826?
Some of the functionality in fastlane is not part of Xcode at all but usually done manually in App Store Connect.

 (Spaceship::UnexpectedResponse)
<title>504 Gateway Time-out</title>

504 Gateway Time-out

nginx

I open or close VPN, but it not use, still failed with the error.

same problem

I am in China.
Connect the VPN, I still didn't solve the problem.

<title>504 Gateway Time-out</title>

504 Gateway Time-out

nginx

I use the node is US, California.

It seems not caused by GFW. This issue appear about four days ago, and I try to run fastlane pilot → fail randomly, but never get this error in ApplicationLoader ( I have tried about 5 apps and ten times per app).

It might very well be that ApplicationLoader is using another API internally. We will try to investigate.
(You might be able to help as well - find a way to see what URLs are being requested from your computer (using e.g. https://mitmproxy.org/) and log both the traffic from using fastlane pilot and the one from using ApplicationLoader. Post the result here.)

@janpio it's hard to log the traffic as the client does not accept self-signed certificate, so I could only see some traffic to itunesconnect.apple.com:443 when the error happens. please point a way to inject self-signed certificate into fastlane to track this issue.

@janpio I have found the url finally.
$ dig itunesconnect.apple.com
; <<>> DiG 9.10.6 <<>> itunesconnect.apple.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15271
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 4096
;; QUESTION SECTION:
;itunesconnect.apple.com.	IN	A
;; ANSWER SECTION:
itunesconnect.apple.com. 996	IN	CNAME	itunesconnect-cdn.itunes-apple.com.akadns.net.
itunesconnect-cdn.itunes-apple.com.akadns.net. 996 IN CNAME itunesconnect-china.itunes-apple.com.akadns.net.
itunesconnect-china.itunes-apple.com.akadns.net. 996 IN	CNAME itunesconnect.apple.com.mwcname.com.
itunesconnect.apple.com.mwcname.com. 996 IN CNAME applewsashark.dtwscache.ourwebcdn.com.
applewsashark.dtwscache.ourwebcdn.com. 300 IN A	<IP_ADDRESS>
applewsashark.dtwscache.ourwebcdn.com. 300 IN A	<IP_ADDRESS>
applewsashark.dtwscache.ourwebcdn.com. 300 IN A	<IP_ADDRESS>
applewsashark.dtwscache.ourwebcdn.com. 300 IN A	<IP_ADDRESS>
;; Query time: 3 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Tue Sep 04 10:25:57 CST 2018
;; MSG SIZE  rcvd: 303
$ curl -vv "https://itunesconnect.apple.com/WebObjects/iTunesConnect.woa/ra/apps/manageyourapps/summary/v2"

Trying <IP_ADDRESS>...
TCP_NODELAY set
Connected to itunesconnect.apple.com (<IP_ADDRESS>) port 443 (#0)
ALPN, offering h2
ALPN, offering http/1.1
Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
successfully set certificate verify locations:
CAfile: /etc/ssl/cert.pem
CApath: none
TLSv1.2 (OUT), TLS handshake, Client hello (1):
TLSv1.2 (IN), TLS handshake, Server hello (2):
TLSv1.2 (IN), TLS handshake, Certificate (11):
TLSv1.2 (IN), TLS handshake, Server key exchange (12):
TLSv1.2 (IN), TLS handshake, Server finished (14):
TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
TLSv1.2 (OUT), TLS change cipher, Client hello (1):
TLSv1.2 (OUT), TLS handshake, Finished (20):
TLSv1.2 (IN), TLS change cipher, Client hello (1):
TLSv1.2 (IN), TLS handshake, Finished (20):
SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
ALPN, server accepted to use h2
Server certificate:
subject: businessCategory=Private Organization; <IP_ADDRESS>.4.1.3<IP_ADDRESS>.3=US; <IP_ADDRESS>.4.1.3<IP_ADDRESS>.2=California; serialNumber=C0806592; C=US; ST=California; L=Cupertino; O=Apple Inc.; OU=Internet Services for Quantil; CN=itunesconnect.apple.com
start date: May 30 00:00:00 2018 GMT
expire date: Mar  4 12:00:00 2019 GMT
subjectAltName: host "itunesconnect.apple.com" matched cert's "itunesconnect.apple.com"
issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 Extended Validation Server CA
SSL certificate verify ok.
Using HTTP2, server supports multi-use
Connection state changed (HTTP/2 confirmed)
Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
Using Stream ID: 1 (easy handle 0x7fd7c2800400)

GET /WebObjects/iTunesConnect.woa/ra/apps/manageyourapps/summary/v2 HTTP/2
Host: itunesconnect.apple.com
User-Agent: curl/7.54.0
Accept: /

Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 504
< server: nginx
< date: Tue, 04 Sep 2018 02:24:55 GMT
< content-type: text/html
< content-length: 176
<

504 Gateway Time-out

504 Gateway Time-out
nginx

* Connection #0 to host itunesconnect.apple.com left intact

how to solve it

same problem

Does everybody in this channel try to upload their build via Fastlane from behind the GFW ?
👍 YES 👎 NO

How about VPN ? I choose 👎. @StevenMasini  😥

same

same here, vpn sometimes work, sometimes not.  seems 2 b a random bug.

@janpio It's worked after change itunesconnect.apple.com to appstoreconnect.apple.com. I do it with following command:
$ cd /Users/xxxxxxxxx/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.102.0/spaceship/

$ grep -lr itunesconnect.apple.com . | xargs gsed -i 's/itunesconnect\.apple\.com/appstoreconnect\.apple\.com/g'

Yes, but can not replace all the domain, one domain keeps itunesconnect.apple.com. If replace all,you will failed randomly. The service key domain keeps old domain.

@xudong98 Talk is cheap, show us the code. If you don't have any valuable suggestion for this fastlane issue, please stop talking. If not, show your code.

@janpio I updated to the latest release 2.103.0 which integrate the  Merged
[spaceship] update API endpoints to use https://appstoreconnect.apple.com but I am still getting 504 Gateway Time-out.
@snipking If I am not mistaken, that PR is also what you suggested ?
Still yesterday, I successfully upload my build to the App Store using XCode without VPN (I am also behind the GFW).
If this problem only concern China, then I am wondering if this isn't due to the African meeting happening right now in Beijing. GFW often get reinforced during official meeting.
Anyway a solution would be to use a remote CI service outside of China then.

Cause another error #13284 when I upgrade to 2.103.0 in this morning. Does someone get this too?

@StevenMasini Best create a new issue, mention that this is with 2.103.0 and include the common information and most important the whole error output.
I suspect there will be a patch release as soon as @joshdholtz is awake, fixing what broke with 2.103.0. Until then, let's collect as much information as possible.

I have updated the, but new problems appeared。
Service key is empty。
@janpio see #13287

Yes, there is currently a problem caused by the changes done in 2.103.0 - so stuff is broken right now.
@chronweigle already fixed it in https://github.com/fastlane/fastlane/pull/13286 and we are currently testing and seeing if this covers all failure cases. As soon as this is confirmed, there will be a 2.103.1 release. Sorry for that.
Until then, you best do not update or downgrade again to 2.102.0

That's all right,so I am 2.103.1 version.

@StevenMasini What I do is change itunesconnect.apple.com to appstoreconnect.apple.com on 2.102.0 and it works (without VPN in Shanghai or with VPN through Taiwan) . I guess the root cause is apple now rebranding itunesconnect as appstoreconnect and they have separate data center in china (the Guizhou center). Maybe there's some differences with other data center.

same

@janpio I updated this morning to Fastlane 2.103.1 which add [spaceship] use itunesconnect.com hostname when looking up itc_service_key for olympus session and I am not getting the 504 Gateway Time-out error anymore.
This issue is fixed for me, I think @snipking is probably right. Might be just a problem of re-branding from Apple and their data-center in China.

Wheee, glad we could fix it! 🚀
Please open a new issue if you have any follow up problems.

@HaloWang Have u resolve the 504 question?

@xudong98 Hello, where is ur solution?


Exception when iframe content not fully loaded

I get the following runtime error on certain pages:
PreviewMate.js?v=1707043428:110 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'querySelectorAll')     at PreviewMate.js?v=1707043428:110:78     at Array.forEach (<anonymous>)     at Object.attatchPreviewBlockEventListeners (PreviewMate.js?v=1707043428:96:53)     at Object.initDevicePreviewIframe (PreviewMate.js?v=1707043428:85:31)     at Object.initPreviewModule (PreviewMate.js?v=1707043428:54:31)
After a bit of debugging, I noticed that the content of the iframe is null when pages are complex and take longer to load. As a local fix I check for the iframe to be fully loaded:
iframe.addEventListener("load", function() {    const previewBlocks = iframe.contentWindow.document.body.querySelectorAll(previewBlocksQuery);    ...

Hey @abinggeli, I haven't been able to reproduce the error yet but i've looked through the code and see where there could be an issue.
Can you test the PreviewMate.js code in pull request #2 and see if that fixes the error you're encountering?
Thanks! - Nick

Hi Nick,
Yeah, the pull request solves my problem. Many thanks for the quick fix. The plugin is really super helpful.
Best regards,
Andy

Am 06.02.2024 um 04:18 schrieb Nick Hamilton @.***>:
Hey @abinggeli https://github.com/abinggeli, I haven't been able to reproduce the error yet but i've looked through the code and see where there could be an issue.
Can you test the PreviewMate.js code in pull request #2 https://github.com/nicholashamilton/craft-preview-mate/pull/2 and see if that fixes the error you're encountering?
Thanks! - Nick
—
Reply to this email directly, view it on GitHub https://github.com/nicholashamilton/craft-preview-mate/issues/1#issuecomment-1928711235, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGE74RTANR4ZIOGSUP4YTE3YSGOHBAVCNFSM6AAAAABCYZNTUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYG4YTCMRTGU.
You are receiving this because you were mentioned.

Hey @abinggeli,
It's great to hear that PR solved the issue. Thank you bringing awareness to that!
Glad you are enjoying the plugin 🎉
I'll be releasing an update with the changes later today.

Hey @abinggeli,
It's great to hear that PR solved the issue. Thank you bringing awareness to that!
Glad you are enjoying the plugin 🎉
I'll be releasing an update with the changes later today.


Upgrade to RxJava2

As the library is incompatible with RxJava2 it should be updated to the newest version.
As RxJava2 disallows emitting null the API had to be adapted to this new design approach.
Instead of emitting null on the Observables the streams emit StoreEvent and ListStoreEvent respectively.
I am not sure if you want to merge this into RxStore or create a new project RxStore2 in any case it would be nice to get a RxJava2 compatible RxStore.

Thanks for the PR! I've actually been toying around with a few different approaches of my own over the past few days. I'll submit a PR shortly and we'll compare notes. My attempts have been a bit more dramatic, as I figured this might be a good time to make some changes to the API for the better.

Sounds good.
I also found Maybe this weekend, which might be a good approach for finding Items in the store. As Single is invoking onError if it cannot find the item.
Anyway I am looking forward to the RxJava2 upgrade as Android DEX throws an error when you want to use RxJava2 and the current version of RxStore.

This PR can be closed as @chris-horner has created his own PR which includes the upgrade to RxJava2 and a general API overhaul.
https://github.com/Gridstone/RxStore/pull/36


Display 'Close ...' as the 'Close Query' button's name in the toolbar of one table

Storage Explorer Version: 1.15.1
Build: 20200904.2
Branch: main
Platform/OS: Windows 10/ Linux Ubuntu 16.04 / MacOS Catalina
Architecture: ia32/x64
Regression From: Previous release (1.15.1)
Steps to reproduce:

Expand one storage account -> Tables.
Create a table -> Click 'Query' on the toolbar.
Check the name of the 'Close Query' button.

Expect Experience:
Display 'Close Query'.

Actual Experience:
Display 'Close ...'.

Verified this issue on build 20200912.3. Fixed


CallbackProperty no longer working for Polygon Entities

A concise explanation of the problem you're experiencing.

var dynamicPositions = new Cesium.CallbackProperty(function () {
 return positions;
}, false);

This used to be a valid input for a polygon entity hierarchy, but now since CesiumJs version 1.60 this no longer works. This approach follows what was (at some point at least) the suggested method from one of the Sandcastle examples to allow users to draw in the scene. This approach still works for at least polylines and billboards. Seems very likely the issue must be related to this update in the 1.60 release "Added support for polygon holes to CZML." The example below should clarify the problem.

A minimal code example. If you've found a bug, this helps us reproduce and repair it.

Sandcastle
Switching to the commented out code provides a more helpful error report, but also fails. Changing "hierarchy: dynamicPositions" to just "hierarchy: positions" behaves normally, but of course if this example actually leveraged the callback in a meaningful way this would be undesirable.

Context. Why do you need to do this? We might know a better way to accomplish your goal.

We're using position callback properties for dynamic editing.

The Cesium version you're using, your operating system and browser.

Last working in Cesium 1.59.
Broken in Cesium 1.60 and 1.61.
(Ubuntu 19.04 + Chrome)

Here's the corrected version of your example:
Sandcastle
PolygonGraphics.hierarchy was always documented as a property of type PolygonHierarchy, meaning that any Property must produce a value of that type.  That would include the CallbackProperty from your example:
var dynamicPositions = new Cesium.CallbackProperty(function() {
    return new Cesium.PolygonHierarchy(positions);
}, false);

Adapting a constant Cartesian array to a PolygonHierarchy was left for backwards compatibility, but using a Cartesian array was undocumented behavior since the hierarchy property was introduced.

good


Add image to GoogleLingSitemapUrl

Currently we can add alternatees by using GoogleLinkSitemapUrl and images by using GoogleImageSitemapUrl. In my case I want to have both at the same time to achieve following output:
<url>
  <loc>http://www.example.com/en/product-1</loc>
  <xhtml:link rel="alternate" hreflang="de" href="http://www.example.com/de/product-1" />
  <xhtml:link rel="alternate" hreflang="en" href="http://www.example.com/en/product-1" />
  <image:image>
   <image:loc>http://www.example.com/image1.jpg</image:loc>
  </image:image>
  <image:image>
   <image:loc>http://www.example.com/image2.jpg</image:loc>
  </image:image>
</url>

What do you think? My idea is to add images to GoogleLinkSitemapUrl and maybe deprecate GoogleImageSitemapUrl. I will implement it myself but want to confirm solution with the community first

same here

Pull request welcome.


Bump json bound

Already edited on hackage. This lets it build with more recent ghcs.

Thanks! I guess since you already made a revision, a new release is not necessary at this point?

correct :-)


GUI kit for designers

#i'm an interface designer, and my developer suggested we use NGX in a project.
it would be amazing to have a GUI kit to adjust features, labels, using the same identity, icons, etc.

Hi @paulocholla, we don't have a GUI Kit for now, unfortunately, but we will think if we can share it somehow in future.


jax.numpy.take() won't return the right value for out-of-bound indices in version 0.4.11

Description
0.4.11						print(jax.version)
[ 0.  1.  2.  3.  4. nan nan]	<----print(jnp.take(jnp.arange(5).astype(float), jnp.arange(7)))
[0. 1. 2. 3. 4. 4. 4.]		<----print(jnp.take(jnp.arange(5).astype(float), jnp.arange(7), mode='clip'))
[0. 1. 2. 3. 4. 4. 4.]		<----print(np.take(np.arange(5).astype(float), np.arange(7), mode='clip'))
Jax 0.4.11, jaxlib 0.4.10, without jax-metal
0.4.11						print(jax.version)
[0. 1. 2. 3. 4. 0. 0.]		<----print(jnp.take(jnp.arange(5).astype(float), jnp.arange(7)))
[0. 1. 2. 3. 4. 0. 0.]		<----print(jnp.take(jnp.arange(5).astype(float), jnp.arange(7), mode='clip'))
[0. 1. 2. 3. 4. 4. 4.]		<----print(np.take(np.arange(5).astype(float), np.arange(7), mode='clip'))
Jax 0.4.11, jaxlib 0.4.10, jax-metal 0.0.3
Looks like Jax-metal caused this
What jax/jaxlib version are you using?
jax 0.4.11, jaxlib 0.4.10, Jax-metal 0.0.3
Which accelerator(s) are you using?
GPU
Additional system info
python 3.10.12
NVIDIA GPU info
No response

Thanks for the report - I'm not sure if this was closed on purpose, but note that the jax-metal plugin is experimental and still has a number of issues that make its outputs incompatible with JAX's behavior on other backends. You can find a list of known issues at the Apple-GPU-Metal-plugin tag.


Make the page faster

The updating of debug box (which is display: none) every second is not neccessary. And it slows down the site.

Thanks :smile:
Welcome to the GitHub anyway.


Update compatibility.md to split coroutine.close from lua_resetthread

Considering how coroutine.close was added recently, it would make sense to rework this document to split lua_resetthread and coroutine.close because of this, to mark one as ticked and the other as not currently available.

We do implement lua_resetthread so we should just mark the existing row as complete


SNOW-1331246: Hashlib type hints breaks snowpark for python 3.9

Please answer these questions before submitting your issue. Thanks!

What version of Python are you using?

Python 3.9.17 (main, Jun 29 2023, 09:32:35)
[Clang 14.0.3 (clang-14<IP_ADDRESS>.1)]

What operating system and processor architecture are you using?

macOS-14.4.1-arm64-arm-64bit

What are the component versions in the environment (pip freeze)?

freeze
agate==1.7.1
annotated-types==0.6.0
appdirs==1.4.4
appnope==0.1.4
asn1crypto==1.5.1
asttokens==2.4.1
attrs==23.2.0
Babel==2.14.0
certifi==2024.2.2
cffi==1.16.0
chardet==5.2.0
charset-normalizer==3.3.2
click==8.1.7
cloudpickle==2.2.1
colorama==0.4.6
comm==0.2.2
cryptography==42.0.5
dbt-core==1.7.11
dbt-extractor==0.5.1
dbt-hubspot-dependencies==0.6.5
dbt-semantic-interfaces==0.4.4
dbt-snowflake==1.7.3
debugpy==1.8.1
decorator==5.1.1
diff_cover==8.0.3
exceptiongroup==1.2.0
executing==2.0.1
filelock==3.13.3
hypothesis==6.100.1
idna==3.6
importlib-metadata==6.11.0
iniconfig==2.0.0
ipykernel==6.29.4
ipython==8.18.1
isodate==0.6.1
jaraco.classes==3.4.0
jedi==0.19.1
Jinja2==3.1.3
jinja2-simple-tags==0.6.1
jsonschema==4.21.1
jsonschema-specifications==2023.12.1
jupyter_client==8.6.1
jupyter_core==5.7.2
keyring==24.3.1
leather==0.4.0
Logbook==1.5.3
markdown-it-py==3.0.0
MarkupSafe==2.1.5
mashumaro==3.11
matplotlib-inline==0.1.6
mdurl==0.1.1
minimal-snowplow-tracker==0.0.2
more-itertools==10.2.0
msgpack==1.0.8
multimethod==1.10
mypy-extensions==1.0.0
nest-asyncio==1.6.0
networkx==3.2.1
numpy==1.26.4
packaging==24.0
pandas==2.2.2
pandera==0.18.3
parsedatetime==2.6
parso==0.8.4
pathspec==0.11.2
pexpect==4.9.0
platformdirs==3.11.0
pluggy==1.4.0
prompt-toolkit==3.0.43
protobuf==4.25.3
psutil==5.9.8
ptyprocess==0.7.0
pure-eval==0.2.2
pycparser==2.22
pydantic==2.6.4
pydantic_core==2.16.3
Pygments==2.17.2
PyJWT==2.8.0
pyOpenSSL==24.1.0
pytest==8.1.1
python-dateutil==2.9.0.post0
python-slugify==8.0.4
pytimeparse==1.1.8
pytz==2024.1
PyYAML==6.0.1
pyzmq==25.1.2
referencing==0.34.0
regex==2023.12.25
requests==2.31.0
rich==13.7.1
rpds-py==0.18.0
ruamel.yaml==0.18.6
ruamel.yaml.clib==0.2.8
six==1.16.0
snowflake-connector-python==3.7.1
snowflake-snowpark-python==1.14.0
sortedcontainers==2.4.0
sqlfluff==2.3.5
sqlfluff-templater-dbt==2.3.5
sqlparse==0.4.4
stack-data==0.6.3
tblib==3.0.0
text-unidecode==1.3
toml==0.10.2
tomli==2.0.1
tomlkit==0.12.3
tornado==6.4
tqdm==4.66.2
traitlets==5.14.2
typeguard==4.2.1
typing-inspect==0.9.0
typing_extensions==4.10.0
tzdata==2024.1
urllib3==1.26.18
wcwidth==0.2.13
wrapt==1.16.0

What did you do?

Recently installed the latest snowflake.snowpark, and now a basic import cannot run. All I ran is import snowflake.snowpark

stacktrace
  File "/Users/tmcclintock/projects/scratch/failing_import.py", line 1, in <module>
    import snowflake.snowpark
  File "/Users/tmcclintock/.pyenv/versions/3.9.17/envs/dbt/lib/python3.9/site-packages/snowflake/snowpark/__init__.py", line 47, in <module>
    from snowflake.snowpark.async_job import AsyncJob
  File "/Users/tmcclintock/.pyenv/versions/3.9.17/envs/dbt/lib/python3.9/site-packages/snowflake/snowpark/async_job.py", line 12, in <module>
    from snowflake.snowpark._internal.analyzer.analyzer_utils import result_scan_statement
  File "/Users/tmcclintock/.pyenv/versions/3.9.17/envs/dbt/lib/python3.9/site-packages/snowflake/snowpark/_internal/analyzer/analyzer_utils.py", line 10, in <module>
    from snowflake.snowpark._internal.analyzer.binary_plan_node import (
  File "/Users/tmcclintock/.pyenv/versions/3.9.17/envs/dbt/lib/python3.9/site-packages/snowflake/snowpark/_internal/analyzer/binary_plan_node.py", line 7, in <module>
    from snowflake.snowpark._internal.analyzer.expression import Expression
  File "/Users/tmcclintock/.pyenv/versions/3.9.17/envs/dbt/lib/python3.9/site-packages/snowflake/snowpark/_internal/analyzer/expression.py", line 9, in <module>
    import snowflake.snowpark._internal.utils
  File "/Users/tmcclintock/.pyenv/versions/3.9.17/envs/dbt/lib/python3.9/site-packages/snowflake/snowpark/_internal/utils.py", line 386, in <module>
    hash_algo: hashlib._hashlib.HASH, path: str, chunk_size: int, whole_file_hash: bool
AttributeError: module 'hashlib' has no attribute '_hashlib'

What did you expect to see?

I expected to be able to import anything from snowpark.
The stacktrace suggests that the type hint is busted and comes from referencing a private attribute of hashlib. IMO, this is poor practice, because the hashlib maintainers clearly did not expect folks to be referencing private attributes. Can we please decouple snowpark from the internal API of hashlib? I suggest using a Protocol class or perhaps an enum that maps string names to hash algos. Something like:
from enum import Enum

hash_algo = Enum('hash_algo', ['md5', 'sha512', 'sha256'])

Can you set logging to DEBUG and collect the logs?

The logging statement did not generate any additional output.
Thank you!

hi @tmcclintock , thanks for the feedback. weirdly I'm not able to reproduce the issue in my env. I checked the code in hashlib, so there is a chance that _hashlib can be None, and it might be caused by some dependency diff.
but I agree that type hint referencing a private module could be unreliable for, and would better be avoided or at least should not cause any error.
I have made a quick fix for it just to unblock: https://github.com/snowflakedb/snowpark-python/pull/1406/files.

thank you @sfc-gh-aling! Appreciate your quick fix here. Good luck with the long term solution!


[Feature] Add ability to pass through metrics to final ad reporting models

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
Currently there are variables in all of the upstream platform specific ad reporting packages that allow for user defined metrics to be included in the end models. However, this same functionality is not available to persist through to the final roll up ad reporting models.
This feature is to explore creating a way (or a new variables) to allow these upstream passthrough variables to persist to the roll up models.
Describe alternatives you've considered
Making custom adjustments or doing further model builds following the dbt package models.
Are you interested in contributing this feature?

[x] Yes.
[ ] Yes, but I will need assistance and will schedule time during your office hours for guidance.
[ ] No.

Anything else?
PR #84 is a great start at tackling this feature update.

This is now possible in the latest release (v1.4.0) of the Ad Reporting package! Closing this issue as the feature is now live.


Adds 'query' object to activeState object

@jbalsas, @eduardolundgren
Hey, wanted to send a PR for this and see what you think. One thing we needed in Faro was the ability to extract the query params for a route. Let me know if this makes sense to you or if I should add anything else. Thanks

LGTM. Maybe rename to .query like express?

@eduardolundgren updated it to be query.

@Robert-Frampton

LGTM. @Robert-Frampton could you merge and release a version? Thanks.


Storing URLs in database to prevent reloading existing data

Next part of #78

Review status: 0 of 2 files reviewed at latest revision, 3 unresolved discussions.

LovefieldService.js, line 94 [r1] (raw file):
Do you actually need to do this? Is there any time that we pass in a string that isn't a url?

LovefieldService.js, line 106 [r1] (raw file):
null, perhaps.

LovefieldService.js, line 539 [r1] (raw file):
testRuns

Comments from the review on Reviewable.io

Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion.

angular_scripts.js, line 66 [r2] (raw file):
Did you get the types the wrong way around here and below?

Comments from the review on Reviewable.io

Reviewed 1 of 2 files at r2, 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from the review on Reviewable.io


HUE-9273 [notebook] Encoding Error when use non-ascii characters in sql-editor-variables

Tested in my Local Cluster

Excellent!
I also just did an example of test that I am going to push https://review.cloudera.org/r/15073/ https://github.com/cloudera/hue/commit/61c1cdbaee140c6b5ea17f7f1f7fcd6f80904a81
(that way we automate the testing there)
Feel free to extend it with your own case test afterwards!

Thanks for reviewing Romain. i will take care of Test cases from next time.
Please help me review this and Commit. https://review.cloudera.org/r/15072/

I am reviewing it, and updating the branch to re-kick the CI


FlowRouter.path lookup by route name returns route name instead of path

on the server, this:
FlowRouter.path("blogPostRoute", params, queryParams);
conveniently returns this:
"blogPostRoute"
haven't tested on client.

Is this on the server? Would love to have some sample code.

Yes, on the server. But I tested on client and it's also not correct.
Sample code is nothing special:
on client, route definition
FlowRouter.route '/password/reset/:token',
  name: 'resetPassword'
  action: ->
    BlazeLayout.render "resetPassword"

on server
FlowRouter.path('resetPassword', { token: '1234' });

returns "resetPassword" instead of /password/reset/1234
on client
FlowRouter.path('resetPassword', { token: '1234' });

returns /password/reset instead of /password/reset/1234

It's working pretty well here: https://github.com/arunoda/hello-react-meteor/blob/master/both/router.jsx
I don't write coffeescript. I suspect this is a syntax issue.
May be someone could help.

Na, I don't think so, it compiles to:
FlowRouter.route( '/password/reset/:token',  {
  name: 'resetPassword',
  action: function() {
    return BlazeLayout.render("resetPassword");
  }
});

But I'll make a repro in javascript for testing. Maybe another package is interfering or something. I'm on v2.7.0 by the way.
(FYI, kind of another topic, but how I found out is because I'm helping lookback:emails to support FR as well as IR. It will use Picker on server side instead of IR, but it has some template helpers that will use either IR or FR. Perhaps it would be interesting to keep a list of packages that support FlowRouter. I'm sure more packages will be migrating).

Hmm. Give me a repo. I'll digg into it.

Here it is: https://github.com/satyavh/Flowrouter-test
It works correct on client, not on server. Check console in browser and terminal for logout

It will have a look at this.
On 2015 ඔක් 27, අඟහ at ප.ව. 4.44 Satya van Heummen<EMAIL_ADDRESS>wrote:

Here it is: https://github.com/satyavh/Flowrouter-test
It works correct on client, not on server. Check console in browser and
terminal for logout
—
Reply to this email directly or view it on GitHub
https://github.com/kadirahq/flow-router/issues/371#issuecomment-151458669
.

This is because, you've only created routes in the client. You need to create routes in a place where it can be seen by both the client and the server.
Here's the fixed app: https://gist.github.com/arunoda/d1247f829f701babf597

Well, that explains! As Flow Router is client only, I never thought about putting routes somewhere where the server can see them as well. But makes sense. Thanks for checking!


Add support to GTK+ and Windows look and feel

This functionality works on Windows and Linux [TESTED]. On Windows, the app use Windows Look and Feel and on linux, it use GTK+.

Nice, thank you very much 👍


Bluetooth: unittest: DLE procedure routines

Unit tests for the time calculations in the DLE update procedure.
This shows a.o. how we can unittest for different configuration settings, for example CODED and 2M phy.
This will avoid regression errors.
Mockup functions are empty, but required for compilation.
Signed-off-by: Andries Kruithof<EMAIL_ADDRESS>

Needs to wait with merging until #23875 is in master.

@kruithofa seems this has not gotten attention.
If still valid, could you reopen and let us know if it is ready for merge.


test(iroh-cli): fix flaky behaviour of cli_provide_file_resume

Description
In windows there is no way to copy a file being accessed by another process in an accessible way. This is what makes this test fail since it attempt to copy the blobs.db folder a couple of times while the iroh instance that handles is running.
The change is simple: shutdown the provider, copy the files, re-start the provider. From my perspective, this does not affect what the test is attempting to assert.
Now, since this includes re-starting the iroh instance that provides the files several times, and we match on output, sometimes we can get weird logs related to shutdown. One of those (and the only one I have seen so far) is for a netcheck report and didn't finish on time. Instead of logging this in the reportgen actor, the error is bubbled up to be handled by the netcheck actor (which will have shutdown by then) thus reducing noise and allowing for better error handling in the future
Breaking Changes
n/a
Notes & open questions
n/a
Change checklist

[x] Self-review.
[ ] Documentation updates following the style guide, if relevant.
[x] Tests if relevant.
[ ] All breaking changes documented.

while I had to re-add the flaky mark since one of the windows worflows failed, I think it's still an improvement: the test is now flaky instead of failing 100% of the time. Addressed your need and if it's ok I'll merge and we can keep looking into the new kinds of failures in later antiflaky attempts


Remote Site Test Manager shall be able to view the lab order for VA patient.

As a product owner, I want to build functionality where Remote Site Test Manager should be able to view the lab order for VA patient.

A mock-up will not be available for Sprint 1 due to the delay in setting up the development environment. Move to Sprint 2.

1/12 - Update Product Backlog Meeting ... the feature is valid. No user stories have been written for this to-date.


Don't access loop variables in goroutines directly

Inspired by https://github.com/lightningnetwork/lnd/pull/7186.
I checked all anonymous goroutines to make sure they don't access any loop or other temporary variables.
This PR fixes the found instances and also contains some readability improvements to visually highlight defer statements better.

I think the ones that don't iterate in a for loop are fine - see comment https://github.com/lightningnetwork/lnd/pull/7186#discussion_r1028534104

I think the ones that don't iterate in a for loop are fine.

I agree after taking a look at your code examples in the referenced PR. I also wasn't sure if the type conversion of the switch already put things on the stack. But I still feel like this more explicit version also puts more emphasis on the goroutine using a variable from outside of its context. So I'm going to merge this anyway.


Feature/prefix globals warning

Since we've released the Theme Sniffer plugin, more and more authors and reviewers are complaining about the prefix all globals sniff.
This PR downgrades it to a warning instead of an error.

I just saw your comment @jrfnl in #189.
I think that rewording of the error message could help, but we would still get a lot of false positives.

I think that rewording of the error message could help, but we would still get a lot of false positives.

Correct me if I'm wrong, but from what I've seen from the discussion, you're not getting false positives, but you want to allow non-prefixed variables in a certain context.
You should still want to forbid non-prefixed classes, global functions etc.
If that's the case, there are two options:

Either downgrade a specific errorcode to a warning, not the whole sniff.
Or (better) extend the sniff and overload the relevant method to bow out early in case of theme template file, but still trigger an error in a other cases.

The fact that people are getting annoyed with the message, is not a fault of the sniff, but a case of educating people to write better code.

Yeah, the issue (from what I've seen) is that non prefixed variables in the template files trigger this sniff. And since there is no required way of loading the templates (like having them all in a specific folder in a theme called templates), it's not possible for the sniffer to know what is a template file and what isn't.
I'll try to get a hold of a few themes and see where the faulty code is, and then try to implement your suggestions. I'll work in this PR so it can stay open.
Thanks for the suggestions and advice :+1:

it's not possible for the sniffer to know what is a template file and what isn't

I had a little think about that and I think we can probably detect whether something is a template file with a reasonably high degree of certainty (providing the customized sniff is only run on themes).
I'm thinking along the following lines:

File isn't called functions.php.
File contains inline HTML.
File does not contain declarations for classes, functions and such.

Does that help ?

I might be underthinking this, but wouldn't it be possible to have a list of 'template-files' that would be right 90%+ of the time?
/template-parts/*
/templates/*
taxonomy-*
category-*
tag-*
page-*
archive-*
single-*
sidebar-*
header.php
footer.php
index.php
comments.php
search.php
searchform.php
404.php

Sure there would be edge cases, but if it eliminated 90% of the 'false-positives', would it be worth it?

I don't think a whitelist is a good idea. I agree with detecting that it's a template. In fact, my theme would not pass because my template files are output as widgets, so would not match the whitelist at all.
And the other half of the problem is that those template files still should not be modifying WordPress globals, so they can't just be skipped. (or is that two different sniffs?)

I think that the globals sniff would just have specific error codes downgraded to warnings, but a separate sniff would be used for the templates and checking if globals are present there.

wouldn't it be possible to have a list of 'template-files' that would be right 90%+ of the time?

I don't think a whitelist is a good idea. I agree with detecting that it's a template. In fact, my theme would not pass because my template files are output as widgets, so would not match the whitelist at all.

@DannyCooper @joyously Both approaches could be combined, a file whitelist first, for files not on that list: check the contents of the file.
If I remember correctly, the WPCS Filename sniff already has a template file name regex which could possibly be used or if not used directly, used a inspiration.

And the other half of the problem is that those template files still should not be modifying WordPress globals, so they can't just be skipped. (or is that two different sniffs?)

Those are two different sniffs, so that shouldn't be a problem and the above would only be applied to the one sniff, the files would not be skipped for any other sniffs.

@jrfnl I'd like to work on this so that I can brush up on writing the sniffs, but I'd need some help 🙂
You've mentioned downgrading certain errorcode to a warning. That would be done in phpcs.xml.dist or?
About sniff extension, I've seen WordPress.WP.GlobalVariablesOverride.OverrideProhibited triggered in template files, so the steps to override this would be:

Create a new sniff, say GlobalVariablesOverrideTemplatesExclude that extends the GlobalVariablesOverrideSniff

use WordPressCS\WordPress\Sniffs\WP\GlobalVariablesOverrideSniff;

class GlobalVariablesOverrideTemplatesExclude extends GlobalVariablesOverrideSniff {
 /* [...] */
}

In the sniff add two regexes for template files and folders check. I took the one from FileNameSniff and modified it slightly (based on the comment by Danny Cooper)

const THEME_EXCEPTIONS_REGEX = '`
		^                    # Anchor to the beginning of the string.
		(?:
							 # Template prefixes which can have exceptions.
			(?:archive|category|content|embed|page|single|tag|taxonomy|template|tag|sidebar|front-page|header|footer|index|comments|search|searchform|404)
			-[^\.]+          # These need to be followed by a dash and some chars.
		)\.(?:php|inc)$      # End in .php (or .inc for the test files) and anchor to the end of the string.
	`Dx';

and for templates (could probably be improved, I'm not a regex expert, but when I test this with regex101 it seems like it makes too much passes)
const THEME_TEMPLATE_FOLDERS_REGEX = '`(?:template-parts/|templates/|partials/)`Dx';

Copy the entire process_token() method, but add two regex checks for the file path and file name at the beginning

$file = $this->strip_quotes( $this->phpcsFile->getFileName() ); // File path that can contain one of the folders from regex.
$fileName = basename( $file ); // File name to check with the first regex.

// If the regex matches skip checking for globals override.
if ( preg_match( self::THEME_EXCEPTIONS_REGEX, $fileName ) === 1 ) {
  return;
}

if ( preg_match( self::THEME_TEMPLATE_FOLDERS_REGEX, $file ) === 1 ) {
  return;
}

Am I on the right track?

@jrfnl Just pinging to check up on this 🙂

Am I on the right track?

@dingo-d Sorry, but no, not really. Might be easier if we discuss this over Slack ? Ping me if you like with a day/time.

I've updated the code after our call @jrfnl
The current sniff overloads the PrefixAllGlobals sniff from WPCS. It looks if the file path contains certain folder names (template-parts, templates and partials). The folders array is set as public property so it can be extended if needed.
Also, the file name is checked against the regex in the FileNameSniff.
The tests are not passing so I'd need some help to see if I'm on the right track here, and what am I doing wrong.
And I've added
<!-- Exclude PrefixAllGlobals Sniff from WPCS and use the one from this ruleset -->
<rule ref="WordPress.NamingConventions.PrefixAllGlobals">
  <severity>0</severity>
</rule>

in the ruleset.xml
Because
<rule ref="WordPress">
  <exclude name="WordPress.NamingConventions.PrefixAllGlobals"/>
</rule>

Would load all sniffs from the WordPress standard, and we don't want that.
I'm not 100% sure this is ok, and if this will silence errors when we don't want them to be silenced in the case of WordPress.NamingConventions.PrefixAllGlobals sniff.

One thing that I kinda realised now is that THEME_EXCEPTIONS_REGEX from the FileNameSniff doesn't check for all the cases mentioned in the comment by Danny Cooper.
Because of that the header.inc file is flagged as a non template file and I get an error in the tests.
I remember you mentioning that this change should be done upstream, but we'd have to wait for this, and for the new version of WPCS, and I'd like to fix this asap so that Theme Sniffer development can continue (we have quite some work to be done there).
Would it be better to define the regex in the sniff here, and once this is fixed upstream, we should just replace it with FileNameSniff::THEME_EXCEPTIONS_REGEX?

I've fixed the issues, the tests should be passing now. If all is ok (I really hope it is 😂), you can squash commits and merge them to avoid the commit clutter 😄

I've fixed the issues, the tests should be passing now. If all is ok (I really hope it is)

Nearly there. Just the question about the PHPCS dependency change + the defaults for the $allowed_folders still being in the sniff remaining.

I think this should be it 🙂

@dingo-d Ok, had yet another critical look. You're so close now.
There were some very minor tidying up things, not worth the up-and-back, so I've just added a new commit to the PR to sort that out.
Now the only thing left is the unit tests.
You have five unit test files - none of which AFAICS will match the regex. so the regex part is untested.
The attachment.inc file says inline OK, template file., but is listed in the getErrorList() method in the group of files to expect an error, while at the same time, it has a comment within that method as if it shouldn't.
For attachment.inc to match the regex would need to be updated in the FileNameSniff.
A filename like page-recent-news.php would already match and could make for a valid test case.
The other three files in the main directory all test the same thing: the fall through, so only one of those would suffice.
Another test case which could be added would be to have a /ThemeTemplatesException/template-parts/subset/my-file-name.inc file - this would test non-template test file names in subdirectories of one of the allowed folders are correctly excluded (which AFAICS they currently are).
If you could have a think about that, I'll have a look at the template hierarchy and see what has changed/been updated since the regex was created and see about updating the regex in WPCS.

Themes aren't supposed to use page template names like page-anything.php. Is the one in the test case supposed to be allowed or we're testing a different thing here?

Themes aren't supposed to use page template names like page-anything.php.

It's an example which literally comes from the theme handbook: https://developer.wordpress.org/themes/basics/template-hierarchy/#single-page - second item in the list.

Is the one in the test case supposed to be allowed or we're testing a different thing here?

Yes, it is supposed to be allowed.

Right, the theme handbook is for themes in general, and not specifically about themes in the repository.
A file like page-xxx.php should be recognized as a template file, but should not be in a theme in the repository.

A file like page-xxx.php should be recognized as a template file, but should not be in a theme in the repository.

In that case, for the purposes of this sniff, I'd say the sniff should be agnostic on whether or the theme would be allowed in the repository.
If it would be so desired that the sniffer would check for a list of allowed template file names and throw warnings for page-xxx.php type template files, that should be in another (new) sniff.
If you think a sniff like that should be added, let's see if there's an open issue for it and if not, open one.

I'll have a look at the template hierarchy and see what has changed/been updated since the regex was created and see about updating the regex in WPCS.

Ok, looking more closely at the regex in WPCS, it only looks for the theme template files which are allowed to break the file name rule of "no underscore", i.e. page-post_type.php and the likes, so adjusting that regex is not really an option.
In other words, we need to solve it here.

@jrfnl I'm happy if you can take this sniff over, it will go a lot quickly than going back and forth with the comments 🙂
I'm puzzled about the comment about the page-xxx.php not being allowed in the theme, and I am failing to see the rationale behind it...

I'm puzzled about the comment about the page-xxx.php not being allowed in the theme, and I am failing to see the rationale behind it...

See https://developer.wordpress.org/themes/template-files-section/page-template-files/#creating-custom-page-templates-for-global-use

This looks good to me, feel free to merge it 👍 Thanks for the help with this, I do appreciate it.

FYI: As discussed with @dingo-d on Slack, I have rebased the PR and squashed all the commits into one commit and added a commit message explaining the change in more detail.
Once the build passes for this new commit, this PR will be merged.


Add dep, delete unused files, update import paths

This change:

adds dep dependency management
updates import paths to use the gradienthealth fork
deletes unused files
adds verbosity to dicomutil

and generally takes stock of the repository and cleans minor things up.

For now I've kept us setup on travis for this, but it's also possible to set up jenkins for public repos which we can do if we want faster builds and consistent build infrastructure in the future.


Announcement: New version with support for CSS files

Hi Everyone,
The newest version of LoadJS (2.1.0) includes support for fetching CSS files:
loadjs(['/path/to/foo.css', '/path/to/bar.js'], {
  success: function() { /* foo.css and bar.js loaded */ },
  fail: function(depsNotFound) { /* foo.css or bar.js didn't load */ }
});

Please try it out and let us know what you think!
Andres
https://github.com/muicss/loadjs
https://www.npmjs.com/package/loadjs

When I tried to load css file in chrome, I got following error.
loadjs.js:104 Uncaught TypeError: Cannot read property 'length' of null
// treat empty stylesheets as failures (to get around lack of onerror
// support in IE
if (e.sheet && !e.sheet.cssRules.length) result = 'e';

without this line, everything is fine.

Interesting, it seems like cssRules can be null under certain conditions. Can you describe how to reproduce the error?

It happens when fetching remote css file. For example,
<!doctype html>

This should be bootstrap style btn-group and it works except error in console.

    <button type="button" class="btn btn-primary">Left</button>
    <button type="button" class="btn btn-danger">Middle</button>
    <button type="button" class="btn btn-success">Right</button>

@monad98 Thanks again for creating this issue. As you pointed out, the problem is that Chrome sets cssRules to null for external stylesheets. Unfortunately, other browsers raise "Permission denied" errors when accessing cssRules so the solution isn't as simple as checking the attribute first.
The root of the problem is that in IE <link> tags don't support onerror callbacks so instead we have to inspect the CSS to detect load failures. After playing around with a few different options I think the best solution is to isolate IE so that code block doesn't get executed by other browsers:
https://github.com/muicss/loadjs/blob/css-bugfix/src/loadjs.js#L104-L114
Let me know what you think about this solution!

It seems a good solution and works fine with Chrome, Safari, Firefox !  👍
Thank you.
When is this new version available as a npm package?

Done! It's available via NPM as v2.1.1:
https://www.npmjs.com/package/loadjs
Let me know if you notice any more problems!

I was about to ask, if the regular expression to check for CSS files could be changed to something like /.css($|\?)/ or /^css:|\.css$/ (allowing for URLs like css:/generated/style/sheet.php) to match files without proper .css extension.
However I could hack around that problem by adding #.css (a dummy fragment identifier) to the stylesheet URL:
loadjs('/generated/style/sheet.php?foo=bar#.css');

I agree - it'd be nice to support css files without a .css suffix. Have you seen the css: prefix used somewhere else? What do you think about using #.cssfor now until we can settle on a more general solution?

A similar project, Toast, uses a [css] prefix. The Webpack CSS loader uses the syntax css-loader!./file.css.
Personally, I thought, that css: looks more "URL like" (like the view-source: pseudo-protocol of Firefox).
For now I'm fine with the #.css hack, since basically all browsers strip it from the requested URL anyway, so it's only visible in the href of the generated <link> if anyone's looking. (Scripts sometimes use the hash in their calling


Add rabbitMQ component tls related description & Set MQTT retain property per request

Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Read the contribution guide
[ ] Commands include options for Linux, MacOS, and Windows within codetabs
[ ] New file and folder names are globally unique
[ ] Page references use shortcodes instead of markdown or URL links
[ ] Images use HTML style and have alternative text
[ ] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description

Add rabbitMQ component tls related configuration docs
Add MQTT per request retain property configuration docs

Issue reference
#2953
https://github.com/dapr/components-contrib/issues/2317

@berndverst Pls take a look

@SpikeWong could you point this PR at the v1.10 branch instead of v1.9? Thanks!

@hhunter-ms if you can edit this PR as a docs maintainer you can change the base branch as well.

@SpikeWong could you point this PR at the v1.10 branch instead of v1.9? Thanks!

@SpikeWong I went ahead and updated to 1.10 - could you resolve the resulting conflicts?

@SpikeWong could you point this PR at the v1.10 branch instead of v1.9? Thanks!

@SpikeWong I went ahead and updated to 1.10 - could you resolve the resulting conflicts?

I have cherry picked my commits

@SpikeWong - There is a link validation error

@SpikeWong - There is a link validation error

I have searched the ci log, have not found where the problem is. Could you point it out? :)

@SpikeWong @msfussell re-ran the tests and it looks like it worked itself out.

There is a link validation error


ADD RADIX SORT

ADD IN SEARCHING_SORTING FOLDER

assign me

I'll like to work on this issue

I would like to work on this issue.
I would like to know that how should I display the output after sorting.

Hey i would like to work on this issue. Can i fork, add code, commit and do a pull request ?

Hello @akshitagupta15june , i would like to work on this issue
Following thing, I would like to add in this repo

[x] Radix sort using python with documentation

Thank you


[BUG] Cython fails to compile the project dwave-samplers

Describe the bug
The project dwave-samplers fails to build with Cython:
------------------------------------------------------------
..

cimport numpy as np
from dimod cimport cyBQM_float64
from dimod.libcpp cimport cppBinaryQuadraticModel

from dwave.samplers.tree.orang cimport samples_type, PyArray_ENABLEFLAGS
^
------------------------------------------------------------

dwave/samplers/tree/sample.pyx:31:0: 'dwave/samplers/tree/orang.pxd' not found

Error compiling Cython file:
------------------------------------------------------------
..

cimport numpy as np
from dimod cimport cyBQM_float64
from dimod.libcpp cimport cppBinaryQuadraticModel

from dwave.samplers.tree.orang cimport samples_type, PyArray_ENABLEFLAGS
^
------------------------------------------------------------

dwave/samplers/tree/sample.pyx:31:0: 'dwave/samplers/tree/orang/samples_type.pxd' not found

Error compiling Cython file:
------------------------------------------------------------
..

cimport numpy as np
from dimod cimport cyBQM_float64
from dimod.libcpp cimport cppBinaryQuadraticModel

from dwave.samplers.tree.orang cimport samples_type, PyArray_ENABLEFLAGS
^
------------------------------------------------------------

dwave/samplers/tree/sample.pyx:31:0: 'dwave/samplers/tree/orang/PyArray_ENABLEFLAGS.pxd' not found

Error compiling Cython file:
------------------------------------------------------------
..
    # pass in pointers so that sample_bqm can fill things in
    cdef double logpf

    # samples
    cdef int srows, scols
    cdef samples_type* samples_pointer
        ^
------------------------------------------------------------

dwave/samplers/tree/sample.pyx:110:9: 'samples_type' is not a type identifier

Error compiling Cython file:
------------------------------------------------------------
..
              &pair_marginals_pointer, &pmrows, &pmcols,
              &pair_pointer, &prows, &pcols)

    # create a numpy array without making a copy then tell numpy it needs to
    # free the memory
    samples = np.asarray(<samples_type[:srows, :scols]> samples_pointer)
                         ^
------------------------------------------------------------

dwave/samplers/tree/sample.pyx:138:26: 'samples_type' is not a type identifier

Error compiling Cython file:
------------------------------------------------------------
..
              &pair_marginals_pointer, &pmrows, &pmcols,
              &pair_pointer, &prows, &pcols)

    # create a numpy array without making a copy then tell numpy it needs to
    # free the memory
    samples = np.asarray(<samples_type[:srows, :scols]> samples_pointer)
                                                       ^
------------------------------------------------------------

dwave/samplers/tree/sample.pyx:138:56: Can only create cython.array from pointer or array

Error compiling Cython file:
------------------------------------------------------------
..
              &pair_pointer, &prows, &pcols)

    # create a numpy array without making a copy then tell numpy it needs to
    # free the memory
    samples = np.asarray(<samples_type[:srows, :scols]> samples_pointer)
    PyArray_ENABLEFLAGS(samples, np.NPY_OWNDATA)
   ^
------------------------------------------------------------

dwave/samplers/tree/sample.pyx:139:4: 'PyArray_ENABLEFLAGS' is not a constant, variable or function identifier

Error compiling Cython file:
------------------------------------------------------------
..
                if samples[i, j] == 0:
                    samples[i, j] = -1

    if marginals:
        variable_marginals = np.asarray(<double[:smlen]> single_marginals_pointer)
        PyArray_ENABLEFLAGS(variable_marginals, np.NPY_OWNDATA)
       ^
------------------------------------------------------------

dwave/samplers/tree/sample.pyx:151:8: 'PyArray_ENABLEFLAGS' is not a constant, variable or function identifier

Error compiling Cython file:
------------------------------------------------------------
..
        variable_marginals = np.asarray(<double[:smlen]> single_marginals_pointer)
        PyArray_ENABLEFLAGS(variable_marginals, np.NPY_OWNDATA)

        if pmrows * pmcols:
            interaction_marginals = np.asarray(<double[:pmrows, :pmcols]> pair_marginals_pointer)
            PyArray_ENABLEFLAGS(interaction_marginals, np.NPY_OWNDATA)
           ^
------------------------------------------------------------

dwave/samplers/tree/sample.pyx:155:12: 'PyArray_ENABLEFLAGS' is not a constant, variable or function identifier

Error compiling Cython file:
------------------------------------------------------------
..
        else:
            interaction_marginals = np.empty(shape=(pmrows, pmcols), dtype=np.double)

        if prows * pcols:
            interactions = np.asarray(<int[:prows, :pcols]> pair_pointer)
            PyArray_ENABLEFLAGS(interactions, np.NPY_OWNDATA)
           ^
------------------------------------------------------------

dwave/samplers/tree/sample.pyx:161:12: 'PyArray_ENABLEFLAGS' is not a constant, variable or function identifier
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "setup.py", line 53, in <module>
    ext_modules=cythonize(
  File "/usr/local/lib/python3.9/site-packages/Cython/Build/Dependencies.py", line 1127, in cythonize
    cythonize_one(*args)
  File "/usr/local/lib/python3.9/site-packages/Cython/Build/Dependencies.py", line 1250, in cythonize_one
    raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: dwave/samplers/tree/sample.pyx
Compiling dwave/samplers/random/cyrandom.pyx because it depends on /usr/local/lib/python3.9/site-packages/dimod/quadratic/cyqm/cyqm_template.pxd.pxi.
Compiling dwave/samplers/tree/sample.pyx because it depends on /usr/local/lib/python3.9/site-packages/dimod/quadratic/cyqm/cyqm_template.pxd.pxi.
Compiling dwave/samplers/tree/solve.pyx because it depends on /usr/local/lib/python3.9/site-packages/dimod/quadratic/cyqm/cyqm_template.pxd.pxi.
Compiling dwave/samplers/tree/utilities.pyx because it depends on /usr/local/lib/python3.9/site-packages/dimod/quadratic/cyqm/cyqm_template.pxd.pxi.
[1/4] Cythonizing dwave/samplers/random/cyrandom.pyx
[2/4] Cythonizing dwave/samplers/tree/sample.pyx
*** Error code 1

Full log (IPv6 URL).
Cython fails to find files that are in the project.
Also this failure occurs on some systems and not on other systems,
Code to reproduce the behaviour:
# example code

Expected behaviour
n/a
Environment
OS: FreeBSD 13.1
Python version 3.9
Cython version 0.29.32
Additional context
No response

Your other report of this https://github.com/dwavesystems/dwave-samplers/issues/32
To be honest I'm not convinced that this is a Cython issue (although I'm not sure it isn't). I'll leave this open because it might be, but I don't think I can be of any help debugging it.

To be honest I'm not convinced that this is a Cython issue [...]

Why? What is the problem then? The files in question do exist in the repository.

Don't know. But it feels like something specific to where FreeBSD puts files when it builds things. I don't have FreeBSD though (and don't really know how to use it) hence I don't think I can really help.
Obviously if you can identify something that Cython is doing wrong here then we'll happily fix it, but for this problem I wouldn't know where to start.

This doesn't happen with any other port using Cython.
And the problem is intermittent.


add demo html and todo compiled bundle

This it PR on this issue - https://github.com/gaearon/redux-devtools/issues/19

What is the build procedure? Can you add a package.json script which would switch to this branch, rebuild and push force?

Maybe this evening, had some work to do.
To build you need to run this in root
cd examples/todomvc && webpack --config webpack.config.js

I don't know how to do switching to branch and push force.

Hah just standard git should work of coarse!

Okay thanks. This helps me so far, I'll add an npm script myself.

@gaearon this should work
git checkout gh-pages && cd examples/todomvc && webpack --config webpack.config.js && cd ../../ && git add . && git commit -m \"rebuild todomvc bundle for demo\" && git push --force


feat: display local weather

Describe the feature you'd like to request
Use location/google account info for home location to display today's weather.
Describe the solution you'd like to see
Display today's forecast alongside an hr by hr display.
STRETCH: see if you can display radar.
Additional information
No response

Weather data: https://weather-gov.github.io/api/general-faqs
open api url: https://api.weather.gov/openapi.json

^ The above api only uses long/lat.
To convert a location to that will need to use:

https://geocoding.geo.census.gov/geocoder/Geocoding_Services_API.html
https://developers.google.com/maps/documentation/geocoding/start

there is data from the api being display.
now have to transform that into a decent display of info.


Add roadmap for project

Add roadmap for project
Signed-off-by: allencloud<EMAIL_ADDRESS>

LGTM


Fix bug - Old testing link on Factories breaks documentation below

Everything after/below this link is missing on the live page. This should fix the issue.

Thank you!


When yml compose files with target port override for LB in v1 version is used to create stack , LB is missing port rules.

Rancher Version: Build form master
Steps to reproduce the problem:
Use the following yml compose files to create stack.
Sangeethas-MacBook-Pro:hostrouting sangeethahariharan1$ cat dc.yml
test678500:
  image: sangeetha/testnewhostrouting:latest
LB-test154262:
  ports:
  - 1008:80
  - 1009:81
  labels:
    io.rancher.loadbalancer.target.test936526: www.abc1.com:1008/service1.html,www.abc1.com:1009/service3.html
    io.rancher.loadbalancer.target.test956454: /service1.html=80,/service3.html=81
    io.rancher.loadbalancer.target.test678500: www.abc1.com
  image: rancher/load-balancer-service
  links:
  - test936526:test936526
  - test956454:test956454
  - test678500:test678500
  - test398531:test398531
test398531:
  image: sangeetha/testnewhostrouting:latest
test936526:
  image: sangeetha/testnewhostrouting:latest
test946778:
  image: sangeetha/testnewhostrouting:latest
test956454:
  image: sangeetha/testnewhostrouting:latest

Sangeethas-MacBook-Pro:hostrouting sangeethahariharan1$ cat  rc.yml
test678500:
  scale: 2
LB-test154262:
  scale: 1
  health_check:
    port: 42
    interval: 2000
    unhealthy_threshold: 3
    healthy_threshold: 2
    response_timeout: 2000
test398531:
  scale: 2
test936526:
  scale: 2
test946778:
  scale: 2
test956454:
  scale: 2
Sangeethas-MacBook-Pro:hostrouting sangeethahariharan1$

Target test956454 has 2 port rules  relating to /service3.html=80 for both ports - 1008 and 1009.
as expected.
Missing  port rules relating relating to  1008 and 1009 for port /service1.html=80

Test with Rancher-compose v0.11.0-rc11

Tested with latest build from master.
Issue is not reproducible anymore. There is no missing port rules.


Security Advisory #GHSA-g6qj-pj38-2465: Address CVE-2024-21634

Addresses https://github.com/TBD54566975/web5-kt/security/advisories/GHSA-g6qj-pj38-2465

This passes FOSSA where it was failing before, newly discovered 3 days ago. Resolves the issue. This forced upgrade to `com.amazonaws:aws-java-sdk-kms:1.12.668` strips out the problematic `software.amazon.ion:ion-java` dependency entirely. TestSuite passes so I assume all is OK?
@jiyoontbd @frankhinek, others, mind an approval and merge here?


Water Jug Problem

Related Issue

Info about the related issue

[x] DevIncept Participant

[x] Contributor

Closes: #16
Describe the changes you've made
The aim was to solve Water Jug Problem using BFS or DFS as per user's choice. The code is running and is working perfectly.
Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Manually run and tested.
Checklist:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added test cases that prove my fix is effective or that my feature works.

Thanks for reviewing, ma'am. You may check the updated files now @prathimacode-hub.


Automated cherry pick of #8771: feature: allow join project across domain

Cherry pick of #8771 on release/3.5.
#8771: feature: allow join project across domain

Codecov Report

Merging #8772 (b892101) into release/3.5 (e3fe6c4) will increase coverage by 1.81%.
The diff coverage is 0.27%.

@@              Coverage Diff               @@
##           release/3.5   #8772      +/-   ##
==============================================
+ Coverage         6.03%   7.84%   +1.81%
==============================================
  Files              795     246     -549
  Lines           124282   33637   -90645
==============================================
- Hits              7503    2640    -4863
+ Misses          116114   30736   -85378
+ Partials           665     261     -404

Flag
Coverage Δ

aFlag
7.84% <0.27%> (+1.81%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/misc.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/domainresource.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/modelbase.go
4.51% <0.00%> (-0.08%)
:arrow_down:

pkg/cloudcommon/db/namevalidator.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/orderby.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/virtualresource.go
0.00% <0.00%> (ø)

pkg/cloudprovider/securitygroup.go
0.00% <ø> (ø)

pkg/compute/regiondrivers/aliyun.go
0.33% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/regiondrivers/base.go
1.03% <0.00%> (-0.04%)
:arrow_down:

... and 499 more

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 848e3af...b892101. Read the comment docs.


fix panic: filter chain should be exited when object is nil

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage

/kind bug
What this PR does / why we need it:
when kube-proxy component list/watch LB service, filter discardcloudservice and nodeportisolation will be selected to create filter chain. if discardcloudservice filter returns a nil object, it will cause panic in nodeportisolation filter.
so we need to exit filter chain if object is nil.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

done in #1984


Replace serde-protobuf and rust-protobuf with prost?

We're using 3 different protobuf crates at the very same time (🤯). Maybe we want to only use prost, as it's supported by:

https://github.com/tikv/grpc-rs
https://github.com/hyperium/tonic, the successor of tower-grpc

Plus, the code generated by prost is more friendly to move semantics.
P.S. PingCAP tried to migrate from rust-protobuf to prost in 2019, but the runtime performance didn't change much (*). However, there are still good reasons to migrate:

Less dependencies (faster build time)
Rust-protobuf generates bloated code that slows down compilation and takes lots of time to optimize (even faster build time)

*: I blame the migration strategy -- we wrapped the prost generated code with a rust-protobuf-like layer, and that's probably slowing down everything.

I believe the dependency can be removed as long as we go through the protobuf decoding thing in connectors. cc @tabVersion may take a look if you have time :)

Do we really use rust-protobuf in gRPC? I think it should be replaced with prost long ago. 🥵

Do we really use rust-protobuf in gRPC? I think it should have been replaced with prost long ago. 🥵

No. The dependency is only introduced in tikv's rust-prometheus (as an optional feature, which we enabled) and risingwave-source. I think we can supersede the usage in risingwave-source.

Probably impossible

There's https://docs.rs/prost-reflect/latest/prost_reflect/index.html, probably someone is working on this.

There's https://docs.rs/prost-reflect/latest/prost_reflect/index.html, probably someone is working on this.

I am looking into this and I will take the issue

So "probably impossible" is probably impossible then


⚠ Samsung has degraded performance

In 351bf9b, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2373 ms

Resolved: Samsung performance has improved in 2e88330.


[bug]  slsa-goreleaser action fails on "Create and sign provenance"

I'm manually running a go-ossf-slsa3-publish.yml action in a private repo by pushing the "Run workflow" button on the actions page.
It fails on the step "Create and sign provenance"
Output from the failure:
>Run set -euo pipefail
provenance generator is slsa-builder-go-linux-amd64
getting entrypoint: getting workflow run: GET https://api.github.com/repos/gorsat/project_root/actions/runs/3011826089: (https://api.github.com/repos/gorsat/idco/actions/runs/3011826089:): 403 Resource not accessible by integration []

The only thing that is even slightly noteworthy about my config is that the file I'm building (yes, it's just one file) is in a subdir of the project root, so I have this in my .slsa-goreleaser.yml:
main: my-file.go
dir: ./my-sub-dir

In addition, I've commented out some of the lines marked "optional" in this file.
But the error message looks like an authorization issue. So I'm wondering if the repo being private has something to do with it.

@gorsat Thanks for submitting the issue! I believe you're right and it is caused by the repo being private. In the Go workflow we aren't requesting the actions: read scope for the step where we are detecting the workflows environment.
https://github.com/slsa-framework/slsa-github-generator/blob/11f701ad156cb8616ed5f5a444f1da6e2b77ed24/.github/workflows/builder_go_slsa3.yml#L78-L79
Unfortunately, We will need to update the workflow and create another release for this to work with private repos.
In the meantime you can give the generic generator starter workflow a try. This one should work as we request the right permissions.
https://github.com/gorsat/reponame/actions/new?category=none&query=slsa

One thing to know: the certificate with your repository name is uploaded to a transparency log for audit purposes. So by using this builder, you are revealing the name of your private repository.
Is that OK with you?
Let's add a disclaimer in the README to make this more explicit.

Thanks for the heads-up. Yes, that's okay for me, but, yeah, a disclaimer would be great, especially for businesses.

OK. So I propose

We amend the documentation
We add a private-repository: true option. At runtime we will check if the repo is private. If it is, we we only proceed if the option is set. Otherwise we will fail.

Wdut?

I like it.


docs(split-view): add JSDoc for manifest

PR Checklist
Please check if your PR fulfills the following requirements:

Tests for the changes have been added: n/a
Docs have been added / updated: n/a
Does this PR introduce a breaking change? N
I have linked any related GitHub issues to be closed when this PR is merged? n/a

Describe the new behavior?
Adding JSDoc comments so the custom elements manifest is sufficient for proxy component generation in forge-angular repo.
Would be nice to have some linting to enforce this, which might be possible using eslint-plugin-jsdoc.  I can open up an issue to track that.

Any objections to changing the label to patch so I can update the forge-angular repo?  I should probably also open an issue there to automate it with a GH workflow or something...

Any objections to changing the label to patch so I can update the forge-angular repo?

There is another change regarding the split-view here that we can merge to publish this release. I say we merge this one as-is, and use that other PR to trigger the release.


Laravel 5 : try catch

Hi
Still feeling my around php and git.  Not sure how to do this via github.
Just wanted to make a small suggestion on the demo php server code.  In App\Http\Middleware\Authenicate in the function handle it might be good to wrap the JWT decode in a
try catch just in case a bad token is passed to ensure json is still returned?
ie
try {
$payload = (array)JWT::decode($token, Config::get('app.token_secret'), array('HS256'));
} catch (\Exception $e) {
return response()->json(['message' => 'Something went wrong with authentication'], 401);
}

Yeah it's a good idea. I skipped it for the sake of an example where I assume other users will use it as intended, but it goes without saying that in production you should always handle potential error cases.
I'd update the code, but I am using $payload = (array)JWT::decode($token, Config::get('app.token_secret'), array('HS256')); throughout many examples in AuthController.php and I don't feel like adding try/catch to every single instance.
Ideally,
$token = explode(' ', $request->header('Authorization'))[1];
 $payload = (array) JWT::decode($token, Config::get('app.token_secret'), array('HS256'));

should be refactored into a function but I am not sure how to have a shared function that I could use inside all controllers in Laravel 5.


Simple 4-key Controls

Alternate to click and drag to rotate.
Simpler for new users

Related to #57

Closed in https://github.com/conix-center/ARENA-core/commit/7d659c0931c31abe1c005e71c1cb955d4a61a909


tree component click

This function solves the problem (这个功能解决的问题)
I've added the node-props property to the tree component and bound a click event, which I want not to fire when I click the collapse icon
Expected API (期望的 API)
No idea

同样的需求

This issue does not have any recent activity. If you are still experiencing similar problems, open a new error, including a minimal copy of the problem