Upgraded to RaspPI3 gps shows disconnected, AHRS works

Stratux version:Stratux v0.8r2
Stratux config:
SDR
[ ] single
[ X] dual
GPS
[ X] yes
[ ] no
type: RY835AI
AHRS
[X ] yes
[ ] no
power source: Anker PowerCore External Battery 20100mAh
usb cable: supplied with Anker
EFB app and version: (e.g., WingX Pro7 8.6.2) WingX Pro 7 (<IP_ADDRESS>)
EFB platform: (e.g., iOS 9.2)
EFB hardware: (e.g., iPad Mini 2) IPAD PRO 9.7 (version 9.3.1)
Description of your issue: Hello, I have upgraded to PI 3 and GPS shows not detected/disconnected. I'll send the logs later today. I did a clean install as well and still the same result, GPS does not acquire a signal when turned on in the settings.
Thanks for your support and development!
If possible, enable "Replay Logs", reproduce the problem, and provide a copy of the logs in http://<IP_ADDRESS>/logs/stratux/ and http://<IP_ADDRESS>/logs/stratux.log.

Known issue (https://github.com/cyoung/stratux/issues/393). Solved with #394.
Fix is included on manual updates since April 20, and involves adding the following line to /boot/config.txt:
dtoverlay=pi3-miniuart-bt
Reboot and the serial connection over GPIO to /dev/ttyAMA0 will be usable.

Awesome, thanks for the fast response AvSquirrel!


Colorscheme doesn't work

Colorscheme doesn't work with my config. It work if I set :set background=light.

Similarly having issues, not entirely sure why - if I revert back to using the v0.1.1 tag I'm not seeing any issues. Happy to help troubleshoot

It work if I set :set background=light

So only the dark variant fails?
Last update I added the light variant, and split the vim colors definitions into two files. I left a dummy file (colors/melange.vim) that would point to the correct variant depending on background.
I'm not entirely sure why it fails tho. It was working on my machine™ . I'll try writing both variants to the same file and see how it goes.

I've got the joy of also moving from linux -> Mac (M1) so there might be some other environmental differences that are causing issues. I've got a free week coming up where I can lend a hand figuring out the issue, I originally assumed it was something Linux/MacOS related but now that I've realized where the issue appears to be I can be more helpful.
(love the color scheme btw)

@spencergilbert,  I made some commits to the dev branch. Could you check it and see if it's working the same as v0.1.1?

(love the color scheme btw)

Thanks! 😄

Just checked and everything looks right to me (MacOS, M1, Alacritty, Neovim), light and dark 👍

Everything seems to be working for me too.
Having both light and dark hightlight definitions in the same file also means that changing background automatically changes the colorscheme, which is a nice plus.


fix(autofill): use static queries to read values used in ngOnInit

@pkozlowski-opensource I think this needs to be rebased

@jelbourn opened a new PR: https://github.com/angular/material2/pull/15574


Some dispersed DUPs missing large deletion component

A subset of dispersed duplication calls actually also have a large deletion at the insertion point, but not all are labelled correctly as ddup_idel.

After some digging on this, I believe this is a result of the method design and not a bug.
Here is an example of the insertion site of a dispersed duplication from the 1KGP reference panel. There is a deletion at the insertion site that is not detected because it is too small (<300 bp) and lacks PE/SR evidence. Our method draws on calls made by PE/SR and depth-only algorithms, so the deletion is detected during GenotypeComplexVariants.

A possible solution would be to flag possible dDUP_iDEL cases based on distance between PE ends at the insertion site. Ends that are sufficiently far apart could be tested for RD support over the separating interval during GenotypeComplexVariants.


[$250] Android - Keyboard doesn't always open on search (reported by @jayeshmangwani)

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open app
Press search from the header
Search input is active but the keyboard is hidden
Note: try 3-4 times issue is inconsistent

Expected Result:
Keyboard should always open
Actual Result:
Sometimes does not open
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers): any
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/178272810-f60e87b8-3a28-41e1-93e3-985b45cd3873.mp4
Expensify/Expensify Issue URL:
Issue reported by: @jayeshmangwani
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1656618123670899
View all open jobs on GitHub

Also applicable to new group, adn new chat page. A proposal should fix all three pages

https://github.com/Expensify/App/blob/ce899227ca6d3823e2865a5e194b429f1263db30/src/pages/SearchPage.js#L179
<OptionsSelector
    shouldDelayFocus={true}     // add this line
    sections={sections}
    value={this.state.searchValue}
    onSelectRow={this.selectReport}

@rushatgabhane Please check this.

🎀 👀 🎀 C+ reviewed
@jeet-dhandha thanks for your proposal, it looks good.
cc: @sketchbook

@rushatgabhane what does "🎀 👀 🎀 C+ reviewed" this mean 😅 ?

that sounds good to me as well, assigning you @jeet-dhandha

@rushatgabhane @sketchydroide How do i sign CLA.md ? As its showing me 404 error when i open it.

That is weird, I'm trying to figure out where it has gone

PATH TO CLA : https://github.com/Expensify/App/blob/main/contributingGuides/CLA.md

thanks, I'll open a GH for us to change the link to the correct one

Okay and can you please check the PR its still not running the Checks.
@sketchydroide

@rushatgabhane @sketchydroide @parasharrajat I have closed the old PR an this the updated PR with Signed Commits and all videos for
Issue: https://github.com/Expensify/App/issues/9827
UPDATED PR: https://github.com/Expensify/App/pull/9936

@jayeshmangwani please apply to the job for reporting. Thanks!

@kevinksullivan I have applied for the job, Thanks

@kevinksullivan I have also accepted the offer, please keep me posted if anything needs to be done on my end.
Thanks, Jeet Dhandha

The solution has been merged, still need to wait another week before the payment.

Paid @jeet-dhandha and @jayeshmangwani . @rushatgabhane send you an invite for C+, please accept!

Should we put shouldDelayKeyboard true for Android platform only ?

Please update me on how will be proceeding with this one.

Waiting for PR fix to deploy to prod.

still waiting for deployment

still seems like it has not been deployed

Same

@rushatgabhane can you let us know if this caused a regression?

Reassigning as I'm OOO for a bit. Thanks @michaelhaxhiu !

This seems ready for payment! I'm going to work on that now.

Don.e


encode the URI before consuming

This PR fixes #14044
if the path is C:\Users\alanren\Documents\New%20folder, it will be parsed as C:\Users\alanren\Documents\New folder in the two places I modified, in order to keep the original value, we have to encode it.

Pull Request Test Coverage Report for Build 566834155

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
8 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.006%) to 43.437%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/api/common/extHostDataProtocol.ts
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/machine-learning/src/common/processService.ts
2
81.48%

src/sql/workbench/api/common/extHostDataProtocol.ts
2
12.72%

extensions/notebook/src/common/ports.ts
4
74.14%

Totals

Change from base Build 565126709:
-0.006%

Covered Lines:
24935

Relevant Lines:
52571

💛  - Coveralls

the ownerURI handling is very confusing, we are doing multiple round of processing of the URI, and I realized there is already a PR out https://github.com/microsoft/azuredatastudio/pull/13503/files
need to think about this more in depth.

Closing this since I'm sending out a PR myself for this


[docs] add custom indexer example to doc page

Description
Linking custom indexer example to doc page
Test plan
manually

Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[ ] JSON-RPC:
[ ] GraphQL:
[ ] CLI:
[ ] Rust SDK:
[ ] REST API:

I think this gives a more realistic Cargo.toml file that project teams can reference. Moving it to the main repo would introduce that Rust workspace related configs that make running the example more difficult

Doesn't this work?
[package]
name = "custom-indexer"
version = "0.1.0"
edition = "2021"

[dependencies]
async-trait = "0.1.81"
tokio = { version = "1.38.0", features = ["full"]}
sui_types = { git = "https://github.com/mystenlabs/sui", package = "sui-types"}
sui_data_ingestion_core = { git = "https://github.com/mystenlabs/sui", package = "sui-data-ingestion-core"}
anyhow = "1.0.86"

[workspace]
# Add an optional note to explain

[[bin]]
name = "custom-indexer"
path = "main.rs"

If it's in its own repo, it'll be forgotten about (esp. if you're not at SF anymore because you started your own company making billions). And if it's in the sui repo, we can test it as part of the ci to make sure it's updated when needed. And we could also import the code into the page if desired instead of forcing the user navigate to the repo.

Yup that worked. I guess I was missing the workspace config

Sweet. With it in there we can add the code to the doc (check the preview from the vercel comment). There's still the link to take the user to the repo, but they can also use the copy code button to never leave the page. I'll wait to get your thoughts before merging.

Not sure how you did the linking magic but it looks good. We can keep both so people have options


Make st2-run-pack-tests command work out of the box on servers with StackStorm installed

More fixes needed to get it to work:

Make sure we run nose with --exe binary so it also runs tests in test files which are executable (packs.download automatically makes all files executable)
Add missing psutil dependency
Various improvements to st2-run-pack-tests script (make sure StackStorm virtualenv is in PYTHONPATH for test run, etc.)

TODO

[ ] Add st2tests for st2-run-pack-tests script

LGTM. But given that I haven't tried this script, is there a sample pack with tests and a sample output of this script that you can post here?

@m4dcoder yeah will do once it's merged and new packages are built.

Here is an example of running this command (latest changes from this PR) on a server with a fresh StackStorm installation:
ubuntu@ip-172-31-11-217:~$ st2-run-pack-tests -p /opt/stackstorm/packs/csv/ -x -j
Running tests for pack: csv
Not activating virtualenv since it doesn't exist
Running tests...
test_run_comma_delimiter (test_action_parse.ParseCSVActionTestCase) ... ok
test_run_pipe_delimiter (test_action_parse.ParseCSVActionTestCase) ... ok

----------------------------------------------------------------------
Ran 2 tests in 0.288s

OK

As you can see in the example above, we can also just use -x flag (don't create virtualenv for pack tests), because pack doesn't depend on any external libraries.
And in case pack depends on external libraries and those external libraries are not available system-wide you need to skip -x flag. This will cause the script to create a virtualenv with all the necessary pack dependencies:
ubuntu@ip-172-31-11-217:~$ st2-run-pack-tests -p /opt/stackstorm/packs/csv/
Running tests for pack: csv
Creating virtualenv in /tmp/st2-pack-tests-virtualenvs/csv...
Using real prefix '/usr'
New python executable in /tmp/st2-pack-tests-virtualenvs/csv/bin/python
Installing setuptools, pip, wheel...done.
Activating virtualenv in /tmp/st2-pack-tests-virtualenvs/csv...
Requirement already up-to-date: pip in /tmp/st2-pack-tests-virtualenvs/csv/lib/python2.7/site-packages
Installing global pack test dependencies...
Running tests...
test_run_comma_delimiter (test_action_parse.ParseCSVActionTestCase) ... ok
test_run_pipe_delimiter (test_action_parse.ParseCSVActionTestCase) ... ok

----------------------------------------------------------------------
Ran 2 tests in 0.280s

OK

And since the pack tests virtualenv now exists you can now use -j flag so on subsequent runs to skip creating and updating of virtualenv (speeds things up, good idea by @dzimine):
ubuntu@ip-172-31-11-217:~$ st2-run-pack-tests -p /opt/stackstorm/packs/csv/ -j
Running tests for pack: csv
Activating virtualenv in /tmp/st2-pack-tests-virtualenvs/csv...
Running tests...
test_run_comma_delimiter (test_action_parse.ParseCSVActionTestCase) ... ok
test_run_pipe_delimiter (test_action_parse.ParseCSVActionTestCase) ... ok

----------------------------------------------------------------------
Ran 2 tests in 0.285s

OK

/cc @dzimine


Retry app store upload (pilot/deliver)

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
The App Store is pretty flaky recently. Submitting from Xcode or using fastlane sometimes just fails for no particular reason. Just retrying usually does the trick.
Is there a way to make the pilot and deliver commands retry once or twice on failure?

Could you share the full output and stack trace when that happens? fastlane should already cover some of those issues.

There's no stack trace. I've been trying to reproduce the error with --verbose, but so far it succeeds every time I used --verbose :/
Here's the full output:
Chimp:appName kluepfel$ fastlane release
[22:21:27]: -------------------------------------------------
[22:21:27]: --- Step: Verifying required fastlane version ---
[22:21:27]: -------------------------------------------------
[22:21:27]: Your fastlane version 1.108.0 matches the minimum requirement of 1.107.0  ✅
[22:21:27]: ------------------------------
[22:21:27]: --- Step: default_platform ---
[22:21:27]: ------------------------------
[22:21:27]: Driving the lane 'ios release' 🚀
[22:21:27]: -----------------
[22:21:27]: --- Step: gym ---
[22:21:27]: -----------------
[22:21:27]: Using legacy build system - waiting for radar to be fixed: https://openradar.appspot.com/radar?id=4952000420642816
[22:21:27]: Successfully loaded '/Users/kluepfel/companyName/appName-iOS/appName/fastlane/Gymfile' 📄
[22:21:27]: No values defined in './fastlane/Gymfile'
[22:21:27]: Installing provisioning profile...
[22:21:27]: Successfully loaded '/Users/kluepfel/companyName/appName-iOS/appName/fastlane/Gymfile' 📄
[22:21:27]: No values defined in './fastlane/Gymfile'
[22:21:27]: $ xcodebuild -list -project ./appName.xcodeproj
[22:21:29]: $ xcodebuild clean -showBuildSettings -scheme appName -project ./appName.xcodeproj

+---------------------------+----------------------------------------------------------------------+
|                                      Summary for gym 1.12.0                                      |
+---------------------------+----------------------------------------------------------------------+
| scheme                    | appName                                                          |
| use_legacy_build_api      | true                                                                 |
| output_directory          | ./build/Production/                                                  |
| project                   | ./appName.xcodeproj                                              |
| provisioning_profile_path | /Users/kluepfel/companyName/appName-iOS/appName/AppStor... |
| destination               | generic/platform=iOS                                                 |
| output_name               | appName                                                          |
| clean                     | false                                                                |
| silent                    | false                                                                |
| buildlog_path             | ~/Library/Logs/gym                                                   |
| xcode_path                | /Applications/Xcode.app                                              |
+---------------------------+----------------------------------------------------------------------+

[22:21:31]: $ set -o pipefail && xcodebuild -scheme appName -project ./appName.xcodeproj -destination 'generic/platform=iOS' -archivePath /Users/kluepfel/Library/Developer/Xcode/Archives/2016-11-14/appName\ 2016-11-14\ 22.21.31.xcarchive archive | tee /Users/kluepfel/Library/Logs/gym/appName-appName.log | xcpretty
[22:21:33]: ▸ Building appName/appName [Distribution]
[22:21:33]: ▸ Check Dependencies
[22:21:37]: ▸ Running script 'Concat Localizable Strings Files'
[22:21:37]: ▸ Copying etc etc etc
[22:21:37]: ▸ Copying etc etc etc

[redacted build steps]

[22:23:11]: ▸ Generating 'appName.app.dSYM'
[22:23:12]: ▸ Touching appName.app
[22:23:12]: ▸ Signing /Users/kluepfel/Library/Developer/Xcode/DerivedData/appName-gncssensmpkouycpyfiycvqtlhhg/Build/Intermediates/ArchiveIntermediates/appName/InstallationBuildProductsLocation/Applications/appName.app
[22:23:21]: ▸ Touching appName.app.dSYM
[22:23:22]: ▸ Archive Succeeded
[22:23:22]: $ /usr/bin/xcrun /tmp/PackageApplication4Gym -v /Users/kluepfel/Library/Developer/Xcode/Archives/2016-11-14/appName\ 2016-11-14\ 22.21.31.xcarchive/Products/Applications/appName.app -o '/var/folders/6y/3w681xkn2hd1m1mbjw56zhjr0000gn/T/gym_output20161114-69081-1p1fo3w/appName.ipa' exportFormat ipa --embed '/Users/kluepfel/companyName/appName-iOS/appName/AppStore_de.companyName.appName.mobileprovision'
[22:23:42]: $ zip --recurse-paths '/var/folders/6y/3w681xkn2hd1m1mbjw56zhjr0000gn/T/gym_output20161114-69081-1p1fo3w/appName.ipa' SwiftSupport > /dev/null
[22:23:43]: Compressing 1 dSYM(s)
[22:23:43]: $ cd '/Users/kluepfel/Library/Developer/Xcode/Archives/2016-11-14/appName 2016-11-14 22.21.31.xcarchive/dSYMs' && zip -r '/Users/kluepfel/companyName/appName-iOS/appName/build/Production/appName.app.dSYM.zip' *.dSYM
[22:23:44]: ▸ updating: appName.app.dSYM/ (stored 0%)
[22:23:44]: ▸ updating: appName.app.dSYM/Contents/ (stored 0%)
[22:23:44]: ▸ updating: appName.app.dSYM/Contents/Info.plist (deflated 51%)
[22:23:44]: ▸ updating: appName.app.dSYM/Contents/Resources/ (stored 0%)
[22:23:44]: ▸ updating: appName.app.dSYM/Contents/Resources/DWARF/ (stored 0%)
[22:23:44]: ▸ updating: appName.app.dSYM/Contents/Resources/DWARF/appName (deflated 68%)

[22:23:44]: Successfully exported and compressed dSYM file
[22:23:44]: Successfully exported and signed the ipa file:
[22:23:44]: /Users/kluepfel/companyName/appName-iOS/appName/build/Production/appName.ipa
[22:23:44]: ------------------
[22:23:44]: --- Step: cert ---
[22:23:44]: ------------------

+---------------+-----------------------------------------------------+
|                       Summary for cert 1.4.4                        |
+---------------+-----------------------------------------------------+
| development   | false                                               |
| force         | false                                               |
| username      | [appleID]                              |
| team_id       | ABCD123456                                          |
| keychain_path | /Users/kluepfel/Library/Keychains/login.keychain-db |
+---------------+-----------------------------------------------------+

[22:23:44]: Starting login with user '[appleID]'
[22:23:47]: Successfully logged in
[22:23:49]: Found the certificate ABCD123456 (companyName) which is installed on the local machine. Using this one.
[22:23:50]: Verifying the certificate is properly installed locally...
[22:23:50]: Successfully installed certificate ABCD123456
[22:23:50]: Use signing certificate 'ABCD123456' from now on!
[22:23:50]: ------------------
[22:23:50]: --- Step: sigh ---
[22:23:50]: ------------------

+-------------------------------------+------------------------------+
|                      Summary for sigh 1.11.2                       |
+-------------------------------------+------------------------------+
| adhoc                               | false                        |
| development                         | false                        |
| skip_install                        | false                        |
| force                               | false                        |
| app_identifier                      | de.companyName.appName |
| username                            | [appleID]       |
| team_id                             | ABCD123456                   |
| ignore_profiles_with_different_name | false                        |
| cert_id                             | ABCD123456                   |
| skip_fetch_profiles                 | false                        |
| skip_certificate_verification       | false                        |
+-------------------------------------+------------------------------+

[22:23:50]: Starting login with user '[appleID]'
[22:23:52]: Successfully logged in
[22:23:52]: Fetching profiles...
[22:24:02]: Found 2 matching profile(s)
[22:24:02]: Downloading provisioning profile...
[22:24:05]: Successfully downloaded provisioning profile...
[22:24:05]: Installing provisioning profile...
/Users/kluepfel/companyName/appName-iOS/appName/AppStore_de.companyName.appName.mobileprovision
[22:24:05]: Setting Provisioning Profile type to 'app-store'
[22:24:05]: --------------------
[22:24:05]: --- Step: resign ---
[22:24:05]: --------------------
<EMAIL_ADDRESS>/Users/kluepfel/companyName/appName-iOS/appName/build/Production/appName.ipa C5B8CF4BDD1D66ADB30C529E68CA197C996D9543 -p /Users/kluepfel/companyName/appName-iOS/appName/AppStore_de.companyName.appName.mobileprovision         /Users/kluepfel/companyName/appName-iOS/appName/build/Production/appName.ipa
security: SecPolicySetValue: One or more parameters passed to a function were not valid.
security: SecPolicySetValue: One or more parameters passed to a function were not valid.
security: SecPolicySetValue: One or more parameters passed to a function were not valid.
_floatsignTemp/Payload/appName.app: replacing existing signature
rm: _floatsignTemp/old-embedded-profile.plist: No such file or directory

[22:24:26]: Successfully signed /Users/kluepfel/companyName/appName-iOS/appName/build/Production/appName.ipa!
[22:24:26]: Successfully re-signed .ipa 🔏.
[22:24:26]: ---------------------
[22:24:26]: --- Step: deliver ---
[22:24:26]: ---------------------
[22:24:26]: Successfully loaded '/Users/kluepfel/companyName/appName-iOS/appName/fastlane/Deliverfile' 📄
[22:24:26]: No values defined in './fastlane/Deliverfile'
[22:24:26]: Login to iTunes Connect ([appleID])
[22:24:28]: Login successful

+-----------------------+--------------------------------------------------------------------------+
|                                      deliver 1.15.0 Summary                                      |
+-----------------------+--------------------------------------------------------------------------+
| force                 | true                                                                     |
| submit_for_review     | false                                                                    |
| name.default          | appName                                                              |
| name.de-DE            | appName                                                              |
| ipa                   | /Users/kluepfel/companyName/appName-iOS/appName/build/Produ... |
| screenshots_path      | ./fastlane/screenshots                                                   |
| metadata_path         | ./fastlane/metadata                                                      |
| app_version           | 4.27                                                                     |
| username              | [appleID]                                                   |
| app_identifier        | de.companyName.appName                                             |
| skip_binary_upload    | false                                                                    |
| skip_screenshots      | false                                                                    |
| skip_metadata         | false                                                                    |
| automatic_release     | false                                                                    |
| dev_portal_team_id    | ABCD123456                                                               |
| overwrite_screenshots | false                                                                    |
+-----------------------+--------------------------------------------------------------------------+

[22:24:30]: Making sure the latest version on iTunes Connect matches '4.27' from the ipa file...
[22:24:32]: '4.27' is the latest version on iTunes Connect
[22:24:32]: Loading './fastlane/metadata/de-DE/description.txt'...
[22:24:32]: Loading './fastlane/metadata/de-DE/keywords.txt'...
[22:24:32]: Loading './fastlane/metadata/de-DE/release_notes.txt'...
[22:24:32]: Loading './fastlane/metadata/de-DE/support_url.txt'...
[22:24:32]: Loading './fastlane/metadata/de-DE/marketing_url.txt'...
[22:24:32]: Loading './fastlane/metadata/de-DE/privacy_url.txt'...
[22:24:32]: Loading './fastlane/metadata/en-US/description.txt'...
[22:24:32]: Loading './fastlane/metadata/en-US/keywords.txt'...
[22:24:32]: Loading './fastlane/metadata/en-US/release_notes.txt'...
[22:24:32]: Loading './fastlane/metadata/en-US/support_url.txt'...
[22:24:32]: Loading './fastlane/metadata/en-US/marketing_url.txt'...
[22:24:32]: Loading './fastlane/metadata/en-US/privacy_url.txt'...
[22:24:32]: Loading './fastlane/metadata/copyright.txt'...
[22:24:32]: Loading './fastlane/metadata/primary_category.txt'...
[22:24:32]: Loading './fastlane/metadata/secondary_category.txt'...
[22:24:32]: Loading './fastlane/metadata/primary_first_sub_category.txt'...
[22:24:32]: Loading './fastlane/metadata/primary_second_sub_category.txt'...
[22:24:32]: Loading './fastlane/metadata/secondary_first_sub_category.txt'...
[22:24:32]: Loading './fastlane/metadata/secondary_second_sub_category.txt'...
[22:24:32]: Detected languages: ["de-DE", "en-US", "default"]
[22:24:33]: Activating languages de-DE, en-US...
[22:24:43]: Uploading metadata to iTunes Connect
[22:24:47]: Successfully uploaded initial set of metadata to iTunes Connect
[22:24:48]: Starting with the upload of screenshots...
[22:24:48]: Activating languages de-DE, en-US...
[22:24:53]: Uploading 10 screenshots for language de-DE
[22:24:53]: Uploading './fastlane/screenshots/de-DE/1_ipadPro_1.ScreenshotBanner-iPadPro-DE.png'...
[22:25:32]: Uploading './fastlane/screenshots/de-DE/1_iphone6Plus_1.ScreenshotBanner-iPhone6Plus-DE.png'...
[22:25:54]: Uploading './fastlane/screenshots/de-DE/2_ipadPro_2.CAR 4.20 Main Screen vertical iPad Pro DE.png'...
[22:26:35]: Uploading './fastlane/screenshots/de-DE/2_iphone6Plus_2.pr_source.png'...
[22:26:58]: Uploading './fastlane/screenshots/de-DE/3_ipadPro_3.CAR 4.20.Tally horizontal iPad Pro DE.png'...
[22:27:37]: Uploading './fastlane/screenshots/de-DE/3_iphone6Plus_3.pr_source.png'...
[22:27:58]: Uploading './fastlane/screenshots/de-DE/4_ipadPro_4.CAR 4.20 Solitaire Portrait iPad Pro DE.png'...
[22:28:36]: Uploading './fastlane/screenshots/de-DE/4_iphone6Plus_4.pr_source.png'...
[22:28:53]: Uploading './fastlane/screenshots/de-DE/5_ipadPro_5.CAR 4.20 Final Scores horizontal iPad Pro DE.png'...
[22:29:34]: Uploading './fastlane/screenshots/de-DE/5_iphone6Plus_5.pr_source.png'...
[22:29:53]: Saving changes
[22:30:00]: Uploading 10 screenshots for language en-US
[22:30:00]: Uploading './fastlane/screenshots/en-US/1_ipadPro_1.ScreenshotBanner-iPadPro-EN.png'...
[22:30:39]: Uploading './fastlane/screenshots/en-US/1_iphone6Plus_1.ScreenshotBanner-iPhone6Plus-EN.png'...
[22:31:04]: Uploading './fastlane/screenshots/en-US/2_ipadPro_2.CAR 4.20 Main Screen vertical iPad Pro EN.png'...
[22:31:46]: Uploading './fastlane/screenshots/en-US/2_iphone6Plus_2.pr_source.png'...
[22:32:08]: Uploading './fastlane/screenshots/en-US/3_ipadPro_3.CAR 4.20.Tally horizontal iPad Pro EN.png'...
[22:32:45]: Uploading './fastlane/screenshots/en-US/3_iphone6Plus_3.pr_source.png'...
[22:33:06]: Uploading './fastlane/screenshots/en-US/4_ipadPro_4.CAR 4.20 Solitaire Portrait iPad Pro EN.png'...
[22:33:42]: Uploading './fastlane/screenshots/en-US/4_iphone6Plus_4.pr_source.png'...
[22:33:59]: Uploading './fastlane/screenshots/en-US/5_ipadPro_5.CAR 4.20 Final Scores horizontal iPad Pro EN.png'...
[22:39:01]: Uploading './fastlane/screenshots/en-US/5_iphone6Plus_5.pr_source.png'...
[22:39:19]: Saving changes
[22:39:36]: Successfully uploaded screenshots to iTunes Connect
[22:39:41]: Uploading binary to iTunes Connect
[22:39:43]: Going to upload updated app to iTunes Connect
[22:39:43]: This might take a few minutes. Please don't interrupt the script.
[22:43:39]: Transporter transfer failed.
[22:43:39]:
[22:43:39]:
[22:43:39]: Return status of iTunes Transporter was 1:
The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.
[22:43:39]: Variable Dump:
[22:43:39]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios release", :IPA_OUTPUT_PATH=>"/Users/kluepfel/companyName/appName-iOS/appName/build/Production/appName.ipa", :DSYM_OUTPUT_PATH=>"/Users/kluepfel/companyName/appName-iOS/appName/build/Production/appName.app.dSYM.zip", :XCODEBUILD_ARCHIVE=>"/Users/kluepfel/Library/Developer/Xcode/Archives/2016-11-14/appName 2016-11-14 22.21.31.xcarchive", :CERT_FILE_PATH=>"/Users/kluepfel/companyName/appName-iOS/appName/ABCD123456.cer", :CERT_CERTIFICATE_ID=>"ABCD123456", :SIGH_PROFILE_PATH=>"/Users/kluepfel/companyName/appName-iOS/appName/AppStore_de.companyName.appName.mobileprovision", :SIGH_PROFILE_PATHS=>["/Users/kluepfel/companyName/appName-iOS/appName/AppStore_de.companyName.appName.mobileprovision"], :SIGH_UDID=>"76167820-ad5c-4e0c-a08f-13666744caff", :SIGH_PROFILE_TYPE=>"app-store"}
[22:43:39]: Could not upload binary to iTunes Connect. Check out the error above

+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | Verifying required fastlane version | 0           |
| 2    | default_platform                    | 0           |
| 3    | gym                                 | 136         |
| 4    | cert                                | 6           |
| 5    | sigh                                | 14          |
| 6    | resign                              | 21          |
| 💥    | deliver                             | 1153        |
+------+-------------------------------------+-------------+

[22:43:39]: fastlane finished with errors

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

➡  Issues with deliver, can't upload binary / IPA
   https://github.com/fastlane/fastlane/issues/6151 [open] 27 💬
   4 weeks ago

➡  Binary upload invalid / [!] {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["ITC.response.error.OPERATION_FAILED"], "info"=>nil}, "statusCode"=>"ERROR"}
   https://github.com/fastlane/fastlane/issues/6419 [open] 54 💬
   5 days ago

➡  Could not upload binary to iTunes Connect
   https://github.com/fastlane/fastlane/issues/4339 [closed] 19 💬
   6 weeks ago

and 36 more at: https://github.com/fastlane/fastlane/search?q=Could%20not%20upload%20binary%20to%20iTunes%20Connect.%20Check%20out%20the%20error%20above&type=Issues&utf8=✓

[!] Could not upload binary to iTunes Connect. Check out the error above

Basically what I'm looking for is a way to check "did the last action succeed?", and an way to perform an action depending on that. Something like
bool success = pilot
if (!success) do
    success = pilot #retry 1st time
end
if (!success) do
    pilot #retry 2nd time
end
#give up if still no success

see PR: https://github.com/fastlane/fastlane/pull/7012

as the PR got closed, you should better do it like this: (should work for pilot & deliver)

$deliver_retry=0
$pilot_retry=0

lane :do_pilot do
      pilot
      rescue => ex
           $pilot_retry +=1
           if $pilot_retry <= 3
                do_pilot
          end
     end
end

lane :do_deliver do
      deliver
      rescue => ex
           $deliver_retry +=1
           if $deliver_retry <= 3
                do_deliver
          end
     end
end

untested/unofficial - but  hopefully this works for you.
for sure this one will retry 3 times if there is a error with the binary - like  "ITMS-XXX"

Great, thanks! I'll give it a try and let you know how it goes.

It's missing a begin, otherwise it works fine. Thanks!
$deliver_retry=0
$pilot_retry=0

lane :do_pilot do
      begin
          pilot
      rescue => ex
           $pilot_retry +=1
           if $pilot_retry <= 3
                do_pilot
          else
              raise ex
          end
     end
end

lane :do_deliver do
    begin
        deliver
    rescue => ex
         $deliver_retry +=1
         if $deliver_retry <= 3
              do_deliver
        else
              raise ex
        end
    end
end

@kluepfel thx for feedback ;) - and glad you got it working! closed/resolved issues are the best issues 👏


Safari Crash Issue

This line of code causes Safari to crash when rendering (at line 563 in the build):
text_align = text_align.replace(["-webkit-auto"],["auto"]);
I also tried removing the strings from the arrays, still crashes. I took out the line of code on my copy and it works.
See my comment here:
https://github.com/niklasvh/html2canvas/commit/61f71c1839ebcfcacb6f435b13869cb633eb0f26#L24L34

Unable to replicate this on 5.1.2, is it happening on all pages?


Python snippets are obsolete

Wheh you are using Python snippets, it is using obsolete functions for click, getText, etc.

For example this case:

Clicking on the button highlighted with red arrow, it is generating the following code:
find_element_by_xpath("//div[@class='column']//img[1]").click();
Latest version of Selenium for Python using this code instead of previous:
find_element(By.XPATH,"//div[@class='column']//img[1]").click()
PLEASE NOTE: in Python language, semicolon at the end of line is also unnecessary! Please, remove it as well to keep the syntax correct.
Thank you in advnace.
Awaiting for update.

Thanks for the update, I'll update the snippets.

I have updated the extension, which should be live in the store within a week.


[SPARK-37018][SQL] Spark SQL should support create function with Aggregator

What changes were proposed in this pull request?
Spark SQL not supports to create function of Aggregator yet and deprecated UserDefinedAggregateFunction.
If we want remove UserDefinedAggregateFunction, Spark SQL should provide a new option.
Why are the changes needed?
We need to provide a new way to create user defined aggregate function so as remove UserDefinedAggregateFunction in future.
Does this PR introduce any user-facing change?
Yes. Users will create user defined aggregate function by implement Aggregator.
How was this patch tested?
New tests.

Test build #144330 has started for PR 34303 at commit 3702b9b.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48809/

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

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48824/

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

retest this please

Test build #144366 has started for PR 34303 at commit 136b8f5.

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

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

Test build #144393 has started for PR 34303 at commit 815c65c.

Test build #144393 has finished for PR 34303 at commit 815c65c.

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


edit config to allow setting lc field value vie API & keep sandbox config in separate file

I added field localcontexts.uriSpace to the lchub url, which is required, in order to set the field (LCProjectUrl) via the API, when allow-free-text is set to false.
Also created a separate config file for the sandbox configuration.

super, thanks @qqmyers . I will give it a try. Despite some more testing and later changes, do you think we can already use the metadatablock and cvoc in production? The LICCI datasets we have should link to one project on the LCHub.

re: production use - we've talked about other ways of getting the LC project id, but what is stored in Dataverse is the same as it is now, so I don't see a reason to delay in cases where curators/responsible users are making the project selection.


scripts/tikv: Fix TiKV's board can't show some GC metrics from PD

Some of the metrics about GC in TiKV's board actually comes from TiDB. However there is {job=~"$job"} filter on them, where the $job evaluates to be tikv_[0-9]+. Then TiDB was filtered out.
This PR tries to fix it by removing this filter from these query expressions.

@overvenus @LinuxGit  PTAL


microflow nameing conventions

microflow naming conventions changed in Mendix 9,
e.g. before commit now BCO_ shall be used, in Mendix 8 BCo_
I come for case sensitive coding (C/C++), so for me this is a rather big change. Personally I liked previous convention better.
(All capital letters direct me towards constants.)

Hi @wobweger thanks for the feedback. This is a rather big change for microflow names, but the goal is to align with what we are teaching developers in Academy as well. This is a best practice we have standardized in Mendix, but of course it can be adapted to your requirements.
Best,
Adam


DNS - Find Dangling DNS Records Error on run "Assembly with same name is already loaded"

Describe the bug
The "DNS - Find Dangling DNS Records" script fails on first time run to scan subscriptions and produce a list of dangling CNAMEs. Script will run successfully in locally from my own machine.
Reproduce
Right after installing, importing, and then running the module as follows:
Get-DanglingDnsRecords -FetchDnsRecordsFromAzureSubscription
I see some progress and it seems to finish fetching subscriptions then begin processing subscriptions & DnsZones/DnsRecordSets
Before the command errors out with the following error message:
Import-Module:                                                                                Line |   13 |  …                       Import-Module -name $module -Scope Local -Force      |                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~      | Assembly with same name is already loaded
Expected behavior
Expected script to finish & produce report
Screenshots

Environment- if applicable

Using the Cloud Shell within Azure
New Cloud Shell being created/tested
Installed latest version of module as of today

Desktop (please complete the following information if applicable):
N/A - Cloud Shell

Just to add that I have had the same issue when trying to run this today

Also adding that the issue is still there

Also it breaks my cloud shell until I restart it.

Does this happen only in the cloud shell?

@drknite72 Did you experience this when not using Cloud shell?

Have not tried in out of cloud shell. Just came back to the tool to see if it had been fixed and was going to try it locally in PS

Update it seems to run just fine locally, the problem still happens when running it from cloud shell

Found a workaround - Deleting the Az.Accounts module imported by this tool seems to let the tool run.
rm -rf /home/<user>/.local/share/powershell/Modules

Closing this issue because a work around exist. Feedback received


Knowledge -Anthropic/Voyage provider -  Ingesting  files from website fails with - "failed to clean website content: failed to LLM-clean markdown: " error

Steps to reproduce the problem:

Configure Anthropic model provider.
Configure Voyage model provider.
Set default model aliases as follows:

Create an agent with knowledge files from website.
Once syncing is done, ingest all files.

Notice that ingesting files fails with following errors
`failed to clean website content: failed to LLM-clean markdown: failed to unmarshal response: invalid character 'd' looking for beginning of value`

The same issue is also seen when testing with  Anthropic on AWS Bedrock provider as well.
Tested with following default  models


Dynamic import not working as expected with base public path option.

Describe the bug
I'm working on a project where we will be building a library to be hosted on a CDN.  Currently, I'm struggling with an issue where dynamic imports are not working as expected with the base public path option.
What I'm expecting to happen is that when this option is set in my config: (E.g.: base: www.somepath.com), all dynamic imports should also have this path appended to them after being built - import('./dynamic.js'); would be come import('www.somepath.com/dynamic.js');
However, this does not seem to currently be the case and the dynamic imports are still using relative paths.  If this is not a bug, and I'm misusing this option and/or is there an alternative approach that I should be taking?
Reproduction
https://stackblitz.com/edit/vitejs-vite-bdc46m?file=dist%2Fmain.js
Steps to reproduce

Run npm run build
Open main.js in the dist folder.
Observe that the import("./dynamic-HASH.js"); does not contain the base path specified in vite.config.ts

System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vite: ^5.4.2 => 5.4.2

### Used Package Manager

npm

### Logs

_No response_

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitejs/vite/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitejs/vite/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitejs.dev/guide).
- [X] Check that there isn't [already an issue](https://github.com/vitejs/vite/issues) that reports the same bug to avoid creating a duplicate.
- [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to [vuejs/core](https://github.com/vuejs/core) instead.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitejs/vite/discussions) or join our [Discord Chat Server](https://chat.vitejs.dev/).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

import("./dynamic-HASH.js"); is relative to the file containing that statement. As long as you are serving the file importing the other file and the imported file on the same origin, it won't be an issue.

The problem is the imported file is not on the same origin.
For example, I am hosting my library at www.someWebsite.com/main.js, and the imported file is at www.someWebsite.com/dynamic-HASH.js.
If the library is consumed via www.anotherWebsite.com, this is a different origin, so the import("./dynamic-HASH.js"); would fail, as it would try to grab it from www.anotherWebsite.com/dynamic-HASH.js.

Do you have the file importing dynamic-HASH.js on a different origin from dynamic-HASH.js? For example, www.someWebsite.com/main.js imports www.anotherWebsite.com/dynamic-HASH.js.
In that case, you should make dynamic-HASH.js an entry point instead of a implicit chunk generated by dynamic import, otherwise the entry signature can be changed by rollup (some export might be removed if main.js doesn't use it).
If you have main.js and dynamic-HASH.js served on the same origin and importing main.js from a different origin, then import can work with relative path. It will be resolved from main.js and not the location.href/document.baseURI.

If you have main.js and dynamic-HASH.js served on the same origin and importing main.js from a different origin, then import can work with relative path. It will be resolved from main.js and not the location.href/document.baseURI.

Interesting, you are correct, I tested this and this does seem to be the case.  I vaguely remember I had problems with webpack around a similar issue (maybe it handles dynamic imports differently?), so that might be why I assumed the latter to be true.
Thanks for the help/clarification!


gt-filter not working correctly with gt_alt_freqs

Hi,
From what I noticed, there is an issue when we are trying to filter using a wildcard_rule containing a . for instance:
(gt_alt_freqs).(*).(>=0.25).(any)
will lead to
"Wildcard filter should consist of 4 elements. Exiting."
It appears that you check for the correct number of tokens by splitting directly on the ., you could just check by splitting on ).( instead.
Thanks a lot,
Freddy

See my answer : https://github.com/arq5x/gemini/issues/925#issuecomment-518772797


Ignore single Json record if size is larger than 256KB which is size limit for eventhub

Tolerance is chosen to be 95% so the internal size limit will be (256K * 0.95)

Test failed in gobblin-cluster module which is not related to this commit.


Add --scale, --position-x-offset, --position-y-offset and --rotation-offset

This addresses #4135 and #4345 by enabling additional transformations to frame the image within the window boundaries. It also applies the transformations on input control signals. Recording is not supported.

Thank you for your contribution :+1:
This feature is indeed often requested for the Meta Quest 3.

I had some compilation issues, that I fixed by replacing float32_t by float and by adding the math library as a dependency:
sed -i 's/float32_t/float/g' app/src/screen.c

diff --git a/app/meson.build b/app/meson.build
index 88e2df9aa..d6f403dbe 100644
--- a/app/meson.build
+++ b/app/meson.build
@@ -99,6 +99,7 @@ endif
 cc = meson.get_compiler('c')

 dependencies = [
+    cc.find_library('m'),
     dependency('libavformat', version: '>= 57.33'),
     dependency('libavcodec', version: '>= 57.37'),
     dependency('libavutil'),

Congrats, the input location seems to work correctly :tada:
I did not really review yet (it may take time, I have other changes to review/implement beforehand).
But I have some general remarks. A priori, I am a bit worried by the (intrinsic) complexity added for supporting any rotation/scale for the rendering. This means that every future change will have to deal with this, and may not assume a landcape/portrait view anymore.
I think that in practice, the Meta Quest 3 is the only use case. Also, this has to be used in conjonction with --crop, and since Android 14 capture cropping is broken (#4011). But anyway.
Semantically, maybe --rotation-offset could be merged with --rotation. One problem is that the window size currently does not depend on the rotation offset. (Should it expand to view the whole content? I don't know.)

As an alternative, I think it should be possible to filter the input directly on the device: IIRC we should be able to capture the screen and filter it via an OpenGL ES shader, and provide the result as input for the encoder.
There would be several benefits:

it would impact recording
it would provide an alternative for cropping (broken since Android 14)
it would be less invasive

I did look into a server-side implementation, but the client offered the path of least resistance. The company I work for was interested in casting the Quest 3 for public events, and this implementation got us there without too much effort. In the case of the Quest 3, It turned out to be useful to keep window size independent from rotation and scale so the image could be framed without black corners.
Regarding --crop, it can technically be used without it by scaling up and moving the image around with position offsets, but it is always a waste of bandwidth. If possible, a server-side solution would be better in the long run.

I did look into a server-side implementation, but the client offered the path of least resistance. The company I work for was interested in casting the Quest 3 for public events, and this implementation got us there without too much effort. In the case of the Quest 3, It turned out to be useful to keep window size independent from rotation and scale so the image could be framed without black corners.
Regarding --crop, it can technically be used without it by scaling up and moving the image around with position offsets, but it is always a waste of bandwidth. If possible, a server-side solution would be better in the long run.

I built it successfully and it works well. But how to rotate and then crop instead of cropping and then rotate like now?

I built it successfully and it works well. But how to rotate and then crop instead of cropping and then rotate like now?
Unfortunately, at the moment, cropping will always happen first since it is done on the device. The only alternative is to be more generous with the initial cropping and then frame the image by playing with --scale, --position-x-offset and --position-y-offset.

When is this coming to the mainbranch and release?

When is this coming to the mainbranch and release?
Because the applicability is low, I think it won't make it to the main branch. If scrcpy has a plugin mechanism like yt-dlp it would be better

@willykc : Do you have a solution that can control the Quest screen? I can only control via display ID (main Quest windows such as horizon feed, settings, windows store...) and cannot control via the main screen or in the app

Unfortunately no, I haven't looked at controlling the Quest externally.

I did look into a server-side implementation, but the client offered the path of least resistance. The company I work for was interested in casting the Quest 3 for public events, and this implementation got us there without too much effort. In the case of the Quest 3, It turned out to be useful to keep window size independent from rotation and scale so the image could be framed without black corners.
Regarding --crop, it can technically be used without it by scaling up and moving the image around with position offsets, but it is always a waste of bandwidth. If possible, a server-side solution would be better in the long run.

Can you post the last scrcpy command for casting to the pc with the rotatiom and cropping...etc, that you use for the quest 3?

Can you post the last scrcpy command for casting to the pc with the rotatiom and cropping...etc, that you use for the quest 3?

This worked well for me on a 16:9 display in fullscreen mode:
scrcpy --crop=2744:1544:20:350 --rotation-offset=22 --scale=159 --position-x-offset=-520 --position-y-offset=-490 --video-bit-rate=16M -f
I think cropping could be more aggressive though. It can still be optimized.

This worked well for me on a 16:9 display in fullscreen mode:
Hi! I'm develope special software for Meta Quest's headsets and scrcpy included to it. Where i can find this modified version scrcpy, with support rotation for Quest 3?

As an alternative, I think it should be possible to filter the video directly on the device

Refs https://github.com/Genymobile/scrcpy/issues/4011#issuecomment-1969174671 for information about implementing a server-side filter.

This worked well for me on a 16:9 display in fullscreen mode:

Hi! I'm develope special software for Meta Quest's headsets and scrcpy included to it. Where i can find this modified version scrcpy, with support rotation for Quest 3?

Just build from @willykc source. This is my build if you need https://github.com/vuisme/escrcpy/tree/main/electron/resources/extra/win/scrcpy

This is my build if you need

Thank you so much!

When is this coming to the mainbranch and release?
Because the applicability is low, I think it won't make it to the main branch. If scrcpy has a plugin mechanism like yt-dlp it would be better

What? This must come to the mainbranch. i really wonder what sidequest ist doing without that. sorry but quest 3 is sold out!

This worked well for me on a 16:9 display in fullscreen mode:

Hi! I'm develope special software for Meta Quest's headsets and scrcpy included to it. Where i can find this modified version scrcpy, with support rotation for Quest 3?

Just build from @willykc source. This is my build if you need https://github.com/vuisme/escrcpy/tree/main/electron/resources/extra/win/scrcpy

Absolute Hero. Thanks für the Build. Will test it right away.

This worked well for me on a 16:9 display in fullscreen mode:

Hi! I'm develope special software for Meta Quest's headsets and scrcpy included to it. Where i can find this modified version scrcpy, with support rotation for Quest 3?

Just build from @willykc source. This is my build if you need https://github.com/vuisme/escrcpy/tree/main/electron/resources/extra/win/scrcpy

Great work! Can I borrow your modified scrcpy to include it in my app which specially made for Meta Quest mirroring?

This worked well for me on a 16:9 display in fullscreen mode:

Hi! I'm develope special software for Meta Quest's headsets and scrcpy included to it. Where i can find this modified version scrcpy, with support rotation for Quest 3?

Just build from @willykc source. This is my build if you need https://github.com/vuisme/escrcpy/tree/main/electron/resources/extra/win/scrcpy

Good work. However, when using -- record, there may be some issues where the recorded video is not rotated or cropped.
Is there any way?

Unfortunately recording is not supported by this approach. Implementing the rotation on the device as discussed previously would address that limitation though.

Can you post the last scrcpy command for casting to the pc with the rotatiom and cropping...etc, that you use for the quest 3?

This worked well for me on a 16:9 display in fullscreen mode: scrcpy --crop=2744:1544:20:350 --rotation-offset=22 --scale=159 --position-x-offset=-520 --position-y-offset=-490 --video-bit-rate=16M -f I think cropping could be more aggressive though. It can still be optimized.

Hello, using this command as a basis, I found out that this crop and scale were absolutly perfect for quest 3.
scrcpy.exe --crop=2064:2208:2064:100 --window-title='Quest3Cast' --rotation-offset=-22 --scale=195 --position-x-offset=-520 --position-y-offset=-490 --video-bit-rate=16M -f

Hello, using this command as a basis, I found out that this crop and scale were absolutly perfect for quest 3. scrcpy --crop=2064:2208:2064:100 --window-title='Quest3Cast' --rotation-offset=-22 --scale=195 --position-x-offset=-520 --position-y-offset=-490 --video-bit-rate=16M -f

This command works well, thank you. The rotation-offset feature is great for the Quest 3 and Quest Pro. Any reason this is not being merged into the main branch?

Any reason this is not being merged into the main branch

Because I would like the transform to be performed on the server side (before encoding): https://github.com/Genymobile/scrcpy/pull/4658#issuecomment-1936558849

I tried to modify a window size of Quest3, it feels good for me.
--crop=1920:1440:20:350 --rotation-offset=20 --scale=159 --position-x-offset=-800 --position-y-offset=-500

I applied the chunks individually against master and this does still work as advertised.

Sorry to pester any updates on this one? Works fine via the alternative method/branch but my god would it be nice to just use SideQuest..

Is there any way to run the modded build that supports rotation on linux? Thx!

@rom1v Can this be merged with a TODO for server-side transform?
That will improve quality of life for a lot of Quest users.

I just published a prototype to apply a video filter on the device: #5455
You can edit the code to hardcode the AffineTransform you need for the Quest 3 (typically, a "reframe" followed by a rotation).

Please test #5455 and the new --angle option.

Superseded by #5455.


RuntimeError: Failed to export an ONNX attribute, since it's not constant, please try to make things (e.g., kernel size) static if possible

Describe the bug
File "/home/admin/.local/lib/python3.6/site-packages/torch/onnx/symbolic.py", line 90, in _parse_arg     raise RuntimeError("Failed to export an ONNX attribute, "
To Reproduce
Snippet of your code
Expected behavior
A clear and concise description of what you expected to happen.
Logs
If applicable, add error message to help explain your problem.
Environment (please complete the following information):

OS: centos
Python 3
Version [e.g. v0.1.11]

Additional context
Add any other context about the problem here.

Hello @Brave731.
It looks like the problem is in torch/onnx, not in the pytorch2keras.


Adding warning to Warehouse Selective Sync section

Proposed changes
Customers have reached out regarding failed warehouse syncs and after taking the proper troubleshooting steps we determine that the error is caused by the customer disabling the received_at property in one or many of their collections in their Warehouse Selective sync settings.
I think adding a warning that states that we use received_at as the sort key for all tables and that disabling this column will cause syncs to fail would be beneficial as it would avoid any failures / disruption in data flow.
Merge timing

ASAP once approved

Hi @pmbasco, @jacobwsmith19 - is there a permanent loss of data associated with a failed sync, or are you all able to recover the missing data with a backfill? If there's a potential for permanent data loss, I would recommend using the error callout instead of the warning callout!


GHA: Added checksum validation

Fixes #3157
Added checksum validation for WinRE Ansible file
Checklist

[x] commit message has one of the standard prefixes
[x] VPC/QPC not applicable for this PR

/merge

/approve

/approve


routed and ipvlan nic requires proxy_ndp enabled for all interfaces for reliable IPv6

The LXD NIC types routed and ipvlan rely on proxy NDP in the Linux kernel in order to advertise a container's IPv6 addresses onto the parent's network without using a bridge.
At a minimal this works by enabling proxy_ndp on both the parent interface (for ipvlan and routed modes) and the container's parent veth interface (for routed mode only).
However I have noticed that there appears to be periodic short periods of high latency approximately every 15-20s which is ultimately caused by not having sysctl net.ipv6.conf.all.proxy_ndp=1 enabled.
Here is a packet trace pinging a container with a routed NIC from another host with sysctl net.ipv6.conf.all.proxy_ndp=0:
16:19:42.030228 IP6 fe80::fc00:2ff:fe7b:13c4 > 2001:xxxx:7402:1f06::2: ICMP6, neighbor solicitation, who has 2001:xxxx:7402:1f06::2, length 32
16:19:42.030438 IP6 fe80::5400:2ff:fe7b:13c4 > fe80::fc00:2ff:fe7b:13c4: ICMP6, destination unreachable, beyond scope 2001:xxxx:7402:1f06::2, source address fe80::fc00:2ff:fe7b:13c4, length 80
16:19:43.054211 IP6 fe80::fc00:2ff:fe7b:13c4 > 2001:xxxx:7402:1f06::2: ICMP6, neighbor solicitation, who has 2001:xxxx:7402:1f06::2, length 32
16:19:43.054269 IP6 fe80::5400:2ff:fe7b:13c4 > fe80::fc00:2ff:fe7b:13c4: ICMP6, destination unreachable, beyond scope 2001:xxxx:7402:1f06::2, source address fe80::fc00:2ff:fe7b:13c4, length 80
16:19:44.078206 IP6 fe80::fc00:2ff:fe7b:13c4 > 2001:xxxx:7402:1f06::2: ICMP6, neighbor solicitation, who has 2001:xxxx:7402:1f06::2, length 32
16:19:44.078263 IP6 fe80::5400:2ff:fe7b:13c4 > fe80::fc00:2ff:fe7b:13c4: ICMP6, destination unreachable, beyond scope 2001:xxxx:7402:1f06::2, source address fe80::fc00:2ff:fe7b:13c4, length 80
16:19:45.871371 IP6 fe80::fc00:2ff:fe7b:13c4 > ff02::1:ff00:2: ICMP6, neighbor solicitation, who has 2001:xxxx:7402:1f06::2, length 32
16:19:46.263519 IP6 fe80::5400:2ff:fe7b:13c4 > fe80::fc00:2ff:fe7b:13c4: ICMP6, neighbor advertisement, tgt is 2001:xxxx:7402:1f06::2, length 32

After the initial proxy NDP has worked and the neighbour has resolved the container's MAC address as the host's (proxy NDP is working), then packets begin to flow normally.
However periodically the neighbour makes a neighbor solicitation request to the unicast address being proxied (2001:xxxx:7402:1f06::2). The host then responds with "destination unreachable, beyond scope 2001:xxxx:7402:1f06::2, source address fe80::fc00:2ff:fe7b:13c4".
This is tried several times, before the neighbour then retries the request, but this time to the multicast link-local broadcast address "ff02::1:ff00:2". At this point the neighbour appears to have invalidated its neighbour cache for 2001:xxxx:7402:1f06::2 and stops routing packets temporarily.
The LXD host kernel now correctly responds with the expected proxy NDP neighbour advertisements.
This all takes place quickly, <1s, but it means periodically there is a noticeable delay of 300-700ms for packets whilst this new NDP resolution takes place.
So proxy NDP is working, but not when the neighbour makes a unicast solicitation, only when making multicast solicitations.
Strangely though, enabling sysctl net.ipv6.conf.all.proxy_ndp=1 on the LXD host fixes this and causes correct response to unicast solicitations. This prevents the neighbour cache entry on the router from being expired and avoids delaying packets whilst a fresh NDP resolution takes place.
I am unsure why this is needed.
Proposed fix:

Update ipvlan and routed NIC type documentation to indicate that  sysctl net.ipv6.conf.all.proxy_ndp=1 should be set.
Update code to check for sysctl net.ipv6.conf.all.proxy_ndp=1 and fail to start container if not set.

Further investigation confirm IPVLAN nic type is not affected by this issue.


Release notes for 2.14

Description
Release notes for 2.14
Issues Resolved

Related https://github.com/opensearch-project/security-dashboards-plugin/issues/1846

Check List

[ ] ~New functionality includes testing~
[X] New functionality has been documented
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Closing as the notes were added as part of #1928


Remove redundant setting of client region

Issue #, if available:
Noticed while reviewing https://github.com/aws-samples/serverless-coffee-workshop/pull/63
Description of changes:
The client region is not required to be set explicitly in JS SDK v3. It's automatically read from AWS_REGION.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Good catch, thanks for the PR


Messagelog missing Label column (7.7.1)

❗ please do not add sensitive information in issues, you can provide extra information via email using issue number as reference ❗
Describe the issue
When working on a small screen with long data fields, the Label column of a messagelog is not always visible, and it is not possible to scroll that far to the right. Switching to a larger screen does show the label.
Reporter
Ricardo

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Configuration
Please provide the configuration of the Pipe or Receiver with the problem.

Input
Please provide an example of the input message.
Alternatively, provide a Ladybug report.

Environment
FF! 7.7.1

Additional Environment

DBMS: [e.g. Oracle, MSSQL, MariaDB, MySql, PostgreSQL]
Browser: [e.g. Chrome, Safari, Edge, Firefox]

Additional Context
Add any other context about the problem here. (f.e. ladybug report / test adapter with larva test)

Do you think an overflow-x would help? It is difficult to fix this as the table is filled after the it's been rendered.

This issue appears to be stale so I'm closing this.


Remove cluster_id from cluster node's hostname

Fixed: #308
Signed-off-by: CS Zhang<EMAIL_ADDRESS>

/hold
We'll need to address the following requirements and simplify the handling of the names

OCP node names having region details
PowerVS resources - instance, boot volumes, network ids, keys etc having user specified string (eg user shortid).
No portion of the name should be repeated in FQDN
PowerVS resource names can't contain dot (.)

Example
cluster_domain: mydom.com
node_name: bootstrap, masterN, workerN (eventually we should allow any names as the node role indicate the type of node)
cluster_id: test  (sub-domain)
Example fqdn for bootstrap: bootstrap.test.mydom.com  <resource_name>[.<cluster_id>].<cluster_domain>
where,
resource_name == node_name
Now if we augment the <resource_name> and cluster_id to handle requirement 1 and 2, then
resource_name = [<node_prefix>-]<node_name>[-<cluster_id_prefix>]
cluster_id_prefix = []-[<cluster_id_prefix>]
cluster_id = [<cluster_id_prefix>.]<cluster_id>
[ ] indicates optional param
where,
node_prefix = <user_specified_node_prefix>  or null
cluster_id_prefix = <random-hex> or null
Example-1
node_prefix: bpradipt
region: eu-de-2
cluster_id_prefix: false
cluster_id: test
cluster_domain: mydom.com
master resource name: bpradipt-master0-eu-de-2
master fqdn:  bpradipt-master0-eu-de-2.test.mydom.com
OCP node name: bpradipt-master0-eu-de-2.test
Example-2
node_prefix: bpradipt-dev
region: eu-de-2
cluster_id_prefix: true
cluster_id: test
cluster_domain: mydom.com
master resource name: bpradipt-dev-master0-eu-de-2-idk4
master fqdn:  bpradipt-dev-master0-eu-de-2-idk4.test.mydom.com
OCP node name: bpradipt-dev-master0-eu-de-2-idk4.test
cc @cs-zhang @Prajyot-Parab @yussufsh please review and let me know your comments

@cs-zhang we can go with example-3. Let's wait for a day to hear back from others.

For resource name, all resources belong to same cluster should be grouped together showing in UI.  For Example 3: master0-bpradipt-dev-eu-de-2-idk4  that would not be possible, in this case the resources will be grouped by base node name master0. So I prefer bpradipt-dev-eu-de-2-idk4-master0, that will make all resources will be grouped together.
Example 1 -- defined cluster_id
node_prefix: bpradipt-dev
region: eu-de-2
cluster_id_prefix: true
cluster_id: test
cluster_domain: mydom.com
master resource name: bpradipt-dev-eu-de-2-idk4-master0
master fqdn: bpradipt-dev-eu-de-2-idk4-master0.test.mydom.com
OCP node name: bpradipt-dev-eu-de-2-idk4-master0.test
Example 2 -- undefined cluster_id
node_prefix: bpradipt-dev
region: eu-de-2
cluster_id_prefix: cluster-id
cluster_id: false
cluster_domain: mydom.com
master resource name: bpradipt-dev-eu-de-2-idk4-master0
master fqdn: bpradipt-dev-eu-de-2-idk4-master0.cluster-id-xxxx.mydom.com
OCP node name: bpradipt-dev-eu-de-2-idk4-master0.cluster-id-xxxx

For resource name, all resources belong to same cluster should be grouped together showing in UI. For Example 3: master0-bpradipt-dev-eu-de-2-idk4 that would not be possible, in this case the resources will be grouped by base node name master0. So I prefer bpradipt-dev-eu-de-2-idk4-master0, that will make all resources will be grouped together.

Good point @cs-zhang .

Example 1 -- defined cluster_id
node_prefix: bpradipt-dev
region: eu-de-2
cluster_id_prefix: true
cluster_id: test
cluster_domain: mydom.com
master resource name: bpradipt-dev-eu-de-2-idk4-master0
master fqdn: bpradipt-dev-eu-de-2-idk4-master0.test.mydom.com
OCP node name: bpradipt-dev-eu-de-2-idk4-master0.test
Example 2 -- undefined cluster_id
node_prefix: bpradipt-dev
region: eu-de-2
cluster_id_prefix: cluster-id

I think you meant it to be true cluster_id_prefix: true

cluster_id: false

undefined cluster_id should be empty cluster_id:

cluster_domain: mydom.com
master resource name: bpradipt-dev-eu-de-2-idk4-master0

master fqdn: bpradipt-dev-eu-de-2-idk4-master0.cluster-id-xxxx.mydom.com

this should be bpradipt-dev-eu-de-2-idk4-master0.mydom.com

OCP node name: bpradipt-dev-eu-de-2-idk4-master0.cluster-id-xxxx

this should be bpradipt-dev-eu-de-2-idk4-master0

I feel we can still use the old format for hostnames eg. master-0.<cluster_id>-<zone>.<domain> and set full FQDN in the dhcp configuration in the helpernode vars.
oc get nodes should start showing node names with sub and main domain. Can you try it our @cs-zhang ?

cluster_id_prefix: true made me confused all along and there is no node_prefix.
cluster_id_prefix can take a string value or can be empty string.

This is fine as long as we don't use a random hex string when cluster_id_prefix is an empty string. The reason I mentioned it as boolean was to emphasize the point about controlling the inclusion (or exclusion) of hex string.

This is fine as long as we don't use a random hex string when cluster_id_prefix is an empty string. The reason I mentioned it as boolean was to emphasize the point about controlling the inclusion (or exclusion) of hex string.

The hex is created when cluster_id is not provided. If cluster_id_prefix is empty only cluster_id is used (no hex). Inclusion of zone depends on the another flag.

Now the instance name in PowerVS looks like this: cz-d8e4-eu-de-2-master-0
the FQDN is used as node name, and the output of the oc:
[root@cz-d8e4-eu-de-2-bastion-0 ~]# oc get nodes
NAME                                 STATUS   ROLES    AGE    VERSION
eu-de-2-master-0.cz-d8e4.cloud.lab   Ready    master   112m   v1.20.0+7d0a2b2
eu-de-2-master-1.cz-d8e4.cloud.lab   Ready    master   111m   v1.20.0+7d0a2b2
eu-de-2-master-2.cz-d8e4.cloud.lab   Ready    master   112m   v1.20.0+7d0a2b2
eu-de-2-worker-0.cz-d8e4.cloud.lab   Ready    worker   96m    v1.20.0+7d0a2b2
eu-de-2-worker-1.cz-d8e4.cloud.lab   Ready    worker   95m    v1.20.0+7d0a2b2
[root@cz-d8e4-eu-de-2-bastion-0 ~]#

Now the instance name in PowerVS looks like this: cz-d8e4-eu-de-2-master-0
the FQDN is used as node name, and the output of the oc:
[root@cz-d8e4-eu-de-2-bastion-0 ~]# oc get nodes
NAME                                 STATUS   ROLES    AGE    VERSION
eu-de-2-master-0.cz-d8e4.cloud.lab   Ready    master   112m   v1.20.0+7d0a2b2
eu-de-2-master-1.cz-d8e4.cloud.lab   Ready    master   111m   v1.20.0+7d0a2b2
eu-de-2-master-2.cz-d8e4.cloud.lab   Ready    master   112m   v1.20.0+7d0a2b2
eu-de-2-worker-0.cz-d8e4.cloud.lab   Ready    worker   96m    v1.20.0+7d0a2b2
eu-de-2-worker-1.cz-d8e4.cloud.lab   Ready    worker   95m    v1.20.0+7d0a2b2
[root@cz-d8e4-eu-de-2-bastion-0 ~]#

I think this fits all the use cases. @bpradipt are we okay with it?
Suggestion:
eu-de-2-master-0.cz-d8e4.cloud.lab -> master-0.cz-d8e4-eu-de-2.cloud.lab
The region info can be added to the full cluster name and will be easy to implement.

Now the instance name in PowerVS looks like this: cz-d8e4-eu-de-2-master-0
the FQDN is used as node name, and the output of the oc:
[root@cz-d8e4-eu-de-2-bastion-0 ~]# oc get nodes
NAME                                 STATUS   ROLES    AGE    VERSION
eu-de-2-master-0.cz-d8e4.cloud.lab   Ready    master   112m   v1.20.0+7d0a2b2
eu-de-2-master-1.cz-d8e4.cloud.lab   Ready    master   111m   v1.20.0+7d0a2b2
eu-de-2-master-2.cz-d8e4.cloud.lab   Ready    master   112m   v1.20.0+7d0a2b2
eu-de-2-worker-0.cz-d8e4.cloud.lab   Ready    worker   96m    v1.20.0+7d0a2b2
eu-de-2-worker-1.cz-d8e4.cloud.lab   Ready    worker   95m    v1.20.0+7d0a2b2
[root@cz-d8e4-eu-de-2-bastion-0 ~]#

Can cluster-id be empty ? For the case where user doesn't want the hexID

I think this fits all the use cases. @bpradipt are we okay with it?
Suggestion:
eu-de-2-master-0.cz-d8e4.cloud.lab -> master-0.cz-d8e4-eu-de-2.cloud.lab
The region info can be added to the full cluster name and will be easy to implement.

For the above, @cs-zhang mentioned the following "For resource name, all resources belong to same cluster should be grouped together showing in UI. For Example 3: master0-bpradipt-dev-eu-de-2-idk4 that would not be possible, in this case the resources will be grouped by base node name master0. So I prefer bpradipt-dev-eu-de-2-idk4-master0, that will make all resources will be grouped together."

Now the instance name in PowerVS looks like this: cz-d8e4-eu-de-2-master-0
the FQDN is used as node name, and the output of the oc:
[root@cz-d8e4-eu-de-2-bastion-0 ~]# oc get nodes
NAME                                 STATUS   ROLES    AGE    VERSION
eu-de-2-master-0.cz-d8e4.cloud.lab   Ready    master   112m   v1.20.0+7d0a2b2
eu-de-2-master-1.cz-d8e4.cloud.lab   Ready    master   111m   v1.20.0+7d0a2b2
eu-de-2-master-2.cz-d8e4.cloud.lab   Ready    master   112m   v1.20.0+7d0a2b2
eu-de-2-worker-0.cz-d8e4.cloud.lab   Ready    worker   96m    v1.20.0+7d0a2b2
eu-de-2-worker-1.cz-d8e4.cloud.lab   Ready    worker   95m    v1.20.0+7d0a2b2
[root@cz-d8e4-eu-de-2-bastion-0 ~]#

Can cluster-id be empty ? For the case where user doesn't want the hexID

cluster_id cannot be empty because helpernode vars required it. So when cluster_id is not provided, random hex will be used.

I think this fits all the use cases. @bpradipt are we okay with it?
Suggestion:
eu-de-2-master-0.cz-d8e4.cloud.lab -> master-0.cz-d8e4-eu-de-2.cloud.lab
The region info can be added to the full cluster name and will be easy to implement.

For the above, @cs-zhang mentioned the following "For resource name, all resources belong to same cluster should be grouped together showing in UI. For Example 3: master0-bpradipt-dev-eu-de-2-idk4 that would not be possible, in this case the resources will be grouped by base node name master0. So I prefer bpradipt-dev-eu-de-2-idk4-master0, that will make all resources will be grouped together."

I am fine with the UI naming. This suggestion was specifically for oc get nodes for simplicity we can associate the region name with cluster_id.

UI: cz-d8e4-eu-de-2-master-0
Nodes: master-0.cz-d8e4-eu-de-2.cloud.lab

eu-de-2-master-0.cz-d8e4.cloud.lab -> master-0.cz-d8e4-eu-de-2.cloud.lab

Since the FQDN for the master-0 is eu-de-2-master-0.cz-d8e4.cloud.lab, the same as the node name and  the region info is not used in cluster_id. Change to master-0.cz-d8e4-eu-de-2.cloud.lab can cause confuse for user.  So for consistent with UI and FQDN,  following is better:
UI: cz-d8e4-eu-de-2-master-0
Nodes: eu-de-2-master-0.cz-d8e4.cloud.lab
If the cluster_id is defined as ocp4:
UI: ocp4-eu-de-2-master-0
Nodes: eu-de-2-master-0.ocp4.cloud.lab

eu-de-2-master-0.cz-d8e4.cloud.lab -> master-0.cz-d8e4-eu-de-2.cloud.lab

Since the FQDN for the master-0 is eu-de-2-master-0.cz-d8e4.cloud.lab, the same as the node name and the region info is not used in cluster_id. Change to master-0.cz-d8e4-eu-de-2.cloud.lab can cause confuse for user. So for consistent with UI and FQDN, following is better:
UI: cz-d8e4-eu-de-2-master-0
Nodes: eu-de-2-master-0.cz-d8e4.cloud.lab
If the cluster_id is defined as ocp4:
UI: ocp4-eu-de-2-master-0
Nodes: eu-de-2-master-0.ocp4.cloud.lab

I am fine with anything.. it was just a suggestion 😄  that would help while implementing the changes.

/unhold

@cs-zhang Changes are good but I feel we can refactor the code to build the name_prefix and node_prefix (including the training -) in ocp.tf instead of each module. Also the cluster_domain with wildcard dns can be built in root module and passed to each module.
What do you think?

@yussufsh : Please let me know if you need any help with this issue/ we are blocked to close?

/cherry-pick release-4.8

/cherry-pick release-4.7

/cherry-pick release-4.6


Reverted! thanks for the advice

          Reverted! thanks for the advice

Originally posted by @prulloac in https://github.com/devcontainers/cli/pull/774#discussion_r1532358300

publish-dev-containers.yml.txt

      Reverted! thanks for the advice

publish-dev-containers.yml.txt

publish-dev-containers.yml.txt
publish-dev-containers.yml (1).txt

publish-dev-containers.yml.1 (1).txt

Looks like this was created by accident, closing. If needed, feel free to reopen with more details, thank you!


Extract review: Error handling

Describe the bug
If ffmpeg_probe fail in extract_review, it can produce empty data {}. Plugin doesn't handle such case and all ends up with:
ERROR:pyblish.plugin:Traceback (most recent call last):
File "Z:\pype\pype-staging\pype-setup\repos\pyblish-base\pyblish\plugin.py", line 517, in __explicit_process
runner(*args)
File "Z:\pype\pype-staging\pype-setup\repos\pype\pype\plugins\global\publish\extract_review.py", line 62, in process
File "Z:\pype\pype-staging\pype-setup\repos\pype\pype\plugins\global\publish\extract_review.py", line 161, in main_process
File "Z:\pype\pype-staging\pype-setup\repos\pype\pype\plugins\global\publish\extract_review.py", line 343, in _ffmpeg_arguments
File "Z:\pype\pype-staging\pype-setup\repos\pype\pype\plugins\global\publish\extract_review.py", line 609, in rescaling_filters
File "Z:\pype\pype-staging\pype-setup\repos\pype\pype\lib.py", line 1381, in ffprobe_streams
return json.loads(popen_output)["streams"]
KeyError: 'streams'

not very informative.
To Reproduce
Publish review on non-existent file 😱
Expected behavior
Shoud print error like "ffmpeg_probe produced empty result. Please check rendered files."

this has already been fixed.


delve and docker setup to debug multi-cloud API

These files allow us to build a debug version of the API, that can be used with delve, inside the docker container:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

1. this is in the debug sub-folder under api folder
2. in this, one needs to run ./runDockerBuild.sh
3. after this, stop  the existing API container
4. bring up the debug version that you just built, by running docker-compose up -d
5. please ensure the same env. settings in the docker-compose.yml under 'debug' folder, from the docker-compose.yml under the 'api' folder

@skdwriting @wisererik @anvithks @nguptaopensds  @himanshuvar please review

multi cloud CI for Travis. Verify and Unit test steps.

@Shruthi-1MN @skdwriting @kumarashit @wisererik please review and merge

If the purpose of this PR is to introduce 'debug with delve' feature, this needs to be in a seperate project, rather than inside multi-cloud project.

hi
this was done ONLY for multi cloud, hence inside multi cloud. Do confirm
either ways, will do
Thanks.
On Tue, Oct 22, 2019 at 10:02 AM Joseph Vazhappilly <
<EMAIL_ADDRESS>wrote:

If the purpose of this PR is to introduce 'debug with delve' feature, this
needs to be in a seperate project, rather than inside multi-cloud project.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/opensds/multi-cloud/pull/182?email_source=notifications&email_token=ALRQ4JJFX6TU5RSFKMJV46TQPZ66BA5CNFSM4IWXBAN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB4QB6Q#issuecomment-544801018,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALRQ4JJDC5GGLHHHA4A24FLQPZ66BANCNFSM4IWXBANQ
.

--
thanks and regards
Prakash

If the purpose of this PR is to introduce 'debug with delve' feature, this needs to be in a seperate project, rather than inside multi-cloud project.

Thanks. will do as we discussed, moving DELVE debug out of the CI PR.

hi this was done ONLY for multi cloud, hence inside multi cloud. Do confirm either ways, will do Thanks.
…
On Tue, Oct 22, 2019 at 10:02 AM Joseph Vazhappilly < @.***> wrote: If the purpose of this PR is to introduce 'debug with delve' feature, this needs to be in a seperate project, rather than inside multi-cloud project. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#182?email_source=notifications&email_token=ALRQ4JJFX6TU5RSFKMJV46TQPZ66BA5CNFSM4IWXBAN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB4QB6Q#issuecomment-544801018>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALRQ4JJDC5GGLHHHA4A24FLQPZ66BANCNFSM4IWXBANQ .
-- thanks and regards Prakash

Thanks. will do as we discussed, moving DELVE debug out of the CI PR.

If the purpose of this PR is to introduce 'debug with delve' feature, this needs to be in a seperate project, rather than inside multi-cloud project.

Thanks. will do as we discussed, moving DELVE debug out of the CI PR.

LGTM

closing, since could not merge  > 10 days


threaded queue fetcher limitations

A brain dump of where I left off.
tqfetcher behaves reasonably (fetches 10-15 stories/second) given a well mixed input queue.  But if the workload is not well mixed (ie; historical URLs from a single site) are dropped into the input queue all at once, the thruput can drop to 1 story every 5 seconds.
RabbitMQ applications can specify the number of messages to be delivered to it until one of the pending messages is acknowledged (and removed from the input queue).  The number is called the prefetch.
tqfetcher keeps a moving average of past req request times, but does not schedule fetches based on the available threads, rather it optimistically delays requests based on past request time and the time of the last request sent.  When a past estimate is not available (average is zero), requests are not delayed.
After delay (or no delay) stories are placed into a work queue for distribution to worker threads.  If the work queue accumulates ANY significant number of ready requests, the ability to control delay between requests to a site is SEVERELY compromised.  Because of this the prefetch is kept very low (two messages per available worker thread).
Thoughts for improvements:
Right now, tqfetcher's MINIMUM delay between starting requests to any one site is 5 seconds.
THIS IS EXCEEDINGLY CONSERVATIVE!  Scrapy may not have had ANY minimum delay!!!
HOWEVER: very low delay numbers would allow VERY large numbers of requests to a site
to be delayed (eating up the prefetch).  A fix for this might be:
Limit the number of stories that can be delayed for a particular site to a "fair share" of the prefetch (perhaps prefetch / active_sites or prefetch / (active_sites + 1), where active_sites is the number of sites successfully fetched from in the last minute (counted in the once a minute periodic task).
Enforce a delay between first requests to any previously uncontacted site?
and/ Check the work queue length before adding a request (more than one request per thread is excessive).
The grandest idea/wish is to plan out all activity (within the next fast delay queue period interval) so that the work queue never gets large, and requests are delivered to the work queue at a measured rate that never exceeds available capacity.  Initial requests to uncontacted sites should be treated as taking a long time (MAX_CONNECT + MAX_READ seconds?).
Consider whether it's possible to detect if ALL requests are failing due to Internet outage.  The worst case is that if the outage is more than 10 hours, stuff gets dumped into the fetcher-quar(antine) queue, and has to be manually moved.

(one of a no doubt continuing series of things I forgot):
Half-baked idea:  If large number of requests seen for a particular site (large number of requests couldn't be delayed in the last minute), consider lowering the minimum interval for that site (requires "fair share" to not hog the prefetch).
This seems reasonable for sites that generate large numbers of URLs per day,
but less reasonable if we want to back fill for a site, and load the queue with old URLs.
There is code that attempts to back off when a 429 response is seen, but it's not well tested.

Another issue/thought (which in theory applies to all queue workers, but in practice only really effects tqfetcher):
When tqfetcher sees that a site/domain is "fully booked" with fetches for the next two minutes, it shunts any additional input requests to the "fetcher-fast" queue, where it will hang out for two minutes, and then be appended to the regular "fetcher-input" queue.
In normal operation (hourly batches from rss-queuer), the new requests are run thru in the first part of the hour (shunting unreachable, and other "soft" errors to the -retry queue (after which they'll end up at the end of the -input queue).
Something I coded for, from the very start, is to allow any queue worker to take input from multiple queues (so that retries can be processed as soon as their delay period ends, rather than going to the back of the line).  The sticky bit is that ISTR that a Pika/RabbitMQ channel can only get messages from one queue, so I made sure that worker objects and channels are not wired into the code as 1:1.
The place this MAY be visible right now:  The fetches from old rss/csv files are taking over a day:  My guess is that the first pass thru the queue is taking less than a day, but that:

running thru the retries (which may or may not be due to the nature of old links) an hour or more
the number of retries keeps the queue abover 100K entries (the point at which another file of stories will be added to the queue, to avoid treating RabbitMQ as a bottomless vessel, which is important on systems that don't have the queues persisted on a huge RAID volume)
it takes a couple of hours for the queue (now containing "dregs") to go below 100K entries and get "fresh meat" added in
I'm not sure lowering the threshold will help: it will allow more dregs to accumulate, more quickly (tho perhaps better mixed with the older retries).

The bottom line:
Consider handling -retry and -fast message handling differently:  Instead of having them appended to -input after their time in purgatory, put them into ANOTHER queue that's served with equal (or higher) thruput/prefetch to/than the -input queue so that they're retried "on time" rather than waiting for the new entries added to the -input queue (during their time in  purgatory) to be drained before getting another chance...


Idea: add pyup.io

pyup.io is a service that helps you to keep your requirements files up to date. It sends you automated pull requests whenever there’s a new release for one of your dependencies.
https://pyup.io

@metachris ping :)

Closing due to focus on NEO3


Fix reproducer directory creation

Current task doesn't correctly loop over items so it only ensures
cifmw_reproducer_basedir is created, not
cifmw_reproducer_basedir/artifacts and cifmw_reproducer_basedir/logs
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

/approve
wow, I thought I corrected that ages ago o_O

recheck

/approve
wow, I thought I corrected that ages ago o_O

Wasn't causing any issues I could see, I just noticed it reading through the role :P

/retest

/retest


Account for corev1.Envvar with ValueFrom

Looks like I may have to do some secret getting and base64 decoding here.
https://github.com/openshift/openshift-velero-plugin/blob/198abe821efdd023ed32344f15c8860e38c401f3/velero-plugins/imagestream/shared.go#L105-L107

closed by https://github.com/openshift/openshift-velero-plugin/pull/154


Docs don't indent bulleted list for attributes of file and image

This is in the pipeline specification section of the docs:
    file:
    path: path to the reported file
    title: human readable description of the file
    image:
    path: path to the reported image, usually PDF
    thumbnail: path to the reported thumbnail, usually PNG or JPEG
    title: human readable description of the image

The lack of nesting is confusing, as file and image should be the top-level names, with the others nested beneath them.

I fixed this here: https://github.com/pepkit/pipestat/commit/54e54ddc9b88ed2a8328a14f36f3c824b40cda9a


mucommander: Use jdk11 & gradle6

Motivation for this change
Remove second-last usage of gradle 4 in nixpkgs. Only one left is in pkgs/development/compilers/openjdk/openjfx/11.nix. Also use jdk11 for running mucommander instead of jre8.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

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

1 package built:

mucommander

Fails to build on mac:
building

Welcome to Gradle 6.7!

Here are the highlights of this release:
 - File system watching is ready for production use
 - Declare the version of Java your build requires
 - Java 15 support

For more details see https://docs.gradle.org/6.7/release-notes.html

FAILURE: Build failed with an exception.

* What went wrong:
Gradle could not start your build.
> Could not create service of type ResourceSnapshotterCacheService using GradleUserHomeServices.createResourceSnapshotterCacheService().
   > java.net.BindException: Operation not permitted (Bind failed)

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 1s

:-(
I cannot reproduce this under linux so far. I guess the sandbox on Mac is different than the one on linux. I have checked all gradle calls and they all pass --no-daemon, so I am not sure why it tries to bind to a network interface. And the gradle source code is rather large, so I have no idea what's going on there.
I am not sure how to proceed here, as I do not have a Mac machine at hand to debug this.

I am not sure how to proceed here, as I do not have a Mac machine at hand to debug this.

Just mark it broken.

Done.


Accessibility in regards to quiz visuals

My quiz is going to have some visuals, how do I make sure they are accessible without describing the visuals in alternative text in such a way that it gives away the answer?

This is somewhat held up by #35 being figured out.


编译时error

error: failed to run custom build command for ctp-futures v0.1.0 (/Users/dhcn/Downloads/rust-share-main/crates/ctp-futures)
Caused by:
process didn't exit successfully: /Users/dhcn/Downloads/rust-share-main/target/debug/build/ctp-futures-80259c5b71578461/build-script-build (exit status: 101)
--- stdout
cargo:rustc-link-search=./crates/ctp-futures/v_current
cargo:rustc-link-search=native=/Users/dhcn/Downloads/rust-share-main/crates/ctp-futures/v_current
--- stderr
thread 'main' panicked at 'called Result::unwrap() on an Err value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', crates/ctp-futures/build.rs:544:10
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

问题在于上下文so的文件名有问题，缺lib了

#5


Minor update dependencies documentation

Bottled Water depends on librdkafka 0.8.4 or later because it refers to rd_kafka_conf_set_dr_msg_cb, which was introduced in 0.8.4 (source).
Besides, the libsnappy documentation is now hosted to Github : )

It looks like @gonzalo-bulnes hasn't signed our Contributor License Agreement, yet.
Appreciation of efforts,
clabot

[clabot:check]

@confluentinc It looks like @gonzalo-bulnes just signed our Contributor License Agreement. :+1:
Always at your service,
clabot

Excellent, thank you @gonzalo-bulnes!


I am using mac book pro, sonoma.

Description
want to connect dbeaver communiy to bigquery. I am using mac book bro. when i tried installing bigquery driver I was getting PKIX no valid ssl for "https://storage.googleapis.com/simba-bq-release/jdbc/SimbaJDBCDriverforGoogleBigQuery42_<IP_ADDRESS>1.zip". Then I have downloaded ssl for storage.googleapis.com and the driver is installed.
Now I am getting same kind of error for service account.
[Simba]BigQueryJDBCDriver HttpTransport IO error : Error getting access token for service account: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target, iss<EMAIL_ADDRESS>EXEC_JOB_EXECUTION_ERR EXEC_JOB_EXECUTION_ERR Error getting access token for service account: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target, iss<EMAIL_ADDRESS>Error getting access token for service account: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target, iss<EMAIL_ADDRESS>PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target unable to find valid certification path to requested target unable to find valid certification path to requested target
DBeaver Version
23.3.0
Operating System
mac os
Database and driver
DB: BigQuery
Driver: SimbaJDBCDriverforGoogleBigQuery42_<IP_ADDRESS>1.zip
Steps to reproduce
No response
Additional context
No response

Hi, @ANIRUDHTEAM1000. Are you working in a restrictive network, behind a proxy, for example?

It's been a while since no update here. If the issue is still actual please let me know and provide additional information.