PFB results in panic: UnmarshalJSON cannot decode empty bytes

Summary of Bug
recovered: UnmarshalJSON cannot decode empty bytes
stack:
goroutine 3717 [running]:
runtime/debug.Stack()	/usr/local/go/src/runtime/debug/stack.go:24 +0x65
github.com/cosmos/cosmos-sdk/baseapp.newDefaultRecoveryMiddleware.func1({0x1f63960, 0xc0065ba800})	/go/pkg/mod/github.com/celestiaorg/cosmos-sdk@v1.8.0-sdk-0.46.7/baseapp/recovery.go:71 +0x27
github.com/cosmos/cosmos-sdk/baseapp.newRecoveryMiddleware.func1({0x1f63960?, 0xc0065ba800?})
	/go/pkg/mod/github.com/celestiaorg/cosmos-sdk@v1.8.0-sdk-0.46.7/baseapp/recovery.go:39 +0x30
github.com/cosmos/cosmos-sdk/baseapp.processRecovery({0x1f63960, 0xc0065ba800}, 0xc001344b00?)
	/go/pkg/mod/github.com/celestiaorg/cosmos-sdk@v1.8.0-sdk-0.46.7/baseapp/recovery.go:28 +0x37
github.com/cosmos/cosmos-sdk/baseapp.processRecovery({0x1f63960, 0xc0065ba800}, 0x2d32158?)
	/go/pkg/mod/github.com/celestiaorg/cosmos-sdk@v1.8.0-sdk-0.46.7/baseapp/recovery.go:33 +0x5e
github.com/cosmos/cosmos-sdk/baseapp.(*BaseApp).runTx.func1()
	/go/pkg/mod/github.com/celestiaorg/cosmos-sdk@v1.8.0-sdk-0.46.7/baseapp/baseapp.go:639 +0xf0
panic({0x1f63960, 0xc0065ba800})
	/usr/local/go/src/runtime/panic.go:838 +0x207
github.com/cosmos/cosmos-sdk/x/params/types.Subspace.Get({{0x2d31748, 0xc000f62bf0}, 0xc000122bd0, {0x2d0e170, 0xc000f62e50}, {0x2d0e1c0, 0xc000f62ef0}, {0xc000052600, 0x4, 0x12}, ...}, ...)
	/go/pkg/mod/github.com/celestiaorg/cosmos-sdk@v1.8.0-sdk-0.46.7/x/params/types/subspace.go:110 +0x307
github.com/celestiaorg/celestia-app/x/blob/keeper.Keeper.GasPerBlobByte(...)
	/celestia-app/x/blob/keeper/params.go:36
github.com/celestiaorg/celestia-app/x/blob/keeper.Keeper.PayForBlobs({{0x2d31748, 0xc000f62bf0}, {0x2d0e170, 0xc000f62ea0}, {0x2d0e170, 0x0}, {{0x2d31748, 0xc000f62bf0}, 0xc000122bd0, {0x2d0e170, ...}, ...}}, ...)
	/celestia-app/x/blob/keeper/keeper.go:60 +0x3a8
github.com/celestiaorg/celestia-app/x/blob.NewHandler.func1({{0x2d24c58, 0xc000138020}, {0x2d32158, 0xc006a22680}, {{0xb, 0x0}, {0xc006eec050, 0x9}, 0x19ed, {0xb752ea5, ...}, ...}, ...}, ...)
	/celestia-app/x/blob/handler.go:20 +0x195
github.com/cosmos/cosmos-sdk/baseapp.(*BaseApp).runMsgs(_, {{0x2d24c58, 0xc000138020}, {0x2d32158, 0xc006a22680}, {{0xb, 0x0}, {0xc006eec050, 0x9}, 0x19ed, ...}, ...}, ...)
	/go/pkg/mod/github.com/celestiaorg/cosmos-sdk@v1.8.0-sdk-0.46.7/baseapp/baseapp.go:800 +0x7a8
github.com/cosmos/cosmos-sdk/baseapp.(*BaseApp).runTx(0xc000facfc0, 0x3, {0xc000540f20, 0x141, 0x141})
	/go/pkg/mod/github.com/celestiaorg/cosmos-sdk@v1.8.0-sdk-0.46.7/baseapp/baseapp.go:725 +0xc45
github.com/cosmos/cosmos-sdk/baseapp.(*BaseApp).DeliverTx(0xc000facfc0, {{0xc000540f20?, 0x20?, 0xc00dc7a460?}})
	/go/pkg/mod/github.com/celestiaorg/cosmos-sdk@v1.8.0-sdk-0.46.7/baseapp/abci.go:283 +0x17a
github.com/tendermint/tendermint/abci/client.(*localClient).DeliverTxAsync(0xc0012e7740, {{0xc000540f20?, 0x0?, 0xc0012e7740?}})
	/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.14.0-tm-v0.34.23/abci/client/local_client.go:93 +0x105
github.com/tendermint/tendermint/proxy.(*appConnConsensus).DeliverTxAsync(0xc00def4bc0?, {{0xc000540f20?, 0x20?, 0xb?}})
	/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.14.0-tm-v0.34.23/proxy/app_conn.go:88 +0x26
github.com/tendermint/tendermint/state.execBlockOnProxyApp({0x2d25e10?, 0xc003416cc0}, {0x2d2ffe8, 0xc0011e3b20}, 0xc00163e000, {0x2d329b0, 0xc000130978}, 0x19ec?)
	/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.14.0-tm-v0.34.23/state/execution.go:390 +0x822
github.com/tendermint/tendermint/state.(*BlockExecutor).ApplyBlock(_, {{{0xb, 0x0}, {0xc0033f33d0, 0x7}}, {0xc0033f33d7, 0x9}, 0x1, 0x19ec, {{0xc00c1e5cc0, ...}, ...}, ...}, ...)
	/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.14.0-tm-v0.34.23/state/execution.go:210 +0x171
github.com/tendermint/tendermint/consensus.(*State).finalizeCommit(0xc00136aa80, 0x19ed)
	/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.14.0-tm-v0.34.23/consensus/state.go:1668 +0xb2d
github.com/tendermint/tendermint/consensus.(*State).tryFinalizeCommit(0xc00136aa80, 0x19ed)
	/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.14.0-tm-v0.34.23/consensus/state.go:1576 +0x2ff
github.com/tendermint/tendermint/consensus.(*State).handleCompleteProposal(0xc00136aa80, 0x454?)
	/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.14.0-tm-v0.34.23/consensus/state.go:1957 +0x399
github.com/tendermint/tendermint/consensus.(*State).handleMsg(0xc00136aa80, {{0x2d06580?, 0xc003c70990?}, {0xc002e3f1d0?, 0x0?}})
	/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.14.0-tm-v0.34.23/consensus/state.go:834 +0x1c5
github.com/tendermint/tendermint/consensus.(*State).receiveRoutine(0xc00136aa80, 0x0)
	/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.14.0-tm-v0.34.23/consensus/state.go:760 +0x419
created by github.com/tendermint/tendermint/consensus.(*State).OnStart
	/go/pkg/mod/github.com/celestiaorg/celestia-core@v1.14.0-tm-v0.34.23/consensus/state.go:379 +0x12d
: panic

Originally reported by @renaynay
Version
https://github.com/celestiaorg/celestia-app/releases/tag/v0.12.0-rc6
Steps to Reproduce
Submit a PFB on Arabica with
{"namespace_id": "0c204d39600fddd3", "data": "f1f20ca8007e910a3bf8b2e61da0f26bca07ef78717a6ea54165f5", "gas_limit": 700000, "fee": 2000}

We currently suspect that the GasPerBlobByte param was not defined in the genesis file for the current iteration of the Arabica testnet.

if we just didn't set the param, then the safest quickest thing in this case (single validator node on arabica), would be to hardfork and change the param manually via an upgrade handler esque script

@Bidon15 confirmed that when Arabica was upgraded the param was not.

via an upgrade handler esque script

Are you referring to an x/upgrade plan?

or we submit a proposal to update it via gov

Seems possible via CLI commands draft proposal and submit proposal. I'll look into preparing a proposal.
What are the downsides to creating a new genesis file with the param populated and starting arabica-5 / shutting down arabica-4?

Are you referring to an x/upgrade plan?

we can hack it by just including a script in the binary then switch the only validator with that binary.

What are the downsides to creating a new genesis file with the param populated and starting arabica-5 / shutting down arabica-4?

that's also a very good option!!

Options:

Stop arabica-4. Start arabica-5 with a genesis.json file that includes the param above.
Draft and submit a governance proposal that sets the param on arabica-4. From the validator's account, vote yes on the proposal. Wait until it goes into effect.
Write a manual script in the celestia-app repo that sets the param. Get the script reviewed, merged, and included in the celestia-appd binary. Cut a new release candidate (potentially v0.12.0-rc8). Upgrade the validator on arabica-4 to the new release candidate.

@sysrex we explored option 2 with a legacy governance proposal:
{
   "title":"Parameter change: initialize gas_per_blob_byte",
   "description":" set the gas_per_blob_byte param to 8",
   "changes":[
      {
         "subspace":"blob",
         "key":"gas_per_blob_byte",
         "value":"8"
      }
   ],
   "deposit":"1000utia"
}

We submitted the governance proposal but it failed because we're trying to initialize a parameter that hasn't been registered yet. Ref:

https://github.com/cosmos/cosmos-sdk/blob/8bd9288051d464a93d1101b189d7cb00c53beef1/x/params/types/subspace.go#L212
https://github.com/cosmos/cosmos-sdk/blob/8bd9288051d464a93d1101b189d7cb00c53beef1/x/params/proposal_handler.go#L37

So we're going to try option 1 now.

We expect this to be resolved by deployment of arabica-5 which is scheduled for tomorrow morning.

Submitting PFBs on arabica-5 appears to work.
$ curl -X POST -d '{"namespace_id": "0c204d39600fddd3",
  "data": "f1f20ca8007e910a3bf8b2e61da0f26bca07ef78717a6ea54165f5",
  "gas_limit": 140000, "fee": 2000}' http://localhost:26659/submit_pfb

Output:
{
  "height": 10573,
  "txhash": "E2CD12457D9263C98629B018C3F7C7D68B779FC90EA539462B94EEBB6D7191B3",
  "data": "122A0A282F63656C65737469612E626C6F622E76312E4D7367506179466F72426C6F6273526573706F6E7365",
  "raw_log": "[{\"msg_index\":0,\"events\":[{\"type\":\"celestia.blob.v1.EventPayForBlobs\",\"attributes\":[{\"key\":\"blob_size\",\"value\":\"1\"},{\"key\":\"namespace_ids\",\"value\":\"[\\\"DCBNOWAP3dM=\\\"]\"},{\"key\":\"signer\",\"value\":\"\\\"celestia1vdjkcetnw35kzvtv89ckvepcdpcx6mr2xd4nwur8dp6hydryxph8xdtyxdsnsumrwaekxumtwaksaphpv9\\\"\"}]},{\"type\":\"message\",\"attributes\":[{\"key\":\"action\",\"value\":\"/celestia.blob.v1.MsgPayForBlobs\"}]}]}]",
  "logs": [
    {
      "msg_index": 0,
      "events": [
        {
          "type": "celestia.blob.v1.EventPayForBlobs",
          "attributes": [
            {
              "key": "blob_size",
              "value": "1"
            },
            {
              "key": "namespace_ids",
              "value": "[\"DCBNOWAP3dM=\"]"
            },
            {
              "key": "signer",
              "value": "\"celestia1vdjkcetnw35kzvtv89ckvepcdpcx6mr2xd4nwur8dp6hydryxph8xdtyxdsnsumrwaekxumtwaksaphpv9\""
            }
          ]
        },
        {
          "type": "message",
          "attributes": [
            {
              "key": "action",
              "value": "/celestia.blob.v1.MsgPayForBlobs"
            }
          ]
        }
      ]
    }
  ],
  "gas_wanted": 140000,
  "gas_used": 76252,
  "events": [
    {
      "type": "coin_spent",
      "attributes": [
        {
          "key": "c3BlbmRlcg==",
          "value": "Y2VsZXN0aWExbDlxZmQ4aHBtbGozazdwZ2h1cjRkMG5zNWQzYThzY3dzY3Nrd20=",
          "index": true
        },
        {
          "key": "YW1vdW50",
          "value": "MjAwMHV0aWE=",
          "index": true
        }
      ]
    },
    {
      "type": "coin_received",
      "attributes": [
        {
          "key": "cmVjZWl2ZXI=",
          "value": "Y2VsZXN0aWExN3hwZnZha20yYW1nOTYyeWxzNmY4NHoza2VsbDhjNWxwbmpzM3M=",
          "index": true
        },
        {
          "key": "YW1vdW50",
          "value": "MjAwMHV0aWE=",
          "index": true
        }
      ]
    },
    {
      "type": "transfer",
      "attributes": [
        {
          "key": "cmVjaXBpZW50",
          "value": "Y2VsZXN0aWExN3hwZnZha20yYW1nOTYyeWxzNmY4NHoza2VsbDhjNWxwbmpzM3M=",
          "index": true
        },
        {
          "key": "c2VuZGVy",
          "value": "Y2VsZXN0aWExbDlxZmQ4aHBtbGozazdwZ2h1cjRkMG5zNWQzYThzY3dzY3Nrd20=",
          "index": true
        },
        {
          "key": "YW1vdW50",
          "value": "MjAwMHV0aWE=",
          "index": true
        }
      ]
    },
    {
      "type": "message",
      "attributes": [
        {
          "key": "c2VuZGVy",
          "value": "Y2VsZXN0aWExbDlxZmQ4aHBtbGozazdwZ2h1cjRkMG5zNWQzYThzY3dzY3Nrd20=",
          "index": true
        }
      ]
    },
    {
      "type": "tx",
      "attributes": [
        {
          "key": "ZmVl",
          "value": "MjAwMHV0aWE=",
          "index": true
        },
        {
          "key": "ZmVlX3BheWVy",
          "value": "Y2VsZXN0aWExbDlxZmQ4aHBtbGozazdwZ2h1cjRkMG5zNWQzYThzY3dzY3Nrd20=",
          "index": true
        }
      ]
    },
    {
      "type": "tx",
      "attributes": [
        {
          "key": "YWNjX3NlcQ==",
          "value": "Y2VsZXN0aWExbDlxZmQ4aHBtbGozazdwZ2h1cjRkMG5zNWQzYThzY3dzY3Nrd20vMA==",
          "index": true
        }
      ]
    },
    {
      "type": "tx",
      "attributes": [
        {
          "key": "c2lnbmF0dXJl",
          "value": "eml2QnpZSy9mUWEwbklLUURBYzF2djVKZFNQUEFlK1RJQlJDVTd5dElCd2xpUGxRaVJLNFhKZUVoNXBxdWtaU3JTOHlsOVN4UUZXTWM0b293SFkySEE9PQ==",
          "index": true
        }
      ]
    },
    {
      "type": "message",
      "attributes": [
        {
          "key": "YWN0aW9u",
          "value": "L2NlbGVzdGlhLmJsb2IudjEuTXNnUGF5Rm9yQmxvYnM=",
          "index": true
        }
      ]
    },
    {
      "type": "celestia.blob.v1.EventPayForBlobs",
      "attributes": [
        {
          "key": "YmxvYl9zaXpl",
          "value": "MQ==",
          "index": true
        },
        {
          "key": "bmFtZXNwYWNlX2lkcw==",
          "value": "WyJEQ0JOT1dBUDNkTT0iXQ==",
          "index": true
        },
        {
          "key": "c2lnbmVy",
          "value": "ImNlbGVzdGlhMXZkamtjZXRudzM1a3p2dHY4OWNrdmVwY2RwY3g2bXIyeGQ0bnd1cjhkcDZoeWRyeXhwaDh4ZHR5eGRzbnN1bXJ3YWVreHVtdHdha3NhcGhwdjki",
          "index": true
        }
      ]
    }
  ]
}

Query the data that got posted:
$ curl -X GET 'http://localhost:26659/namespaced_data/0c204d39600fddd3/height/10573'
{"data":["8fIMqAB+kQo7+LLmHaDya8oH73hxem6lQWX1"],"height":10573}%


Return exit code 1 & usage message when an unknown command is passed …

- What I did
Return the usage message and 1 as return code when a bad command is passed to the CLI
- How I did it
remove the empty case on completion switch
call to the command help function
return a error with this format "unknown command: %s", strings.Join(args," ")
- How to verify it

execute the command line docker app, check it displays the usage message & check the return code is 0 with echo $?
execute the command line with an invalid command such as docker app unknown_command, check it displays the usage message & check the return code is 1 with echo $?

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

There is a different behavior between the unknown flag & command, the flag is displayed before the usage message and after for an unknown command (because we need to finish by error to trigger an exit 1)
A solution to have a similar behavior will be to do os.Exit(1) directly without sending the error to the CLI plugin
WDYT?

To be more in line with what the cli is doing we should maybe:

write a message like 'titi' is not a docker app command
not print out the help

The cli does this:
$ docker asdf
docker: 'asdf' is not a docker command.
See 'docker --help'


Enable screenshots, resizing and videos in child windows

We should enable window management actions for child windows.

Any update on this? Would love to be able to resize an opened window.

Yes, I'm also watching this issue and would love to hear if there are any updates.

@jornncc @itrusevich
Resizing and screenshots will be available in Chrome with the next TestCafe release.

@AlexKamaev great, thank you for the update!

https://github.com/DevExpress/testcafe/issues/5017
The feature is shipped with<EMAIL_ADDRESS>


Set time zone through environment variable

Currently, timezone and localtime files must be mounted to set the correct time zone.
Adding the tzdata package to the Alpine Linux base image will let the time zone be set through the env var TZ.

Thanks, that's a good point. I'll have to check if there was some reason why the tzdata package isn't already included in the list of packages that get installed, did this possibly change in some Alpine version along the way or did I just somehow manage to miss the interaction between the tzdata package and the TZ env.

Thanks @vergoh, much appreciated!


[backport] Fix F632 (use ==/!= to compare str)

Backport of #6346

[automatic post] Jenkins, test this please.

I dropped the change to requirements in setup.py, as well as changes irrevelant to v5.

Jenkins CI test (for commit e80460d41250c184c9db341c8e068ee7083f9fca, target branch v5) succeeded!


[BUG] Project creator doesn't work

Describe the bug
Running the create-next-app command fails  with
Could not locate the repository for "https://github.com/frontegg/frontegg-nextjs/tree/main". Please check that the repository exists and try again.

To Reproduce

Open a terminal
Run project creator command npx create-next-app --example "https://github.com/frontegg/frontegg-nextjs/tree/main" --example-path "apps/example" my-nextjs-app-name

Expected behavior
A new next project with frontegg is created
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

@zgagnon now its fixed!

https://github.com/frontegg/frontegg-nextjs/pull/42
כןסק


How to use locust to test the server program of tcp and udp protocols?

How to use locust to test the server program of tcp or udp or tcp + udp protocols?
At present, there is little information about this kind of information on github and youtube.
I am a new user. I hope there will be more official examples and personal sharing.
Thanks again for all your work !

I remember seeing some attempts on SO and other places, but unfortunately I dont have a good reference to give.

thank you


Blue Ribbon Panel List

Determine, contact, and test SHR with key medical, policy, epatient advocates.

I recommend we invite Abraham Verghese. He's a proponent of teaching the history and physical exam to medical students, and would have a vested interest in ensuring that our data model doesn't sacrifice the unique diagnostic skills of a well trained physician-as-sensor.
http://www.nytimes.com/2010/10/12/health/12profile.html?_r=0

Second that concept and that guy

CAPT Denise Koo, MD, MPH, USPHS is Senior Advisor to the Assistant Director for Policy at CDC. She is the leading authority within CDC on leveraging social determinants to improve health and for integration between public health and primary care. And a personal connection of mine.

Steven Woolf, MD, MPH, professor of Family Medicine and Population Health at VCU, and director of the Center for Society and Health. Leading researcher in SDOH. Editor of the IOM/NAM report U.S. Health in International Perspective: Shorter Lives, Poorer Health (2013)
http://www.nap.edu/catalog/13497/us-health-in-international-perspective-shorter-lives-poorer-health


Use BioImage.IO RDF spec

Not sure exactly, but won't it be great if you can adopt our RDF spec: https://github.com/bioimage-io/spec-bioimage-io/blob/gh-pages/rdf_spec_latest.md for the notebook yaml file? The only required fields are type, format_version, name and description, for example, this notebook rdf file will be like this:
source: https://raw.githubusercontent.com/HenriquesLab/ZeroCostDL4Mic/master/Colab_notebooks/Cellpose_2D_ZeroCostDL4Mic.ipynb # <-------------change to source
requirements_url: https://raw.githubusercontent.com/HenriquesLab/ZeroCostDL4Mic/master/requirements_files/Cellpose_2D_requirements_simple.txt
cuda_version: 11.8.0
ubuntu_version: 22.04
python_version: 3.10
sections_to_remove: 1.1. 1.2. 2. 6.3.
version: 0.1.0
description: "Cellpose_2D_DL4Mic is the conversion of the CellPose 2D notebook from ZeroCostDL4Mic."
name: "Cellpose 2D DL4Mic" # <------------added name
format_version: "0.2.3" # <-------------added format version
type: "application"  # <-------------added type
tags: ["notebook", "ZeroCostDL4Mic"]  # <-------------added tags with notebook

Like this we will be able to list it in the model zoo, if that's useful at all.

Thank you Wei! Yes, this was the idea :D We are thinking on a strategy to get ZeroCostDL4Mic synchronised with this and the zoo to avoid duplication and generate/update it automatically. I hope to have something the following days

This is done already :)


Node 4.4

Fixes #453 in attempt to fix #551.
Still work in progress -- gets the donation request working, which does still take a while... but comments out sendSuccessMessages for now.

It works!


{'info': 'unique_modify() got null op.orm_modlist', 'desc': 'Invalid syntax'}

It raises if I click on SAVE AND CONTINUE, in model admin, without any changes on fields.
If I change some fields it works without any error.
context:
Django 2, django-ldap master branch from git

Fixed in PR https://github.com/django-ldapdb/django-ldapdb/pull/152
I Close this, I hope that you'll enjoy my PR and merge in your master branch the changes I've done.

Hi @rbarrois, have you a vision about how to solve this issue?
I can code but I do not want to waste time to an approach that could sound wrong to you.
What you think we should do in terms of design to fix this?
My approach in PR https://github.com/django-ldapdb/django-ldapdb/pull/152 works but is not enough

@peppelinux this should be fixed now; let me know if you still see the issue.

Yes, it's fixed with that code, I wrote it almost a month ago and I'm wondering why you have not accepted my PR but you used the same code.  I'm widening my eyes :)
There are also some other questions and purpose regarding this beautiful project, can you accept community contributions and in which terms?

@peppelinux Thanks for the feedback :)
I'm totally open to contributions from the community, whatever their form (code, bug reports, documentation, etc.) — which you've already helped with :smiley_cat:
Regarding code contributions, I'm sorry I didn't merge your PR without any explanation, I didn't want to seem rude :crying_cat_face:
I didn't merge it directly for a couple of reasons: the main one was that I was going using the EuroPython sprints session to go through the backlog of issues, trying to fix as many as possible — and didn't take enough time to review all suggested options; the other reason is that your PR mixes lots of different things, which makes it much harder to review for me.
In order to make it easier to get community contributions in, I do intend to write a "contribution guide" soonish, which would make it clearer how best to contribute code to the project — in a few words, it would be: open an issue to explain the problem that needs fixing; state in the PR's subject what approach has been taken; include a test reproducing the issue that is being fixed; include a ChangeLog entry; don't mix features in the same PR.

Yes, rude is the word :)
I admit that I should rebase my commits and create separate branches for every pull requests but I went fast to put my integrations in my production environment and I didn't thought that a single PR could take so much time.
btw I'll merge your commits into my fork and, actually, only the MultiValuefield with the TextField JS autosize (js) will be merged if you agree. There are some other purposes that I did not put in my PR because of your silence and also because I dunno if they are interesting for you. They are described into PR and issues posts.
I think that this could be helpfull for the project.
Let me know if it is interesting for you:

MultiValueField (we could also make it works like a ListField but with multiline in TextField only in AdminModel)
https://github.com/django-ldapdb/django-ldapdb/pull/152/

Password encoding selection menu, I use it in procduction, is well tested and omni cohomprensive of all the slapd encoding algorithms.
https://github.com/django-ldapdb/django-ldapdb/pull/46#issuecomment-406627651
https://github.com/django-ldapdb/django-ldapdb/issues/162

Let's compare our ideas, I'll rebase my PR and I'll keep all in the way that you prefer if my contributions will be taken seriously into consideration. Do you enjoy these? I'll wait for your ideas, then we'll decide what we should merge first and then I'll lfollow your indications to get thm merged in the main official branch. I would like to emprove my experience with the help of the community, I think that it could be helpfull in time.


How to calculate coverage？

AFL is a classic fuzzer. There are many studies based on AFL. However, my known work does not explain how to calculate coverage.
I use llvm mode for instrumentation. Accumulate the inst_blocks in afl_llvm_pass.so.cc as the total number of instrumentation. Use ((MAP_SIZE << 3)-count_bits(virgin_bits)) as the number of positions covered in the code. However, the results did not meet expectations.
If anyone knows how to get the coverage, can I trouble you with some suggestions? Thank you!

https://github.com/mrash/afl-cov

@walter708 But afl-cov only supports gcc, and I want to collect the coverage of chakracore compiled by afl-clang-fast. So I use Clang's SOURCE-BASED CODE COVERAGE to collect coverage, but I found that when there are many running files, it cannot be calculated. So is there any other way?

The afl-cov fork by @vanhauser-thc works with llvm.
https://github.com/vanhauser-thc/afl-cov

The afl-cov fork by @vanhauser-thc works with llvm.
https://github.com/vanhauser-thc/afl-cov

Because if afl runs for a long time, it will generate tens of thousands of files. Does this version of afl-cov support processing a large number of files?


Update the code.

Can you please update to the latest version of the main fork. Some things have changed and I(and possibly others) wish to use them.

I'll take a look. I haven't played Palworld in a long time, but I can take a look at updating the everything.


[schemaregistry-avro] upgrade dev dependency stream to ^0.0.3

and update pnpm-lock.yaml
Resolves issue https://github.com/Azure/azure-sdk-for-js/issues/30249

API change check
API changes are not detected in this pull request.


clarified specialties

:warning: Validation status: warnings

File
Status
Preview URL
Details

advocates/seth-juarez.yml
:warning:Warning
View
Details

advocates/seth-juarez.yml

[Warning] the value Profile is undefined for metadata pagetype

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


add dependabot config script

Inspired by https://github.com/kubeflow/pipelines/issues/4682  I created a script that will create a config file for depandabot so that it knows what directories to scan. It will scan the repository for files named *ockerfile*, package*.json, *requirements.txt and go.*.  It is setup for dockerfiles, npm packages, pip dependencies and gomod at the moment. It is trivial to further customize what folders are selected if further customization is needed. It also parses the closest OWNERS file for a given dependency listing file, and assigns the relevant approvers and adds the relevant reviewers to the PRs it creates.
This is a sibling PR to https://github.com/kubeflow/pipelines/pull/5015, https://github.com/kubeflow/kubeflow/pull/5542, https://github.com/kubeflow/kfserving/pull/1309, https://github.com/kubeflow/arena/pull/403, https://github.com/kubeflow/testing/pull/855, https://github.com/kubeflow/fairing/pull/550, https://github.com/kubeflow/kfp-tekton/pull/432, https://github.com/kubeflow/katib/pull/1420, https://github.com/kubeflow/tf-operator/pull/1224, https://github.com/kubeflow/kfp-tekton-backend/pull/28, https://github.com/kubeflow/mpi-operator/pull/319, https://github.com/kubeflow/pytorch-operator/pull/315, https://github.com/kubeflow/metadata/pull/255, https://github.com/kubeflow/xgboost-operator/pull/107, https://github.com/kubeflow/fate-operator/pull/26, https://github.com/kubeflow/mxnet-operator/pull/87 and https://github.com/kubeflow/website/pull/2459.
As it stands now, I am not yet sure how many PRs will be created with this configuration, as dependabot has not yet started scanning my fork.
For reference, the PRs that will be created can be found here: https://github.com/DavidSpek/kfctl/pulls

/assign @patrickxys

/assign @patrickxys

I am holding the PR to have some control over when it gets merged so that the optional test infra doesn't get overloaded if all the repo's were to merge this at the same time.
/hold

I am holding the PR to have some control over when it gets merged so that the optional test infra doesn't get overloaded if all the repo's were to merge this at the same time.
/hold


Problem with failing primitiveStringHash? | Cannot load metacello.sar

I tried to file in this metacello.sar in two images, Squeak5.3-19448-32bit.image and a fresh 64-bit Trunk image. In each case, I get the following error message while the preamble of the SAR file is processed:
MessageNotUnderstood: ByteString>>bitAnd:
ByteString(Object)>>doesNotUnderstand: #bitAnd:
ByteString(String)>>hashWithInitialHash:
ByteString>>hashWithInitialHash:
MCMethodDefinition>>hash
Set>>scanFor:

A closer look at the temporary variables causes confusion:

in String>>hashWithInitialHash: and below, speciesHash contains the receiver
in MCMethodDefinition>>hash, hash is nil
When I restart from MCMethodDefinition>>hash and step over all sends, the error does not occur
But when I restart and step over from the sender of this context (Set>>scanFor:), the error occurs again

So, is there a bug in primitiveStringHash that probably misaligns the stack variables in any way? Interesting bug ...
PS: Please let me know if you can reproduce it.

No sure what's going on, but the implementation of primitiveStringHash is generated and looks ok:
https://github.com/codefrau/SqueakJS/blob/3538c55eb66355a137554aa218e0ffccc3d7575c/plugins/MiscPrimitivePlugin.js#L544-L574

That primitive looks buggy, because it is called with argCount = 1 so it should pop 2 (string+arg) but actually pops 3.
What does it do in other VMs? Are they using argCount? This was generated many years ago, but I don't think the primitive changed?

That primitive looks buggy, because it is called with argCount = 1 so it should pop 2 (string+arg) but actually pops 3.
What does it do in other VMs? Are they using argCount? This was generated many years ago, but I don't think the primitive changed?

OMG this must have been wrong since 2014. I just tried it with
primitiveStringHash(argCount) {
   ...
   interpreterProxy.popthenPush(argCount + 1, hash);
}

and metacello.sar installs correctly.
However, that means some other generated primitives are likely wrong too 🤔 I have not committed a fix yet.
Thank you for the test case!

OMG this must have been wrong since 2014. I just tried it with
primitiveStringHash(argCount) {
   ...
   interpreterProxy.popthenPush(argCount + 1, hash);
}

and metacello.sar installs correctly.
However, that means some other generated primitives are likely wrong too 🤔 I have not committed a fix yet.
Thank you for the test case!

So ca63f69 checks the stack after every primitive.
And 4e152a6 fixes an embarrassing number of primitives that left the stack imbalanced or at least did not check argCount.
Released as 1.0.1.

So ca63f69 checks the stack after every primitive.
And 4e152a6 fixes an embarrassing number of primitives that left the stack imbalanced or at least did not check argCount.
Released as 1.0.1.

So ca63f69 checks the stack after every primitive.
And 4e152a6 fixes an embarrassing number of primitives that left the stack imbalanced or at least did not check argCount.
Released as 1.0.1.

This is always fun :D

So ca63f69 checks the stack after every primitive.
And 4e152a6 fixes an embarrassing number of primitives that left the stack imbalanced or at least did not check argCount.
Released as 1.0.1.

This is always fun :D

Great, thanks for fixing! :D

So ca63f69 checks the stack after every primitive.

Out of curiosity, how large is the performance impact of such "assertions in production"? :-)

Great, thanks for fixing! :D

So ca63f69 checks the stack after every primitive.

Out of curiosity, how large is the performance impact of such "assertions in production"? :-)

@LinqLover please use the vm-dev list for this kind of question/discussion. Nobody’s gonna read through closed tickets ;)

@LinqLover please use the vm-dev list for this kind of question/discussion. Nobody’s gonna read through closed tickets ;)


cmd/kubectl-gadget: Implement tools-mode flag per gadget

The deploy command has a "tools-mode" flag that indicates which kind of
gadgets to use. The container entrypoint script has some logic to
determine the kind of tool to use when this is "auto". This logic
it not totally precise and some gadgets could not support the core
mode in some cases even if that logic indicates so.
In order to avoid the user having to redeploy IG, this commit adds a new
flag to each tool, so the user can choose the mode each time the tool is
run.
The previous existing "tools-mode" flag on the deploy command is renamed
to "default-tools-mode" as this can be useful to avoid having to pass
the mode each time a tool is executed.

Fixes https://github.com/kinvolk/inspektor-gadget/issues/349

BTW, I was wondering if we should execute the integration tests twice, one with standard and another with core mode. WDYT?

Possible, it should be a matter of adding a matrix to integration tests.
But maybe we will need to tweak some tests as I never run the tests with CORE tools, so it is highly possible some will not give the exact same output and we will need to differentiate tests between CORE and standard.

BTW, I was wondering if we should execute the integration tests twice, one with standard and another with core mode. WDYT?

Possible, it should be a matter of adding a matrix to integration tests. But maybe we will need to tweak some tests as I never run the tests with CORE tools, so it is highly possible some will not give the exact same output and we will need to differentiate tests between CORE and standard.

The output shouldn't change, the possible problem would be that some BCC gadgets do not have a core version but I think @mauriciovasquezbernal already managed it by internally forcing standard mode for those ones.

I've been thinking about this PR a bit more and I'm not sure if this is really a good change. I think the concept of "standard" and "core" gadgets is an internal implementation detail and probably we shouldn't expose this to the user. The initial idea of this flag was to let the user fallback to standard tools if something was wrong with the core ones. I think we could implement that fallback automatically: i.e. always try to use the core version and fallback to the standard one if something goes wrong. I experimented this idea here and it worked fine. We can always add this flag if we found this useful in the future, but I won't do it now.
Any comments on this?

After discussing internally we think it makes sense not to move forward with this PR. We'll continue the approach taken in https://github.com/kinvolk/inspektor-gadget/pull/438 as it seems to be better.


After upgrading to flutter 3,i can't build my app this error message keep coming up

e: /media/trinity/E24E79554E792387/folders/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_paystack-1.0.5+1/android/src/main/kotlin/co/paystack/flutterpaystack/FlutterPaystackPlugin.kt: (48, 62): Type mismatch: inferred type is Activity? but Activity was expected
e: /media/trinity/E24E79554E792387/folders/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_paystack-1.0.5+1/android/src/main/kotlin/co/paystack/flutterpaystack/MethodCallHandlerImpl.kt: (19, 37): Type mismatch: inferred type is BinaryMessenger? but BinaryMessenger was expected

iOS works though

Yes got same issue
e: /Users/isaacadariku/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_paystack-1.0.5+1/android/src/main/kotlin/co/paystack/flutterpaystack/FlutterPaystackPlugin.kt: (48, 62): Type mismatch: inferred type is Activity? but Activity was expected
e: /Users/isaacadariku/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_paystack-1.0.5+1/android/src/main/kotlin/co/paystack/flutterpaystack/MethodCallHandlerImpl.kt: (19, 37): Type mismatch: inferred type is BinaryMessenger? but BinaryMessenger was expected

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':flutter_paystack:compileDebugKotlin'.
> Compilation error. See log for more details

i have same error

Any one have the issue, before they fix it. Change your flutter_paystack: line to this.
  # Temporarily using this until we can resolve the issue with the plugin.
  # Issue is: https://github.com/wilburt/flutter_paystack/issues/117
  flutter_paystack:
    git:
      url: https://github.com/definitelyme/flutter_paystack.git
      ref: a4a33c3dd0a12f46d655a2e63d11e9f20ba82d01

same error in some another packages

Any one have the issue, before they fix it. Change your flutter_paystack: line to this.
  # Temporarily using this until we can resolve the issue with the plugin.
  # Issue is: https://github.com/wilburt/flutter_paystack/issues/117
  flutter_paystack:
    git:
      url: https://github.com/definitelyme/flutter_paystack.git
      ref: a4a33c3dd0a12f46d655a2e63d11e9f20ba82d01

same error in some another packages
I think it's relation with kotlin file
thanks in advance

Any one have the issue, before they fix it. Change your flutter_paystack: line to this.
            ![Save to Pieces](chrome-extension://igbgibhbfonhmjlechmeefimncpekepm/save_button.svg)

        ```

Temporarily using this until we can resolve the issue with the plugin.
Issue is: https://github.com/wilburt/flutter_paystack/issues/117
flutter_paystack:
git:
url: https://github.com/definitelyme/flutter_paystack.git
ref: a4a33c3dd0a12f46d655a2e63d11e9f20ba82d01

same error in some another packages I think it's relation with kotlin file or something like that thanks in advance

Yes, the new upgrade affect those files, but since you have pass through Paystack issue, you can check the other package if there is a solution over there.

Any one have the issue, before they fix it. Change your flutter_paystack: line to this.
  # Temporarily using this until we can resolve the issue with the plugin.
  # Issue is: https://github.com/wilburt/flutter_paystack/issues/117
  flutter_paystack:
    git:
      url: https://github.com/definitelyme/flutter_paystack.git
      ref: a4a33c3dd0a12f46d655a2e63d11e9f20ba82d01

@isaacadariku This works fine for me, was having the same issues after upgrading to 3.0 but after using this it builds successfully thanks.

This Solution is awesome for now ..
Thank You so much for this

This should be fixed in 1.0.6. Can you update the package version?


requirements.txt

Hello, can you send me  dependencies file that you have configured？
gensim==1.0.1
matplotlib==2.0.0
nltk==3.2.2
numpy==1.12.1
pandas==0.19.2
scikit_learn==0.18.1
I didn't find the library file.   My email address is<EMAIL_ADDRESS>  thank you

Hey you can download it from here. And to install the dependencies run:
$ pip install -r requirements.txt


Update getting-started.md

Missing an less-than symbol for the closing anchor tag on line 158.

Fixed in b159246.


pytho310Packages.pyunifiprotect: Enable more tests

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Could we not fix the build more simply by having home-assistant override the pydantic dependency in its local package overrides to set it back to 1.9.0? This might require ongoing maintenance if pydantic is updated for subsequent versions without fixing the bug, but reverting it to 1.9.0 in the local package overrides is really easy and would unblock it for now.

@onny Hey - trying to build your changes but you're missing ffprobe-python from your repo.
I see the reference to it but not the actual package directory itself - maybe a .gitignore slipped in or something?

Could we not fix the build more simply by having home-assistant override the pydantic dependency in its local package overrides to set it back to 1.9.0? This might require ongoing maintenance if pydantic is updated for subsequent versions without fixing the bug, but reverting it to 1.9.0 in the local package overrides is really easy and would unblock it for now.

I am leaving this to the home-assistant people how to handle this but since pythonPackages can only have one version we are doing to stick with this for now.


Add support for transformations for getInitialProps

Feature request
Is your feature request related to a problem? Please describe.
Next is unable to handle data types that are not pure JSON. The most common use case is a Date but in order to use it in Next, we have to manually convert values to pure JSON (a string representation of a date or ms from epoch) on the server, fetch them as JSON in getInitialProps then transform them somewhere in the Component.
Describe the solution you'd like
Add a transformInitialProps callback that transforms pure JSON props into any JavaScript object.
For example, if we fetch a date range from the server encoded as ms we might have a transformInitialProps like this:
Home.transformInitialProps = function({startDate, endDate}) {
  return {
    startDate: new Date(startDate),
    endDate: new Date(endDate)
  }
}

This gets much more interesting and much more powerful if you can add it to all pages automatically. Maybe we can have a way to add it to the _document.js page.
Document.transformInitialProps = function(props) {
  return EJSON.fromJSONValue(props)
}

EJSON is a library that automatically supports dates in JSON through an encoding and also allows you to extend it to support any custom data type you like. It was originally designed for Meteor which also had to deal with shipping dates from server to client.
NextJS doesn't have to be opinionated about using EJSON but this gives everybody the option to support the date type and other custom types. The beauty is that you don't have to write custom transformInitialProps functions for each page if you can set a global one. Then you just make sure to encode everything in a standard JSON compatible encoding like EJSON.
Describe alternatives you've considered
Do the conversion somewhere in the component. The problem is having redundant code on every page. Easy to make mistakes. Not as clean because it doesn't feel standardized.
Additional context
A few thoughts:

When first using NextJS, the inability to pass date values which is common since it's a base type in databases felt like a bug. Having an immediate way to help people and provide an example in the documentation could alleviate that feeling.

NextJS is opinionated about some things. Might be worthwhile to consider one day adding EJSON support as a default so we get built-in date support. That's just a thought for the future though. I think the immediate value is to add without built-in EJSON support. Others might prefer other encoding schemes.

We're not planning to change the way that getInitialProps works at this point. Introducing another static method would introduce more complexity for users for very minimal benefit (eg using Date which can be generated in other ways).


[fix]cms: article seed data

Coverage increased (+0.09%) to 84.933% when pulling 0f726b0141e4678778eff67d4a86d1e5f6a09039 on fix-cms_article_seed into 706701cd79ab07daadd6570099ce5b07f63206a2 on master.


Unable to finish CLI processing for certain images

Hi @nathanhillyer,
I am trying to extract features for an image/mask combination as follows:
inputMask.nii.gz
inputImage.nii.gz
But the following command did not work:
collage_cli + " -i " + inputImage + " -m " + inputMask + " -s 1 -b 20 -o " + outputCSV

With the following output:
collage_output.log
And this is the traceback:
Traceback (most recent call last):
  File "collageradiomicscli.py", line 93, in <module>
  File "click\core.py", line 829, in __call__
  File "click\core.py", line 782, in main
  File "click\core.py", line 1066, in invoke
  File "click\core.py", line 610, in invoke
  File "collageradiomicscli.py", line 44, in run
  File "collageradiomics.py", line 602, in execute
ValueError: could not broadcast input array from shape (3,3,5,13,2) into shape (5,5,5,13,2)

However, full-size images work fine. Could you please help? I am guessing this might be as simple as including some error-checking on my side.
Cheers,
Sarthak

@sarthakpati Thanks for the report and attaching the image + mask, looking into this.

@nathanhillyer: any update on this?

@sarthakpati I mistakenly thought this was resolved when I saw https://github.com/CBICA/CaPTk/issues/1288 merged.
My fault, we're looking into this now.

I think the problem here is the mask is too big. It encompasses the whole image and our dominant angle calculation is not accurate at the edges. So the mask should be with the image minus svd_radius*2+1 (diameter).
I think adding error checking on both yours and our end will resolve this.
But I'm going to sync up with the team to make sure I'm not missing something here. Thanks for your patience!

I think the problem here is the mask is too big. It encompasses the whole image

We will have a lot of cases where the mask will span the entire image [ref]. In fact, I am seeing similar behavior for exceedingly small masks as well (in the order of a few voxels in an image of 240x240x155).

But I'm going to sync up with the team to make sure I'm not missing something here.

Thanks!

We can reduce the mask size automatically in the case where it spans the whole image and still have the statistics compute.
We are also going to implement a minimum size for the images. Pallavi and Satish highly recommend leaving the svd radius as 5, which would mean the image would ideally be 50x50 minimum in the x, y dimensions. We'll talk with them this week and see how they want to handle small images.

Cool. It would be great to not give a compute failure for smaller images and make adjustments internally. Let me know how I can help!

@sarthakpati I talked with Pallavi & Satish and we're going to make a minimum size for images going through collage. We can't in good faith compute statistics for images under 50x50 and have dependable results. We'll update the error message accordingly, and suggest leaving collage radiomic features out of smaller images.
They also highly discourage running a mask that is the entire image size. Our algorithm is computationally expensive and doesn't scale well to full images. It's much better to target a certain area or areas. As it looks like your image pipeline is setup for full images in some cases already, we suggest leaving collage out for those cases, as it's not the intended use case. We ruled out supporting a full image mask because we don't want to encourage such usage.
We can make helper methods (if we don't have them already) where you can pass a minX, maxX, minY, maxY, and have collage run over a passed in smaller region if you want these full images to be ran. Would that work?

We can't in good faith compute statistics for images under 50x50 and have dependable results. We'll update the error message accordingly, and suggest leaving collage radiomic features out of smaller images.

Completely fair.

They also highly discourage running a mask that is the entire image size

We cannot control the mask that the user is providing, to be honest. If they choose to provide a full image mask, we are obliged to do the computation. Additionally, the lattice computation (the part of the pipeline where we are seeing this particular behavior) is the one where we are splitting the main input image into a bunch of smaller images (which consequently can have the full mask, depending on where they are sourced from).

We can make helper methods

Thank you, but I doubt we will be able to do much with them. I will simply disable Collage processing for smaller images. Is there a minimum size that I should be looking at?

We cannot control the mask that the user is providing, to be honest. If they choose to provide a full image mask, we are obliged to do the computation. Additionally, the lattice computation (the part of the pipeline where we are seeing this particular behavior) is the one where we are splitting the main input image into a bunch of smaller images (which consequently can have the full mask, depending on where they are sourced from).

If a bigger image is being split into a bunch of smaller images, and the size of each of the smaller images is not huge (think in the order of typical tumor sizes), COLLAGE will run in a reasonable amount of time. The problem is if one tries to run COLLAGE on an entire 256 x 256 (or larger) image in one shot, computing gradient co-occurrences etc will take way too long.. since these are done within sliding window neighborhoods. Does that make sense?

Thank you, but I doubt we will be able to do much with them. I will simply disable Collage processing for smaller images. Is there a minimum size that I should be looking at?

Like Nathan mentioned, I suspect 50 x 50 is a reasonable minimum. For reference, we have typically run COLLAGE on ROIs that are the size of a tumor + peritumor annotation where it executes in a reasonable amount of time (trying to give you a sense of the ROI sizes that we have been working with).

We cannot control the mask that the user is providing, to be honest. If they choose to provide a full image mask, we are obliged to do the computation. Additionally, the lattice computation (the part of the pipeline where we are seeing this particular behavior) is the one where we are splitting the main input image into a bunch of smaller images (which consequently can have the full mask, depending on where they are sourced from).

If a bigger image is being split into a bunch of smaller images, and the size of each of the smaller images is not huge (think in the order of typical tumor sizes), COLLAGE will run in a reasonable amount of time. The problem is if one tries to run COLLAGE on an entire 256 x 256 (or larger) image in one shot, computing gradient co-occurrences etc will take way too long.. since these are done within sliding window neighborhoods. Does that make sense?

Absolutely, just that we have no control over how a user will initialize this and would want to run their experiment. The same holds true for other texture-based features getting extracted using CaPTk, BTW.

Thank you, but I doubt we will be able to do much with them. I will simply disable Collage processing for smaller images. Is there a minimum size that I should be looking at?

Like Nathan mentioned, I suspect 50 x 50 is a reasonable minimum. For reference, we have typically run COLLAGE on ROIs that are the size of a tumor + peritumor annotation where it executes in a reasonable amount of time (trying to give you a sense of the ROI sizes that we have been working with).

I can set that as the minimum for COLLAGE computation on my end.

@nathanhillyer based on what Sarthak is saying, I am thinking we should only specify a minimum size for running COLLAGE (since that is based on real constraints of what the feature means). If the mask is the size of the entire image, we should probably just pop up a strident warning and let the end-user deal with the consequences of a looooong execution time.

@satishev Okay, works for me! We'll update to 50x50 as the minimum size, and make some tweaks that allow a fully masked image to be computed.

@sarthakpati These two issues are resolved in version 0.3.0 which will be on PyPi shortly.


Define Annotator interface and related factory

Add annotator interface
Add general AnnotatorException type
Add KeyInfo class as a java bean
Add SignatureInfo class as a java bean
Implement MockAnnotator which is used in unit tests
Implement and expose AnnotatorFactory class
Implement all related unit tests

Fix #33
Signed-off-by: Karim Elghamry<EMAIL_ADDRESS>

Rebased with latest main updates in c0bafdffb4ebe975d7f56b98ce49a2bf5e14f303

changed from make to execute in ca463faac57844822760441a6a1911874ac9fd35 and rebased.


Sticky header for only one section (not first section header)

Is there a simple way to only have one section header be sticky, and have all other section headers float with the content?
Specifically, say I have three header sections in my collection view. I want the 1st and 3rd section header to float. However, I want the second header to stick.

I have the same issue, any advice?

I ended up using the native iOS sticky header implementation. To make this work, I used multiple sections. The important detail to know is that section headers with no content do not stick whereas headers with content do stick.


Fix docstring typos pointing to incorrect events

Summary
Corrected the docstrings for StartingEvent and StoppingEvent, both of which suggest the use of themselves over StartedEvent and StoppedEvent respectively.
Checklist

[x] I have run nox and all the pipelines have passed.
[ ] I have made unittests according to the code I have added/modified/deleted. (N / A)

Related issues
None

Great catch, thank you!


Jax solver mode: only include output variables

Description
This continues #2796 for the JaxSolver.
Motivation
For parameter estimation, it is (computationally) benefitical to store only the required output variables.
This issue also aims to provide functionality for jit-compiled parameter estimation or optimisation workflows. At the moment this isn't possible since the creation of the ProcessedVariable dict is completed with Casadi. Further discussion here: https://github.com/pybop-team/PyBOP/pull/25
Possible Implementation
No response
Additional context
No response

Hi, @BradyPlanden – you had mentioned that #3658 should have closed this issue, but I think we forgot to do so. Should we close this now?

Yep, marking closed.


Limit concurrent HTTP/2 Streams

Meta issue: #2627
Proposal for two limits: 1) max streams per connection and 2) max total streams.
1 maps to SETTINGS_MAX_CONCURRENT_STREAMS.
The spec default is unlimited.

Spec suggested minimum: 100
Nginx default: 128 http://nginx.org/en/docs/http/ngx_http_v2_module.html#http2_max_concurrent_streams
Apache default : 100 https://httpd.apache.org/docs/2.4/mod/mod_http2.html
IIS/Http.Sys default?


Translation completed

The translation needs some fixes - I will merge this into testnet for now, but it needs polishing before mainnet. Feedback has been sent via DM on Discord.


No Referrer Request Header in form post

Hi,
we have an issue with our implementation using the embedded method. Everything is working great in sandbox mode but once we remove sandbox and switch to live we get...
'505 You cannot use this service from there null Please contact the merchant.'
Looking at the request headers for the form data post to https://pay.elavonpaymentgateway.com/pay we can see Origin: null. Also no referrer header is present in the headers. Is this causing the 505 error?
Anyone ran into this issue or know of a solution?
Thanks for any help.

@MathewWoodhall - Did you solve this?  I have exactly the same issue.

@MathewWoodhall - Did you solve this? I have exactly the same issue.

I came up with the following work around which has been fine for us for the past few months. If I remember right the issue stems from the iframe needing a src attribute(without one the referrer and origin will not be sent with the initial request to https://pay.elavonpaymentgateway.com/pay) so we changed the iframe html to:
<iframe id="targetIframe" src="assets/loading-iframe.html" (load)="innitHPP()"></iframe>

and loading-iframe.html has the following content:
<!doctype html>
<html>
	<head>
		<meta name="referrer" content="origin">
	</head>
	<body>
		Loading...
	</body>
</html>

When initting the hpp you will see 'Loading...' breifly and the request to 'https://pay.elavonpaymentgateway.com/pay' should have the required origin and referrer.
Hope this helps.

Hi,
I have the same issue after we updated to the newest version of this library. With older version it did make any difference if 'Origin' was null or not. It does make difference now.
I was necessary to update to new version, because support for 3DSv2 was needed.
As @MathewWoodhall mentioned it works fine if we request to snadbox, but as soon as we set domain to 'https://pay.realexpayments.com/pay' then we get error.
This code we added to our checkout page:
$(document).ready(function () {
RealexHpp.setHppUrl(realexDomain);
RealexHpp.lightbox.init("checkout-button", "/basket/response", data);
});
'data' comes from backend (we use https://github.com/realexpayments/rxp-hpp-php):
$realexHpp = new \com\realexpayments\hpp\sdk\RealexHpp($sharedSecret);
$realexHpp->requestToJson($hppRequest, false);
I could not resolve it so far. Any help is much appreciated.

I have the exact same issue. the solution from @MathewWoodhall which seems to work on our dev server but it is inconsistent so sometimes the iframe loads other times it does not.
So this is definitely a problem. I played around with the rxp-js code to see if I can get it working but it does not want to work at all.

Any progress on this one?

I have used the same solution as @MathewWoodhall, where the iframe must initially load a local page with  in the head, which ensures the Origin and Referrer headers are set.
I also then encountered the same issue described by @heinrich-fresh, where sometimes the iframe would not load, i.e. sometimes it would be stuck on "Loading...".
I believe the issue was caused by identifying when to call the RealexHpp.embedded.init() method.
You cannot load it on $(document).ready() because this is when the parent document is loaded, not the document within the iframe src (which we need for the Origin and Referrer headers to be correct). I then tried using the iframe's load() event, but this proved inconsistent.
My current solution utilizes JS postMessage function, so the iframe tells the enclosing document when to call it. This will only work if the iframe src document is in the same origin as the enclosing document.
So the iframe src document includes:

The enclosing document includes:


Doesn't work on height specified on %

Hello.
When you have to use the option scrollContainer to indicate where is the table scrolled, if the height of that container is specified on % this JQuery plugin mess up that.
In the fiddle are the steps to reproduce it:

You can turn off the floatThead  activation to see how looks without this JQuery plugin, or
Change the css to specified the height with px to see that in that case it works.

JsFiddle -> https://jsfiddle.net/dianjuar/3jhyLvdc/16/

Use fixed position mode:
https://jsfiddle.net/3jhyLvdc/20/
On Fri, Apr 20, 2018 at 2:07 PM, Diego Juliao<EMAIL_ADDRESS>wrote:

Hello.
When you have to use the option scrollContainer to indicate where is the
table scrolled, if the height of that container is specified on % this
JQuery plugin mess up that.
In the fiddle are the steps to reproduce it:

You can turn off the floatThead activation to see how looks without
this JQuery plugin, or
Change the css to specified the height with px to see that in that
case it works.

JsFiddle -> https://jsfiddle.net/dianjuar/3jhyLvdc/16/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mkoryak/floatThead/issues/416, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXbSR1G7HtfMoGffnWOIAnxF0vP6J47ks5tqiPvgaJpZM4Td34k
.

Works as expected


USHIFT-4712: Fix tests and node configuration for CNCF conformance

Which issue(s) this PR addresses:

Closes #

/test e2e-aws-tests-periodic

/test e2e-aws-tests-periodic

/hold

/override ci/prow/e2e-aws-tests-periodic
Failures from FIPS tests in https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_microshift/4092/pull-ci-openshift-microshift-main-e2e-aws-tests-periodic/1849350186288025600 are not related to this change.
CNCF conformance in that link works again, which is the target for this PR.

/lgtm

/hold cancel

/cherry-pick release-4.17


TextBox Widget polish

We need padding and a better cursor.

Also:

key repetition - holding down keys for X seconds should then make them re-emit a keypress every Y seconds, both for arrows and for regular keys
support for more control keys: home, end, ctrl-left, ctrl-right, delete
I think it would be nicer if the size were fixed, especially I think the height should be according to the line height, and not depend on the specific characters currently in the line

Looks like we've solved key repetition (at least on Windows). I hope this behavior is consistent across platforms, we are relying on Winit. We should probably refactor the event to handle passing along key repeat info so that widgets can decide whether they want repeats or not.
I've added support for home, end, and delete. I'd like to refactor out the text input handlers into a separate module that we can test rigorously and maybe share with the community. I tried to do this a long time ago for LÖVE, before I really knew what I was doing: https://github.com/LPGhatguy/textbox
The vertical size is now fixed based on the font's ascent or size. I'm not sure this is the right metric to use.
We should change the textbox layout code so that a user can set a minimum width, or at least stop the textbox from pushing back against constraints it's given.

On linux I'm seeing key repetition for the TextInput event but not for the KeyChanged event.


[RFE] Please consider also discovery via unicast DNS-SD

On very nice page dns-sd.org there is link also to DNS based discovery. It allows discovery similar to MDNS protocol, but also across routed segments and without requirement for working multicast. I have seen problem with mdns resolution on some wifi networks. I think unicast resolution might be interesting especially for corporates, where only administrator should be allowed to publish printers (or other devices).
Not sue how much does existing Avahi implementation support it or whether it is even a job for it.

@pemensik IMHO this is a dupe of #319 - it would be great if you checked the existing issues before you file a new :) .


supabase migration squash deletes storage schema migration script

Describe the bug
The supabase migration squash command is supposed to flatten all the migration scripts to one file.
It seems to delete one of my storage policies.
To Reproduce
Pull migration script, pull storage script with supabase db pull --schema storage, run supabase migration squash
Expected behavior
It should should flatten all of the logic into one file, not delete the logic.
Screenshots
https://www.loom.com/share/fe6854a529044e2aba4d16e1046ebcbc
Desktop (please complete the following information):

OS: MacOS
Version of CLI: v1.93.0
Version of Node.js (if applicable): v20.4.0

Additional context
Add any other context about the problem here.

Maybe adding new flag -s like with db diff to the squash command to specify the schemas would work.

Any update?

Is there a reason why supabase migration squash doesn't just merge the migration files together?

If you have been working on a project for a long time, chances are there will be migrations that repeatedly change the same column, function, etc. The value proposition for squashing is to get rid of these intermediate migrations so that you can migrate once to reach the final state of the desired database.
On capturing changes in auth and storage schemas, I think we can make a simplifying assumption here that such changes do not introduce new columns to the tables defined by auth and storage service. That way, we can diff statements from pg_dump directly before and after running migrations.
I will open a PR soon to try out this approach. Would appreciate your feedback once it's released to beta channel.

Please give npx supabase@beta migration squash a try and let me know if you run into any problems.
I will keep this issue open for another week or so to collect feedback.

@sweatybridge  I only have triggers on auth and storage schemas so it's not a full test but from what I see on my end it looks great

@sweatybridge Same here: I had the very same problem and using the beta version correctly added my triggers in the squashed file 🥳

@sweatybridge That being said, it seems that statements like the following are lost after squashing 😩
alter publication supabase_realtime add table public.posts;

If someone has the same issues as we do (with the squash not gathering the alter publication statements), it is indeed logic because when I think about it, the migration system seems to ignore these statements. Seeing how the squash works (applying the migrations and then diffing the schema), it's logic that the alter publication) statements are ignored during this process too.
To work around this, here is what we did:

Create a file supabase/migrations/99999999999999_publications.sql. It will contain all our publication-related statements (typically the alter publication supabase_realtime...). The fake timestamp guarantees that these statements are executed last, after all other database modifications are performed.
Create a new script in our package.json:"supabase:migration-squash": "npx rimraf supabase/migrations/99999999999999_publications.sql && npx supabase@beta migration squash --local && git restore supabase/migrations/99999999999999_publications.sql",

This script does 3 things:

Remove the file containing all the publication-related statements: it is necessary because otherwise the squash will overwrite this file as it is the last migration file.
Perform the squash (using the beta version 😉 until a new version is published)
Restore the publication-related SQL file.
We will now use the npm run supabase:migration-squash command to perform migrations.

For some reason, the generated squash file truncates the first parts of the storage/auth schema functions, right after the
--
-- Dumped schema changes for auth and storage
--

statement.  They seem to start at some random point

Also, the squashed migration now contains the DDL SQL statements for storage and auth schema, so when generating a new migration after the squashed migration, it seems some internal process is priorly creating those schemas.

Hmm could you share with me the entities you've changed in auth and storage schemas? I will try to reproduce.

We havent changed any of the entities, the squashed migration is trying to contain all the storage/auth schema SQL regardless if we changed it, as if it was going to create everything from scratch.
With this singe file, we are attempting to run supabase db diff to check for any remaining changes in schema, but the command fails as soon as the new squashed migration file is being applied to the shadow database.

May I double check the version of Postgres you are running? I think the new squash wouldn't work with <IP_ADDRESS> or below.

I ran the diff command in debug, and i am seeing these statements in the console:
2024/03/15 11:55:46 PG Recv: {"Type":"NoData"}
2024/03/15 11:55:46 PG Recv: {"Severity":"NOTICE","SeverityUnlocalized":"NOTICE","Code":"42P07","Message":"relation \"buckets\" already exists, skipping","Detail":"","Hint":"","Position":0,"InternalPosition":0,"InternalQuery":"","Where":"","SchemaName":"","TableName":"","ColumnName":"","DataTypeName":"","ConstraintName":"","File":"parse_utilcmd.c","Line":209,"Routine":"transformCreateStmt","UnknownFields":null}
2024/03/15 11:55:46 PG Recv: {"Type":"CommandComplete","CommandTag":"CREATE TABLE"}

It is as if the shadow database already has the auth/storage schemas set up before the squashed migration runs, so it will conflict when the squashed migration attempts to "recreate" those schemas.

So the squashed migrations should not contain any entities already defined by storage because it is a supabase managed schema. That's why I suspect there might be some conflicting changes in the migrations before they were squashed. Was any of your earlier migration created by db pull?

Maybe, this is an old schema and we have over 40 migration files, let me check our migration history to see if we did somehow generated the schema DDL for those and added them to our history..
So to be clear, we should not have any DDL SQL related to the creation of entities or the auth/storage schemas in our migration history, only any changes we've made?
The only changes we do have is some added triggers to one auth table, my mistake earlier. Apart from that one both schemas have been untouched.

So to be clear, we should not have any DDL SQL related to the creation of entities or the auth/storage schemas in our migration history, only any changes we've made?

Yup, that is correct.
I think triggers should work fine, as long as they are not replacing any existing ones predefined by supabase (we plan to lock them down in the future anyway).
If the problem persists, could you file a support ticket so I can take a closer look at your project?


adding 3d objects such as spectacles to the head in the facemesh solution in browser

Exactly as the tiltle mentions, I would like to know if it is possible and if so what are best practice steps I should take to do it.
So far I have obtained the landmarks of various parts of the mesh and tried to use those to manipulate a 3d model in a babylonjs canvas. But I was wondering if there is a better way to do the same using some calculators available in mediapipe itself that will work on the browser. I have encountered while searching the forums, the effects rendering calculator that uses the openGL for android and IOS but I do not know how to make it work on the browser.
Thanks in advance.

We unfortunately don't have examples to do this and do not have plans to provide it. You can check out the face effect renderer calculator and https://google.github.io/mediapipe/solutions/face_mesh.html#face-effect-example


navbar improved

Description
Improved the navbar. Added an interesting bouncing effect in the navbar.
Please include a summary of the change and which issue is fixed.
Improved navbar by adding the following features.
•Bouncing effect - On scrolling, the navbar bounces upside and disappears for a while and then visible again.
• Added hr tag in menu list after each  tag.
• Hovering effect in hr tag.
Fixes (issue) #287
List any dependencies that are required for this change
Type of change

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

How Has This Been Tested?
I have tested these changes by applying them to my local machine.
UI /UX changes
Attach gif or screenshot for changes.

Before :

https://user-images.githubusercontent.com/59495227/112950356-d49a5b00-9157-11eb-80c0-53ab2583ccb2.mp4
- After :
-

https://user-images.githubusercontent.com/59495227/112951245-c39e1980-9158-11eb-8ccc-782b2fee8579.mp4
Checklist:

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

@Shruti3004 @harikesh409 @ravikr126 please review these changes regarding navbar.

@bajajanjana resolve the conflicts.

everything is good but resolve the conflicts @bajajanjana

I'll resolve this conflict soom

@harikesh409 @ravikr126 I have made a new PR #318  regarding the same issue #287 after solving the conflicts.
Please review the new PR #318 in place of this.

moved to #318


pin build-custom since it is being deprecated

Pinning this for now since it will be removed shortly and I don't want development on starknet to accidentally be halted. There is a ticket to use the new actions in progress by @AnieeG so this pin should just be a short term stop gap.

Looks like there is more broken then just the build pin so pinning this branch would do nothing.


Figma export PBSharedMasterNode inside Screen

Describe the bug
On Figma componentes can be created even inside pages, so if we do so, it will create a PBSharedMasterNode inside a page, which it will create a Stateless Structure inside the body.
To Reproduce
Steps to reproduce the behavior:

Run Parabeac-core using the Figma file "zXXWPWb5wJXd0ImGUjEU1X"
Go to landing page
It should try to do a Stateless inside a child

Impact of the problem
I don't know how common is this practice on Figma, but it heavily affects the output
Environment:

OS: macOS

This issue was resolved

This issue was resolved


Behavior change in 12.4: nameless resources

As part of @jkeiser's new DSL work, the behavior of a resource with no name file { ... } has changed. I'm hesitant to call this a compat break because the old behavior was probably a bug for everyone except me. In the current release that code would result in a resource with name set to nil, in master that is a syntax error. This is because the old method_missing code uses args[0] as the name, which is nil if there are no args. The new code has real methods defined for each resource in the DSL and those require a name parameter.
I'm cool with fixing this on the Poise side of things if we can find a non-terrible way to do that, and if we agree the old nil behavior was a bug and not an API compat break to change it.

A solution for this on the Chef side would be to make the DSL stub methods have a default value for the name parameter (probably nil) and then in declare_resource check that the name is something valid (not nil or '') and raise an exception if it isn't. Kind of roundabout though, and this will probably only benefit me (I override declare_resource in this case and it fills in a default name in some situations). An alternative would be for Poise to create overrides for every DSL stub method, which seems tricky and still gross.

Another advantage of doing the error check in declare_resource is we could show a nicer error message, more like the runtime error display that shows the snippet of recipe code, rather than a standard SyntaxError. There is already a check in ResourceBuilder for name.nil? so that's a thing too.

You mean we allowed resource name to default to nil?  That seems like an
unintended compat change.
What I really want is to involve the resource in its own construction, I.e.
implement build_resource in the resource class and let it take whatever
arguments it wants.
On May 22, 2015 12:14 PM, "Noah Kantrowitz"<EMAIL_ADDRESS>wrote:

Another advantage of doing the error check in declare_resource is we
could show a nicer error message, more like the runtime error display that
shows the snippet of recipe code, rather than a standard SyntaxError.
There is already a check in ResourceBuilder for name.nil? so that's a
thing too.
—
Reply to this email directly or view it on GitHub
https://github.com/chef/chef/issues/3416#issuecomment-104746455.

Yes, I use this in nested resources to allow for simpler syntax:
application 'foo' do
  bundle_install do
    deployment true
  end
end

In that case bundle_install gets a default name, but this is now broken because the DSL stub method for it requires a name. I created #3417 with a potential fix on the Chef side to restore the old behavior.

this got fixed and merged


question about flattening

question from @sangwinc (originally in #90, moved here because it wasn't specific to equations)

Can I ask (sorry I didn't read the code....) how you are dealing with "associative, commutative binary operators" such as + and *?
Maxima has an "n-ary" operator concept which allows "+" to have an arbitrary number of arguments.
So (x + 1) - 1 is (internally) like "+"("+"(x,1),-1) and x+1-1 is like "+"(x,1,-1).
I quite like this design. "flattening" the first example into the second is essentially using associativity.
You still have the unary minus to worry about, e.g. "+"(x,1,-1) might be displayed as x+1+-1, so that is an important detail.

Answer:
Yes! We deal with those things exactly as you describe. You can learn more in our blog post under the heading "2. Modifying expression trees for step-by-step solutions"

feel free to ask more followup questions about that here, or close the issue if you're satisfied :)

The PRESS researchers also implemented "flattening" in their solver, and they used a data structure called a "bag" to represent variadic functions and predicates. The following passage from Dr. Bundy's writings discusses variadic functions and predicates and the bag data structure:
http://patternmatics.org/mathsteps/tmp/press_bags.txt
Over the past few days I have been working on an interface between MathPiper and mathsteps so some of the visualization tools in MathPiper can be used to better understand how mathsteps works. The following image is my first attempt to visualize how each step transforms an equation's expression tree during the solving process (note, this image is tall so it needs to be clicked on to enlarge it. Also, its size is 175k):
http://patternmatics.org/mathsteps/tmp/solve_steps_with_trees.png
Bag-like data structures needed to be implemented in MathPiper to hold the variadic forms of the +, *, and - operators.

cool visualization!


Plans to integrate/support scrapy or integrate with scrapy-playwright?

Great package! Are you planning to integrate this functionality as middleware/compatible to Scrapy?

Hello,
Scrapy integration isn't on my current roadmap, but it definitely sounds interesting to add in the future.
I'll mark this as help wanted.
Thanks


Typo introduced in commit 1 one month ago

https://github.com/reddit/baseplate.py/commit/29d99fc1d770497bfc20fcf1c794539899cd482b#diff-63712203d887896d022bc211be536eb7R129
Leading "r" before docstring

This is false issue. Is new declaration of string literal. https://docs.python.org/3/reference/lexical_analysis.html


Cannot find module '/var/www/html/git/bitpay/node_modules/bitpay-sdk/dist/index ---For node sdk

Error: Cannot find module '/var/www/html/git/bitpay/node_modules/bitpay-sdk/dist/index'. Please verify that the package.json has a valid "main" entry

Solved by downgrading version of npm i<EMAIL_ADDRESS>

This is the issue I mentioned in this PR discussion: https://github.com/bitpay/nodejs-bitpay-client/pull/40#discussion_r774644314 The currently-published package is in a bad state because of the "src" confusion. That PR should fix it after it's merged.


Use random text for naming product and category in the testings

@mplt-simon update the tests to use e() for user->name assertions. 👍

@mplt-aleks Brilliant, thanks

@mplt-simon another revision to solve testing issues for user's name


Bug bash to find samples for Event Hubs that need to use the latest package

Update from @ramya-rao-a
Review the .Python samples for Event Hubs in the below locations to find the ones that do not use the latest version of the package. Update this issue with the list of samples that need updating.

Event Hubs Python samples repos under Azure-samples org
Event Hubs Python samples under docs.microsoft.com/samples

Additionally, ensure the samples that live next to the source code for Event Hubst in this repo shows up in Event Hubs Python samples under docs.microsoft.com/samples. This is done by setting up the right metadata. Ensure that these samples are not outdated.

Samples
Link
Status
Notes
Action

Azure Event Hubs client library for Python Samples
link

Collecting Scheduled Events with Event Hub
link

Azure Event Hubs client library samples with persistent checkpointing for Python
link

Azure Event Hubs client library samples with persistent checkpointing for Python
link

same title as the sync one, can we improve that?

authenticate_with_sas_token.py, Line 9: replace ServiceBus with EventHub

Nice find @swathipil
@yunhaoling To your question on sample title, we control that. You can make the change at https://github.com/Azure/azure-sdk-for-python/tree/master/sdk/eventhub/azure-eventhub-checkpointstoreblob-aio/samples#azure-event-hubs-client-library-samples-with-persistent-checkpointing-for-python
@swathipil Please use https://github.com/Azure/azure-sdk-for-python/issues/15114 to track the changes for the issues you listed above.
https://docs.microsoft.com/en-us/samples/azure-samples/virtual-machines-python-scheduled-events-central-logging/virtual-machines-python-scheduled-events-central-logging/ uses the REST APIs to send events. I have another tracking item to consider whether or not we should update it to use the Event Hubs package


feat(preimage): add serde feature flag to preimage crate for keys

Description
We need to Serialize and Deserialize traits implemented on PreimageKeys to pass them into the zkVM. Adding a feature flag to the preimage crate to do that.
Tests
N/A
Additional context
N/A
Metadata
N/A

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

Project coverage is 70.3%. Comparing base (5a2325c) to head (1ac526d).

Additional details and impacted files

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


Add directus

https://github.com/directus/directus/tree/main/docker

https://docs.directus.io/self-hosted/installation/docker.html

https://docs.directus.io/self-hosted/docker-guide.html


Implement interface changes on seedlot details page

Describe the task
Implement interface changes on seedlot details page.
Changes inside seedlot details page

2.1 - Remove review form section
Was: There was a review form section
Change to: Remove review form section from seedlot details page for every user besides TSC ADM
Reference: seedlot details
Requested: MVP 1
Goal: make the screen easier to build and less repetitive.

2.2 - Can't edit when submitted or approved status
Was: There was a "edit seedlot" and "edit applicant" button for every seedlot status
Change to: Users should not be able to edit the form or the applicant information when the seedlot is submitted or approved. Remove the "edit applicant" button from "Check your applicant and seedlot information" section. Change the "edit seedlot form" button's label to "View seedlot form", inside the "see where you are in the registration process" and at the combo-button action.
Reference: seedlot details - submitted and approved status
Requested: business rule
Goal: make the interface follow the determined business rule.

Acceptance Criteria

[ ] All implemented and looking good, just like on figma :)

Already implemented!


NextFederationPlugin: Module not found error

Package Versions:
next: 13.2.4
react: 18.2.0
@module-federation/nextjs-mf: 7.0.8
Import statement:
import something from “host/something”;
Webpack Error upon building:
Module not found: Can’t resolve “host/something”
Importing a module from a remote using the above syntax works fine on the dev server, but throws a webpack error upon running “next build”.
In a separate example repo that was using ModuleFederationPlugin and NOT nextjs, this type of import statement built fine without any webpack errors. When I replaced ModuleFederationPlugin with NextFederationPlugin in this example repo and built, I saw the same webpack error that I saw in my next app.
I also didn’t have luck with the 8.0.1 canary 7
@ScriptedAlchemy

bump

Try lower canary version? Like .1

Are you loading only client side or server side as well.

Are you loading only client side or server side as well.

Ah, this was the key! Since I'm only using federation on the client-side, the server build was failing. I was able to resolve the error using a custom loader. Thank you sir!


Added Ingredient Project

added the required data
using a host link for web application image

[ ] I have followed (at least) the PR section of the contributing guide.

@Prottoy2938 Thanks for sharing your project. I'm closing, as our showcase policy is to include items that at least have: a high volume of traffic, a nondefault material design look, an open-source quality codebase.


dispatcher: Add MultiClusterService events to the dispatch system

This PR adds the MultiClusterService events (add, update, delete) to the catalog/dispatch system so these events cause Envoy config refreshes as well.
Signed-off-by: Delyan Raychev<EMAIL_ADDRESS>

Codecov Report

Merging #3769 (dedc132) into main (32b9a78) will decrease coverage by 0.20%.
The diff coverage is 32.14%.

@@            Coverage Diff             @@
##             main    #3769      +/-   ##
==========================================
- Coverage   69.98%   69.77%   -0.21%
==========================================
  Files         185      185
  Lines       10366    10407      +41
==========================================
+ Hits         7255     7262       +7
- Misses       3062     3096      +34
  Partials       49       49

Flag
Coverage Δ

unittests
69.77% <32.14%> (-0.21%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/envoy/bootstrap/config.go
93.95% <0.00%> (-1.94%)
:arrow_down:

pkg/errcode/errcode.go
100.00% <ø> (ø)

pkg/envoy/cds/cluster.go
94.04% <33.33%> (-1.11%)
:arrow_down:

pkg/envoy/cds/response.go
80.00% <40.00%> (-4.13%)
:arrow_down:

pkg/catalog/dispatcher.go
36.84% <100.00%> (+1.12%)
:arrow_up:

pkg/envoy/lds/ingress.go
79.03% <0.00%> (-5.46%)
:arrow_down:

pkg/envoy/lds/tracing.go
84.21% <0.00%> (-4.68%)
:arrow_down:

pkg/envoy/lds/rbac.go
81.03% <0.00%> (-4.43%)
:arrow_down:

pkg/envoy/lds/auth.go
93.33% <0.00%> (-3.22%)
:arrow_down:

pkg/envoy/lds/inmesh.go
77.77% <0.00%> (-2.61%)
:arrow_down:

... and 7 more

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 7ef0c47...dedc132. Read the comment docs.


[ROCm] Fix for ROCm CSB Breakage - 200902 - 2

The following commit introduces regressions in one unit-test, in the ROCm TF build
https://github.com/tensorflow/tensorflow/commit/458d0906ebe75072ebd87cf5088772405d0cd03e
//tensorflow/python/kernel_tests:pooling_ops_test_gpu                    FAILED in 3 out of 3 in 41.8s

The failures occur in the newly added subtests for testing the explicit padding feature. The code in the ROCm path has a couple of bugs in it, which lead to the failures. This commit fixes those bugs.
Note that changes in PR #42897 are also required for to make the above unit test pass again with the ROCm TF build. The isssue being addressed in that PR is orthogonal to what is being addressed here, and hence the two separate PRs.

@chsigg @cheshire @nvining-work

@chsigg gentle ping

@chsigg gentle ping

@chsigg gentle ping

@chsigg gentle ping

@chsigg gentle ping

@chsigg gentle ping

@chsigg gentle ping


Updated README to run the example.

Why this PR?
Executing flutter run in the example folder, with a running iPhone XR simulator, causes the following error:
Launching lib/main.dart on iPhone XR in debug mode...

Oops; flutter has exited unexpectedly.
Sending crash report to Google.

From the log, I can read:
FileSystemException: FileSystemException: Getting current working directory failed, path = '' (OS Error: Too many open files, errno = 24)

Which is the problem reported here: https://github.com/trentpiercy/trace/issues/1
How this PR fixes the issue?
Updated the README with the instructions I found in the link.
What are the expected outcomes after the merge?
It is possible to run the example app in the iOS simulator.

thanks!  I think this is happening because the example uses a lot of tiles... added an issue to track https://github.com/johnpryan/flutter_map/issues/269


feature: 重新梳理权限内容

Codecov Report

Merging #479 (4a3e38e) into v2.6.x_develop (751c0ba) will decrease coverage by 0.02%.
The diff coverage is 8.33%.

@@                Coverage Diff                 @@
##           v2.6.x_develop     #479      +/-   ##
==================================================
- Coverage           62.69%   62.67%   -0.03%
==================================================
  Files                 441      441
  Lines               27226    27232       +6
==================================================
- Hits                17070    17067       -3
- Misses              10156    10165       +9

Impacted Files
Coverage Δ

itsm/component/constants/iam.py
100.00% <ø> (ø)

itsm/ticket/views/ticket.py
47.13% <ø> (-0.28%)
:arrow_down:

itsm/ticket/permissions.py
35.06% <8.33%> (-1.75%)
:arrow_down:

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 751c0ba...4a3e38e. Read the comment docs.


add support for climate entities

I'm really liking the style of this component far more than a lot of similar ones.
I'm wondering if you could add support for climate elements with a min and max value. For example I could have my wall-mounted dashboard have a min and max control of 14-21C

Added to the roadmap, will definitely implement this.

@Mearman I've made a beta release v.1.7.0-beta with support for climate entities, could you please test this?

@Mearman @dougiteixeira I've made a beta release v.1.7.0-beta with support for climate entities, could you please test this?

For me it works well.

Works a treat!
Were you able to add a field for setting a min and max range?
Also is it currently possible to set a custom colour gradient? e.g. blue at 15C to red at 25C

Added in v1.9.0
@Mearman

Mode is show now, support for current temp will be added in feature for templating.
min and max are auto filled from min_temp and max_temp on the entity
a. Can be manually overridden by setting slider.min and slider.max options in yaml
Not currently possible, I like the idea though


Add servies for hegel and tink-server in tinkerbell chart

Description of changes:
Add services for hegel and tink-server with optional loadBalancer configuration
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherrypick release-0.10


ci: add travis configuration

Added travis ci configuration file for running builds on github.

@maihde I'm thinking of accepting this today, do you have any objections?


feat: Support PHPUnit 11

fyi I can upgrade to and use PHPUnit 11 now with a green pipeline in a project where we are using both php-mock/php-mock-mockery and php-mock/php-mock-phpunit.
it's not an issue per se, but I noticed that unfortunately there are deprecations coming from inside this lib, presumably both https://github.com/php-mock/php-mock-phpunit/blob/2.10.0/classes/PHPMock.php#L69 and https://github.com/php-mock/php-mock-phpunit/blob/2.10.0/classes/PHPMock.php#L72

MockBuilder::addMethods() is deprecated and will be removed in PHPUnit 12. No replacement is/will be provided.

MockBuilder::getMockForAbstractClass() is deprecated and will be removed in PHPUnit 12. No replacement is/will be provided.

Again, I don't think these are issues, but maybe we can avoid them somehow before people create issues here.


different of weather between weatherapi and météofrance

Hi,
thanks for the work !
i've two weather integrations, and with weatherapi the weather today in Normandy is rainy ! (with meteo france integration weather is sunny, and it's the real weather today)
when i use weatherapi with curl api, the information is good, but not with HA ?
may be there is a problem with latitude and longitude, but i don't know how change it...
regards

thanks for reply...
the datas are : Lat/Lon:	49.9, 1.27
but since my post, now the text is "sunny" like for meteo france...
i think it was some problem with updating, now all is OK ! (you can closed my post)
sorry for disturbing...
regards

I think it might be worth considering if the weather state should be cleared if the data fetch failed. I have seen data fetch fail occasionally and then it corrects itself. Showing the last good state doesn't feel correct.

The last 2 release are tackling JSON decoding better and log if the response received was incorrect. This should help with mismatches.

thank for update iprak


Feature wishlist

Hey, I just used this library and it's honestly great. Even lifesaving since Apple does not provide this to developers for some reason.
Here are just a few features/settings I wish that were included:

Fling
Allow the image to move outside of the crop, but fling it back on drag end.

Custom button & title labels
It's impossible to localize this for every possible language. Allow me to pass my own strings instead, localized or not.

Fixed size mask (aka Allow image to be off screen)
Mask always scales so the whole image is visible in the initial state. Allow the mask to stay the same size on screen & have sides of the image outside the screen.

CocoaPods version

Some of those can be addressed by copying the source code & editing it, but it would be nice to have an official support.

Hi @mr-kew, thanks for your ideas!
Here are some of my thougts:

Probably hard to accomplish, I also don't really see the use case. It suggests the user that the cropping area can leave the bounds but then snaps back. Is there a similar cropping tool that uses this functionality?
Easy, I can look into this and add it as a feature.
Probably also a little harder to accomplish. I think this makes sense when cropping profile pictures?
Should be easy to do, altough Cocoapods is to be replaced with SPM.

If you want to tackle one of these wishes yourself, feel free to submit a PR! I am always open for contributions :)

@benedom
I am generally basing it on the default iOS cropping in contact app, see video (thats kinda what I am going for in my app). Although now that I looked at it again, I find it pretty weird that they allow the image smaller than the crop area.
For the 1. it is really not a big deal, it's just that the native app has it. The 3. is more justified I think. I am using it for profile pictures and I think it would make it more consistent. Anyway it would be great to have that option.
Btw: I am using maskRadius: .infinity and then SwiftyCropView(...).padding(.horizontal, 30). Idk if it was designed this way, but I wanna the crop area to be dependent on the size of the screen, so thats what I did.
I develop in Kotlin Multiplatform, so thats why (well its much more complicated) SPM is not an option for me, so I would appreciate CocoaPods version. It is also a reason why 2. is important for me, because I am using multiplaform localization system and I wanna keep my strings all in one place, so even if the library supported my language I would not use it. Therefore I would like to use the CocoaPods version, but unless I can use my own strings for the buttons & title, I would still have to use the source code version and edit it. I know it's kinda a niche use case, but I wanted to explain where I am coming from with those.
Yeah I might look into some of them in the future. I just figured I might as well write the wishlist here rather than keep it for my future self. Also for now the library is enough for my superiors as is, so I might never get around to implementing some of those things myself as I have other things to focus on right now.
https://github.com/user-attachments/assets/666af1e5-8bd1-48e3-a772-ce1f2b046d64

@mr-kew
Thanks for your reply and the example video!
It's a good idea to voice your wishes as it always improves the library for everyone :)
I will start looking into issues 2) and 4) ASAP and give you an update once they are available!

@mr-kew the custom texts are now available, I am still working on the cocoapods support


Maint/fix trailing whitespace

Resolve all whitespace issues found by git's --check.

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


consensus: remove bundle_validator

bundle_validator in consensus became kind of useless since the logic has been moved to the bundle model.
load_bundle_transactions can be a tangle operation and then bundle_validator can be removed.

Actually, with the introduction of the validity field, iota_consensus_bundle_validator_validate and bundle_validate are now quite different so it won't be removed after all.


Revert "remove unnecessary sort"

Reverts istio/istio#36382
This broke a bunch of tests. Some were obvious like https://github.com/istio/istio/pull/36388 but for the NDS I am not sure. May be more complex

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
37e85068b0b29a9561cc0e9a01bdb7c1aa89e0ab
link
true
/test unit-tests_istio

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

/retest

Surprised to see tests relying on this sort.


Allow using secondary type names in schemas

Hi,
First of all, thanks a lot for this library. It allows using flatbuffers with swift really easy.
I think that could be good to allow using the secondary type names in the schemas. By secondary names I mean the names in parenthesis in the types section here https://google.github.io/flatbuffers/flatbuffers_guide_writing_schema.html
I had a schema that used uint8 and I had to change it to ubyte in order to compile.

I am really sorry for the late response. I 've update newewst flatbuffers version to fix this issue. thx :)

Thanks! It works like a charm! 🎉
Did you know if this library could be merged with FlatBuffers to allow Swift official support?
It's being discussed here https://github.com/google/flatbuffers/issues/3785#issuecomment-382780634
This library makes life easier with FlatBuffers and Swift!