fix for #1270

fixes #1270

Note locally i get an exception during gradlew build about checkstyle, not sure if it's related to my changes ?
Caused by: java.io.FileNotFoundException: /home/heymjo/.gradle/daemon/5.6.2/src/checkstyle/checkstyle-suppressions.xml (No such file or directory)
        at java.xml/com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:654)
        at java.xml/com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:150)
        at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:860)
        at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:824)

@artembilan tests are failing now because in some test scenario's DefaultKafkaProducerFactory is not used as a Spring bean. Is this a valid usage scenario ? If yes then i should undo moving the logic to afterPropertiesSet

Well, It is OK to call that afterPropertiesSet() from tests, but we might need to consider to revise your logic and do only an info in the  afterPropertiesSet(). I would leave an initialization from ctor as is, but would have an extra transactionIdPrefixExplicitlySet boolean flag populated from that setTransactionIdPrefix(). This one would be an indication for us to info or not in the   afterPropertiesSet(). And the last one won't be required from the tests.

Not sure what is going on with Checkstyle on your side, but it works well for us on Mac, Windows locally and on Linux in Travis and Bamboo.

checkstyle error was due to missing newline, that is fixed now.

I would leave an initialization from ctor as is, but would have an extra transactionIdPrefixExplicitlySet boolean flag populated from that setTransactionIdPrefix(). This one would be an indication for us to info or not in the afterPropertiesSet(). And the last one won't be required from the tests.

Not sure i understand, can this class be an InitializingBean or not, meaning is the use case where DefaultKafkaProducerFactory is not a spring bean valid ?

No, that use-case is really not valid. Excluding our unit-tests, of course.
See DefaultKafkaProducerFactory contract:
public class DefaultKafkaProducerFactory<K, V> implements ProducerFactory<K, V>, ApplicationContextAware,
		ApplicationListener<ContextStoppedEvent>, DisposableBean {

So, it expects ApplicationContext, a ContextStoppedEvent even and it also does already something in the destroy() callback.
Therefore I didn't expect any problems with introducing an afterPropertiesSet().
But if our tests doesn't initialize it properly, it doesn't mean that we need to go through the whole project and fix those tests to really present this DefaultKafkaProducerFactory as a bean.
Saying that I mean that let's try find a middle ground here!
Let's consider some logic with an additional internal transactionIdPrefixExplicitlySet flag to check in the mentioned afterPropertiesSet()! This way we won't need to change tests since that new callback is going to have only INFO logging logic.
And also we need to keep in mind a backward compatibility. We can't have guarantees that everybody uses it as a bean. Such a new afterPropertiesSet() with moved logic over there will break their apps.
So, while I agree with you about a robust solution, it would be better to do something what would fit your original requirements and won't break anyone else.
Does it make sense?

see #1286


Your request to provision "Microsoft 365 learning pathways"  template failed!

Here's the requested correlation ID: 21fe9d36-539e-401e-8766-2fb0056ec4a4 for the failed attempt.
Interesting scenario.  I was able to provision the LP site through the service, but there were web part errors presumably from not have the proper tenant admin permissions.  I am not a tenant admin, but I have the SharePoint admin role.  I deleted (and permanently deleted) this LP site from the SharePoint Admin center.  The tenant admin went to provision the LP site and this attempt failed with the above correlation ID.

Removed the old site collection and apps by emptying second stage recycle bin.


Decision tree based function specialization

This would speed up typechecking and would be a cool data structure.

I think the general datastructure would be a tree of clauses.


Subtraction of mean on images that have white background

If I subtract the fixed mean (104,117,123) from the image, I get a much worse result on images that have a white background.
Is it better to subtract the actual mean of the image being tested?

Empirically, we subtract the fixed mean (104,117,123) during training and testing should be consistent with this. It is strange that on images that have white background, subtracting the actual mean has better results than subtracting the fixed mean. Is this an individual case or a general phenomenon?

It appears to be in general, images that have the face only and a blank colour background perform worse with the trained mean.
I found a suitable improvement is averaging the trained mean with the real mean and subtracting this instead. This improves results on all images I clueing the tests.

@xsacha
Nice. Does this suitable for other images?

Yes, I'm using this for all images:
    static torch::Tensor mean = torch::tensor({104.0f, 117.0f, 123.0f});
    auto imMean = tensorImage.view({-1, 3}).mean(0);
    tensorImage.sub_(torch::mean(torch::stack({imMean, mean})));

Basically averages the trained mean and the image mean and then subtracts that from the image.

@xsacha
Interesting operation. What is its improvement on AFW, PASCAL, FDDB?

Quite small, about 0.15%. Didn't test FDDB.
It makes a much bigger difference on plain colour background images though.

@xsacha
Ok. Got it. Thank you.

I retrained the model from my best checkpoint and found an improvement when using only the image mean rather than the fixed mean.
-        image_t = _pad_to_square(image_t,self.rgb_means, pad_image_flag)
+        mean = cv2.mean(image_t)[:3]
+        image_t = _pad_to_square(image_t, mean, pad_image_flag)
         image_t, boxes_t = _mirror(image_t, boxes_t)
         height, width, _ = image_t.shape
-        image_t = _resize_subtract_mean(image_t, self.img_dim, self.rgb_means)
+        image_t = _resize_subtract_mean(image_t, self.img_dim, mean)

I got a new high accuracy with unmodified model (only pooling change) in AFW (99.12% AP, 99.98% precision @ 94% recall) and PASCAL (98.47% AP) as well as improvements for single colour background images.
The fixed mean you are using is from FG-Net I think? Any reason it is trained against it rather than image mean?

@xsacha
We follow SSD and Faster RCNN to subtract the fixed mean.
Subtraction of image mean seems to be a better choice for slightly higher performance while subtraction the fixed mean is simpler and doesn't require extra calculations.


autoUpdater: How to use GithubUpdateManager?

Electron version: 0.36.7
Operating system: Windows 10 x64

Is there a way to use the GithubUpdateManager? I can't find any documentation here about that.

No, the autoUpdater in Electron relies on the command line interface of Squirrel, while GithubUpdateManager only provides programming interface in C#.

No, the autoUpdater in Electron relies on the command line interface of Squirrel, while GithubUpdateManager only provides programming interface in C#.

OK. thanks for the clarification. Any plans to add it?

It would need a command line interface in Squirrel.Windows first, and we probably need to add the same thing in Squirrel.Mac too. We don't have a plan to add it, but I will accept PRs adding that.


fixed hf convert and now it's working with tinyllama

Fixed huggingface convert

I've compared the outputs with the transformers code:
from transformers import LlamaForCausalLM, LlamaTokenizer

model = LlamaForCausalLM.from_pretrained("tinyllama_503b", local_files_only=True)
tokenizer = LlamaTokenizer.from_pretrained("tinyllama_503b/tokenizer.model")
prompt = "Where do you live?"
inputs = tokenizer(prompt, return_tensors="pt")
generate_ids = model.generate(inputs.input_ids, max_length=30)
print(tokenizer.batch_decode(generate_ids, skip_special_tokens=True, clean_up_tokenization_spaces=False)[0])

Here is the transformers output:
The 2018-19 season is the 10th season for the club and the

And here is the output from tinygrad:
python llama.py --gen=tiny --model tinyllama_503b/model.safetensors --size 1B --temperature 0 --count 30 --prompt "Where do you live?"

The 2018-19 season is the 10th season for the club and the 10th season in the

I used the config from https://github.com/tinygrad/tinygrad/issues/2228

Can it auto fetch the weights if they aren't there?

@geohot @chenyuxyz I've added default size evaluation based on model gen and added code for dynamically updating help for easier development in the future. I suggest we add model fetch in separate PR, what do you think?

Tested and merged<EMAIL_ADDRESS>to claim the bounty, either USDC or PayPal.


Make tensor eval parameterised

When we create a tensor.Box, it forgets the dtype, e.g.
>> b1 = tensor.Box('sauce_0', Dim(1), Dim(2), data=array([0.84193562, 0.91343221]))
>> print(b1.eval())
Tensor[int]([0, 0], dom=Dim(1), cod=Dim(2))

@boldar99 any updates on this one? Now I can't remember what was blocking us.

So the problem was related to isinstance, but I also can't exactly remember it.
If I'm correct, something like isintance(Tensor(1), Tensor[int]) wouldn't be True because it'd be isintance(Tensor(1), Tensor)


Will you upload the training loop

Hi,
Will you upload the training loop to the project ?
Thanks a lot

Could the author share the training code?
I'm interested, too.


Antd 4.0 introduced new components, but there is a warning in the console due to the unconfigured unplugin-auto-import plugin.

Describe the bug
Antd 4.0 introduced new components, but there is a warning in the console due to the unconfigured unplugin-auto-import plugin

Reproduction
If Antd 4.0 beta version and the unplugin-auto-import plugin are used in the project, there will be an issue when importing the Segmented component
System Info
System:
    OS: Windows 10 10.0.22621
  Browsers:
    Edge: Spartan (44.22621.1555.0), Chromium (112.0.1722.68)
    Internet Explorer: 11.0.22621.1

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

need reproduction

We temporarily close this due to the lack of enough information.
Please provide a minimal reproduction to reopen the issue.
Thanks.

Why reproduction is required


Monsterhearts 2: Roll Results Cut Off In Chat

Hi!
I am a new DM and was setting up my game space for my first session. I was doing some practice rolls to test and all of them are cut off. I am not sure what the issue is or how to fix it. Here is what they look like in the chat:

Adjusting the chat size does not solve the issue.
Thanks!

I did not do this part of the character sheet. Someone modified my code
then left me as the only contact and I don't know them at all. I also don't
currently have the time to work on this sheet. Sorry.
-Allie Bustion
http://madpierrot.tumblr.com
http://alliebustion.com
On Sat, Sep 5, 2020 at 10:15 PM SailorTrivia<EMAIL_ADDRESS>wrote:

Hi!
I am a new DM and was setting up my game space for my first session. I was
doing some practice rolls to test and all of them are cut off. I am not
sure what the issue is or how to fix it. Here is what they look like in the
chat:
[image: image]
https://user-images.githubusercontent.com/70829196/92317344-8d872580-efcd-11ea-8663-65ca726e6574.png
Adjusting the chat size does not solve the issue.
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lemadpierrot/roll20-character-sheets/issues/1, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADTWYTEWDRL5QR7OS6WYYLDSEL5E7ANCNFSM4Q3YMLMQ
.


trt-llm integration

What does this PR do ?
added trt-llm integration. the nemo path is mostly unaffected

fixed a bug I caught while running e2e:
f96cb883e48d195121e82157672f76ae8500e123
it turns out torch masked tensor doesn't support dim is None, probably a bug on their side

tests look good! so i'm merging now


Add Linux support to the project

Hi Cherno,

added support for Linux to the premake5.lua file
changed the "Hazel/Hazel/src/Hazel/Events/Event.h" to fix gcc compile error:
src/Hazel/Events/Event.h:32:83: error: pasting "::" and "WindowResize" does not give a valid preprocessing token
#define EVENT_CLASS_TYPE(type) static EventType GetStaticType() { return EventType::##type; }
changed files: "Hazel/src/Hazel/Core.h" and "Hazel/src/Hazel/EntryPoint.h" to add support for Linux

Thanks.
Marian

Can you please update this branch and make sure it's ready to merge? I'd be keen to merge this in. 🙂

I updated this PR on https://github.com/TheCherno/Hazel/pull/27

As this PR is already updated on #27 , perhaps this one should be closed as it is obsolete, right?

On Manjaro 18.0.3, I am getting an error after running premake5 gmake and make:
==== Building GLFW (debug) ====
==== Building Glad (debug) ====
==== Building ImGui (debug) ====
==== Building Hazel (debug) ====
Linking Hazel
/usr/bin/ld: vendor/imgui/bin/Debug-linux-x86_64/ImGui/libImGui.a(imgui.o): relocation R_X86_64_PC32 against symbol `GImGui' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:121: ../bin/Debug-linux-x86_64/Hazel/libHazel.so] Error 1
make: *** [Makefile:62: Hazel] Error 2

@ritobanrc this is already fixed on PR #27 (I myself use manjar too, so it should work for you aswell)

I cloned the latest marian-bielcik/Hazel branch and found it works with a minor modification.
I cloned the project.
git clone https://github.com/marian-bielcik/Hazel.git marian-test
cd marian-test

Modified ./Hazel/vendor/imgui/premake5.lua by appending:
    filter "system:linux"
	pic "on"

Ran premake with make.
premake5 gmake
make

And Sandbox compiled properly!
It was cubedtear's branch that worked for me a few months ago. I contributed a little documentation to his branch too. I attempted to rebase cubetear's branch from TheCherno's latest work but I found myself stuck after making some modifications. Now I'm wondering what the differences are between the @cubedtear and @marian-bielcik branches.

Closing since this has been moved to #27

This branch looks to be the most promising Pull Request for Linux support! The latest repository is 3 commits behind. A proper repository clone compiles and runs fine on my system. The submodule links need to be changed to point back to TheCherno's repositories.


SOAP Client

Hi guys, thanks for creating this package. It makes things much easier and elegant.
I'm creating a soap client and at the moment I'm passing a raw xml to the data option as follows.
data: `
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://servicio.interoperadorws.interoperacion.dinardap.gob.ec/">
      <soapenv:Header/>
      <soapenv:Body>
          <ser:getFichaGeneral>
            <!--Optional:-->
            <codigoPaquete>622</codigoPaquete>
            <!--Optional:-->
            <numeroIdentificacion>1718896580</numeroIdentificacion>
          </ser:getFichaGeneral>
      </soapenv:Body>
    </soapenv:Envelope>
  `

So I'm wondering if there is a way to send the soap action/method and the arguments as an object similar to the one below?, I'm just trying to avoid the raw xml syntax
data: {
  soap {
    action: 'getFichaGeneral',
    args: {
      codigoPaquete: 622,
      numeroIdentificacion: '1718896580'
    }
  }
}

This project seems inactive from last 2 years. But you can have a look on https://www.npmjs.com/package/restler-base


CUDA version dependency

Hello @aqeelanwar , I am using  Nvidia rtx 3090 ti and cuda version 11.2 . Is there any dependencies on cuda version?

Hi, did you solve the bug? I am having the same problem.


support gbk

Using Chinese word, an exception appears, likes:
UnicodeDecodeError: 'gbk' codec can't decode byte 0xad in position 145: illegal multibyte sequence

In newest version v0.2.7, the fix has been patched. Sorry for the waiting!


[fix] Fixed commit message check missing close/fix keyword #136

Added failing test + fix.
Expecting build to fail, I sent a commit message which should trigger the failure on purpose to ensure it works.

Coverage increased (+0.0007%) to 99.735% when pulling 0a45d23452a3abb09a1181a4e2817292616eb63a on issue-136-fix-commit-check into ca385c577d7b3427186c2e287398ccf30254b902 on master.


update next pages:dev script

This is not a proper solution at all, but soon the pages:dev script should be replaced with a pages:preview one and for local development developers should just use the standard dev command (as per the recommended workflow), so I am not sure if we should invest more time in trying to make pages:dev better now or add this simple stopgap until we're ready finalize next-dev

After chatting with @jculvey we thought that might be worth it to just hold off on this and just implement a proper solution as soon as we can instead of adding a stopgap here


How Can I use it?

Hi,thanks your code.I have finished the trainning. And how can I use the model to predict Visualization about 3D bounding box   ?

@Ben940315 Have you solved this problem of visualization 3D bounding box?

Yeah, The code should be debuged.  The some space key is wrong.


US1 - Viewing Content

User would like to watch the site's contents which include job offers, newsletters, events etc

Adding links that will help to navigate in the site.


No staged files match any configured task.

I don't know what to do
Who can help me

I found that the path matching gave unexpected results.
ie this would not match anything (angular app):
"lint-staged": {
    "src/**/*.{ts,html}": [

if I changed it to just the file, it works:
    "*.{ts,html}": [

In the first example, I did verify what the working directory was and if the specified path existed (which it did), but I could not get it to work.

@wadefleming-nz please post debug logs of the incorrect behaviour.

same result when using husky@v8
the scripts mentioned in lint-staged are not running.

Please open separate issues along with debug logs, otherwise we can't really help.


only download the required files

only download the required files for the job, added filter on the download artifacts task
This PR fixes #9373

I'm not sure what you mean, we need to depend on the windows build since that's the build that produces the windows binaries. Ideally we would run everything, including tests, on the hosted machines, but we can't atm, so we build everything on the hosted machines then test on ours.
We depend on the linux build since thats were we build our extensions. And since we are already depending on the windows build, it doesn't have any impact to also depend on the linux build for extensions.

the test build passed, and it is only downloading the required files now.


Fix failing tests for type2/hermez branch

The following tests (121 in total) from the Ethereum test suite are currently failing on type2/hermez branch (on plonky2 side), as of commit be7c9a84e07ba00521e12901d66737fbfa6eef11:

[ ] ABAcallsSuicide0_d0g0v0_Shanghai
[ ] CREATE_AcreateB_BSuicide_BStore_d0g0v0_Shanghai
[ ] Create2OOGFromCallRefunds_d12g0v0_Shanghai
[ ] CreateOOGFromCallRefunds_d12g0v0_Shanghai
[ ] CreateOOGFromEOARefunds_d12g0v0_Shanghai
[ ] InitCollisionParis_d0g0v0_Shanghai
[ ] InitCollisionParis_d1g0v0_Shanghai
[ ] InitCollisionParis_d2g0v0_Shanghai
[ ] InitCollisionParis_d3g0v0_Shanghai
[ ] NonZeroValue_SUICIDE_ToOneStorageKey_Paris_d0g0v0_Shanghai
[ ] RevertInCreateInInitCreate2Paris_d0g0v0_Shanghai
[ ] RevertInCreateInInit_Paris_d0g0v0_Shanghai
[ ] ZeroValue_SUICIDE_ToOneStorageKey_Paris_d0g0v0_Shanghai
[ ] callToSuicideThenExtcodehash_d0g0v0_Shanghai
[ ] callToSuicideThenExtcodehash_d1g0v0_Shanghai
[ ] callToSuicideThenExtcodehash_d2g0v0_Shanghai
[ ] callToSuicideThenExtcodehash_d3g0v0_Shanghai
[ ] callcall_00_SuicideEnd_d0g0v0_Shanghai
[ ] callcallcall_000_SuicideEnd_d0g0v0_Shanghai
[ ] callcallcallcode_001_SuicideEnd_d0g0v0_Shanghai
[ ] callcallcode_01_SuicideEnd_d0g0v0_Shanghai
[ ] callcallcodecall_010_SuicideEnd_d0g0v0_Shanghai
[ ] callcallcodecall_010_SuicideMiddle_d0g0v0_Shanghai
[ ] callcallcodecallcode_011_SuicideEnd_d0g0v0_Shanghai
[ ] callcallcodecallcode_011_SuicideMiddle_d0g0v0_Shanghai
[ ] callcodecall_10_SuicideEnd_d0g0v0_Shanghai
[ ] callcodecallcall_100_SuicideEnd_d0g0v0_Shanghai
[ ] callcodecallcallcode_101_SuicideEnd_d0g0v0_Shanghai
[ ] callcodecallcode_11_SuicideEnd_d0g0v0_Shanghai
[ ] callcodecallcodecall_110_SuicideEnd_d0g0v0_Shanghai
[ ] callcodecallcodecall_110_SuicideMiddle_d0g0v0_Shanghai
[ ] callcodecallcodecallcode_111_SuicideEnd_d0g0v0_Shanghai
[ ] callcodecallcodecallcode_111_SuicideMiddle_d0g0v0_Shanghai
[ ] codeCopyZero_Paris_d0g0v0_Shanghai
[ ] create2collisionStorageParis_d0g0v0_Shanghai
[ ] create2collisionStorageParis_d1g0v0_Shanghai
[ ] create2collisionStorageParis_d2g0v0_Shanghai
[ ] createEmptyThenExtcodehash_d0g0v0_Shanghai
[ ] createLargeResult_d0g0v0_Shanghai
[ ] createLargeResult_d1g0v0_Shanghai
[ ] createLargeResult_d4g0v0_Shanghai
[ ] createLargeResult_d5g0v0_Shanghai
[ ] doubleSelfdestructTouch_Paris_d0g0v0_Shanghai
[ ] doubleSelfdestructTouch_Paris_d0g0v1_Shanghai
[ ] doubleSelfdestructTouch_Paris_d0g0v2_Shanghai
[ ] dynamicAccountOverwriteEmpty_Paris_d0g0v0_Shanghai
[ ] eoaEmptyParis_d0g0v0_Shanghai
[ ] eoaEmptyParis_d0g1v0_Shanghai
[ ] eoaEmptyParis_d0g1v1_Shanghai
[ ] eoaEmptyParis_d1g0v0_Shanghai
[ ] eoaEmptyParis_d1g1v0_Shanghai
[ ] eoaEmptyParis_d1g1v1_Shanghai
[ ] extCodeHashAccountWithoutCode_d0g0v0_Shanghai
[ ] extCodeHashCALLCODE_d0g0v0_Shanghai
[ ] extCodeHashCALL_d0g0v0_Shanghai
[ ] extCodeHashChangedAccount_d0g0v0_Shanghai
[ ] extCodeHashCreatedAndDeletedAccountCall_d0g0v0_Shanghai
[ ] extCodeHashCreatedAndDeletedAccountRecheckInOuterCall_d0g0v0_Shanghai
[ ] extCodeHashCreatedAndDeletedAccountStaticCall_d0g0v0_Shanghai
[ ] extCodeHashCreatedAndDeletedAccount_d0g0v0_Shanghai
[ ] extCodeHashDELEGATECALL_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount1Cancun_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount1_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount2Cancun_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount2_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount3_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount4_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccountCancun_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount_d0g0v0_Shanghai
[ ] extCodeHashDynamicArgument_d1g0v0_Shanghai
[ ] extCodeHashDynamicArgument_d2g0v0_Shanghai
[ ] extCodeHashDynamicArgument_d3g0v0_Shanghai
[ ] extCodeHashInInitCode_d0g0v0_Shanghai
[ ] extCodeHashInInitCode_d1g0v0_Shanghai
[ ] extCodeHashMaxCodeSize_d0g0v0_Shanghai
[ ] extCodeHashNewAccount_d0g0v0_Shanghai
[ ] extCodeHashPrecompiles_d0g0v0_Shanghai
[ ] extCodeHashSTATICCALL_d0g0v0_Shanghai
[ ] extCodeHashSelfInInit_d0g0v0_Shanghai
[ ] extCodeHashSelf_d0g0v0_Shanghai
[ ] extCodeHashSubcallOOG_d0g0v0_Shanghai
[ ] extCodeHashSubcallOOG_d1g0v0_Shanghai
[ ] extCodeHashSubcallOOG_d2g0v0_Shanghai
[ ] extCodeHashSubcallSuicideCancun_d0g0v0_Shanghai
[ ] extCodeHashSubcallSuicide_d0g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d0g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d1g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d2g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d3g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d4g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d5g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d6g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d7g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d8g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d9g0v0_Shanghai
[ ] invalidAddr_d30g0v0_Shanghai
[ ] invalidAddr_d32g0v0_Shanghai
[ ] invalidAddr_d34g0v0_Shanghai
[ ] invalidAddr_d36g0v0_Shanghai
[ ] invalidAddr_d38g0v0_Shanghai
[ ] refund_CallToSuicideStorage_d1g0v0_Shanghai
[ ] refund_CallToSuicideTwice_d1g0v0_Shanghai
[ ] refund_TxToSuicide_d0g0v0_Shanghai
[ ] static_callcodecall_10_SuicideEnd2_d0g0v0_Shanghai
[ ] static_callcodecall_10_SuicideEnd2_d0g0v1_Shanghai
[ ] static_callcodecall_10_SuicideEnd_d0g0v0_Shanghai
[ ] static_callcodecall_10_SuicideEnd_d1g0v0_Shanghai
[ ] static_callcodecallcodecall_110_SuicideEnd2_d0g0v0_Shanghai
[ ] static_callcodecallcodecall_110_SuicideEnd2_d0g0v1_Shanghai
[ ] static_callcodecallcodecall_110_SuicideEnd_d0g0v0_Shanghai
[ ] static_callcodecallcodecall_110_SuicideEnd_d0g0v1_Shanghai
[ ] static_callcodecallcodecall_110_SuicideMiddle2_d0g0v0_Shanghai
[ ] static_callcodecallcodecall_110_SuicideMiddle_d0g0v0_Shanghai
[ ] static_refund_CallToSuicideTwice_d1g0v0_Shanghai
[ ] suicideAddress_d0g0v0_Shanghai
[ ] suicideCallerAddresTooBigLeft_d0g0v0_Shanghai
[ ] suicideCallerAddresTooBigRight_d0g0v0_Shanghai
[ ] suicideCaller_d0g0v0_Shanghai
[ ] suicideOrigin_d0g0v0_Shanghai
[ ] walletKillToWallet_d0g0v0_Shanghai
[ ] walletKill_d0g0v0_Shanghai

I've identified 3 causes for the failing tests:

Call to SELFDESTRUCT: As mentioned previously, the current implementation of SELFDESTRUCT is buggy. It can be fixed with the new behavior coming in Cancun.
Some tests store the result of a call to EXTCODEHASH: In the Hermez type2, EXTCODEHASH returns the Poseidon hash of the code, not the Keccak hash. This lead to discrepancies in the expected post-tx state trie.
Some tests are of the form:

There is some account A with nonce 0 and non-empty storage.
Do a contract creation tx that creates a new account colliding with A.
This should clear the storage of A.

Since it's not possible to clear the storage of an account with this SMT design, the test fails. I think we can just discard such tests since in practice it's impossible to have accounts with nonce=0 and non-empty storage.
All the tests listed above fail for one of these 3 reasons.

since in practice it's impossible to have accounts with nonce=0 and non-empty storage.

Wasn't this already removed upstream? I thought they had mentioned getting rid of such tests (like InitCollision).

Wasn't this already removed upstream? I thought they had mentioned getting rid of such tests (like InitCollision).

It's not exactly the same situation as in InitCollision as the accounts are not empty (they have non-zero balance). But yeah we can just filter these tests out.

Call to SELFDESTRUCT: As mentioned previously, the current implementation of SELFDESTRUCT is buggy. It can be fixed with the new behavior coming in Cancun.

So does this mean you need to rebase on top of the feat/type2 branch? So we could say we're blocked on type2 being complete?

We have more tests failing than before when running against the Ethereum test suite (234), but the latest changes on the parser side added more tests to the list, so these may be false positives, triggered by one of the reasons William mentioned above.
Sharing them all anyway in case we do have a regression (would need to investigate more closely at some point):

[ ] ABAcallsSuicide0_d0g0v0_Shanghai
[ ] CALL_OneVCallSuicide2_d0g0v0_Shanghai
[ ] CALL_OneVCallSuicide_d0g0v0_Shanghai
[ ] CALL_ZeroVCallSuicide_d0g0v0_Shanghai
[ ] CREATE2_ContractSuicideDuringInit_ThenStoreThenReturn_d0g0v0_Shanghai
[ ] CREATE2_Suicide_d2g0v0_Shanghai
[ ] CREATE2_Suicide_d3g0v0_Shanghai
[ ] CREATE2_Suicide_d6g0v0_Shanghai
[ ] CREATE2_Suicide_d7g0v0_Shanghai
[ ] Create2OOGFromCallRefunds_d12g0v0_Shanghai
[ ] CreateOOGFromCallRefunds_d12g0v0_Shanghai
[ ] CreateOOGFromEOARefunds_d12g0v0_Shanghai
[ ] InitCollisionParis_d0g0v0_Shanghai
[ ] InitCollisionParis_d1g0v0_Shanghai
[ ] InitCollisionParis_d2g0v0_Shanghai
[ ] InitCollisionParis_d3g0v0_Shanghai
[ ] NonZeroValue_SUICIDE_ToEmpty_Paris_d0g0v0_Shanghai
[ ] NonZeroValue_SUICIDE_ToNonNonZeroBalance_d0g0v0_Shanghai
[ ] NonZeroValue_SUICIDE_ToOneStorageKey_Paris_d0g0v0_Shanghai
[ ] NonZeroValue_SUICIDE_d0g0v0_Shanghai
[ ] SelfDestruct_d0g0v0_Shanghai
[ ] SelfDestruct_d1g0v0_Shanghai
[ ] SelfDestruct_d2g0v0_Shanghai
[ ] SuicideToExistingContract_d0g0v0_Shanghai
[ ] SuicideToNotExistingContract_d0g0v0_Shanghai
[ ] SuicidesAndInternlCallSuicidesBonusGasAtCallFailed_d0g0v0_Shanghai
[ ] SuicidesAndInternlCallSuicidesBonusGasAtCall_d0g0v0_Shanghai
[ ] SuicidesAndInternlCallSuicidesSuccess_d0g0v0_Shanghai
[ ] SuicidesAndInternlCallSuicidesSuccess_d1g0v0_Shanghai
[ ] SuicidesAndSendMoneyToItselfEtherDestroyed_d0g0v0_Shanghai
[ ] SuicidesStopAfterSuicide_d0g0v0_Shanghai
[ ] TouchToEmptyAccountRevert3_Paris_d0g0v0_Shanghai
[ ] ZeroValue_SUICIDE_ToEmpty_Paris_d0g0v0_Shanghai
[ ] ZeroValue_SUICIDE_ToNonZeroBalance_d0g0v0_Shanghai
[ ] ZeroValue_SUICIDE_ToOneStorageKey_Paris_d0g0v0_Shanghai
[ ] ZeroValue_SUICIDE_d0g0v0_Shanghai
[ ] baseFeeDiffPlaces_d23g0v0_Shanghai
[ ] callToSuicideThenExtcodehash_d0g0v0_Shanghai
[ ] callToSuicideThenExtcodehash_d1g0v0_Shanghai
[ ] callToSuicideThenExtcodehash_d2g0v0_Shanghai
[ ] callToSuicideThenExtcodehash_d3g0v0_Shanghai
[ ] callcall_00_SuicideEnd_d0g0v0_Shanghai
[ ] callcallcall_000_SuicideEnd_d0g0v0_Shanghai
[ ] callcallcall_000_SuicideMiddle_d0g0v0_Shanghai
[ ] callcallcallcode_001_SuicideEnd_d0g0v0_Shanghai
[ ] callcallcallcode_001_SuicideMiddle_d0g0v0_Shanghai
[ ] callcallcode_01_SuicideEnd_d0g0v0_Shanghai
[ ] callcallcodecall_010_SuicideEnd_d0g0v0_Shanghai
[ ] callcallcodecall_010_SuicideMiddle_d0g0v0_Shanghai
[ ] callcallcodecallcode_011_SuicideEnd_d0g0v0_Shanghai
[ ] callcallcodecallcode_011_SuicideMiddle_d0g0v0_Shanghai
[ ] callcodecall_10_SuicideEnd_d0g0v0_Shanghai
[ ] callcodecallcall_100_SuicideEnd_d0g0v0_Shanghai
[ ] callcodecallcall_100_SuicideMiddle_d0g0v0_Shanghai
[ ] callcodecallcallcode_101_SuicideEnd_d0g0v0_Shanghai
[ ] callcodecallcallcode_101_SuicideMiddle_d0g0v0_Shanghai
[ ] callcodecallcode_11_SuicideEnd_d0g0v0_Shanghai
[ ] callcodecallcodecall_110_SuicideEnd_d0g0v0_Shanghai
[ ] callcodecallcodecall_110_SuicideMiddle_d0g0v0_Shanghai
[ ] callcodecallcodecallcode_111_SuicideEnd_d0g0v0_Shanghai
[ ] callcodecallcodecallcode_111_SuicideMiddle_d0g0v0_Shanghai
[ ] codeCopyZero_Paris_d0g0v0_Shanghai
[ ] create2InitCodes_d6g0v0_Shanghai
[ ] create2collisionSelfdestructed2_d0g0v0_Shanghai
[ ] create2collisionSelfdestructed2_d1g0v0_Shanghai
[ ] create2collisionSelfdestructed_d0g0v0_Shanghai
[ ] create2collisionSelfdestructed_d1g0v0_Shanghai
[ ] create2collisionSelfdestructed_d2g0v0_Shanghai
[ ] create2collisionStorageParis_d0g0v0_Shanghai
[ ] create2collisionStorageParis_d1g0v0_Shanghai
[ ] create2collisionStorageParis_d2g0v0_Shanghai
[ ] createEmptyThenExtcodehash_d0g0v0_Shanghai
[ ] createFailBalanceTooLow_d0g0v0_Shanghai
[ ] createFailBalanceTooLow_d0g0v1_Shanghai
[ ] createInitFailBadJumpDestination2_d0g0v0_Shanghai
[ ] createInitFailBadJumpDestination_d0g0v0_Shanghai
[ ] createInitFailStackSizeLargerThan1024_d0g0v0_Shanghai
[ ] createInitFailStackUnderflow_d0g0v0_Shanghai
[ ] createInitFailUndefinedInstruction2_d0g0v0_Shanghai
[ ] createInitOOGforCREATE_d0g1v0_Shanghai
[ ] createLargeResult_d0g0v0_Shanghai
[ ] createLargeResult_d1g0v0_Shanghai
[ ] createLargeResult_d4g0v0_Shanghai
[ ] createLargeResult_d5g0v0_Shanghai
[ ] diffPlaces_d23g0v0_Shanghai
[ ] doubleSelfdestructTest_d0g0v0_Shanghai
[ ] doubleSelfdestructTest_d1g0v0_Shanghai
[ ] doubleSelfdestructTest_d2g0v0_Shanghai
[ ] doubleSelfdestructTest_d3g0v0_Shanghai
[ ] doubleSelfdestructTest_d4g0v0_Shanghai
[ ] doubleSelfdestructTest_d5g0v0_Shanghai
[ ] doubleSelfdestructTest_d6g0v0_Shanghai
[ ] doubleSelfdestructTest_d7g0v0_Shanghai
[ ] doubleSelfdestructTouch_Paris_d0g0v0_Shanghai
[ ] doubleSelfdestructTouch_Paris_d0g0v1_Shanghai
[ ] doubleSelfdestructTouch_Paris_d0g0v2_Shanghai
[ ] dynamicAccountOverwriteEmpty_Paris_d0g0v0_Shanghai
[ ] eip2929-ff_d0g0v0_Shanghai
[ ] eip2929-ff_d1g0v0_Shanghai
[ ] eip2929-ff_d2g0v0_Shanghai
[ ] eip2929-ff_d3g0v0_Shanghai
[ ] eip2929-ff_d4g0v0_Shanghai
[ ] eip2929-ff_d5g0v0_Shanghai
[ ] eip2929-ff_d6g0v0_Shanghai
[ ] eip2929-ff_d7g0v0_Shanghai
[ ] eip2929-ff_d8g0v0_Shanghai
[ ] eoaEmptyParis_d0g0v0_Shanghai
[ ] eoaEmptyParis_d0g1v0_Shanghai
[ ] eoaEmptyParis_d0g1v1_Shanghai
[ ] eoaEmptyParis_d1g0v0_Shanghai
[ ] eoaEmptyParis_d1g1v0_Shanghai
[ ] eoaEmptyParis_d1g1v1_Shanghai
[ ] extCodeHashAccountWithoutCode_d0g0v0_Shanghai
[ ] extCodeHashCALLCODE_d0g0v0_Shanghai
[ ] extCodeHashCALL_d0g0v0_Shanghai
[ ] extCodeHashChangedAccount_d0g0v0_Shanghai
[ ] extCodeHashCreatedAndDeletedAccountCall_d0g0v0_Shanghai
[ ] extCodeHashCreatedAndDeletedAccountRecheckInOuterCall_d0g0v0_Shanghai
[ ] extCodeHashCreatedAndDeletedAccountStaticCall_d0g0v0_Shanghai
[ ] extCodeHashCreatedAndDeletedAccount_d0g0v0_Shanghai
[ ] extCodeHashDELEGATECALL_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount1Cancun_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount1_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount2Cancun_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount2_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount3_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount4_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccountCancun_d0g0v0_Shanghai
[ ] extCodeHashDeletedAccount_d0g0v0_Shanghai
[ ] extCodeHashDynamicArgument_d1g0v0_Shanghai
[ ] extCodeHashDynamicArgument_d2g0v0_Shanghai
[ ] extCodeHashDynamicArgument_d3g0v0_Shanghai
[ ] extCodeHashInInitCode_d0g0v0_Shanghai
[ ] extCodeHashInInitCode_d1g0v0_Shanghai
[ ] extCodeHashMaxCodeSize_d0g0v0_Shanghai
[ ] extCodeHashNewAccount_d0g0v0_Shanghai
[ ] extCodeHashPrecompiles_d0g0v0_Shanghai
[ ] extCodeHashSTATICCALL_d0g0v0_Shanghai
[ ] extCodeHashSelfInInit_d0g0v0_Shanghai
[ ] extCodeHashSelf_d0g0v0_Shanghai
[ ] extCodeHashSubcallOOG_d0g0v0_Shanghai
[ ] extCodeHashSubcallOOG_d1g0v0_Shanghai
[ ] extCodeHashSubcallOOG_d2g0v0_Shanghai
[ ] extCodeHashSubcallSuicideCancun_d0g0v0_Shanghai
[ ] extCodeHashSubcallSuicide_d0g0v0_Shanghai
[ ] extcodecopy_d0g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d0g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d1g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d2g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d3g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d4g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d5g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d6g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d7g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d8g0v0_Shanghai
[ ] extcodehashEmpty_Paris_d9g0v0_Shanghai
[ ] gasPriceDiffPlaces_d23g0v0_Shanghai
[ ] invalidAddr_d30g0v0_Shanghai
[ ] invalidAddr_d32g0v0_Shanghai
[ ] invalidAddr_d34g0v0_Shanghai
[ ] invalidAddr_d36g0v0_Shanghai
[ ] invalidAddr_d38g0v0_Shanghai
[ ] invalidAddr_d80g0v0_Shanghai
[ ] invalidAddr_d81g0v0_Shanghai
[ ] invalidAddr_d82g0v0_Shanghai
[ ] invalidAddr_d83g0v0_Shanghai
[ ] invalidAddr_d84g0v0_Shanghai
[ ] multiSelfdestruct_d0g0v0_Shanghai
[ ] multiSelfdestruct_d1g0v0_Shanghai
[ ] multiSelfdestruct_d2g0v0_Shanghai
[ ] multiSelfdestruct_d3g0v0_Shanghai
[ ] multiSelfdestruct_d4g0v0_Shanghai
[ ] randomStatetest147_d0g0v0_Shanghai
[ ] randomStatetest14_d0g0v0_Shanghai
[ ] randomStatetest173_d0g0v0_Shanghai
[ ] randomStatetest198_d0g0v0_Shanghai
[ ] randomStatetest201_d0g0v0_Shanghai
[ ] randomStatetest212_d0g0v0_Shanghai
[ ] randomStatetest22_d0g0v0_Shanghai
[ ] randomStatetest232_d0g0v0_Shanghai
[ ] randomStatetest273_d0g0v0_Shanghai
[ ] randomStatetest282_d0g0v0_Shanghai
[ ] randomStatetest287_d0g0v0_Shanghai
[ ] randomStatetest376_d0g0v0_Shanghai
[ ] randomStatetest401_d0g0v0_Shanghai
[ ] randomStatetest409_d0g0v0_Shanghai
[ ] randomStatetest487_d0g0v0_Shanghai
[ ] randomStatetest495_d0g0v0_Shanghai
[ ] randomStatetest559_d0g0v0_Shanghai
[ ] randomStatetest581_d0g0v0_Shanghai
[ ] randomStatetest635_d0g0v0_Shanghai
[ ] randomStatetestDEFAULT-Tue_07_58_41-15153-575192_d0g0v0_Shanghai
[ ] randomStatetestDEFAULT-Tue_07_58_41-15153-575192_london_d0g0v0_Shanghai
[ ] refundFF_d0g0v0_Shanghai
[ ] refundSuicide50procentCap_d1g0v0_Shanghai
[ ] refund_CallToSuicideNoStorage_d1g0v0_Shanghai
[ ] refund_CallToSuicideStorage_d1g0v0_Shanghai
[ ] refund_CallToSuicideTwice_d1g0v0_Shanghai
[ ] refund_TxToSuicide_d0g0v0_Shanghai
[ ] refund_multimpleSuicide_d0g0v0_Shanghai
[ ] refund_singleSuicide_d0g0v0_Shanghai
[ ] selfdestructEIP2929_d0g0v0_Shanghai
[ ] static_ABAcallsSuicide0_d0g0v0_Shanghai
[ ] static_ABAcallsSuicide0_d1g0v0_Shanghai
[ ] static_callcodecall_10_SuicideEnd2_d0g0v0_Shanghai
[ ] static_callcodecall_10_SuicideEnd2_d0g0v1_Shanghai
[ ] static_callcodecall_10_SuicideEnd_d0g0v0_Shanghai
[ ] static_callcodecall_10_SuicideEnd_d1g0v0_Shanghai
[ ] static_callcodecallcodecall_110_SuicideEnd2_d0g0v0_Shanghai
[ ] static_callcodecallcodecall_110_SuicideEnd2_d0g0v1_Shanghai
[ ] static_callcodecallcodecall_110_SuicideEnd_d0g0v0_Shanghai
[ ] static_callcodecallcodecall_110_SuicideEnd_d0g0v1_Shanghai
[ ] static_callcodecallcodecall_110_SuicideMiddle2_d0g0v0_Shanghai
[ ] static_callcodecallcodecall_110_SuicideMiddle_d0g0v0_Shanghai
[ ] static_refund_CallToSuicideTwice_d1g0v0_Shanghai
[ ] suicideAddress_d0g0v0_Shanghai
[ ] suicideCallerAddresTooBigLeft_d0g0v0_Shanghai
[ ] suicideCallerAddresTooBigRight_d0g0v0_Shanghai
[ ] suicideCaller_d0g0v0_Shanghai
[ ] suicideNonConst_d0g0v0_Shanghai
[ ] suicideNonConst_d0g0v1_Shanghai
[ ] suicideNotExistingAccount_d0g0v0_Shanghai
[ ] suicideOrigin_d0g0v0_Shanghai
[ ] suicideSendEtherPostDeath_d0g0v0_Shanghai
[ ] suicideSendEtherToMe_d0g0v0_Shanghai
[ ] suicide_d0g0v0_Shanghai
[ ] suicide_d1g0v0_Shanghai
[ ] suicide_d2g0v0_Shanghai
[ ] variedContext_d10g0v0_Shanghai
[ ] variedContext_d11g0v0_Shanghai
[ ] variedContext_d12g0v0_Shanghai
[ ] variedContext_d13g0v0_Shanghai
[ ] walletKillToWallet_d0g0v0_Shanghai
[ ] walletKill_d0g0v0_Shanghai

Update:
Testing combination of feat/type2 and feat/cancun (cf type2_cancun branch) to get rid of the selfdestruct issues, brings us down to 78 failed tests, listed below.
Failed tests

[ ] CREATE2_ContractSuicideDuringInit_ThenStoreThenReturn_d0g0v0_Cancun
[ ] CREATE2_Suicide_d2g0v0_Cancun
[ ] CREATE2_Suicide_d3g0v0_Cancun
[ ] CREATE2_Suicide_d6g0v0_Cancun
[ ] CREATE2_Suicide_d7g0v0_Cancun
[ ] InitCollisionParis_d0g0v0_Cancun
[ ] InitCollisionParis_d1g0v0_Cancun
[ ] InitCollisionParis_d2g0v0_Cancun
[ ] InitCollisionParis_d3g0v0_Cancun
[ ] callToSuicideThenExtcodehash_d0g0v0_Cancun
[ ] callToSuicideThenExtcodehash_d1g0v0_Cancun
[ ] callToSuicideThenExtcodehash_d2g0v0_Cancun
[ ] callToSuicideThenExtcodehash_d3g0v0_Cancun
[ ] codeCopyZero_Paris_d0g0v0_Cancun
[ ] create2InitCodes_d6g0v0_Cancun
[ ] create2collisionStorageParis_d0g0v0_Cancun
[ ] create2collisionStorageParis_d1g0v0_Cancun
[ ] create2collisionStorageParis_d2g0v0_Cancun
[ ] createEmptyThenExtcodehash_d0g0v0_Cancun
[ ] createLargeResult_d0g0v0_Cancun
[ ] createLargeResult_d1g0v0_Cancun
[ ] createLargeResult_d4g0v0_Cancun
[ ] createLargeResult_d5g0v0_Cancun
[ ] dynamicAccountOverwriteEmpty_Paris_d0g0v0_Cancun
[ ] eoaEmptyParis_d0g0v0_Cancun
[ ] eoaEmptyParis_d0g1v0_Cancun
[ ] eoaEmptyParis_d0g1v1_Cancun
[ ] eoaEmptyParis_d1g0v0_Cancun
[ ] eoaEmptyParis_d1g1v0_Cancun
[ ] eoaEmptyParis_d1g1v1_Cancun
[ ] extCodeHashAccountWithoutCode_d0g0v0_Cancun
[ ] extCodeHashCALLCODE_d0g0v0_Cancun
[ ] extCodeHashCALL_d0g0v0_Cancun
[ ] extCodeHashChangedAccount_d0g0v0_Cancun
[ ] extCodeHashCreatedAndDeletedAccountCall_d0g0v0_Cancun
[ ] extCodeHashCreatedAndDeletedAccountRecheckInOuterCall_d0g0v0_Cancun
[ ] extCodeHashCreatedAndDeletedAccountStaticCall_d0g0v0_Cancun
[ ] extCodeHashCreatedAndDeletedAccount_d0g0v0_Cancun
[ ] extCodeHashDELEGATECALL_d0g0v0_Cancun
[ ] extCodeHashDeletedAccount1Cancun_d0g0v0_Cancun
[ ] extCodeHashDeletedAccount1_d0g0v0_Cancun
[ ] extCodeHashDeletedAccount2Cancun_d0g0v0_Cancun
[ ] extCodeHashDeletedAccount2_d0g0v0_Cancun
[ ] extCodeHashDeletedAccount3_d0g0v0_Cancun
[ ] extCodeHashDeletedAccount4_d0g0v0_Cancun
[ ] extCodeHashDeletedAccountCancun_d0g0v0_Cancun
[ ] extCodeHashDeletedAccount_d0g0v0_Cancun
[ ] extCodeHashDynamicArgument_d1g0v0_Cancun
[ ] extCodeHashDynamicArgument_d2g0v0_Cancun
[ ] extCodeHashDynamicArgument_d3g0v0_Cancun
[ ] extCodeHashInInitCode_d0g0v0_Cancun
[ ] extCodeHashInInitCode_d1g0v0_Cancun
[ ] extCodeHashMaxCodeSize_d0g0v0_Cancun
[ ] extCodeHashNewAccount_d0g0v0_Cancun
[ ] extCodeHashPrecompiles_d0g0v0_Cancun
[ ] extCodeHashSTATICCALL_d0g0v0_Cancun
[ ] extCodeHashSelfInInit_d0g0v0_Cancun
[ ] extCodeHashSelf_d0g0v0_Cancun
[ ] extCodeHashSubcallOOG_d0g0v0_Cancun
[ ] extCodeHashSubcallOOG_d1g0v0_Cancun
[ ] extCodeHashSubcallOOG_d2g0v0_Cancun
[ ] extCodeHashSubcallSuicideCancun_d0g0v0_Cancun
[ ] extCodeHashSubcallSuicide_d0g0v0_Cancun
[ ] extcodehashEmpty_Paris_d0g0v0_Cancun
[ ] extcodehashEmpty_Paris_d1g0v0_Cancun
[ ] extcodehashEmpty_Paris_d2g0v0_Cancun
[ ] extcodehashEmpty_Paris_d3g0v0_Cancun
[ ] extcodehashEmpty_Paris_d4g0v0_Cancun
[ ] extcodehashEmpty_Paris_d5g0v0_Cancun
[ ] extcodehashEmpty_Paris_d6g0v0_Cancun
[ ] extcodehashEmpty_Paris_d7g0v0_Cancun
[ ] extcodehashEmpty_Paris_d8g0v0_Cancun
[ ] extcodehashEmpty_Paris_d9g0v0_Cancun
[ ] invalidAddr_d30g0v0_Cancun
[ ] invalidAddr_d32g0v0_Cancun
[ ] invalidAddr_d34g0v0_Cancun
[ ] invalidAddr_d36g0v0_Cancun
[ ] invalidAddr_d38g0v0_Cancun

which I think all fallback to the categories William mentioned above.

@Nashtare Is this one resolved?


tests: allocate more memory for all_in_one job

Since we fire up much less VMs than other job, we can affoard allocating
more memory here for this job.
Each VM hosts more daemon so 1024Mb can be too few.
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

jenkins test centos-non_container-all_in_one

jenkins test centos-container-all_in_one

jenkins test centos-container-all_in_one

jenkins test centos-non_container-all_in_one

jenkins test centos-non_container-all_in_one

jenkins test centos-non_container-all_in_one


False positive if query has leading whitespace

In our code we have SQL in constants, and for readability they start with an empty line:
err := s.db.QueryRow(someSQL).Scan(&foo)

const someSQL = `
  SELECT foo
  FROM bar
  WHERE ...query continues
`

On this input we get an execinquery error:
It's better to use Execute method instead of QueryRow method to execute `` query

Suggestion: TrimLeft the query string.

Have we met your request?

Thanks, judging by the test cases #10 should fix it.


client.nack(message) invalid

var subscribeHeaders = {
'destination': destination,
'ack': 'client-individual'
//'ack': 'client'
};
var overEvent = function(err, message){
if(err){
client.nack(message);
} else {
client.nack(message);
}
}
client.subscribe(subscribeHeaders, function(error, message) {
if (error) {
logger.error('subscribe error ' + error.message, error);
return subscribeFailCallback(error, message);
}
message.readString('utf-8', function(error, body) {
if (error) {
logger.error('read message error ' + error.message, error);
return overEvent(error, message);
}
onMessageCallback(body, function(err){
overEvent(err, message);
});
});
});
can not nack message!!! it's acked！

Your code is not compatible with client ack mode. Use client-individual ack mode.
Another thing, don't send a nack message after an error event. The client is dead after any error occurs and thereafter sending any messages to the server will fail.

Still the same！
I use activemq with stomp.

It's typical behaviour of a server to dequeue a message after it receives a nack.
A STOMP client can't enforce what action a server takes when it receives a nack or ack, it depends on what the server software supports and what configuration is in use.
I believe Activemq interprets nack as meaning the message is invalid, and does not attempt to send the message to another subscriber because they too should reply with nack.

but how can nack messsage ?
if process message error，then let's activemq resend with nack message， how to implement this

Found the problem!
nack will be move the message to DLQ.(this message must be Persistence).

@zhudan
I am facing the same problem. I use ActiveMQ with stompit. Problem I have is that if I nack a message it will be removed from the queue (couldn't find the DLQ yet, do you need to setup something for it to show up in ActiveMQ?). But I need the message to persist in the queue and be redelivered. Were you able to achieve such thing?


Refine CellInfo-type

Today, the CellInfo type that is passed into renderCell is bit of a mix. It contains the actual output, the element to render onto, and metadata. I think a little more structure would be better. Suggestions

make the HTMLElement a dedicated argument of the renderCell-function
rename CellInfo to OutputItem or just Output
rename bytes() to data()
make id the last argument of renderCell?

make id the last argument of renderCell?

This can be passed when requiresMessaging is set, since (as far as I know) it's not useful internally.

How about moving the id into CellInfo? renderCell(element, cellInfo)

OutputItem is ok with me but feels a little weird for markup cells (I guess for those you can think of them as being their own output)
If we make this change though, we should also rename renderCell to renderOutputItem

data sounds good. It's closer to the fetch api

I'll go ahead and prep a PR that makes the code changes but will hold off on merging anything until you take a look @jrieken

Checkin to code with #125351. Types and samples should be updated now too


Bump cudatoolkit minor versions

Bump a few of the cudatoolkit minor versions. Needed as part of the CUDA Docker image updates in PR ( https://github.com/conda-forge/docker-images/pull/237 ).

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please restart CI

What a treat to the eyes, so much simpler!

@conda-forge-admin, please restart CI

The linux_64 CUDA 11.8 package fails to build due to lack of space. However that one isn't been changed here
Going to merge to get the other packages out
Will raise a follow up issue for linux_64 CUDA 11.8 builds to debug further

Will raise a follow up issue for linux_64 CUDA 11.8 builds to debug further

Filed as issue: https://github.com/conda-forge/cudatoolkit-feedstock/issues/91


.probe() returns error

The code snippet below fails with the following error message if the URI is not present in the database:
  message: 'probe document: challenge request failed for /v1/documents?format=json&uri=%2Ftest.json (on /test.json)' }```

Here's the code that I've used:

```javascript
'use strict';
var connection = {
  host: 'localhost',
  port: 8000,
  user: 'admin',
  password: 'admin'
};

var db = marklogic.createDatabaseClient(connection);
var qb = marklogic.queryBuilder;
var pb = marklogic.patchBuilder;

var uri = '/test.json';

db.documents.probe(uri).result()
.then(function(probeResponse) {
  console.log(probeResponse);
})
.catch(function(error) {
  console.log(error);
});

I was expecting to see probeResponse.exists to be false.
ML version: 8.0-3.2

FWIW, I cannot reproduce this in my environment on 8.0-4. That almost sounds like an auth failure. Are you able to successfully make other requests with that connection?

Yes - If I have the /test.json file in the DB I get the proper probeResponse object back, no problem. If I clear the DB, I get the above error.

Very interesting - the issue was that for the App Server running on that port I've set the authentication to be 'application-level' and the default user was set to 'admin'.
The question remains though: how come I could verify the existence of one document but when the DB was empty I saw an error?

This is a totally uninformed guess:
When the probe fails, a 404 is returned by the REST API. Perhaps there's something about app level security that causes it to mask 404's behind a different kind of error. IDK why it would, though.

The REST API doesn't play well with application-level security, which requires sessions.  Please use digest or basic+SSL instead.


add wget and net-tools tempoarily for testing

This PR adds wget and net-tools to container image for temporary introspection
Will remove wget and net-tools once testing is complete.

Reference Server Preview is available here:https://anchor-ref-pr177.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr177.previews.kube001.services.stellar-ops.com/


chore(main): release 0.4.0

:robot: I have created a release beep boop
0.4.0 (2024-12-17)
Features

license comment (49ed466)

Bug Fixes

build (0249df4)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.4.0
:sunflower:


Starting a new sentence with a number crashes the page

Describe the bug
When a new sentence starts with a number it crashes the page.
To Reproduce
Steps to reproduce the behavior:

Type "Hello world. "
Type "2"
See that page becomes unresponsive

Expected behavior
Page doesn't become unresponsive, and doesn't change sentence.
Desktop (please complete the following information):

OS: MacOS
Browser: Chrome
Version: Version 103.0.5060.114 (Official Build) (x86_64)

Additional context
This is on a webpage I maintain which utilises "react-quill". It is hard to determine whether this affects other use cases.

@ejvet-ct I can't replicate it. If your page is public, can you share it?


refactor: return DataFrame type from read functions and None from writing ones

https://github.com/fal-ai/fal/runs/7114868311?check_suite_focus=true

Ignore failing test, I will merge the fix from #425

https://github.com/fal-ai/fal/actions/runs/2591039422


elastic_aio doesn't work on OS X

Last week I wrote a poll()-based version of elastic instead of fixing the async version on OS X, but we should use the async version if possible.
Why? AIO seems to (1) be faster than polling, (2) match the Windows IOCP approach, and (3) admit an abstraction for threads to exchange data without copying too much.

aio_read() on stdin fails and sets errno to EAGAIN (resource temporarily unavailable).
The same code works for regular files, so it appears that OS X just doesn't support AIO on pipes. Drat!

https://github.com/grencez/lace/commit/35798555d5d95f105ea7a6c0d9624a03cb9b38bf is the result of this work. No fix, but some improvements.


having trouble getting it to work with pure perms

I'm having trouble with using pure perms as the group manager. In my configs it says I can only use xperms and the one that comes with it. Does this mean my version is old and if so how do I get the most up to date. I'm sure I'm missing something easy and just don't know it. Your help would be greatly appreciated.

Change your preferred-groupmanager in the RankUp config to rankup\\permission\\PurePerms

I copyed exactly what you posted and it gave me this error as it has been probably would have been helpful to begin with but here it us now.[PocketMine] Server is starting...
[PocketMine] Server was started.
[Server] 05:18:47 [WARNING] Timezone could not be automatically determined. An incorrect timezone will result in incorrect timestamps on console logs. It has been set to "UTC" by default. You can change it on the php.ini file.
[Server] 05:18:47 [INFO] Starting Minecraft: PE server version v0.10.5 alpha
[Server] 05:18:47 [INFO] Loading pocketmine.yml...
[Server] 05:18:47 [INFO] Loading server properties...
[Server] 05:18:47 [INFO] Advanced cache enabled
[Server] 05:18:47 [INFO] Starting Minecraft PE server on <IP_ADDRESS>:19132
[Server] 05:18:47 [INFO] This server is running PocketMine-MP version 1.4.1dev-965 "絶好(Zekkou)ケーキ(Cake)" (API 1.11.0)
[Server] 05:18:47 [INFO] PocketMine-MP is distributed under the LGPL License
[Server] 05:18:48 [INFO] Loading PurePerms v1.0.7
[Server] 05:18:48 [INFO] Loading EssentialsPE v1.0.2
[Server] 05:18:48 [INFO] Loading iProtector v3.0
[Server] 05:18:48 [INFO] Loading MineReset v2.0.3
[Server] 05:18:48 [INFO] Loading SimpleAuth v1.6.0
[Server] 05:18:48 [INFO] Loading TimeCommander v2
[Server] 05:18:48 [INFO] Loading Universe v1.0.0
[Server] 05:18:48 [INFO] [Universe] Universe Loaded!

[Server] 05:18:53 [INFO] If you would like to be kept informed about new Beta or Development builds, it is recommended that you change 'preferred-channel' in your pocketmine.yml to 'beta' or 'development'.
[Server] 05:18:53 [INFO] ----- -------------------------- -----
[Server] 05:18:53 [INFO] Enabling PurePerms v1.0.7
[Server] 05:18:54 [INFO] [PurePerms] Set data provider to YAML.
[Server] 05:18:54 [INFO] Enabling SimpleAuth v1.6.0
[Server] 05:18:54 [INFO] [SimpleAuth] Everything loaded!
[Server] 05:18:54 [INFO] Enabling TimeLimitCMD v0.0.1
[Server] 05:18:54 [INFO] [TimeLimitCMD] TimeLimitCMD Initializing [...]
[Server] 05:18:54 [INFO] [TimeLimitCMD] Everything is Loaded!
[Server] 05:18:54 [INFO] Enabling PureChat v1.2.3
[Server] 05:18:54 [INFO] Preparing level "world"
[Server] 05:18:55 [INFO] Enabling EssentialsPE v1.0.2
[Server] 05:18:55 [INFO] [EssentialsPE] Loading...
[Server] 05:18:55 [INFO] Enabling iProtector v3.0
[Server] 05:18:55 [INFO] Enabling MineReset v2.0.3
[Server] 05:18:55 [INFO] Enabling TimeCommander v2
[Server] 05:18:55 [INFO] Enabling Universe v1.0.0
[Server] 05:18:55 [INFO] Enabling FurnaceIndicator v1.0
[Server] 05:18:55 [INFO] Enabling EconomyAPI v2.0.5
[Server] 05:18:55 [NOTICE] [EconomyAPI] Auto save has been set to interval : 10 min(s)
[Server] 05:18:55 [INFO] Enabling EconomyLand v2.0.6
[Server] 05:18:55 [INFO] Enabling EconomyProperty v2.0.3
[Server] 05:18:55 [INFO] Enabling EconomySell v2.0.4
[Server] 05:18:55 [INFO] Enabling EconomyShop v2.0.4
[Server] 05:18:55 [INFO] Enabling ItemCloud v1.1
[Server] 05:18:55 [INFO] Enabling EconomyPShop v2.0.0
[Server] 05:18:55 [INFO] Enabling RankUp v0.2.1
[Server] 05:18:55 [INFO] [RankUp] Loaded DoesGroups.
[Server]
[Server] Fatal error: Class ' rankup\permission\PurePerms' not found in phar:///storage/emulated/0/PocketMine/plugins/plugin-830.phar/src/rankup/permission/PermissionLoader.php on line 15
[Server] 05:18:55 [EMERGENCY] An unrecoverable error has occurred and the server has crashed. Creating a crash dump
[Server] 05:18:55 [EMERGENCY] Please submit the "/storage/emulated/0/PocketMine/CrashDump_Wed_Mar_11-05.18.55-UTC_2015.log" file to the Bug Reporting page. Give as much info as you can.
[Server] 05:19:01 [INFO] Disabling PurePerms v1.0.7
[Server] 05:19:01 [INFO] Disabling EssentialsPE v1.0.2
[Server] 05:19:01 [INFO] Disabling iProtector v3.0
[Server] 05:19:01 [INFO] Disabling MineReset v2.0.3
[Server] 05:19:01 [INFO] Disabling SimpleAuth v1.6.0
[Server] 05:19:01 [INFO] Disabling TimeCommander v2
[Server] 05:19:01 [INFO] Disabling Universe v1.0.0
[Server] 05:19:01 [INFO] [Universe] Universe Unloaded!
[Server] 05:19:01 [INFO] Disabling FurnaceIndicator v1.0
[Server] 05:19:01 [INFO] Disabling TimeLimitCMD v0.0.1
[Server] 05:19:01 [INFO] Disabling EconomyAPI v2.0.5
[Server] 05:19:01 [INFO] Disabling EconomyLand v2.0.6
[Server] 05:19:01 [INFO] Disabling EconomyProperty v2.0.3
[Server] 05:19:01 [INFO] Disabling EconomySell v2.0.4
[Server] 05:19:01 [INFO] Disabling EconomyShop v2.0.4
[Server] 05:19:01 [INFO] Disabling ItemCloud v1.1
[Server] 05:19:01 [INFO] Disabling EconomyPShop v2.0.0
[Server] 05:19:01 [INFO] Disabling PureChat v1.2.3
[Server] 05:19:01 [INFO] Disabling RankUp v0.2.1
[Server] 05:19:01 [INFO] Unloading level "world"

Sorry, I forgot the package and release PurePerms support, I have done it now. https://github.com/Falkirks/RankUp/releases/tag/v0.3

Thanks a ton

OK sorry but I have one last question, what do I do with the files you linked me to. I tried just putting the new phar file in there and deleteing the only folder I created but it gave me to same error. So I'm guessing you have to do something with the other files on the page you linked me to but I'm not sure what.

@Rspuds That shouldn't happen. I will test this tomorrow.

Just letting you know Pocket money and economy's have both taken away the payment methods so rankup won't work so if you could please change it to work with massiveeconomys thanks I really need rank up for my prison server so could you tell me when you'll have it updated?

It takes time to add a new plugin because plugin developers tend not to fully document their APIs.

Thank you so much

And I have a question how can I make my own plugin for people to use I want to start becoming a plugin developer

Anything new on getting the plugin to work with Pure Perms?

To falls have you updated the rankup so it works with massiveeconomy?
Sent from my iPad

On Mar 15, 2015, at 8:46 PM, Rspuds<EMAIL_ADDRESS>wrote:
Anything new on getting the plugin to work with Pure Perms?
—
Reply to this email directly or view it on GitHub.

@Kadin15 @Rspuds I haven't got a chance to make any updates. I will update here when there is progress.

OK thanks

Any progress on this plugin with pureperms?

Yeah I did the same thing it does not work for me

Does the built in group manager work for you?

I don't know how to use it

I will update this into a working state for 1.5 and 0.11 when 0.11 is released.

Thank you!

Still when...
[20:16:28] [Server thread/CRITICAL]: Unhandled exception executing command 'rankup' in rankup: strtolower() expects parameter 1 to be string, object given
[20:16:28] [Server thread/WARNING]: InvalidArgumentException: "strtolower() expects parameter 1 to be string, object given" (E_WARNING) in "/RankUp-master/src/rankup/rank/RankStore" at line 25

@goerick @Falkirks https://github.com/Falkirks/RankUp/pull/7

@goerick This should be fixed now by #7, let me know if the issue appears again.


Adding Rayleigh-Taylor instability elixir

This PR does three things:

Extends BoundaryConditionWall and addresses #805
Replaces the scatter plot default for StructuredMesh and UnstructuredMesh with the new Plots.jl recipe using UnstructuredPlotData2D
Adds initial conditions and an elixir for the Rayleigh Taylor instability.

Example of the solution for polydeg=3 and a 32 x 128 mesh:

Smoothing the solution: new solution with polydeg=3 and a mesh of size 32 x 128.

@sloede @ranocha should be ready for another look. I won't push any more commits.

Looks good to me and can be merged from my point of view when tests pass and coverage is good.

Thanks!

Well, thank you for creating this setup :+1:


Large Models suuport: too large to be loaded automatically (67GB > 10GB)

How can I use WizardLM/WizardCoder-Python-34B-V1.0 or any other large module ?

In case I go with either Spaces or Inference Endpoints, should I replace the string for the model, and use the endpoint direclty?

Yes! It's either a model id from the Hugging Face Hub either an http url.


Make repository smaller

Currently it is pretty big because of some binaries being committed into it in the history.

Done.


AZ Interactive command fails in MS Learn Sandbox

This is autogenerated. Please review and update as needed.
Describe the bug
In a Microsoft Learn module that introduces interactive mode for the command line, the command to enter interactive mode (az interactive) fails in the sandbox.
URL: https://learn.microsoft.com/en-us/training/modules/describe-core-architectural-components-of-azure/4-exercise-explore-learn-sandbox
Command Name
az interactive
Errors:
The command failed with an unexpected error. Here is the traceback:
No module named 'prompt_toolkit.interface'
Traceback (most recent call last):
  File "/usr/lib64/az/lib/python3.9/site-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/usr/lib64/az/lib/python3.9/site-packages/azure/cli/command_modules/interactive/custom.py", line 41, in start_shell
    azext_interactive.start_shell(cmd, style=style)
  File "/home/zhanknight/.azure/cliextensions/interactive/azext_interactive/__init__.py", line 10, in start_shell
    from .azclishell.app import AzInteractiveShell
  File "/home/zhanknight/.azure/cliextensions/interactive/azext_interactive/azclishell/app.py", line 33, in <module>
    from prompt_toolkit.interface import Application, CommandLineInterface
ModuleNotFoundError: No module named 'prompt_toolkit.interface'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az interactive

Expected Behavior
Expected sandbox CLI to enter interactive mode.
Environment Summary
Linux-5.4.0-1094-azure-x86_64-with-glibc2.35 (Cloud Shell), CBL-Mariner/Linux
Python 3.9.13
Installer: RPM

azure-cli 2.41.0

Extensions:
interactive 0.4.5
ai-examples 0.2.5
ml 2.10.0
ssh 1.1.2

Dependencies:
msal 1.20.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

Duplicate of https://github.com/Azure/azure-cli/issues/24213


Add dtype_numpy with medium-effort validation

Add dtype_numpy to Event Descriptor.
Supersedes #215.

Running the schema generation seems to remove NX_class and not add dtype_numpy. I'm confused.
$ git diff
diff --git a/event_model/schemas/event_descriptor.json b/event_model/schemas/event_descriptor.json
index 3549af5..5958023 100644
--- a/event_model/schemas/event_descriptor.json
+++ b/event_model/schemas/event_descriptor.json
@@ -112,12 +112,6 @@
             "description": "The 'interesting' data keys for this device.",
             "type": "object",
             "properties": {
-                "NX_class": {
-                    "title": "Nx Class",
-                    "description": "The NeXus class definition for this device.",
-                    "type": "string",
-                    "pattern": "^NX[A-Za-z_]+$"
-                },
                 "fields": {
                     "title": "Fields",
                     "description": "The 'interesting' data keys for this device.",

Running the schema generation seems to remove NX_class and not add dtype_numpy. I'm confused.
I'll take a look!

Thank you, @evalott100!

And I get the same correct output as above on your branch directly (with python 3.10/3.11) $ python event_model/documents/generate :thinking:
Were you using an older venv?


meson --skip-subprojects option ignored when building wheel

My project use a subproject, and the subproject installs a static lib. I don't want to include the static lib, or any file installed by the subproject. Howerver, adding
[tool.meson-python.args]
install = ['--skip-subprojects']

to pyproject.toml does not prevent meson-python trying to install files from the subproject:
+ meson install --quiet --no-rebuild --destdir C:\Users\CHARLE~1.BRU\AppData\Local\Temp\build-via-sdist-03nfoz4f\pypkgconf-0.1.0\.mesonpy-tmvd08tf\install --skip-subprojects

meson-python: error: Could not map installation path to an equivalent wheel directory: '{libdir_static}\\libpkgconf.a'

ERROR Backend subprocess exited when trying to invoke build_wheel

For reference, my project is on https://github.com/bruchar1/pypkgconf

meson install seems to be invoked before the files for the wheel are collected. I wonder if, instead of having special treatments for every meson switch, we could simply compare the file list from the install plan with the files copied to the temp install dir? This would allow to remove the special handling for --tags, and to support any special install switches meson could support in the future.
Otherwise, this should be documented that --skip-subprojects is not supported.

This is precisely what I meant with revisting the architecture of this part of meson-python. meson-python currently does not do anything with the results of meson install. The build artifacts are collected from the source directory and from the build directory. It is a long standing bug in meson-python that we need to correct. #348 and #364 fix that. The fix for this issue would have to build on top of these patches.

Thinking about this a bit more, the solution is not as easy as I though: in several places we need to know which files will be included in the wheel before we run meson install and start populating the wheel file. We even need it before running the compilation, for determining if we need to inject a build dependency on patchelf on Linux.
Unfortunately, I don't see an easy way to implement the equivalent of --skip-subprojects with only the information available in the Meson introspection data. I don't know how to implement this functionality within these constraints.

See https://github.com/mesonbuild/meson/pull/11909


PR: Add extra links for related issues and prs

Fixes #63

It's missing a test

@ccordoba12 yep, working on that


cmake: add cache variables for BUILD_SHARED_LIBS & VVENC_LIBRARY_ONLY

closes #433

What happens to make test if you do that?

Make test will fail naturally fail if you set VVENC_LIBRARY_ONLY=1, but I guess that is how it is. How should you run the tests, when you don't build the tests?
You can still go to your build directory (e.g. build/release-static), explicitly build all the binaries, and then run ctest.

We do output a warning now that the test suite will not be able to run, when enabling VVENC_LIBRARY_ONLY.


Cleanup axiom dependencies

Purpose
This PR cleans up the axiom related dependencies since orbit versions are no longer used.

Codecov Report

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

@@            Coverage Diff            @@
##             master   #14201   +/-   ##
=========================================
  Coverage          ?   64.74%
  Complexity        ?      426
=========================================
  Files             ?     2173
  Lines             ?    95949
  Branches          ?    12817
=========================================
  Hits              ?    62123
  Misses            ?    28805
  Partials          ?     5021

Continue to review full report at Codecov.

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


Add BandLab, Curiosity Stream & Homeworker

Description
Added icons for BandLab, Curiosity Stream and Homeworker.

I'm aware that the Homeworker icon doesn't exactly match the style guide as there are parts between the main 6px and 12px stroke widths, but I found it doesn't look good without the 6px-parts or without the smoothing parts.
Type of change
:x: Bug fix (non-breaking change which fixes an issue)
:white_check_mark: Icon addition (non-breaking change that adds/modifies Lawnicons's icons)
:x: General change (non-breaking change that doesn't fit the above categories like copyediting)
Icons addition information
Icons added

Bandlab (com.bandlab.bandlab)
Curiosity Stream (com.curiosity.curiositystream)
Homeworker (info.xolf.homeworker)

@Chefski Sorry for that, forgot to unify the stroke width.


Sybil Attacker Report

Related Safe Addresses
0x97fc476dbfdfb15465d8ccf8a75a995b432c713c
0x7daa1956626a6d831e3968c9c6a8904a773d345f
0x5a7f653b6c4b661eb75cc39aac6540e7145da5c6
0x83a6f8cb2fcc00b74313de4037495f8958f258f1
0x94569fc153906f79f4bbb1c9100f2e57230ff86f
0x26dbdec275c9d90ba9abf803399b8486210e9ee9
0x388f2b8b1a7ef310ba4686fad23082e688d7a718
0xdb26f4edf068c74dd0f89a5d933cfa34d798b73c
0x03b9a3a06ec9de8421b3172c80b06a49a959ea0c
0xa50a74df0568734be3a710b69c54fe18c6d1068c
0x77d3d5ec084915eddb211a5ae1c71de68e8e55c9
0x172582768a35bec8c5ed4d482bc076898783b137

Reasoning

All the above safe addresses have EXACT 3 transactions: the creation, a transaction of receiving ETH, and a transaction of mint compound ETH (exact the first safe address which minted twice.).
The receive and mint transactions in each safe address are at the same time.
The receive and mint timestamps of these safe addresses are consecutive.
The received-from addresses got funds from the same central address (0xc062Eeca3891539F75054b1060997aa3459b7390) within a couple of minutes on 7/27/2022  (except three received-from addresses got funds from the central address before.).  Details are in the below tables.

Following is the list of safe addresses, all transactions, safe created date, Received/Compound Ether Date, received time, mint time, received ETH value, and receive-from addresses

Safe address
Safe Address's transactions
Safe created date
Received/Compound Ether Date
Received time
Mint time
Received ETH value
Received from

0x97fc476dbfdfb15465d8ccf8a75a995b432c713c
https://gnosis-safe.io/app/eth:0x97fc476dbfdfb15465d8ccf8a75a995b432c713c/transactions/history
10-Jul-22
27-Jul-22
3:20 PM / 4:40 PM
3:22PM / 4:42 PM
0.01 ETH
0x4e229156470863b00bb6c03a78797632921be81d

0x7daa1956626a6d831e3968c9c6a8904a773d345f
https://gnosis-safe.io/app/eth:0x7daa1956626a6d831e3968c9c6a8904a773d345f/transactions/history
9-Jul-22
27-Jul-22
3:31 PM
3:31 PM
0.01 ETH
0xbbfc1d1f420703aebe13007f5ce0182f70bf35b9

0x5a7f653b6c4b661eb75cc39aac6540e7145da5c6
https://gnosis-safe.io/app/eth:0x5a7f653b6c4b661eb75cc39aac6540e7145da5c6/transactions/history
10-Jul-22
27-Jul-22
3:34 PM
3:38 PM
0.01 ETH
0xf918c679fae9e6dafa3d29a62e28f36f1661d279

0x83a6f8cb2fcc00b74313de4037495f8958f258f1
https://gnosis-safe.io/app/eth:0x83a6f8cb2fcc00b74313de4037495f8958f258f1/transactions/history
10-Jul-22
27-Jul-22
3:40 PM
3:47 PM
0.01 ETH
0x0bc4ecc2a47413af3552be58bf741fcb04f13bcd

0x94569fc153906f79f4bbb1c9100f2e57230ff86f
https://gnosis-safe.io/app/eth:0x94569fc153906f79f4bbb1c9100f2e57230ff86f/transactions/history
9-Jul-22
27-Jul-22
4:11 PM
4:13 PM
0.01 ETH
0xf55f8884203632eb007f239758d1b25cd173458b

0x26dbdec275c9d90ba9abf803399b8486210e9ee9
https://gnosis-safe.io/app/eth:0x26dbdec275c9d90ba9abf803399b8486210e9ee9/transactions/history
10-Jul-22
27-Jul-22
4:24 PM
4:25 PM
0.01 ETH
0x70ae7ed8469e55a82497816001644ac123513a18

0x388f2b8b1a7ef310ba4686fad23082e688d7a718
https://gnosis-safe.io/app/eth:0x388f2b8b1a7ef310ba4686fad23082e688d7a718/transactions/history
10-Jul-22
27-Jul-22
4:27 PM
4:29 PM
0.01 ETH
0x2fc5fe33b36f75219beb038db84049ffa74dc036

0xdb26f4edf068c74dd0f89a5d933cfa34d798b73c
https://gnosis-safe.io/app/eth:0xdb26f4edf068c74dd0f89a5d933cfa34d798b73c/transactions/history
10-Jul-22
27-Jul-22
4:32 PM
4:30 PM
0.01 ETH
0xfb107ef723793fd617519735daf4ddb49f8561c3

0x03b9a3a06ec9de8421b3172c80b06a49a959ea0c
https://gnosis-safe.io/app/eth:0x03b9a3a06ec9de8421b3172c80b06a49a959ea0c/transactions/history
28-May-22
27-Jul-22
4:37 PM
4:38 PM
0.01 ETH
0xc03f8455f1492a1598b43211b0573b67ecc58c62

0xa50a74df0568734be3a710b69c54fe18c6d1068c
https://gnosis-safe.io/app/eth:0xa50a74df0568734be3a710b69c54fe18c6d1068c/transactions/history
30-May-22
27-Jul-22
4:47 PM
4:48 PM
0.01 ETH
0xda6c2d0f44352d9f4b8ebb00606657310ea4e26b

0x77d3d5ec084915eddb211a5ae1c71de68e8e55c9
https://gnosis-safe.io/app/eth:0x77d3d5ec084915eddb211a5ae1c71de68e8e55c9/transactions/history
28-May-22
27-Jul-22
4:55 PM
4:58 PM
0.01 ETH
0x40276ba5efdfbbf749557f6b2a094abd78197164

0x172582768a35bec8c5ed4d482bc076898783b137
https://gnosis-safe.io/app/eth:0x172582768a35bec8c5ed4d482bc076898783b137/transactions/history
10-Jul-22
27-Jul-22
5:01 PM
5:02 PM
0.01 ETH
0x1765a1b1cf3f083edc084e72301caa51f89e4028

Following is the transactions of all receiving-from addresses got funded from central address 0xc062Eeca3891539F75054b1060997aa3459b7390.

Received from
Transaction
Date Time
Value

0x4e229156470863b00bb6c03a78797632921be81d
https://etherscan.io/tx/0x24e87aca749e8d09fb7feab31414454bcddab11ed3e9c5e659052a12eddf9711
7/27/2022   11:30
0.2 Ether

0xbbfc1d1f420703aebe13007f5ce0182f70bf35b9
https://etherscan.io/tx/0x371744a74fe51221d07dbf84fdbe2e35e0251660b7e65061ea6dafb3e8a8f5ac
7/27/2022   11:30
0.2 Ether

0xf918c679fae9e6dafa3d29a62e28f36f1661d279
https://etherscan.io/tx/0x9f4f1a5bf05bce43f5cafebd1d3b78c9350b80a399629e147c6ea5703fc73cef
7/27/2022   11:29
0.2 Ether

0x0bc4ecc2a47413af3552be58bf741fcb04f13bcd
https://etherscan.io/tx/0x3bf13ff6b0ad0eaa1857031c15e6af23408835c3e4d121342f9ebf31a194a76a
7/27/2022   11:32
0.2 Ether

0xf55f8884203632eb007f239758d1b25cd173458b
https://etherscan.io/tx/0x7300de7cf2870ef39013f54632f0782fb9441b6f6102e6293374535759c603a4
12/25/2020   14:21
1 Ether

0x70ae7ed8469e55a82497816001644ac123513a18
https://etherscan.io/tx/0x2cc2d64a4e4b408e8d7d0180bb7ea6c06cb6cfccb32e87dbaa743d499a3f9f82
7/27/2022   11:33
0.1 Ether

0x2fc5fe33b36f75219beb038db84049ffa74dc036
https://etherscan.io/tx/0x8fd92b11cea0610390020e1e6a7b8cc3ec80a9d1031162b9bd7e76232d3f33ae
7/27/2022   11:29
0.2 Ether

0xfb107ef723793fd617519735daf4ddb49f8561c3
https://etherscan.io/tx/0xdd62261c16dbd3488bfce5e620314917c10defe5d808ce115c37e4d91906a3b6
7/27/2022   11:28
0.2 Ether

0xc03f8455f1492a1598b43211b0573b67ecc58c62
https://etherscan.io/tx/0x821b7fbdac3909d0d713c0be1883c2f326e204c0bfbcb05ded2cd590fda0249c
7/27/2022   11:28
0.2 Ether

0xda6c2d0f44352d9f4b8ebb00606657310ea4e26b
https://etherscan.io/tx/0x050f5a23cfd6104010e62bdc123effe5cb36b9bfdc003855008951cf42b06531
12/31/2020   8:15
0.43 Ether

0x40276ba5efdfbbf749557f6b2a094abd78197164
https://etherscan.io/tx/0x17a6adfa338123defaa78f4fa77e7a0be95b002c099c1c67503b21681594dbc9
12/26/2020   14:45
3.2 Ether

0x1765a1b1cf3f083edc084e72301caa51f89e4028
https://etherscan.io/tx/0xef467c2e80287402241903e03134d3ec59a941ab183e2bd802b4da235b8ab3c7
7/27/2022 11:34
0.1 Ether

Methodology
The reported addresses were discovered by checking their safe behaviors using https://gnosis-safe.io/app/, and the mainnet behaviors using ethscan.
Safe Address
0xAbeA4DC133037af99dfa63541090124ae9e0C81c

I am just curious where I had copied these addresses from. @tschubotz

It is not right to insult people without a single piece of evidence.
@tschubotz @johannesmoormann @lukasschor
I will progressively add the following facts to all my reported issues.

Totally different reasons were reported in this issue.
Pls see the following table.

Reported issue
Number of safe addresses
Status

#377
12

Other report issues contained partial or   all these safe addresses
Number of reported address

#256
~100
staker

#503
hundreds
invalid

#262
59
staker valid

wow, #124 (comment)
can you provide evidence that i am copycat????

I never said anyone is copycat. I only stated the facts.

Wow, what's your fact?
you said me
skydotone raised a lot of empty issues (too many), and suddenly, these empty issues were full of results
But always there is someone in these issues who said that he was the first to find these addresses. :-)

Then can you give me an example? Whose address did I steal? ?

LISTEN, @zlgitol  ,
I gave you six hours today, and I hope we can have a good communication. check it 👉 https://github.com/safe-global/safe-user-allocation-reports/issues/443#issuecomment-1253183888
However, you have never made any reply.
So, let me sort out what happened.

You said me:
skydotone raised a lot of empty issues (too many), and suddenly, these empty issues were full of results
But always there is someone in these issues who said that he was the first to find these addresses. :-)

I answer you that I need to get the issue number to save my local markdown file , i always edit content to format in typora
I post 26 issues, only two of which had disputes with others, issue124 and issue260

SO THIS IS ALWAYS??????

Issue260, please look at this comment,https://github.com/safe-global/safe-user-allocation-reports/issues/343#issuecomment-1251968990   please work out WHO COPY WHO.
issue124, I think my answer is clear.

AND PLEASE KNOW , In this issue, I put forward a total of 99 addresses, 11 of which have disputes with others. Please see clearly! ! !.

That's all what happened. if you think what i said is wrong, please let us have a discussion. PLEASE

The next day, all my report were labeled Heavily edited and potential copycat.
Do you know how much damage you have done to me??
Do you know how hard it is for me to prove my innocence now??
Because of your insult and slander, all of my efforts have been ruined, ALL EFFORT!
I CAN TELL YOU CLEARLY THAT THIS IS REVENGE

Thanks for the report. Some of the Safes have been reported before already. But we found the following to be related to airdrop farming:
0x97fc476dbfdfb15465d8ccf8a75a995b432c713c
0x7daa1956626a6d831e3968c9c6a8904a773d345f
0x5a7f653b6c4b661eb75cc39aac6540e7145da5c6
0x83a6f8cb2fcc00b74313de4037495f8958f258f1
0x94569fc153906f79f4bbb1c9100f2e57230ff86f
0x26dbdec275c9d90ba9abf803399b8486210e9ee9
0x388f2b8b1a7ef310ba4686fad23082e688d7a718
0xdb26f4edf068c74dd0f89a5d933cfa34d798b73c
0x03b9a3a06ec9de8421b3172c80b06a49a959ea0c
0xa50a74df0568734be3a710b69c54fe18c6d1068c
0x77d3d5ec084915eddb211a5ae1c71de68e8e55c9
0x172582768a35bec8c5ed4d482bc076898783b137


Adding missing GLSL types

Related to issue #7, need to add:

[x] bool
[x] bvec (2,3,4)
[x] ivec (2,3,4)

I've decided to stop here - the new types are in at a basic level. I expect there will be lots of gaps around this stuff, such as operators for combining bvecs with themselves and other types, but I'll tackle them as the need arises.


Issues : how to find the problem when returning MEDIA_INVALID ?

when I tried sending a inputMediaPoll using messages.sendMedia， the server returned the MEDIA INVALID. I don't know what the wrong direction this error is returning.

Logz

Spam

This is not related to TDLib. You can hardly receive MEDIA_INVALID when sending a poll with TDLib.

@levlam I'm trying to use only parts of the telegram_api, such as sending text messages and sending files. But it seems that I made a mistake when I was trying to send the file, and the server returned me this error code, I kind of don't know what the mistake is. If the question was bad, thanks for answering it.


ok, plumbery 1.0 -- what is required to go there?

[ ] check all documentation at the wiki server for accuracy
[ ] reach 75% of test coverage
[ ] move the documentation to a separate project
[ ] convert the documentation to markdown for easy update directly in github
[ ] document connectivity options and the beachhead directive
[ ] change from xxx.parameter to parameter.xxx
[ ] reach full compatibility with python3 -- Anthony
[ ] implement anti-affinity

Python 3 support done

change from xxx.parameter to parameter.xxx -- done

massive documentation change on-going -- not finished yet, see my repo for details

documentation of directives done, including beachhead

little progress on documentation with 1.0.1

closing this page as plumbery 1.0.2 has been released


matchParams() utility

A match factory utility to match params (/[user]/[foo?]/) and populate req.params

This library looks nice: https://github.com/snd/url-pattern

I believe this library is better maintained
https://www.npmjs.com/package/path-to-regexp

This is definitely something I can and want to help with 🙂

I believe this library is better maintained https://www.npmjs.com/package/path-to-regexp

According to Express.js documentation, this is exactly the library they use to define regex for path definitions.
They even link a tool for testing paths: http://forbeslindesay.github.io/express-route-tester/

Adding initial router support with #64.

Why not go with the matching pattern as initially proposed: More thinking, route matching could be expensive if we lookup all middleware. Using a router we could also properly throw 404/405 error when route or method are not matching


[JENKINS-58902] Non-user-scoped credentials are not shown when build authentication is configured

Fix CredentialProvider to always gather system credentials when logged user or user associated to run the project by Authrize Project plugin have USE_ITEM permission. This allow a user/admin/devops to create a project and configure it choosing credentialsId between one of possible. Actually no one system credentials is shown also if current and the use selected in Authorize Project plugin have JOB/configure permission.
I did not have change SystemCredentialProvider because in the signature we have only ItemGroup for which is not possible get ACL and query if given authorisation has USE_ITEM permission. This issue happens only on UI because at runtime CredentialsProvider.findCredentialById has already the logic to lookup peeking in mind USE_ITEM/USER_OWN permission when current authentication is not ACL.SYSTEM

[x] Make sure you are opening from a feature branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[x] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

If you agree on approach I can provide some test case.

I am afraid I know next to nothing about user-scoped credentials and cannot meaningfully review this. Generally think it best to avoid them.
Also see #210.

Who is the best person to review this PR.

I am afraid I do not know who has expertise. @jvz? Original creator of user credentials was @stephenc but this is something about usage with authorize-project (which last I recall was abandoned).

authorize-project is free for adoption (maybe for you mean abandoned) but since Jenkins warning you to use at least one QueueItemAuthenticator implementation and there are not much choice... this have to work otherwise the only work around is run job with SYSTEM rights

Not currently comfortable merging any PRs related to user credentials since I do not understand the security model.

rebase master.
There are other 3/4 bugs related to this defect. @jvz could you have a look into this please?

@jtnord please provide some details on how to should be changed the code in the PR to solve all issues related to the current behaviour

@jtnord please provide some details on how to should be changed the code in the PR to solve all issues related to the current behaviour

I do not think you can (and more to the point should) as System credentials must never be able to be used by anything other than System.  if you run your jobs as a user - that includes those jobs.
perhaps start with a discussion on the Jenkins mailing list and / or a Jira ticket.   but accessing System scoped credentials as anything other than System is a non starter for security reasons.

The issue is describe step by step by @ikedam in JIRA.
In my case I'm a Jenkins administrator, when i create new pipeline job and go to configure the SCM as Git, in the credentials combobox I can not see any credentials.
Run a build (policy=run as specific user) it works but THE problem is that I'm not able to configure any credentials using web UI. As pig-around I have to edit the config.xml of the job in jenkins master and than reload the job (very bad practices).

since Jenkins warning you to use at least one QueueItemAuthenticator implementation

Not as of https://github.com/jenkinsci/jenkins/pull/6222.

Yo what up? It appears I don't get notifications from GitHub anymore (probably due to volume).
I'll note that one of the points of user scoped credentials are to separate them from the rest of the system such that they require some level of informed user consent to use said credentials anywhere. If I were to update the design of them today, I'd give each credential an ACL to allow others to use the credential, but that wouldn't really fit too well with the existing API as it's not directly tied to ACLs or any particular authorization model. However, I would generally expect that running a build as a user means having access to said user's credentials (consider it analogous to the RunAsManager in Spring Security where you should be granted all the same authorities as the user, hence that should imply access to their user-scoped secrets). I'm not familiar with how authorize-project works, though.

And system credentials aren't meant to be used by users; they're for the Jenkins system itself (background tasks such as scanning git repos). User scope and system scope should not cross beams as they're entirely unrelated scopes.

I am not sure if there is a miscommunication in this discussion.
Currently when using the "Authorize Project" plugin, and "Run as Specific User" is selected, "Global" scoped credentials under the "System" credential store are unavailable in the UI even when the user in "Run as Specific User" has the global Credentials/UseItem permission. These credentials can still be used in the job, as long as the global "Credentials/UseItem" is given, but they won't appear in the UI. This seems like a bug?
It should not be a security issue to add these into the UI, unless there is already a security issue given that these credentials can already currently be used by the job, they just don't show up in the UI.
The documentation states "Using the GLOBAL scope will, in addition to the usage permitted by SYSTEM scope, will make the credential available to all jobs within Jenkins running as an authentication that has the Credentials/UseItem permission."
The behavior of the job itself follows that, but the behavior of the UI does not.

Looking at this further, JENKINS-58902 and JENKINS-55624 were about the Git plugin. It was the behavior of this plugin I was describing in my last comment, where when using the "Authorize Project" plugin, and "Run as Specific User" is selected, "Global" scoped credentials under the "System" credential store are unavailable in the UI but can be used on clone if the user for "Run as Specific User" has the global Credentials/UseItem permission..
I looked the credentials binding plugin too. This plugin also makes the "Global" scoped credentials under the "System" credential store available, if the user for "Run as Specific User" has the global Credentials/UseItem permission.
For the Git plugin, these lines of code are part of the problem together with how the Credentials plugin works. They use the user's authorization to populate the dropdown in the UI, but the Credentials plugin's SystemCredentialsProvider.getCredentials methods always reject anything other than ACL.SYSTEM.
I am not sure whether the change should belong in the Credentials plugin or the Git plugin, but parts of at least two common plugins seem to believe that "Global" scoped credentials in the "System" store should be accessible to all users with Credentials/UseItem permission. The documentation I quoted above also suggests that.

I agree with the previous comment, the current behavior is a bug.
Global scoped credentials in the System store should be accessible to all users with the Credentials/UseItem permission.
It matches what is present in the documentation:

If you install the Authorize Project plugin and configure a job to run as a specific user, the credentials available to that job will now be determined by that user’s permissions in the context of that job. If the user does not have either Credentials/UseOwn (normally implied by Item/Build) or Credentials/UseItem (normally implied by Job/Configure) then the job will be unable to access any credentials at all.
If a user has Credentials/UseOwn permission in a specific context then they are allowed to use their user scoped credentials for actions performed with their authentication in that context. For example, jobs running as the user’s authentication will have access to that user’s user scoped credentials if and only if the user has Credentials/UseOwn permission in the context of that job.
If a user has Credentials/UseItem permissions in a specific context then they are allowed to use the global scoped credentials for actions performed with their authentication in that context. For example, jobs running as the user’s authentication will have access to the global scoped credentials available in the context of that job if and only if the user has Credentials/UseItem in the context of that job.

I think the current PR is correctly fixing it but should also check for the Credentials/UseOwn permission to permit user scoped credentials to be visible (the same code but not on ACL.SYSTEM but on the current authentication).
If you're still willing to update this PR, I'd be happy to test it and approve it to finally correct this bug!

I do not know what happens but the only way to update this PR is edit the source branch. Push on my repository does not trigger a build and an update of content of the PR


fixadd oss and cos sdk, supported their properties

Proposed changes
add oss sdk, supported oss properties
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

wait for test and add cos

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 39.12 seconds
stream load tsv:          462 seconds loaded<PHONE_NUMBER>9 Bytes, about 154 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          57 seconds loaded<PHONE_NUMBER> Bytes, about 18 MB/s
stream load parquet:          29 seconds loaded 861443392 Bytes, about 28 MB/s
insert into select:          69.2 seconds inserted 10000000 Rows, about 144K ops/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230625130140_clickbench_pr_167234.html


[Event Request] Codeunit 99000832 - Sales Line-Reserve - OnBeforeTransferSaleLineToSalesLine with VAR TransferQty parameter

Dear ALAppExtensions team,
Through this issue we would like to request the event described in #7294, but
also with parameter TransferQty as VAR parameter.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Auto Re-indexing

Is your feature request related to a problem? Please describe.
Currently, there seems to be a gap in the package’s functionality regarding when changes to my Eloquent models in Laravel are not automatically reflected in my Elasticsearch index. This requires manual re-indexing or creating custom solutions to ensure data consistency between my database and Elasticsearch, which is time-consuming and error-prone.
Describe the solution you'd like
I want the package to support an auto re-indexing feature that automatically updates the Elasticsearch index whenever changes are made to the associated Eloquent models. This should include creating, updating, and deleting records. Ideally, this feature would be configurable to allow developers to enable or disable it as needed, and it should work seamlessly with Laravel's event system.
Describe alternatives you've considered
Manual Re-indexing: Running artisan commands or scripts to manually re-index data. This approach is not efficient for real-time applications and increases maintenance overhead.
Custom Event Listeners: Implementing custom event listeners in Laravel to handle model changes and update the Elasticsearch index. While this works, it requires additional development and can lead to boilerplate code that the package could potentially handle internally.
Scheduled Tasks: Setting up scheduled tasks to periodically re-index data. This approach doesn't provide real-time indexing and can lead to stale data between indexing intervals.
Additional context
Auto re-indexing would greatly enhance the usability of this package, particularly for applications with dynamic data. It would also align with Laravel's philosophy of providing elegant and developer-friendly solutions. Below are some screenshots of the current process.

Hey @abdokouta
It may help if I better understand the issues you're running into. IE: the details of what changes happened where, and how they affected the index, what custom solutions do you need to create? Etc. The screenshots mentioned did not show.
Taken at face value, I'll share feedback so long:
Re-indexing is common to ES and the package has the tools available to do it safely albeit manually, the docs outline the steps here along with the checks and balances: https://elasticsearch.pdphilip.com/re-indexing
In terms of auto-reindexing, this seems fraught with danger & inefficiencies since it involves several steps to do it safely. Unless I've misunderstood what you mean by auto, this would be akin to changing a field in a MySQL-based Model and Laravel automatically running the migration to accommodate it. ES will already guess the mapping when it finds a new field and add it to the index, but the issue comes when an existing field mapping needs to change. Further, there would be a considerable overhead to checking mapping versions on every create/update and delete, and should a re-index be triggered, depending on your number of records, this could take several minutes (even hours) to execute.
A reasonable & useful enhancement would be to package the manual steps shown in the docs into an artisan command that calls a 'migration type' file and runs through the process safely. This is in line with Laravel's workflow of managing data in general (via migrations).
If you feel I've missed something please share the issues you're running into in more detail. Thanks

@pdphilip  Thank you for your response! While I haven't used the package yet, I did go through the documentation. Coming from a Magento background, I'm familiar with how well Magento handles indexing and auto-indexing. Magento provides commands to reindex either a specific index or all indexes at once.
Magento also employs a sophisticated reindexing mechanism where it creates temporary indexes to apply the reindexing process. Once the reindexing is complete, Magento replaces the original index with the newly created one and updates the aliases accordingly. This approach ensures that the data is always consistent and available without downtime during the reindexing process.
Similarly, in the Laravel ecosystem, Laravel Scout achieves this with Typesense and Meilisearch, where any addition, update, or deletion of MySQL records is reflected in the index. When it comes to mapping, if you add or modify a field in the database, it's essential to update the Elasticsearch (ES) mapping as well, using ES’s update settings or update mapping methods.
Explanation of Magento Indexing and Reindexing:
In Magento, indexing is a process that converts data (like products, categories, and prices) into index tables, which makes it faster to retrieve and display on the front end. Magento uses indexes to improve the performance of your store by pre-processing complex data and saving it in index tables. For instance, when you update a product price or add a new product, the changes are not immediately visible on the front end until the related index is updated.
How Magento Indexing Works:
Indexing: Whenever data changes (like a product update), Magento needs to process this data so that it can be efficiently retrieved from the database. This processing creates indexes, which are used by the front end to display data quickly.
Modes of Indexing:
Update on Save: Indexes are updated as soon as any change is made to the data. This ensures that the front end always reflects the most recent data, but it may impact performance during data updates.
Update on Schedule: Indexes are updated on a scheduled basis via cron jobs. This mode is more performance-friendly because changes are batched and processed together, but the front end might not immediately reflect the most recent data.
Reindexing in Magento:
Reindexing: Reindexing is required when significant changes are made to your data, like adding a new product attribute or changing store configurations. Magento provides CLI commands (bin/magento indexer:reindex) that allow you to reindex either specific indexes or all indexes. This process regenerates the index tables to reflect the latest data.
Temporary Indexes and Aliases:
Temporary Indexes: During reindexing, Magento creates temporary indexes rather than updating the original indexes directly. This ensures that the current data remains unaffected and accessible to users during the reindexing process.
Replacement and Aliases: Once the reindexing process is complete, Magento replaces the original index with the newly created temporary index and updates the aliases. This seamless switch ensures there’s no downtime or data inconsistency, as the front end always points to the correct and most up-to-date index.
Use Cases for Reindexing:
After adding or modifying product attributes.
After significant changes in pricing rules or categories.
To fix inconsistencies between the data and the index.

Hi @abdokouta,
Appreciate the feature request, but it seems like there's a bit of a misunderstanding about what this package is designed for. laravel-elasticsearch is a low-level package that maps Laravel models to Elasticsearch indices (similar to how Laravel models map to MySQL tables) and allows you to use eloquent queries to administer your Elasticsearch indices directly. It's meant to give developers complete control over indexing (from any source), not automate it.
I'd recommend that you use the package first to understand its scope and utility. For your use case, you can implement it by creating (for example) an IndexedProduct model that extends this package, setting up a hybrid hasOne relationship with your MySQL Product model, and using Observers to manage syncing Product and IndexedProduct records. This allows you to leverage Elasticsearch's features effectively.
Hybrid Relations: https://elasticsearch.pdphilip.com/es-mysql
FYI: Having implemented this solution in many of my own projects I am in the process of publishing a package that does exactly this using this package under the hood. I'll link it to you in here once it's published.
Good luck with your project

@pdphilip thank you for your response, please check these links https://laravel.com/docs/11.x/scout#adding-records, https://github.com/babenkoivan/elastic-scout-driver/blob/master/src/Engine.php

FYI @abdokouta - I have released the following package that does what you're looking to do here: https://github.com/pdphilip/elasticlens