Unable to read QR

Hi all,
We're trying to decrypt a QR-code we received from our instances.
But when I try to decode it. The COSE signature seems to be different.
Shouldn't all COSE signatures be the same across countries?
A colleague of mine used the Android implementation and he's able to decode a QR code which was generated on https://dgc.a-sit.at/ehn/ and is also able to scan a QR-code our instance created..
Could you somehow help me with the different implementations.. Because I don't fully understand why Android does work and the iOS code is so much different..

Hi,
Can it be related to https://github.com/ehn-digital-green-development/ValidationCore/issues/5 ?

Indeed it seems that our cose is nog tagged.
And I updated the implementation like this
init?(from data: Data) {
        guard let decodedData = try? CBOR.decode(data.bytes) else {
            return nil
        }

        if let cose = try? CBORDecoder(input: data.bytes).decodeItem()?.asCose(),
           let type = CoseType.from(tag: cose.0),
           let protectedHeader = CoseHeader(from: cose.1[0]),
           let signature = cose.1[3].asBytes() {
            self.type = type
            self.protectedHeader = protectedHeader
            self.unprotectedHeader = CoseHeader(from: cose.1[1])
            self.payload = cose.1[2]
            self.signature = Data(signature)
        } else {
            guard let decodedDataList = decodedData.asList() else {
                return nil
            }

            let headerCBOR = decodedDataList[0]
            guard let header = CoseHeader(from: headerCBOR) else { return nil }
            self.protectedHeader = header

            let text = decodedDataList[2]
            self.payload = text

            self.unprotectedHeader = nil
            self.signature = decodedDataList[3].asData()
            self.type = .sign1
        }
    }

Thank you for sharing your code, I needed to make a change for it to work with https://dev.a-sit.at/certservice.
From
CoseHeader(from: ...
to
CoseHeader(fromBytestring: ...
Did you try with https://dev.a-sit.at/certservice using your code?

@DKvarn I din't test my code using a COSE (Base45) from the certservice since I received another signature from our instances..

Hi,
thank you for the feedback. Unfortunately, different COSE libraries will output quite different structures. As there is currently no clarification how to handle untagged structures, I changed the initializer based on your code to process them as well. It works with codes generated by https://dgc.a-sit.at/ehn (the successor of dev.a-sit/certservice). @HannesVDB Could you please check the changes against your implementation and close this issue, if it is resolved?

@asitdm I have looked at your change and with my examples we have List but I need to use CoseHeader(fromBytestring: ... now it use CoseHeader(from: ... for List so that's a problem for me. Should be support that the header can be in both formats? Then it should support that for both tagged and not tagged, or?

@DKvarn Could you by chance give ma a link to your generation service or provide one of your QR codes for testing?

@asitdm or @DKvarn the qr-code we have from our authorities is:
HC1:NCF3TDJ%B6FL9SS8UVTKULG8W9WFI1Y%7NDC3LE $CZK9TNVTWG4G5WJAN9HNO4*J8OX4W$C2VLWLIML5PYH1LALX95Y58XEDXH8NI7 93W1*%EVC2QX5$W5R$9:V5VQIZ0Q:O1NTICZU5/GX/KR96/-KKTCY73JC3DG3IFTG233ZC%CTVMFD-48YI 35Z/KCZKK3JC-4D-4HRVUMNMD3*20EJK-+K.IA9D88QEI1KY/F0JAXD15IAXMFU*GSHGRKMXGG6DBYCB-1JMJKR.KI91L4DWZJ$7K+ CMED:NKDAD1QD.ZJI7JSTNB95.16EAOEYK8L6R95D261L5N/5.KMVE4+Y5GT4D:7VT4IVQSA7G6MY1SADSKVQQQ6JINQ+MN/Q19QE8QNQOTZ8$3H9*R0MPI:140IEFFQ.7Z93S MU3T82SNFTI1F6S3HO509W4:E5P7GLT*PC2HR+FL:FOBVVCGA:SB*TSKAM+4UL5MBMDCTPB854G0TTE

Which is signed with:
-----BEGIN CERTIFICATE-----
MIICLTCCAZYCAQEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCQkUxEzARBgNV
BAgMClNvbWUtU3RhdGUxCzAJBgNVBAoMAlZPMQ4wDAYDVQQLDAVNQUdEQTEPMA0G
A1UEAwwGQ0EtREVWMSswKQYJKoZIhvcNAQkBFhxvcnR3aW4uam9uaWF1eEB2bGFh
bmRlcmVuLmJlMB4XDTIxMDUwNTEwMjEzOVoXDTIyMDUwNTEwMjEzOVowgYcxCzAJ
BgNVBAYTAkJFMRMwEQYDVQQIDApTb21lLVN0YXRlMQswCQYDVQQKDAJWTzEOMAwG
A1UECwwFTUFHREExGTAXBgNVBAMMEERFVi1BdHRlc3RhdGlvbnMxKzApBgkqhkiG
9w0BCQEWHG9ydHdpbi5qb25pYXV4QHZsYWFuZGVyZW4uYmUwWTATBgcqhkjOPQIB
BggqhkjOPQMBBwNCAATeOZDvexQEQOmQohMeBCkyrIw7w9B16TcXFRfAOmmmg2nv
xkChDQHlkwaGG8NhFkeUET3sAShyVM1duny+16yuMA0GCSqGSIb3DQEBCwUAA4GB
AKue+KOyCv4/GAF28PC5ZWL9n9nt86x4LoftWji76uTTC+1QVWLhyFhfvXMfhArn
u9OY/Te1jIyxWROuJv5QVa8h5BMpvV2DdFd7YmpoRN+UuAs6Dd+ve+m82up0Yww/
r4cnUsPorHGNPbBILJOXxhxi9mu1Jrd4pgWr+oXTipft
-----END CERTIFICATE-----

It seems that it's not possible to decode de CBOR.. So I updated the init from the Cose.swift to the following
init?(from data: Data) {
        guard let decodedData = try? CBOR.decode(data.bytes) else {
            return nil
        }

        guard let decodedDataList = decodedData.asList() else {
            return nil
        }

        let headerCBOR = decodedDataList[0]
        guard let header = CoseHeader(from: headerCBOR) else { return nil }
        self.protectedHeader = header

        let text = decodedDataList[2]
        self.payload = text

        self.unprotectedHeader = nil
        self.signature = decodedDataList[3].asData()
        self.type = .sign1
    }

Where the CoseHeader has the following init
init?(from cbor: CBOR) {
            guard let cborMap = cbor.decodeBytestring()?.asMap() else { return nil }
            guard let alg = cborMap[1],
                  let value = alg.asUInt64(),
                  let algortithm = Algorithm(rawValue: value) else {
                return nil
            }
            self.algorithm = algortithm
            self.keyId = cborMap[4]?.asBytes()
            self.rawHeader = cbor
        }

This works for the decode of the CBOR.. But the TrustlistService can't decode my .der or .cert I created..
Any ideas how we could update this?

Your data decodes as:
 pbpaste | sed -e 's/^HC1://'   | base45 --decode | zlib-flate -uncompress | cose_dumper
 [
   h'a201260448cbe813fb712a0fab',
   {},
        h'a401624245041a60b9ff14061a60927214390103a101a4617681aa626369782432326437356138322d623364632d343330332d626131382d38653537383963613736313562636f62424562646e016264746a323032312d30342d30326269736f654865616c74682042656c6769756d626d616d4f52472d313030303031363939626d706643566e436f5662736402627467693834303533393030366276706a3131313933343930303763646f626a313938342d31322d3133636e616da462666e664f727477696e62676e674a6f6e6961757863666e74664f525457494e63676e74674a4f4e494155586376657265312e302e30',

h'04160c04574da4fcf0dac56a4839e6b95cc57d99a82d8d5bf83e370885a8adfd3b43ed9242d9015756a45a5b51e52f7d5a3f0ab05e4bd4db8a7379f537aa3ce5'
]
So expected was a tag (18) followed by an array of 4 entries. It is untagged.
The protected header then breaks into
  echo a201260448cbe813fb712a0fab | xxd -r -p | cbor2js
 Map(2) {
   1 => -7,
   4 => <Buffer cb e8 13 fb 71 2a 0f ab>
 }

which s exactly what you'd expect. Then the empty unprotected header {} is also fine.
The main payload:
echo a401624245041a60b9ff14061a60927214390103a101a4617681aa626369782432326437356138322d623364632d343330332d626131382d38653537383963613736313562636f62424562646e016264746a323032312d30342d30326269736f654865616c74682042656c6769756d626d616d4f52472d313030303031363939626d706643566e436f5662736402627467693834303533393030366276706a3131313933343930303763646f626a313938342d31322d3133636e616da462666e664f727477696e62676e674a6f6e6961757863666e74664f525457494e63676e74674a4f4e494155586376657265312e302e30 | xxd -r -p | cbor2js
 Map(4) {
   -260 => Map(1) {
     1 => {
       dob: '1984-12-13',
       nam: {
         fn: 'Ortwin',
         fnt: 'ORTWIN',
         gn: 'Joniaux',
         gnt: 'JONIAUX'
       },
       v: [
         {
           ci: '22d75a82-b3dc-4303-ba18-8e5789ca7615',
           co: 'BE',
           dn: 1,
           dt: '2021-04-02',
           is: 'eHealth Belgium',
           ma: 'ORG-100001699',
           mp: 'CVnCoV',
           sd: 2,
           tg: '840539006',
           vp: '1119349007'
         }
       ],
       ver: '1.0.0'
     }
   },
   1 => 'BE',
   4 =><PHONE_NUMBER>,
   6 =><PHONE_NUMBER>
 }

Looks fine. As do the 64 raw bytes of the signature:
  echo 04160c04574da4fcf0dac56a4839e6b95cc57d99a82d8d5bf83e370885a8adfd3b43ed9242d9015756a45a5b51e52f7d5a3f0ab05e4bd4db8a7379f537aa3ce5 | xxd -r -p | wc -c
  64

If we take the certificate and extract the public keys from it
RAW=$(echo `pbpaste | openssl x509  -noout -pubkey | openssl pkey  -pubin -text | grep '^ '` | sed -e 's/[: ]*//g'
RAW=$(echo $RAW | sed -e 's/^04//')
X=$(echo $RAW | cut -c 1-64)
Y=$(echo $RAW | cut -c 65-128)

we get
RAW=04de3990ef7b140440e990a2131e042932ac8c3bc3d075e937171517c03a69a68369efc640a10d01e59306861bc361164794113dec01287254cd5dba7cbed7acae
X=de3990ef7b140440e990a2131e042932ac8c3bc3d075e937171517c03a69a683
Y=69efc640a10d01e59306861bc361164794113dec01287254cd5dba7cbed7acae

With X and Y the public keys that should match the signature of above. I've not tried that (https://github.com/ehn-digital-green-development/ehn-sign-verify-python-trivial does not support untagged signatures).

Hi,
thanks to your example, I was able to fix the support for untagged COSE structures.
Unfortunately the included trustlist service is tailored to the structure provided by https://dgc.a-sit.at/ehn/ and instantiates the public key directly from an PKCS#1/X9.63 structure. For this reason, it is not able to parse certificates.
I turned the TrustlistService into a protocol and renamed our implementation to DefaultTrustlistService. You should be able to fix this by writing your own trustlist service, which parses your certificate and create a SecKey from it, and provide it as argument in the constructor of the ValidationCore struct.

@asitdm awesome!
I will start with a custom TrustlistService and create a PR!
Thanks for your help!

For kotlin I found that the trustlist provided by https://dgc.a-sit.at/ehn/ is only implmented in the sample app. not in the hcert library itself. So maybe this should be moved out of this repository and into the sample app. That would make more sense I think.

@HannesVDB Glad to help :)
The proposal sounds interesting, we will discuss that internally!


 I'll close #5100 in favor of yours.

/lgtm


Update "Implementation Status" section

The information in this section doesn't appear to be relevant. May somebody update the state of the table?

what parts are wrong? if you see something that is not correct, feel free to submit a PR with proposed changes.


Added newlines around div tags

Fixes domchristie/to-markdown#49
Previously div tags were ignored.  Now they are treated the same way
p tags are treated.
Added matching test, bumped package.json version.
Added repository field to package.json so the repository is easier
to find from npm.
The test suite passes my new test, but breaks during the headless
browser tests (for me).  I suspect they will continue working as well as
they did before, and this is just an environment issue, because I didn't
change much.

I still think this is a suitable PR, what would the objection to it be?  div elements take up full horizontal space by default, so creating a linebreak seems like a pretty un-controversial markdown conversion to me.


Objects appear completely black in image

I have an issue where the albedo and image render as completely black.
I first suspected that this is due either to

the directory of the texture images being incorrect relative to the OBJ files, or
the directory of the texture images being incorrect relative to the rendering script.

I put the shapenet OBJ files in a directory called shapenet/models. I placed the rendering script in the shapenet directory, and ran blender from that directory. I have tried placing the textures directory in the models directory, placing it in theshapenet directory, and copying the JPG texture images directly into the models directory, to no avail.
Upon inspecting, the logs seem to indicate that the materials and images are loaded:
(  0.0000 sec |   0.0000 sec) Importing OBJ 'models/17c318cf53f978d22feb9fdea8e07927.obj'...
  (  0.0002 sec |   0.0002 sec) Parsing OBJ file...
    (  0.0525 sec |   0.0523 sec) Done, loading materials and images...
    (  0.0563 sec |   0.0560 sec) Done, building geometries (verts:13968 faces:4656 materials: 4 smoothgroups:0) ...
    (  0.0781 sec |   0.0778 sec) Done.
  (  0.0782 sec |   0.0781 sec) Finished importing: 'models/17c318cf53f978d22feb9fdea8e07927.obj'
Progress: 100.00%

So I now suspect that this has something to do with the lighting/scene settings instead. I'll place the settings here in case there's anything I'm obviously missing.
Settings
Views: 30 (default)
Obj: models/17c318cf53f978d22feb9fdea8e07927.obj
Output Folder: tmp (note: local, not the OS /tmp)
Scale: 0.005 (note: gave good results for the normals)
Remove doubles: False
Edge Split: True
Depth Scale: 1.4
Color Depth: 8 (also tried 16)
Format: PNG
Resolution: 2000
Engine: BLENDER_EEVEE (also tried CYCLES, got even more degenerate results, entire image was black and normals/depth were empty)
Outputs
Albedo:

Depth:

Normal:

Image:

I meet the problem, too.


success modal view has no header any more

@yaseminc what do you think from design perspective?

commit
file reference
pull request

cc0039852364826fd8df3cd557df3d25ff0f0521
src/client/modals/templates/linkSuccess.html#L3
#50

was there a specific reason to leave it out?

I suppose the the header and the content were repeating each other. Maybe we can use another wording there, like "Well done" or "Success", "Congrats" ...
@yaseminc, @dfarr what do you think about it?

I thought it already said "success"?

it was "You created a new link!"

I'm not sure if it's better now or not. @yaseminc ?

I am not sure either. First, the space above and beneath 'Success' is definitely too much... My view is first led to the illustration, then to the button, afterwards I read the text below the illustration. The headline is floating and the words double in the meaning.. @KharitonOff could you send me a shot of the very first mockup I did for this to compare, please?


Add ExternalName to model.Service

Please provide a description of this PR:
In 1.17 we filter service events by comparing services(https://github.com/istio/istio/pull/42617). However the comparison does not take ExternalName into account since model.Service does not include it. It does matter because ExternalName is used to generate endpoints for DNS clusters.
This bug is breaking Knative
Fixes https://github.com/istio/istio/issues/43440
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[ ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@dddddai: 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

integ-security_istio
c42a91ee04ea40682fd3658cfa18c20bbcc7d17a
link
true
/test integ-security

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.

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

Test name
Commit
Details
Required
Rerun command

integ-security_istio
c42a91ee04ea40682fd3658cfa18c20bbcc7d17a
link
true
/test integ-security

integ-security-istiodremote_istio
c42a91ee04ea40682fd3658cfa18c20bbcc7d17a
link
true
/test integ-security-istiodremote

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.

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

Test name
Commit
Details
Required
Rerun command

integ-security_istio
c42a91ee04ea40682fd3658cfa18c20bbcc7d17a
link
true
/test integ-security

integ-security-istiodremote_istio
c42a91ee04ea40682fd3658cfa18c20bbcc7d17a
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio
c42a91ee04ea40682fd3658cfa18c20bbcc7d17a
link
true
/test integ-security-multicluster

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.

@dddddai Is this a regression or always there?

No, before 1.17 we always push when a service is updated

We should make sure everything that affects xDS is in model.Service

That's hard for some fields that are not read from Service, like ExternalName

/retest

did you try setting ISTIO_ENABLE_OPTIMIZED_SERVICE_PUSH to false?

did you try setting ISTIO_ENABLE_OPTIMIZED_SERVICE_PUSH to false?

Yes, disabling it fixes https://github.com/istio/istio/issues/43440

Curious if you also handle FQDN on EndpointSlices?
https://kubernetes.io/docs/concepts/services-networking/endpoint-slices/#address-types

In response to a cherrypick label: new pull request created: #43469

@dddddai Is it possible to add a integration test for this?

afaik we do not support fqdn in ES: https://github.com/istio/istio/issues/34995 @dprotaso

@dddddai Is it possible to add a integration test for this?

Do you mean testing ExternalName updates triggering xDS pushes? If so a util test would be enough IMHO

Do you mean testing ExternalName updates triggering xDS pushes? If so a util test would be enough IMHO

Yes. Basically at test case that could have caught this miss


Exit Code Issue

I am not getting an exit code when using --old-exit-code

It works (verified with v2.4.1). See following:
cmd>log4j2-scan.exe --old-exit-code d:\tmp
Logpresso CVE-2021-44228 Vulnerability Scanner 2.4.1 (2021-12-21)
Scanning directory: d:\tmp
[*] Found CVE-2021-45105 (log4j 2.x) vulnerability in d:\tmp\2_16\log4j-core-2.16.0.jar, log4j 2.16.0
[*] Found CVE-2021-45046 (log4j 2.x) vulnerability in d:\tmp\apache-log4j-2.15.0-bin\apache-log4j-2.15.0-bin\log4j-core-2.15.0-sources.jar, log4j 2.15.0 (mitigated)
..snip..
[*] Found CVE-2021-44228 (log4j 2.x) vulnerability in d:\tmp\verify\log4j-core-2.13.1.jar, log4j 2.13.1 (mitigated)
[*] Found CVE-2021-44228 (log4j 2.x) vulnerability in d:\tmp\verify\log4j-core-2.14.1.jar, log4j 2.14.1 (mitigated)
[*] Found CVE-2021-45105 (log4j 2.x) vulnerability in d:\tmp\verify\log4j-core-2.16.0.jar, log4j 2.16.0

Scanned 5738 directories and 34169 files
Found 5 vulnerable files
Found 2 potentially vulnerable files
Found 15 mitigated files
Completed in 22.77 seconds

cmd>echo %ERRORLEVEL%
7

Works with 2.4.1 on macOS.
➜  CVE-2021-44228-Scanner git:(main) target/log4j2-scanner --old-exit-code ~/Downloads/log4j
Logpresso CVE-2021-44228 Vulnerability Scanner 2.4.1 (2021-12-21)
Scanning directory: /Users/christian/Downloads/log4j
[*] Found CVE-2021-44228 (log4j 2.x) vulnerability in /Users/christian/Downloads/log4j/log4j-core-2.14.0.jar, log4j 2.14.0
[*] Found CVE-2021-45105 (log4j 2.x) vulnerability in /Users/christian/Downloads/log4j/log4j-core-2.16.0.jar, log4j 2.16.0
[*] Found CVE-2021-45046 (log4j 2.x) vulnerability in /Users/christian/Downloads/log4j/log4j-core-2.15.0.jar, log4j 2.15.0
[*] Found CVE-2021-44228 (log4j 2.x) vulnerability in /Users/christian/Downloads/log4j/loggingBuddies.war (log4j-core-2.14.0.jar), log4j 2.14.0
[*] Found CVE-2021-45046 (log4j 2.x) vulnerability in /Users/christian/Downloads/log4j/loggingBuddies.war (log4j-core-2.15.0.jar), log4j 2.15.0
[*] Found CVE-2021-45105 (log4j 2.x) vulnerability in /Users/christian/Downloads/log4j/loggingBuddies.war (log4j-core-2.16.0.jar), log4j 2.16.0

Scanned 1 directories and 5 files
Found 4 vulnerable files
Found 0 potentially vulnerable files
Found 0 mitigated files
Completed in 0.36 seconds
➜  CVE-2021-44228-Scanner git:(main) printf '%d\n' $?
4

Yeah, my bad. My procedure in my RMM had a typo, -old-exit-code.


Allow depending on either v1 or v2 of random_compat

Projects that use random_compat v1 are not compatible with oauth2-client. One such example is laravel 5.1 LTS. Since random_compat v1 and v2 are functionally same, it should allow composer decide which version to install based on what other projects use.

Changes Unknown when pulling 6409c2ed12efbcd4c3ab2d625f5852cf05bf1b55 on pravindahal:master into ** on thephpleague:master**.

Changes Unknown when pulling 6409c2ed12efbcd4c3ab2d625f5852cf05bf1b55 on pravindahal:master into ** on thephpleague:master**.

Changes Unknown when pulling 6409c2ed12efbcd4c3ab2d625f5852cf05bf1b55 on pravindahal:master into ** on thephpleague:master**.

:+1:


 Xcode cannot find a team matching '2WQE6AU5PD'.
No signing certificate "Mac Development" found:  No "Mac Development" signing certificate matching team ID "2WQE6AU5PD" with a private key was found.
运行弹这个错是什么原因，是需要我的开发账号要在一个mac development里？

恩，要选下自己的开发team和证书。

我没有mac development是不是就运行不了了，我没有mac development team

你有iOS的就有Mac的。


Add tx2 car model.

This PR is adding the tx2 car model in the simulation.
Once we finalize the hardware of our car it should be relatively easy to change the shape.
ros2 launch maila_2d_sim sim.launch.py

Relates to: MAILA-24

I have also added the willow garage world that might be useful for some first testing of the navigation stack.

@ValerioMa We should use git LFS for binary files (i.e. *pgm). In my experience binary files can blow up the repository.
Further information: GitHub LFS

@ValerioMa Could you also add a README.md with usage information?


Workaround a bug in windows cmd

When calling flyway using System.Diagnostics.Process in .Net to create a database as part of my test suite setup I encountered a bug in Windows CMD with how %~dp0 is resolved, a bit of information and the solution I borrowed from can be found here: https://stackoverflow.com/a/26851883

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

Hmmm interesting... I had no idea! Thanks for the fix!


cl_khr_command_buffer::info_state does not check the state after the command buffer has completed execution

Once a command buffer completes execution (assuming no other pending instances), its state should be transitioned back to CL_COMMAND_BUFFER_STATE_EXECUTABLE_KHR. The info_state test should check that.

There is already state verification for RunStateInfoTests():
error = verify_state(CL_COMMAND_BUFFER_STATE_EXECUTABLE_KHR);
test_error(error, "verify_state failed");

Could you please specify the details of the requirements for the tests? What other tests should be extended here?

@kpet at the moment such a scenario is tested in CommandBufferGetCommandBufferInfo::RunStateInfoTest, I think we can close that issue.

It looks like this was fixed by https://github.com/KhronosGroup/OpenCL-CTS/pull/1740 but the issue was never closed. Closing now.


Preserve Data - Books and Labels

Hi, I did the following tasks:
All data should be preserved by saving collections in .json files.
Books.
Labels.

Status: Aproved
Congratulations @jlberbesi ! Your task is complete! There's nothing more to say other than... It's time to merge :shipit: !!
Highlights
✔Applied changes
✔Saving and loading works for books and label
✔Linters pass


Badge ID must be upper case when badge creation from the frontend

Solved. Tested in UI and with postman.


Error Install botnet

Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/run
Operating System: linux
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.When installing dotnet, when I enter the commands to be installed, this error is seen at the end of the work. Can anyone help?
E: Couldn't find any package by glob 'dotnet-sdk-5.0'
E: Couldn't find any package by regex 'dotnet-sdk-5.0'

Hi @GameOver61
Which Linux distro are you using?


Unify some functions in pkg/agent/route

This PR unifies the functions in route_linux.go and route_windows.go:

AddLoadBalancer
DeleteLoadBalancer

Remove:

DeleteClusterIPRoute
AddClusterIPRoute

Fix:

Add the route for calculated ClusterIP CIDR to Service route cache,
then the route can be restored when it was deleted since members of
the route cache are synchronized periodically.

Signed-off-by: Hongliang Liu<EMAIL_ADDRESS>

/test-windows-proxyall-e2e

/test-windows-proxyall-e2e

/test-windows-e2e

/test-all

/test-e2e

Codecov Report

Merging #3889 (50c1db6) into main (b8279c9) will decrease coverage by 9.29%.
The diff coverage is 6.66%.

@@            Coverage Diff             @@
##             main    #3889      +/-   ##
==========================================
- Coverage   64.41%   55.12%   -9.30%
==========================================
  Files         291      292       +1
  Lines       42795    43200     +405
==========================================
- Hits        27568    23812    -3756
- Misses      13003    17429    +4426
+ Partials     2224     1959     -265

Flag
Coverage Δ

kind-e2e-tests
31.07% <6.66%> (-19.68%)
:arrow_down:

unit-tests
44.58% <0.00%> (-0.21%)
:arrow_down:

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

Impacted Files
Coverage Δ

...gent/controller/noderoute/node_route_controller.go
54.86% <0.00%> (-1.26%)
:arrow_down:

pkg/agent/proxy/proxier.go
58.42% <ø> (-3.53%)
:arrow_down:

pkg/agent/route/route_linux.go
24.97% <7.14%> (-22.99%)
:arrow_down:

pkg/agent/nodeportlocal/k8s/annotations.go
0.00% <0.00%> (-84.45%)
:arrow_down:

...g/agent/apiserver/handlers/featuregates/handler.go
4.54% <0.00%> (-77.28%)
:arrow_down:

pkg/agent/nodeportlocal/k8s/npl_controller.go
0.00% <0.00%> (-61.13%)
:arrow_down:

pkg/apis/controlplane/v1beta2/helper.go
40.00% <0.00%> (-60.00%)
:arrow_down:

...agent/controller/traceflow/traceflow_controller.go
14.03% <0.00%> (-58.93%)
:arrow_down:

pkg/agent/nodeportlocal/portcache/port_table.go
8.75% <0.00%> (-58.75%)
:arrow_down:

pkg/agent/nodeportlocal/npl_agent_init.go
0.00% <0.00%> (-57.15%)
:arrow_down:

... and 114 more

/test-windows-proxyall-e2e
/test-windows-e2e
/test-e2e

/test-windows-proxyall-e2e
/test-windows-e2e

/test-windows-proxyall-e2e
/test-windows-e2e

/test-windows-proxyall-e2e
/test-windows-e2e

/test-windows-proxyall-e2e
/test-windows-e2e

/test-windows-proxyall-e2e
/test-windows-e2e

Could you have a look at this PR when you are available? @tnqn @jianjuns Thanks!

/test-all

/test-windows-all

/test-all
test-windows-all

@tnqn @wenyingd Do you have any further comments? Thanks.

/test-windows-all

Do we still have time to verify and merge this PR @tnqn ?

/test-all
/test-windows-all
/test-ipv6-all
/test-ipv6-only-all

/test-all
/test-windows-all

/test-all
/test-windows-all

Do you have any further comment? Thanks @tnqn

/test-all
/test-windows-all

/test-windows-networkpolicy
/test-windows-conformance
/test-windows-networkpolicy

/test-windows-containerd-networkpolicy

/test-windows-conformance

/test-windows-containerd-networkpolicy


Parser doesn't handle local variable declaration with no initial value

Declaring a variable with no initial value is supported in TIC-80's Lua implementation, but results in a ParseException in Pakettic:
local x

Traceback (most recent call last):
  File "/usr/local/bin/pakettic", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/usr/local/lib/python3.11/site-packages/pakettic/main.py", line 175, in main
    root = parser.parse_string(code)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/pakettic/parser.py", line 294, in parse_string
    return chunk.parse_string(x, parse_all=True)[0]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/pyparsing/core.py", line 1141, in parse_string
    raise exc.with_traceback(None)
pyparsing.exceptions.ParseException: Expected end of text, found 'local'  (at char 0), (line:1, col:1)

This example is handled fine, even though only one of the vars is set:
local x,y,z = 0

Who uses locals ;) Sounds like a trivial thing to fix, but I don't have time to investigate until Dec 14. Do you need a fix asap?

Checking the changelogs, 1.3.0 has 0e47, you probably are on 1.2.0 or earlier. Can you try pip install pakettic --upgrade and see if this solves your issue?


upgrade to 3 channels when doing color conversions

When color correcting single channel images, oiio just color corrects them as (y, 0, 0), it's better to use (y, y, y). We also fix a couple of spots in maketx with the same issue.

LGTM, thanks!


Release 1.0.0

Version 1.0.0 🎉
Additions ➕

Add support for every endpoint and resource currently supported by the API itself
Every resource now includes a serialize method to serialize the resource into an object.
Add tests to the SDK to at least have 100% of coverage
Document the library's capabilities a bit better (user-facing documentation)

Breaking Changes ❌

Change the interface to interact with almost every resource. Refer to the documentation for more information.
Remove superfluous methods like showAccounts that don't fit inside the SDK paradigm.

Fixes 🐛

Fix date management issues that bugged the library

Codecov Report

:exclamation: No coverage uploaded for pull request base (stable@fc87504). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             stable       #4   +/-   ##
=========================================
  Coverage          ?   98.28%
=========================================
  Files             ?       23
  Lines             ?      409
  Branches          ?       50
=========================================
  Hits              ?      402
  Misses            ?        0
  Partials          ?        7

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fc87504...5d40b77. Read the comment docs.


refactor: place normal C# classes in Extism.Sdk namespace

Extism.Sdk.Native should only contain classes/structs/enums that are defined by the native runtime

There seems to be a lot of unrelated changes in this PR


Problems on incremental decoder

I'm not sure about the decoding process in the convolutional sequence to sequence learning. So the convolutional decoder just use ngram of the decoded sentence and attention weighted encoder output when doing incremental inference? why not use RNN as decoder(it can use the whole decoded sentence part)?

Convolutional decoders are typically much faster to train than RNN-based decoders.


[NDTensorscuTENSORExt] Temporary fix for block sparse contractions

Description
Quick fix by copying all the viewed blocks and rewriting the block back to fix cuTENSOR problem.
Checklist:

[x] BlockSparse cutensor contractions work.
[x] Check that the performance isn't too slow compared to cuBLAS implementation.
[x] Avoid copying when it isn't needed, for example when the offset field of the CuArray is 0 (https://github.com/JuliaGPU/CUDA.jl/blob/v5.4.2/src/array.jl#L61).

I think using a single function with if-statements would be better here:
arrayR = array(R)
is_R_zero_offset = iszero(arrayR.offset)
if is_R_zero_offset
  arrayR = copy(arrayR)
end
cuR = CuTensor(arrayR, collect(labelsR))

# ...

if is_R_zero_offset
  arrayR .= cuR.data
end

Then we can remove the if-statements once https://github.com/JuliaGPU/CUDA.jl/issues/2407 is fixed.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 43.65%. Comparing base (e08e131) to head (e4d590d).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1485   +/-   ##
=======================================
  Coverage   43.65%   43.65%
=======================================
  Files         136      136
  Lines        8806     8806
=======================================
  Hits         3844     3844
  Misses       4962     4962

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

Looks good, thanks. Is this ready to merge once tests pass?

Looks good, thanks. Is this ready to merge once tests pass?

Yes ready to merge when tests pass!

Glad to see the timings are comparable, I'll be curious to see what the timings are once we can remove the calls to copy. Pretty soon we'll have the entire table in https://itensor.github.io/ITensors.jl/dev/RunningOnGPUs.html#GPU-backends supported!
Have you tried profiling or timing (https://cuda.juliagpu.org/stable/development/profiling) to get an estimate of how much time the calls to copy are taking up?

Have you tried profiling or timing (https://cuda.juliagpu.org/stable/development/profiling) to get an estimate of how much time the calls to copy are taking up?
No I haven't yet don't any indepth timings of the function just a quick dmrg calculation to see if it was significantly effecting performance in a known case where GPU finds improvement over CPU.
I will run more and get back on timings/performance


minor: normalizeSchemaToIdWithVersion utility function

:tada: This PR is included in version 18.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Use LLVM 7.0 on SLES

Add option to find LLVM 7 package (version installed on our SLES builds).

Good for now. Not sure why cmake doesn't supported a version request list

Yea, spent a while searching for an alternative to the nested list of versions. The closest I found is cmake allows changing the sort order of found configs (natural asc des). But since we want any version between 6 and 9, there doesn't seem to be a tidier way to implement that with find_package.


docs(toh-4/ts): copyedits

Contributing to #1628.

LGTM.  I don't know about @Foxandxss question but if we messed up, we can fix it.

No, it would not mess anything up. I think that Jesus was commenting about a potentially unnecessary extra line (i.e., have two #enddocregion tags instead of one).


Run clean up command before exit

Would be great to have an option to run a command to do some cleanup. Example would be stopping a database docker container when you're done working.

Straw man alternative: just run it after concurrently:
concurrently foo bar; cleanup

Do you want some different semantics?

Thanks @cben! Don't know why I didn't think of that.


Documentation fix

Assuming this isn't a priority, but I'm still using this gem and thought I'd share that token and secret are incorrect in the docs, and instead it should be access_token and access_token_secret
In a separate YAML config file. Create a file named botname.yaml – the botname part must match your bot’s username EXACTLY. Put the following contents, pasting the credential values that you just generated:

  ---
  :consumer_secret: Consumer Secret (API Secret) GOES HERE
  :consumer_key: Consumer Key (API Key) GOES HERE
  :access_token: Access Token GOES HERE
  :access_token_secret: Access Token Secret GOES HERE
```

Thanks for that. If you want to submit a PR for that I'll be happy to merge
it in, otherwise I'll get to this as soon as I can
On Sat, May 21, 2022, 21:24 Ryan TG @.***> wrote:

Assuming this isn't a priority, but I'm still using this gem and thought
I'd share that token and secret are incorrect in the docs
http://muffinista.github.io/chatterbot/setup.html, and instead it
should be access_token and access_token_secret
In a separate YAML config file. Create a file named botname.yaml – the botname part must match your bot’s username EXACTLY. Put the following contents, pasting the credential values that you just generated:

:consumer_secret: Consumer Secret (API Secret) GOES HERE
:consumer_key: Consumer Key (API Key) GOES HERE
:access_token: Access Token GOES HERE
:access_token_secret: Access Token Secret GOES HERE

—
Reply to this email directly, view it on GitHub
<https://github.com/muffinista/chatterbot/issues/66>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAMAFC2ZSZFHBVQRBRZTRTVLGZIDANCNFSM5WSZFTIQ>
.
You are receiving this because you are subscribed to this thread.Message
ID<EMAIL_ADDRESS>

I’ll do a PR. I didn’t realize the docs were part of this repo.

Resolved by #67, thanks!


How to implement?

On first read, there are no instructions on how to implement the styling on AMP Start. How to implement this css for inputs, etc.?

@88kbbq - If you are using one or the ampstart templates you need to just copy paste the components from ampstart.com/components -https://ampstart.com/getstarted - Does this help? (Feel free to re-open if you need more help or ping me on our slack channel)


Fix syntax error in Windows packaging script

PR Summary
Fixes a parse error in the Windows packaging automation caused by https://github.com/PowerShell/PowerShell/pull/14090.
PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@PoshChan please remind me 2 hours

@rjmholt, I do not understand: please remind me 2 hours

Commands available in this repo for you:

retry <target> this will attempt to retry only the failed jobs for the target pipeline, restart can be used in place of retry

rebuild <target> this will perform a complete rebuild of the target pipeline, rerun can be used in place of rebuild Supported values for <target> which can be a comma separated list are: static,windows,macos,linux,ssh,all

get failures this will attempt to get the latest failures for all of the target pipelines

remind me in <value> <units> this will create a reminder that will be posted after the specified duration <value> is a number, and <units> can be minutes, hours, or days (singular or plural)

@PoshChan please remind me in 2 hours

@rjmholt, this is the reminder you requested 2 hours ago


File extensions not triggering default flags in import

According to mmdbctl import help the file extensions should trigger the default flag
    -t, --tsv
      interpret input file as TSV.
      by default, the .tsv extension will turn this on.

but it's giving error if we don't specify the flag explicitly
$ mmdbctl import abc.csv
err: input file type unknown

Giving error on json and csv as well

This is because the input is not given via arguments, it's given via the -i or --input flag.


fix cli bug

This PR fixes the bug described in #36, with the CLI remaining the same per reviewer suggestion.
closes #36

@brews thanks for the suggestion in #36, that worked. Ready for another review.


Add Client Policies to Signed Packages ref doc

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/reference/Signed-Packages-Reference.md
:warning:Warning
View
Details

docs/reference/Signed-Packages-Reference.md

Line 181: [Warning] Invalid file link:(~/reference/tools/cli-ref-trusted-signers.md#nuget-trusted-signers-sync--name-).
Line 185: [Warning] Invalid file link:(~/reference/reference/nuget-config-file#trustedsigners-section).

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.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/Signed-Packages-Reference.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.

@karann-msft this PR should be merged before the upcoming blogpost

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/Sign-a-Package.md
:white_check_mark:Succeeded
View

docs/reference/Signed-Packages-Reference.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.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/Sign-a-Package.md
:white_check_mark:Succeeded
View

docs/reference/Signed-Packages-Reference.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.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/Sign-a-Package.md
:white_check_mark:Succeeded
View

docs/reference/Signed-Packages-Reference.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.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/Sign-a-Package.md
:white_check_mark:Succeeded
View

docs/reference/Signed-Packages-Reference.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.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/Sign-a-Package.md
:white_check_mark:Succeeded
View

docs/reference/Signed-Packages-Reference.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.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/create-packages/Sign-a-Package.md
:white_check_mark:Succeeded
View

docs/reference/Signed-Packages-Reference.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.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/consume-packages/installing-signed-packages.md
:white_check_mark:Succeeded
View

docs/create-packages/Sign-a-Package.md
:white_check_mark:Succeeded
View

docs/reference/Signed-Packages-Reference.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.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Publishing of document 'docs/wxpu5wap.lso.json' failed at SafeOpenReadStream with relative path: nuget/wxpu5wap.lso.json. Error: Could not find file 'W:\bbz1-s\docs\wxpu5wap.lso.json'.
[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

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.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Publishing of document 'docs/kkz3nxhm.hmk.json' failed at SafeOpenReadStream with relative path: nuget/kkz3nxhm.hmk.json. Error: Could not find file 'W:\nbqw-s\docs\kkz3nxhm.hmk.json'.
[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

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.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.md
:white_check_mark:Succeeded
View

docs/consume-packages/installing-signed-packages.md
:white_check_mark:Succeeded
View

docs/create-packages/Sign-a-Package.md
:white_check_mark:Succeeded
View

docs/reference/Signed-Packages-Reference.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.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Publishing of document 'docs/dfz4pfgv.r4y.json' failed at SafeOpenReadStream with relative path: nuget/dfz4pfgv.r4y.json. Error: Could not find file 'W:\yhxm-s\docs\dfz4pfgv.r4y.json'.
[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

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.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Publishing of document 'docs/ltavrvee.wk2.json' failed at SafeOpenReadStream with relative path: nuget/ltavrvee.wk2.json. Error: Could not find file 'W:\0tgd-s\docs\ltavrvee.wk2.json'.
[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

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.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Publishing of document 'docs/jmlvezj4.t0v.json' failed at SafeOpenReadStream with relative path: nuget/jmlvezj4.t0v.json. Error: Could not find file 'W:\zatf-s\docs\jmlvezj4.t0v.json'.
[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

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.

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/create-packages/Sign-a-Package.md
:warning:Warning
View
Details

docs/TOC.md
:white_check_mark:Succeeded
View

docs/consume-packages/installing-signed-packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/ways-to-install-a-package.md
:white_check_mark:Succeeded
View

docs/reference/Signed-Packages-Reference.md
:white_check_mark:Succeeded
View

docs/create-packages/Sign-a-Package.md

Line 98: [Warning] Invalid file link:(~/create-packages/installing-signed-packages.md).

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.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

docs/create-packages/Sign-a-Package.md
:warning:Warning

Details

[Error] Publishing of document 'docs/22lujhfg.wqd.json' failed at SafeOpenReadStream with relative path: nuget/22lujhfg.wqd.json. Error: Could not find file 'W:\lq53-s\docs\22lujhfg.wqd.json'.
[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

docs/create-packages/Sign-a-Package.md

Line 98: [Warning] Invalid file link:(~/create-packages/installing-signed-packages.md).

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.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

docs/create-packages/Sign-a-Package.md
:warning:Warning

Details

docs/reference/Signed-Packages-Reference.md
:warning:Warning

Details

[Error] Publishing of document 'docs/fd3fcofv.odw.json' failed at SafeOpenReadStream with relative path: nuget/fd3fcofv.odw.json. Error: Could not find file 'W:\s1me-s\docs\fd3fcofv.odw.json'.
[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

docs/create-packages/Sign-a-Package.md

Line 98: [Warning] Invalid file link:(~/create-packages/installing-signed-packages.md).

docs/reference/Signed-Packages-Reference.md

Line 55: [Warning] Invalid file link:(~/reference/installing-signed-packages.md).

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.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

docs/reference/Signed-Packages-Reference.md
:warning:Warning

Details

[Error] Publishing of document 'docs/jcgmhiov.xeo.json' failed at SafeOpenReadStream with relative path: nuget/jcgmhiov.xeo.json. Error: Could not find file 'W:\0hyh-s\docs\jcgmhiov.xeo.json'.
[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

docs/reference/Signed-Packages-Reference.md

Line 55: [Warning] Invalid file link:(~/reference/installing-signed-packages.md).

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.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

docs/reference/Signed-Packages-Reference.md
:warning:Warning

Details

[Error] Publishing of document 'docs/5dhdypf0.jmi.json' failed at SafeOpenReadStream with relative path: nuget/5dhdypf0.jmi.json. Error: Could not find file 'W:\gtec-s\docs\5dhdypf0.jmi.json'.
[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

docs/reference/Signed-Packages-Reference.md

Line 55: [Warning] Invalid file link:(~/reference/installing-signed-packages.md).

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.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/TOC.md
:white_check_mark:Succeeded
View

docs/consume-packages/installing-signed-packages.md
:white_check_mark:Succeeded
View

docs/consume-packages/ways-to-install-a-package.md
:white_check_mark:Succeeded
View

docs/create-packages/Sign-a-Package.md
:white_check_mark:Succeeded
View

docs/reference/Signed-Packages-Reference.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.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

docs/consume-packages/installing-signed-packages.md
:warning:Warning

Details

[Error] Publishing of document 'docs/mi5f0rrn.j5b.json' failed at SafeOpenReadStream with relative path: nuget/mi5f0rrn.j5b.json. Error: Could not find file 'W:\v1ba-s\docs\mi5f0rrn.j5b.json'.
[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

docs/consume-packages/installing-signed-packages.md

Line 22: [Warning] Invalid file link:(~/tools/cli-ref-config).
Line 22: [Warning] Invalid file link:(~/reference/nuget-config-file).
Line 38: [Warning] Invalid file link:(~/consume-packages/..tools/cli-ref-trusted-signers).

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.


Joe/update GitHub workflows

(Reopen from forked pull request from earlier)
Updates included:

Parameterizing the Dockerfiles found within.
Fixing minor bug in validate-docker-images.sh.
Adding secrets to the repo for where we reference our images.

Note on item # 3: Secrets should work for regular pull requests however they will not be passed to runners if the pull request comes from a forked pull request. To mitigate this, we can review any incoming PRs to be sure the code does nothing unexpected. Then reopen a pull request (not from the fork) to run any required checks.
Please let me know if there are any questions or concerns.

@karianna @brunoborges This is ready for another once over. Should include support for Mainer 1.0 and 2.0. With 1.0 having the cm-1 tag. Let me know if there are any issues please and thanks!


[GJ] Translation to Gujarati - Ch1 Page1-2

Issue: #284
Added chapter1 page1 and page2
Reviewer: @lewtun

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Adding @mishig25 for review and merge


fix: static page generation includes nonces

Version
nuxt-security: 1.0.0-rc.4
nuxt: 3.8.1
Reproduction Link
https://stackblitz.com/edit/github-ljxjtg-r2tm2f?file=app.vue
Steps to reproduce
The docs specify:

The nonce option and the "'nonce-{{nonce}}'" placeholders are ignored when you build your app for SSG via nuxi generate.

What is Expected?
No sha256-... to be under script-src of a generated page (those should be nonces, right?).
What is actually happening?
The head's meta contains <meta http-equiv="Content-Security-Policy" content="base-uri 'none'; font-src ; form-action 'none'; img-src ; object-src ; style-src 'self'; script-src  'sha256-x80VopB6Gfm0Y/Q1F8zIYGL4MRRmUNoKz72T7lRGiiA=' 'sha256-ChValuzd0cyaDyQRGsHBMsFX2hzljF1GK3M80fFrnAk='; child-src ; connect-src 'self'; default-src 'none'; frame-src ; media-src ; navigate-to ; report-to ; worker-src "> which includes two nonces.

@vejja
Is this a bug? Isnt it actually a correct behavior of subresource integrity?

It is the correct behaviour - no bug here
@dargmuesli what you are seeing are not nonces but hashes, which is normal behaviour with SSG
In SSG mode the hash method is used instead of the nonce method (it is not possible to use nonces in SSG)
In addition, the doc says that whatever you set for the nonce option and the nonce placeholders will be ignored.
For the sake of completeness, this is independent of subresource integrity. What you are seeing here are the hashes of your inline scripts, whereas subresource integrity deals with the hashes of external scripts

Thank you for the clarification!

Thanks for the clarification @vejja . Glad to have such an expert here! 💚


CustomTabIntent Closed On App In Background

Android When CustomTabIntent Open For Entering The OTP Code , If I Send App To The Background The Custom Tab Closed And Return With Cancelled Status .

Could you please provide the details of the device that you tested on:

Emulator or real?
What's the Android version?


Update llama2-model.libsonnet

Description
Please include a summary of relevant context/issue and your changes.
Tests
Please describe the tests that you ran on Cloud VM to verify changes.
Instruction and/or command lines to reproduce your tests: ...
List links for your tests (use go/shortn-gen for any internal link): ...
Checklist
Before submitting this PR, please make sure (put X in square brackets):

[x] I have performed a self-review of my code.
[x] I have necessary comments in my code, particularly in hard-to-understand areas.
[x] I have run one-shot tests and provided workload links above if applicable.
[x] I have made or will make corresponding changes to the doc if needed.

LGTM!
Also we need to merge https://github.com/GoogleCloudPlatform/ml-auto-solutions/pull/434 first, or the v5p capacity won't be accessible.

Do you want to add v5p tests in this PR? If so, we need to update https://github.com/GoogleCloudPlatform/ml-auto-solutions/blob/master/dags/pytorch_xla/r2_5.py as well.

Yes, we need to add something like below to r2_5.py for v5p test:
US_EAST5_A_TPU_PROD_ENV_AUTOMATED = gcp_config.GCPConfig(
    Project.TPU_PROD_ENV_AUTOMATED.value,
    Zone.US_EAST5_A.value,
    metric_config.DatasetOption.XLML_DATASET,
)
...

llama_3_train_v5p_8 = task.run_queued_resource_test(
      test_config.JSonnetTpuVmTest.from_pytorch(
          test_name="pt-2-5-llama3-train-func-v5p-8-1vm",
          reserved=True,
          network=V5_NETWORKS,
          subnetwork=V5P_SUBNETWORKS,
      ),
      US_EAST5_A_TPU_PROD_ENV_AUTOMATED,
  )
...

The exact test_name can be see after you run bash scripts/gen-configs.sh

cc @tengyifei, would you mind help to review this PR?


3D model instability

Hi Kuangdai,
I hope you are well. I have three 3D models which keep producing instabilities when trying to run. They generally start to blow up ~ 30-50 % of the way through the simulation. I have attempted lowering the Courant number, as well as altering the dominant frequency of the mesh from 2 Hz to 2.1 Hz and 2.3141592 Hz in the hope that this would offset any sharp velocity boundaries from the boundaries of the mesh elements. Unfortunately neither of these worked. Finally, I previously attempted tapering the edges of the perturbed regions so that the boundaries were not as sharp, but this also did not solve the issue. I was wondering whether you had any suggestions for alterations to the mesh/model/inparam files that may make these simulations stable.
I attach below a zip file containing the input files and 3D models.
inputs.zip
It is worth noting that similar 3D models (eg. with spheres of radius 1.5 and separation 3, instead of radius 1 and separation 2) run fine.
Any advice on this would be amazing!
Best wishes,
Will

Can you try halve the courant number? If it is not working, try to decrease the perturbation from 20% to 5%. In the file, I only see 20% and 0. If you have done boundary smoothening, there should be other values between 20% and 0.

The Courant number is already at 0.15, but i'll give it a go! Yes, these models didnt have smoothing but having run other simulations that had instabilities, the smoothing didnt make any difference. I will try re-running again with smoothing and with a courant of 0.075.

You can try a bigger Nr as well.  360 may be too sparse so it caused overshooting in the azimuthal dimension.

Hi Kuangdai,
Just to update you. I tried re-running with nr of 800 instead of 360 and instability still grows early on ~ 40 % of the way through simulation.

This input is too large for local inspection. Can you reproduce the error with a smaller mesh and Nr so that it can be run on one processor. I cannot debug under MPI, which will take ages.

Sorry for the slow reply. I tried to re-install axisem locally (new computer) to run these smaller simulations but I'm getting an issue with the compiler when I try to make axisem (command line output is attached in a text file - I think its an issue with finding mpicxx but Im not very confident on this stuff).
I have attached a zip with the following files:

Normal inparam files I use
Install issue command line output + copy of build directory containing CMake logs etc. (if you want to take a look but no worries I know youre super busy!)
Smaller homo2Hz.e mesh (15 km radius instead of 125 km)
Smaller corresponding 3D model, called model.nc, as well as the model-generating script (variables in the bottom ~ 10 lines can be changed to produce different models/change resolution etc)
Currently nr is set to 5 instead of 360
loop_info_interval is set to 10 as I was aiming to check how long it would take on one processor.

I cant run it locally and produce the error until I can sort out the axisem install - If you are able to run it on your end that would be amazing. I anticipate (hope) it will blow up as usual, but cant be sure until its run.
In the mean time I will try and get axisem downloaded (sorry!)
mini_domain.zip

Hi Kuangdai, I just ran the aforementioned smaller simulation on archer to circumvent the installation issues. Seems to run fine in this case. I guess there must be some issue when increasing the nr/size of the simulation? I'll try running some slightly larger ones to pinpoint when it blows up

Further update - I ran with this same smaller model with nr = 100. Took ~ 8 minutes on one node on archer so hopefully managable on your local station if required. Record sections of Greens functions and 2 Hz BP Greens functions (below) show instability growing. Note that the amplitude of each trace is normalised hence why, because of the growing instability at the earlier stations, you cant see the first ~ 200 seconds of the GF for the first few stations.
Attached below are the logs from the develop section of the output. Please let me know if you require any other files. Thanks again for all your help so far!
loop_timers.log
measured_element_costs.log
preloop_diagnosis.log

The uploaded mini_domain.zip contains something incorrect. Without changing anything, it will stop with an error of wrong source depth. After using a correct source depth, it will cost 25 hours on my Mac with nr=100. It is impossible that one node on Archer (or any HPC on Earth) can be 25*60/8 times faster than an i7 CPU on Mac. Please verify.

Yes, sorry I forgot to change the source depth. Possibly worth clarifying that each node on archer2 has 128 cores where as I assume the Mac has ~ 4-8? Do you need it to run on a single core for debugging? I will try and find the minimum nr at which I observe an instability.

Have run simulations at the following nr values:

20
25
30
35
50
100

Using nr = 25 the simulation doesnt blow up, but it does for nr = 30. Hopefully nr=30 should be managable on Mac? I also note that currently the courant number is set to 0.25 for all of these simulations so I guess that could be increased to shorten run times?

Hi Kuangdai - I was just wondering whether there was any update on this?

I am afraid not. Does it run with 20% perturbation instead of 40%?

Sorry for the slow reply - I can't get access to my linux system at the moment so can't check this but the perturbations should be 20 %. It may show as 40 % in paraview because the spheres almost overlap, but I believe the max. value of the arrays in the netcdf file should be 20 % (I hope!)). My deadline for this project is coming up in the next week or so, so I think I will just have to do without these simulations. Thanks for your help in trying to solve the issue, I really appreciate you taking the time.

Are you sure about 20%? I have been testing this using the attached model file. The perturbation is -20% or 0% on most of the points but with some "isolated" points with -40% perturbation at the corners. Not sure how you get this model, but I assume this is what you want. These isolated points tend to cause overshooting by SEM.

[model.nc.zip](https://github.com/kuangdai/AxiSEM-3D/files/6324634/model.nc.zip)

Hmm...I think I know what the issue will be in the model-generating script. I will have a look at that asap and check - it should be very easy to rectify and then i'll try re-running the simulations! Thanks!


update: change encodeUri to encodeUriComponent

Replaced encodeUri with encodeUriComponent to add better support for characters.

Adding @jazibsawar to review.


Fix bugs with collapsed series data on updating options/series

Fixes multiple bugs with calling updateOptions when one or more series are hidden:

Y-Axis was not sized appropriately to visible series
Un-hiding series did not show full data set

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

@junedchhipa Is there anything I can add to get this merged?


WIP: Initial support for preprocessing plotting data

The idea is to allow certain preprocessing operations to be performed before creating a solution plot. Initially, we have support for plotting everything on a uniform mesh of a fixed refinement level. This is based on an idea by @gregorgassner. Comments & suggestions welcome!
Run simulation and plot solution as it is
julia> trixi_include("examples/2d/elixir_advection_amr.jl")

julia> pd = PlotData2D(sol)

julia> plot(pd, seriescolor=:heat)

julia> plot!(getmesh(pd))

Run simulation and plot at coarser refinement level (level = 4)
julia> trixi_include("examples/2d/elixir_advection_amr.jl")

julia> pd = PlotData2D(adapt_to_mesh_level(sol, 4)...)

julia> plot(pd, seriescolor=:heat)

julia> plot!(getmesh(pd))

Run simulation and plot at coarser refinement level (level = 6)
julia> trixi_include("examples/2d/elixir_advection_amr.jl")

julia> pd = PlotData2D(adapt_to_mesh_level(sol, 6)...)

julia> plot(pd, seriescolor=:heat)

julia> plot!(getmesh(pd))

There are now both a modifying version adapt_to_mesh_level!, which works on the given solution and semi, and a non-modifying version adapt_to_mesh_level available. The latter creates a deepcopy of the mesh and u_ode and remakes the semi with the mesh copy.

For documentation:
julia> trixi_include("examples/2d/elixir_euler_blast_wave_amr.jl", tspan=(0.0, 2.0))

julia> pd = PlotData2D(adapt_to_mesh_level(sol, 4)...)

julia> plot(pd["rho"], seriescolor=:heat)

julia> plot!(getmesh(pd))

Larger:

Smaller:


Image not in datasource if field required

The image will only be in the datasource if the field is fully optional. As soon as all or 1 language is required, the field will not be in the datasource

Fixed in 2.0.1


iOS: When app is killed in background, story and position don’t return

When I just logged the last bug, after returning to NewsBlur a minute later, it was killed and the wrong story was loaded. I want this feature to work flawlessly, so let’s spend a month or two tracking down the issue.
I’m on an iPad with a Smart Keyboard and in landscape orientation. I suspect the story pager recorded the wrong story for whatever reason, since I would expect the All Site Stories list to load without finding the original story, now that its state is read. Instead it found a different story. (...) It looks like it was just the first story.

Since we know we’re in looking for story mode, how about loading in All Stories unread_filter instead of the folder/feed’s preference.

That's a tricky one to investigate. What is supposed to happen, and does happen in my testing, is that when the app goes in the background, the current story is temporarily marked as unread, and the feed and story IDs are saved in the state restoration info.
If the app gets killed by the system (not force quit by the user), the state restoration mechanism will kick in, re-displaying that same feed and story, and re-marking it as read.  That all works fine in my testing now.
As I recall, if the story can't be found (e.g. because it's been a while), it might select the first story in the feed, as better than nothing.
If the app is force quit, or crashes, the state is not restored.
The state restoration logic is fairly complex, so I could imagine that it could fail in some situations, but I might need more info on how to reproduce an issue. I'll continue to test it and see if I can get it to fail.


Be able to fetch inbound_hash value from email.to property

It might be helpful for cases when Postmark's Inbound Domain Forwarding has been configured and something meaningful precedes inbound domain name. For example, I use it for defining publication level and messages from inbound email<EMAIL_ADDRESS>go private.

Hey, thanks for the PR! I'm a little hesitant to pull this in because I think it's something that should be done at the application layer since it's kind of interpreting the data that comes from Postmark. This gem just kind of maps the fields.
I've been recommending people use
https://github.com/thoughtbot/griddler
https://github.com/r38y/griddler-postmark

Hey Randy! Thanks for recommendations – I haven't noticed ABANDONWARE warning in the README file )

It's not quite abandonware, we're still heavily dependent on it at my current company and if we see something that needs to change and fits what this gem does (basically maps fields), we add or fix it. But I'm also migrating us away from it right now.
That being said, this gem is really just mapping json to prettier method names and I'm not sure this diff fits in with that.


Introducing comments to the CV entries

To better understand the interpretation of the CV entries, or rather the values in the mzQC file itself, I would like to introduce comments to the obo files.
This will be in the next pull request (containing the entries from issue #52 ) and needs to be done for all metrics. Help is very welcome for this.

:+1:
So I guess this will be a thing of ongoing refinement: so should we suggest comments/changes in the respective original cv issue, new issue, PR or elsewhere?
Interesting though is to have an open thread for each cv term. Worry with this is it might get too long and confusing.

wiki might be another place, but it's bad for discussions.

This might actually help us some

present our terms as clear as possible for a #141 PR
our terms being mixed in with general MS terms, PEFF terms, etc. (after #141) it will help avoid misinterpretation in the future even more

gets a priority :+1: from me

As discussed recently, we don't want to overdo it and introduce unnecessary comments. However, we do want to include comments when they can help to clarify how to interpret metrics.
The first batch of terms proposed for inclusion into the PSI-MS-CV illustrates this perfectly. Although this remains an ongoing point of attention as we merge more terms into the PSI-MS-CV, I'll close this issue for now.


Disabling browsersync

We need a way to prevent two browsers from being synchronized while developing.   We are building software that synchronizes youtube videos on playback between different browsers.  The issue is that browsersync gets in the way when we load the video.
We have two browsers pointed to the same url.  One browser loads a youtube video and then our code tells the other browser to load the same video.  All user interactions are synchronized.  So it is important that browsersync does not change the url in other browsers while developing this part of our software.
Thanks!

@friksa - So what exactly are you looking for here? Completely disabling browser-sync or just keeping a single browser in sync? The solution depends entirely on your exact requirement.

Keeping a single browser in sync would be ideal so that development changes are reflected in the browser... maybe using live reload instead of browsersync since it requires a browser plugin??

@friksa - iirc you can just disable "ghost mode" to stop the multiple browser functionality.

Thanks so much!! That works perfectly.  Just in case others have the same question, this is how it is set up.
Edit tools/config/project.config.ts and add this to the constructor
this.BROWSER_SYNC_CONFIG.ghostMode  = false;


PAB Wallet Emulator: make wallet number more consistent

I feel like this is not the correct fix, but without it there's a bug in the wallet config of PAB.
In that if we select the Wallet 1:
walletServerConfig:
  baseUrl: http://localhost:9081
  wallet:
    getWallet: 1

We end up using Wallet 10.
With
walletServerConfig:
  baseUrl: http://localhost:9081
  wallet:
    getWallet: 2

We end up using Wallet 1, etc.
Does anyone know the best fix for this issue? I'm ready to dig deeper with some guidance. Or without one next week.

Pre-submit checklist:

Branch

[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[ ] Reviewer requested

If you updated any cabal files or added Haskell packages:

[ ] nix-shell shell.nix --run updateMaterialized to update the materialized Nix files
[ ] Update hie-*.yaml files if needed

If you changed any Haskell files:

[x] nix-shell shell.nix --run fix-stylish-haskell to fix any formatting issues

If you changed any Purescript files:

[ ] nix-shell shell.nix --run fix-purty to fix any formatting issues

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

We end up using Wallet 10.

What does this mean in practice? As far as I know, walletPrivKey is the only place where we index into the list of private keys directly. So I don't think it is necessary that Wallet 1 gets the first key from knownPrivateKeys.

The issue is happening on the PAB Client. For example with the current config where we should act with Wallet 1, when we pay to Wallet 2.

We'd get an Insufficient Funds error:

Even though we should have 1 million ADA.
Now when we use the prism-mirror contract:

It suggests that we're acting with Wallet 10!

Similarly if we change the config to getWallet: 2 we'd end up acting as Wallet 1.
I thought fixing this in the client makes more sense but didn't have enough time to investigate so ended up moving on with this temporary fix. I also saw the privateKey values being counted from 1 in the source code so maybe this fix makes sense after all. And yeah, I'm not familiar enough to know all the affected places yet...

Ok that makes sense, thanks for the info. Yeah I'm not sure where the mismatch comes from, walletPrivKey should be the only place where we convert wallets to keys.
I'm happy to accept your fix also, looks like the test failure is just from the hashes changing, which is expected (to repair that, delete all the .txt files from plutus-use-cases/spec and run the tests again)

Thank you for the guidance, @j-mueller! I've updated the hashes and all checks have passed now.

@j-mueller I've rebased to fix the conflicts.

Great. Thank you!


update gribi tests to use become leader

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 73.151%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1602

Relevant Lines:
2190

💛  - Coveralls


[WIP] Add flake8 and vim configs

[x] Add flake8 config file
[ ] Test it
[ ] Add a flake8 check to travis
[ ] Fix all current flake8 errors

If we add a .flake8 file, shouldn't we also add --flake8 to addopts in pytest.ini?

That would be a possibility. I usually have a flake8 check as a separate step in CI, so that CI can fail early if there are flake8 problems. But I never used py.test with --flake, maybe I should take a look at that.

After a quick look at https://pypi.python.org/pypi/pytest-flake8, I wonder what the benefit of this plugin over just running flake8 directly is.

@rfleschenberg can we close this?

It's ok if you close it, but I'd prefer to keep it open, but as a low-priority, "maybe if I have time" kind of thing :)

About .vimrc:
I'm not very favorable adding IDE/Editor specific stuff to the repository. Each IDE has their own config files and adding all of them can create a mess.
There is one exception to this: .editorconfig which is understood by all major IDEs.

I'd prefer to read these from .editorconfig, unfortunately that's not supported with my current setup. I should probably modernize my Vim setup. Time constraints :(


Wrong id in inheritedFrom section

When generating from d.ts file the resulting part of json file is
"id": 160728,
"name": "ASPxClientGaugeControl",
"kind": 128,
"kindString": "Class",
"flags": {
	"isExported": true
},
"children": [
	{
		"id": 160760,
		"name": "Init",
		"kind": 1024,
		"kindString": "Property",
		...
		"inheritedFrom": {
			"type": "reference",
			"id": 160760,
			"name": "ASPxClientControlBase.Init"
		}
	},
	...
]

[x] I have checked issues with bug label and found no duplicates

Expected Behavior
The "id" value in inheritedFrom section should be as the id of "Init" property of the ASPxClientControlBase class.
Actual Behavior
The "id" value in inheritedFrom section is the id of "Init" property of the ASPxClientGaugeControl class (the inherited member itself).
Steps to reproduce the bug
typedoc --json tsDoc.json --ignoreCompilerErrors --includeDeclarations --excludePrivate --target ES5 d:\Temp

Environment

Typedoc version: 0.16.11
Node.js version: 12.13.1
OS: Windows 10

The whole system surrounding TypeDoc's reference types really needs to be redone...
We currently frequently try to guess what a reference is referring to given nothing but its name. While this might have worked decently well in pre-module TypeScript.... it is a horrible idea now.
I spent a few hours looking into this yesterday and partially fixed it, but ran into several other blockers that will need some more hours to figure out. I should be able to look more deeply into it this weekend.

I'm not familiar with the generated JSON here, but I think I'm seeing the same issue. I have a class hierarchy that looks like this:

Most of those classes inherit a number of methods from Property, but the generated documentation shows it all as inherited from Node, which is a final class not extended by anything. For example, here's the documentation for getName() on the Node class, which claims to be inherited from itself:

Is this the same bug, or have I misunderstood the description?

We are also running into the same issue. Sometimes the inherited from references its own class, sometimes a sibling class, and sometimes the actual base class.

That sounds like the same bug, it sounds like we have a check inverted somewhere for which node to add the inherited from property to.

I spent a few hours looking into this yesterday and partially fixed it, but ran into several other blockers that will need some more hours to figure out. I should be able to look more deeply into it this weekend.

This never happened... GitHub's old notification system didn't save the notification and it dropped off my radar. PR welcome if someone wants to take a look at fixing this. I need to try to get library mode finished first.

@Gerrit0 is this a duplicate of https://github.com/TypeStrong/typedoc/issues/1209?

It might be, all of TypeDoc's logic regarding reference resolving is sketchy at best. I'll keep both open for now.


App crashes (on iOS) when try to detect face

error log:
2022-11-11 19:06:21.489 Runner[16926/0x103738580] [lvl=3] +[MLKITx_CCTClearcutUploader crashIfNecessary] Multiple instances of CCTClearcutUploader were instantiated. Multiple uploaders function correctly but have an adverse affect on battery performance due to lock contention.
Initialized TensorFlow Lite runtime.
INFO: Initialized TensorFlow Lite runtime.
2022-11-11 19:06:21.510 Runner[16926/0x103738580] [lvl=3] +[MLKITx_CCTClearcutUploader crashIfNecessary] Multiple instances of CCTClearcutUploader were instantiated. Multiple uploaders function correctly but have an adverse affect on battery performance due to lock contention.
* thread #3, queue = 'ProviderImageSurfaceCacheQueue', stop reason = EXC_BAD_ACCESS (code=1, address=0x1350dc000)
    frame #0: 0x00000001db9238e4 libsystem_platform.dylib`_platform_memmove + 196
libsystem_platform.dylib`_platform_memmove:
->  0x1db9238e4 <+196>: ldnp   x10, x11, [x1, #0x10]
    0x1db9238e8 <+200>: add    x1, x1, #0x20
    0x1db9238ec <+204>: sub    x2, x2, x5
    0x1db9238f0 <+208>: stp    x12, x13, [x0]
Target 0: (Runner) stopped.
Lost connection to device.

flutter doctor:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.3.3, on macOS 12.2 21D49 darwin-arm, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] VS Code (version 1.73.1)
[✓] Connected device (4 available)
[✓] HTTP Host Availability

• No issues found!

google ml kit version :
google_mlkit_face_detection: ^0.5.0

Facing same issue. @TalebRafiepour Any workaround?

Facing same issue. @TalebRafiepour Any workaround?

Not yet :((

Hey @TalebRafiepour, This issue is related to a limitation.
As per the documentation, ML Kit (iOS SDK) does not support 32-bit architectures (i386 and armv7) and  64-bit architectures (x86_64 and arm64).
Reference: https://developers.google.com/ml-kit/migration/ios
@TalebRafiepour  Please go though the doc
Thanks.

Hey @TalebRafiepour, This issue is related to a limitation.
As per the documentation, ML Kit (iOS SDK) does not support 32-bit architectures (i386 and armv7) and 64-bit architectures (x86_64 and arm64). Reference: https://developers.google.com/ml-kit/migration/ios
@TalebRafiepour Please go though the doc Thanks.

Thanks for you help

As per the documentation, ML Kit (iOS SDK) does not support 32-bit architectures (i386 and armv7) and 64-bit architectures (x86_64 and arm64). Reference: https://developers.google.com/ml-kit/migration/ios

Perhaps this was just a typo, but note that the linked documentation notes that it does support 64-bit architectures: "ML Kit does support 64-bit architectures (x86_64 and arm64).".

ML Kit does not support 32-bit architectures (i386 and armv7). ML Kit does support 64-bit architectures (x86_64 and arm64).
Refer to our updated README.

i am having the same issue i folowed the docs and still having the same error if you fixed it pls tel me how


Raids Special Loot

Describe the bug
COX final interface is all de-colored to default text color.
To Reproduce

Get a rare drop in your name.
Drop is not highlighted
Infinite rage.

Expected behavior
Red color text for special rare loot. Purple color text for other important stuff.
Screenshots
How it looks without bug

How it looks with bug

Environment (please complete the following information):

OS: Windows 10
RuneLite version: 1.5.27
Launcher version: Latest..?

Could you provide a screenshot of your Chat Notifications configuration please?

Highlight words strips colour before highlighting, and since you have your name in there (Frir), it killed all the colour from the unique. You don't actually need your name in the highlight list, as Highlight own name will do that automatically.

lets hope that was the problem, thanks.


Add model Dockerfile and update toronto yaml

Hi Michael Z,
Can we push modifications to the model.yamls on this branch? How do you want to manage this?

(@bnaul @alexeisw)

Ah, hi @stevededalus! Yeah, I think you're right, let's continue this on your fork. Gets rather deployment-specific.


Structure of aln.cpp

This shows which functions call which other functions in aln.cpp. This is an updated version of #98.
I’m documenting this because I think some functions should be renamed to make it easier to remember what function does what. I will update this over time.
Paired end
graph LR;
    align_PE_read --> shuffle_top_nams;
    align_PE_read --> output_hits_paf_PE;
    align_PE_read --> align_PE;
    align_PE_read --> get_best_map_location;

    align_PE --> is_proper_nam_pair;
    align_PE --> rescue_read;
    align_PE --> extend_seed;
    align_PE --> get_best_scoring_nam_pairs;
    align_PE --> joint_mapq_from_high_scores;
    align_PE --> is_proper_pair;
    align_PE --> get_mapq;
    align_PE --> top_dropoff;

    extend_seed --> hamming_distance;
    extend_seed --> hamming_align;
    extend_seed --> Aligner.align;
    get_best_scoring_nam_pairs --> is_proper_nam_pair;
    rescue_mate --> has_shared_substring;
    rescue_mate --> Aligner.align;
    rescue_read --> extend_seed;
    rescue_read --> rescue_mate;
    rescue_read --> get_best_scoring_pairs;
    rescue_read --> joint_mapq_from_alignment_scores;
    rescue_read --> is_proper_pair;
    joint_mapq_from_high_scores --> joint_mapq_from_alignment_scores;
    get_best_map_location --> get_best_scoring_nam_pairs;

Single end
graph LR;
    align_SE --> reverse_nam_if_needed;
    align_SE --> extend_seed;
    extend_seed --> hamming_distance;
    extend_seed --> hamming_align;
    extend_seed --> Aligner.align;
    align_SE_read --> shuffle_top_nams;
    align_SE_read --> align_SE;
    align_SE_read --> output_hits_paf;

Good idea! Functions like get_best_scoring_nam_pairs are probably better represented by a name like score_nam_pairs.


uses_from_macos: allow ed

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Follow up PR in core: https://github.com/Homebrew/homebrew-core/pull/56365

Thanks @iMichka!


Use encoding="utf-8" in open.

Description
Use parameter encoding="utf-8"in open function.
Motivation and Context
#772
Pass the install script in Windows Big 5 OS.
How Has This Been Tested?

[x] Pass the test by running: python setup.py install under upper directory of qlib.
[ ] If you are adding a new feature, test on your own test scripts.

Screenshots of Test Results (if appropriate):

Pipeline test:
Your own tests:

Types of changes

[x] Fix bugs
[ ] Add new feature
[ ] Update documentation

It looks great!  Thanks so much!


Your program is excellent.

Can you make program for Instagram IGTV video views, reel view? I know you can it would be great if you do so. Consider adding Paytm number so that people from India too can sponsor you.

I'm sorry I don't know anything about instagram IGTV or reel video. Also I can't create a paytm account from my country. But you can support by PayPal, payoneer or cryptocurrency. Thanks


Place topic drawer on same level as workspace

Is your feature request related to a problem? Please describe.
Right now, the topic drawer is in front of the workspace, so closing it does not affect the space that the workspace takes up. This was ok when react flow was the only thing in the workspace because it's easy to move around that flow, but this is painful for the criteria table, because the table always appears behind the drawer.

Describe the solution you'd like
Move the topic drawer to the same level as the workspace, so that the drawer takes space from the workspace when the drawer is expanded.
Describe alternatives you've considered
Additional context
Technical ideas
Drawer's position probably needs to be changed
This Material UI example is taking up space, might be useful to look at (though we don't want the drawer to push the header - it should remain below the header so the header shouldn't be in the way)

Going to close this for now - I think #229 will want to be the issue to address this, since the topic description will influence the feel of where the topic drawer best makes sense.