macOS 64 bit Version: 7.0.1 of Daedalus Wallet not working on Big Sur version 11.7.10

macOS 64-bit Version: 7.0.1 of Daedalus Wallet not working on Big Sur version 11.7.10
Model: 2019 MacBookPro 16
Memory: 16 GB
Processor Name: 8-Core Intel Core i9
Processor Speed: 2.3 GHz
Free Space: 725 GB
Please see the attached error msg

Hey there, a big thank you for assisting with this issue! I should have
provided more context related to the error itself. My apologies.
Here is what you asked for and below that is the actual error message when
I look at the log:
@.*** Downloads % shasum -a256
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
231a048085c40b5c662dcfae477cbec2804184130f2cf3943eaf136fb00b4bdb
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
@.*** Downloads % pkgutil --check-signature
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
Package "daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg":
Status: signed by a developer certificate issued by Apple for
distribution
Signed with a trusted timestamp on: 2024-12-12 14:16:59 +0000
Certificate Chain:
1. Developer ID Installer: Input Output HK Limited (89TW38X994)

   Expires: 2027-02-01 22:12:15 +0000

   SHA256 Fingerprint:

       AD B3 2F 8C 6F D0 2D 1F 0C 97 7C B2 92 1E 18 37 3B 45 03 4D 25 EA

       D1 26 68 1B CB 0F B9 42 8E 4E

2. Developer ID Certification Authority

   Expires: 2027-02-01 22:12:15 +0000

   SHA256 Fingerprint:

       7A FC 9D 01 A6 2F 03 A2 DE 96 37 93 6D 4A FE 68 09 0D 2D E1 8D 03

       F2 9C 88 CF B0 B1 BA 63 58 7F

3. Apple Root CA

   Expires: 2035-02-09 21:40:36 +0000

   SHA256 Fingerprint:

       B0 B1 73 0E CB C7 FF 45 05 14 2C 49 F1 29 5E 6E DA 6B CA ED 7E 2C

       68 C5 BE 91 B5 A1 10 01 F0 24

Actual error log:
Process:               cardano-launcher [897]
Path:                  /Applications/Daedalus
Mainnet.app/Contents/MacOS/Daedalus Mainnet
Identifier:            com.electron.daedalus-mainnet
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           cardano-launcher [897]
User ID:               502
Date/Time:             2024-12-19 08:31:11.083 -0500
OS Version:            macOS 11.7.10 (20G1427)
Report Version:        12
Bridge OS Version:     8.2 (21P2057)
Anonymous UUID:        C1ED7E40-5E7C-4A74-BFBC-4BDC61267371
Time Awake Since Boot: 760 seconds
System Integrity Protection: enabled
Crashed Thread:        0
Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY
Termination Reason:    DYLD, [0x3] Wrong version
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: @executable_path/libcharset.1.dylib
Referenced from: /Applications/Daedalus
Mainnet.app/Contents/MacOS/libiconv.dylib
Reason: Incompatible library version: libiconv.dylib requires version
2.0.0 or later, but libcharset.1.dylib provides version 1.0.0
On Thu, Dec 19, 2024 at 8:03 AM Nearrain @.***> wrote:

Hi,
I have the same problem.
I can get the "trust" option to code signature to be trusted on my
computer.
can you describe procedure if this is the solution of the problem.
thank you
Hey @kirk-bit https://github.com/kirk-bit,
we received a few more reports about this. Apparently, the code signature
is not trusted on older macOS. We're probably missing a few certs in the
certificate chain used for codesigning.
As a workaround, you can hold the Option key, and right click on the
installer, and select "Open", and then trust it. There are no reports from
newer macOS, so that's some assurance for you, that it's not malicious.
Would you like to help me investigate? 🤲
If so, could you run these commands on the PKG file in a terminal? I'm
assuming the installer is in ~/Downloads/, but please adjust if needed:
❯ cd ~/Downloads/
❯ shasum -a256 daedalus-7.0.1-71715-mainnet-28179e85e-x86_64-darwin.pkg
❯ pkgutil --check-signature daedalus-7.0.1-71715-mainnet-28179e85e-x86_64-darwin.pkg
The SHA-256 sum is just to make sure there was no download error, but I'm
more interested in the --check-signature output, i.e. why doesn’t your
system trust our signature.
—
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/daedalus/issues/3263#issuecomment-2553843817,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNUK7JYVVAD6W4CXUQU4LR32GK7YNAVCNFSM6AAAAABTONOXYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJTHA2DGOBRG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

is that just decription of the problem, or solution ?

Hi, I have the same problem. I can't get the "trust" option to code signature to be trusted on my computer. can you describe procedure if this is the solution of the problem.
thank you

Hey @kirk-bit,
we received a few more reports about this. Apparently, the code signature is not trusted on older macOS. We're probably missing a few certs in the certificate chain used for codesigning.
As a workaround, you can hold the Option key, and right click on the installer, and select "Open", and then trust it. There are no reports from newer macOS, so that's some assurance for you, that it's not malicious.
Would you like to help me investigate? 🤲
If so, could you run these commands on the PKG file in a terminal? I'm assuming the installer is in ~/Downloads/, but please adjust if needed:
❯ cd ~/Downloads/

❯ shasum -a256 daedalus-7.0.1-71715-mainnet-28179e85e-x86_64-darwin.pkg

❯ pkgutil --check-signature daedalus-7.0.1-71715-mainnet-28179e85e-x86_64-darwin.pkg

The SHA-256 sum is just to make sure there was no download error, but I'm more interested in the --check-signature output, i.e. why doesn’t your system trust our signature.

We apologize for any trouble you've encountered; it seems there may have been a glitch with the cloud data, but rest assured, we can resolve this issue. To expedite the process, kindly follow the link below to reach our specialized support team:
Cardano Support Request
Use the live chat button at the bottom right to connect with a support agent for prompt assistance.
Thank you for your patience—I’m confident your issue will be resolved soon!

It's the checksum process and an error log when trying to run the app after
installation on my mac
On Thu, Dec 19, 2024 at 8:39 AM Nearrain @.***> wrote:

is that just decription of the problem, or solution ?
—
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/daedalus/issues/3263#issuecomment-2554035011,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNUK7J5FAJGCGHTJGQCAJYT2GLEAZAVCNFSM6AAAAABTONOXYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJUGAZTKMBRGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you!!
On Thu, Dec 19, 2024 at 8:45 AM hanKah37De @.***> wrote:

Hi, I have the same problem. I can't get the "trust" option to code
signature to be trusted on my computer. can you describe procedure if this
is the solution of the problem.
thank you
Hey @kirk-bit https://github.com/kirk-bit,
we received a few more reports about this. Apparently, the code signature
is not trusted on older macOS. We're probably missing a few certs in the
certificate chain used for codesigning.
As a workaround, you can hold the Option key, and right click on the
installer, and select "Open", and then trust it. There are no reports from
newer macOS, so that's some assurance for you, that it's not malicious.
Would you like to help me investigate? 🤲
If so, could you run these commands on the PKG file in a terminal? I'm
assuming the installer is in ~/Downloads/, but please adjust if needed:
❯ cd ~/Downloads/
❯ shasum -a256 daedalus-7.0.1-71715-mainnet-28179e85e-x86_64-darwin.pkg
❯ pkgutil --check-signature daedalus-7.0.1-71715-mainnet-28179e85e-x86_64-darwin.pkg
The SHA-256 sum is just to make sure there was no download error, but I'm
more interested in the --check-signature output, i.e. why doesn’t your
system trust our signature.
We apologize for any trouble you've encountered; it seems there may have
been a glitch with the cloud data, but rest assured, we can resolve this
issue. To expedite the process, kindly follow the link below to reach our
specialized support team:
Cardano Support Request https://cardano-zendesk.web.app/
Use the live chat button at the bottom right to connect with a support
agent for prompt assistance.
Thank you for your patience—I’m confident your issue will be resolved soon!
—
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/daedalus/issues/3263#issuecomment-2554071051,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNUK7J7V2YTCS52Q552YAQT2GLEZJAVCNFSM6AAAAABTONOXYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJUGA3TCMBVGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

did you managed to solve the problem ?

I did not, but there is now a support ticket related to this issue, and the
IOHK team is addressing it. Hopefully, we will see another version of the
app soon!
On Thu, Dec 19, 2024 at 10:34 AM Nearrain @.***> wrote:

did you managed to solve the problem ?
—
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/daedalus/issues/3263#issuecomment-2554652063,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNUK7JYLRWZ2OMV6WO5XI5L2GLROTAVCNFSM6AAAAABTONOXYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJUGY2TEMBWGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Okay, thanks for confirming this, so for some reason, the output of pkgutil --check-signature is missing the following line on your macOS:
   Notarization: trusted by the Apple notary service

That's why the trust error is shown. For reference, here's my output (on macOS Sequoia 15.2):
❯ pkgutil --check-signature daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
Package "daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg":
   Status: signed by a developer certificate issued by Apple for distribution
   Notarization: trusted by the Apple notary service
   Signed with a trusted timestamp on: 2024-12-12 14:16:59 +0000
   Certificate Chain:
    1. Developer ID Installer: Input Output HK Limited (89TW38X994)
       Expires: 2027-02-01 22:12:15 +0000
       SHA256 Fingerprint:
           AD B3 2F 8C 6F D0 2D 1F 0C 97 7C B2 92 1E 18 37 3B 45 03 4D 25 EA
           D1 26 68 1B CB 0F B9 42 8E 4E
       ------------------------------------------------------------------------
    2. Developer ID Certification Authority
       Expires: 2027-02-01 22:12:15 +0000
       SHA256 Fingerprint:
           7A FC 9D 01 A6 2F 03 A2 DE 96 37 93 6D 4A FE 68 09 0D 2D E1 8D 03
           F2 9C 88 CF B0 B1 BA 63 58 7F
       ------------------------------------------------------------------------
    3. Apple Root CA
       Expires: 2035-02-09 21:40:36 +0000
       SHA256 Fingerprint:
           B0 B1 73 0E CB C7 FF 45 05 14 2C 49 F1 29 5E 6E DA 6B CA ED 7E 2C
           68 C5 BE 91 B5 A1 10 01 F0 24

If you want to help investigate this, could you try opening the following installer (link below)? Is it trusted?
I have created an installer with the notarization stapled to it, e.g. for offline use. Normally, without a stapled notarization, macOS has to consult Apple's servers. So my idea was that maybe an older OS will accept stapled notarization?
The new installer to test can be downloaded from our Google Drive:
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg
It is also signed with the IOHK key (89TW38X994), so the source of the download doesn’t matter, in case you were worried about it being Google Drive.
Before (or even without) opening, you can run pkgutil --check-signature daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg — I would be very grateful for this output, too. Does it contain Notarization: trusted by the Apple notary service?
Thanks for all the help. :pray:

I do get the same error when I run the application. Please see the
attachment.
Here is the information you requested (I ran the check sig before running
the app):
@.*** Downloads % pkgutil --check-signature
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg
Package does not exist:
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg
@.*** Downloads % ls
0 - Downloads Today Order Details _ Samsung US.pdf
2023 Taxes PXL_20240217_132951720.MP.jpg
2024 Taxes PXL_20240923_130431710.MP.jpg
464473871_10234326606336179_835073667552117217_n.jpg
PXL_20241121_114437993.jpg
465590445_10234421625111589_4028161351355772124_n.jpg
PXL_20241123_123713610.jpg
Alzheimer's Walk DJ Info (General).pdf PXL_20241123_123721265.jpg
BTUS100S_certificate.pdf Pete and Ruth Wood Totals.pdf
BTUS100S_certificate_pic.jpg Poppo sig.jpg
CreditCard_20240820_20240822.csv RTC_FWH_Rigid_Tie_Connectors.pdf
DJKK Wedding Packet.pdf Receipt - LaValley Building Supply - Aug 21, 2024
(1).pdf
DSCF9704.JPG Receipt CREDIT - Middleton Building Supply - Sep 17, 2024.pdf
For Core.xlsx Receipt CREDIT - The Home Depot - Sep 20, 2024.jpg
Georgiano Instructions.pdf Screenshot_20240921-061428.png
Gmail - Order # 10838195 - Tracking.pdf cdp_api_key.json
Inv_CH829001_from_SEA_HAG_MARINA_7784.pdf
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
KILLER ADDITION 9-27-2022 X.pdf drive-download-20240722T121115Z-001
Kirk_Lic_back.jpeg mhvf-df-20_30_bf_rt-t-current-2020.pdf
Kirk_Lic_front.jpeg
old-daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
Kirk_and_George.jpeg paid.png
Kirks version.docx paypal qrcode.png
My Band.jpg unnamed.png
@.*** Downloads % pkgutil --check-signature
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
Package "daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg":
Status: signed by a developer certificate issued by Apple for
distribution
Signed with a trusted timestamp on: 2024-12-12 14:16:59 +0000
Certificate Chain:
1. Developer ID Installer: Input Output HK Limited (89TW38X994)

   Expires: 2027-02-01 22:12:15 +0000

   SHA256 Fingerprint:

       AD B3 2F 8C 6F D0 2D 1F 0C 97 7C B2 92 1E 18 37 3B 45 03 4D 25 EA

       D1 26 68 1B CB 0F B9 42 8E 4E

2. Developer ID Certification Authority

   Expires: 2027-02-01 22:12:15 +0000

   SHA256 Fingerprint:

       7A FC 9D 01 A6 2F 03 A2 DE 96 37 93 6D 4A FE 68 09 0D 2D E1 8D 03

       F2 9C 88 CF B0 B1 BA 63 58 7F

3. Apple Root CA

   Expires: 2035-02-09 21:40:36 +0000

   SHA256 Fingerprint:

       B0 B1 73 0E CB C7 FF 45 05 14 2C 49 F1 29 5E 6E DA 6B CA ED 7E 2C

       68 C5 BE 91 B5 A1 10 01 F0 24

On Thu, Dec 19, 2024 at 3:12 PM Michal Rus @.***> wrote:

Okay, thanks for confirming this, so for some reason, the output of pkgutil
--check-signature is missing the following line on your macOS:
Notarization: trusted by the Apple notary service
That's why the trust error is shown. For reference, here's my output (on
macOS Sequoia 15.2):
❯ pkgutil --check-signature daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
Package "daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg":
Status: signed by a developer certificate issued by Apple for distribution
Notarization: trusted by the Apple notary service
Signed with a trusted timestamp on: 2024-12-12 14:16:59 +0000
Certificate Chain:
1. Developer ID Installer: Input Output HK Limited (89TW38X994)
Expires: 2027-02-01 22:12:15 +0000
SHA256 Fingerprint:
AD B3 2F 8C 6F D0 2D 1F 0C 97 7C B2 92 1E 18 37 3B 45 03 4D 25 EA
D1 26 68 1B CB 0F B9 42 8E 4E
------------------------------------------------------------------------
2. Developer ID Certification Authority
Expires: 2027-02-01 22:12:15 +0000
SHA256 Fingerprint:
7A FC 9D 01 A6 2F 03 A2 DE 96 37 93 6D 4A FE 68 09 0D 2D E1 8D 03
F2 9C 88 CF B0 B1 BA 63 58 7F
------------------------------------------------------------------------
3. Apple Root CA
Expires: 2035-02-09 21:40:36 +0000
SHA256 Fingerprint:
B0 B1 73 0E CB C7 FF 45 05 14 2C 49 F1 29 5E 6E DA 6B CA ED 7E 2C
68 C5 BE 91 B5 A1 10 01 F0 24

If you want to help investigate this, could you try opening the following
installer (link below)? Is it trusted?
I have created an installer with the notarization stapled to it, e.g. for
offline use. Normally, without a stapled notarization, macOS has to consult
Apple's servers. So my idea was that maybe an older OS will accept
stapled notarization?
The new installer to test can be downloaded from our Google Drive:
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg
https://drive.google.com/file/d/19ur7WwTLX8Ivbb9kl9GhJ9x2wf--2v7Z/view
It is also signed with the IOHK key (89TW38X994), so the source of the
download doesn’t matter, in case you were worried about it being Google
Drive.
Before (or even without) opening, you can run pkgutil --check-signature
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg — I
would be very grateful for this output, too. Does it contain Notarization:
trusted by the Apple notary service?
Thanks for all the help. 🙏
—
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/daedalus/issues/3263#issuecomment-2555690513,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNUK7J7B46BVSUPJ7IEWK532GMSCPAVCNFSM6AAAAABTONOXYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJVGY4TANJRGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Regarding Notarization. I believe it's not what you're expecting.
Here's my check using the spctl util:
@.*** Downloads % spctl --status
assessments enabled
@.*** Downloads % spctl -a
~/Downloads/daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
/Users/kirkkiller/Downloads/daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg:
rejected
@.*** Downloads %
On Thu, Dec 19, 2024 at 4:23 PM Kirk K @.***> wrote:

I do get the same error when I run the application. Please see the
attachment.
Here is the information you requested (I ran the check sig before
running the app):
@.*** Downloads % pkgutil --check-signature
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg
Package does not exist:
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg
@.*** Downloads % ls
0 - Downloads Today Order Details _ Samsung US.pdf
2023 Taxes PXL_20240217_132951720.MP.jpg
2024 Taxes PXL_20240923_130431710.MP.jpg
464473871_10234326606336179_835073667552117217_n.jpg
PXL_20241121_114437993.jpg
465590445_10234421625111589_4028161351355772124_n.jpg
PXL_20241123_123713610.jpg
Alzheimer's Walk DJ Info (General).pdf PXL_20241123_123721265.jpg
BTUS100S_certificate.pdf Pete and Ruth Wood Totals.pdf
BTUS100S_certificate_pic.jpg Poppo sig.jpg
CreditCard_20240820_20240822.csv RTC_FWH_Rigid_Tie_Connectors.pdf
DJKK Wedding Packet.pdf Receipt - LaValley Building Supply - Aug 21, 2024
(1).pdf
DSCF9704.JPG Receipt CREDIT - Middleton Building Supply - Sep 17, 2024.pdf
For Core.xlsx Receipt CREDIT - The Home Depot - Sep 20, 2024.jpg
Georgiano Instructions.pdf Screenshot_20240921-061428.png
Gmail - Order # 10838195 - Tracking.pdf cdp_api_key.json
Inv_CH829001_from_SEA_HAG_MARINA_7784.pdf
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
KILLER ADDITION 9-27-2022 X.pdf drive-download-20240722T121115Z-001
Kirk_Lic_back.jpeg mhvf-df-20_30_bf_rt-t-current-2020.pdf
Kirk_Lic_front.jpeg
old-daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
Kirk_and_George.jpeg paid.png
Kirks version.docx paypal qrcode.png
My Band.jpg unnamed.png
@.*** Downloads % pkgutil --check-signature
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
Package "daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg":
Status: signed by a developer certificate issued by Apple for
distribution
Signed with a trusted timestamp on: 2024-12-12 14:16:59 +0000
Certificate Chain:
1. Developer ID Installer: Input Output HK Limited (89TW38X994)

   Expires: 2027-02-01 22:12:15 +0000

   SHA256 Fingerprint:

       AD B3 2F 8C 6F D0 2D 1F 0C 97 7C B2 92 1E 18 37 3B 45 03 4D 25

EA
       D1 26 68 1B CB 0F B9 42 8E 4E

2. Developer ID Certification Authority

   Expires: 2027-02-01 22:12:15 +0000

   SHA256 Fingerprint:

       7A FC 9D 01 A6 2F 03 A2 DE 96 37 93 6D 4A FE 68 09 0D 2D E1 8D

03
       F2 9C 88 CF B0 B1 BA 63 58 7F

3. Apple Root CA

   Expires: 2035-02-09 21:40:36 +0000

   SHA256 Fingerprint:

       B0 B1 73 0E CB C7 FF 45 05 14 2C 49 F1 29 5E 6E DA 6B CA ED 7E

2C
       68 C5 BE 91 B5 A1 10 01 F0 24

On Thu, Dec 19, 2024 at 3:12 PM Michal Rus @.***>
wrote:

Okay, thanks for confirming this, so for some reason, the output of pkgutil
--check-signature is missing the following line on your macOS:
Notarization: trusted by the Apple notary service
That's why the trust error is shown. For reference, here's my output (on
macOS Sequoia 15.2):
❯ pkgutil --check-signature daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
Package "daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg":
Status: signed by a developer certificate issued by Apple for distribution
Notarization: trusted by the Apple notary service
Signed with a trusted timestamp on: 2024-12-12 14:16:59 +0000
Certificate Chain:
1. Developer ID Installer: Input Output HK Limited (89TW38X994)
Expires: 2027-02-01 22:12:15 +0000
SHA256 Fingerprint:
AD B3 2F 8C 6F D0 2D 1F 0C 97 7C B2 92 1E 18 37 3B 45 03 4D 25 EA
D1 26 68 1B CB 0F B9 42 8E 4E
------------------------------------------------------------------------
2. Developer ID Certification Authority
Expires: 2027-02-01 22:12:15 +0000
SHA256 Fingerprint:
7A FC 9D 01 A6 2F 03 A2 DE 96 37 93 6D 4A FE 68 09 0D 2D E1 8D 03
F2 9C 88 CF B0 B1 BA 63 58 7F
------------------------------------------------------------------------
3. Apple Root CA
Expires: 2035-02-09 21:40:36 +0000
SHA256 Fingerprint:
B0 B1 73 0E CB C7 FF 45 05 14 2C 49 F1 29 5E 6E DA 6B CA ED 7E 2C
68 C5 BE 91 B5 A1 10 01 F0 24

If you want to help investigate this, could you try opening the following
installer (link below)? Is it trusted?
I have created an installer with the notarization stapled to it, e.g. for
offline use. Normally, without a stapled notarization, macOS has to consult
Apple's servers. So my idea was that maybe an older OS will accept
stapled notarization?
The new installer to test can be downloaded from our Google Drive:
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg
https://drive.google.com/file/d/19ur7WwTLX8Ivbb9kl9GhJ9x2wf--2v7Z/view
It is also signed with the IOHK key (89TW38X994), so the source of the
download doesn’t matter, in case you were worried about it being Google
Drive.
Before (or even without) opening, you can run pkgutil --check-signature
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg — I
would be very grateful for this output, too. Does it contain Notarization:
trusted by the Apple notary service?
Thanks for all the help. 🙏
—
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/daedalus/issues/3263#issuecomment-2555690513,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNUK7J7B46BVSUPJ7IEWK532GMSCPAVCNFSM6AAAAABTONOXYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJVGY4TANJRGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@kirk-bit hey, thanks, I see that you sent the output on a non-stapled installer twice:
pkgutil --check-signature daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg

Could you also download the new -stapled.pkg version, and run the command on it, too? 🙏
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg
pkgutil --check-signature daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg

Hi Michal. I tried the stapled version, and unfortunately, the result is
similar. Please see below.
spctl:
@.*** Downloads % spctl -a
~/Downloads/daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg
/Users/kirkkiller/Downloads/daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg:
rejected
check sig:
@.*** Downloads % pkgutil --check-signature
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg
Package "daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg":
Status: signed by a developer certificate issued by Apple for
distribution
Signed with a trusted timestamp on: 2024-12-12 14:16:59 +0000
Certificate Chain:
1. Developer ID Installer: Input Output HK Limited (89TW38X994)

   Expires: 2027-02-01 22:12:15 +0000

   SHA256 Fingerprint:

       AD B3 2F 8C 6F D0 2D 1F 0C 97 7C B2 92 1E 18 37 3B 45 03 4D 25 EA

       D1 26 68 1B CB 0F B9 42 8E 4E

2. Developer ID Certification Authority

   Expires: 2027-02-01 22:12:15 +0000

   SHA256 Fingerprint:

       7A FC 9D 01 A6 2F 03 A2 DE 96 37 93 6D 4A FE 68 09 0D 2D E1 8D 03

       F2 9C 88 CF B0 B1 BA 63 58 7F

3. Apple Root CA

   Expires: 2035-02-09 21:40:36 +0000

   SHA256 Fingerprint:

       B0 B1 73 0E CB C7 FF 45 05 14 2C 49 F1 29 5E 6E DA 6B CA ED 7E 2C

       68 C5 BE 91 B5 A1 10 01 F0 24

Error Log:
Process:               cardano-launcher [6741]
Path:                  /Applications/Daedalus
Mainnet.app/Contents/MacOS/Daedalus Mainnet
Identifier:            com.electron.daedalus-mainnet
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           cardano-launcher [6741]
User ID:               502
Date/Time:             2024-12-20 04:53:39.190 -0500
OS Version:            macOS 11.7.10 (20G1427)
Report Version:        12
Bridge OS Version:     8.2 (21P2057)
Anonymous UUID:        C1ED7E40-5E7C-4A74-BFBC-4BDC61267371
Sleep/Wake UUID:       B5A1A344-C398-4223-8C74-7E58F2E2FF1F
Time Awake Since Boot: 62000 seconds
Time Since Wake:       53000 seconds
System Integrity Protection: enabled
Crashed Thread:        0
Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY
Termination Reason:    DYLD, [0x3] Wrong version
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: @executable_path/libcharset.1.dylib
Referenced from: /Applications/Daedalus
Mainnet.app/Contents/MacOS/libiconv.dylib
Reason: Incompatible library version: libiconv.dylib requires version
2.0.0 or later, but libcharset.1.dylib provides version 1.0.0
Binary Images:
0x108da1000 -        0x10919ffff +cardano-launcher (0)
/Applications/Daedalus Mainnet.app/Contents/MacOS/cardano-launcher
0x1095ff000 -        0x109613fff +libz.dylib (0)
 /Applications/Daedalus
Mainnet.app/Contents/MacOS/libz.dylib
0x109623000 -        0x109623fff +libiconv.dylib (0)
/Applications/Daedalus Mainnet.app/Contents/MacOS/libiconv.dylib
0x109632000 -        0x1096bdfff +libgmp.10.dylib (0)
 /Applications/Daedalus
Mainnet.app/Contents/MacOS/libgmp.10.dylib
0x1096d5000 -        0x1096dbfff +libffi.8.dylib (0)
 /Applications/Daedalus
Mainnet.app/Contents/MacOS/libffi.8.dylib
0x1096e9000 -        0x1097c7fff +libiconv-nocharset.dylib (0)
/Applications/Daedalus Mainnet.app/Contents/MacOS/libiconv-nocharset.dylib
0x10a47e000 -        0x10a519fff  dyld (852.2)
 /usr/lib/dyld
0x7fff2029d000 -     0x7fff2029efff  libsystem_blocks.dylib (79)

/usr/lib/system/libsystem_blocks.dylib
0x7fff2029f000 -     0x7fff202d4fff  libxpc.dylib (2<IP_ADDRESS>1.2)
<151C64CA-CA6F-3989-A558-796EB6ED0C11> /usr/lib/system/libxpc.dylib
0x7fff202d5000 -     0x7fff202ecfff  libsystem_trace.dylib (1277.120.1)
<1F20357C-395F-3095-B525-AD9403290A92> /usr/lib/system/libsystem_trace.dylib
0x7fff202ed000 -     0x7fff2038afff  libcorecrypto.dylib (1000.140.4)
 /usr/lib/system/libcorecrypto.dylib
0x7fff2038b000 -     0x7fff203b7fff  libsystem_malloc.dylib (317.140.5)
<3AB4C7E9-C49C-3EB7-9370-370F3F655024>
/usr/lib/system/libsystem_malloc.dylib
0x7fff203b8000 -     0x7fff203fcfff  libdispatch.dylib (1271.120.2)
<5D824C33-C5E2-38A8-BD00-D934443DBDAB> /usr/lib/system/libdispatch.dylib
0x7fff203fd000 -     0x7fff20436fff  libobjc.A.dylib (824.1)
 /usr/lib/libobjc.A.dylib
0x7fff20437000 -     0x7fff20439fff  libsystem_featureflags.dylib
(28.60.1) <2BAC8770-AFC8-3FE2-B6C6-27CE44B2B2BA>
/usr/lib/system/libsystem_featureflags.dylib
0x7fff2043a000 -     0x7fff204c2fff  libsystem_c.dylib (1439.141.1)
 /usr/lib/system/libsystem_c.dylib
0x7fff204c3000 -     0x7fff20518fff  libc++.1.dylib (905.6)
<5BA6B5ED-7842-3B13-86B0-00EB511CE2FE> /usr/lib/libc++.1.dylib
0x7fff20519000 -     0x7fff2052efff  libc++abi.dylib (905.6)
 /usr/lib/libc++abi.dylib
0x7fff2052f000 -     0x7fff2055efff  libsystem_kernel.dylib
(7<IP_ADDRESS>2.12)
/usr/lib/system/libsystem_kernel.dylib
0x7fff2055f000 -     0x7fff2056afff  libsystem_pthread.dylib
(4<IP_ADDRESS>0.1) <409239A7-2E4E-31C7-87EB-EE50B7981204>
/usr/lib/system/libsystem_pthread.dylib
0x7fff2056b000 -     0x7fff205a6fff  libdyld.dylib (852.2)
 /usr/lib/system/libdyld.dylib
0x7fff205a7000 -     0x7fff205b0fff  libsystem_platform.dylib
(254.80.2) <52A77346-8AA5-3BB7-906D-C7503B491CF9>
/usr/lib/system/libsystem_platform.dylib
0x7fff205b1000 -     0x7fff205dcfff  libsystem_info.dylib (542.40.4)
<406353B2-E48A-3D20-B08F-0AB26ED8A0B3> /usr/lib/system/libsystem_info.dylib
0x7fff229ae000 -     0x7fff229b7fff  libsystem_darwin.dylib
(1439.141.1) <75592BEC-777B-381F-8C07-15B8A4C712A7>
/usr/lib/system/libsystem_darwin.dylib
0x7fff22dcd000 -     0x7fff22dd8fff  libsystem_notify.dylib (279.40.4)
<02E22D9D-01E2-361C-BB9A-B5BE18D28280>
/usr/lib/system/libsystem_notify.dylib
0x7fff24d64000 -     0x7fff24d72fff  libsystem_networkextension.dylib
(12<IP_ADDRESS>1.1) <9C5A85AC-C593-34FD-8481-5CFC05DE3897>
/usr/lib/system/libsystem_networkextension.dylib
0x7fff24dd1000 -     0x7fff24de7fff  libsystem_asl.dylib (385.0.2)
<88F4051D-1CF5-314E-A952-247C38996E16> /usr/lib/system/libsystem_asl.dylib
0x7fff264b0000 -     0x7fff264b7fff  libsystem_symptoms.dylib
(1431.140.1)
/usr/lib/system/libsystem_symptoms.dylib
0x7fff284bf000 -     0x7fff284cffff  libsystem_containermanager.dylib
(3<IP_ADDRESS>0.1) <45445167-AFC7-3406-A858-9AE8D8F45907>
/usr/lib/system/libsystem_containermanager.dylib
0x7fff291d4000 -     0x7fff291d7fff  libsystem_configuration.dylib
(1109.140.1) <53B71513-3009-3A8C-A5AA-9C15DD0AB54E>
/usr/lib/system/libsystem_configuration.dylib
0x7fff291d8000 -     0x7fff291dcfff  libsystem_sandbox.dylib
(14<IP_ADDRESS>1.2) <1E19BC49-484C-32BB-8BB7-99D41C63F86E>
/usr/lib/system/libsystem_sandbox.dylib
0x7fff29ece000 -     0x7fff29ed0fff  libquarantine.dylib (119.40.4)
<21C63859-6DFB-3463-9ADF-BB44FB28067C> /usr/lib/system/libquarantine.dylib
0x7fff2a479000 -     0x7fff2a47dfff  libsystem_coreservices.dylib
(127.1) <6D84FA08-CB2B-34E1-9AB4-A54E82CB9161>
/usr/lib/system/libsystem_coreservices.dylib
0x7fff2a68d000 -     0x7fff2a6d4fff  libsystem_m.dylib (3186.100.3)
<1836B380-C579-3195-BC3F-77404D432186> /usr/lib/system/libsystem_m.dylib
0x7fff2a6d6000 -     0x7fff2a6dbfff  libmacho.dylib (980)
 /usr/lib/system/libmacho.dylib
0x7fff2a6f8000 -     0x7fff2a703fff  libcommonCrypto.dylib
(60178.120.3)
/usr/lib/system/libcommonCrypto.dylib
0x7fff2a704000 -     0x7fff2a70efff  libunwind.dylib (201)
<9D6A6228-8DC3-3521-B458-4EDE4A9F5E65> /usr/lib/system/libunwind.dylib
0x7fff2a70f000 -     0x7fff2a716fff  liboah.dylib (203.58)
 /usr/lib/liboah.dylib
0x7fff2a717000 -     0x7fff2a721fff  libcopyfile.dylib (173.40.2)
 /usr/lib/system/libcopyfile.dylib
0x7fff2a722000 -     0x7fff2a729fff  libcompiler_rt.dylib (102.2)
 /usr/lib/system/libcompiler_rt.dylib
0x7fff2a72a000 -     0x7fff2a72cfff  libsystem_collections.dylib
(1439.141.1) <21F2EF42-56ED-3E0F-9C29-94E0888DC52C>
/usr/lib/system/libsystem_collections.dylib
0x7fff2a72d000 -     0x7fff2a72ffff  libsystem_secinit.dylib (87.60.1)

/usr/lib/system/libsystem_secinit.dylib
0x7fff2a730000 -     0x7fff2a732fff  libremovefile.dylib (49.120.1)
<5AC9F8EC-F0E8-3D8A-ADB5-96B5FB581896> /usr/lib/system/libremovefile.dylib
0x7fff2a733000 -     0x7fff2a733fff  libkeymgr.dylib (31)
<9FBE08F6-0679-3976-AFDC-1EAF40C3958F> /usr/lib/system/libkeymgr.dylib
0x7fff2a734000 -     0x7fff2a73bfff  libsystem_dnssd.dylib (1310.140.1)
<8C4D6C93-285F-3587-A986-5BB96A1C664F> /usr/lib/system/libsystem_dnssd.dylib
0x7fff2a73c000 -     0x7fff2a741fff  libcache.dylib (83)
<56DCEFF5-111E-32FD-B4E9-E148507C4FEC> /usr/lib/system/libcache.dylib
0x7fff2a742000 -     0x7fff2a743fff  libSystem.B.dylib (1292.120.1)
 /usr/lib/libSystem.B.dylib
0x7fff2db4a000 -     0x7fff2db4afff  liblaunch.dylib (2<IP_ADDRESS>1.2)
 /usr/lib/system/liblaunch.dylib
0x7fff2ffe6000 -     0x7fff2ffe6fff
libsystem_product_info_filter.dylib (8.40.1)

/usr/lib/system/libsystem_product_info_filter.dylib
Model: MacBookPro16,1, BootROM 2<IP_ADDRESS>.0 (iBridge: 21.16.2057.0.0,0), 8
processors, 8-Core Intel Core i9, 2.3 GHz, 16 GB, SMC
Graphics: kHW_IntelUHDGraphics630Item, Intel UHD Graphics 630,
spdisplays_builtin
Graphics: kHW_AMDRadeonPro5500MItem, AMD Radeon Pro 5500M,
spdisplays_pcie_device, 4 GB
Memory Module: BANK 0/ChannelA-DIMM0, 8 GB, DDR4, 2667 MHz, Micron,
8ATF1G64HZ-2G6E1
Memory Module: BANK 2/ChannelB-DIMM0, 8 GB, DDR4, 2667 MHz, Micron,
8ATF1G64HZ-2G6E1
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0:
Aug 10 2021 20:10:47 version 9.30.4<IP_ADDRESS>.71 FWID 01-30b2601e
Bluetooth: Version 8.0.5d7, 3 services, 25 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB3.1 Hub
USB Device: USB 10/100/1000 LAN
USB Device: USB3.1 Hub
USB Device: USB 3.1 Bus
USB Device: USB2.1 Hub
USB Device: USB 2.0 Hub
USB Device: USB2.1 Hub
USB Device: Apple T2 Bus
USB Device: Composite Device
USB Device: Touch Bar Backlight
USB Device: Touch Bar Display
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Headset
USB Device: Ambient Light Sensor
USB Device: FaceTime HD Camera (Built-in)
USB Device: Apple T2 Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 63.5
Thunderbolt Bus: MacBook Pro, Apple Inc., 63.5
On Fri, Dec 20, 2024 at 4:28 AM Michal Rus @.***> wrote:

@kirk-bit https://github.com/kirk-bit hey, thanks, I see that you sent
the output on a non-stapled installer twice:
pkgutil --check-signature daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin.pkg
Could you also download the new -stapled.pkg version, and run the
command on it, too? 🙏
daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg
https://drive.google.com/file/d/19ur7WwTLX8Ivbb9kl9GhJ9x2wf--2v7Z/view
pkgutil --check-signature daedalus-7.0.2-71760-mainnet-331049f3e-x86_64-darwin-stapled.pkg
—
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/daedalus/issues/3263#issuecomment-2556608233,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNUK7J5FOHOCL6QEPAXWLN32GPPMTAVCNFSM6AAAAABTONOXYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJWGYYDQMRTGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Okay, I'm also getting rejected from spctl -a, but it works on my machine (macOS 15.1).
The issue you're seeing now (i.e. Incompatible library version: libiconv.dylib requires version 2.0.0 or later, but libcharset.1.dylib provides version 1.0.0) is a separate one, let's try to get notarization and trust working first, and then look at that, if you're still willing to help. 🙏
Question: were you able to install the -stapled.pkg without overriding trust by holding Option + RightClick + Open? Did simple double click install work for -stapled.pkg?

Okay sounds good. Yes, I was able to install the stapled version just by
double clicking. Thx!
On Fri, Dec 20, 2024, 5:58 AM Michal Rus @.***> wrote:

Okay, I'm also getting rejected from spctl -a, but it works on my machine
(macOS 15.1).
The issue you're seeing now (i.e. Incompatible library version:
libiconv.dylib requires version 2.0.0 or later, but libcharset.1.dylib
provides version 1.0.0) is a separate one, let's try to get notarization
and trust working first, and then look at that, if you're still willing to
help. 🙏
Question: were you able to install the -stapled.pkg without overriding
trust by holding Option + RightClick + Open? Did simple double click
install work for -stapled.pkg?
—
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/daedalus/issues/3263#issuecomment-2556769389,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNUK7J5SUXR6JFGRHMRVEAL2GPZ37AVCNFSM6AAAAABTONOXYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJWG43DSMZYHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Awesome to hear this! So the 1st issue is solved by stapling. We'll have to release 7.0.3 to solve it for everyone, but let's solve the 2nd issue first, and release both.
The 2nd issue is Incompatible library version: libiconv.dylib requires version 2.0.0 or later, but libcharset.1.dylib provides version 1.0.0.
It's confusing that it doesn't happen on my machine (or the ones of our QA). I'll analyze the log, will try to think of something, and will give you a new installer to test soon. ⏳
Thank you for the cooperation. 🙌

Hey, I really really appreciate the help with this! Thank you very much!!
On Fri, Dec 20, 2024 at 6:06 AM Michal Rus @.***> wrote:

Awesome to hear this! So the 1st issue is solved by stapling. We'll have
to release 7.0.3 to solve it for everyone, but let's solve the 2nd issue
first, and release both.
The 2nd issue is Incompatible library version: libiconv.dylib requires
version 2.0.0 or later, but libcharset.1.dylib provides version 1.0.0.
It's confusing that it doesn't happen on my machine (or the ones of our
QA). I'll analyze the log, will try to think of something, and will give
you a new installer to test soon. ⏳
Thank you for the cooperation. 🙌
—
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/daedalus/issues/3263#issuecomment-2556783606,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BNUK7J4BYFJ4CWM6WUCABF32GP23LAVCNFSM6AAAAABTONOXYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJWG44DGNRQGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Is any info yet when will be new version of Deadalus wallet ( 7.0.2) published which will solve this problem also for users which are not computer experts?

@Nearrain, I was told the team would be working on the new release, but they haven't provided a release date yet. Additionally, the libiconv.dylib is still an active ticket with IOHK, and that's the remaining piece of this multi-part issue to my knowledge. Still, there may be additional issues I'm unaware of.


Update sbt-typelevel-ci, ... to 0.5.4

About this PR
📦 Updates

org.typelevel:sbt-typelevel-ci
org.typelevel:sbt-typelevel-github
org.typelevel:sbt-typelevel-mergify
org.typelevel:sbt-typelevel-settings
org.typelevel:sbt-typelevel-versioning

from 0.4.22 to 0.5.4
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel" }
}]

labels: sbt-plugin-update, early-semver-major, semver-spec-minor, version-scheme:early-semver, commit-count:n:2

Superseded by #97.


Appstudio update hacbs-test-project-e3ci

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: hacbs-test-project-e3ci-on-pull-request-
creating pipelinerun hacbs-test-project-e3ci-on-pull-request- in namespace rhtap-demo-kudl-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


DllNotFoundException: LottiePlugin assembly on MacOS

Hello, I followed the manual to open sample scene but get the DLL error.

This is my environment detail:

Apple M2 chip Ventura
Unity 2021.3.16f1

I saw there is also a similar issue: https://github.com/gindemit/unity-rlottie/issues/6
How can I fixed that?

@simonpham After check your solution, seems like it need Cmake rebuild that rlottie?
Sorry I am a Unity Developer and have no experience how to do it, need more clues.

Hello @chile109, thanks for trying out. It seems that the current compiled native libraries are targeting only x86_64 architecture. And you have the arm64 CPU.
You can check it yourself In terminal:
konstantingindemit@Konstantins-MBP OSX % file libLottiePlugin.dylib
libLottiePlugin.dylib: Mach-O 64-bit dynamically linked shared library x86_64
konstantingindemit@Konstantins-MBP OSX % file librlottie.dylib
librlottie.dylib: Mach-O 64-bit dynamically linked shared library x86_64

Can you please try out the attached files.
Archive.zip
You need to unpack the zip archive, close Unity project and replace the dylib files in the
git/unity-rlottie/unity/RLottieUnity/Assets/LottiePlugin/Plugins/OSX folder.
With the attached files I get following in terminal:
konstantingindemit@Konstantins-MBP rlottieOSXArm64 % file libLottiePlugin.dylib
libLottiePlugin.dylib: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64
- Mach-O 64-bit dynamically linked shared library x86_64] [arm64:Mach-O 64-bit dynamically linked shared library arm64
- Mach-O 64-bit dynamically linked shared library arm64]
libLottiePlugin.dylib (for architecture x86_64):	Mach-O 64-bit dynamically linked shared library x86_64
libLottiePlugin.dylib (for architecture arm64):	Mach-O 64-bit dynamically linked shared library arm64
konstantingindemit@Konstantins-MBP rlottieOSXArm64 % file librlottie.dylib
librlottie.dylib: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64
- Mach-O 64-bit dynamically linked shared library x86_64] [arm64:Mach-O 64-bit dynamically linked shared library arm64
- Mach-O 64-bit dynamically linked shared library arm64]
librlottie.dylib (for architecture x86_64):	Mach-O 64-bit dynamically linked shared library x86_64
librlottie.dylib (for architecture arm64):	Mach-O 64-bit dynamically linked shared library arm64

Hey @gindemit , after replace the libLottiePlugin.dylib the plugin is working now.
Thanks for your help and Detailed explanation!


Support Arithmetic function MOD

Backgrounds

Kotlin JDSL does not yet support an arithmetic function MOD.

Objects

Support an arithmetic function MOD.

Requirements

Creates mod() function in com.linecorp.kotlinjdsl.dsl.jpql.Jpql for supporting an arithmetic function MOD.

Contribution

Please check if there is an assignee in this issue. And if it don't have an assignee, please leave comment to assign.
Please check the commit convention through the commitlint.config.js file. The commit  convention also described in the PR template.
When you use intellij, please set the code style through the .editorconfig file.
Please create the PR for develop as the base branch.
If you have any questions, please leave comment in Kotlin-JDSL Discord Channel in LINE Open Source

I would like to contribute to this issue, would be glad if you can assign, thanks!

Hi Dogacel!
I assigned this issue to you. Thank you for your help!

It's been 3 weeks since the last comment. I'm going to close the PR created by Dogacel and change the assignee of this issue.

Hello, I would like to be assigned to the specific issue.

I assigned this issue to graceful-martin. Thanks for your help!


Examples of Generative Model

From now on, we recommend using our discussion forum (https://github.com/rusty1s/pytorch_geometric/discussions) for proposing new features.
🚀 Feature
Generative Model
Motivation
Pytorch Geometric is easy to use and there are some great examples. However, Pytorch Geometric lacks examples of generative models.
I am wondering whether there are any plans to include any of the following models:

GraphRNN: https://github.com/JiaxuanYou/graph-generation

Also, Pytorch Geometric lacks examples of Graph2Seq based models. It would be awesome to consider any of the following Graph2Seq based generative models.

Graph-to-Sequence Learning using Gated Graph Neural Networks, ACL’18, https://github.com/beckdaniel/acl2018_graph2seq
Using MXNet

Densely Connected Graph Convolutional Networks for Graph-to-Sequence Learning, ACL’19
https://github.com/Cartus/DCGCN
Using MXNet 1.3.0

Heterogeneous Graph Transformer for Graph-to-Sequence Learning, ACL’18
https://github.com/QAQ-v/HetGT
Using OpenNMT

Additional context
I'm happy to contribute as well.

See https://github.com/rusty1s/pytorch_geometric/discussions/2614


CLOUD-68246: Allow deleting multiple instances in a stack in the backend

This enhancement allows multiple instances to be deleted in the backend InstanceTerminationFlow. The flow involves termination from the cloud provider and Ambari. Multiple instance termination from cloud provider is already supported in the API (due to downscale).
This enhancement will help in ongoing work to recover from multiple faulty slave nodes in the cluster. So, while there is no front end exposure to this capability right now, it will be used with development of that feature.
Could you please review this and let me know if it can be merged, or any other feedback to address.

I tested the following manually:

Validated that single instance termination from Cloudbreak UI continues to work fine.
Validated multiple instance termination by changing some code to inject termination of 2 instances.


ng build --prod problem

Hi, when I tried to do a prod build with the newest version of cli, it throws this error.
ERROR in ng:///home/user/Documents/AngularProyects/myApp/node_modules/angular2-image-upload/lib/image-upload/image-upload.component.d.ts.ImageUploadComponent.html (3,5): Property 'fileCounter' is private and only accessible within class 'ImageUploadComponent'.
If you guys can change that property it will be awesome! thanks for your time.

This is fixed in #72, pending release: #70 @aberezkin


Create 0091-decode-ways.swift

File(s) Modified: 0091-decode-ways.swift
Language(s) Used: swift
Submission URL: https://leetcode.com/problems/decode-ways/submissions/1431154812/

Important
Please make sure the file name is lowercase and a duplicate file does not already exist before merging.

@drxlx Thanks for your contribution 👍


Update examples.md

I prefer keeping 'r' in lowercase in my blog's name.

Summary

Test plan

A picture of a cute animal (not mandatory but encouraged)

Deploy preview for netlify-cms-www ready!
Built with commit 8a5980f8d9a0b8a68552416b8b11ec0dd0848b56
https://deploy-preview-1784--netlify-cms-www.netlify.com

Deploy preview for cms-demo ready!
Built with commit 8a5980f8d9a0b8a68552416b8b11ec0dd0848b56
https://deploy-preview-1784--cms-demo.netlify.com


Remove -AuthorizationPolicyId which doesn't exist (anymore?)

This parameter doesn't exist. At least in the latest v1.0 version of the Graph PowerShell module. Perhaps it used to exist?
Proof in doc: https://learn.microsoft.com/en-us/powershell/module/microsoft.graph.identity.signins/update-mgpolicyauthorizationpolicy?view=graph-powershell-1.0
And in this error:
PS> Update-MgPolicyAuthorizationPolicy -AuthorizationPolicyId $authorization_policy -BodyParameter $body
Update-MgPolicyAuthorizationPolicy : A parameter cannot be found that matches parameter name 'AuthorizationPolicyId'.

PS> Get-InstalledModule Microsoft.Graph

Version              Name                                Repository           Description
-------              ----                                ----------           -----------
2.19.0               Microsoft.Graph                     PSGallery            Microsoft Graph PowerShell module

Edit: Actually! It exists, but only for the beta version!
https://learn.microsoft.com/en-us/powershell/module/Microsoft.Graph.Beta.Identity.SignIns/Update-MgBetaPolicyAuthorizationPolicy?view=graph-powershell-beta
There are significant differences between the v1.0 and beta versions of this API (returning an object vs. array, authorization policy under defaultUserRolePermissions.permissionGrantPoliciesAssigned vs. permissionGrantPolicyIdsAssignedToDefaultUserRole)
Currently all the content in the page refers to the beta version of the API and the commands. My advice is to either adapt it to v1.0, or keep beta but make it very explicit and use instead Update-MgBetaPolicyAuthorizationPolicy

@omondiatieno
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Still applies

I sent a Teams message to the content owner today.

#sign-off


spelling fixes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 64.64%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1552

Relevant Lines:
2401

💛  - Coveralls


Updates Italian translations

We updated Italian translations by adding missing key-value pairs from en.yml and translating the values to Italian. We did not remove any keys that were previously present, so it.yml now has more keys then en.yml of solidus core.
We tested the translations only by manually navigating the app and we made sure that no translations were missing by raising exceptions for missing translations (config.action_view.raise_on_missing_translations = true)
In addition to this we updated the Italian localization files for other solidus gems and will send pull requests to their repos.

#64 fixes the build failures. Please rebase once it's landed in master

@tvdeyen what do I need to do in order to help this get into the master so that we can use the main gem instead of a fork?

@bosskovic how is your work related to #56?
Please

Rebase with current master now that #65 landed to fix the build errors
Stash all commits into one commit that is called "Updates Italian translation" or similar, because currently the commit messages doesn't provide any value (http://chris.beams.io/posts/git-commit/)

Thanks for your contribution

@bosskovic
There are too many additions to comment line by line, so I post you direct links:
https://github.com/Xpitality/solidus_i18n/blob/e9070d890c1e5bfd4518814301f96b873fd6129f/config/locales/it.yml#L5
typo, should be Quantità
https://github.com/Xpitality/solidus_i18n/blob/e9070d890c1e5bfd4518814301f96b873fd6129f/config/locales/it.yml#L317
should be Icona

@bosskovic Would you mind squashing your commits and rebasing on master?

Hi!
It was easier for me to create a new pull request: https://github.com/solidusio-contrib/solidus_i18n/pull/90
I based it on the most recent master. I used the en.yml from solidus core as reference (added the missing keys and fixed the order of existing keys to match that in en.yml as much as possible). I took the values from our Italian translations and the existing it.yml of solidus_i18n repo.
In it.yml now there are lot more keys then in en.yml of solidus core. Possibly many are obsolete, but I did not remove any of them myself.
Please note that I am not an Italian speaker, so I did not (nor am I able to) add any new translations, I just used those that were already there and picked and chose between the two when there were variants (one being the existing it.yml translations and the other those translated by our team in the past year).
Please take a look and merge it soon, because it is quite time consuming doing these compares and resolving conflicts.

I'd like to emphasise again that I changed the order of keys in it.yml of solidus_i18n to match the order of keys in en.yml of solidus_core. Thus many keys will appear to be deleted in the diff, but if you look carefully, they are added back at some other place. it.yml now contains all keys from en.yml + some other (probably mostly obsolete).

What's the status on this? I wanted to contribute, but I don't understand... I don't want to do the work twice


Bugfix for Google Authentication

[x] Fixed hardcoded parameters in Google login link
[x] Externalized site_id , client_id , and callback uri
[x] Update Google Authentication setup guide

I'll add some tests for the get context data method tomorrow

I'll review after #95 is closed and you've updated this branch as the branch will be outdated.

The program works the same as before after following the instructions, they are not too hard to understand as well. 👍

I have thoroughly inspected the code that thou hath written. Neither my eyes nor my ears saw anything wrong with the literature of yours. It is, therefore, passed the acceptable quality to be merged into main, in my opinion.

Ah mine compatriot, I am truly touched by thine splendorous words. (but can you please be a bit more serious next time)


Add activity-square icon

It feels a bit skewed, maybe something like this would have been better?

It feels a bit skewed, maybe something like this would have been better?

@karsa-mistmere I can’t tell, is that .5px difference? Tweak it in another PR if you like…


Remove unnecessary "isDedupe" json check

watchify doesn't cache when "deps" are emitted, it caches module-deps' output - which would be the preprocessed json.

@terinjokes @jmm: Any thoughts on this? Basically, this is a hack for users on watchify 2.4.0 and under.


Drupal 7 redis.cluster.enabled is now mandatory?

This is more of a question, maybe an issue... We recently tried to update our D7 site and saw the following error.:
Error: template: drupal7/templates/job/post-upgrade-reconfigure.yaml:78:32: executing "drupal7/templates/job/post-upgrade-reconfigure.yaml" at <.Values.redis.cluster.enabled>: nil pointer evaluating interface {}.enabled
We had to specify redis.cluster.enabled to false, which we didn't have to before in our yaml.
I noticed the d7 and d9 charts seem to diverge in this.:
https://github.com/drupalwxt/helm-drupal/blob/master/drupal7/templates/job/post-install-site-install.yaml#L78
https://github.com/drupalwxt/helm-drupal/blob/master/drupal/templates/job/post-install-site-install.yaml#L78
I didn't see any mention in the changelog about redis updates or having to specify this value now in d7... I guess I am wondering if you are aware of this, and this is correct or an issue. I appologize if this doesn't make sense, helm isn't my native language. :package:
P.S. Appreciate you reading this and all the hard work that goes into this chart.

We seem to also be running into issues with the REDIS_PASSWORD environment variable not being the same in the Drupal install container/job and in redis. Not sure if this is related... On the drush status, we get the following error. We don't see this in our d9 projects (with a database restore).

Drush command terminated abnormally due to an unrecoverable error.       [error]
Additional uncaught exception thrown while handling exception.OriginalRedisException: WRONGPASS invalid username-password pair or user is disabled. in Redis->auth() (line 18 of /var/www/html/sites/all/modules/contrib/redis/lib/Redis/Client/PhpRedis.php).AdditionalRedisException: WRONGPASS invalid username-password pair or user is disabled. in Redis->auth() (line 18 of /var/www/html/sites/all/modules/contrib/redis/lib/Redis/Client/PhpRedis.php).+OK
+OK

Hi @nathanpw is this dev for WCMS I can take a look right now?
The logic should be virtually identical btw the drupal and drupal 7 one so its possible something got missed in the backport.
I'm checking now.

Yup your right @nathanpw something was missed in the backport to Drupal 7 related to the redis changes. All of the D9 sites won't be affected but the D7 site needs the remaining fixes. I am going through it now, sorry for the inconvenience. I forced @zachomedia to rush the merge in to help you but we should have checked it closer.

Thanks @sylus, for the quick response and fix! We will look at this, this morning!

We still seem to be having issues. When I shell into the containers the $REDIS_PASSWORD environment variable now seems to match, however in the settings.php $conf['redis_client_password'] doesn't seem to be updated or match what is set in the environment variable. Not sure if this is a config on our part or still an issue in the chart...
In our d9 projects settings.php I see: $settings['redis.connection']['password'] = getenv('REDIS_PASSWORD') ?: '';
Where in our d7 project it seems hard coded.: $conf['redis_client_password'] = "aLongSecurePassword";
Should the d7 use the same getenv assignment?
helm-drupal$ grep -nr redis_client_password
drupal7/conf/settings.d7.php:747:$conf['redis_client_password'] = "{{ .Values.redis.password }}";

The hardcoded password seems to be coming from the default in .: wcms.yaml:172:  password: aLongSecurePassword

Yup your right pushing the fix now. (Need to wait 5 mins before u can grab)
https://github.com/drupalwxt/helm-drupal/commit/e91032f33b189dad944d0376e4d76c03200e7b16
Zach is going to write some test coverage for this so won't happen in future, and I have a D7 environment i'm can use now to test this so doesn't happen again.
Thanks for your debugging and quickly pointing me where to look ^_^

This also makes sense since the password moved under the global field so it will be empty in yours and fallback to the default. But now getting from the environment should be ok :D

Ok @nathanpw its out now can you try and report back?
I'm committed to fixing the remaining errors for this and apologize the backport should have been tested more which we will do more in future.
The D9 always get tested since have production deployments with it.

That worked for both our d7 sites, thanks again!


Feat: Export map state

Addresses #48. Introducing an eox-map layers getter as an action and suggests a composite approach for the following components (internal widgets):

PopUp: base dialog component that takes in a widget prop to be rendered and a show/hide trigger v-model, this can come in handy for creating markdown-based popups using eox-storytelling for example.
ExportState:  this is an interface for exporting eox-map state utilizing the PopUp component, and it can also be extended for other types of maps in the future.
EodashMapBtns: this is meant to be the central location for EodashMap related buttons. Controls showing ExportState

Example of configuring the PopUp widget with markdown content using v-model elaborate syntax:
const show = ref(false);
export default createEodash({
...
 widgets:
  ...
      {
        id: 1,
        type: 'internal',
        layout: { x: 0, y: 0, w: 0, h: 0 },
        title: "Welcome",
        widget: {
          name: "PopUp",
          properties: {
            class: 'pa-5 ma-5',
            modelValue: show,
            "onUpdate:modelValue": (newVal) => show.value = newVal,
            /** @type{import('@/types').Widget} */
            widget: {
              id: 2,
              type: 'web-component',
              layout: { x: 0, y: 0, w: 0, h: 0 },
              title: "Welcome",
              widget: {
                link: 'https://cdn.jsdelivr.net/npm/@eox/storytelling',
                tagName: 'eox-storytelling',
                properties: {
                  markdown: "## Welcome to eodash"
                }
              }
            }
          }
        }
      }
  })

Close #48


how to run linux.netstat action with arguments

PLEASE READ: If you are a paid Extreme Workflow (EWC) customer, please contant Extreme
Network GTAC
or send an email to<EMAIL_ADDRESS>For free community support, please use out forum at https://forum.stackstorm.com
I try to run linux.netstat action with args, but result are error as follow.
$ st2 run linux.netstat hosts=<IP_ADDRESS> args="-antp"
ERROR: 'type'

looks like type attribute is missing for netstat action. I hope #4947 will fix that permanently.
In the meantime, you can add the type attribute and re-register the Linux pack and that should fix the issue.
update /opt/stackstorm/packs/linux/actions/netstat.yaml to
---
  name: "netstat"
  runner_type: "remote-shell-cmd"
  description: "Run netstat"
  enabled: true
  entry_point: ""
  parameters:
    cmd:
      immutable: true
      default: "netstat {{args}}"
    args:
      description: "Command line arguments"
      default: " "
      type: "string"

and re-register the Linux pack using the following command
st2 pack register linux

This should resolve the issue for you.


Spring Security/Gorouter Issue?

I am working with Spring Security to secure an application deployed on Pivotal Cloud Foundry. When I logout the securitycontext is cleared and the JSESSIONID cookie is deleted. When I go back to the home page, a new JSESSIONID is automatically created and the application logs me in, without asking me to authenticate. This happens only on PCF but works fine locally. When I run the application locally, logout deletes the cookie and forces me to relogin. On PCF, it does not, wondering if I need to delete the VCAP_ID cookie too?
The code snippet is as below:
`
@Configuration
@EnableWebMvcSecurity
public class WebSecurityConfig extends WebSecurityConfigurerAdapter {
	http.headers().cacheControl().disable();
    http.headers().xssProtection();
    http.headers().httpStrictTransportSecurity();

    http
    .headers()
    .addHeaderWriter(new XFrameOptionsHeaderWriter(XFrameOptionsMode.SAMEORIGIN))
    .and()
    .csrf().disable()
    .sessionManagement().sessionCreationPolicy(SessionCreationPolicy.ALWAYS)
    .and()
    .exceptionHandling()
    .authenticationEntryPoint(ssoRedirectionEntryPoint()).accessDeniedPage(accessDeniedUrl)
    .and()
    .authorizeRequests()
    .antMatchers("/ui/**").access(<<custom-permission-check>>)
    .anyRequest().authenticated()
    .and()
    .addFilterBefore(ssoAuthenticationProcessingFilter(), AbstractPreAuthenticatedProcessingFilter.class);

http.logout().deleteCookies("JSESSIONID").invalidateHttpSession(true).addLogoutHandler(ssoLogoutHandler());
}

@Bean
public LogoutFilter ssoLogoutFilter() {
LogoutFilter filter = new LogoutFilter("/", ssoLogoutHandler());
    filter.setLogoutRequestMatcher(new AntPathRequestMatcher("/logout"));
    return filter;
}

public class SSOLogoutHandler implements LogoutHandler {
@Override
public void logout(HttpServletRequest request, HttpServletResponse response,
Authentication authentication) {
//At the end, invalidate the session if there is one
if (request.getSession(false) != null) {
  request.getSession(false).invalidate();
}

SecurityContextHolder.clearContext();

......
}
`

We noticed that your corresponding issue in PCF-dev was closed, so we are going to close this as well. We recommend contacting Pivotal Support if further assistance is needed.

Hello,
If you could provide us with an app with which we can reproduce this in an OSS Cloud Foundry environment, we'll take a look. Gorouter shouldn't be removing the JSESSIONID cookie, only adding the VCAP_ID cookie.
Thank you

This can be closed, cachecontrol was the issue and after adding that, this got resolved.


Arnej/allocate vector before use

@geirst please review
@baldersheim @havardpe FYI

@geirst please take another look


Dialpad is not enabled

unable to key in the numbers using dialpad where as able to key in using keyboard in the given text box. Is this expected behavior?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c4ef2b1d-8b33-2f5c-5adb-ad8ff31326c3
Version Independent ID: 17e1ef7f-cc58-e9dd-a097-4b9ad28707cb
Content: Sample code for softphone integration using Channel Integration Framework (CIF)
Content Source: ce/developer/channel-integration-framework/sample-softphone-integration.md
Service: dynamics-365-cross-app
GitHub Login: @kabala123
Microsoft Alias: kabala

@Bhuvi31 : Thanks for reaching out. I will get back with the information for your query.
Thanks for the patience.
Regards,
Karthik

@Bhuvi31: The dial-pad isn’t implemented in the sample. Since it is not implemented, it is an expected behavior. Please share if you have any feedback about the documentation or product.
Thanks,
Karthik


Few more cases in SQLite specs

Issue Number

Overview

[ ] I have added few more cases into SqliteSpec and SqliteFileModeSpec

Comments

@piotr.stachyra, I believe most of those cases are already checked by the statemachine tests, have you checked the labelled there?

I believe most of those cases are already checked by the statemachine tests, have you checked the labels there?

I thought they might, but I haven't wrapped my head around them quite yet :)

The high level idea of the state machine tests is that they randomly generate a list of commands. Then these commands are run against the real implementation and model implementation at the same time. At every step, the results are compared and must be the same.
We need to verify:

That the model is correct -- the model is supposed to be as simple as possible.
The coverage of commands is sufficient -- so we tag generated test cases.

So, model and tags, they are the important parts.
The state machine tests print the coverage of tags. If there's something we think might not be covered then we should add a tag and see.

@rvl - thanks! I chatted with @KtorZ yesterday also. I'm closing this pr as it just partially duplicates the state machine tests.


Update color,-light-and-materials.md

Adding reference to the MRTK standard shader when dynamic lighting is needed.

Docs Build status updates of commit f0e6c20:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/color,-light-and-materials.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit aaa0a88:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/color,-light-and-materials.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Remove deprecated usage of Pauli

Summary
#5439 deprecates some methods and args in init.
This PR removes them.

Please add @t-imamichi as a reviewer.


security: exposed token in user.py

https://github.com/yuvipanda/hubtraf/blob/78ab8b5ad9d09ce245f5056adebce843978c4351/hubtraf/user.py#L96-L98
Why is there a hardcoded api-token for use against JupyterHub's /hub/api endpoint configured here? Even if no JupyterHub is now using this token, it could encourage someone to take the quick and easy way to try by configuring a JupyterHub to accept that API token.

ah, fun. it is a token for a hub that is no longer around, but should kill it...

Has been fixed by #27


Should be able to have multiple admins for a package

Virtualenv and pip have a triumvirate. We all want access.

@wraithan did you make any progress on this feature?

This is now possible with the API, and will make its way into the UI eventually. Going to call this closed however, since it's documented:
http://read-the-docs.readthedocs.org/en/latest/api.html#example-of-adding-a-user-to-a-project


Godot 4 compatability

These are the minimum neccessary changes to make the code work with current Godot 4 alpha 1.
They work and I tested them, but they should likely not be merged without thinking about how the Godot 4 version will work on the Asset Lib - separate branch, separate repo, master branch and move 3.x to another branch?
Of course, whether you want to support Godot 4 at all is your choice. :-) Do what you want with this code.
I just wanted to contribute the few changes back to save others some time. Thanks for the work, nicely done!
(Marked as draft to signify changes aren't compatible with Godot 3. Feel free to merge anyway.)

Thank you and for the spelling fixes too. Will be holding on to this as a pull request for now since i am working on a few changes.

Figured I could have the godot4 branch now. Was wondering if you had any tips on a decent workflow to keep things synced up.

Unfortunately not - haven't really used the Asset Lib myself. If it can pull from branches, I'd do a branch for 4.x. Otherwise probably needs its own repo for now. On the Asset Lib side, I think it lacks support for multiple versions right now, so you'll likely need to create another asset for 4.0 and link to the right branch (or repo) if you want to keep the 3.x version up (or just update to 4.x and link to the old 3.x branch in the description?)
I'd try to keep 3.x compat up for a bit, as it will likely be some time before 4.x is fully out, stable, and widely used over 3.x.
However, not the best one to talk to about this, I'd recommend hitting up the people in the #devel channel on chat.godotengine.org to ask about this :) they may know more (although getting a response may need some idling after asking, people be busy)
Thanks again for the cool asset, saved me quite some time!


Bump camel-bom from 3.15.0 to 3.19.0

Bumps camel-bom from 3.15.0 to 3.19.0.

updated-dependencies:

dependency-name: org.apache.camel:camel-bom
dependency-type: direct:production
update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>
Stack:

#502 ⬅
#496
#501
#500
#499

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.


Extending this to a Datagrid

Hi, extremely useful combobox that ive been looking for. I am trying to extend this to work with a datagrid but no luck. I have a really simplified project that implements this on a single combobox and it works. However whenever I try to use this in a datatemplate column, it crashes as soon as I select an item from the drop down.
Any hints? Im new to WPF.
WPFTestApp MultiComboBox.zip

So I figured out the issue. The internal selecteditems container is of type observablecollection. I didnt expect this to be hard coded especially if you have SelectionMode="Single". Is there any workaround for this? I am binding the selecteditem of the combobox to a single value not an observablecollection.

We've added SelectedItem dependency property that internally manages SelectedItems as well, for this purpose (PR #83). Hope it helps.


Sveltekit with windi extended colors is not working.

I wrote this colors in windi.config.cjs:
module.exports = {
  theme: {
    container: {
      center: true
    },
    extend: {
      colors: {
        white: '#ffffff',
        'gray-lightest': '#f8f8f9',
        'gray-lighter': '#e4e4e5',
        'gray-light': '#d0d1d1',

        gray: '#bebebf',
        'gray-dark': '#969697',
        'gray-darker': '#6e6f6f',
        'gray-darkest': '#484849',
        black: '#202021',

        'primary-light': '#cacfe3',
        primary: '#1a4c8f',
        'primary-dark': '#192846',

        'secundary-light': '#eac7c0',
        secundary: '#8f231a',
        'secundary-dark': '#481911',

        'info-light': '#d7eff9',
        info: '#33bee8',
        'info-dark': '#275b6d',

        'warning-light': '#faeed1',
        warning: '#dbbd45',
        'warning-dark': '#695a27',

        'success-light': '#d7f3d6',
        success: '#47cc5d',
        'success-dark': '#2b6131',

        'danger-light': '#fed2d1',
        danger: '#dd4054',
        'danger-dark': '#6a262c'
      }
    }
  },
  variants: {},
  plugins: []
};```

In `sevelte.config.cjs`:
```JS
/** @type {import('@sveltejs/kit').Config} */
module.exports = {
	preprocess: [
		windicss({
			kit: true,
			config: "windi.config.cjs",
		}),
	],
	kit: {
.....

When I need to use text-primary the extended color is not working:
But, in Code editor, the colors is not presente in the list:

https://github.com/windicss/windicss-intellisense/issues/92

After some tests, now it's working. After I restart the application with 'npm run dev'. Just WindiCSS Intellisense extension is now not working. But, I think that windi.config.cjs is not reloading/recompiling after it is changed.

windicss/windicss-intellisense#92

The extension is updated, but, the problem persist in the sveltekit project.

I don't use Windi CSS so I am ending support for this project. I am sorry for the time you've wasted trying to use it thus far.
After the svelte-add rewrite, someone who can be trusted to set it up correctly and maintain it can contribute it to the svelte-add repository.


Edits/suggestions from Jaclyn (SRG 2019 meeting)

Attached are minor edits/ suggestions for the Exec Summary to clarify wording/ interpretation.
I think 5) and 7) are the only ones necessary for SRG discussion.
Questions/ edits for Executive Summary

[x] 1.	Page 5
“The stock is estimated to have been at relatively high levels since 2013…”

Suggest linking this statement directly to %Bo. (rather than subjective statement)

[x] 2.	Page 11
Suggest: “Pacific Hake appear to have low average recruitment with occasional large year-classes (Table c and Figure e).”

[x] 3.	Page 12
Suggest: “From 2000 to 2007 estimated recruitment was at some of the lowest values in the time series, but this was followed by a relatively large an above average 2008 year class.”

[x] 4.	Page 14
Suggest: “Total landings last exceeded the coast-wide quota in 2002 when utilization was 112%, though in retrospect, the fishing intensity was relatively low in that year due to appearance of the 1999 year class.”

[x] 5.	Page 15

The joint history of the medians for relative spawning biomass and relative fishing intensity shows that the median relative fishing intensity has never been above the target of 1.0 when the female spawning biomass is below the reference point of B40% (Figure h). This highlights the highly dynamic nature of the stock due to high variation in recruitment strength, such that spawning biomass could fall below B40% even in the absence of fishing.
I’m not following how the second statement in bold is explained by the first statement in bold.

[ ] 6.	Page 17 (2nd para)
“However, comparable results in terms of catch could be achieved with a more precise age-2+ survey or alternative harvest control rules.”

Was this shown?
If no, suggest rewording to indicate “may be achieved…”

[ ] 7.	Relative fishing intensity:

Relative fishing intensity is described as a ratio from 0:1 but expressed as both a percentage and ratio.
e.g., “Median relative fishing intensity on the stock is estimated to have been below the target of 1.0 for all years” (p13), Fig f
and
“Between 2007 and 2011, median relative fishing intensity ranged from 80% to 97%” (p15), Table h
Suggestion: add a statement to clarify that ratio and percentage are reported interchangeably for this metric.

7 - be good to make it consistent. Maybe best for general discussion in the meeting to decide what people prefer?

Fixed 1 with d82aaf010ce522a2b670d7835769fb6e03982299

Jaclyn said to remove "such ..." during her formal request for 5. Also did 2-6. Someone else can handle 7 :).
Done with a9d93338219ce4a00bbb0906f2edfe6f0f77585c

I can build again (just not without the new catch levels as I can't run SS3 any more). But I can do text edits and check them... back in business. I'll do 7.


Filter operator predicate overwrites the observable's type

Bug Report
Current Behavior
The type of the first argument of the predicate passed to the filter operator will overwrite the observable's type. The linked stackblitz shows the issue very clearly, hover the variable name to see its type.
Reproduction
// type of filteredNumber$ is Observable<any>
const filteredNumber$ = of(5).pipe(filter((num: any) => true));

Reproduction with possible solution: https://stackblitz.com/edit/rxjs-filter-typing?file=index.ts&view=editor
Expected behavior
The filter operator does not affect the type of the observable it is used on.
// type of filteredNumber$ is Observable<number>
const filteredNumber$ = of(5).pipe(filter((num: any) => true));

Environment

Runtime: any
RxJS version: 6.4.0

Possible Solution
Use a second type parameter for the predicate argument, so it doesn't affect the return type:
type newFilterType = <T, R extends T = T>(predicate: (value: R, index: number) => boolean, thisArg?: any) => MonoTypeOperatorFunction<T>

Context
Came across this issue when trying to use filter(Boolean). Noticed the type of the observable was lost after the filter operator. I'm willing to submit a PR with a solution if that's useful 😄

distinctUntilChanged has the same issue, added it to the stackblitz. There are probably some more operators I'm not thinking of 😛

By explicitly declaring the type as any you have widened it. So this is the expected behaviour.

I understand, in my example it's pretty explicit but in practice it can be less intuitive:
// type of filteredNumber$ is Observable<any>
const filteredNumber$ = of(5).pipe(filter(Boolean));

or
import { filterPredicate } from 'dependency-without-typedef';

// type of filteredNumber$ is Observable<any>
const filteredNumber$ = of(5).pipe(filter(filterPredicate));

Personally I didn't expect filter to have any effect on the type of the Observable.

filter (and distinctUntilChanged) emissions will always be a subset of their inputs, so they "real" types must also be a subset of the input types. Given that, it seems like ideally the typings for these should never be able to widen types, whatever predicates are passed? And if that can be achieved in a way that doesn't break anything else then that's the way it should be?
If there's something wrong with that logic, or if there's some strong consistency-based reason for inferring filter's output type from the arg type then ok, but otherwise it seems like a simple question of whether @eliasmeire 's possible solution breaks any other type behavior (e.g. can it be added in a way that doesn't stop you from being able to narrow the type, which you definitely should be able to)?

The problem is that the inference of the type parameter for filter will first come from the callback passed. If the type can be inferred from that callback, then that's what will be used. This all happens before pipe is even considered.
Essentially it is:
const op = filter((num: any) => true); // OperatorFunction<any, any>
const filteredNumber$ = of(5).pipe(op); // Observable<any>

It's the first step that is the problem. You have introduced an OperatorFunction that is specifically typed as any. And that is compatible with the number from the source observable, so TypeScript is happy.
Because it's an OperatorFunction<any, any>, the type of the Observable that's returned by pipe will be any. pipe has no idea about the semantics of filter, it just uses the second type parameter from OperatorFunction as the type for the Observable that is returned or input into the next operator.
AFAICT, there is nothing that can be done about this and the behavior is expected.

@eliasmeire I'm not sure that your proposed solution solves the problem. It doesn't appear to solve it for me. filter already has a signature similar to yours:
export declare function filter<T, S extends T>(predicate: (value: T, index: number) => value is S, thisArg?: any): OperatorFunction<T, S>;

And adding S extends T = T does not appear to solve the problem, AFAICT.

Yeah, sorry, good explanation @cartant - here's a stackblitz showing the problem https://stackblitz.com/edit/rxjs-pxbhzr

The filter(Boolean) bit is fixed now, and the rest is working as expected.


Add fish comments

Awesome thank. Btw have you checked set cms? for a random fish file? Is it the same with what you have added here?

It should actually by done like this: https://github.com/winston0410/commented.nvim/commit/a7fed2e21cdef40ee91d79460fbb53085931d5df
The reason being that is the only way of inline commenting in fish, and the set cms? of fish is originally /*%s*/. Setting the cms to #%s allow you to comment and uncomment correctly, instead of being able to only uncomment.


PAM config files are executable

The file rstudio-workbench/templates/_helpers.tpl has following:
{{- if .Values.config.pam }}
- name: rstudio-pam
  configMap:
    name: {{ include "rstudio-workbench.fullname" . }}-pam
    defaultMode: 0755

So pam config files are set to executable. Shouldn't those files have something like 0644 permissions?

Yes, great call - thanks for the heads up here! Laziness at its finest 😅


[BUG] Criteo example fail due to "Runtime error: file list open failed: ./criteo_data/file_list.txt"

Describe the bug
Criteo example fails because file_list.txt is missing
To Reproduce
Steps to reproduce the behavior:

Follow the step https://github.com/NVIDIA-Merlin/HugeCTR/tree/master/samples/criteo, running directly the docker image nvcr.io/nvidia/merlin/merlin-hugectr:22.07
Download and preprocess data using NVTabular
python3 ../samples/criteo/criteo.py

Expected behavior
Model trains
Screenshots

Environment (please complete the following information):

OS: # uname -a
Linux gke-us-central1-v3-t4x1-prod-v1-4a179b1d-l59w 5.4.188+ #1 SMP Tue May 24 10:06:08 PDT 2022 x86_64 x86_64 x86_64 GNU/Linux
Graphic card: T4
CUDA version: NVIDIA-SMI 470.82.01    Driver Version: 470.82.01    CUDA Version: 11.7
merlin-hugectr:22.07

Additional context
Add any other context about the problem here.

Preprocessing with perl does not have this problem. Seems nvt has some difference here.

@thuningxu could you please confirm the ./criteo_data/file_list.txt does exist? If there's no such file or the file is in wrong directory, the preprocessing may accout for it, otherwise the data reader may be buggy.

Hi @thuningxu , do you still have this problem in the latest release?


Feature:  run --compile-only

Is there an option to just see if the code compiles without flashing any chips?  This would be helpful for people who are testing what code does and doesn't get past the compile phase.
I hope I haven't overlooked an option to do this.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/13556678-feature-run-compile-only?utm_campaign=plugin&utm_content=tracker%2F2014790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2014790&utm_medium=issues&utm_source=github).

Hi @TheNotary!
platformio run builds your code.
platformio run -t upload flashes board with your firmware.

Looks like you have created a project with enabled auto-uploading. Just disable target = upload in your platformio.ini.

Ah, thanks, I knew I had to have been missing something.  I commented out the target = upload line in my platformio.ini file and can now commence further trial and error at learning type casting =)


Refactor to Node SDK

This change marks the starting point of the new MediaFire Node SDK which will be used in place of the older JavaScript SDK in upcoming MediaFire Projects. This new project is formatted as a standard Node Package and uses Babel and web pack to build the final deliverables.

This project will more than likely live in a separate repo than this SDK.


NullReferenceException while using OpenTo with MudDatePicker

Bug type
Component
Component name
MudDatePicker
What happened?
I get NullReferenceError while using MudDatePicker with OpenTo parameter
Expected behavior
Expected behavior is to open MudDatePicker for example with OpenTo="Year" and the component shows year selection list at initial state
Reproduction link
https://try.mudblazor.com/snippet/wuwQaBvdCbajWmme
Reproduction steps
You can reach the issue even in MudDatePicker sample codes in "Fixed Values Usage" section
Relevant log output
No response
Version (bug)
6.0.11
Version (working)
No response
What browsers are you seeing the problem on?
Firefox, Chrome, Microsoft Edge, Other
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

You're right, so I will close the issue to prevent redundancy.

I Reopened this one because you closed the previous one, and I think one should be opened to be referenced.


Implement coreference resolution

Use NLPTK, documentation can be googled.

Decided against coreference resolution in favor of synonym recognition.


date time invalid_argument to runtime_error

fix #211

coverage: 75.249%. remained the same when pulling ca5e942024ce904d49fff2ccf186d08a70cee3cc on fix/date_parsing_crash into acea2d852f54e82122c740e851f7c3eba8a35633 on develop.

What is the idea here? std::invalid_argument seems more specific than std::runtime_error. I think it would be better to handle std::invalid_argument instead of replacing it.

As we just learned, std::invalid_argument breaks existing code. And finding all instances of me throwning it is a lot easier/quicker than finding every instance where a std::runtime_error is cought, but a std::invalid_argument is not.


Manually add the release notes for v3.4.1 to changelog

This PR simply pulls in the changelog from version 3.4.1.

This changelog entry is fine for now, but once the announcement blog post is out, let's also add more details to the changelog entry itself.

I cherry picked those changes into #5182, synced it up and merged into master.


assert_eq: Better error messages

Consider this example:
>>> assert_eq(2m, 201cm, 0.1cm)
error: Assertion failed
  ┌─ <input:2>:1:15
  │
1 │ assert_eq(2m, 201cm, 0.1cm)
  │           --  ^^^^^ 201 cm
  │           │
  │           2 m
  │
  = Assertion failed because the following two quantities differ by more than 0.1 cm:
      2 m
      201 cm

This is not very helpful, since we show the LHS/RHS values in different units.
And if the contrived example is not enough, here's a real world error message that I got today:
>>> assert_eq(-77° + 0′ + 32″, -77.0089°, 1e-4°)
error: Assertion failed
  ┌─ <input:1>:1:28
  │
1 │ assert_eq(-77° + 0′ + 32″, -77.0089°, 1e-4°)
  │           ---------------  ^^^^^^^^^ -77.0089°
  │           │
  │           -1.34375
  │
  = Assertion failed because the following two quantities differ by more than 0.00000174533:
      -1.34375
      -77.0089°

We certainly want to do a unit conversion here (to the same unit that is also used for the actual comparison, I would guess the LHS unit). Maybe we even want to show a comparison in the two possible units (the LHS unit and the RHS unit)?

I'm thinking of contributing this feature.
I think converting both lhs and rhs to epsilon (the maximum expected difference) would be the most intuitive and would allow a user to see the difference in different units easily if desired by changing the unit of epsilon and without having to mess with the lhs or rhs expressions.
For example:
>>> assert_eq(2m, 201cm, 0.1cm)
error: Assertion failed
  ┌─ <input:1>:1:15
  │
1 │ assert_eq(2m, 201cm, 0.1cm)
  │           --  ^^^^^ 201 cm (201 cm)
  │           │
  │           200 cm (2 m)
  │
  = Assertion failed because the following two quantities differ by more than 0.1 cm:
      200 cm (2 m)
      201 cm (201 cm)

>>> assert_eq(2m, 201cm, 0.1mm)
error: Assertion failed
┌─ <input:4>:1:15
│
1 │ assert_eq(2m, 201cm, 0.1mm)
│           --  ^^^^^ 2010.0 mm (201 cm)
│           │
│           2000 mm (2 m)
│
= Assertion failed because the following two quantities differ by more than 0.1 mm:
    2000 mm (2 m)
    2010.0 mm (201 cm)

The original values are written in parentheses but it feels a bit redundant, so I could be convinced to remove it.
Note that, in the second example with degrees, epsilon is converted to radians at some point before the core assertion is handled. So with this change the comparison would be done in radians. Expressions like -77° + 0′ + 32″ are also converted to radians automatically.
>>> assert_eq(-77° + 0′ + 32″, -78.0089°, 1°)
error: Assertion failed
  ┌─ <input:6>:1:28
  │
1 │ assert_eq(-77° + 0′ + 32″, -78.0089°, 1°)
  │           ---------------  ^^^^^^^^^ -1.36151 (-78.0089°)
  │           │
  │           -1.34375 (-1.34375)
  │
  = Assertion failed because the following two quantities differ by more than 0.0174533:
      -1.34375 (-1.34375)
      -1.36151 (-78.0089°)

I'm thinking of contributing this feature.

Cool! Let us know if you need help.

I think converting both lhs and rhs to epsilon (the maximum expected difference) would be the most intuitive and would allow a user to see the difference in different units easily if desired by changing the unit of epsilon and without having to mess with the lhs or rhs expressions.

This sounds very reasonable, and your example output looks great to me.

The original values are written in parentheses but it feels a bit redundant, so I could be convinced to remove it.

I like it.

Note that, in the second example with degrees, epsilon is converted to radians at some point before the core assertion is handled.

Oh, ok. This is something very specific to angles, since they "decay" to scalars (in radian), as you observed. So let's ignore this for now and maybe discuss this elsewhere. If you are interested in the topic, see also: #167

One thing that I think is missing after #527, is allowing users to get more precision in the error message by adding 0s to epsilon.
In the example below, ideally I think it would show 3 decimal places of precision:
assert_eq(212121000.123456cm, 212121001.123456cm, 0.900cm)
error: Assertion failed
  ┌─ <input:23>:1:31
  │
1 │ assert_eq(212121000.123456cm, 212121001.123456cm, 0.900cm)
  │           ------------------  ^^^^^^^^^^^^^^^^^^ 212121001.1 cm
  │           │
  │           212121000.1 cm
  │
  = Assertion failed because the following two quantities differ by 1.0 cm, which is more than 0.9 cm:
      212121000.1 cm
      212121001.1 cm

Implementing this would probably require some way to carry the user's desired precision alongside the epsilon Quantity.
To work around this one would need to add a 1 in the last decimal place, though this could change the comparison slightly.

I'm not super concerned about the trailing zero problem.
But I found some cases where the current implementation leads to problems. It might only be relevant for angles since they have this weird simplification behavior. Take a look at the new output for the input suggested in the first post:
>>> assert_eq(-77° + 0′ + 32″, -77.0089°, 1e-4°)
error: Assertion failed
  ┌─ <input:2>:1:28
  │
1 │ assert_eq(-77° + 0′ + 32″, -77.0089°, 1e-4°)
  │           ---------------  ^^^^^^^^^ -1.3440588583390611000000 (-77.0089°)
  │           │
  │           -1.3437483836576787000000
  │
  = Assertion failed because the following two quantities differ by 0.0003104746813824555000, which is more than 0.0000017453292519943296:
      -1.3437483836576787000000
      -1.3440588583390611000000 (-77.0089°)

That illustrates a few problems:

Epsilon is converted to a scalar at some point so we compare scalar values
In the deg->rad conversion, 1e-4° turns into a irrational number, which means that we use the maximum number of digits. Far too many for the given precision.
We don't show the value in degrees for the left-hand-side argument.

Oh hold on. That will actually be fixed by #537. I'll add a regression test in there.


feature: add assert resource method for tests

How it add value
This PR adds the capability to test a resource against a response.
The idea comes from Laracon Summer 2021, in Colin DeCarlo's talk.
It adds the ability to test the whole response with a oneliner instead of replicating the complete response structure.
The main advantage of this assertion is when someone changes a resource structure (remove or change a key and/or a value) there would be no need to refactor all the tests that have assertions with a hard code structure.
Usage
For a single model resource:

```php
// create a user and a post that belongs to the user
$user = User::factory()->create();
$post = Post::factory()->for($user, 'author')->create();

// ACT - Create
$response = $this->actingAs($user)->getJson(route('api.users.posts.show', $post));

$resource = PostResource::make($post->load('authors'));
$response->assertResource($resource);

It also works for collections and paginated collection resources:

// create a user and a post that belongs to the user
$user = User::factory()->create();
$posts = Post::factory()->for($user, 'author')->count(10)->create();

// ACT - Create
$response = $this->actingAs($user)->getJson(route('api.users.posts.show', $posts));

$resource = PostResource::make(Post::query()->with('authors')->paginate());
$response->assertResource($resource);

Hope it would be useful.
Thanks.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

Hi @taylorotwell thanks for the time to review the PR, I think that it saves a lot of time to test an endpoint that could return a resource.
I plan to make a package for this assertion and some useful assertions, I would find your thoughts about why you think this assertion is not approved and if you think that it could help another developer as a package or is a redundant test method.
Thanks for your time and the great effort that the Laravel team do.


chore: remove unnecessary lock from nodeserver_v2

What type of PR is this?
/kind cleanup

What this PR does / why we need it:

nodeserver_v2 is missing changes made in nodeserver from https://github.com/abhisheksinghbaghel/azuredisk-csi-driver/commit/d67f1710cfeaa346357fbccd83e87cd860b05e1d#diff-156099288763837ad0c787f45bac8fd4d37c584f17956cbdb0287cadeb845221

Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 42.721%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
179

Relevant Lines:
419

💛  - Coveralls


Fix: SocreCard.jsx is now working as expected.

I have identified the issue and fixed the problem that led to scoreCard not working earlier.

@Spyware007 please check and merge PR.


pool: ignore source port

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

test_ztunnel
ebb9d952a8ecf92e40a8684c2f8016d968c47c59
link
true
/test test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


wxGridBagSizer Rows and Cols cannot edit

I just add a frame to the application, and change the sizer_1 to wxGridBagSizer. On the Grid tab, everytime I click the Rows and Cols, the wxglade crashes. I've tried the other six Sizer, all work well.
and the error info is as below:
ERROR   : None
An unexpected error occurred!
Exception type:      <class 'IndexError'>
Exception details:   list index out of range
Application stack traceback:
File "C:\Program Files\Python36\lib\site-packages\wx\core.py", line 3240, in
lambda event: event.callable(*event.args, **event.kw) )
File "F:\Download\wxGlade-0.8.3\edit_sizers\edit_sizers.py", line 561, in change_sizer
szr._check_slots(remove_only=True)  # mark overlapped slots
File "F:\Download\wxGlade-0.8.3\edit_sizers\edit_sizers.py", line 2138, in _check_slots
occupied = set( self._get_occupied_slots() )
File "F:\Download\wxGlade-0.8.3\edit_sizers\edit_sizers.py", line 2112, in _get_occupied_slots
child = self.children[pos]
Date and time:       2018-09-06T16:11:12.516409
Python version:      3.6.6
wxPython version:    4.0.3
wxWidgets platform:  WXMSW
wxGlade version:     0.8.3

Thanks for reporting. It seems that there are some issues when the number of rows or cols is 1.
I will try to fix as soon as possible.

This seems to be quite tricky. It will proably take me some days.

It should work now in the master branch.

yes, it works now, thank you very much.


PowerShell doesn't set PATH in fish

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Running fish shell
Installing PowerShell over brew
Expected behavior
PowerShell should be in PATH and run by pwsh.
Fish set path different than zsh.

Instead of "export" you use "fish_add_path".

Actual behavior
No Path is set

Error details
No response
Environment data
Name                           Value

PSVersion                      7.2.1
PSEdition                      Core
GitCommitId                    7.2.1
OS                             Darwin 21.4.0 Darwin Kernel Version 21.4.0: Mon…
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0
No avalible

Visuals
No response
~  pwsh
fish: Unknown command: pwsh

Please share Environment data

Please share Environment data

How? If im unable to run PowerShell

Done!

We do not set the PATH when installing through HomeBrew. It seems like it should be filed as an issue for HomeBrew.

After PoweShell installer is run it installs itself to a non regularly directory. Thus a Path must be set.
This is the job of the PowerShell installer and not HomeBrew. Except if PowerShell was a formula but this is a cask with a proprietary installer.

I checked again.
The script for the PATH is inside the pkg.
Please reopen this issue again!

@msftbot reopen

/reopen

Please reopen this issue! It is still there. (It seems that PWSH is trying to push us to stand on python closer.)


hi my friend

hi my friend i need your help can you help me on this project?

Hello, I am sorry for not replying to you sooner. I did not get a notification of this issue.
What do you need help with?


Add gcp_iam_role_dashboard closes #17

Checklist

[ ] Issue(s) linked

Closing draft PR as it's stale, will re-open if required.