Anno 1800

The RDA Explorer <IP_ADDRESS> for the beta Anno 1800 works fine and I'm able to edit the assets. But when exporting it back the .rda gives two options;  version 2.0 (Anno 1404 & 2070) version 2.2 (Anno 2205)
The game crashes with either of these.
Thank you in advance.

There were issues with repacked rda files in later versions of Anno 2205 already. I assume the same is the case now.
Do these instructions work for your purposes?
https://github.com/lysannschlegel/RDAExplorer/issues/4#issuecomment-235424120

Did as instructed but no luck. (Missing the folder and file; config/engine.ini)
All in time, thank you for your prompt response and support!

Apparently the "PreferLocalFiles" option was deactivated in February, so unpacking the files to change them  does not work anymore; A short checksum.db file also was added to check the .rda files before launch, I've been unable to find out how it was calculated.

There were issues with repacked rda files in later versions of Anno 2205 already. I assume the same is the case now.
Do these instructions work for your purposes?
#4 (comment)

rebuild database working.. but take only files data*.*.rda  and now is in the folder file with language too..
for example in my folder: en_us0.rda so file.db is smaller
also is problem with checksum.db. I try find which alogarithm use but I dont find... I think its checksum of
file.db because I was finding for this file (md5, md4, sha1, sha256, crc, checksum) ..but nothig

A short checksum.db file also was added to check the .rda files before launch, I've been unable to find out how it was calculated.

Interesting.
How do you know what it's used for?
They have some kind of encryption for the rda files already and that one was a common encryption method that could just be brute-forced. Maybe we're lucky with checksum.db too.

As a general statement from me (since it's my repository): I really want to play Anno 1800 for a bit first before I venture into getting the explorer up and running for it. I had sat down in the past to make a new explorer that can work with the file.db, but it's a long process.
But everybody here, please feel free to find out how to get things to work, what checksum.db does and how it is calculated, and so on :)

Now I use quickbms for the press pack.
Using the previous 2205 bms.
It does not need to modify file.db and checksum.db  ...
Below is the code for 2205：
Anno 2070 / 2205 (script 0.1.2)
script for QuickBMS http://quickbms.aluigi.org
quickbmsver "0.7.0"
getdstring SIGN 32
if SIGN & "Resource File V2.2"
goto 0x310
get FIRST_NEXT long
math RES_FILE_TYPE = 2
else
set SIGN unicode SIGN
if SIGN & "Resource File"   # "Resource File V2.0"
math FIRST_NEXT = 0x404
math RES_FILE_TYPE = 1
else
print "Error: no magic signature found"
cleanexit
endif
endif
get FULLSIZE asize
for NEXT_OFF = FIRST_NEXT < FULLSIZE
goto NEXT_OFF
math OFFSET = NEXT_OFF
get TYPE long
get FILES long
if RES_FILE_TYPE <= 1
get ZSIZE long
get SIZE long
get NEXT_OFF long
else
get ZSIZE longlong
get SIZE longlong
get NEXT_OFF longlong
endif
math OFFSET -= ZSIZE
savepos BACKUP_OFFSET
# type & 4 uses a compressed container
# instead of single compressed files

# MEMORY_FILE   table of information
# MEMORY_FILE2  decompressed file system

if SIZE != 0
    if TYPE & 4
        math OFFSET -= 8
    endif

    # copy&paste except for the target file
    callfunction SET_ENCRYPTION 1
    if TYPE & 1
        clog MEMORY_FILE OFFSET ZSIZE SIZE
    else
        log MEMORY_FILE OFFSET ZSIZE
    endif
    encryption "" ""

    if TYPE & 4
        math TMP = OFFSET
        math TMP += ZSIZE
        goto TMP
        if RES_FILE_TYPE <= 1
            get ZSIZE long
            get SIZE long
        else
            get ZSIZE longlong
            get SIZE longlong
        endif
        math OFFSET -= ZSIZE

        callfunction SET_ENCRYPTION 1
        if TYPE & 1
            clog MEMORY_FILE2 OFFSET ZSIZE SIZE
        else
            log MEMORY_FILE2 OFFSET ZSIZE
        endif
        encryption "" ""
    endif

    for i = 0 < FILES
        getdstring NAME 0x208 MEMORY_FILE
        set NAME unicode NAME
        if RES_FILE_TYPE <= 1
            get OFFSET long MEMORY_FILE
            get ZSIZE long MEMORY_FILE
            get SIZE long MEMORY_FILE
            get CRC long MEMORY_FILE
            get ZERO long MEMORY_FILE
        else
            get OFFSET longlong MEMORY_FILE
            get ZSIZE longlong MEMORY_FILE
            get SIZE longlong MEMORY_FILE
            get CRC long MEMORY_FILE
            get ZERO long MEMORY_FILE
            get ZERO long MEMORY_FILE
            get ZERO long MEMORY_FILE
        endif

        if TYPE & 4
            log NAME OFFSET ZSIZE MEMORY_FILE2
        else
            callfunction SET_ENCRYPTION 1
            if TYPE & 1
                clog NAME OFFSET ZSIZE SIZE
            else
                log NAME OFFSET ZSIZE
            endif
            encryption "" ""
        endif
    next i

    goto BACKUP_OFFSET
endif

next
startfunction SET_ENCRYPTION
# Crypt "34AT9fdY33uT16m7" is used for signature in 2070
if TYPE & 2
if RES_FILE_TYPE >= 2
print "Alert: Encrypted TYPE 2 not supported yet on V2, I continue with the other files"
math FILES = 0
else
#encryption random "5 666666" 16    # not valid because needs >>16 on xor!
math KEY = 666666
putvarchr MEMORY_FILE3 ZSIZE 0 short
log MEMORY_FILE3 0 0
math TMPSZ = ZSIZE
math TMPSZ / 2
math TMPSZ * 2
for x = 0 < TMPSZ
math KEY * 0x000343fd
math KEY + 0x00269ec3
math TMP = KEY
math TMP >> 16
math TMP & 0x7fff
putvarchr MEMORY_FILE3 x TMP short
next x + 2
putvarchr MEMORY_FILE3 x 0 short # padding
getdstring XOR_KEY ZSIZE MEMORY_FILE3   # wastes some memory
encryption xor XOR_KEY "" 0 ZSIZE
endif
endif
endfunction
I don't know if it works for you...

@cunesewu Your script worked for me, I were able to add more zoom levels to Anno to be able to zoom further out! Thx

well it does not work with big files like from data8

try
`# Anno 1800 only! - supports bigger rda files (ex. data8.rda)
script for QuickBMS http://quickbms.aluigi.org
quickbmsver "0.7.0"
getdstring SIGN 32
goto 0x310
get FIRST_NEXT longlong
math RES_FILE_TYPE = 2
get FULLSIZE asize
for NEXT_OFF = FIRST_NEXT u< FULLSIZE
goto NEXT_OFF

math OFFSET = NEXT_OFF

get TYPE long

get FILES long

if RES_FILE_TYPE <= 1

    get ZSIZE long

    get SIZE long

    get NEXT_OFF long

else

    get ZSIZE longlong

    get SIZE longlong

    get NEXT_OFF longlong

endif

math OFFSET -= ZSIZE

savepos BACKUP_OFFSET

if SIZE != 0

    if TYPE & 4

        if RES_FILE_TYPE <= 1

            math OFFSET -= 8

        else

            math OFFSET -= 16

        endif

    endif

    callfunction SET_ENCRYPTION 1

    if TYPE & 1

        clog MEMORY_FILE OFFSET ZSIZE SIZE

    else

        log MEMORY_FILE OFFSET ZSIZE

    endif

    encryption "" ""

    if TYPE & 4

        math TMP = OFFSET

        math TMP += ZSIZE

        goto TMP

        if RES_FILE_TYPE <= 1

            get ZSIZE long

            get SIZE long

        else

            get ZSIZE longlong

            get SIZE longlong

        endif

        math OFFSET -= ZSIZE

        callfunction SET_ENCRYPTION 1

        if TYPE & 1

            clog MEMORY_FILE2 OFFSET ZSIZE SIZE

        else

            log MEMORY_FILE2 OFFSET ZSIZE

        endif

        encryption "" ""

    endif

    for i = 0 < FILES

        getdstring NAME 0x208 MEMORY_FILE

        set NAME unicode NAME

        get OFFSET longlong MEMORY_FILE

        get ZSIZE longlong MEMORY_FILE

        get SIZE longlong MEMORY_FILE

        get CRC long MEMORY_FILE

        get ZERO long MEMORY_FILE

        get ZERO long MEMORY_FILE

        get ZERO long MEMORY_FILE

        if SIZE != 0

            if TYPE & 4

                log NAME OFFSET ZSIZE MEMORY_FILE2

            else

                callfunction SET_ENCRYPTION 1

                if TYPE & 1

                    clog NAME OFFSET ZSIZE SIZE

                else

                    log NAME OFFSET ZSIZE

                endif

                encryption "" ""

            endif

        endif

    next i

    goto BACKUP_OFFSET

endif

next
startfunction SET_ENCRYPTION
if TYPE & 2

    math KEY = 0x71C71C71

    putvarchr MEMORY_FILE3 ZSIZE 0 short

    log MEMORY_FILE3 0 0

    math TMPSZ = ZSIZE

    math TMPSZ / 2

    math TMPSZ * 2

    for x = 0 u< TMPSZ

        math KEY * 0x000343fd

        math KEY + 0x00269ec3

        math TMP = KEY

        math TMP >> 16

        math TMP & 0x7fff

        putvarchr MEMORY_FILE3 x TMP short

    next x + 2

        putvarchr MEMORY_FILE3 x 0 short

    getdstring XOR_KEY ZSIZE MEMORY_FILE3

    encryption xor XOR_KEY "" 0 ZSIZE

endif

endfunction`
should work for every rda currently in the game

https://github.com/kskudlik/Anno-1800-RDA-Extractor/blob/master/anno7.bms

I have figured out how checksum.db is calculated. The latest release (<IP_ADDRESS>) includes the tool to generate file.db and checksum.db after you made changes to the *.rda files.
The workflow for this is quite convoluted at the moment. I may or may not have time to tackle that. But it's at least working now.
I have successfully run Anno 1800 after making changes to a rda file and file.db.
I will close this issue now, comment or create new issues if you have problems with the release.

I also want to point your attention to this project: https://github.com/xforce/anno1800-mod-loader
It allows to mod files that are "loose" and in another directory. It relies on injecting itself into the application, which might be more prone to break, but it is probably much easier to work with at least when developing mods.

It's not injecting technically speaking because I replace the python35.dll which the game loads anyways.


Herald of Thunder - Evaluate - An Error Occured

Trying to evaluate Herald of Thunder Lv1 Q15

Other gems load ok

0.5.12 (2020-02-03)

fix herald of thunder wrong item category (#176)


There seems to be an issue with the publication of releases on Zenodo

On the Zenodo page there are different versions but they all seem to point to version 0.5: https://zenodo.org/record/6792665
However, the actual latest snapshort is version 1.1.3 (which is the current latest release)
This makes it a bit hard when trying to cite the right version using the right citation meatdata.
The problem might be that the CITATION.cff file still references version 0.5. It seems Zenodo is pulling out the citation metadata form that file. See also: https://twitter.com/ZENODO_ORG/status/1420357001490706442

You're right, that is not how it is supposed to be. Zenodo does take the version number out of the citation metadata. I misunderstood the citation file and thought that the .cff file was 'attached' to our publication that cites the v0.5 release. Don't ask how i thought that was supposed to work. Just read up on it and will fix the version number starting with the next release which should be scheduled for monday or tuesday.
As for the past zenodo releases that still reference the v0.5 release: Do you know if we can change the referenced version number retroactively? Ideally i'd like all releases to have their correct citation file.

I fear that you cannot change the deposited archive afterwards. Thus, I would change the Citation.cff to make sure it works for the next releases. In addition, I would change the metadata of each archived version on Zenodo manually. I.e., you can change the displayed metadata in Zenodo but not the uploaded files.

I updated the citation file for the current release (v1.1.4). I'll keep the issue pinned until i fix the metadata of the archived versions.

This issue describes the behavior of citation files in conjunction with github and zenodo.


Auto-append trailing slash to target directory

Otherwise this will happen:

Fixed by use of filepath.Join()


IBC ConnectionOpenAck fails for solo machine client

Summary of Bug
After creating an IBC solo machine client, the connection handshake fails at ConnectionOpenAck.
For a solo machine, in MsgConnectionOpenAck, we send proof_height, proof_try, proof_client and proof_consensus. On cosmos-sdk side, this  function is called to verify all the details of the message. For solo machine, proof_try contains signed connection data, proof_client contains signed client state of tendermint client on solo machine, proof_consensus contains signed consensus state of tendermint client on solo machine and proof_height is the height of the solo machine at which these proofs were created.
Each of these proofs are verified by cosmos chain in these functions:

VerifyConnectionState
VerifyClientState
VerifyClientConsensusState

All these functions are also supplied with proof_height which are verified against the sequence stored in solo machine client state on cosmos chain. But, all the above three functions increment the sequence stored in solo machine client state. here, here and here.
The verification goes fine for the first verification function which is called, i.e., VerifyConnectionState (which increments the sequence in client state). Verification fails in VerifyClientState here because VerifyConnectionState changes the sequence/revision height in client state.
Version
v0.42.4
Steps to Reproduce
Here is the code:

Solo machine: https://github.com/devashishdxt/ibc-solo-machine
Cosmos SDK (there was a small bug in cosmos-sdk's solo machine code so I'm currently using my own fork): https://github.com/devashishdxt/cosmos-sdk/tree/solo-machine

To run the solo machine setup:

Start IBC enabled cosmos-sdk chain (with replaced custom cosmos-sdk fork).
Start solo machine server cargo run -- start (If you're running cosmos chain locally, all the defaults are set and you don't have to provide any values when starting)
Next, send AddChainRequest (use bloom RPC to send grpc requests). The defaults are set in a way that you don't have to provide any values if you're running the chain locally.

Finally, to establish connection, call grpc Connect. This will create a client, connection on both cosmos-sdk and solo machine and fails when sending acknowledgement of connection to cosmos-sdk.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Thanks for opening the issue and providing a lot of information. We need to change the solo machine verify functions to be a pointer so that incrementing the sequence can be referenced in the call to the client state verify function

We won't be backporting this, so the fix won't be included until the first release of the IBC module on this repository (3-4 weeks)

Thanks for the writeup!


Windows installer

Build mackerel-agent.msi by call wix\build.bat

Build requirement: WiX Toolset, git, mercurial, go
How to install: msiexec /qa /i build\mackerel-agent.msi APIKEY="..."

Installer registers mackerel-agent Windows Service and STDERR be logged to Windows Event Log.

Coverage remained the same at 50.3% when pulling 95a4d6f2d6c77867505a50b2ec6494305442b500 on windows_installer into 9bcb4cbb1c112a8f765c829ee56b9f2be68fd5d9 on master.

ci/appveyor  failure will be fixed by #61

Coverage remained the same at 50.3% when pulling 0229ae02f752fb99daf4502cde9740fe638e5546 on windows_installer into 6bed630d81a2d4151a5a743d181654e1c5561de3 on master.

Coverage remained the same at 50.3% when pulling ac68d8b2362aef44be8a764880b80bb335721b96 on windows_installer into e69595df7ec2907ea987e9d9c983042a7092e478 on master.


otk-make-partition-stages: add new otk-make-partition-stages external

This external will consume the data from otk-gen-partition-table and generate osbuild stages from it.
The expected usage is something like:
otk.define.modifciations.defauls:
 modifications:
  filesystem:
    min_disk_size: 20 GiB
    image_filename: disk.img

otk.define.defaults:
 filesystem:
   otk.external.gen_partition_table:
     modifications: ${modifications.filesystem}
     properties: ...
     partitions: ...

stages:
 ...
 otk.external.make_partition_stages:
   internal: ${filesystem.internal}
   filename: ${modifications.filesystem.image_filename}

We can use https://github.com/osbuild/images/blob/main/internal/testdisk/partition.go to generate partition tables for testing.

Opened #8 which includes this PR too.


Tool install request circexplorer2 2.3.8+galaxy0

toolshed.g2.bx.psu.edu/repos/iuc/circexplorer2/circexplorer2/2.3.8+galaxy0

Update:  pending install


Warning: LCW invalid configuration error

When running iOS version of LCW, the following warning is triggered:
warn Package @digitalcredentials/vc-status-list has been ignored because it contains invalid configuration. Reason: Package subpath './package.json' is not defined by "exports" in<EMAIL_ADDRESS>

@kayaelle yeah, I think so..


Perf: when launching cherry diff, only launch selected metrics

Currently, cherry diff launches two cherry runs:

one for the current commit (in your feature branch)
another one for the base branch commit (the commit from where your branch was started)
then it compares both of them:

if the number of violations increased, then it reports an error

Since it runs two cherry runs, and requires a subset of the metrics, we want to save CI time by only launching the required metrics. The challenge with that is notably the plugins, because we don't know in advance what names they'll have, so we'll need to think about it :)

Fixed here 12189dfd715ac1260d30c6733884cc66659ebf2a and here 36024aa2bcbde6ee1cd52a944e674e48aef8b3b7


Unique synthesized foreign type witnesses and make witness tables part of the metadata cache key

rdar://24958043

@swift-ci Please test

@swift-ci Please test source compatibility

What do you mean by "witnesses"?

Witness tables

Can you clarify that in the commits/comments? When I first saw that the "witnesses" were part of the uniquing key, I thought you meant the witness thunk function pointers themselves, which would be quite odd :)

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 276a4cea31943ca8af3bf734d17ab24eb49340db

Build failed
Swift Test OS X Platform
Git Sha - 276a4cea31943ca8af3bf734d17ab24eb49340db

@swift-ci Please test os x

@swift-ci Please test source compatibility

Build failed
Swift Test OS X Platform
Git Sha - 276a4cea31943ca8af3bf734d17ab24eb49340db

Build failed
Swift Test OS X Platform
Git Sha - 1ba367ada89a945abcafd7b683d41ceac359c9f3

Build failed
Swift Test Linux Platform
Git Sha - 1ba367ada89a945abcafd7b683d41ceac359c9f3

Build failed
Swift Test OS X Platform
Git Sha - 1ba367ada89a945abcafd7b683d41ceac359c9f3

@swift-ci Please test source compatibility

Source compatibility run: https://ci.swift.org/view/Pull Request/job/swift-PR-source-compat-suite/1206/


[kong] consolidate Ingress and Service templates

What this PR does / why we need it:
Create helper functions for Ingress and Service generation and refactor existing service templates to use them. Per-service templates now just gate whether to render these for a given service and set up some boilerplate variables.
This avoids copy-paste work when adding new features to these resources, which has historically been a source of inconsistent feature support across them (e.g. previously only the proxy supported explicitly setting a predefined ClusterIP because we forgot to add it to anything else).
This deprecates support for multi-host proxy Ingress resources. Although this has use in some environments (namely when Kong is behind some other ingress controller), it's unnecessary for the stock Ingress we generate, and prevents us from unifying the template. Users will need to write their own Ingress manually (or patch the proxy Ingress after creation--Helm 3 will preserve the change) to use this style of configuration.
Special notes for your reviewer:

We have to populate a bunch of variables for the helper context, since templates that receive a non-root context don't allow accessing things like .Chart.Name otherwise, and other helpers the new helpers use rely on them.
This places per-service Service and Ingress templates in the same file, mostly because they need similar sets of boilerplate variables.
Admin and proxy templates are kind of a mess since they just dump the old legacy template alongside the new template. After 2.0 (which will remove those deprecated configuration options), they'll look like the Manager template.
This technically allows you to create stream Service configuration on non-proxy services, but nobody should actually do so. It's ultimately harmless (the Service will have some ports that don't actually work) if someone does for some reason.

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] PR is based off the current tip of the next branch and targets next, not main
[x] New or modified sections of values.yaml are documented in the README.md
[x] Title of the PR and commit headers start with chart name (e.g. [kong])

This passes automated testing but affects things that automated tests don't check. I need to run through manual tests to confirm that all services remain reachable and check for unexpected differences between rendered templates before and after this change. Draft until that's done.

This passes automated testing but affects things that automated tests don't check. I need to run through manual tests to confirm that all services remain reachable and check for unexpected differences between rendered templates before and after this change. Draft until that's done.

I'm unsure if multi-host proxy Ingresses are commonly in use. They're something of a historical artifact from the early days of the chart, before our ingress controller existed. Placing Kong behind some other controller's proxy and using that controller to direct traffic to Kong (to match route configuration that had no corresponding K8S configuration) made more sense then. I'd argue it still makes more sense to define Ingresses per application (even if they point to Kong's Service rather than to the application Service) instead of having an omnibus Ingress for all applications, but can't easily say what's in the wild.
If we end up getting user complaints after releasing the deprecation warning, restoring support for it shouldn't be difficult, as the Ingress template is simple (for now, at least, Ingress has far fewer options than Service). We would need to write additional helpers for the rules section of the spec, one supporting the single host+TLS Secret config and one supporting the multi config, and choose which to render using the current legacy logic (whether hostname or hosts is present).

I'm unsure if multi-host proxy Ingresses are commonly in use. They're something of a historical artifact from the early days of the chart, before our ingress controller existed. Placing Kong behind some other controller's proxy and using that controller to direct traffic to Kong (to match route configuration that had no corresponding K8S configuration) made more sense then. I'd argue it still makes more sense to define Ingresses per application (even if they point to Kong's Service rather than to the application Service) instead of having an omnibus Ingress for all applications, but can't easily say what's in the wild.
If we end up getting user complaints after releasing the deprecation warning, restoring support for it shouldn't be difficult, as the Ingress template is simple (for now, at least, Ingress has far fewer options than Service). We would need to write additional helpers for the rules section of the spec, one supporting the single host+TLS Secret config and one supporting the multi config, and choose which to render using the current legacy logic (whether hostname or hosts is present).

I performed additional manual testing by comparing template output from current next against the consolidated version with ALL THE OPTIONS. full-k4k8s-with-kong-enterprise.yaml.txt and minimal-kong-standalone.yaml.txt cover most, though a few I turned on/off separately. Remaining discrepancies are:

The proxy metrics label moved from the end to the beginning of the label list. Doesn't actually matter.
externalIPs is now only rendered if it has content. Previously we rendered an empty block, which serves no purpose.
All admin templates now include namespace. We missed a bug in https://github.com/Kong/charts/pull/231 that only rendered it when using legacy admin configuration.

I performed additional manual testing by comparing template output from current next against the consolidated version with ALL THE OPTIONS. full-k4k8s-with-kong-enterprise.yaml.txt and minimal-kong-standalone.yaml.txt cover most, though a few I turned on/off separately. Remaining discrepancies are:

The proxy metrics label moved from the end to the beginning of the label list. Doesn't actually matter.
externalIPs is now only rendered if it has content. Previously we rendered an empty block, which serves no purpose.
All admin templates now include namespace. We missed a bug in https://github.com/Kong/charts/pull/231 that only rendered it when using legacy admin configuration.

Missed a bug with legacy proxy TLS sections, hence c7bd903. We don't check those currently in CI because the attempts to start instances will fail if we reference a non-existent Secret, and we don't have any Secrets (TLS or otherwise) available in the test environment.

Missed a bug with legacy proxy TLS sections, hence c7bd903. We don't check those currently in CI because the attempts to start instances will fail if we reference a non-existent Secret, and we don't have any Secrets (TLS or otherwise) available in the test environment.


Is there a limit to how many projects can be displayed?

I just added a fourth project but it's only showing the last three in the project section.
here's the site: https://getsomejam.net/#projects
here's the fork: https://github.com/bulentyusuf/gatsby-starter-mate

The projects are coming from this query, so in theory there is no constraint :)


GC: Restore: MockEvent w/ Attachment

Description
Adds feature to be able to create mock events with attachments

Type of change

[x] :sunflower: Feature

Issue(s)

*closes  #1005
Test Plan
Testing:
internal/connector/exchange$ go test -v . --run TestExchangeServiceSuite/TestRestoreExchangeObject/Test_Event_with_Attachment

[x] :zap: Unit test

 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.

@ashmrtn Unable to use
go test -v . --run TestGraphConnectorIntegrationSuite/TestMultiFolderBackupDifferentNames
due to the following failures:
graph_connector_helper_test.go:415:
        	Error Trace:	/Users/dadams39/workspace/Alcion/corso/src/internal/connector/graph_connector_helper_test.go:415
        	            				/Users/dadams39/workspace/Alcion/corso/src/internal/connector/graph_connector_helper_test.go:600
        	            				/Users/dadams39/workspace/Alcion/corso/src/internal/connector/graph_connector_helper_test.go:618
        	            				/Users/dadams39/workspace/Alcion/corso/src/internal/connector/graph_connector_helper_test.go:673
        	            				/Users/dadams39/workspace/Alcion/corso/src/internal/connector/graph_connector_test.go:898
        	Error:      	Not equal:
        	            	expected: []models.Attachmentable{(*models.FileAttachment)(0x14000446070)}
        	            	actual  : []models.Attachmentable{(*models.FileAttachment)(0x14000446000)}

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -7,3 +7,3 @@
        	            	     },
        	            	-    id: (*string)((len=180) "AAMkAGZmNjNlYjI3LWJlZWYtNGI4Mi04YjMyLTIxYThkNGQ4NmY1MwBGAAAAAADCNgjhM9QmQYWNcI7hCpPrBwDSEBNbUIB9RL6ePDeF3FIYAAAAAAENAADSEBNbUIB9RL6ePDeF3FIYAACLjfLQAAABEgAQAHoI0xBbBBVEh6bFMU78ZUo="),
        	            	+    id: (*string)((len=180) "AAMkAGY2ZWRmOTExLTVlYzYtNDEwZC05MmVlLTZmOTU3MTExYjIzZQBGAAAAAACFdCMEAOtyQ4SGcbCYoCwaBwBE3s1O9tepRYaJdBWpJfIBAACLlT1cAABE3s1O9tepRYaJdBWpJfIBAACLlt_DAAABEgAQAAMcKIqiSf1PhQl9IQTepNs="),
        	            	     odataType: (*string)((len=31) "#microsoft.graph.fileAttachment")
        	            	@@ -14,3 +14,3 @@
        	            	     wall: (uint64) 0,
        	            	-    ext: (int64)<PHONE_NUMBER>2,
        	            	+    ext: (int64)<PHONE_NUMBER>5,
        	            	     loc: (*time.Location)(<nil>)
        	            	@@ -18,3 +18,3 @@
        	            	    name: (*string)((len=11) "database.db"),
        	            	-   size: (*int32)(11418)
        	            	+   size: (*int32)(11466)
        	            	   },
        	Test:       	TestGraphConnectorIntegrationSuite/TestMultiFolderBackupDifferentNames/Events
        	Messages:   	Attachments

Unable to use
go test -v . --run TestGraphConnectorIntegrationSuite/TestMultiFolderBackupDifferentNames
due to the following failures:

Looks like events also need to use the custom attachment comparison logic defined in graph_connector_helper_test.go. An example of how to call it is here, so a similar line should be added to the events comparison logic here

Unable to use
go test -v . --run TestGraphConnectorIntegrationSuite/TestMultiFolderBackupDifferentNames
due to the following failures:

Looks like events also need to use the custom attachment comparison logic defined in graph_connector_helper_test.go. An example of how to call it is here, so a similar line should be added to the events comparison logic here

Created #1353 to be able to address this in a different PR.


Access image name and type

How can I access the image name and the type(jpeg, png or heif)?

it‘s not support

该邮件从移动设备发送
--------------原始邮件--------------
发件人："Stefan Sturm @.>;
发送时间：2021年5月3日(星期一) 凌晨4:22
收件人："flutter-package/images_picker" @.>;
抄送："Subscribed @.***>;
主题：[flutter-package/images_picker] Access image name and type (#25)
How can I access the image name and the type(jpeg, png or heif)?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Is it possible to add it? It would make things way easier, as we need to know the file type on backend side :)

if you set compress param, it must return JPG type , because only JPG support compress
if you did not set compress, it will return type itself in gallery.
if you want get file type,you should get the suffix of string you get

please use version 1.2.4.


[GOBBLIN-542] Change AsynRequest instance variable into protected

To make this class is extensible.
Gobblin Salesforce Writer implementation is going to extend this class to have some customized behavior in the Request.
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-542] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-542

Description

[x] Here are some details about my PR, including screenshots (if applicable):

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

+1 Thanks @zxcware


Latency of simple tf.data.Dataset transformations is higher than raw Python

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 16.04
TensorFlow installed from (source or binary): pip install tensorflow (CPU only)
TensorFlow version (use command below): v1.4.0-rc1-11-g130a514 1.4.0
Python version: 3.5.2

Describe the problem
I'm trying to improve performance by moving to tf.data.Datasets to manage epochs and minibatches (particularly I/O performance on a GPU when I come to scaling up). However I'm finding that this is much slower than just using nested for loops in Python.
Source code / logs
Here's an example using a dataset with 10,000 numbers, 10 epochs and a minibatch size of 100:
import tensorflow as tf
import numpy as np
from time import time

MINI_BATCH = 100
EPOCHS = 10

# Dataset consisting of 10000 random numbers
raw_data = np.random.randn(10000)

# Raw Python implementation
start = time()
split_data = np.split(raw_data, 10000 // MINI_BATCH)

for _ in range(EPOCHS):
    for i, batch in enumerate(split_data):
        # Do stuff with batch data
        x = batch * 2
print("Raw Python done in", time() - start)

# TensorFlow implementation
start = time()
dataset = tf.data.Dataset.from_tensor_slices(raw_data)
dataset = dataset.repeat(EPOCHS)
dataset = dataset.batch(MINI_BATCH)
iterator = dataset.make_one_shot_iterator()
next_chunk = iterator.get_next()

with tf.Session() as sess:
    while True:
        try:
            batch = sess.run(next_chunk)
            # Do stuff with batch data
            x = batch * 2
        except tf.errors.OutOfRangeError:
            break
print("TensorFlow done in", time() - start)

Output:
Raw Python done in 0.0011773109436035156
TensorFlow done in 0.14212393760681152

Does anyone know why this might be the case?
I'm guessing that most of the overhead is in the evaluation of iterator.get_next() on every loop. If this is not supposed to be evaluated it would be useful to have some examples of how it should be used without using sess.run each time.

The short answer here is that building a single minibatch of 100 elements is too small an operation to benefit from TensorFlow as it's currently implemented. (You'll also find that multiplying two small matrices is faster in NumPy than loading it into TensorFlow.)
The Dataset implementation is designed to perform non-trivial amount of preprocessing (decoding images, parsing text, etc.); and the Session implementation is geared towards computations that take at least a few milliseconds to perform. In the intended use case, you would pass the output of iterator.get_next() to the input of a neural network, for inference or training.
Each of the TensorFlow operations in your example takes approximately 140 microseconds. Calling into TensorFlow from Python currently has an overhead of around 60 microseconds, a trivial step takes around 20 microseconds, and invoking an operation such as Iterator.get_next() incurs a few more microseconds of overhead, plus a context switch.
There are a couple of things you could try:

Try using a tfe.Iterator in Eager mode, which acts more like a Python iterator, and takes approximately 100us per batch in my tests.

Creating a callable for the step, using get_next_chunk = sess.make_callable(next_chunk) and then using get_next_chunk() in place of sess.run(next_chunk) shaves about 65us off each invocation (to approximately 92us per batch) in my tests.

Rewrite the pipeline to cache the processed data for an epoch:
dataset = tf.data.Dataset.from_tensor_slices(raw_data)
dataset = dataset.batch(MINI_BATCH)
dataset = dataset.cache()
dataset = dataset.repeat(EPOCHS)
iterator = dataset.make_one_shot_iterator()

This change reduces the cost of each mini-batch to about 42us in my tests (and ~52us in Eager mode).

Where does the rest of the time go? In the non-caching versions, the data are currently copied twice, out of the original array in Dataset.from_tensor_slices(), then into the batch in Dataset.batch(). We could potentially use Tensor::Slice() to avoid a deep copy in some cases, although that only works when the slices are aligned to 32-byte boundaries, which might not always be the case. (It isn't for a vector of shape (10000,) int64 elements but it is if e.g. you reshape it to (100, 100).) Alternatively, and at the cost of some memory inflation, Dataset.from_tensor_slices() could eagerly slice up its input ahead of time, where the up-front initialized cost would be amortized over multiple epochs... this is what the explicit Dataset.cache() does for you. There are more context switches than are strictly necessary, especially when running in Eager mode, where the work can happen on a donated Python thread. Finally, profiling suggests that there are some non-trivial overheads when dealing with tensors of a single element (shape calculations, in particular, weigh heavily in the profile when the cost of the actual copy is small).
There are definitely some overheads worth paring down here, although they are likely to have only a small effect on headline performance numbers, so fixing them won't be top priority. I'll add some benchmarks to track the various versions, and invite contributions that improve things for all workloads.

@mrry What do you think?

@bhack tf.py_func() has to acquire the GIL in order to run read_fn, so unless there is a substantial amount of work in that function that happens while the GIL is released, it is unlikely that you will see much of a parallel speedup for that code.

@mrry We need to have a decent amount of computation to surpass the GIL overhead right?

Yes, plus that computation has to happen in a method that releases the GIL (e.g. many NumPy routines).

@mrry Do you think to add something about this in https://github.com/tensorflow/tensorflow/blob/master/tensorflow/docs_src/performance/datasets_performance.md? I think it could be useful.


phpMyAdmin not work

I has installed 1.8.1,but phpMyAdmin not work correctly ,show error
"403
Forbidden
Unfortunately, you do not have permission to view this"

replace it with new phpMyAdmin nginx config, try:
sudo rsync -avh /vesta-start/etc/nginx/conf.d/*.inc /etc/etc/nginx/conf.d/
sudo nginx -t
sudo nginx -s reload

thanks.
i try this below
###############################
[root@iZj6c2lvtw1kaa41257su4Z vestacp]# docker exec -it 45e0f240544d  /bin/bash
root@45e0f240544d:/# sudo rsync -avh /vestacp/etc/nginx/conf.d/*.inc /etc/nginx/conf.d/
sending incremental file list
rsync: change_dir "/vestacp/etc/nginx/conf.d" failed: No such file or directory (2)
sent 20 bytes  received 12 bytes  64.00 bytes/sec
total size is 0  speedup is 0.00
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1183) [sender=3.1.1]
root@45e0f240544d:/# ls /vestacp/etc/nginx/conf.d/
ls: cannot access '/vestacp/etc/nginx/conf.d/': No such file or directory
root@45e0f240544d:/# sudo rsync -avh /vesta/etc/nginx/conf.d/*.inc /etc/nginx/conf.d/
sending incremental file list
sent 80 bytes  received 12 bytes  184.00 bytes/sec
total size is 1.15K  speedup is 12.46
root@45e0f240544d:/# sudo nginx -t
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/YL/conf/web/1gk.net.nginx.ssl.conf:4
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/HB/conf/web/qzep.cn.nginx.ssl.conf:4
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/CLnet/conf/web/cl1.net.nginx.ssl.conf:4
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/HB/conf/web/hb1.net.nginx.ssl.conf:4
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/CLcom/conf/web/cl5u.com.nginx.ssl.conf:4
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
root@45e0f240544d:/# sudo nginx -s reload
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/YL/conf/web/1gk.net.nginx.ssl.conf:4
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/HB/conf/web/qzep.cn.nginx.ssl.conf:4
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/CLnet/conf/web/cl1.net.nginx.ssl.conf:4
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/HB/conf/web/hb1.net.nginx.ssl.conf:4
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /home/CLcom/conf/web/cl5u.com.nginx.ssl.conf:4
root@45e0f240544d:/# exit
exit
[root@iZj6c2lvtw1kaa41257su4Z vestacp]# reboot
###############################
but not fixed,show 404
404
Page Not Found
It seems that the page you were trying to reach does not exist anymore, or maybe it has just moved. You can start again from the home or go back to previous page.
Appreciate for any reply from you!

Ooopse, I forgot the main domain is proxy to apache and not fpm.  Try this, make sure you replace {hostname} with your actual panel hostname:
sudo bash /bin/vesta-update.sh
sudo echo 'include /etc/nginx/conf.d/dbadmin.inc;' /home/admin/web/{hostname}/private/nginx.conf
sudo nginx -t
sudo nginx -s reload

Explain:
sudo bash /bin/vesta-update.sh - Update your vesta with latest templates and php config
Then push the dbadmin config into your panel private/customizable nginx.conf
I'll work on the change to update the docker image.

Close as resolved with adminer.


Not seem to work on MacOS BigSur

On click. Seems to not do anything.
Tried out both options. Neither one is working.

Hi @luv4ever2shail 😄
I've also had some issues when running on Linux or in specific folder names in Windows such as data. Could you tell me what is your OS, and if it never works?

I'm using macOs Big Sur

I think there's a problem on activating the extension. I spent most of yesterday trying to fix it in Linux but I could not find the reason why it happens 😞
If I cannot solve it, I will re-write the extension. Currently I'm a bit busy with university but as soon as I can I will get into it.
If you want to fork and make a pull request, feel free!

Hey @luv4ever2shail :smile:
I've migrated the extension from TS to JS. I wanted to see if I could do it with TypeScript but I guess I still have a long road to learn. So I decided to go back to JS, since I've coded more with it.
Before publishing the app, I have created a branch Ts_to_js where you can find the new/updated extension.
Could you plese clone the branch and try to run it in your MacOS? It would mean a lot to me! :1st_place_medal:
Once you've told me that it works properly, I will make the final pushes and update it.

Hey @mikededo
I would love to test it out for you. But I have never created or ran a VSCode extension.
So could you please guide me through in order for me to test it out?
Thank you for looking into this. This is awesome.

Hey @mikededo
I was able to successfully run and test the project.
It works awesome.
Some problems:

Option to generate barrel file was not able on the right click when I was testing (Is this normal?)
When running the command current and nested folders on the lib doesn't seem to work
Another issue is the barrel file is named after the folder name. Which wipes out the data of the file present with the same name in the folder. Can you to do check for that as well if possible?

Let me know if you need more testing done on this?

Sorry! I was in class...

I was able to clone and install all the npm dependencies but it just giving me error on the 'lodash' import. Any reason?

I'm glad you solved it!

Option to generate barrel file was not able on the right click when I was testing (Is this normal?)

Hmm 🤔, that is not normal. You could only do Generate Current and Nested option?

When running the command current and nested folders on the lib doesn't seem to work

I will give it a check. With the last version there where some times where the folder named data would not work. Did any error pop out? Was any file created? If so, was the file empty? Does this lib folder contain any .dart file (it only works if it has a .dart file as a direct child)?

Another issue is the barrel file is named after the folder name. Which wipes out the file contents present with the same name in the folder. Can you to do check for that as well if possible?

Well, I think it breaks it's philosohpy. Barrel files are intended to be named after the folder, that's is why it wipes out it's content. I do not intend to change it but maybe we'll see in the future 😉
I've also seen that now I do not export the nested folders barrel file when using Generate Current and Selected.
If you find anything, please, do not hesitate to update the code!

Hmm 🤔, that is not normal. You could only do Generate Current and Nested option?

I was not able to access the Generate Current and Nested option on right click during testing. (in fact none of the option was available on right click)
Regarding lib folder.. I didn't receive any error message.
Thank you

That is strange. I can use both options... By the way, are you clicking in a folder, or in a file? The extension is set up only to work when clicked on a folder!

Changes pushed and working in Windows and Linux!

I'm closing this issue!
I've you encounter any error, just open a new one 😉

ajafja


Create out PyPi Package

[x] Sign into PyPi Account
[x]  Generate access token
[x]  Add token to GitHub repo secrets
[x]  Create Python PyPi Package deployment action
[x]  Update package version
[x]  Push/release changes to PyPi
[x]  Test package in another environment

Done

Done

https://pypi.org/project/IPYNBRENDERERBYDIP/0.0.2/

Link Added


✨(frontend) add CRUD entities pages (5)

Purpose
Creation of CRUD pages for API models
Proposal

[x] Create CRUD organization pages
[x] Create CRUD course-run pages
[x] Create CRUD course pages
[x] Create CRUD certificate-definition pages

Remember to use the new FUN logo :

Few UI/UX suggestions during my live testing :
I'll put notifications just below the user component.

Let's sort models alphabetically first :

Into model list views, I think each row should be clickable to access quickly to the edition view.

In edition view, for translatable models, I think language tabs should have a different color.

yarn lint raises several warnings that can be fixed easily.

It seems there is a bug within autocompletion fields.

Within the toast, the font family seems not well set.

Remaning to sort alphabetically. Furthermore, Organization should be be plural.


feat(plugin): use relative paths, support "%/" in rootPathSuffix to r…

Quite a lot of changes:
This packages uses absolute paths that don't play well with compiled files, it leads to compiles files requiring non-compiled files and breaks.
When you have several modules with one parent build system (like babel), you have to be able to dynamically adjust the rootPath. Plugged in %/ syntax in the rootPathSuffix option to automatically bubble up to the closest package.json directory.

Hi @mgcrea sorry for the late response,
Thanks for the PR, i've a few questions about your (great) ideas:

why do you change the syntax from ~/ to %/?
you're changing the replacing of the ~/ with ./, that means the path directs to the current folder, what is the behind this?

Btw, it would be great if your PR deliver green tests :)
michael

Something new? Otherwise i close this PR.


fix mem leaks in try_decode_PKCS12() of crypto/store/

When loading PKCS#12 files that include a cert/ca chain the chain container was not deallocated.
Fixing this I improved the layout of crypto/store/loader_file.c to satisfy check-format.pl -l.

BTW, the mem leak came up experimenting how to use the OSSL_STORE API as requested by @mattcaswell  for the CMP contribution chunk 11: https://github.com/openssl/openssl/pull/11470#discussion_r416669564
It indicates that the OSSL_STORE API is not sufficiently tested. In fact, I can't find any tests for it.

It indicates that the OSSL_STORE API is not sufficiently tested. In fact, I can't find any tests for it.

There are lots of store tests in 90-test_store.t - but they all test via the command line store app rather than the API directly.

It indicates that the OSSL_STORE API is not sufficiently tested. In fact, I can't find any tests for it.

There are lots of store tests in 90-test_store.t - but they all test via the command line store app rather than the API directly.

Ah, right.
I've made sure that these tests can run also if DSA and/or EC key generation does not work
(BTW, I had to disable tests based on pbeWithMD5AndDES-CBC apparently due to deprecation)
and added -chain -CAfile cacert.pem to the openssl pkcs12 -export calls
such that memory leaks are caught also in case they are due to a non-empty chain.

Currently I always see one Travis CI failure like this:
 No space left on device at ./Configure line 1722.

No space left on device at ./Configure line 1722.

Gosh, my mem leak fixes did not solve this ;-)

I've meanwhile adapted OSSL_STORE_close() such that it succeeds gracefully when given a NULL argument, like any free() function does.

Note that I also fixed some issues in the OSSL_STORE documentation.

Regarding OSSL_STORE_close() being a kind of free(), it's semantically closer to fclose(). What's the result of fclose(NULL)? :wink:

Regarding OSSL_STORE_close() being a kind of free(), it's semantically closer to fclose(). What's the result of fclose(NULL)? wink

I know that the semantics of fclose(NULL) is officially undefined,
and I believe that this is purely for historical reasons,
IMHO it is preferrable to define the behavior in this case as no-op.
For OSSL_STORE_close() we have the chance to do better :smile:

I've just done the same enhancements of OSSL_STORE_open.pod as in #11912.

For commit messages, I disagree with "Allow NULL argument (as with *_free()) to OSSL_STORE_close()".  Please make it "Allow NULL argument to OSSL_STORE_close()".
My reasoning is that although OSSL_STORE_close() does free its argument, it's semantically closer to fclose(), the freeing part is just an implementation detail.

The commit message can be amended without a re-review or even during the merge.

The commit message can be amended without a re-review or even during the merge.

Thanks @t8m for helping out toward finalizing this PR!
I've just rebased it, squashed two related commits (regarding doc of OSSL_STORE),
and re-worded one commit as requested by @levitte.
Unless there is an objection I'm going to merge this tomorrow.

Still approved after the rebase, for the record.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

When loading PKCS#12 files that include a cert/ca chain the chain container was not deallocated.

Looking back, I'm surprised we haven't seen that already.  Is there a way to demonstrate this with existing master, or even 1.1.1?

When loading PKCS#12 files that include a cert/ca chain the chain container was not deallocated.

Looking back, I'm surprised we haven't seen that already. Is there a way to demonstrate this with existing master, or even 1.1.1?

Oops, I put my answer further up in the discussion; see there.

And so far the tests did not include a chain in the PKCS#12 file(s) parsed.

Thanks, that's what I suspected.  So we need one to test the mem leak, can one be provided, or musst we count on one being generated?

I had already added a chain to some of the PKCS#12 test cases:
+++ b/test/recipes/90-test_store.t
@@ -374,6 +374,7 @@ sub init {
                           }
                           run(app(["openssl", "pkcs12", "-inkey", $srckey,
                                    "-in", $srccert, "-passout", "pass:password",
+                                   "-chain", "-CAfile", "cacert.pem",
                                    "-export", "-macalg", $macalg,
                                    "-certpbe", $certpbe, "-keypbe", $keypbe,
                                    "-out", $dstfile]));

These would fail if if the mem leak still existed - provided not all the test were disabled due to init fail issue discussed above.

Meanwhile I've added also $use_des and successfully tested various combinations of
negating $use_md5, $use_des, $use_dsa, and $use_ecc.

I also found that, due to the so far 'successful' skip of the tests in case their init failed,
the test cert generation using the rather new CA configuration file test/ca-and-certs.cnf
went wrong without being noticed by its author (apparently @richsalz in commit 4e6e57cfcdd75b827ff7171927d87e95b5b86ae8).
I've corrected this as well and made sure that the tests fail if their init fails,
to prevent such obscure failure issues for the future.

@levitte wrote:

Will need re-review

Yes. Now the PR is ready for that.

For some reason Travis build is not getting executed.

For some reason Travis build is not getting executed.

I kicked it by closing and re-opening the PR, but this did not help.
Apparently a more general issue?

It looks like Travis just had a delay starting up. It's running again.

There was Travis failure, which pointed out that PKCS#12 generation is not possible in case no-des.
Fixup committed.

It turns out that there was another init failure in case no-des, which I've handled now.
@levitte, I meanwhile understand why when authoring 90-test_store.t you took the shortcut of simply letting the tests pass' (for void) if anything went wrong in init()`.
I'm confident that now all relevant algorithm exclusion cases are finally sorted out and ask you to re-confirm your approval.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Thanks @levitte for the swift re-review and re-confirmation.
I've just rebased and squashed the fixups (to be merged on Monday morning).

Merged - thanks!


C3: Fix keyboard buttons on the right getting stuck in pressed state

fixed #21907
This is not the final solution.there is no problem with KeyButton.  KeyButton::PaintEvent and QAbstractButton::setDown(https://code.woboq.org/qt5/qtbase/src/widgets/widgets/qabstractbutton.cpp.html#_ZN15QAbstractButton7setDownEb) are always be called with correct state.
but the relevant area of the screen is not updated. I don't know the reason yet. the quick solution is to call parentWidget()->update() in KeyButton::event  or set focus on line edit.

The keyboard feels less responsive after this for some reason.

@adeebshihadeh keyboard multitouch was broken in https://github.com/commaai/openpilot/commit/a96f35896681cbbf9752b2ba4176b4d7b43d6d1b somehow

@adeebshihadeh it's ok now

Thanks for tracking that down @sshane.
Nice work @deanlee! There still seems to be something weird going on with the right side of the keyboard. If you hold down a button on the left side and tap on buttons on the right, the buttons on the right don't show the pressed style. Will merge as this is a big improvement, but would be nice to track that down.

@adeebshihadeh  : fixed this issue in #22127


api: add RouteConditionReason to v1alpha2

What type of PR is this?
/kind documentation
/kind feature
/kind api-change
/kind deprecation
What this PR does / why we need it:
Adds a RouteConditionReason type with known required reasons and renames two RouteConditionType constants. Not sure if the release note formatting would make more sense to split this into two separate PRs.
Which issue(s) this PR fixes:

Fixes #1109, refs #1112
Does this PR introduce a user-facing change?:

adds RouteConditionReason type with RouteReasonAccepted, RouteReasonResolvedRefs and RouteReasonRefNotPermitted constants

deprecates ConditionRouteAccepted and ConditionRouteResolvedRefs constants, adds RouteConditionAccepted and RouteConditionResolvedRefs constants

In the course of writing our Gateway.Listeners[].allowedRoutes implementation @shaneutt noted that there was no way we could indicate rejections on the resource. He originally suggested a ConditionRouteRejected in line with the existing constants, but assuming this is accepted it looks like we should instead add a false RouteConditionReason for RouteConditionAccepted.
Not sure if we could piggyback off this PR to do so; I submitted https://github.com/mikemorris/gateway-api/pull/1 if so, or can retarget it to this repo after this is merged.

Agreed that's a valid case that's difficult to communicate currently @rainest, and I do think communicating this through a RouteConditionReason feels safer than crossing a disallowed namespace boundary to set a ListenerStatus condition.
I think I'd lean towards retargeting after merging this though given that it's somewhat new/unspecified scope - might be nice to add a conformance test (or augment the existing HTTPInvalidCrossNamespace test) illustrating expected usage too!

@mikemorris A few tiny comments but otherwise LGTM. @rainest I like the change you proposed in https://github.com/mikemorris/gateway-api/pull/1, do you mind filing a follow up PR here once this one merges?

/ok-to-test

/lgtm


Connection lost due to roster items

Thanks for this impressive client!
Just discovered issue with disconnects after having contacts from not available XMPP transports. After unregistering from those I was able to remain logged on JSXC. Could be related to issue with strophe.js - not sure.

Thanks for reporting. Can you give me an example of an "not available XMPP transport"? Never tried transports before.
I think this is not related to diaspora/jsxc#60.

Not sure when I will have time to install transports and test with my roster again.

With the latest beta release we updated strophejs to the latest release, so you should check if this issue is still valid. If you can confirm that or give an example how to reproduce this, please reopen this issue.


python311Packages.dask: 2023.12.0 -> 2024.1.1

Description of changes

Changelog dask: https://docs.dask.org/en/latest/changelog.html
Changelog dask-histogram: https://github.com/dask-contrib/dask-histogram/releases/tag/2024.2.0
Changelog dask-awkward: https://github.com/dask-contrib/dask-awkward/releases/tag/2024.2.0
Changelog awkward: https://github.com/scikit-hep/awkward/releases/tag/v2.6.0

cc @veprbl @FRidh
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.


document theater extension

Please! What is this magic? :)

I will probably rip it out. It's an extension that allows an authorized user to send messages as any NICK. This was pretty cool when we had a bot to play back the script to Ghostbusters. Actually, thinking back on how cool that was, maybe we should keep the theater extension around.

:+1 for ripping this out. This seems out-of-scope :D
James Mills / prologic
E<EMAIL_ADDRESS>W: prologic.shortcircuit.net.au
On Tue, Jul 25, 2017 at 1:22 PM, Edmund Huber<EMAIL_ADDRESS>wrote:

I will probably rip it out. It's an extension that allows an authorized
user to send messages as any NICK. This was pretty cool when we had a bot
to play back the script to Ghostbusters. Actually, thinking back on how
cool that was, maybe we should keep the theater extension around.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/edmund-huber/ergonomadic/issues/16#issuecomment-317860808,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABOv-vOV71quvvmPzkgnfNLeN4JoMQ4Kks5sRk6jgaJpZM4FKd6X
.


Update version from 0.0.81 to 0.0.82

This is an automated update of version in pyproject.toml. This action is performed by publish.yml.

updated version from 0.0.81 to 0.0.82, @SuleyNL pls review


ERROR:composer.cli.launcher:Rank 0 crashed with exit code -11.

@Skylion007 when i start train the sd-2 (vae.encoder step) ,the issue occurs, no any information but "ERROR:composer.cli.launcher:Rank 0 crashed with exit code -11." hope your reply,thanks.
Instantiating logger <composer.loggers.wandb_logger.WandBLogger>
[2024-05-07 09:39:45,349][composer.algorithms.low_precision_groupnorm.low_precision_groupnorm][INFO] - Successfully replaced 61 instances of GroupNorm with LowPrecisionGroupNorm
[2024-05-07 09:39:45,379][composer.algorithms.low_precision_layernorm.low_precision_layernorm][INFO] - Successfully replaced 48 instances of LayerNorm with LowPrecisionLayerNorm
Instantiating callbacks <composer.callbacks.speed_monitor.SpeedMonitor>
Instantiating callbacks <composer.callbacks.lr_monitor.LRMonitor>
Instantiating callbacks <composer.callbacks.memory_monitor.MemoryMonitor>
Instantiating callbacks <composer.callbacks.runtime_estimator.RuntimeEstimator>
Instantiating callbacks <composer.callbacks.OptimizerMonitor>
start to train........
[W Utils.hpp:135] Warning: Environment variable NCCL_ASYNC_ERROR_HANDLING is deprecated; use TORCH_NCCL_ASYNC_ERROR_HANDLING instead (function getCvarInt)
[2024-05-07 09:39:45,388][composer.utils.reproducibility][INFO] - Setting seed to 17
[2024-05-07 09:39:45,572][composer.trainer.trainer][INFO] - Run name:<PHONE_NUMBER>-burrowing-goshawk
wandb: (1) Create a W&B account
wandb: (2) Use an existing W&B account
wandb: (3) Don't visualize my results
wandb: Enter your choice: 3
wandb: You chose "Don't visualize my results"
wandb: Tracking run with wandb version 0.16.3
wandb: W&B syncing is set to offline in this directory.
wandb: Run wandb online or set WANDB_MODE=online to enable cloud syncing.
wandb: WARNING URL not available in offline run
[2024-05-07 09:40:08,246][composer.trainer.trainer][INFO] - Stepping schedulers every batch. To step schedulers every epoch, set step_schedulers_every_batch=False.
[2024-05-07 09:40:08,249][composer.utils.reproducibility][INFO] - Setting seed to 17
/home/jinglianzhong/miniforge3/envs/py39/lib/python3.9/site-packages/torch/distributed/fsdp/_init_utils.py:437: UserWarning: FSDP is switching to use NO_SHARD instead of ShardingStrategy.SHARD_GRAD_OP since the world size is 1.
warnings.warn(
[2024-05-07 09:40:08,308][composer.trainer.trainer][INFO] - Setting seed to 17
[2024-05-07 09:40:08,308][composer.utils.reproducibility][INFO] - Setting seed to 17
[2024-05-07 09:40:08,308][composer.trainer.trainer][INFO] - Using precision Precision.AMP_FP16

Config:
composer_commit_hash: None
composer_version: 0.22.0
node_name: unknown because NODENAME environment variable not set
num_gpus_per_node: 1
num_nodes: 1
rank_zero_seed: 17
time/remaining_estimate_unit: hours

                                                                                self.image_key: image            0%|                         | 0/550000 [00:00<?, ?ba/s]

c: <torch.cuda.amp.autocast_mode.autocast object at 0x7f013c97c820>
ERROR:composer.cli.launcher:Rank 0 crashed with exit code -11.
Waiting up to 30 seconds for all training processes to terminate. Press Ctrl-C to exit immediately.
Global rank 0 (PID 1234168) exited with code -11
ERROR:composer.cli.launcher:Global rank 0 (PID 1234168) exited with code -11

wrong pytorch version


Unexpected behavior when using vm.prank in a Foundry test

Component
Forge
Have you ensured that all of these are up to date?

[ ] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (6822860 2024-07-29T00:20:30.057117769Z)
What command(s) is the bug in?
forge test
Operating System
Linux
Describe the bug
Unexpected Behavior with vm.prank in Foundry Tests
Issue Description
I've encountered an unexpected behavior when using vm.prank in a Foundry test. It appears that the pranked address is only being applied to the first function call after vm.prank, even when that call is part of the arguments of a subsequent call.
Code Snippet
vm.prank(COMMUNITY_CREATOR);
artBlockNFT.approve(address(mainEngine), artBlockNFT.getTokenId(userProductID));

Expected Behavior
I expected vm.prank(COMMUNITY_CREATOR) to set the caller address to COMMUNITY_CREATOR for the entire approve call, including the nested getTokenId call.
Actual Behavior
The test output suggests that only getTokenId is called with the pranked address, while approve is called with a different address:
├─ [0] VM::prank(COMMUNITY_CREATOR: [0x3140316e3923d01946617334372A56dc30ecdfbB])
│   └─ ← [Return]
├─ [670] ArtBlockNFT::getTokenId(0xa750005500000000000000000000000000000000000000000000000000000000) [staticcall]
│   └─ ← [Return] 0
├─ [3311] ArtBlockNFT::approve(MainEngine: [0xbD7A792B8B0943A2f6716974fe1755E7f36aa5b0], 0)
│   └─ ← [Revert] ERC721InvalidApprover(0x7FA9385bE102ac3EAc297483Dd6233D62b3e1496)
└─ ← [Revert] ERC721InvalidApprover(0x7FA9385bE102ac3EAc297483Dd6233D62b3e1496)

The approve call is reverting with ERC721InvalidApprover, suggesting it's not being called by COMMUNITY_CREATOR.
Questions

Is this the intended behavior of vm.prank?
If not, is this a bug in Foundry?
If this is intended, what's the correct way to ensure both getTokenId and approve are called by the pranked address?

Any insights or clarifications on this behavior would be greatly appreciated. Thank you!

This is intended behavior for vm.prank.
You can use vm.startPrank(addr) for your use-case.
eg.
vm.startPrank(COMMUNITY_CREATOR)
artBlockNFT.approve(address(mainEngine), artBlockNFT.getTokenId(userProductID));
vm.stopPrank()

Marking as resolved by https://github.com/foundry-rs/foundry/issues/8740#issuecomment-2309571665, expected behavior.


BREAKING CHANGE(Loader): component refactor

This PR:

updates docs to latest pattern (#564);
fixes Loader warning in tests (#599);
adds content shorthand instead of text.

Is breaking change.

Current coverage is 100% (diff: 100%)

No coverage report found for master at 89456fa.

Powered by Codecov. Last update 89456fa...f8100bd

LGTM and codecov is showing no drop in coverage (https://codecov.io/gh/Semantic-Org/Semantic-UI-React/commit/ba955b37fb58484b0b06ea9315f7e9bf2690639a) 👍

Released in<EMAIL_ADDRESS>


Height does not get calculated with Mat-accordion.

Describe the bug
Using Mat-accordion. Height does not seem to be get evaluated when expansion and collapse happen. Tried using all calculation methodologies, none of them seems to be working.
It left lot of blank space after Accordion ( almost the space it took  during expansion )
Expected behavior
Should get the height calculated correctly.
Desktop (please complete the following information):

all

Smartphone (please complete the following information):
-all

You might need to manual force the iFrame to resize after the accordion runs, so events are hard to detect
if ('parentIFrame' in window) {
  parentIFrame.size()
}

If that doesn’t work then it will be a CSS bug in the accordion control

Looks to be an issue with CSS on page. Used 100vh that does not seems to work with it.


Actual JS Formatting

Don't use double quotes and commas, that's not regular JS format

Thanks for your pr.


MSIX packaging for arbitrary .NET project types

Motivation
The .NET SDK supports streamlined MSIX publishing for WinUI 3 and MAUI projects. For other project types one can use an application packaging project. Packaging projects are cumbersome to use, more complicated to use than dotnet in CI pipeline and cannot pass MSBuild properties to child projects easily.
Desired solution
I would like to have MSIX packaging tools for arbitrary .NET project types including Avalonia, WPF, WinForms, Console. It should be compatible with other features like single file executable, trimming and Native AOT.
Additional context
I originally posted this issue at dotnet/sdk#45045. However, as @Sergio0694 pointed out, MSIX packaging functionality is already implemented in Microsoft.Windows.SDK.BuildTools.MSIX and could be extended to support other frameworks than WinUI 3 or MAUI. Unfortunately, I could not find the source code for that NuGet package and hope that I am not totally wrong by opening this issue here.

"could be extended to support other frameworks than WinUI 3 or MAUI"

Note, UWP (on .NET 9) also uses that package, so it's already the case that it supports several different frameworks. The MSIX tooling itself doesn't really care about the UI framework in the first place. Have you tried using it with an Avalonia/WPF/WinForms app already, as a test? Did you get any errors in particular? Knowing that could be useful as a starting point 🙂
cc. @Scottj1s

Single project MSIX packaging works „out of the box“ for WinForms 🤯
I created a Blank App, Packaged (WinUI 3 in Desktop) and copied over the Assets folder, Properties folder including launchSettings.json and PublishProfiles and almost the entire project file to a Windows Forms project and it works in Visual Studio.
When I tested this before opening this issue I used only the online documentation for MAUI MSIX packaging and did not use samples from project templates which did not work. Looking forward I will test more frameworks and configurations:

[x] WinForms
[ ] WPF
[ ] Avalonia
[ ] CI/CD Integration

If everything works, I will close this issue and open issues at the respective docs repositories to inform developers about this amazing feature.

This aligns with what I was expecting, and it was one of the reasons why we decoupled the MSIX tooling in its own package 🙂
In theory you should be able to just add a package reference to it, set EnableMsixTooling, and that's it. Don't even need WinAppSDK.

@Sergio0694
Just to clarify, is this an official statement that this package is supported in arbitrary projects? If it is, where can we find the documentation, or if it doesn't exist yet, when can we expect the documentations?

It's not an official statement, no. Right now, the package is only officially supported for UWP, and it will be officially supported for WinUI 3 when WinAppSDK switches to it as well in a future release. I will see if we can add documentation to make this overall support official though. I'm just saying in the meantime, people can try it out on other frameworks (eg. WinForms, WPF), and it should work fine, in theory 🙂

You should be able to just add a package reference to it, set EnableMsixTooling, and that's it. Don't even need WinAppSDK.

That's right. I can build and deploy arbitrary projects as MSIX using Visual Studio's launch configuration.
However, I faced two problems:

Visual Studio's package and publish context menu works only when using Microsoft.WindowsAppSdk instead of Microsoft.Windows.SDK.BuildTools.MSIX. Setting HasPackageAndPublishMenu and <ProjectCapability Include="Msix" /> have no effect on that.
When I build for x86 the first time, I get an error (MSB4062) which disappears once I built for x64 which does not cause this error.
The "Microsoft.Build.Msix.Recipe.WinAppSdkMatchItemsByFileNameOnMetadataValue" task could not be loaded from the assembly C:\Users***.nuget\packages\microsoft.windows.sdk.buildtools.msix\1.1.20241024.1\build..\tools\net472\Microsoft.Build.Msix.dll.  Confirm that the  declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
I will try to reproduce this error within the next days.


fixes tests for Archlinux

I forked this repo for my own use and saw the tests were failing for Archlinux, so I thought I'd contribute to fix it.

Thanks a lot! Working on updating this role today. So this is great!


[Discussion] Cluster-aware graph logic

Historically, Dask has been execution-model agnostic when constructing graphs. This has had some notable advantages, since it means that dask task graphs/collections can be executed using any of a number of different schedulers. So the same graph can be computed using local schedulers, the distributed scheduler, and even third-party schedulers like Ray. It also enforces a certain amount of separation-of-concerns so that dask/dask and dask/distributed can be developed in a semi-independent fashion.
There is, however, some downside to this cluster-agnostic approach. Often there are specific tuning parameters and configuration options that significantly affect the performance of computations. Choosing good values for these parameters typically requires fairly advanced knowledge of Dask, its optimizations, and distributed systems in general. As developers, we would like to remove the onus from users to possess this information, but often cannot do that without knowledge of the cluster that they will be running it on.
One example of this that I ran into recently was with groupby/aggregations and the split_every parameter. It defaults to 8, but there are some easy-to-hit cases where that winds up being a very bad choice. And making a better choice requires knowing, at a minimum, the number of workers you will likely be using. This doesn't seem like an unreasonable ask for the task graph, but it's not easily available today.
Some tuning parameters which might benefit from having more context about the cluster:

chunks (array creation and rechunking)
split_every (array reductions)
merge_chunks (array reshaping)
split_every, split_out (dataframe reductions)
npartitions, broadcast (dataframe merges)
divisions, npartitions, partition_size (dataframe creation and repartitioning)
split_every (bag reductions)
dataframe.parquet.metadata-task-size-remote (parquet metadata processing)

There are some caveats to the above assertion that dask task graphs are cluster-unaware:

The default cluster implementation depends on whether there is an active distributed.Client. This usually does the right thing, but can cause problems if the graph is constructed before the client starts.
p2p shuffling does some out-of-task-graph work on the workers.

These are both interesting antecedents for reasoning about the execution environment, but it's not clear to me how reproducible they are in other contexts. From my perspective, I'd like to have something like the following:

A repeatable pattern for learning about a cluster during graph construction. Today, the default shuffle implementation goes through the dask config system, but I might want something a bit more formalized and thread-safe. It should also be able to be run on the scheduler: if we are delaying graph construction until an expression reaches the scheduler, we should be able to take advantage of more detailed information.
Possibly have an abstract HLG/HLE for repartitioning and rechunking. In particular, knowing some things about the number of workers and how much memory they have would help to avoid having too much or too little work-per-worker.

Some questions I don't have good answers to:

Even if we do have cluster information available during graph construction, can we write down good defaults for some of the tuning parameters? In some cases, maybe yes, in other cases, maybe no.
Is it possible all of the above is wildly overthinking things? Could a half-dozen blocks like the following do everything I want?try:
    import distributed
    info = distributed.get_default_client().scheduler_info()
    # Set some defaults based on the info.
except ImportError, ValueError:
    # Set some default defaults.

Is any of the above doable in the absence of HLG refactoring (cf discussion in #9159 and linked issues)? If the answer is no, I still think this is a valuable thing to think about when designing and implementing their replacement.

I think it makes a lot of sense to (optionally) allow the client/scheduler to use cluster information to choose how to build the graph. While working on https://github.com/dask/dask/issues/9216, I realized that the new HLG/Layer design could easily be used to label each individual task with a preferred worker. The only changes outside of HLG design would be:

We would need to allow the client to (optionally) check if there is an active distributed cluster, and to use that information to encode worker preferences in the Layer-materialization logic.
We would need a simple mechanism to annotate individual tasks with preferred workers, and we would need to add the scheduling logic to use the worker preference when assigning tasks.

With these two features in place, it would be relatively simple for appropriate worker preferences to be assigned as an HLG is materialized. For example, consider a simple HLG comprising 1+ Blockwise layers, followed by a groupby aggregation:

If feature (1) was available in Dask, the aggregation layer could use information about the expected worker set to specify graph-materialization parameters, like split_every. For example, if there are two workers in the detected cluster, split_every could be chosen so that the aggregation could be perfectly balanced between the two workers:

At graph-materialization time, a layer will be materialized within a method like Layer.subgraph(keys: Set, color: str | dict | None = None). Within the subgraph logic, the cluster-aware aggregation layer could (optionally) assign a worker color (or perhaps even a specific worker address) to each task it materializes (prioritizing the color specified in the function signature if it isn't None):

Since each layer will also be responsible for specifying which keys it wants from dependency layers (only after it has been materialized by a subgraph call), the returned key-dependency information can be organized by dependency color. This way, the preferred worker dependencies can propagate through the entire graph as it is materialized:

The final result is that (1) we are making better decisions about graph topology, and (2) are making it easier for the scheduler to properly co-locate distinct tasks on the same worker.  If done properly, I suppose this design could even make successful HLG-level fusion less critical.


Fix request error leak

I have added a 'timeout' event at RetrySend, and it is captured by the Agent that cleans up the request and avoids keeping a reference to a request that never will be completed

This is awesome! Can you add a unit test for this?

I've been trying to add a simple test and I'm unable to pass it. Disclaimer: I've never used mocha.
I've added this test right after 'should error after ~247 seconds' (test/request.js)
    it('should timeout after ~247 seconds', function(done) {
      var req = doReq()

      req.on('timeout', function(err) {
        expect(err).to.have.property('message', 'No reply in 247s')
        expect(err).to.have.property('retransmitTimeout', 247)
        done()
      })

      fastForward(1000, 247 * 1000)
    })

It fails. But what's worse, if at lib/retrySend.js I emit 'error' and 'timeout' in the reverse order (first 'timeout') the my test passes ... but all the ones that listen to 'error' fail !! I'm sure I'm missing something, but I have no clue ...

Ok, I figured out. It seems that mocha checks that all emitted events have been processed.
I've added a very simple test, but maybe it should be merged with the previous one.


Nord Aurora theme is not present

Hello,
Thanks for this wonderful color scheme. Would you kindly add the Aurora theme for alacritty?
There is a chance I am not getting this right. Is Aurora + Frost in the same file?
This is how my terminal looks right now

~ Have a good day.

Hi @Adyel :wave:, nice to see you like Nord 😄
This repository only provides the actual color codes that Alacritty than uses to colorize the output of commands. This theme provides all color palettes of Nord
Based on your screenshot I guess you're looking for a color theme for the ls or respectively exa which is documented on their website in detail. Since exa is inspired by and designed as replacement for ls you could simply use Nord dircolors to get a style that matches Nord's colorization design.
Please let me know if this answers your question or if I misunderstood your actual problem 😄

@arcticicestudio  Thank you very much. You did answer my question. I am sorry my question was not well articulated. You can close this now. 😄


Enable LNURL links

See https://github.com/rootzoll/raspiblitz/issues/3264

I think it makes sense to detect LNURL and maybe offer education on LNURL and what to Apps to use with them - but its fair that we dont support it with our basic dashboard wallet.


IGNITE-11647: ML Vectors should work with all Serializable objects besides double

@dmitrievanthony thanks for review
please, read my comments

The ticket is resolved, closing PR.
Please close PRs for your resolved tickets and other non-needed PRs.
Alternatively, ask a committer

to use GitHub UI (committer can associate accounts here: https://gitbox.apache.org/setup/ )
or /scripts/apply_pull_request.sh from Apache Ignite source.
or mention in commit message 'Fixes #(a number of PR)'.

These methods will automatically close PR.
Feel free to reopen this PR if it is actual.


Start a design doc for an ATIP backend + database

This is more like a set of questions we need to start exploring, rather than a design. Happy to try other formats for this (like Google Docs with comments), but I think it could be helpful to document the architectural decisions we make as the project evolves.
There are tons of questions raised, please comment!

I updated to use UK-agnostic terminology everywhere. In lieu of "ATE", I've defined "Central" -- more than happy to use another less awkward term here

Cleaning up old PRs+branches, so going to merge this for posterity. It links to this PR with all the comments, and states at the top that it's just a brainstorm / set of questions to think about


First step fails: gradle error

I have not been able to try out this project successfully. When I add the line "implementation("com.liftric:kvault:1.7.0")" to my apps build.gradle.kts I get a taskExecutionException. Any ideas to why the first step doesnt work?
This source of the error is:
Incompatible abi version. The current default is '1.4.2', found '1.5.0'. The library produced by 1.5.20 compiler?
I tried 1.5.30 as well, but the error remains.

I resolved this by updating kotlin to at least 1.5.30.


Question about IFEval on LeaderBoard

There are two metrics for IFEval, inst_level_strict_acc and prompt_level_strict_acc, but the leaderboard only shows one number, how to get that number based on these two metrics?

Hi! The number is the average of  Strict Accuracy at Instance and Prompt Levels (inst_level_strict_acc,none and prompt_level_strict_acc,none) as stated in this about page


BUG - Release 0.3.3a still has "Now Playing" player on top of Activity Section?

Client Mod
BetterDiscord
Description of bug
Hey.
So, on releases, there's version 0.1.3a and current version 0.3.3a.
Version 0.1.3a on Assets, has the .css file but 0.3.3a only has Source Code files.
So I went and grabbed the Source Code from 0.3.3a and got the css file from that zip file, thinking that the source code would have the fixed version.
However, on Discord this issue still persists.
Am I missing something or is the 0.3.3a release really missing the fixed css file?
Cheers man, awesome theme
Steps to reproduce

Download 0.3.3a Source Code file (or BetterDiscord SpotiDiscord
Apply the CSS file to BetterDiscord theme and enable it

Suspected cause
No response
Screenshots

This issue is unique

[X] I have searched the issue tracker and did not find an issue describing my bug.

This is an intentional design. Please scroll to access the voice controls.


Update release.yml

Make PRs without labels appear under "new features" (that's the most common case). Also cleaned up the config file according to the actual labels we have.

coverage: 72.076%. remained the same
when pulling c517b29d84a725e70ff092c7e6ef68500713a244 on masci-patch-1
into d7066e7457f782d26e9c1f74450d062310c97fe0 on main.


create new jsdelivr links

approval pending: https://github.com/jsdelivr/jsdelivr/pull/12754

Links have been created.  For more info check the docs https://base-apps.github.io/angular-base-apps/#!/installation


./eosio_uninstall.sh: line 5: ./scripts/helpers/eosio.sh: No such file or directory

On tags/v1.8.0, this is the output of running eosio_uninstall.sh from within the scripts folder. Works if you execute it from the parent root folder though. Looks like a hardcoded relative path to the scripts folder is the issue.

Similar to #7564.

Same thing for the install script as well.

me too,i did not find this script in the branch

Please run from the root directory for now until the next release


Implement jQuery version checking

Changes this pull request makes :
Implement jQuery version checking and get a list of the possible vulnerabilities
Checklist :

[X] I have added the relevant documentation.
[X] My branch is up-to-date with the upstream master branch.
[X] I have fully tested the changes locally.

Development environment
OS: Linux
Python Version: 3.4.6

Fixes #52

@nahuelhm17 Thanks for the PR! Looking forward to see more contribution from you :)

You're welcome. Take it for granted.


Manipulate the Garmin data

Is there any way to manipulate the Garmin data - e.g. put activities on the strength training session or fix the title of the individual training sessions?

Closing due to the age of this issue. If this is a still a valid query, please create a new issue.


image encode decode

Description
Script that encodes and decodes a given image
Image is converted to byte stream that is encoded by XOR-ing it with a randomly generated key. Which is stored into a text file
Only with that key, the  reverse process on the text file will occur to convert it into an image again
Fixed #74
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) 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] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added screenshots(if any) that prove my fix is effective or that my feature works

@all-contributors please add @namanshah01 for code, doc


"Doom + Doom II" re-release appears to have new versions of every WAD, plus some new ones

All these files are in the rerelease folder of that title. The doom, doom2, extras, masterlevels, nerve, plutonia, and tnt wads don't match any SHA-1 hashes in the repo, sigil doesn't match the version of it I already had and may also be a new version, and it includes the new files id1-res.wad, id1-weap.wad, id1.wad, id24res.wad, iddm1.wad, and Common.kpf (notable for containing a bunch of unused and previously-unreleased resources). (id24res.wad is of particular note because apparently it's required in order to implement the new id24 spec/complevel still in development?)
Here's all the hashes of the files I have:
[username@distro]:[steam library location]/SteamLibrary/steamapps/common/Ultimate Doom/rerelease$ sha1sum ./*.wad
c745f04a6abc2e6d2a2d52382f45500dd2a260be  ./doom2.wad
997bae5e5a190c5bb3b1fb9e7e3e75b2da88cb27  ./doom.wad
f83b2f84de582fe4ec4a4b2125507f9e48e4a151  ./extras.wad
6ec1646b348a8ca52a5a6ad386668127d87cff4b  ./id1-res.wad
6905630f20d512844f8c9692d021da4df243b978  ./id1.wad
b877cba17b5306f9201f672a77a1babb615d0480  ./id1-weap.wad
ff85c552e2335f81811f11141f80a4c7c904cea1  ./id24res.wad
cb7b39fe4083f8c9d327ac6e51bfcc7fb7cf07f9  ./iddm1.wad
47d5b10aee861791c9272ba4944e8eb1ea1e0819  ./masterlevels.wad
4522eaec7a13aac24b456e29520e99ac879e6989  ./nerve.wad
816c7c6b0098f66c299c9253f62bd908456efb63  ./plutonia.wad
89186ec316fe2ad7e065e685604230b60ee3bb29  ./sigil.wad
9820e2a3035f0cdd87f69a7d57c59a7a267c9409  ./tnt.wad
[username@distro]:[steam library location]/SteamLibrary/steamapps/common/Ultimate Doom/rerelease$ sha1sum ./Common.kpf
252ed3fc2ce8ed9cf937e9817f53217301d2575f  ./Common.kpf

For clarity, Common.kpf is just a zip file.

Resolved with #36. Thanks!

Thanks for the prompt fix!

With the latest update, all the wads except id24res, iddm1, nerve, and sigil changed:
michaelj@nobara-pc:~/Mount/Data2/SteamLibrary/steamapps/common/Ultimate Doom/rerelease$ sha1sum ./*.wad
2921cf667359fd3a80aba3c0cf62ab39297e7e9e  ./doom2.wad
87651324502044f9a6eed403e48853aa16c93e49  ./doom.wad
9c4fe2ae23b4c94c30cfb74f619ed1011fb8cda1  ./extras.wad
50bd7932c28c0d936de40529c2f13ca847855420  ./id1-res.wad
9848ba3d1726ce738811cef22ad55e2e6af4bbf4  ./id1.wad
2e4e975208a95202aef3000d44795315197747eb  ./id1-weap.wad
ff85c552e2335f81811f11141f80a4c7c904cea1  ./id24res.wad
cb7b39fe4083f8c9d327ac6e51bfcc7fb7cf07f9  ./iddm1.wad
32e7937fda52c4cecc8ddc75ddd41b5e0dfe6892  ./masterlevels.wad
4522eaec7a13aac24b456e29520e99ac879e6989  ./nerve.wad
fbcc140825b507ab88d844c6b1635c60c4b8bcd6  ./plutonia.wad
89186ec316fe2ad7e065e685604230b60ee3bb29  ./sigil.wad
ab4e71e360a1e64e262d77a53e4bb202450d0f6e  ./tnt.wad

Apologies, I should have checked first! All of these hashes are already in the project except extras, sigil, and the id wads.


Task Parallelism Detection: data sharing clause validation and simple alias detection

@aryamazaheri
Hi Arya,
Please take a look over our latest changes, especially the newly added script, whenever it suits your schedule.
If the scripts aren´t in the correct location, please let me know.
Thanks a lot!

@aryamazaheri
Hi Arya,
I have included the discussed changes.
However, two checks are failing while building. The same error occured on my local machine and could be fixed by installing "libclang-8-dev".
Please let me know how to proceed.
Best,
Lukas

@aandergr, Would you please help @lukasrothenberger to fix the CI issues?

However, two checks are failing while building. The same error occured on my local machine and could be fixed by installing "libclang-8-dev".

This fix also worked in the CI workflow :)

@aandergr
Great, thank you very much!

@aryamazaheri
Hi Arya,
could you please have another look over the changes?
Thanks a lot!


Ender io says its needed the specific version while on both end has the same version "See Comment"

Ender io seems to not want to verify version deleted for now


Meet an open() failure when running a reactor .wasm

Like mentioned in https://github.com/bytecodealliance/wasm-micro-runtime/issues/1771. When running a .wasm in reactor, open() will fail with an error code 76 which information is Capabilities insufficient.

There are two root causes for different scenarios:

Doesn't execute _initialize if run a reactor .wasm only. Regardless WASM_ENABLE_MULTI_MODULE.

https://github.com/bytecodealliance/wasm-micro-runtime/blob/97d2b5a06082ad60f816c056d7aefb6f5ffcdc37/core/iwasm/interpreter/wasm_runtime.c#L1187-L1193
Only call the entry function on dependencies of a commander .wasm. But there is no restriction to prevent running a reactor .wasm only.

Call _initialize and _start before prepare preopens in WASIContext.

https://github.com/bytecodealliance/wasm-micro-runtime/blob/97d2b5a06082ad60f816c056d7aefb6f5ffcdc37/core/iwasm/interpreter/wasm_runtime.c#L1347
executes
https://github.com/bytecodealliance/wasm-micro-runtime/blob/97d2b5a06082ad60f816c056d7aefb6f5ffcdc37/core/iwasm/interpreter/wasm_runtime.c#L1461
and
https://github.com/bytecodealliance/wasm-micro-runtime/blob/97d2b5a06082ad60f816c056d7aefb6f5ffcdc37/core/iwasm/interpreter/wasm_runtime.c#L1814
in a wrong order. Because wasm_call_ctors needs preopen information which set-up in WASIContext.

https://github.com/bytecodealliance/wasm-micro-runtime/pull/1816