[BUG] Upgrading a 3-node cluster to 1.1.0 stuck indefinitely

Describe the bug
While upgrading a 3-node cluster from 1.0.3 to 1.1.0 the upgrade process becomes stuck indefinitely in the "pre-drain" job for the first node.
Pre-Drain Job Pod:
+ echo 'Waiting for volume pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113 to be healthy...'
+ sleep 10
Waiting for volume pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113 to be healthy...
+ '[' true ']'
+ '[' 3 -gt 2 ']'
++ kubectl get volumes.longhorn.io/pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113 -n longhorn-system -o 'jsonpath={.status.robustness}'
+ robustness=degraded
+ '[' degraded = healthy ']'
+ '[' -f /tmp/skip-pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113 ']'
+ echo 'Waiting for volume pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113 to be healthy...'
+ sleep 10
Waiting for volume pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113 to be healthy...

The volume is from the Prometheus deployment:
/home/rancher # kubectl get pv volume pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                                                                                STORAGECLASS   REASON   AGE
pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113   50Gi       RWO            Delete           Bound    cattle-monitoring-system/prometheus-rancher-monitoring-prometheus-db-prometheus-rancher-monitoring-prometheus-0   longhorn

/home/rancher  # kubectl -n longhorn-system get lhv pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113
NAME                    STATE   ROBUSTNESS  SCHEDULED  SIZE     NODE  AGE
pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113  attached  degraded<PHONE_NUMBER>0  donna  169d

home/rancher # kubectl get nodes
NAME     STATUS                     ROLES                       AGE    VERSION
donna    Ready                      control-plane,etcd,master   168d   v1.22.12+rke2r1
harvey   Ready,SchedulingDisabled   control-plane,etcd,master   169d   v1.22.12+rke2r1
mike     Ready

harvey:/home/rancher # kubectl get blockdevices.harvesterhci.io -A -o wide
NAMESPACE         NAME                               TYPE   DEVPATH    MOUNTPOINT                                                        NODENAME   STATUS   AGE
longhorn-system   502a522e036e17535bb9e7dc6cb772e6   disk   /dev/sdb   /var/lib/harvester/extra-disks/502a522e036e17535bb9e7dc6cb772e6   mike       Active   168d
longhorn-system   5c5a4447502b97530f54d41ae73ce095   disk   /dev/sdb   /var/lib/harvester/extra-disks/5c5a4447502b97530f54d41ae73ce095   harvey     Active   169d
longhorn-system   f4f0e311027560b0845129cc0f6eeb88   disk   /dev/sdb   /var/lib/harvester/extra-disks/f4f0e311027560b0845129cc0f6eeb88   donna      Active   168d

Longhorn Manager logs endlessly repeating:
time="2022-10-26T15:47:52Z" level=debug msg="Found 0 node has at least one schedulable disk" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=donna owner=donna state=attached volume=pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113
time="2022-10-26T15:47:52Z" level=error msg="There's no available disk for replica pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113-r-afb2054f, size<PHONE_NUMBER>0"
time="2022-10-26T15:47:52Z" level=error msg="unable to schedule replica" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=donna owner=donna replica=pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113-r-afb2054f state=attached volume=pvc-b4ffc53c-f8d4-4c90-8011-a7f9cd156113

There is an existing issue describing the problem of the Prometheus volume never recovering: https://github.com/harvester/harvester/issues/1906
Prometheus volume is configured with 3 replicas. And since 1 of the 3 nodes is cordoned during upgrade. The volume can never recover fully blocking any further upgrade process.

 When ONE nodes is drained, the LH volume needs another alternative NODE to hold the traditional 3-replicas, but the system can not meet this.
4+ nodes cluster will have no this issue.   (another issue https://github.com/harvester/harvester/issues/2907 is solved by a related workaround)

Upgrade was also blocked by upgrade-repo-hvst-upgrade-52qzw-disk-0 volume having 3 replicas.

Interestingly this issue did not exist when upgrading from 1.0.2 to 1.0.3 @w13915984028

Technically, it is because in v1.1.0, the upgrade_node.sh will check longhorn volume, but in previous version, it does NOT. @janeczku  @bk201
v1.0.3 (execute when v1.0.2 upgrade to v1.0.3)
https://github.com/harvester/harvester/blob/v1.0.3/package/upgrade/upgrade_node.sh#L201
v1.1.0 (execute when v1.0.3 upgrade to v1.1.0)
https://github.com/harvester/harvester/blob/master/package/upgrade/upgrade_node.sh#L303

@janeczku Correct. We add volume health check in this version to ensure data availability. In the previous versions, the controller just continue on next node without checking.

Related to https://github.com/harvester/harvester/issues/1926, we need a way to let user know what's blocking the upgrade.

Beside of the health check being very useful - any idea why we can not rely on the "deprecated" status plus PDB from Longhorn?


Sorting blindedMessages by amount

Fixes: #90
Description
Ordered blindedMessages returned by createSplitPayload by amount and added a keepVector
Changes

Ordered blindedMessages by amount
added keepVector as return value

PR Tasks

[x] Open PR
[x] run npm run test --> no failing unit tests
[x] run npm run format

This is now ready for review. As outline above I changed createSplitPayload to return a payload containing a list of proofs ordered by amount, as well as a list of booleans indicating which proof to keep and which to send.
I then changed send to use the list of booleans (keepVector) to /split and keep the right proofs.
@gandlafbtc @callebtc

Looks good! Only thing missing is a Unit test testing the behaviour.

I was under the assumption that the old units tests for this method would still suffice, but we should probably add one to check wether the amount is actually sorted (will do asap). Or am I missing something?

Looks good! Only thing missing is a Unit test testing the behaviour.

What would be good way to easily generate secrets and signatures for the Unit tests?

@Egge21M I think this PR might be outdated, especially after https://github.com/cashubtc/cashu-ts/pull/159.. shall we close it?


Rename spawn_allocate to try_set_spawned_state

This commit contains a suggestion to rename TaskStorage::spawn_allocate.
The motivation for this is when reading through the code I was
expecting something else to happen in this method, due to allocate in
the method name.
I'm very new to this code base so I may be wrong in thinking this
is a good change, but I wanted to open this PR to get some feedback.

The logic behind the old names is "spawning" is two steps: "allocate" the memory for the task (mark the TaskStorage as "in use"), then "initialize" it with the future.
I'd rather keep the "symmetry" in the names, but I agree "allocate" can be misleading because it's not using "The One Alloc" (the heap). Perhaps "spawn_reseve", "spawn_mark_used", "spawn_mark"? Or perhaps just addding comments would clarify it enough?

I'd rather keep the "symmetry" in the names, but I agree "allocate" can be misleading because it's not using "The One Alloc" (the heap). Perhaps "spawn_reseve", "spawn_mark_used", "spawn_mark"? Or perhaps just addding comments would clarify it enough?

Thanks for the fast reply! I like your suggestion spawn_mark_used and updated with the PR with it.
Adding a comment would work, the only thing it that at least for me it would be easier to read with the changed name and not have to read a comment. But this is just a suggestion and I have no problem with not changing this at all if you'd prefer that :+1:


cloudscraper needs recaptcha provider settings

Expected behaviour:
Cloudscraper should work as expected to allow to load resources protected by CloudFlare. There should be a way to provide the recaptcha parameter if needed as described here: https://github.com/VeNoMouS/cloudscraper#3rd-party-recaptcha-solvers
Actual behaviour:
Flexget crash with a cloudscraper related error.
Log:
2020-03-04 08:31:08 CRITICAL task          discover-series BUG: Unhandled error in plugin discover: Cloudflare reCaptcha detected, unfortunately you haven't loaded an anti reCaptcha provider correctly via the 'recaptcha' parameter.
cloudflare_exceptions.Cloudflare_reCaptcha_Provider: Cloudflare reCaptcha detected, unfortunately you haven't loaded an anti reCaptcha provider correctly via the 'recaptcha' parameter.
2020-03-04 08:31:08 CRITICAL manager       discover-series An unexpected crash has occurred. Writing crash report to /root/.flexget/crash_report.2<IP_ADDRESS>108170837.log. Please verify you are running the latest version of flexget by using "flexget -V" from CLI or by using version_checker plugin at http://flexget.com/wiki/Plugins/version_checker. You are currently using version 3.1.30.dev
2020-03-04 08:31:08 WARNING  task          discover-series Aborting task (plugin: discover)

Additional information:

FlexGet version: 3.1.30.dev
Python version: 3.8
Installation method: Docker
Using daemon (yes/no): yes
OS and version: Alpine container on Arch Linux
Link to crash log: https://pastebin.cedricgirard.fr/?5ee02b6460e76cf9#BnbwdivysfCLycg2schL3ortFQGTmLU1Mioe4U8ojjbG

Scratch that, we should not have to solve recaptcha. cloudscraper 1.2.26 fix that.


Cannot compile examples

It seems that the examples have not been upgraded to Leptos 0.3 yet. But even after upgrading manually, I get some kind of linking error when running cargo leptos build regarding to wasm-bindgen.

Hi @124C41p
I've just updated the dependencies in the examples and they seem to compile okay for me.. Maybe try pulling down the latest changes from main branch and try again?
If it still doesn't work please post what linking errors you're seeing thanks!

Thanks for updating! Unfortunately, the linking issue remains for me - even after reinstalling my rust toolchain and cargo-leptos. When trying to build the axum-example using cargo leptos build on latest nightly, I get the following error message:
       Cargo finished cargo build --package=axum_example --lib --target-dir=target/front --target=wasm32-unknown-unknown --no-default-features --features=hydrate
Error: at `/home/<username>/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-leptos-0.1.8/src/compile/front.rs:42:30`

Caused by:
    0: at `/home/<username>/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-leptos-0.1.8/src/compile/front.rs:108:10`
    1:

       it looks like the Rust project used to create this wasm file was linked against
       version of wasm-bindgen that uses a different bindgen format than this binary:

         rust wasm file schema version: 0.2.86
            this binary schema version: 0.2.84

       Currently the bindgen format is unstable enough that these two schema versions
       must exactly match. You can accomplish this by either updating the wasm-bindgen
       dependency or this binary.

       You should be able to update the wasm-bindgen dependency with:

           cargo update -p wasm-bindgen

       or you can update the binary with

           cargo install -f wasm-bindgen-cli

       if this warning fails to go away though and you're not sure what to do feel free
       to open an issue at https://github.com/rustwasm/wasm-bindgen/issues!

It looks like maybe running cargo update in the example directory might solve this, since you have a lock file containing wasm-bindgen 0.2.84

Ah it seems like we actually need to se wasm-bindgen to =0.2.84 for now.
https://github.com/leptos-rs/leptos/issues/1051#issuecomment-1550539377

Seems to be resolved.
https://github.com/leptos-rs/leptos/issues/1051#issuecomment-1586197897


Override 'searchPredicate(text: String?) -> NSPredicate?'

Hi, I want to override the searchPredicate function but I can't since it is private. I tried to override refreshSearchResults() since it is public but then I can't access searchQueue property, since it is private. Can you offer another solution? Thanks

There is a basePredicate property that you can override to add additional filtering to the text filtering.

I am using a predicate like this: NSPredicate(format: "ANY messages.value CONTAINS[c] %@", text) so I can't set the base predicate with a constant. I forked the project and made overriding searchPredicate possible to solve the problem for now, which seems to work.


[ODS-4531] Verify course transcript workaround for DATASTD-1408

See also https://github.com/Ed-Fi-Alliance-OSS/Ed-Fi-ODS/pull/188.

Closing the PR. ODS-4612 covers this work.


fix(graphql-relational-schema-transformer): escape SQL reserved keywords

Issues:
#5525, #2293
Description of changes:
Escape reserved keywords used in table names when executing DESCRIBE tableName.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@vic-blt you will have to update the test too at https://github.com/aws-amplify/amplify-cli/blob/c932d6f264b4260a98ed8f8975a67e47c4c47c85/packages/graphql-relational-schema-transformer/src/tests/AuroraDataAPIClient.test.ts#L460

@ammarkarachi I updated the test and force pushed.

@ammarkarachi There was also an occurrence at line 443.
It should be good this time :sweat_smile:.


Downsampled data has NaNs in dual-marker statistics

Version: unsure - 0.8.6 or 0.8.3, but likely applies to both
Platform: Win10
A customer observed that statistics had NaNs over a certain range:

Sample drops causing NaNs?

Fixed in joulescope 23b91fd.


fix case where reused property record isn't updated correctly on server

There was a synchronization issue between numeric property map on server and runtime.
The following is the problematic sequence:
Add numeric property id
Update server map
Reclaim that property id
Add same numeric property id (this incorrectly causes to be put on pendingPropsList)
Remove that property (since it is in pendingPropsList, we don't think we need to update server)
Add same non-numeric property id
update server map (does nothing; should remove propId)
Codegen (with that propid used in an InitFld).
The server still has this propId in numeric props list, which breaks some assumptions in globopt.

Nice find!
:shipit:


⚠ AGEG website (redirect) has degraded performance

In 5f0b1fb, AGEG website (redirect) (https://ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 3130 ms

Resolved: AGEG website (redirect) performance has improved in 5b652ea.


REL: 24.0.0

All good on my end. Thank you for your continued efforts to push forward the NiPreps set of tools.


PDF Text Color

Hi,
i have problems setting up text colors.
The preview for PDF shows colored text, the actual output not.
tests in a fresh editor:
[blue]#*BLAU*# +
[yellow]#*GELB*# +
[red]*ROT*

For pdf theming you should define a theme and colors you want to use. Please check https://discuss.asciidoctor.org/Color-for-Text-td7509.html

I really dont know how to do this. I cant find a *.yaml file in which it could find place.
Further help appreciated.

Please ask on https://discuss.asciidoctor.org/ since it is Asciidoctor specific question

Create theme file
custom-color-theme.yml
# FOR Asciidoctor-PDF 2.x
extends: default-with-font-fallbacks

# Set the base text color
base_font_color: #333333

heading:
# Color for H1 headings
  h1_font_color: #1a73e8
# Color for H2 headings
  h2_font_color: #1a73e8
# Color for H3 headings
  h3_font_color: #1a73e8
# Color for links
link:
  font_color: #0000ee
# Color for literal text or code
literal:
  font_color: #d63384

demo3.adoc
= Asciidoc Theme Custom Color Demo
:pdf-themesdir: {docdir}
:pdf-fontsdir: GEM_FONTS_DIR;
:pdf-theme: custom-color

== Test Level 2

This is a Test 2.

This is a Link https://docs.asciidoctor.org/pdf-converter/latest/theme/[Asciidoctor PDF Theming]

=== Test Level 3

This is a Test 3.

AsciidocFx open demo3.adoc
PDF -> Save

Show PDF Color


Adding option "selectable"

Add option "selectable" resulting in autosized text using Flutter's SelectableText widget.
This is related to: #49

Can a contributor merge this please? @kentcb @timsneath @Kavantix @leisim

Any updates? @leisim @Kavantix @timsneath @kentcb

Please merge this as it is really critical for the web side

@leisim @Kavantix @timsneath @kentcb what's happening?
Please merge this PR. Great work guys!

Not sure why I'm being pinged - I am not a maintainer.


Feature request: carry comments in the middle of function bodies down to LLBC

In the following snippet, I would like a way to retrieve the comment in LLBC.
fn foo() -> u32 {
 // Bar
  0
}

Possible thoughts include:

looking up the text via span information
using a rustdoc comment in the hope that it gets attached to an AST node
...?

Thanks!

Turns out clippy has a lint that detects // SAFETY comments before unsafe blocks. They do span shenanigans to recover the comments. Code is here for inspiration.

I made a decent attempt here: https://github.com/AeneasVerif/charon/pull/358, which is made mostly pointless by #233.

Alright, this now works! The heuristic for where to place comments is quite naive however, so please report back if comments end up in surprising places.


Clarify relationship with robust method extraction

See https://github.com/tc39/proposal-pipeline-operator/issues/110#issuecomment-374398256, https://github.com/tc39/proposal-pipeline-operator/issues/107#issuecomment-373897984, https://github.com/tc39/proposal-pipeline-operator/issues/101#issuecomment-374729114.

console.log.bind(console) is not the same as (...$) => console.log(...$), when assigned to a variable rather than used inline.


BETA: Register bangexams.is-cool.me

Added bangexams.is-cool.me using the dashboard.

The dashboard is under development so the prs won't merge of it @ShamyakGoel


Tutormagic stop woking within an IFrame on Jupyter Notebook

Hi Kiko. The tutormagic stop working when embedded within an IFrame on Jupyter Notebook. It only works with --tab or --link options.
tks in advance,
Marcio

I was digging on this last weekend. The url is well formed and sometimes it works and sometimes it doesn't... I have no idea what is happening. Maybe is something related with browser security (I use firefox).
I've added the tag "help wanted" to see if someone could provide some feedback on this.
@iviarcio Which browsers did you use to test what is happening?

I have used tutormagic these days and I can't reproduce this issue and everything is working fine.
Please, if you continue having this issue reopen it. Thanks.


fix style table in README.md

Thanks for the fix @batazor. Would you mind signing the CLA please? The instructions are here: https://neo4j.com/developer/cla/

Thanks for the fix @batazor. Would you mind signing the CLA please? The instructions are here: https://neo4j.com/developer/cla/

done

Thanks for the contribution @batazor!


bpf: Add BPF map operations for the StateDB reconciler

This allows defining the desired state of a BPF map as a StateDB table and to reconcile it with a BPF map. The table can be inspected with "cilium-dbg statedb dump" (or with a table-specific command), and the reconciliation state of each object can be queried. Failure the reconcile will be reported in module health, metrics and in the individual objects.
See ops_linux_test.go for example usage.

I left out the batch operations as I'm not sure how we could currently do this efficiently without bunch of copying and the benchmarks didn't show significant improvement in speed.
Here's how it would approximately look like: https://github.com/cilium/cilium/pull/31035/files#diff-d8fb501ccfd280cddcf1eb74a221bcd6de40714f3fbba1176502fbb435ec18c7R165.

/test

/test


Function Calls API

Will add support for function calls.
This will close #37.

The API is pretty much ready, just testing and documentation left.

My OpenAI API key ran out of tokens and I can't really add balance, so I will be releasing functions experimentally. If any issues arise please create an issue so I can fix them as soon as possible.


Removed redundant code

The removed code would never run, as once this self.shutdown = true; runs, the while loop doesn't run any further so this check was redundant.

Thinking about this some more, I actually think it is better to keep it. Even though it never triggers in the current codebase, it makes the code more robust to future changes that might make it possible to hit this case in the future.
How about adding a comment that explains this instead?


Replace incorrect use of getIndex() in EnumValueDescriptor with getNumber()

Fixes #225

Best practice for protocol buffers is to use getNumber rather than ordinal on the generated Java enum (which the EnumValueDescriptor's getIndex corresponds to
The cel-go implementation that cel-java is based on uses getNumber
other parts of cel-java use getNumber

Note: the test update corrects the test to do the right thing, but it doesn't fail in the existing (incorrect) implementation because the test enum has getNumber() == getIndex() for all values.

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


flyover or hover enhancement

No issues to report yet. I would like to see two options. 1) Have option to have default be no gooey unless option is provided, but this looks like it's being worked on.

Would be to add a description field that could provide more context in a flyover the field. Still pretty new to Python, any tips on how to get started with this if no one else is working on it?

-David

No plans to implement this baring a sudden surge in interest.


MongodB security

Add security to MongoDb on EC2

We currently let the user define the MongoDB client using PyMongo, meaning that you should be able to implement security protocols prior to injecting thst sependency into the UnitOfWorkProvider.
However, we may not have anticipated all scenarios. If you have a specific suggestions, please feel free to reach out to me on LinkedIn and we can set up a call. https://www.linkedin.com/in/olivershetler

Apologies. We have a fork, and these issues were meant for it.


[EN] Feedback for: /web/tools/chrome-devtools/?hl=en

Cant view video on full screen.

cc @pbakaus

Duplicate of issue #2325.
tldr from comment over there, it is an upstream issue with MDL.

Please consolidate discussion to #2325


Interpret std::vectorstd::string

Can provide example ROOT file on request, but at the moment don't have one that I'd like to post publicly.

It looks like I already have an example to use for testing:
uproot.open("tests/samples/small-evnt-tree-fullsplit.root")["tree"]["StlVecStr"]

So I won't need a specially prepared file. Thanks!

Done (in 2.6).


Python: Propagate taint through parse_qs

Encountered this in Gruyere. It was not essential to anything, but we should handle it none the less.
reference: https://docs.python.org/3.8/library/urllib.parse.html#urllib.parse.parse_qs

This all looks good. I take it that we were unable to track taint through the definitions of any of these things, or if we could, it wasn't enough b/c of not being able to analyze certain imports, etc.?

What an excellent question! I did not think about it, simply found that we didn't propagate taint properly, and made a fix.
So I looked over the urllib.parse code more in depth. Currently the taint stops at the call the _coerce_args -- to handle that case, we would need to track taint through star args (tracked in https://github.com/github/codeql-python-team/issues/49)
If that was solved the taint would stop because we currently don't propagate taint through str.split (fix in https://github.com/Semmle/ql/pull/3302).
Once these two problems have been fixed, it would be interesting to see if we can handle this case out-of-the-box without any special handling.

No matter what, we should also handle parse_qsl :+1:

After adding support for parse_qsl I thought that this might be enough to get the taint for parse_qs working, but alas; although we figure out that pairs is tainted, neither name nor value gets tainted :disappointed: src I'll try to investigate this a bit more in a different issue/PR.
In conclusion, for now, we need both of these special cases.


Mac App Store refuses app via transporter

I have an app that I can notarize, sign and execute properly. But when I upload it to Mac App Store for review via transporter, I get the following errors:
Asset validation failed (90287)
Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. The bundle contains a key that is not included in the provisioning profile: 'com.apple.developer.team-identifier' in 'network.goodip.client.pkg/Payload/GoodIP.app/Contents/Library/LoginItems/GoodIP Login Helper.app/Contents/MacOS/GoodIP Login Helper'. (ID: a7ba6702-bf50-4fb8-9623-9923a325c547)

Asset validation failed (90287)
Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. The bundle contains a key that is not included in the provisioning profile: 'com.apple.application-identifier' in 'network.goodip.client.pkg/Payload/GoodIP.app/Contents/Library/LoginItems/GoodIP Login Helper.app/Contents/MacOS/GoodIP Login Helper'. (ID: ee3241a0-ba7d-4a04-8e15-5f0e62e021cc)

Asset validation failed (90287)
Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. The bundle contains a key that is not included in the provisioning profile: 'com.apple.developer.team-identifier' in 'network.goodip.client.pkg/Payload/GoodIP.app/Contents/MacOS/GoodIP'. (ID: 85ac6410-7994-46a3-8c40-8bfa441beee4)

Asset validation failed (90287)
Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. The bundle contains a key that is not included in the provisioning profile: 'com.apple.application-identifier' in 'network.goodip.client.pkg/Payload/GoodIP.app/Contents/MacOS/GoodIP'. (ID: 79445e6f-1e21-446f-bd9f-d32cfef3901f)

I suspect that I have a mis-configuration somewhere rather than a bug, but I can't find the problem.
To give more precisions:

"security find-identity -p codesigning -v" reports both the "Developer ID Application" and "Apple Distribution" certificates.
in full debug mode, osx-sign shows the entitlement

<key>com.apple.developer.team-identifier</key><string>Correct ID of my developer account</string>

"npm run electron:make" signs, notarizes and creates a dmg successfully. I can run the app on a Mac at a physical Apple Store.
The script shows that for mas configuration, the .pkg app is signed with the "Apple Distribution" certificate.
I have read and I think that I do everything described at https://www.electronjs.org/docs/latest/tutorial/mac-app-store-submission-guide

What could be wrong? I apologize if it's not a bug.
The only thing that doesn't make sense is that I'm not using the provisioning file downloaded from the apple website for the platform "macOS".

Make sure you're building a mas build and not darwin/mac
You'll also need to use the
"Apple Distribution" + "3rd Party Mac Developer Installer" certificates with the matching provisional profile.
Hope this helps.

Hey! Where you able to get a working build on the Mac App Store (TestFlight) ?

No. :-( :-(
I build both mac and mas and I'm sure that I'm dealing with the right mas file when dealing with transporter.
Here is my keys. I do I have "Apple Distribution" and "3rd Party Mac Developer Installer".

I'm unsure what kind of configuration I should have to make sure that the build system use the right certificates. Can you be more precise or is there a recent WORKING tutorial somewhere?

That's annoying man. Share your config files here... I can take a look and let you know if anything stands out. What package builder are you using? I'm currently using electron-forge which uses electron-packager & electron-osx-sign.
I have now managed to successfully package the app and upload via Transporter to TestFlight BUT the app directly hits status "Not Available for Testing" without any error messages or logs. Such a pain.

I'm a little bit confused. Do you have success or do you have (you too) an issue which would be different from mine?
I'm disappointed by Apple. Their certificates are just pure nightmare. All the error messages are completely cryptic. I have complained multiple times on their forums but they don't care. It's like complaining against a wall.
I'm using:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>I'm building mas:
	"mac": {
		"category": "public.app-category.utilities",
		"target": ["dmg", "mas"],
		"icon": "assets/main.icns",
		"hardenedRuntime": true,
		"entitlements": "entitlements.mac.plist",
		"entitlementsInherit": "entitlements.mac.plist",
		"gatekeeperAssess": false
	},
	"dmg": {
		"title": "GoodIP App",
		"background": "assets/background.tiff",
	},
	"mas": {
		"entitlements": "entitlements.mas.plist",
		"entitlementsInherit": "entitlements.mas.plist",
	},
	"afterSign": "./notarize.js",
	"afterAllArtifactBuild": "./post.js"

and notarize.js:
const { notarize } = require ("@electron/notarize");

module.exports = async () => {
	if (process.platform === 'darwin') {
		console.log("Starting notarization");
		try {
			await notarize({
				appBundleId: "...",
				appPath: "./dist/mac/GoodIP.app",
				appleId: "....",
				appleIdPassword: "...",
				ascProvider: "G..."
			});
			await notarize({
				appBundleId: "...",
				appPath: "./dist/mas/GoodIP.app",
				appleId: "....",
				appleIdPassword: "...",
				ascProvider: "G..."
			});
			console.log("Ending notarization");
		} catch (error) {
			console.log("Error: ", error);
		}
	}
}

Can you share your setup and configuration similarly to what I have written above?

@gregoiregentil I was able to solve that same error by switching to electron-forge. But now I'm also getting the "Not available for testing" error

@gregoiregentil I'm new to Electron and experiencing my own issues so I'm no expert, but it looks like your electron-builder config may be missing some things required for the mas build. I've included my configs below along with the back story.
@sanjubhambhani @ntbosscher I'm having the same problem with Forge. I was able to get a working build using electron-builder, but I'm still hoping to get Forge working.
I'm using Electron (25.0.0) Forge (6.1.1). I can package with Forge and "make" (dist) with electron-builder (^22.14.13), but I can't figure out how to make with Forge (App Store Connect says "Not Available for Testing" and app crashes on launch).
yarn package ("package": "electron-forge package --arch=universal --platform=mas")
Works: yarn dist ("dist": "yarn package && electron-builder --config builder.config.js")
Doesn't work: yarn make ("make": "electron-forge make --arch=universal --platform=mas")
"main": ".webpack/main", (package.json default from Forge for reference)
Note: The latest version of electron-builder (23.x.x) didn't work. I had to downgrade for it to work (^22.14.13).
// mas build certificates required
security find-identity -v
  4) myHash "Apple Distribution: myEntityName (myTeamId)"
  6) myHash "3rd Party Mac Developer Installer: myEntityName (myTeamId)"
     2 valid identities found

// mas build code signing certificate required
security find-identity -p codesigning -v
  3) myHash "Apple Distribution: myEntityName (myTeamId)"
     1 valid identities found

// builder.config.js
module.exports = {
  appId: 'com.myApp.myAppName',
  copyright: `Copyright © 2023 ${myEntityName}`,
  mac: {
    category: 'public.app-category.myCategory',
    icon: './build/logo.icns',
    target: {
      arch: 'universal',
      target: 'mas',
    },
  },
  mas: {
    entitlements: './build/entitlements.mas.plist',
    entitlementsInherit: './build/entitlements.mas.inherit.plist',
    entitlementsLoginHelper: './build/entitlements.mas.loginhelper.plist',
    hardenedRuntime: false,
    provisioningProfile: './build/Mac_App_Store.provisionprofile',
    type: 'distribution',
  },
}

// entitlements.mas.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>com.apple.security.app-sandbox</key>
    <true/>
    <key>com.apple.security.application-groups</key>
    <string>myTeamId.com.myApp.myAppName</string>
    <key>com.apple.application-identifier</key>
    <string>myTeamId.com.myApp.myAppName</string>
    <key>com.apple.developer.team-identifier</key>
    <string>myTeamId</string>
    <key>com.apple.security.cs.allow-jit</key>
    <true/>
    <key>com.apple.security.cs.allow-unsigned-executable-memory</key>
    <true/>
    <key>com.apple.security.cs.allow-dyld-environment-variables</key>
    <true/>
    <key>com.apple.security.network.client</key>
    <true/>
    <key>com.apple.security.files.user-selected.read-only</key>
    <true/>
    <key>com.apple.security.files.user-selected.read-write</key>
    <true/>
  </dict>
</plist>

// entitlements.mas.inherit.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>com.apple.security.app-sandbox</key>
    <true/>
    <key>com.apple.security.inherit</key>
    <true/>
    <key>com.apple.security.cs.allow-jit</key>
    <true/>
    <key>com.apple.security.cs.allow-unsigned-executable-memory</key>
    <true/>
  </dict>
</plist>

// entitlements.mas.loginhelper.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>com.apple.security.app-sandbox</key>
    <true/>
  </dict>
</plist>

@nathanarritt One thing that stands out to me is that com.apple.security.application-groups is an array of strings.
https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_application-groups
For an approach that worked for me: https://github.com/electron-userland/electron-builder/issues/4553#issuecomment-1967527022


Game screen interface resizing problem

When I resize the window, objects drawn with ShapeRenderer do not scale correctly

Probably this shouldn't bother me, as I am not giving users ability to change window size anyway


missing network space support

Currently k8s-related charms do not support Juju network spaces. Using IP_ADDR_ANY by default in daemon configs helps to some extent but not being explicit or using private-address is a bad practice in general.
If spaces are present in a provider you will most likely end up with an incorrect behavior.
As can be seen below, addresses from <IP_ADDRESS>/21 are used sometimes although the default space binding is to oam-space.
charms use private-address for certain purposes.
https://github.com/kubernetes/kubernetes/blob/master/cluster/juju/layers/kubernetes-worker/reactive/kubernetes_worker.py#L287-L291
Otherwise, bind-address helpfully has a default of binding to <IP_ADDRESS>: for different services:
--bind-address ip                              The IP address for the proxy server to serve on (set to <IP_ADDRESS> for all interfaces) (default <IP_ADDRESS>)
https://kubernetes.io/docs/admin/kube-apiserver/
etcd also uses IPADDR_ANY
ubuntu@qilin:~$ sudo ss -tlpn | grep etcd
LISTEN     0      128    <IP_ADDRESS>:4001                     *:*                   users:(("etcd",pid=16078,fd=6))
LISTEN     0      128         :::2379                    :::*                   users:(("etcd",pid=16078,fd=7))
LISTEN     0      128         :::2380                    :::*                   users:(("etcd",pid=16078,fd=5))

However, one of the etcd servers is specified as having an address in a different subnet from the others.
--etcd-servers https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:2379
ubuntu@empusa:~$ ip -4 -o a
1: lo    inet <IP_ADDRESS>/8 scope host lo\       valid_lft forever preferred_lft forever
2: enp4s0f0    inet <IP_ADDRESS>/21 brd <IP_ADDRESS> scope global enp4s0f0\       valid_lft forever preferred_lft forever
6: enp4s0f0.2730    inet <IP_ADDRESS>/21 brd <IP_ADDRESS> scope global enp4s0f0.2730\       valid_lft forever preferred_lft forever
7: enp4s0f1.2732    inet <IP_ADDRESS>/21 brd <IP_ADDRESS> scope global enp4s0f1.2732\       valid_lft forever preferred_lft forever
8: enp4s0f0.2731    inet <IP_ADDRESS>/21 brd <IP_ADDRESS> scope global enp4s0f0.2731\       valid_lft forever preferred_lft forever

In this case it is not a leader:
ubuntu@empusa:~$ etcdctl cluster-health
member d7b0b5972e8ecb2 is healthy: got healthy result from https://<IP_ADDRESS>:2379
member 209cdd47a369b92a is healthy: got healthy result from https://<IP_ADDRESS>:2379
member 4eea03bbbd50c3c6 is healthy: got healthy result from https://<IP_ADDRESS>:2379
cluster is healthy
ubuntu@empusa:~$ curl -s localhost:4001/debug/vars | grep -iPo 'raftState.*?,'
raftState":"StateFollower",

The rest of the setup is below:
juju spaces
Space               Subnets
admin-space         <IP_ADDRESS>/21
ceph-access-space   <IP_ADDRESS>/21
ceph-replica-space  <IP_ADDRESS>/21
internal-space      <IP_ADDRESS>/24
oam-space           <IP_ADDRESS>/21
                    <IP_ADDRESS>/24
                    <IP_ADDRESS>/24
public-space        <IP_ADDRESS>/21
undefined           <IP_ADDRESS>/16

Dif
juju ssh kubernetes-master/0

ubuntu@gamayun:~$ cat config  | grep server
    server: https://<IP_ADDRESS>:443

ubuntu@gamayun:~$ kubectl --kubeconfig config cluster-info
Kubernetes master is running at https://<IP_ADDRESS>:443
Heapster is running at https://<IP_ADDRESS>:443/api/v1/proxy/namespaces/kube-system/services/heapster
KubeDNS is running at https://<IP_ADDRESS>:443/api/v1/proxy/namespaces/kube-system/services/kube-dns
kubernetes-dashboard is running at https://<IP_ADDRESS>:443/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard
Grafana is running at https://<IP_ADDRESS>:443/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
InfluxDB is running at https://<IP_ADDRESS>:443/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb

juju ssh kubernetes-worker/0
ubuntu@ipotane:~$ kubectl cluster-info
Kubernetes master is running at https://<IP_ADDRESS>:443
Heapster is running at https://<IP_ADDRESS>:443/api/v1/proxy/namespaces/kube-system/services/heapster
KubeDNS is running at https://<IP_ADDRESS>:443/api/v1/proxy/namespaces/kube-system/services/kube-dns
kubernetes-dashboard is running at https://<IP_ADDRESS>:443/api/v1/proxy/namespaces/kube-system/services/kubernetes-dashboard
Grafana is running at https://<IP_ADDRESS>:443/api/v1/proxy/namespaces/kube-system/services/monitoring-grafana
InfluxDB is running at https://<IP_ADDRESS>:443/api/v1/proxy/namespaces/kube-system/services/monitoring-influxdb

ubuntu@ipotane:~$ cat .kube/config | grep server
    server: https://<IP_ADDRESS>:443

ubuntu@gamayun:~$ pgrep -af kube
5666 bash /var/lib/juju/init/jujud-unit-kubernetes-master-0/exec-start.sh
5677 /var/lib/juju/tools/unit-kubernetes-master-0/jujud unit --data-dir /var/lib/juju --unit-name kubernetes-master/0 --debug
25385 /snap/kube-apiserver/27/kube-apiserver --admission-control NamespaceLifecycle,LimitRanger,ServiceAccount,ResourceQuota,DefaultTolerationSeconds --basic-auth-file /root/cdk/basic_auth.csv --etcd-cafile /root/cdk/etcd/client-ca.pem --etcd-certfile /root/cdk/etcd/client-cert.pem --etcd-keyfile /root/cdk/etcd/client-key.pem --etcd-servers https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:2379 --insecure-bind-address <IP_ADDRESS> --insecure-port 8080 --kubelet-certificate-authority /root/cdk/ca.crt --kubelet-client-certificate /root/cdk/client.crt --kubelet-client-key /root/cdk/client.key --logtostderr --min-request-timeout 300 --service-account-key-file /root/cdk/serviceaccount.key --service-cluster-ip-range <IP_ADDRESS>/24 --storage-backend etcd2 --tls-cert-file /root/cdk/server.crt --tls-private-key-file /root/cdk/server.key --token-auth-file /root/cdk/known_tokens.csv --v 4
25399 /snap/kube-controller-manager/18/kube-controller-manager --logtostderr --master http://<IP_ADDRESS>:8080 --min-resync-period 3m --root-ca-file /root/cdk/ca.crt --service-account-private-key-file /root/cdk/serviceaccount.key --v 2
25405 /snap/kube-scheduler/27/kube-scheduler --logtostderr --master http://<IP_ADDRESS>:8080 --v 2

ceQuota,DefaultTolerationSeconds --basic-auth-file /root/cdk/basic_auth.csv --etcd-cafile /root/cdk/etcd/client-ca.pem --etcd-certfile /root/cdk/etcd/client-cert.pem --etcd-
keyfile /root/cdk/etcd/client-key.pem --etcd-servers https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:2379 --insecure-bind-address <IP_ADDRESS> --insecur
e-port 8080 --kubelet-certificate-authority /root/cdk/ca.crt --kubelet-client-certificate /root/cdk/client.crt --kubelet-client-key /root/cdk/client.key --logtostderr --min-
request-timeout 300 --service-account-key-file /root/cdk/serviceaccount.key --service-cluster-ip-range <IP_ADDRESS>/24 --storage-backend etcd2 --tls-cert-file /root/cdk/serv
er.crt --tls-private-key-file /root/cdk/server.key --token-auth-file /root/cdk/known_tokens.csv --v 4
root     25399     1 25399 25399  3 15:18 ?        00:02:27   /snap/kube-controller-manager/18/kube-controller-manager --logtostderr --master http://<IP_ADDRESS>:8080 --min-res
ync-period 3m --root-ca-file /root/cdk/ca.crt --service-account-private-key-file /root/cdk/serviceaccount.key --v 2
root     25405     1 25405 25405  0 15:18 ?        00:00:05   /snap/kube-scheduler/27/kube-scheduler --logtostderr --master http://<IP_ADDRESS>:8080 --v 2
root     31444     1 31444 31444  0 15:21 ?        00:00:00   /usr/local/bin/flanneld -iface=enp4s0f0 -etcd-endpoints=https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:2379 -etcd-certfile=/etc/ssl/flannel/client-cert.pem -etcd-keyfile=/etc/ssl/flannel/client-key.pem -etcd-cafile=/etc/ssl/flannel/client-ca.pem

From a jumphost (got a 'bad' .kube/config):
juju scp kubernetes-master/0:config ~/.kube/config
grep server ~/.kube/config
    server: https://<IP_ADDRESS>:443

time kubectl cluster-info
Kubernetes master is running at https://<IP_ADDRESS>:443
^C

real    0m6.531s
user    0m0.192s
sys     0m0.064s

Changed to a oam-space ip address of the master (better after the change):
grep server ~/.kube/config
    server: https://<IP_ADDRESS>:443

time kubectl cluster-info
Kubernetes master is running at https://<IP_ADDRESS>:443
Heapster is running at https://<IP_ADDRESS>:443/api/v1/namespaces/kube-system/services/heapster/proxy
KubeDNS is running at https://<IP_ADDRESS>:443/api/v1/namespaces/kube-system/services/kube-dns/proxy
kubernetes-dashboard is running at https://<IP_ADDRESS>:443/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy
Grafana is running at https://<IP_ADDRESS>:443/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy
InfluxDB is running at https://<IP_ADDRESS>:443/api/v1/namespaces/kube-system/services/monitoring-influxdb/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

real    0m0.360s
user    0m0.308s
sys     0m0.080s

cat cdk.yaml
variables:
  channel: &channel 1.6/stable
  oam-space: &oam-space oam-space
series: xenial
description: A nine-machine Kubernetes cluster, appropriate for production. Includes a three-machine etcd cluster and three Kubernetes worker nodes.
services:
  easyrsa:
    annotations:
      gui-x: '450'
      gui-y: '550'
    charm: cs:~containers/easyrsa-15
    num_units: 1
    bindings:
      "": *oam-space
  etcd:
    annotations:
      gui-x: '800'
      gui-y: '550'
    charm: cs:~containers/etcd-48
    num_units: 3
    bindings:
      "": *oam-space
  flannel:
    annotations:
      gui-x: '450'
      gui-y: '750'
    charm: cs:~containers/flannel-26
    bindings:
      "": *oam-space
  kubeapi-load-balancer:
    annotations:
      gui-x: '450'
      gui-y: '250'
    charm: cs:~containers/kubeapi-load-balancer-25
    expose: true
    num_units: 1
    bindings:
      "": *oam-space
  kubernetes-master:
    annotations:
      gui-x: '800'
      gui-y: '850'
    charm: cs:~containers/kubernetes-master-47
    num_units: 1
    options:
      channel: *channel
    bindings:
      "": *oam-space
  kubernetes-worker:
    annotations:
      gui-x: '100'
      gui-y: '850'
    charm: cs:~containers/kubernetes-worker-52
    constraints: cores=4 mem=4G
    expose: true
    num_units: 3
    options:
      channel: *channel
    bindings:
      "": *oam-space
relations:
- - kubernetes-master:kube-api-endpoint
  - kubeapi-load-balancer:apiserver
- - kubernetes-master:loadbalancer
  - kubeapi-load-balancer:loadbalancer
- - kubernetes-master:kube-control
  - kubernetes-worker:kube-control
- - kubernetes-master:certificates
  - easyrsa:client
- - etcd:certificates
  - easyrsa:client
- - kubernetes-master:etcd
  - etcd:db
- - kubernetes-worker:certificates
  - easyrsa:client
- - kubernetes-worker:kube-api-endpoint
  - kubeapi-load-balancer:website
- - kubeapi-load-balancer:certificates
  - easyrsa:client
- - flannel:etcd
  - etcd:db
- - flannel:cni
  - kubernetes-master:cni
- - flannel:cni
  - kubernetes-worker:cni

juju run --application kubernetes-worker 'unit-get private-address'
- Stdout: |
    <IP_ADDRESS>
  UnitId: kubernetes-worker/0
- Stdout: |
    <IP_ADDRESS>
  UnitId: kubernetes-worker/1
- Stdout: |
    <IP_ADDRESS>
  UnitId: kubernetes-worker/2

There are certain changes coming up to juju to properly set private-address in relation-data. It used to be SettingsAddress that returned what juju perceived as private-address which is not very well defined (there is a tie-breaker logic for that when multiple network interfaces are present on a machine). A natural choice would be to set private-address to an address equal to a primary address in a default binding space but this behavior was not implemented properly (it is an issue in 2.2.2 and will most likely be there in 2.2.3):
https://bugs.launchpad.net/juju/+bug/1708492 (in short: unit-get private-address is default-binding aware but what gets put into relation data as private-address is not)
Changes coming for cross-model & cross-controller relations address that:
https://github.com/juju/juju/commit/1127c68e9285d80e7371c5ba331b5ea91d6f5ca4#diff-046ccfccf9e885c5ffe51c6721266a32R472
ingressAddress, err := relUnit.IngressAddress()
...
settings["private-address"] = ingressAddress.Value
settings["ingress-address"] = ingressAddress.Value
https://github.com/juju/juju/blob/49e7402/state/relationunit.go#L477
https://github.com/juju/juju/blob/49e7402ea1355292b8e9ae2c24e0e9f98e2f2c49/apiserver/facades/agent/uniter/uniter.go#L1141-L1154
However, those changes are not yet released and the original issue may be avoided by using network-get hook tool instead of unit-get private-address:
https://jujucharms.com/docs/stable/reference-hook-tools#network-get
https://pythonhosted.org/charmhelpers/api/charmhelpers.core.hookenv.html?highlight=network_get_primary_address#charmhelpers.core.hookenv.network_get_primary_address
instead of https://pythonhosted.org/charmhelpers/api/charmhelpers.core.hookenv.html?highlight=network_get_primary_address#charmhelpers.core.hookenv.unit_private_ip

@wwwtyro @hyperbolic2346 I see some merge requests for this issue, has it been resolved or is the support for network spaces still broken?
Cheers

Hey @CalvinHartwell. This isn't resolved. The merged changes cover what we think will be needed, but we haven't had access to an environment to test multiple network spaces on until very recently. There's a good chance we missed something.
The changes are currently in candidate and will go out in the next stable release. But again, I wouldn't expect it to work quite yet.

I think we can close this now. Please reopen if I'm wrong.


about DataParallel（DP）with multi-gpus in testing

Thanks for your great works!
And I have confused that Why it can be achieved with 2 GPUs in the training phase,  however in the testing phase, DataParallel is not working？ So that the test.py only works on one of 2 GPUs, the other one's memory is always zero.
Add:  the param "num_gpu: 2" in the test.yml.
Looking forward to your answer! thanks so much.

Hi, this is because the batch size of dataloader is set to be 1 during the testing phase. See the following code https://github.com/xinntao/BasicSR/blob/3c30fb3661d8fdb4a05fbab793ce47312b09d802/basicsr/data/init.py#L78

@jnjaby yeah, u r right. Thanks for your reminding


Update to Grails 3

Not sure if you are still maintaining this plugin or not and if you have any plans on releasing a Grails 3 version.  If not, I'm happy to take over ownership of the plugin and release the Grails 3 version to Bintray.  Please let me know.

As the original author of the plugin I say: yes, we'd love to see an upgrade to Grails 3. I'm afraid I'm been out of touch with Grails for a while. @berngp is certainly quite busy too. So here's 1 out of 2 votes to follow Bobby's proposal to take over :wink:

I vote for it too so 2 out of 2 votes :).

@bobbywarner I can't transfer you the ownership since you already have a grails-rest project. Let me know what you want to do.

@berngp Ok, great!  Yea, I'll take over ownership of it.  Do you want to merge the pull request and then I'll delete my grails-rest repo so you can transfer ownership?  Please let me know.

@bobbywarner let me know when you mv or rm your repo and I'll transfer the ownership of the project.

@berngp I have deleted my fork repo.  Please transfer anytime.  Thanks!

@bobbywarner done, thanks for stepping up.


React18 refactor Badge

tests meet React18 standards
all stories are tested
all layouts / setups are rendered in stories
scoped CSS without named exports
added description in readme

closes #358

Wow the great Abhinav is back!!!!


Reporting Requirement statuses should be derived

The way statuses are implemented currently as static column data in the reporting_requirement table means that they will not update automatically. We have no mechanism to change the database data based on when a due date passes & so a status will never change to late.
The reporting_requirement statuses should be derived (using a computed column) rather than stored as a data column in the database so that the statuses are fetched and calculated on page load. This means removing the status column from the reporting_requirement table, removing the reporting_requirement_status lookup table and creating a computed column to retrieve that data on reporting_requirement form_change records.
Statuses should be returned by the computed column as follows:
Has future due date & no received date: on_track
Has past due date & no received date: late
Has due date & received date: completed

Users want to be able to override the calculated value of statuses. The statuses should be derived by default, but a user should be able to override them manually

This is the behaviour described in #532 (in progress) and #588 (iceboxed)


Can not run with --bundle

Steps to reproduce:
git clone https://github.com/NativeScript/nativescript-marketplace-demo
cd nativescript-marketplace-demo
tns build android --bundle

Error is:
ERROR in ./examples/chart/area-series-page.xml
Module not found: Error: Can't resolve 'examples/example-base-page' in '/Users/topuzov/Git/nativescript-cli-tests/nativescript-marketplace-demo/app/examples/chart'
 @ ./examples/chart/area-series-page.xml 1:72-109 1:198-235
 @ . sync (root|page)\.(xml|css|js|ts|scss)$
 @ ./app.ts

ERROR in ./examples/chart/line-series-page.xml
Module not found: Error: Can't resolve 'examples/example-base-page' in '/Users/topuzov/Git/nativescript-cli-tests/nativescript-marketplace-demo/app/examples/chart'
 @ ./examples/chart/line-series-page.xml 1:72-109 1:198-235
 @ . sync (root|page)\.(xml|css|js|ts|scss)$
 @ ./app.ts

ERROR in ./examples/chart/pie-series-page.xml
Module not found: Error: Can't resolve 'examples/example-base-page' in '/Users/topuzov/Git/nativescript-cli-tests/nativescript-marketplace-demo/app/examples/chart'
 @ ./examples/chart/pie-series-page.xml 1:72-109 1:198-235
 @ . sync (root|page)\.(xml|css|js|ts|scss)$
 @ ./app.ts

ERROR in ./examples/chart/bar-series-page.xml
Module not found: Error: Can't resolve 'examples/example-base-page' in '/Users/topuzov/Git/nativescript-cli-tests/nativescript-marketplace-demo/app/examples/chart'
 @ ./examples/chart/bar-series-page.xml 1:72-109 1:198-235
 @ . sync (root|page)\.(xml|css|js|ts|scss)$
 @ ./app.ts
.....

No issues with latest version of the app.


Issue a warning when unsupported characters are used in wildcard names

Is your feature request related to a problem? Please describe.
Wildcard names only allow [a-zA-Z0-9_] and when an unsupported character is included in a wildcard name, it is silently ignored (get_wildcard_names returns an empty set). This can lead to confusing error messages like in issue #1349
Describe the solution you'd like
Issue a warning message, something along the lines of "there appears to be an unsupportedcharacter in what seems like a wildcard name. Wildcard names can only include alphanumeric characters and underscore"
Describe alternatives you've considered
Alternative is silently ignoring unsupported characters as it is now. This can cause confusion when troubleshooting a workflow
Additional context
Add any other context or screenshots about the feature request here.

Yes, a warning is a good idea. Happy to receive a PR! Thanks a lot!


WIP adding linear combination option

WIP: Currently, tests only have use_kzg_flag=false

This change is

Codecov Report
Attention: 10 lines in your changes are missing coverage. Please review.

Comparison is base (8256040) 70.83% compared to head (b7681f4) 71.10%.
Report is 2 commits behind head on main.

Files
Patch %
Lines

crates/blockifier/src/transaction/objects.rs
0.00%
3 Missing and 1 partial :warning:

crates/blockifier/src/fee/fee_checks.rs
66.66%
0 Missing and 2 partials :warning:

crates/blockifier/src/fee/gas_usage.rs
88.88%
0 Missing and 2 partials :warning:

crates/blockifier/src/fee/fee_utils.rs
94.73%
0 Missing and 1 partial :warning:

.../blockifier/src/transaction/account_transaction.rs
66.66%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1359      +/-   ##
==========================================
+ Coverage   70.83%   71.10%   +0.27%
==========================================
  Files          59       59
  Lines        7550     7631      +81
  Branches     7550     7631      +81
==========================================
+ Hits         5348     5426      +78
- Misses       1779     1780       +1
- Partials      423      425       +2

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

Trying to fix


FSharpi fails with message Failed to install ctrl-c handler

Please provide a succinct description of the issue.
Repro steps
Provide the steps required to reproduce the problem

install fsharp/fsharp from master into Mono

run fsharpi

Expected behavior
F# Interactive for F# 4.1
Freely distributed under the Apache 2.0 Open Source License

For help type #help;;

Actual behavior
F# Interactive for F# 4.1
Freely distributed under the Apache 2.0 Open Source License

For help type #help;;

> Failed to install ctrl-c handler - Ctrl-C handling will not be available. Error was:
	Exception has been thrown by the target of an invocation.

Known workarounds
None
Related information
Running fsharpi with Mono debug logging shows
Failed to install ctrl-c handler - Ctrl-C handling will not be available. Error was:
	Exception has been thrown by the target of an invocation.Mono: Found assembly remapping for System and was for the same version <IP_ADDRESS>
Mono: Found assembly remapping for System and was for the same version <IP_ADDRESS>

Provide any related information
Mono 5.0.0
fsharp/fsharp master

Must have been something wrong with my local build. HEAD of master fsharp/fsharp from our build server has no issues.
13:53 $ installpkg ~/Downloads/MonoFramework-MDK-<IP_ADDRESS>.macos10.xamarin.universal.pkg
Password:
installer: Package name is Mono Framework
installer: Upgrading at base path /
installer: The upgrade was successful.
✔ ~
13:59 $ fsharpi

F# Interactive for F# 4.1
Freely distributed under the Apache 2.0 Open Source License

For help type #help;;

>

on OSX 10.12.5 Sierra, I was seeing this problem with mono <IP_ADDRESS>. So I brew upgraded to <IP_ADDRESS>, the latest. This is still a problem. I type nothing at the fsharpi prompt, it just crashes itself.
$ fsharpi
Microsoft (R) F# Interactive version 4.1
Copyright (c) Microsoft Corporation. All Rights Reserved.

For help type #help;;

> - Failed to install ctrl-c handler - Ctrl-C handling will not be available. E\
rror was:
    Exception has been thrown by the target of an invocation.Your system doesn'\
t seem to support WinForms correctly. You will
need to set fsi.EventLoop use GUI windows from F# Interactive.
You can set different event loops for MonoMac, Gtk#, WinForms and other
UI toolkits. Drop the --gui argument if no event loop is required.


Error occurs when removing a Quiz Administrator in PKI mode

Physical hardware at the node level.

PR: #2554

https://www.microsoft.com/en-us/industry/microsoft-in-business/business-transformation/2022/05/04/eliminating-data-silos-to-support-value-based-care/

Network all of the silos.


treewide: get rid of platforms.allBut

Motivation for this change
Negative reasoning like allBut is a bad idea with an open world of platforms. Concretely, if we add a new, quite different sort of platform, existing packages with allBut will claim they work on it even though they probably won't.
Also, there's no good/cheap way to implement this with a https://github.com/NixOS/nixpkgs/pull/34444-like strategy.
all is also bad, but at least as a good constructive interpretation of "I work everywhere because I require nothing; so give me nothing". Relatedly, everything we have left can be expressed with horn clauses, allBut couldn't be.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

@dezgeg oh as it turned out, this achieved some of https://github.com/NixOS/nixpkgs/pull/7846


Skipping RCs?

Not in https://typescript.azureedge.net/indexes/pre-releases.json but it was built:

Both 4.2.1 and 4.3.1 are in the pre-releases json


feat(meshservice): adds MeshService detail page

Direct Links:

Listing
Detail

New things:

Ports and Tags in listing rows
Ports and Tags in the summary drawer
New Detail > Overview page with Ports, Tags and Dataplane listing with search and summary drawer.
New Detail > YAML page just repeating the same YAML from the summary drawer

Overall pretty happy we can build all this with almost zero Javascript 🎉
Listing

Listing with summary

Detail

### Detail with summary

Put back in draft, just realised I need to find dataplanes by the MeshService's dataplaneTags not just kuma.io/service

Since I originally PRed this, I've added:

Addresses: Both in listing, summary and detail. I'm assuming there is usually one of these but could be multiple (they truncate if there are lots)
VIPs: Only in the detail page, my thinking being these are more of an internal thing (let me know if this decision is bad). Again, assuming there is usually one of these but could be multiple (they truncate if there are lots)
Zone: In the listing based on labels['kuma.io/zone'] (similar to other areas of the GUI)

In details I think hostnames are more useful than ips

We also show hostnames in the detail page, so both vips and addresses, (sorry I didn't update the screengrabs above after adding this new stuff)

I'm not even totally sure if showing vips is any use, as far as I understand it they're for tproxy right?


Cloning objects should also clone their behaviors

Currently, Component::__clone() will null-out the $_behaviors array:
https://github.com/yiisoft/yii2/blob/3d96a45f6b2ded171c607e20b9f3e39a618ab9cb/framework/base/Component.php#L307-L312
I can see why this is better than leaving $_behaviors alone (those behaviors contain a reference to the original component instance), but I think it would be better if those behaviors were cloned to the new instance as well.
public function __clone()
{
    $this->_events = [];
    $this-> _eventWildcards = [];

    if ($this->_behaviors !== null) {
        $behaviors = array_merge($this->_behaviors);
        $this->_behaviors = null;
        foreach ($behaviors as $name => $behavior) {
            $this->attachBehavior($name, clone $behavior);
        }
}

That way any property values set on the behavior will be maintained on the cloned instance, just like normal properties.
$obj = new MyClassWithBehavior();
$obj->myBehaviorProperty = 'bar';
$obj2 = clone $obj;
echo $obj2->myBehaviorProperty; // should output 'bar'

(related: craftcms/cms#2857)

Yes. It's not backwards compatible and could be done in 2.1. Would you like to send a pull request?

I figured it would be more of a 2.1 thing. Happy to submit a PR.

@samdark ICYMI a PR was submitted for this (#16291).


Bundling .node files (as required by the bindings util)

Great Project! I've been working on identifying an adequate way to handle bundling in nexe And I concluded that a virtual filesystem for modules was the best route, and it looks like fusebox has solved that problem quite well. So my goal is to use it as the primary opt in bundling tool for the project. I had a few questions before I began. (might need separate issues)
While its simple enough to build a .node loader plugin similar to this one
I was wondering if there were any suggestions for enabling support for the bindings module. Its gist, is that it uses an Error object to determine the root path of invokation and then scans some (further) dynamic directories for the .node dll.
Additionally -- Is there a mechanism to emit the bundle in memory instead of writing an output file?
I appreciate any guidance!

@calebboyd welcome and thank you for the kind words :)
Yes, FuseBox takes a great approach to creating a virtual file system.
Did you check FuseBox Dynamic Modules feature http://fuse-box.org/page/loader-api#dynamic-modules?  we use it all the time in our project to dynamically create and load modules.
Regarding other questions @nchanged could you elaborate please.

Welcome @calebboyd
From what I understood you want to modify the behaviour at runtime, Which is possible with plugins.
A simple plugin would look like:
FuseBox.init({
  plugins : {
    myPlugin : {
      transform : (file) = { file.contents = "hello world" }
    }
  }
})

Please describe the logic there, we will help you.

Thanks for your fast replies.

Did you check FuseBox Dynamic Modules feature

I don't think this will help at all for enabling bindings to discover the .node file. I'd also note that it isn't clear in the docs that its referring to the global FuseBox present inside the bundle. It held me a up a bit since the only static method on the FuseBox class is .init. Am I correct in assuming that the dynamic module declarations should be emitted in transforms, Or should they be used in user code?
@nchanged Here is a small example of what i'm trying to accomplish (gist)
You can clone that gist and npm i will emit two bundles
My goal is to have index.js's bundle behave like the index-node.js bundle.
I think this might be possible if I can identify each module that has bindings as a direct dependency. in addition to bindings I'd also want to make it work with node-pre-gyp#find

I think this might be possible if I can identify each module that has bindings as a direct dependency

Attaching to bundleEnd and inspecting context.nodeModules doesn't appear to have dependencies set.
Is there some hook that would work better to pursue my approach (or will that approach even work)

Isn't it easier to process this part
at build time? and write the actual contents?

If you want to add dependencies, try
file.analysis.dependencies.push('./relative-path')

OR
file.analysis.dependencies.push('~/from-root/path')

Isn't it easier to process this part
at build time? and write the actual contents?

Since the bundle is for nexe the goal is a single file. Other than that, when is "build time" if not when fusebox is running?
I noticed that the dependencies don't populate until the files are analyzed. How can I have a plugin trigger for node_modules. It seems if I use a test \.js$ it only triggers for "Your Own Code"

Of course, we analyse it and then populate the dependencies, how else? ;-)
What do you mean? You can trigger any module from your plugin.  And inject any code that triggers anything. Please clarify, maybe easier if you write down the steps

Hah, excuse my naiveté as I discover the api. I found that my .allowExtension call more restrictive than my test regexp.

So it's all good now?

Sorry, I haven't had much of a chance to look into it more.
There isn't much documentation on the ast parameter of the transform function

When is it populated?
If changes are made to the ast do they need to be serialized to file.contents? Or will that be done automatically if ast exists (or when it is created using makeAnalysis)

during the AST traversing
yes, you can set a flag and fusebox will generate the code (requiresRegenation or something)

Haha, Yes, of course. I should've phrased my question differently. It sounds like it is the responsibility of the plugin to invoke "makeAnalysis" if the ast is not already populated when the plugin's transform function is invoked.
Following up with a previous question:
Is there a mechanism to emit the bundle in memory instead of writing to a file? For example, webpack uses memory-fs for this.

would be fairly simple if one could hook into context.bundle.bundleSplit.beforeMasterWrite & context.writeOutput & context.output.writeStaticCache


Launcher doesn't seem to work in wine

Describe the bug/error
Looking at the log it seems to be a JSON parsing error ("2023-12-09 11:02:37.898 +11:00 [ERR] Couldn't login: Couldn't parse json - ExpectedStartOfValueNotFound, < LineNumber: 0 | BytePositionInLine: 0.") followed by an html webpage of some sort.
This launcher was listed as a solution to running Elite Dangerous in Wine here however I can't seem to get it to work.
Thank you!
Debug log
min-ed-launcher.log

Hmm. Maybe since the game hasn’t been opened normally. I will download a virtual machine since it launches well enough there, and then I will try again with the script in the virtual machine, then in wine.  That's something the normal launcher goes through that this one doesn't. You don't have to use the normal launcher though. You can do it through the web interface. https://www.frontierstore.net/frontier_partnerkeys/thirdparty/

Aha! No I have not done that. If I can do it through the web interface that’s great as I can save myself a windows installation. I’ll let you know how it goes.

If you purchased from steam after april 2019, you'll want to use the third party link/section. There should be a button in there that allows you to sign in with steam. Is that what you tried?

Yes I signed into steam on the website on the previous link you gave however it said no available keys were found. Sorry for turning you into tech support by the way haha. Feel free to just ditch me if you want.

Nah, no worries.
I have read that it can take more than 12 hours for frontier to acknowledge the license, though I don't know how true that is.
One of the issues with this game is that authentication problems aren't that uncommon. If it doesn't work after some time, I'd try the normal launcher. If that has issues, you might have to contact frontier support.

Yep will do.!” Thanks so much.

It seemed just waiting seemed to fix the login issue. The game seems to work for the most part. Just some weird resolution things. Thank you!


read colors from template

closes #70

This PR now has px defer to the default template if it's not None, and reads the colors from the template.

Thanks!
This is a case where tests will be useful :)
I’ll add an issue to unit test this function.


Whats is the HFT-Orderbook's main use ?

Love this implementation;
Wondering what you find the main use of it is ?
Do you market make with it across multiple exchanges, by creating a synthetic order book of all the exchanges and use this to allocate the orders ?
Do reach out to me at: vertokli74 at gmail.com
Keen to work together on this; and share my existing system.
Best,
Sam

Hey @samholt ,
glad to hear you like it!
Regarding its use, it was actually just a C excercise. Using it to compile a cross-exchange book would be a use case for it indeed. Coming from crypto, the difficulty with that is though, that it requires an order ID for every order.
While some exchanges provide that, many of them do not (some do not even provide level3 book data) - which makes order tracking difficult this way.  Which is why my systems usually only track level 2 books and disregard granular order specifics.
That's an entirely different scenario, of course, for "proper" financial instruments. Being what it is, crypto is still very much in its baby shoes.
What type of collaboration did you have in mind?
Cheers,
Nils
btw: Pardon that I didn't mail you instead of replying here - I'm currently abroad and it appears my mail service is being blocked.

Excellent,
Currently extending https://github.com/ccxt/ccxt, to implement Websocket's for all the exchanges that support it. Love your previous work on your Websocket's for: https://github.com/nlsdfnbch/bitex. Would you be interested in helping us port it over to ccxt, and begin to integrate all the api functionality alongside the other 90 exchanges, with our active dev team.
Eventually would like to add certain features, such as creating an synthetic order book using most of what you have here with the HFT-Orderbook's, its very well designed and documented.

Absolutely! Although I would like to point out that the websocket were a beta, which since then hasn't been improved. Especially the bitfinex one should perhaps be replaced, depending on what you need.
I have had a look at ccxt  in the past and was quite impressed.

Do you have a slack or gitter channel on which we could discuss the implementation?

Closing this, moved to gitter :)


Fix up crash when calling object_getClass on non object.

This fixes up a crash that was found in Chrome when running on an iOS 15 device.
It did not show up on the simulator.
https://chromium-review.googlesource.com/c/chromium/src/+/3011651
Calling object_getClass on something that isn't an object is at best undefined
behavior.

Hit this same issue when running some tests on ARM-based Macs. The same tests would pass on x86. Pulling in this PR solved the problem.


add simple modifiers to change precision/rounding

I would like to see a simple way to change the precision/rounding.
i.e. in the demo, you could add so that while holding shift changes the rounding to half a cube size when moving it and for rotation round to nearest 90 degrees

If I understood your message correctly, egui-gizmo already has such feature. You can use coarse precision by holding ctrl and finer precision by holding ctrl+shift, although by default the ctrl rotation only rounds to nearest PI/32.0 radians.
You can customize it with snap_distance, snap_angle and snap_scale in Gizmo. https://docs.rs/egui-gizmo/latest/egui_gizmo/struct.Gizmo.html#method.snap_angle. Is this what you were looking for?

Yes, that's exactly it. Thanks!
On Wed, 31 Aug 2022, 13:26 Urho Laukkarinen, @.***>
wrote:

If I understood your message correctly, egui-gizmo already has such
feature. You can use coarse precision by holding ctrl and finer precision
by holding ctrl+shift, although by default the ctrl rotation only rounds to
nearest PI/32.0 radians.
You can customize it with snap_distance, snap_angle and snap_scale in
Gizmo.
https://docs.rs/egui-gizmo/latest/egui_gizmo/struct.Gizmo.html#method.snap_angle.
Is this what you were looking for?
—
Reply to this email directly, view it on GitHub
https://github.com/urholaukkarinen/egui-gizmo/issues/12#issuecomment-1232811236,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPIOP4V3B3H7FU7GMN2CJLV346OXANCNFSM6AAAAAAQA2MPXA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Copy public zstd_errors.h into output directory

The common/zstd_errors.h header file is also part of the public
interface of the zstd library. Copy it into the output directory, like
the upstream build system does 0, so that downstream dependencies can
find it.

Thanks for the PR!

Thanks for the quick merge! Any idea when the next release will be
published?
On Tue, Oct 22, 2019 at 4:49 PM Alexandre Bury<EMAIL_ADDRESS>wrote:

Thanks for the PR!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gyscos/zstd-rs/pull/68?email_source=notifications&email_token=AAGXSIFLCWRQ5PS7342Y4UDQP5RMHA5CNFSM4JC5R4ZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB7EZ2A#issuecomment-545148136,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGXSIEFYC2K52NEGXEPU23QP5RMHANCNFSM4JC5R4ZA
.


can add content view like Android Dialog?

The library doesn't even exist yet :)
But my experimenting has been promising and I do have a working solution. I just need to work out all the kinks. I'll add complete instructions to the README within the next few hours.

Okay, I've added some instructions.
Closing this for now, do let me know if you still have anything you'd like to clarify.


API response with cafe_version even when not in cafe mode

https://github.com/textileio/go-textile/blob/master/core/api.go#L103
not sure the best way to go here, perhaps
cafe_version should be returned only when in cafe mode
api_version should be returned always (since the api is running).
or maybe they will always be the same, so just call it api_version

Ah, okay. So this is the same number that is contained in the URL actually api/v0/ == cafe_version: 0. What I need here is more like the minor version so clients can uncover breaking changes a bit faster.

That would be node_version


coin daemon: RPC -getinfo deprecated in bitcoin 0.16

the RPC command was intermediately (bitcoin master 0.15.99) removed totally and now at the 0.16 release it's back responding with the DEPRECATED message and no information.
This makes us believe we can't connect to the node....

It’s been replaced with three new commands. The CLI still allows it with a parameter to gather the old information and then merge it into getinfo format.
If someone wants to address this here an idea to make it compatible with old versions:

Run getinfo and check the output
If OK, return data
If invalid, run the new commands and merge data into old getinfo format

This will allow us to continue using it for all these other coins that have not upgraded to the new commands.
Other places affected could be the admin dashboard and wallet info page.

As asked by @HashUnlimited, I updated the code and added compatibility with Bitcoin 0.16:
#2714

Already merged into Development, I'll close this and happy testing guys.


Historical Task: Integration + E2E testing + Code review

#Description
Historical task Integration with api + testing + code review

Please add your planning poker estimate with ZenHub @vivek-devtron

Please add your planning poker estimate with ZenHub @sohel-rp


Support for custom protected headers in t_cose_sign1_encode_parameters

Suggesting to extend t_cose_sign1_encode_parameters with custom parameters handling.
One of the possible options - a callback(ctx) to be called after setting base parameters, so users can add more custom fields.

Hi @laurencelundblade, could you please let me know if this's a valid suggestion?
We were researching means to pass more protected headers whilst working on https://github.com/microsoft/CCF/issues/6445.
We ended up introducing a more complex signing code with encode_paremeters_.._ replaced(). However, if you think there're other (better) ways of dealing with this issue, we'll very much appreciate hearing your thoughts on this.
cc @achamayou

Hi,
The t_cose dev branch supports custom parameters in the t_cose_sign_sign interface. While there's a fair bit of work to do on the dev branch the parameters part is pretty stable. It works by passing in a linked list of header parameters you want added. It works for COSE_Sign, COSE_Sign1, COSE_Encrypt, COSE_Recipient...
Maybe you want counter signatures? My thought there was to use something specific to counter signatures rather the (simple) extended parameter mechanism in the dev branch.
While the dev branch is compatible with the main branch, a switch to the dev branch is possibly a big thing for you because the dev branch is a big expansion of functionality and is not as stable.

Thank you very much for your reply. We went with a workaround this time, but will track the progress of the dev branch for the future.

Maybe you want counter signatures? My thought there was to use something specific to counter signatures rather the (simple) extended parameter mechanism in the dev branch.

For our purposes we specifically needed to set custom parameters (more details on spec).


Is there an EXAMPLE of a refresh scheme? (Migrating from @nuxtjs/auth-next)

Discussed in https://github.com/sidebase/nuxt-auth/discussions/401

Originally posted by akiot-b May 19, 2023
I was using @nuxtjs/auth-next with Nuxt2 but am thinking of migrating to sidebase/nuxt-auth with Nuxt3.
I can't find an example that corresponds to the refresh scheme in @nuxtjs/auth-next. Where can I find it?
In @nuxtjs/auth-next, the following definition was used. nuxt.config.js
  auth: {
    // https://dev.auth.nuxtjs.org/schemes/refresh.html#usage
    localStorage: false,
    cookie: {
      options: {
        secure: process.env.NODE_ENV === 'production',
        expires: 30,
      },
    },
    strategies: {
      localRefresh: {
        scheme: 'refresh',
        token: {
          property: 'detail.access_token',
          maxAge: 60 * 15,
          type: 'Bearer',
        },
        refreshToken: {
          property: 'detail.refresh_token',
          data: 'refresh_token',
          maxAge: 60 * 60 * 24 * 30,
        },
        user: {
          property: 'detail.user',
        },
        autoLogout: true,
        endpoints: {
          login: {
            url: '/api/auth/signin',
            method: 'post',
            withCredentials: true,
          },
          refresh: {
            url: '/api/auth/refresh',
            method: 'post',
            withCredentials: true,
          },
          user: {
            url: '/api/auth/user',
            method: 'get',
          },
          logout: {
            url: '/api/auth/signout',
            method: 'post',
            withCredentials: true,
          },
        },
      },
    },
  },

Currently there is no refresh schema provider in this package. There is a PR, that aims to add support for this here: https://github.com/sidebase/nuxt-auth/pull/373
Lets follow up the conversation and testing there, to keep it in one place!


Add multicore flag

The PackPipeline makes only use of one AIE tile so far, by tiling to (16,64) at the first tiling operation.
With the new flag iree-amdaie-use-multicore this behaviour can be adapted, namely

iree-amdaie-use-multicore=2: tile to (16,128) and use two AIE tiles
iree-amdaie-use-multicore=4: tile to (16,256) and use four AIE tiles.

By default, a single tile is used. Values different than 1, 2 or 4 result in an error.
Note that this PR is built on top of https://github.com/nod-ai/iree-amd-aie/pull/127, assuming that this will soon be merged.
TODO:
Currently this flag is ignored within the PadPipeline and SimplePackPipeline, is such a case distinction also desired for these?

I am currently ignoring the use-multicore flag except for the PackPipeline. I could also adapt the pad-pipeline for different numbers of cores, but I am unsure about the current usage of cores therein. From the dump after ParallelToHerd, I would interpret that all four cores are used here:
%c2_8 = arith.constant 2 : index
%c2_9 = arith.constant 2 : index
air.herd @herd_0  tile (%arg2, %arg3) in (%arg4=%c2_8, %arg5=%c2_9) args(%arg6=%alloc_3, %arg7=%alloc, %arg8=%alloc_2) : memref<8x8xi32, 1 : i32>, memref<8x256xi8, 1 : i32>, memref<256x8xi8, 1 : i32> {
   ...
}

@yzhang93 are you familiar with this?
If this interpretation is correct, I would set useMulticore=4 by default for this pipeline, and for other values throw an error.

Name suggestion: iree-amd-aie-num-cores.  Currently the flag name sounds to me like a binary "use or don't use multicore". Do you know if 'cores' or 'tiles' is more commonly used?

Name suggestion: iree-amd-aie-num-cores. Currently the flag name sounds to me like a binary "use or don't use multicore". Do you know if 'cores' or 'tiles' is more commonly used?

True, I prefer your suggestion. I have heard both in verbal use, but within the AIR dialect I have seen 'tile' so perhaps that is more specific?

@yzhang93 @MaheshRavishankar Is this interpretation correct? And are you interested in an adaptable number of cores for the Pad and SimplePack pipelines? If so, I would set iree-amdaie-num-cores=4 by default for this pipeline, and for other values adapt the tiling parameters or throw an error.

Thanks for your contribution. I think currently we should use this flag to pack pipeline only, and we will adapt it to other pipelines later.

Actually if you dont mind I have a suggeston that will help us in the future. Introduce a new struct called AIEConfig in KernelDispatch.h and populate it with just one filed num_cores. I expect we can adapt this to capture the configuration better over time, but this would have been plumbed through to begin with.

Sure that makes sense, the struct would be right next to the enum for the pass pipeline. I will then have this struct be filled depending on the flag, is that what you mean? Or do you suggest to leave out the flag altogether and only use the value hardcoded in the struct?
Our default values are 1 for the pack pipeline and - as it seemed to me from later dumps - 4 for the pad pipeline.

I was wondering whether at some point the information on spatial tiling would become part of https://github.com/openxla/iree/blob/8c4c3e03ff4e7797eaf00e2682e63971096fabfd/compiler/src/iree/compiler/Codegen/Dialect/Codegen/IR/IREECodegenAttrs.td#L177 upstream, so that it can be passed together with tile_sizes to the matmul op @yzhang93  @MaheshRavishankar For now however I am fine with leaving the handling like it is here, please let me know if there is anything left to adapt!

Thanks!

I just rebased and ran CI again, if you agree to these changes @yzhang93 I will merge this PR.


az bot authsetting list fails in pipelines build

Tool
Name: az bot
Version: latest
OS: Windows
Describe the bug
I'm running an Azure Pipelines build using the botskills CLI, which calls az bot commands.
The command az bot authsetting list -n {botName} -g {botName} --output json (this is to add authentication providers from Skills connected to the VA)
This fails with:

I suspect it's related to the warning format or that json is outputted?

To Reproduce
Steps to reproduce the behavior:

Run az bot authsetting list -n {botName} -g {botName} --output json in a Powershell task in a build pipeline with error handling set to Continue.

Expected behavior
A clear and concise description of what you expected to happen.
The command works as expected.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
[bug]

Spoke with @stevengum and he is looking into this today.

@Batta32 were you able to repro the problem described in microsoft/botbuilder-tools#1393?
I think this would be a popular issue if the problem was widespread, but haven't seen more tickets from users.
@ryanlengel, @lauren-mills is this issue still happening?

comment in  https://github.com/microsoft/botframework-solutions/issues/2801

Changing tags to investigate, p1, and R9.

The underlying mechanism for the warning message is a feature of the base Azure CLI, not of az bot
If this was a recurring problem, we would have received more customer reports
The Solutions team has moved away from using az bot authsetting due to design choices in their offerings

Closing due to inactivity and lack of customer reports.


[FR] Better messaging on in-progress parsing

//Was: Date/Time related commands not working in Alfred 3 on OSX 10.11.5
Been using this for a few days and it's a great workflow! But I'm having issues where commands that start with a date keywork (today, tomorrow, or a date string) or simply a time (at 6pm) result in a "Reminder command not recognized" message. I looked at some other tickets and went through the more recent forum posts but couldn't find anything that worked.
I tried uninstalling and reinstalling and also repairing disk permissions and when I run 'rtest' get the output below (which seems to indicate that things are fine). What else can I do to provide info to help debug? Would love to keep using this as shared lists are an important part of my team workflows. Thanks!
Test results:
OS version: 10.11.5 (0 seconds)
Current date: Thursday, June 23, 2016 at 12:34:23 PM (0 seconds)
Initialize workflow path: /Users/lrhyne/Library/Application Support/Alfred 3/Alfred.alfredpreferences/workflows/user.workflow.3598351E-2D79-4D11-9F23-2747AC0BD8C3 (0 seconds)
Initialize alfred-library: OK (0 seconds)
Initialize update-library: OK (0 seconds)
Initialize wf-library: OK (0 seconds)
Initialize plist-library: OK (0 seconds)
Reminders.app state: Running (0 seconds)
Fetch reminder count: 12 (3 seconds)
Fetch reminder info: OK (4 seconds)
Fetch reminder list count: 3 (0 seconds)
Fetch reminder list info: OK (0 seconds)
Run cache process: SKIPPED (0 seconds)
Fetch cache timestamp: SKIPPED (0 seconds)
Fetch cached reminder count: SKIPPED (0 seconds)
Test basic query: OK (0 seconds)
Test today query: OK (0 seconds)
Test in n minutes query: OK (0 seconds)
Test in n hours query: OK (0 seconds)
Test in n days query: OK (0 seconds)
Test in n days y hours query: OK (0 seconds)
Test in n hours y minutes query: OK (0 seconds)
Test at time query: OK (0 seconds)
Test tomorrow at time query: OK (0 seconds)
Test in x list query: OK (0 seconds)
Subtitle generation: OK (0 seconds)
Test basic reminder filtering: OK (0 seconds)
Test remind today reminder filtering: OK (0 seconds)
Test due tomorrow reminder filtering: OK (0 seconds)
Test reminder list filtering: OK (0 seconds)
Test version-check response: OK (0 seconds)
Current unix time: 1.46671047E+9 (0 seconds)
Simple JSON: OK (0 seconds)
Test execution time: 7 seconds

After more playing with this I realized that I was just being thrown off by the error messaging and simply needed to continue through using the appropriate syntax. Probably doesn't even warrant an FR to improve the text flow here, but it would be nice if instead of giving the generic error, it instead went ahead with the nice parsed text response that you get once you've moved past the date/time portion of the syntax into the reminder text.

The options for doing so are somewhat limited, but I'll take another crack at it next time I go through the code.

Fixed in https://github.com/surrealroad/alfred-reminders/commit/2241da9e15bd6a16b90e10d71fec9e0a3f7d31ab


chocolatey package

I have made a choco package to install apt-cyg, because the original cyg-get does not work.
This is just a wrapper around apt-cyg.
Hope this is okay.
Here is the project file:
https://github.com/chantisnake/apt-cyg-powershell
Here is the choco page:
https://chocolatey.org/packages/apt-cyg/0.1

@chantisnake choco install apt-cyg fails for me.
How can i install your choco package :) ?

choco install apt-cyg -version 0.1

they still haven't pass my package, because when install Cygwin fails.
I will try to talk to them these days.

@chantisnake Did this ever end up getting anywhere?
(I noticed you in the end took the package down yourself?)

the package remain unlisted for too long, I therefore self-rejected it...
all the file can still be find here