When runtime adds Cocoapods, it should include 'i386' as architecture options

For instance, this Cocoapod:
https://github.com/NathanWalker/MaterialCard
Can be setup as a plugin with a Podfile:
pod 'MaterialCard', '~> 1.0.4'

And when run via tns emulate ios, it fails because the Simulator requires i386 architecture and pod setups by default only specify the various standard $(ARCHS_STANDARD) flavors like arm64 armv7 armv7s.
The runtime should automatically ensure that i386 architecture is added for CocoaPods when installing and running them in the Simulator.
Worth noting that using tns run ios with a iPhone connected runs just fine.
So it's definitely isolated to running in the Simulator.
The pod is used here:
https://github.com/bradmartin/nativescript-cardview
Holding off on releasing a new version until I can get some feedback here on what's going on with the aforementioned.
Please help provide insight here if anyone knows?

Sample of errors resulting from not including i386 as build architecture option:
ld: warning: Auto-Linking supplied '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftFoundation.dylib', missing required architecture i386 in file /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftFoundation.dylib (3 slices)
ld: warning: Auto-Linking supplied '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftObjectiveC.dylib', missing required architecture i386 in file /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftObjectiveC.dylib (3 slices)
ld: warning: Auto-Linking supplied '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftDispatch.dylib', missing required architecture i386 in file /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftDispatch.dylib (3 slices)
ld: warning: Auto-Linking supplied '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftCore.dylib', missing required architecture i386 in file /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftCore.dylib (3 slices)
ld: warning: Auto-Linking supplied '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftCoreGraphics.dylib', missing required architecture i386 in file /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftCoreGraphics.dylib (3 slices)
ld: warning: Auto-Linking supplied '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftUIKit.dylib', missing required architecture i386 in file /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftUIKit.dylib (3 slices)
ld: warning: Auto-Linking supplied '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftDarwin.dylib', missing required architecture i386 in file /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftDarwin.dylib (3 slices)
ld: warning: Auto-Linking supplied '/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftCoreImage.dylib', missing required architecture i386 in file /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos/libswiftCoreImage.dylib (3 slices)

Hi @NathanWalker
Check this thread and try the suggested solutions. Downgrading to Xcode 7.1 should do the trick but if you don't want to downgrade you can try settings "Embedded Content Contains Swift Code" option to "Yes" in the app's target. If this makes it work, you can apply this setting by setting it in a plugin's build.xcconfig file, instead of manually changing the Xcode project in platforms/ios. The CLI will merge the .xcconfig file with the project settings.
Let me know if this works for you.

@ivanbuhov Thanks for you help. I've tried this but doesn't seem to work or I'm not doing it correctly.
Things I've tried:

add platforms/ios/build.xcconfig alongside the Podfile in the plugin with these contents:

EMBEDDED_CONTENT_CONTAINS_SWIFT = YES

Doesn't appear to change anything.

add post_install step to Podfile which would append that to the Pod's .xcconfig:

post_install do |installer|
    system "sed -i '' -E 's/SKIP_INSTALL[[:space:]]=[[:space:]]YES/SKIP_INSTALL = YES\\\nEMBEDDED_CONTENT_CONTAINS_SWIFT = YES\\\n/g' Pods/Target\\ Support\\ Files/MaterialCard/*.xcconfig"
end

It does add to the .xcconfig correctly but it results in the same error above. (missing required architecture i386)

modifying post_install to add VALID_ARCHS:

post_install do |installer|
    system "sed -i '' -E 's/SKIP_INSTALL[[:space:]]=[[:space:]]YES/SKIP_INSTALL = YES\\\nEMBEDDED_CONTENT_CONTAINS_SWIFT = YES\\\nVALID_ARCHS = \\\"i386\\\"/g' Pods/Target\\ Support\\ Files/MaterialCard/*.xcconfig"
end

Same error still.
Any other suggestions? Or help me understand what is going on. Pretty frustrating.

My idea was to take advantage of the CLI support for merging build.xcconfig files instead of doing it manually, but it seems this will not make it work. What is your Xcode version? If you are using Xcode 7.2, try downgrading to 7.1.1. It is helpful to know whether the issue is reproducible with Xcode 7.1.1 because according to this related thread it appears only on Xcode 7.2.

Thanks @ivanbuhov you've been very helpful. I'm going to try the brave new ground with XCode 7.3 just released yesterday actually. If that doesn't work, I'll downgrade.

Ok so I just tried 7.3 and it works and fixes this issue! Hooray! :+1:
However this issue applies (added separately) here:
https://github.com/NativeScript/ios-runtime/issues/538
I'll close this in favor of the new one, hopefully a new ios-runtime can be released to fix that for 7.3 and all will be good.


Follow Up: JSON Cluster Files

Follow up to #174

[x] Documentation on setup, usage, options
[x] Support S3 events module
[ ] Support custom Terraform as input
[x] CloudTrail patterns as inputs
[ ] Investigate if we still need variables.tf

Support custom Terraform as input

A special filename can be reserved in the terraform directory for this purpose (like misc.tf, or custom.tf).   Documentation should also reflect this

Investigate if we still need variables.tf

We still need it


⚠ PrivateHD has degraded performance

In b985d9a, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2340 ms

Resolved: PrivateHD performance has improved in 5633346.


hi Dev

Can anyone please explain how to integrate different application
am new to integration and new to ESB
thanks in advance.......

Please refer to Mulesoft documentation site for more information:
https://docs.mulesoft.com/
Thanks!


Dmceachernmsft/MeetingCompsiteAlternateProp

What
remove the boolean type for the ui options props for the meeting composite and call control component
Why
Alternate change to PR: https://github.com/Azure/communication-ui-library/pull/1266/files
How Tested
Ran locally in story book with different meeting composite options props.

Other options in pull 1266 this is based off of is better. Closing as a result.


newsflash: 2.3.1 -> 3.0.2

Description of changes

currently blocked by #247766
fixes #258497
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/developing-news-flash-gtk/11031/5

@kira-bruneau : I added the blueprint-compiler and rebased, because the GNOME PR is merged.

it starts and seems to work fine, but it prints:
23:20:55 - ERROR - Failed to set background message: Portal request failed: org.freedesktop.portal.Error.NotAllowed: Only sandboxed applications can set background status (news_flash_gtk::app:2501)

no idea about it.

it starts and seems to work fine, but it prints:
23:20:55 - ERROR - Failed to set background message: Portal request failed: org.freedesktop.portal.Error.NotAllowed: Only sandboxed applications can set background status (news_flash_gtk::app:2501)

no idea about it.

My guess is that's coming from support for that GNOME 44 feature which well... works only with Flatpak and maybe snap(?). We can probably ignore it or patch it out so it doesn't attempt to use that api.

btw second commit should probably be newsflash: adjust binary name

@surfaceflinger i thought about squashing the commits before merging.

so i did use this for 3 days. Works perfectly. I think this is ready for merge.
Not sure if we should patch out the "gnome-background" stuff. gnome users might want to rely on it. We better should report upstream, that there are users without gnome.

so i did use this for 3 days. Works perfectly. I think this is ready for merge.
Not sure if we should patch out the "gnome-background" stuff. gnome users might want to rely on it. We better should report upstream, that there are users without gnome.

not sure what u meant by gnome users might want to rely on it, i meant there's no need to touch it (in newsflash, not gnome, i assume it would work if you installed newsflash from flatpak, not nix) unless this error in log makes u mad.
basically newsflash tries to use that new gnome api that (currently?) is available only for apps from flatpak. it can just be ignored :p

anyways, i'm using this too right now, imported my opml and so far works great 🙂

Hmm... I wonder if there's some way we can workaround around that with the way we package newsflash - but I think this is good to merge without it since it's non-breaking.
Thanks @Stunkymonkey!!

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

1 package built:

newsflash

Note t hat I also get
ERROR - Failed to set background message: Portal request failed: org.freedesktop.portal.Error.NotAllowed: Only sandboxed applications can set background status (news_flash_gtk::app:2461)

when running the old version of Newsflash on KDE Plasma. The message appears each time I toggle the "Keep running; fetch updates in the background" option in settings as well.
It would be nice to get background support working, I'd assume that's a modern replacement for the systray and notification stack? But I feel that would require a decent amount of work.
PS, I assume adding a desktop file to ~/.config/autostart with io.gitlab.news_flash.NewsFlash --headless  is the main way to auto start the app when running with background on?


feat(new): Added Azure.ASE.AvailabilityZone

PR Summary
Fixes #2964
Added Azure.ASE.AvailabilityZone.
PR Checklist

[x] PR has a meaningful title
[x] Summarized changes
[x] Change is not breaking
[x] This PR is ready to merge and is not Work in Progress
Rule changes

[x] Unit tests created/ updated
[x] Rule documentation created/ updated
[x] Link to a filed issue
[x] Change log has been updated with change under unreleased section

Other code changes

[ ] Unit tests created/ updated
[ ] Link to a filed issue
[ ] Change log has been updated with change under unreleased section

Ready for review @BernieWhite.
I had to do some deployments to test this out.
When enabling it at environment level, all deployed plans within the environments will have the property set to true.
Setting zone redundancy at the App Service Environment (ASE) level ensures that all VMs pre-provisioned for the environment are distributed across different availability zones. The minimum configuration will be 3 VMs by default.
Since it's also inherited on the plan level, the minimum 3 default instances will be distributed across these VMs. Instance 1 on VM1 (AZ1), instance 2 on VM2 (AZ2), instance 3 on VM3 (AZ3) etc.

Thanks @BernieWhite. I agree with you, the custom reason is confusing. I have adjusted accordingly now.


Write a Java program to convert inches to feet

Description
Write a Java program to convert inches to feet
1 foot = 12 inches
Input  : 60
Output : 5

How to contribute

Save the solution in ConvertInchesToFeet.java file
Add ConvertInchesToFeet.java file in program/convert-inches-to-feet folder

!assign

!assign

Hey @anandfresh, this issue is already assigned to @notpx !!!
Please choose another issue.
Thanks for your interest in contributing to this project.


Update workflow config to prevent specific jobs from executing in forked repositories

Description
Update workflow config to prevent specific jobs from executing in forked repositories.
Type of change

This pull request adds or changes features of Radius and has an approved issue (issue link required).
Fixes: #6869

Auto-generated summary

🤖[deprecated] Generated by Copilot at 2adcf55
Summary
🔒🚫🛠

This pull request adds repository checks to various GitHub workflows to ensure they only run on the main radius-project/radius repository. This prevents wasting resources, causing errors, or interfering with other repositories that may use the same workflows.

Sing, O Muse, of the wise and skillful changes
That the noble developers of radius made
To guard their workflows from unwanted dangers
And ensure their quality standards stayed.

Walkthrough

Add conditions to various workflows to only run on the official repository radius-project/radius (link, link, link, link, link, link, link, link, link, link, link, link)
Add conditions to the generate-release-note and release jobs of the release workflow to only run on pull requests or pushes, respectively (link, link)

/ok-to-test

/ok-to-test


Code coverage NOT pickup up all files

the isparta loader for karma is not picking up all files so its code coverage reports are wrong as it only includes files one has imported into a test. I think this was working in version 0.18 when you had the karma.entry.js file

Hey @CurtisHumphrey, I saw you mention that in another PR/issue. I just pushed a fix for this an hour or two ago and the problem appears to be fixed. Could you verify?
Thanks!

It does appear to work now!  I'll have to figure out what different between my snapshot and your current build.


Replace objects.include/exclude -> objects.filter?

Include/exclude are my own invention. Their purpose is to selectively add/remove properties from an object by key. The original include was actually named filterByKey. Also, object.includes overlaps functionality with objects.pick.
That's good an all but I think it would be much more beneficial to have an object-specific filter method that allows the ability to include/exclude based on a function that returns true/false.
Notes
console.log(objects.filter({ small: "ant", medium: "dog", big: "elephant" }, (key, value) => ['small', 'big'].includes(key)));
> { small: 'ant', big: 'elephant' }

References

objects.exclude
objects.include
objects.pick

@jkvyff What do you think?

It would make sense to make it more flexible to the type of filtering desired.
Followup,  would you want to retain the dual focus of include/exclude with a filter/remove functionality but the remove function would return the object with instead of properties removed?

I like the idea of just having filter to have a very flexible function while using not operator in user provided function to handle negation cases.


gpt-4o with Images throws a 431 Request Header Fields Too Large

When exchanging gpt-4 vision-preview with gpt-4o we are running into a 431 Request Header Fields Too Large. When running the same POST agains openAI directly it works.
curl --location 'https://.../openai/deployments/gpt-4o/chat/completions?api-version=2024-06-01'
--header 'Content-Type: application/json'
--header 'api-key: 42...'
--data '{
    "messages": [
        {
            "role": "system",
            "content": "You are a helpful assistant."
        },
        {
            "role": "user",
            "content": [
	            {
	                "type": "text",
	                "text": "Describe this picture:"
	            },
	            {
	                "type": "image_url",
	                "image_url": {
                        "url": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAABQAAAAKUCAIAAADU1gJ7A...
                        aP89xM/oSDR3/CuINP8f4ZKVUxiyAcEAAAAASUVORK5CYII="
                    }
                }
           ]
        }
    ],
    "max_tokens": 100,
    "stream": false
}'

Hey @krohm, I have added a test for image requests and was not able reproduce your issue. Are you using the latest version of PowerProxy and its dependencies?

As discussed/evaluated, the issue is related to App Service. Not investigating further as you are migrating to Container Apps.

Hey @timoklimmer - we're experiencing same issue on CA behind AGW - any pointers before we start nuking AGW policies?

@timoklimmer we have modified an cloned powerproxy.px with this line (thanks @brettnf):
filter headers to only include those that are relevant for the request to AOAI
headers = {key: headers[key] for key in headers if key.lower() in ["api-key", "authorization", "content-type", "accept", "accept-encoding", "user-agent", "cache-control"]}

First Tests are ok, what do you think pushing this into main branch ?

Good catch, @codylittle and thanks a lot for the code, @krohm, @brettnf. Sending krohm's problem request incl. 10++ headers still works for me, but I do see a benefit in being able to filter headers. Need to think about it how we can make this as comfortable as possible - given that the set of headers required by AOAI will change over time.

@timoklimmer - from running a quick echo server through AGW, below headers were added.
My recommendation would be to not include any headers that start with x-
    "x-appgw-trace-id": "",
    "x-forwarded-for": "",
    "x-forwarded-host": "",
    "x-forwarded-port": "80",
    "x-forwarded-proto": "http, https",
    "x-original-host": "",
    "x-original-url": "/api/echo",
    "x-middleware-invoke": "",
    "x-invoke-path": "",
    "x-invoke-query": "",
    "x-invoke-output": "/api/echo"

I am thinking of adding an optional configuration setting under aoai named "forward_http_header_only_if_matches_regex". If the name of the incoming header matches the regex, the header would be forwarded to AOAI, else not.
For example:
a. to have all headers forwarded: .*
b. to have all x- headers removed: (?!x-)
c. to have all x-headers removed except x-abc: ((?!x-)|x-abc)
Default would be .* to avoid introducing breaking changes, but if deployments like yours need header filtering, it would be possible without having to adjust the source code.
@codylittle @krohm @brettnf What do you think?

[heart]         Michael Kroh reacted to your message:

From: Timo Klimmer @.>
Sent: Thursday, October 17, 2024 5:52:29 PM
To: timoklimmer/powerproxy-aoai @.>
Cc: Michael Kroh @.>; Mention @.>
Subject: [EXT] Re: [timoklimmer/powerproxy-aoai] gpt-4o with Images throws a 431 Request Header Fields Too Large (Issue #117)
Done and available in the lastest release (v0.13.0).
—
Reply to this email directly, view it on GitHubhttps://github.com/timoklimmer/powerproxy-aoai/issues/117#issuecomment-2420148546, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACCSZEKNMRONI2HQIRHE6O3Z372N3AVCNFSM6AAAAABOYIFY3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRQGE2DQNJUGY.
You are receiving this because you were mentioned.Message ID: @.***>

Hey @timoklimmer - can confirm this resolved the issue when removing the x- headers. Cheers for getting this rolled in so quickly. Just noting, in the config example you referenced 403 rather than 431

Ooops, thanks for the hint. I will correct that.


Filesystem Index

Is your feature request related to a problem? Please describe.

It is difficult to navigate the contents of the filesystem in a performant way.
It is also difficult to reference files in the filesystem in an immutable way.

Describe the solution you'd like
A stream that stores StorageAttributes cache essentially. This will allow browsing, searching, and interacting in a way that can decorate the filesystem.
Describe alternatives you've considered
Using the filesystem directly w/cache even is not ideal due to sorting options and complex filtering and search operations.
Additional context
Required for files module type feature parity.

Duplicate: https://github.com/laravel-streams/streams/issues/121


Simplifying bootstrapping with clean data representation

I would like to make a small suggestion that may help to simplify lr_gen.pl.
The idea is to reconsider how the rules in prolog_grammar.pl are represented.
Currently, you are using Prolog clauses to state the rules. This certainly seems straight-forward, but has a major disadvantage: The Prolog representation of clauses is called defaulty, as opposed to clean. This is the reason why you need so many !/0 to reason about these clauses.
The key insight to achieving a clean representation is to be aware that we have a lot of freedom in how we could represent the exact same rules instead.
For example, consider the following fragment of the rules:

term(N) :- subterm('<'(N)), op(N, xf), subterm('<'(N)).
term(N) :- subterm(N), op(N, yf).

We could also represent this as:

term(N) :- [subterm('<'(N)), op(N, xf), subterm('<'(N))].
term(N) :- [subterm(N), op(N, yf)].

In the above, I have used lists to get rid of the defaultiness at the outermost layer. Now, these rules are of the form:

Head :- List.

and we can easily process the body with maplist/3 and related predicates. Importantly, we can now symbolically distinguish the empty list [] from a list with at least one element [E|_].
Second, we can apply the same idea to get rid of the defaultiness at the inner layer, using for example:

meta(R) for a rule R that is to be interpreted at the meta-level
nt(R) for a rule R that is a nonterminal of the actual grammar.

For example, it could look like this:

term(N) :- [nt(subterm('<'(N))), meta(op(N, xf)), nt(subterm('<'(N)))].
term(N) :- [nt(subterm(N)), meta(op(N, yf))].

I am not saying that this is correct for this particular example, but I am giving this as one case where it could make sense to symbolically distinguish between two different kinds of rules by supplying suitable wrappers.
This will allow you to process the whole grammar more easily, relying on pattern matching to distinguish the different cases. You can use any number of additional wrappers at your discretion to introduce additional categories of elements.
Of course, the result will no longer be directly executable in Prolog, but you can easily run it with a meta-interpreter.

Hi Markus,
Thanks for your suggestions but I'm rewriting the grammar. It's impossible to get a clean LALR(1) parser from the published grammar.  And don't focus too much on lr_gen. It's purpose is to produce C++ code that will be plugged into the parser.
You'll see more of it in my next commit. Interesting that you're following my repo.
Thanks,
Datavetaren

1 juli 2017 kl. 13:13 skrev Markus Triska<EMAIL_ADDRESS>I would like to make a small suggestion that may help to simplify lr_gen.pl.
The idea is to reconsider how the rules in prolog_grammar.pl are represented.
Currently, you are using Prolog clauses to state the rules. This certainly seems straight-forward, but has a major disadvantage: The Prolog representation of clauses is called defaulty, as opposed to clean. This is the reason why you need so many !/0 to reason about these clauses.
The key insight to achieving a clean representation is to be aware that we have a lot of freedom in how we could represent the exact same rules instead.
For example, consider the following fragment of the rules:
term(N) :- subterm('<'(N)), op(N, xf), subterm('<'(N)).
term(N) :- subterm(N), op(N, yf).
We could also represent this as:
term(N) :- [subterm('<'(N)), op(N, xf), subterm('<'(N))].
term(N) :- [subterm(N), op(N, yf)].
In the above, I have used lists to get rid of the defaultiness at the outermost layer. Now, these rules are of the form:
Head :- List.
and we can easily process the body with maplist/3 and related predicates. Importantly, we can now symbolically distinguish the empty list [] from a list with at least one element [E|_].
Second, we can apply the same idea to get rid of the defaultiness at the inner layer, using for example:
meta(R) for a rule R that is to be interpreted at the meta-level
nt(R) for a rule R that is a nonterminal of the actual grammar.
For example, it could look like this:
term(N) :- [nt(subterm('<'(N))), meta(op(N, xf)), nt(subterm('<'(N)))].
term(N) :- [nt(subterm(N)), meta(op(N, yf))].
I am not saying that this is correct for this particular example, but I am giving this as one case where it could make sense to symbolically distinguish between two different kinds of rules by supplying suitable wrappers.
This will allow you to process the whole grammar more easily, relying on pattern matching to distinguish the different cases. You can use any number of additional wrappers at your discretion to introduce additional categories of elements.
Of course, the result will no longer be directly executable in Prolog, but you can easily run it with a meta-interpreter.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Support for _NET_WM_CM_Sn

I took a look at the code and it's very well written and easy to understand, so thanks for this.
I looked at the Atoms and you have 2 TODOs there that are interesting
https://github.com/arminfriedl/xcb-wm/blob/f61f0b4b2fd4e0a7fae19e283bba3ceff2151c23/src/ewmh/atoms.rs#L3
and
https://github.com/arminfriedl/xcb-wm/blob/f61f0b4b2fd4e0a7fae19e283bba3ceff2151c23/src/ewmh/atoms.rs#L97
So these two seem a bit conflicting I was wondering if there was a way to do both?
I say they are conflicting because the xcb::atoms_struct is a macro and would consider every field as a single atom.
But to use _NET_WM_CM_Sn you would need an array of atoms, so this would not be easily included in the macro struct.
I was wondering if you have any thoughts on this?

Thank you, that's very kind! Some parts could still use quite some love unfortunately (particularly the macros :cold_sweat:).
The reason I wanted to explore the xcb::atom_struct!{} is because it basically does what I'm doing (quite manually) in the atoms.rs. I think there's a chance we could remove quite some code there and make it more readable by just using the atom_struct!{}.
Regarding the _NET_WM_CM_Sn: This is indeed the most complicated atom because it is dynamic (depends on the number of screens). However, be aware that at the end of the day - for X11 - this is not an array. The atoms that need to be interned are e.g. _NET_WM_CM_S0, _NET_WM_CM_S1, _NET_WM_CM_S2, etc.
I feel like we will need to handle  _NET_WM_CM_Sn in a special way. That's also what  lbxcb-wm (the C implementation of xcb-wm) ended up doing. I'm open for better solutions, but I think adding the static atoms via xcb::atom_struct!{} (if possible) and then dynamically adding the _NET_WM_CM_Sn afterwards would be a good way to go here.


Remove version: dukus.digiCamControl version <IP_ADDRESS>

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: URL works;


Consider model ranking

It would be nice to have explicit model ranking for selection. I.e., something that answers the question of which is the "best" model between a group of trained models without human-eyeballing (of course human eye-balling is also great!). This would be in addition to Pareto-based selection, not a replacement for Pareto-based selection.
Consider Caruana et al. 2004 "b" - https://dl.acm.org/doi/10.1145/1046456.1046470.
I have a prototype here: https://jphall663.github.io/GWU_rml/, code: https://nbviewer.org/github/jphall663/GWU_rml/blob/master/assignments/eval.ipynb.
In addition to prototype, would be really cool for users to be able to:

select the number and type of assessments, e.g., 3 assessments: AUC, max. ACC, and AIR (gets at balancing real-world selection criteria)
for users to choose between random folds and user-selected segments (gets at weakspots and robustness)
for users to be able to perturb folds or data segments (gets at robustness)

(The current prototype is fixed at 5 folds, fixed with five quality assessment stats (no AIR, etc.), and does not perturb folds.)
Let me know if you'd like to discuss.

That makes sense. We may provide an enhanced leaderboard panel that adopts the model ranking and segmented metrics in future releases.


Issuer validation

Hi
With the update to the packages I noticed that issuer validation is being enforced differently, previously I didnt have to put in a Valid issuer or anything in the AddOpenIdConnect defaults now I have to, here's some sample code to demo it, below is what I have to do now
services.AddAuthentication(CookieAuthenticationDefaults.AuthenticationScheme)
        .AddCookie("Cookies", options =>
        {
            options.Cookie.Name = "mycookie";
            options.Cookie.SameSite = SameSiteMode.None;

        })
        .AddOpenIdConnect(options =>
        {
            options.ClientId = "__invalid"; // Needed for validation, will be overwritten per-tenant.
            options.Authority = "https://__invalid"; // Needed for validation, will be overwritten per-tenant.
            options.Prompt = "login consent"; // For sample purposes.
            options.ResponseType = "code";
            options.RequireHttpsMetadata = false;//remove when switch to https
            options.GetClaimsFromUserInfoEndpoint = true;
            options.ClaimActions.MapAll();
            options.ClaimActions.Add(new RoleClaimAction());
            options.TokenValidationParameters.ValidIssuers= new List<string>() {"https:/myissuer.dev.com", "http://myissuer2.dev.com/" };

        });

and before
services.AddAuthentication(CookieAuthenticationDefaults.AuthenticationScheme)
        .AddCookie("Cookies", options =>
        {
            options.Cookie.Name = "mycookie";
            options.Cookie.SameSite = SameSiteMode.None;

        })
        .AddOpenIdConnect(options =>
        {
            options.ClientId = "__invalid"; // Needed for validation, will be overwritten per-tenant.
            options.Authority = "https://__invalid"; // Needed for validation, will be overwritten per-tenant.
            options.Prompt = "login consent"; // For sample purposes.
            options.ResponseType = "code";
            options.RequireHttpsMetadata = false;//remove when switch to https
            options.GetClaimsFromUserInfoEndpoint = true;
            options.ClaimActions.MapAll();
            options.ClaimActions.Add(new RoleClaimAction());

        });

Is there a way that hasnt been documented to have per tenant issuer validation or not and if not I'd suggest this might be worth a look into?

Hi can you please post the error message? I’ve checked OpenIdConnectOptions and they don’t have this validation. I will check a few more places in the aspnetcore source code.

Hi Andrew
Sorry for the slow reply, see below
Main Error:
An unhandled exception occurred while processing the request.
SecurityTokenInvalidIssuerException: IDX10205: Issuer validation failed. Issuer: '<removed for security>'. Did not match: validationParameters.ValidIssuer: 'null' or validationParameters.ValidIssuers: 'null' or validationParameters.ConfigurationManager.CurrentConfiguration.Issuer: 'localhost:5000'. For more details, see https://aka.ms/IdentityModel/issuer-validation.
Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.ValidateTokenUsingHandlerAsync(string idToken, AuthenticationProperties properties, TokenValidationParameters validationParameters)

AuthenticationFailureException: An error was encountered while handling the remote login.
Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler<TOptions>.HandleRequestAsync()

Stack:
Microsoft.IdentityModel.Tokens.SecurityTokenInvalidIssuerException: IDX10205: Issuer validation failed. Issuer: '<removed for security>'. Did not match: validationParameters.ValidIssuer: 'null' or validationParameters.ValidIssuers: 'null' or validationParameters.ConfigurationManager.CurrentConfiguration.Issuer: 'localhost:5000'. For more details, see https://aka.ms/IdentityModel/issuer-validation.
   at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.ValidateTokenUsingHandlerAsync(String idToken, AuthenticationProperties properties, TokenValidationParameters validationParameters)
   at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleRemoteAuthenticateAsync()

Hope that helps

Ok I found that it was this commit that added this:
https://github.com/dotnet/aspnetcore/commit/a56e968c19be1275db6dc462310d723615b006a7
Per tenant issuer should be possible. You would just use per-tenant options for OpenIdConnectOptions and override that property for the options class using something on the tenant info. Likely you'd want to add a specific  property to your tenant info type to store that. I will add a convention to the per-tenant authentication functionality that will look for a property with that name and use it by convention.

Also I’ll add that in most of my dev and samples I disable issuer validation so I wouldn’t have seen this for a while. Thanks for bringing it to the community’s attention.


Clear the Alarm

Is there any way that can clear the alarm
Python code will not work unless resetting the Dobot Magician's current alarm
I don't think this library built-in with Alarm commands yet.
Thanks in advance

I have implemented reading alarms in my fork, see https://github.com/ZdenekM/pydobot/blob/master/pydobot/dobot.py. There are get_alarms and clear_alarms.

I have implemented reading alarms in my fork, see https://github.com/ZdenekM/pydobot/blob/master/pydobot/dobot.py. There are get_alarms and clear_alarms.

ZdenekM, many thanks, I took a quick check in your fork. That alarm was quite helpful. I decided to download your code, used your example code and I get the result something like this, care to explain why I am getting this error message that the 'mode' isn't defined?

%Run Example.py
Pose(position=Position(x=10.184884071350098, y=177.5911865234375, z=4.0564422607421875, r=86.7176742553711), joints=Joints(j1=86.7176742553711, j2=14.331169128417969, j3=59.5638313293457, j4=0.0))
Traceback (most recent call last):
File "/home/pi/Desktop/OtherPyDobot/pydobot-master/alarm.py", line 12, in
device.move_to(position.x + 20, position.y, position.z, position.r, wait=False)
File "/home/pi/Desktop/OtherPyDobot/pydobot-master/pydobot/dobot.py", line 589, in move_to
return self._extract_cmd_index(self._set_ptp_cmd(x, y, z, r, mode))
NameError: name 'mode' is not defined

@SForney54 Which example code do you mean? I probably haven't touched https://github.com/ZdenekM/pydobot/blob/master/examples/basic.py at all. Try removing wait=False.

Hi, could this feature be merged to the main repo. Looks like move commands get sent to Dobot like normal, but the Dobot doesn't move if there are alarms about some axis being too close to limit.

@jKostet Absolutely, that is the plan. I am helping luismesas with issues and maintenance and I would like to do a new release this month with some small improvements, like clearing the alarm and not crashing on empty messages (#44). Maybe this is the most straightforward thing to fix, so the next release could just include this.
I still need to look at @Sforney54's work myself. At this point in time I'm not sure whether the library should try to clear axis alarms itself to keep the arm moving, or if it should raise an exception and offer functionality to clear the alarm and retry the move. Sforney54 seem to clear the alarm in the constructor, i.e. clear alarms on connection to the robot. This is sensible, but what about during operations?

Not sure but looking at the hardware I don't see physical end switches on the Dobot, so I think it just relies on absolute encoders, + the servo having a fourth cable for reading position. Thus I'd assume the limits are fixed in firmware and it should be safe Dobot-wise to actively ignore the alarms, e.g. having some variable that can be set in init like device.ignoreAlarms = true. Though this would then lead to the Dobot moving to unexpected positions environment-wise if a single move in a sequence of moves is not completed. Soo guess the expection + way to continue sequence after that would be best.

Apologies for jumping into this existing thread, after the fact. @ZdenekM I noticed that the command id for get_alarms and clear_alarms are both 20, yet the documentation, API and comms protocol for Dobot split them so that clear_alarms is 21. Is there a reason for your code using 20 for both? (PS I'm using Gustafsson's dobot-python repo, but the comms process is the same)


Add messages to stream sensor data

This PR adds a new message SensorData, which can used by APIs to send and receive data originating from sensors. Such data samples will contain the metric and the value reported by the sensor, and will also contain a state to inform the system if a sensor is in an error state or not.

@thomas-nicolai-frequenz ready for a look

Rebased on top of v0.x.x.


Support Symfony 6

Feature request
Now that Symfony6 is out, it should be supported.

Already tracked by #6095.


Refer to xDai instead of ETH if in mainnet

Summary
Currently printed text on logs refers always to ETH, even if mainnet where the coin is xDai instead. Update printed texts.
Example:
time="2022-01-09T18:40:10Z" level=warning msg="cannot continue until there is sufficient ETH (for Gas) and at least 1 BZZ available on xxxxxxxxxxxx"
Expected behavior
Each net should call its main coin properly.
Actual behavior
It's always cited ETH.
Possible solution
A dictionary with Net->CoinName should be kept as a coin name source by text printers.

thanks @tmm360. I believe that xDai is officially called Gnosis chain now, and I'm not sure what the native token will be, I guess GNO. Let's follow up on this once their transition is done, and we can sweep through the codebase and do the appropriate cleanups

@acud Correct, it's Gnosis Chain, but main coin is still xDai. It is a bridge on stablecoin Dai, so no clue that is will go to change name. Anyway, the dictionary is easy to update at any moment the coin should change name in future, if it will.

.

I don't agree. To explicit quote the token name remove any ambiguity. Important when some one is using bee for the first time. It's a very very simple implementation.

Instead of naming token variables by it's symbol names, bee client can use network agnostic term in order to be flexible.

There is clearly a usability issue here and the solution is not necessary more flexibility, but rather some added clarity. I think it makes sense to internally keep track of the context if it is about native token or swarm token, however when communicating with the user it would be better to resolve it to the actual token name.


Add SmartWallet by @novinfard

[x] Project URL:
[x] Update contents.json instead of README
[x] One project per pull request
[x] Avoid iOS or open-source in description as it is assumed
[x] Use this commit title format if applicable: Add app-name by @github-username
[x] Use approved format for your entry

I changed it as you described. Appstore URL is working now

@novinfard thank you!


Created a docker-compose file and fixed the Dockerfile to work with it

This PR adds | fixes:

Fix #22

How to test:

Run docker-compose up
Go to http://<IP_ADDRESS>:7000/

Expected outcome:

[ ] The up should be up and running

Review:

[x] Tests executed by CR

This version is a:

[ ] MAJOR - when you make incompatible API changes
[x] MINOR - when you add functionality in a backwards compatible manner
[ ] PATCH - when you make backwards compatible bug fixes or documentation/instructions

Codecov Report

Merging #26 (504dfb0) into main (db25514) will increase coverage by 1.78%.
The diff coverage is 96.49%.

@@            Coverage Diff             @@
##             main      #26      +/-   ##
==========================================
+ Coverage   93.86%   95.65%   +1.78%
==========================================
  Files           7        8       +1
  Lines         163      207      +44
==========================================
+ Hits          153      198      +45
+ Misses         10        9       -1

Flag
Coverage Δ

unittests
95.65% <96.49%> (+1.78%)
:arrow_up:

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

Impacted Files
Coverage Δ

preClinVar/csv_parser.py
97.97% <92.30%> (ø)

preClinVar/main.py
89.09% <95.65%> (+5.30%)
:arrow_up:

preClinVar/build.py
100.00% <100.00%> (ø)

preClinVar/constants.py
100.00% <100.00%> (+100.00%)
:arrow_up:

preClinVar/demo/__init__.py
100.00% <100.00%> (ø)

tests/test_main.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Tested OK 👍🏻


User guide translations

Description
Professional translators will adapt the ODE user guide to Spanish, Portuguese and French.
Note: the docs translation will need to include https://starlight.astro.build/guides/i18n/
@sapetti9: I know you are handling this, but I also assign this to myself and @roll for the implementation part.

Let me know once the guides are ready to be translated, so I can export them to text files and send them to the translators.

There aren't any translations in the current state of the main branch left to sync for now.


React-Native support?

Re-opening this issue as it is not supporting on react-native.
After importing import filter from 'filter-object'; ,
I'm getting below error
 Module 'util' does not exist in the haste module map

util is a built-in node module. If it's not found, then you'll need to configure your bundler (whatever builds your react-native app) to use or polyfill built-in node modules.


SLD to FeatureStyle?

Hi, currently QGIS will store styles as SLD in a table called "layer_styles" in a geopackage. Is there a way to transform these settings to FeatureStyles?

As far as I know, QGIS is utilizing this extension: https://github.com/pka/qgpkg/blob/master/qgis_geopackage_extension.md
We currently do not implement that extension, but would welcome a pull request which implements it.  That extension would have to be implemented, along with QML and SLD parsing to be able to translate the styles into the FeatureStyle extension.  This library works both in node and the browser which complicates this further.


AWS ECS cloudformation template fails after a few minutes and is rolled back

Add labels appropriate to the issue
Describe the expected behaviour and the actual behaviour
Describe steps to reproduce the problem

Expected behavior: use CF template to launch SockShop on ECS. SockShop will run until CF template is explicitly terminated.
Actual behavior: SockShop comes up and starts working, but then front-end container "did not stabilize" and entire CF template is rolled back.
Steps to reproduce: Deployed CF template to AWS Oregon region using 3x m4.large instances. Sock shop comes up. Ran load test container to send traffic to the sock-shop and can observe in Weave Cloud. Then SockShop disappears from Weave Cloud. Checking CF console shows the following error caused CF rollback:
14:19:46 UTC-0700   CREATE_FAILED   AWS::ECS::Service   FrontEndService Service arn:aws:ecs:us-west-2:376248598259:service/sockshop-ecs-FrontEndService-17JH4G3K9KWBM did not stabilize.

Can not reproduce this; the ecs deployment test works fine at the moment. It could be caused by this problem that we fixed. https://github.com/microservices-demo/front-end/commit/d715e7adeaae5a713d3984ce41e569608a1b1bbe


getting not found "shape_predictor_68_face_landmarks.dat"

I've installed the nuget package as mentioned the wiki
https://github.com/takuya-takeuchi/FaceRecognitionDotNet/wiki
I'm getting the error while create instance. I just created the folder c:\models and don't added anything in the models folder.
May I know how to solve the issue or what are the files need to add in the models directory

Please check the following instructions.
https://github.com/takuya-takeuchi/FaceRecognitionDotNet/wiki/Quickstart#deploy-model-files

thanks


SDL2_mixer: add opusfile dependency for opus support

Motivation for this change
SDL2's opus sound features are now usable by library users. New packages may depend on this support.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
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 nix-review --run "nix-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.

Notify maintainers
cc @MP2E

@GrahamcOfBorg build SDL2_mixer


CVE-2007-4559 Patch

Patching CVE-2007-4559
Hi, we are security researchers from the Advanced Research Center at Trellix. We have began a campaign to patch a widespread bug named CVE-2007-4559. CVE-2007-4559 is a 15 year old bug in the Python tarfile package. By using extract() or extractall() on a tarfile object without sanitizing input, a maliciously crafted .tar file could perform a directory path traversal attack. We found at least one unsantized extractall() in your codebase and are providing a patch for you via pull request. The patch essentially checks to see if all tarfile members will be extracted safely and throws an exception otherwise. We encourage you to use this patch or your own solution to secure against CVE-2007-4559. Further technical information about the vulnerability can be found in this blog.
If you have further questions you may contact us through this projects lead researcher Kasimir Schulz.

The extraction indicated here is intended to be used with specific, controlled input paths and not arbitrary input paths. In light of that, I don't believe this is a high priority to address. This repository exists for archival purposes and is not actively maintained or operational code.


Remove Current User Vote Info for Homepage - BE

@calvinhlee23  Same here.. Is this ticket still legit and OS eligible? If so, can you provide some context?


Problem with &

Hello guys,
I'm having problems when the xlm contains the character ' & ' . I did some testing by changing the character with other and it worked.
Could you help me fix this problem?
hugs,

RSS parsing error!
Failed to save to data store: The operation couldn’t be completed. (NSXMLParserErrorDomain error 23.)
NSLocalizedDescription = "The operation couldn\U2019t be completed. (NSXMLParserErrorDomain error 23.)"


PDM can't load the plugin

% pdm sbom -h
WARNING: Failed to load plugin pdm-sbom=pdm_sbom:main: No module named 'packageurl'
Usage: pdm [-h] [-V] [-c CONFIG] [-v | -q] [-I] [--pep582 [SHELL]] ...
pdm: error: Script unknown: sbom

Looks like it's an issue with your entry point, which doesn't exist?

The entrypoint exists.
I have found the issue.
To minimize the dependency tree, the parts have been moved to extras. PURL were only used in SPDX and CycloneDX so far, but have now emerged to the core model.
As a workaround, I would suggest to use pdm-sbom[spdx] or pdm-sbom[cyclonedx] for installation.
I will provide an update in the course of the week.

Sorry for the late reply. New Version is published, I uploaded the fix, but did Not publish the wheel.
Should Work now


New package: RelocatableFolders v0.1.0

Registering package: RelocatableFolders
Repository: https://github.com/MichaelHatherly/RelocatableFolders.jl
Created by: @MichaelHatherly
Version: v0.1.0
Commit: 80848a06ed7da2c535c0354285e939b12705e33c
Reviewed by: @MichaelHatherly
Reference: https://github.com/MichaelHatherly/RelocatableFolders.jl/commit/80848a06ed7da2c535c0354285e939b12705e33c#commitcomment-52135129

@MichaelHatherly you've registered the fork MichaelHatherly/RelocatableFolders.jl and not what appears to be the upstream repository JuliaPackaging/RelocatableFolders.jl.  Was it done on purpose?
[noblock]

It used to be the main repo, @staticfloat helped move it across the JuliaPackaging yesterday, so we just need to update the URL here I guess to point to the right place.

Try to retrigger registration in https://github.com/JuliaPackaging/RelocatableFolders.jl/commit/80848a06ed7da2c535c0354285e939b12705e33c
[noblock]

Looks to have worked, thanks.
[noblock]


Question about Mediapipe pose estimation for better FPS

Hello everyone,
We are looking to implement the Mediapipe pose estimation model into an Android device. Is it better to use the pose estimation from the Google ML Kit (base/accurate) or rather to grab the tflite model for blazepose 3d ghum?
We are currently using the ML Kit on device pose estimation (base model) but running into a problem with the device only running at 2-3 FPS so we are now looking into further acceleration (XNNPack) in hopes of running with a higher performance. Is it better to use pose_landmark_lite.tflite in this type of situation? Or can XNNPack be directly applied to the ML Kit SDK? Or is there any other type of acceleration that we should be considering? Thanks.

Hi @richardhfj, You can understand it from here https://github.com/google/mediapipe/issues/1160#issuecomment-872706753


I want to add support for a neuro accelerator

Hi.
I want to add to tf support for its own neural gas pedal like CUDA, how difficult is it to implement such a thing?

@Muzantip ,
Can you please elaborate about your Feature that supports your statement. Also, please specify the Use Cases for this feature. Thanks!


cmd/compile: prefer AND instead of SHR+SHL

In cl/19485 we added a generic SSA rule to replace an AND with specific constants by two SHIFT instructions.
While this optimization does avoid a load of the constant to be ANDed into an extra register and has a shorter encoding on amd64 it does use two data dependent instructions. There was already some discussion on the CL after accidental early submission that micro benchmarks do not show using two shifts to be faster. Some seem to show it can be slower e.g. x &= 1 << 63. I benchmarked math.Copysign and it showed the same throughput using either variant. LLVM and GCC do not seem to replace AND with SHIFTs on amd64 either and some platforms like arm64 in the go gc compiler even reverse this rewrite.
https://go.googlesource.com/go/+/06f709a04acc6d5ba0ba181129e9ee93ed20f311/src/cmd/compile/internal/ssa/gen/ARM64.rules#1866
There has also been some unwanted interaction with other optimizations rules e.g. #32781.
The initial added rules from cl/19485 operated on And64 and And32. The And32 case was already removed in cl/20410 .
Removing the And64 case too can make binaries slightly larger but in common cases where there is no register pressure should be as fast or faster as two SHIFTs on modern amd64 CPUs and should create less interference with other SSA rules that need not consider the additional case of a mask using AND having been rewritten to SHIFTs.
I intend to send CLs for evaluation and submission to remove the generic rule to rewrite AND into a pair of SHIFTs for go1.14 and follow up with some CLs that avoid regressing on interaction with other rules that are based on optimizing SHIFTs instead of ANDs. For example the AND instruction in (u64>>32)&0xFFFFFFFF should still be optimized away by SSA.
This issue is to document the related CLs and discuss this (de)optimization and whether any go gc supported 64bit platforms should keep rewriting some ANDs to two SHIFTs.
/cc @klauspost @cherrymui @khr @dr2chase @laboger @mundaym

Looking at instruction timing it should be pretty much the same.
I am not saying that this is a bad change, just that I don't think this benchmark is accurate if it is emitting what you write.
func BenchmarkAndHighBits(b *testing.B) {
	x := uint(0)
	for i := 0; i < b.N; i++ {
		x &= 1 << 63
	}
	GlobalU = x
}

Is  MOVQ $0x8000000000000000, RAX actually inside the loop? And wouldn't it emit ANDQ  $0x8000000000000000, REG?
On Ivy Bridge (your CPU) and pretty much all other CPUs, the instructions involved are all with a 1 cycle latency. Since your benchmark is serial, it should pretty much be the same assuming it is emitting MOVQ+ANDQ. If it is only ANDQ, it should be 2x faster (excluding the loop overhead).
It could also be that Ive Bridge is able to do some magic and can ignore the MOVQ.
Either way; with the AND, the compiler will be able to do some optimizations. A clever compiler could even move the constant loading outside the loop, as mentioned above.

Looking at instruction timing it should be pretty much the same.

I would agree if viewed standalone. If there is surrounding code like in the benchmark loop I would expect the MOV being able to be issued in parallel ahead with some earlier instruction (unless the CPU is saturated with 4 retires per cycle already). The two shifts together always need at least 2 cycles after their input is ready from a previous loop iteration.

Is MOVQ $0x8000000000000000, RAX actually inside the loop?
I have not rechecked but I think that is what I saw. That a MOV is needed should only be clear very late - in the arch specific SSA (see why below). I do not think there is loop hoisting pass run after that stage.

And wouldn't it emit ANDQ $0x8000000000000000, REG?
AND does not support 64bit immediates https://www.felixcloutier.com/x86/and .

Yeah, the CPU is doing magic.
A simple test, pure assembler:
TEXT ·testAnd(SB), NOSPLIT, $0
	MOVQ $65535, CX
	XORQ AX, AX

loop_and:
	MOVQ $0x8000000000000000, BX
	ANDQ BX, AX
	DECQ CX
	JNZ  loop_and
	RET

TEXT ·testShift(SB), NOSPLIT, $0
	MOVQ $65535, CX
	XORQ AX, AX

loop_shift:
	SHRQ $63, AX
	SHLQ $63, AX
	DECQ CX
	JNZ  loop_shift
	RET

Using AND is ~2x as fast on my Ryzen 3600. Moving the MOVQ outside the loop makes absolutely no difference, which indicates the magic :)

The first attempt broke codegen tests in arm64 (bfxil) and s390x (abs and copysign).
https://build.golang.org/log/a47a1c98bac2aa509d570d6bf583609857b1be5a
https://build.golang.org/log/6456da8a84cc82e7407981287f211caaab41c7eb
Will make sure to run codegen tests for all platforms for the new version of the CL.
For a new version of the CL I added abs and copysign rules that need detect the new AND variant, still working on the arm64 bitfield adjustment.

Anything else need to be done here?

The feature is in at the 3rd try and AFAIK did not cause any new breakages since then.
There is some cleanups that can be done. e.g. adding codegen tests that the old shift based rules are exercised and tested or just remove the old rules. However I wont likely get to that and test them across the different architectures due to other feature CLs before go1.14. Therefore closing this issue as the desired generate of code itself is in for go1.14.


Corrections and additions to core-operators asciidoc

If anyone has suggestions on a better organization of the overloadable operators table, let me know and I'll make the changes.

+1

Thanks! :+1:


Add a "changelog_skip" default ignored label

similar to 'wontfix' but analogous to the [ci skip] tag that travis allows.

Lets merge discussion of this label-support feature with #284.


Center Remote Content

The main Remote screen should be centered on the page.
I also added some flair to the "waiting for question" default that animates the ellipsis to be "loading"

Fixed in #54


🐛 [cloud_firestore] Firestore data is read on iOS but not on Android

Bug report
I have a strange behavior in a Flutter app that I am currently developing.
On iOS, everything works fine, the data from Firestore is displayed.
On Android, the data is loaded in the first view of the app, then when I navigate in other views, it displays this error, sometimes instantly, sometimes after a long loading:
I/flutter ( 4938): ----------------FIREBASE CRASHLYTICS----------------
I/flutter ( 4938): [cloud_firestore/unavailable] The service is currently unavailable. This is a most likely a transient condition and may be corrected by retrying with a backoff.
I/flutter ( 4938): #0      StandardMethodCodec.decodeEnvelope
package:flutter/…/services/message_codecs.dart:607
I/flutter ( 4938): #1      MethodChannel._invokeMethod
package:flutter/…/services/platform_channel.dart:167
I/flutter ( 4938): <asynchronous suspension>
I/flutter ( 4938): #2      MethodChannel.invokeMapMethod
package:flutter/…/services/platform_channel.dart:367
I/flutter ( 4938): <asynchronous suspension>
I/flutter ( 4938): #3      MethodChannelDocumentReference.get
package:cloud_firestore_platform_interface/…/method_channel/method_channel_document_reference.dart:68
I/flutter ( 4938): <asynchronous suspension>
I/flutter ( 4938): #4      _JsonDocumentReference.get
package:cloud_firestore/src/document_reference.dart:146
I/flutter ( 4938): <asynchronous suspension>
I/flutter ( 4938): #5      _FutureProviderElementMixin._listenFuture.<anonymous closure>
package:riverpod/src/future_provider.dart:95
3
W/Firestore( 4938): (24.1.2) [WatchStream]: (88291dc) Stream closed with status: Status{code=RESOURCE_EXHAUSTED, description=Resource has been exhausted (e.g. check quota)., cause=null}.

Of course, despite of the resource exhaust mentioned, it is certainly not the problem because the project is in Blaze plan, and it works fine on iOS.
The data is listened like this:

class CodeListPage extends ConsumerWidget {
  const CodeListPage({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    final codes = ref.watch(codeListProvider);

    return codes.whenData(data) {
        // useless code
    });
  }
}

final codeListProvider = StreamProvider<List<Code>>((ref) {
  final repository = ref.watch(codeRepositoryProvider);
  return repository.stream();
});

final codeRepositoryProvider = Provider<CodeRepository>((ref) {
  final service = ref.watch(firestoreServiceProvider);
  return CodeRepository(service);
});

class CodeRepository {
  CodeRepository(this._service);

  final FirestoreService _service;

  final _codeRef = FirebaseFirestore.instance
      .collection(FirestorePath.codes)
      .withConverter<Code>(
        fromFirestore: (snapshot, _) => Code.fromJson(snapshot.data()!),
        toFirestore: (code, _) => code.toJson(),
      );

  Stream<List<Code>> stream() {
    return _service.streamDocuments(
      _codeRef.where("etat", isEqualTo: "VIGUEUR"),
    );
  }
}

final firestoreServiceProvider =
    Provider<FirestoreService>((ref) => FirestoreService.instance);

class FirestoreService {
  FirestoreService._();
  static final instance = FirestoreService._();
  static final firestore = FirebaseFirestore.instance;

  Stream<List<T>> streamDocuments<T>(Query<T> query) {
    return query.snapshots().map((snapshot) {
      return snapshot.docs.map((snapshot) => snapshot.data()).toList();
    });
  }
}

Flutter dependencies
Click To Expand
Dart SDK 2.17.1
Flutter SDK 3.0.1
mcj 7.0.0+5

dependencies:
- cloud_firestore 3.1.16 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cloud_functions 3.2.15 [cloud_functions_platform_interface cloud_functions_web firebase_core firebase_core_platform_interface flutter]
- cupertino_icons 1.0.4
- dio 4.0.6 [http_parser path]
- elastic_app_search 0.2.1 [flutter dio freezed_annotation html_unescape]
- extensions 0.2.4 [flutter flutter_riverpod intl]
- firebase_analytics 9.1.8 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_auth 3.3.18 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_auth_web 3.3.15 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core 1.17.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 2.8.0 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_storage 10.2.16 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
- firestore_service 0.2.0 [flutter json_annotation]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math]
- flutter_riverpod 1.0.3 [collection flutter meta riverpod state_notifier]
- freezed_annotation 1.1.0 [collection json_annotation meta]
- html_unescape 2.0.0
- intl 0.17.0 [clock path]
- layout_builder 2.5.4 [flutter flutter_localizations extensions localization modal_bottom_sheet cached_network_image flutter_riverpod intl freezed_annotation numberpicker]
- modal_bottom_sheet 2.0.2-dev.3 [flutter]
- models 0.1.4 [flutter freezed_annotation]
- purchases 2.0.1 [flutter flutter_localizations extensions layout_builder localization purchases_flutter freezed_annotation flutter_riverpod intl url_launcher]
- quiver 3.1.0 [matcher]
- sign_in 5.10.0 [flutter flutter_localizations extensions firestore_service firebase_storage_service layout_builder localization modal_bottom_sheet cloud_firestore cloud_functions firebase_auth firebase_storage freezed_annotation flutter_libphonenumber flutter_login_facebook flutter_riverpod google_sign_in intl pinput the_apple_sign_in]
- url_launcher 6.1.2 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]

dev dependencies:
- build_runner 2.1.11 [args async analyzer build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style frontend_server_client glob graphs http_multi_server io js logging meta mime package_config path pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- flutter_launcher_icons 0.9.2 [args image path yaml]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph]
- freezed 1.1.1 [analyzer build build_config collection meta source_gen freezed_annotation]
- json_serializable 6.2.0 [analyzer async build build_config collection json_annotation meta path pub_semver pubspec_parse source_gen source_helper]
- lints 1.0.1

transitive dependencies:
- _fe_analyzer_shared 38.0.0 [meta]
- analyzer 3.4.1 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- archive 3.3.0 [crypto path]
- args 2.3.1
- async 2.8.2 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- build 2.3.0 [analyzer async convert crypto glob logging meta path]
- build_config 1.0.0 [checked_yaml json_annotation path pubspec_parse yaml]
- build_daemon 3.1.0 [built_collection built_value http_multi_server logging path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.0.8 [analyzer async build crypto graphs logging path package_config pool pub_semver stream_transform yaml]
- build_runner_core 7.2.3 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta path package_config pool timing watcher yaml]
- built_collection 5.1.1
- built_value 8.3.0 [built_collection collection fixnum meta]
- cached_network_image 3.2.0 [flutter flutter_cache_manager octo_image cached_network_image_platform_interface cached_network_image_web]
- cached_network_image_platform_interface 1.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.0.1 [flutter flutter_cache_manager cached_network_image_platform_interface]
- characters 1.2.0
- charcode 1.3.1
- checked_yaml 2.0.1 [json_annotation source_span yaml]
- clock 1.1.0
- cloud_firestore_platform_interface 5.5.6 [collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 2.6.15 [cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- cloud_functions_platform_interface 5.1.6 [firebase_core flutter meta plugin_platform_interface]
- cloud_functions_web 4.2.14 [cloud_functions_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- code_builder 4.1.0 [built_collection built_value collection matcher meta]
- collection 1.16.0
- convert 3.0.1 [typed_data]
- crypto 3.0.2 [typed_data]
- dart_style 2.2.3 [analyzer args path pub_semver source_span]
- fake_async 1.3.0 [clock collection]
- ffi 1.2.1
- file 6.1.2 [meta path]
- firebase_analytics_platform_interface 3.1.6 [firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.4.0+13 [firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_auth_platform_interface 6.2.6 [firebase_core flutter meta plugin_platform_interface]
- firebase_core_platform_interface 4.4.0 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.6.4 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.2.6 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_platform_interface 4.1.6 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_service 0.3.0 [flutter firebase_storage flutter_riverpod]
- firebase_storage_web 3.2.15 [async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
- fixnum 1.0.1
- flutter_blurhash 0.7.0 [flutter]
- flutter_cache_manager 3.3.0 [clock collection file flutter http path path_provider pedantic rxdart sqflite uuid]
- flutter_libphonenumber 1.1.0 [flutter]
- flutter_login_facebook 1.4.1 [flutter list_ext]
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta vector_math]
- frontend_server_client 2.1.3 [async path]
- glob 2.0.2 [async collection file path string_scanner]
- google_sign_in 5.3.1 [flutter google_sign_in_android google_sign_in_ios google_sign_in_platform_interface google_sign_in_web]
- google_sign_in_android 5.2.7 [flutter google_sign_in_platform_interface]
- google_sign_in_ios 5.3.1 [flutter google_sign_in_platform_interface]
- google_sign_in_platform_interface 2.1.3 [flutter quiver]
- google_sign_in_web 0.10.1+2 [flutter flutter_web_plugins google_sign_in_platform_interface js]
- graphs 2.1.0 [collection]
- http 0.13.4 [async http_parser meta path]
- http_multi_server 3.2.0 [async]
- http_parser 4.0.1 [collection source_span string_scanner typed_data]
- image 3.1.3 [archive meta xml]
- infinite_listview 1.1.0 [flutter]
- io 1.0.3 [meta path string_scanner]
- js 0.6.4
- json_annotation 4.5.0 [meta]
- list_ext 1.0.4 [quiver collection]
- localization 1.1.3 [flutter extensions flutter_riverpod]
- logging 1.0.2
- matcher 0.12.11 [stack_trace]
- material_color_utilities 0.1.4
- meta 1.7.0
- mime 1.0.2
- numberpicker 2.1.1 [flutter infinite_listview]
- octo_image 1.0.2 [flutter flutter_blurhash]
- package_config 2.0.2 [path]
- path 1.8.1
- path_provider 2.0.10 [flutter path_provider_android path_provider_ios path_provider_linux path_provider_macos path_provider_platform_interface path_provider_windows]
- path_provider_android 2.0.14 [flutter path_provider_platform_interface]
- path_provider_ios 2.0.9 [flutter path_provider_platform_interface]
- path_provider_linux 2.1.6 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_macos 2.0.6 [flutter path_provider_platform_interface]
- path_provider_platform_interface 2.0.4 [flutter platform plugin_platform_interface]
- path_provider_windows 2.0.6 [ffi flutter path path_provider_platform_interface win32]
- pedantic 1.11.1
- petitparser 4.4.0 [meta]
- pinput 2.2.9 [flutter smart_auth]
- platform 3.1.0
- plugin_platform_interface 2.1.2 [meta]
- pool 1.5.0 [async stack_trace]
- process 4.2.4 [file path platform]
- pub_semver 2.1.1 [collection meta]
- pubspec_parse 1.2.0 [checked_yaml collection json_annotation pub_semver yaml]
- purchases_flutter 3.10.0 [flutter freezed_annotation json_annotation]
- riverpod 1.0.3 [collection meta state_notifier]
- rxdart 0.27.3
- shelf 1.3.0 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 1.0.1 [shelf stream_channel web_socket_channel]
- sky_engine 0.0.99
- smart_auth 1.0.5 [flutter flutter_web_plugins]
- source_gen 1.2.2 [analyzer async build dart_style glob meta path source_span yaml]
- source_helper 1.3.2 [analyzer collection source_gen]
- source_span 1.8.2 [collection path term_glyph]
- sqflite 2.0.2+1 [flutter sqflite_common path]
- sqflite_common 2.2.1+1 [synchronized path meta]
- stack_trace 1.10.0 [path]
- state_notifier 0.7.2+1 [meta]
- stream_channel 2.1.0 [async]
- stream_transform 2.0.0
- string_scanner 1.1.0 [charcode source_span]
- synchronized 3.0.0+2
- term_glyph 1.2.0
- test_api 0.4.9 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- the_apple_sign_in 1.1.1 [flutter]
- timing 1.0.0 [json_annotation]
- typed_data 1.3.0 [collection]
- url_launcher_android 6.0.17 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.0.17 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.0.1 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.0.1 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.0.5 [flutter plugin_platform_interface]
- url_launcher_web 2.0.11 [flutter flutter_web_plugins url_launcher_platform_interface]
- url_launcher_windows 3.0.1 [flutter url_launcher_platform_interface]
- uuid 3.0.6 [crypto]
- vector_math 2.1.2
- watcher 1.0.1 [async path]
- web_socket_channel 2.2.0 [async crypto stream_channel]
- win32 2.5.2 [ffi]
- xdg_directories 0.2.0+1 [meta path process]
- xml 5.3.1 [collection meta petitparser]
- yaml 3.1.1 [collection source_span string_scanner]

@julienlebren
The error indicates probably an issue at firebase side and not at client's side (i.e flutterfire) so we can't do much about this error since it is not in flutterfire's control. You'll need to check out https://github.com/firebase/flutterfire/discussions/5708 discussion and see if any any of the comments help you to resolve it.
Closing from here as this is not flutterfire plugin issue.


ws2tcpip: Fix GetAddrInfoEx parameters

Remove GetAddrInfoExW reference to lpCompletionRoutine parameter type LPWSAOVERLAPPED_COMPLETION_ROUTINE.

Clarify that lpCompletionRoutine parameter type is always LPLOOKUPSERVICE_COMPLETION_ROUTINE regardless of Windows version.

Change GetAddrInfoExW references of lpNameHandle to lpHandle, since the latter name is used in the function prototype.

Prior to this change the lpCompletionRoutine parameter was erroneously documented for GetAddrInfoExW as LPWSAOVERLAPPED_COMPLETION_ROUTINE in the parameter details. Further, both GetAddrInfoExA/W implied that the correct type, LPLOOKUPSERVICE_COMPLETION_ROUTINE, was for Windows 8 and Windows 2012. In fact all versions of Windows and SDKs (including Windows 11) that support these functions expect parameter type LPLOOKUPSERVICE_COMPLETION_ROUTINE.
Assisted-by<EMAIL_ADDRESS>Ref: https://github.com/curl/curl/issues/12630
Closes #xxxxx

The related issues below should also be addressed but there is no way to file them as issues.
#1. GetAddrInfoExW prototype uses the name lpHandle for the last parameter and GetAddrInfoExA prototype uses the name lpNameHandle for the last parameter. It may be better for consistency with GetAddrInfoExA doc to modify the GetAddrInfoExW function prototype in the SDK to use lpNameHandle rather than change all references of that in nf-ws2tcpip-getaddrinfoexw.md to lpHandle like I did. The function prototype is not in nf-ws2tcpip-getaddrinfoexw.md so I cannot make the change myself.
#2. While investigating LPWSAOVERLAPPED_COMPLETION_ROUTINE (the incorrect type of lpCompletionRoutine) it was determined that the minimum supported client/server Windows 10 Build 20348 requirement is wrong, and it is used in much earlier SDKs and Windows versions.
/cc @edmcln @pps83

The bad reference to LPWSAOVERLAPPED_COMPLETION_ROUTINE came from 6dc0a1cc. Other files in that commit have the same change but they all look correct because the function prototypes for those functions and structs have at least one parameter type of LPWSAOVERLAPPED_COMPLETION_ROUTINE.
/cc @stevewhims


Support setting priority for classifier programs

The SchedClassifier attach function does not currently allow the priority (aka preference) of a classifier program to be explicitly set.  Instead, the underlying netlink_qdisc_attach function defaults the priority to zero which tells the system to assign it the next highest priority for the given qdisc.  It is useful to be able to explicitly control the order in which filters are executed and also to be able to insert new filters into an existing set at less than the highest priority.

It's done, closing


Delete Group by ID

This one is similar to #222.
Problem
The current GroupsDelete API requires the user to pass in a Group entity acquired from a query. This may serve as an inconvenience when users saved a referenced to an ID that they want to delete. They would have to perform a query first before being able to delete.
Solution
Add functions to the GroupsDelete  API that allows users to pass in Group IDs instead of entities. It would look something like;
delete
    .groupsWithId(1, 2, 3)
    .commit()

[x] Update documentation; https://github.com/vestrel00/contacts-android/blob/main/docs/groups/delete-groups.md
[x] Update cheatsheet; https://github.com/vestrel00/contacts-android/blob/main/docs/cheatsheet.md

This is out now in the 0.2.3 release!


Fix LNbits css building

see https://github.com/lnbits/lnbits/issues/99
replace the QuickFix in bonus.lnbits.sh simply by overwriting the bundle.css with a real solution.

OK this should be fixed when raspiblitz tag gets upadted to include this fix:
https://github.com/lnbits/lnbits/issues/99#issuecomment-711058357
The quickfix then can be removed.

OK quickfix removed and tested. Looks good - closing issue.


Release Candidate Comments (Board/Council Diversity)

This issue was created to collect comments about the upcoming metrics release.
This thread is for comments about Board/Council Diversity
GitHub location: https://github.com/chaoss/wg-diversity-inclusion/blob/master/focus-areas/governance/board-council-diversity.md
See all release candidates of metrics are at:
https://chaoss.community/metrics-202001/

Remove Focus Area prior to metric name -- this is consistent with the layout of the other release candidate metrics.


[BUG] custom-initialize-reset: Unknown option ‘--restore’

I'm getting this error on startup:
custom-initialize-reset: Unknown option ‘--restore’

I'm not sure the reason for this, but I see a --restore argument in the doom codebase, and it seems like it's no longer usable.

Does doom refresh -f fix it? The --restore argument is handled here, and loaded early in the startup process.

Does doom refresh -f fix it? The --restore argument is handled here

I tried it but it did not work for me.

As of ea936d9 this should be resolved. Let me know if that isn't the case and I'll reopen the issue. Thanks for bringing it to my attention!


Add hollow triangle pattern in Python, Pattern34

Description
Task
For the given input n the number of rows printed should be 2*n-1 for ex:

Note

Filename should be Pattern34.py

pr merged #41


Improve handling of apps with helper apps

Describe the solution you'd like
With Fabric, running an app with an as-yet unknown bundle identifier would automatically create an entry for that app in the dashboard. And I would only need to upload dSYMs once; they would be available to all apps. I would appreciate the same functionality in App Center.
Additional context
My [Mac] app consists of one main app and two helper apps shipped as part of the main app's bundle. In addition, I need to build the app twice — once for direct sale and once for Setapp. That makes for a total of six bundle identifiers.
With App Center, I had to create six individual "apps" for each of the bundle identifiers to separate my analytics and crashes for each binary. Fabric (which I used to use) would automatically create a new "app" on the dashboard for each of these bundle identifiers the first time the corresponding app was run.
In addition, I have to upload the same set of dSYMs three times (see below).
Describe alternatives you've considered
I have manually created the apps in the App Center dashboard now.
However, I currently have to run the appcenter_upload Fastlane action three times per build, uploading the same set of dSYMs three times, once per app. Most of the libraries (and thus dSYMs) are shared across the main app and its helpers, so ideally it would be possible to only upload the dSYMs archive once, then having it available to all apps for symbolication.

@MrMage thanks for the feature request! We don't have any immediate plans to address this but I recognize this is a pretty painful experience. We'll monitor this request for community support and re-prioritize this if necessary. Thanks!

This is still relevant.

This is still relevant.

This is still relevant.

Still relevant :-)

Still relevant.

Not stale.

Still relevant.

Still relevant. @winnie, any chance this could get prioritized?

Still relevant.

...

...


Get dns reverse of OriginIP

OriginIP is an IP, it's not very human friendly for dashboard. We can resolv this ip and give the reverse dns name

first comment updated

@pierrecdn I already create PTR for the current cloudflare VIP.

Still not seeing why you need to do reverse DNS lookups, could you please explain it?

it's on the PR comment -> OriginIP is an IP, it's not very human friendly for dashboard. We can resolve this ip and give the reverse dns name if available.


FT300, socketcan_interface missing

Hey,
I have a robotiq Ft300 on ubuntu 14.04 with ROS indigo. I run into problems cmake the work space. I wonder if you could help me with it.
I tried to use rosdep install robotiq_modbus_tcp and it doesn't work and it says
ERROR: Rosdep cannot find all required resources to answer your query Missing resource robotiq_modbus_tcp ROS path [0]=/opt/ros/indigo/share/ros ROS path [1]=/home/drpslab/surface/src ROS path [2]=/home/drpslab/scann1/src ROS path [3]=/home/drpslab/descartes1/src ROS path [4]=/home/drpslab/descartes/src ROS path [5]=/opt/ros/indigo/share ROS path [6]=/opt/ros/indigo/stacks
I tried to cmake the workspace and it says
`  Could not find a package configuration file provided by
"socketcan_interface" with any of the following names:
socketcan_interfaceConfig.cmake
socketcan_interface-config.cmake

`
I checked socketcan_interface on this page  but I still don't know how to install this package.
Any help would be deeply appreciated.
Thank you.

If anyone runs into this problem, try this:
rosdep install --from-paths ~/robotiq/src --ignore-src
~/robotiq is my workspace


feat: setup 6.43.x lts branch

enable releases
release-brancher create-pull-request \
  --branch-name="6.43.x" \
  --target-tag="v6.43.2" \
  --repo="googleapis/java-spanner" \
  --pull-request-title="feat: setup 6.43.x lts branch" \
  --release-type=java-backport

@burkedavison I was revisiting this old PR. Can you provide a bit more context on why we are providing this LTS branch? Is it a regular chore?

Closing as there has not been any activity in the past several weeks. Please re-open if this is still relevant.


Remove the ODCA tool link

Hi there,
This doc site has the mention of ODCA (On-Demand Code Analysis tool) and it's hyperlinked. Since we are in the process of removing partner's access to this tool, could you please remove the hyperlink and keep it flat without any URL attached.
Thanks,
Rajyashree

Hi there,
Just wanted to follow up on this request. Could you please give me an ETA on this?
Thank you,
Rajyashree

Can you please share the docs URL that you refer to here? App certification checklist doesn't seem to list it; if it was for this URL.

Closing due to no response.


[Snyk] Fix for 1 vulnerabilities

Snyk has created this PR to fix one or more vulnerable packages in the `rubygems` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

Gemfile.lock

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

591/1000  Why? Recently disclosed, Has a fix available, CVSS 6.1
Cross-site Scripting (XSS) SNYK-RUBY-ACTIVESUPPORT-3360028
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Cross-site Scripting (XSS)

Code coverage
Total coverage: 93.36%

Powered by Slather

  Generated by :no_entry_sign: Danger

Fixed in https://github.com/twilio/twilio-verify-ios/pull/220


Added fix to deal with CPM: extensible SizeConstraint

Is this a patch of the 32 bit support patch or something different?
(We already have a dev branch here merging all of our patches.)


internal/gamepad: error gamepad: GetRawInputDeviceList failed: The data area passed to a system call is too small.

Ebitengine Version
v2.6.0-alpha.4
Operating System

[X] Windows
[ ] macOS
[ ] Linux
[ ] FreeBSD
[ ] OpenBSD
[ ] Android
[ ] iOS
[ ] Nintendo Switch
[ ] Xbox
[ ] Web Browsers

Go Version (go version)
go1.20.4
What steps will reproduce the problem?
Not sure. The error was reported from games in the real world.
What is the expected result?
No error
What happens instead?
gamepad: GetRawInputDeviceList failed: The data area passed to a system call is too small. was reported in a function in the package gamepad.
Anything else you feel useful to add?
/CC @wasedaigo
This seems very rare.

Let's wait and see with the fix later.


feat(@angular-devkit/build-angular): fine grain settings for sourceMaps

Still need to add a couple of tests but this is the idea. @clydin, @hansl, @filipesilva


Move code generation out from Roslyn Source Generator

Code generation should be placed in a separate library, so the Roslyn Source Generator will use the library to produce code. It can be helpful for such cases as the reverse engineering domain models from a database file.

Implemented in dec144e24eff0e5468cc97f875b4e42bf218cd65


Performance documentation

Greetings!
It's not actually an issue, but more of a question, so sorry for putting it here. 🤷♂
I'm performing an investigation regarding potential usage of SpiceDB in our system, but can't find any docs or benchmarks (at least on the surface) on how SpiceDB behaves on large number of entries, especially: users and resources.
I quite understand that benchmarking and numbers heavily depend on the particular permission model one choses and designs, but I think it'd be nice to have at least benchmarks and docs or the models for examples you show in your blog.
Was I merely not a decent finder or there're none yet?
In general, I would love to have (treat it as a request for future improvements 🙂):

Documented benchmarks for some most popular permission models (e.g. recreation of the RBAC system for REST API with lots of users on decent amount of routes/resources)
O-notation complexities of the operations (especially for authz checks)
Explanations/benchmarks of various cache levels (e.g. w-w/o Zed-tokens, consistency levels, etc.)
Tools to easily bootstrap a performance testing in anyone's environment

One live running benchmark is the Authzed Website which uses Authzed as authorization backend
Refer: https://status.authzed.com
For more questions like this, you can join their discord server: https://authzed.com/discord


Use ":clearjumps" in new NERDTree windows

See commit message.

I'm not sure about this. Looking at @juanibiapina's comments in #250, there may be cases where jumping out of NERDTree with <C-O> is desirable, particularly when you use :e .. If I've misunderstood either of these scenarios, let me know.


fix: add min/max support to DayPicker

Motivation
Adding a mechanism to specify a min/max date, as well as selectively disabling dates arbitrarily.
Behavior

@danperkins seems like a good idea. I'll target for a subsequent PR.

Actually, I'll just add to this PR for ease.


break and continue

The break and continue section of the book could be improved by explaining these keywords without including arrays in the examples, e.g. https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/continue

This is currently around https://csci-1301.github.io/book.html#break-and-continue-1 and I agree that there could be simpler use cases.


Incompatibility with default ProxySelector?

Hi there, I'm trying to use OkHttp in a desktop application that sets a JVM-wide proxy via java.net.ProxySelector#setDefault, but looks like OkHttp doesn't like that.  Unfortunately I can't get rid of ProxySelector and I was wondering if there were ways to still use OkHttp.
So, using Java 7 (1.7.0_72) on Mac OS X and OkHttp 2.2.0, the sample code at https://gist.github.com/agatti/7620010f1a356965e4d7 fails with this:
Exception in thread "main" java.net.SocketException: Unknown proxy type : HTTP
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:396)
at java.net.Socket.connect(Socket.java:579)
at com.squareup.okhttp.internal.Platform.connectSocket(Platform.java:100)
at com.squareup.okhttp.Connection.connect(Connection.java:155)
at com.squareup.okhttp.Connection.connectAndSetOwner(Connection.java:174)
at com.squareup.okhttp.OkHttpClient$1.connectAndSetOwner(OkHttpClient.java:120)
at com.squareup.okhttp.internal.http.RouteSelector.next(RouteSelector.java:131)
at com.squareup.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:312)
at com.squareup.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:235)
at com.squareup.okhttp.Call.getResponse(Call.java:262)
at com.squareup.okhttp.Call$ApplicationInterceptorChain.proceed(Call.java:219)
at com.squareup.okhttp.Call.getResponseWithInterceptorChain(Call.java:192)
at com.squareup.okhttp.Call.execute(Call.java:79)
at ProxyTest.main(ProxyTest.java:36)

although the normal URL#connect() method of getting data works with a default ProxySelector being set.
Is this a (known) bug or is there a way to work around this?  Maybe it's just me doing things wrong here :)
Thank you!

This is quite a surprise. We're assuming the system proxy selector won't be picked-up at this level. Do other Java HTTP clients work here? I would expect your proxy selector to completely break your network here.

I haven't tried any other clients besides HttpURLConnection, but I did find a way to get it working with OkHttp.  Apparently the code for the ProxySelector instance always returns HTTP proxies even for SOCKS connections (as far as the JVM is concerned), and since OkHttp sends such requests, well, you know what happens.
I haven't checked the okhttp-urlconnection module yet, but on paper it looks like it should work around this situation by sticking with sending HTTP requests to be proxied rather than SOCKS ones, right?

Yuck. From OkHttp's perspective we're using raw sockets. But unfortunately, the sockets we're getting are consulting proxy selector against our wishes!
You really can't clear the proxy selector?

No action for us to take here.

Unfortunately not, otherwise other pieces break.  Still, thanks for the help!
However, how about adding a warning or a note somewhere in the documentation to prevent others from getting stuck as I was?  I'm not a native English speaker otherwise I might have submitted that PR myself.


KNL-1436 When ClusterEventTracking thread dies events stop being processed.

Switch from an eternal thread to ScheduledExecutorService
updated logging messages
use Throwable to catch IO Errors

Nice. Thanks @ern


Update ProGit2 links, as the TFS content is removed

Changes this pull request makes:

Update both links to the ProGit 2 book
Ensure that readers can still find the last release that covers TFS and the migration towards Git

Context:
I made the last push to remove the TFS content from the Pro Git book, seeing as the content was getting badly out of date, and that the TFS project is end of life. This removal was done after discussing with the Pro Git 2 author on this move, and after people have had ample time to complain about the proposed removal at https://github.com/progit/progit2/issues/1326. Nobody has complained since Oct 29,2019, so the decision was made to remove the content.
The old content can still be found in html, epub, pdf and mobi formats though, so it's not totally gone!
Prior discussion that happened before deciding to remove the TFS content:
https://github.com/progit/progit2/pull/1322
https://github.com/progit/progit2/issues/1323
https://github.com/progit/progit2/issues/1326
Pull request that removes the TFS content:
https://github.com/progit/progit2/pull/1480

I think this pull request should be merged, as the git tfs content was removed.

Thanks.

Thanks for merging! :smile:


Please bump "websocket-stream" to  3.0.0 or above

Now busmq uses<EMAIL_ADDRESS>which uses<EMAIL_ADDRESS><EMAIL_ADDRESS>has a security Vulnerability, see https://nodesecurity.io/advisories/67.
Can you please bump websocket-stream to 3.0.0 or above? This is pretty urgent.

I tried updating to  v3.3.3 but it seems to break busmq federation.
It might take a while to find the cause.
If it's urgent, perhaps you would be willing to investigate

Found the cause, will be releasing a new version shortly

Actually, busmq uses<EMAIL_ADDRESS>directly, not relying on the ws usage embedded in websocket-stream, so there doesn't seem to be a problem here.
Released version 2.2.0 in any case.

@fujifish thanks for quick fix!


add no_wildcard_variable_uses; rev to a new major version

add no_wildcard_variable_uses; rev to a new major version
closes #139

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.
Most changes should add an entry to the changelog and may need to rev the pubspec package version.
Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

This stages this change for the next time we publish a major release of package:lints (likely not for at least 1-2 quarters; previously thinking on the publish cadence has been ~yearly).
cc @pq @natebosch