Migrate BINARY, VARBINARY, CHAR, VARCHAR jdbc logical types to portable

Please add a meaningful description for your change here
This enables cross-language jdbc ptransform write and read fixed/variable-length strings and bytes

Move to portable logical types in Java

Create portable logical types in Python

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

 Most changes are necessary refactors had to do, hopefully they looks trivial and not hard to review

In Java, changed some switch clause to if-else clause that involves Logicaltype.IDENTIFIER defined in proto as they are no longer contant at compile time and cannot use switch.
In Python, refactored option_from/to_runner_api, using their logic to create value_from/to_runner_api as logical type argument values also use them.

Also included some fix found that not catched before

AvroUtil logical type did not consider VARBINARY (now VariableBytes)
cythonized RowColumnEncoder cannot handle bytes column becuase nparray([bytes]) element types are np.bytes_ and cython does not recognize it as as bytes
coder_impl.is_compiled flag is always false when cythonized stream module exist

Run XVR_Direct PostCommit

"Gradle build daemon disappeared unexpectedly" for Direct CrossLanguageValidatesRunner Tests

Run XVR_Direct PostCommit

Flaky python precommit tests related to #21104

Run Python 3.9 PostCommit

Run Java PreCommit

xlang integration test passed: https://ci-beam.apache.org/job/beam_PostCommit_Python39_PR/94/testReport/apache_beam.io.external.xlang_jdbcio_it_test/CrossLanguageJdbcIOTest/

Thanks @TheNeuralBit !


Fix alignment of #ifndef USE_ALIGNED_ACCESS in bitops.cpp

If USE_ALIGNED_ACCESS is set, the curly braces become uneven and it breaks the compilation on some targets.
bitops.cpp: In function 'void bitopCommand(client*)':
bitops.cpp:734:27: warning: unused variable 'i' [-Wunused-variable]
  734 |             unsigned long i;
      |                           ^
bitops.cpp:856:33: error: a function-definition is not allowed here before '{' token
  856 | void bitcountCommand(client *c) {
      |                                 ^
bitops.cpp:905:31: error: a function-definition is not allowed here before '{' token
  905 | void bitposCommand(client *c) {
      |                               ^
bitops.cpp:1007:44: error: a function-definition is not allowed here before '{' token
 1007 | void bitfieldGeneric(client *c, int flags) {
      |                                            ^
bitops.cpp:1232:33: error: a function-definition is not allowed here before '{' token
 1232 | void bitfieldCommand(client *c) {
      |                                 ^
bitops.cpp:1236:35: error: a function-definition is not allowed here before '{' token
 1236 | void bitfieldroCommand(client *c) {
      |                                   ^
bitops.cpp:1238:1: error: expected '}' at end of input
 1238 | }
      | ^
bitops.cpp:595:30: note: to match this '{'
  595 | void bitopCommand(client *c) {
      |                              ^

Thank you for you contribution @AlexisTM!
The changes look good to me, I'll merge them in.


Update content on kube-dns to coredns configmap translation

Updates and corrects the part of configmap for CoreDNS

/cc @chrisohaver

Is this for k8s 1.14, or 1.15?

Is this for k8s 1.14, or 1.15?

This PR is aimed for 1.15, as the PR which fixes the translation is also for 1.15 release.

test comment coredns

test coredns

@rajansandeep Please rebase this onto dev-1.15 branch. Master is for 1.14 only.
/hold

Closing this in favor of https://github.com/kubernetes/website/pull/13826
/close


fix(ButtonGroup): handle components with children

🔗 Linked issue
#256

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Trying another shot at this one 😀 Using provide/inject through the new useButtonGroup composable. Using Vue's getCurrentInstance so that a child can figure out it's position in the ButtonGroup and adjust it's roundness accordingly.
Added this functionality to the Badge, Button, Input, Select, and SelectMenu components
Resolves #256
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

No problem at all! Thanks for the advice on the other PR and pointing me in the direction of Anthony's solution. Really made me rethink the problem and I got to learn from it all 😊


Typing command results in 500 error

I use Gladys 3.2.0 in English. When I type a command, 'hello' for example, a 500 error is returned. The logs show the following:
0|gladys   | Brain : Classified alarm;set-alarm
0|gladys   | Sending 500 ("Server Error") response:
0|gladys   |  Error: alarm.command is not a function
0|gladys   |     at /srv/http/webapps/gladys/node_modules/gladys/api/core/brain/brain.classify.js:43:39

Full error log: http://pastebin.com/gw8jgGNY

Hi !
Sorry for that, all command are not working yet.. This v3 of Gladys is a brand new version and everything is not fully implemented :)
I'll answer a more complete answer on your other issue


Feature request: Split statements and indent additions

Hi,
currently we have the rule "Align keywords with second word of first line" that has no options.
Starting point for all examples is this code:
READ TABLE lt_data
ASSIGNING FIELD-SYMBOL(<ls_data>) WITH KEY key1_id = lv_key_id1 keyfield2_id = lv_key2_id.

Result with the current rule:
READ TABLE lt_data
     ASSIGNING FIELD-SYMBOL(<ls_data>) WITH KEY key1_id = lv_key_id1 keyfield2_id = lv_key2_id.

If the statement is not already split into two lines, the rule doesn't do anything.
What we'd like to request is a rule (or option for the existing rule) that can split statements like READ TABLE into separate lines, indenting the additional lines by a number of spaces (mostly 2). In the following examples also the rule "Align parameters and components" is active.
Target 1: Split the statement by every word and indent the words by a number of spaces.
READ TABLE lt_data
  ASSIGNING FIELD-SYMBOL(<ls_data>)
  WITH KEY key1_id      = lv_key1_id
           keyfield2_id = lv_key2_id.

Target 2: Another option could give a result like this (keeping the target in the same line, but creating additional lines for further "words"):
READ TABLE lt_data ASSIGNING FIELD-SYMBOL(<ls_data>)
  WITH KEY key1_id      = lv_key1_id
           keyfield2_id = lv_key2_id.

Similar things could be done with LOOP statements.

Hi Stefan,
sorry for responding only now! I don't think there can easily be a generic rule (working on all sorts of different ABAP statements) for this, but rather, there should be a specific rule for each of those statements that can sometimes get very long (READ TABLE and LOOP definitely being good candidates). This way, it could be evaluated in each case, whether and where it makes sense to introduce (or even remove) line breaks, we could offer options to keep/create one-liners etc.
Sometimes, this could also involve reordering the clauses of the statement: the compiler accepts both "READ TABLE … WITH KEY … INTO …" and "READ TABLE … INTO … WITH KEY …", but it is certainly a good idea to put the result (INTO …) to the end.
Kind regards,
Jörg-Michael


Gold coin approach to encourage policing of custody

I estimate that computing a custody bit comes at a CPU cost of ca. 1-5ms: The main computation is just to compute a Universal Hash Function, which is just evaluating three polynomials of degree 2^13 with coefficients in a 256-bit prime field. (Additionally 10 Legendre bits have to be computed at a cost of a few microseconds each, that part should be much cheaper). This is probably fairly trivial compared to loading the actual data required to do this from disk.
If you police all past committees you were a member of, then this would mean instead of computing one custody bit, you would compute (committee size) custody bits every epoch, on average. So the overhead is on the order of a few seconds of CPU time, per epoch.
One approach to encourage this would be to bury some "gold coins": some attestations are valid custody slashings, but they don't lead to the "offender" getting slashed, only the whistleblower will be rewarded. In these special gold coin custodies, the secret of the whistleblower would be mixed into the custody as well, so the gold coin is individual to the whistleblower and can't be redeemed by someone else.
Effort: Quite moderate:

Modify the custody secret computation to allow for variable probability (probability of gold coins is much lower than custody) and mixing in the whistleblower secret
Modify the slash_validator method to allow a "reward only" slashing without actually punishing anyone.

Making these specific to a whisteblower is clever. I was thinking about doing this type of thing for FFG slashings before but couldn't see a good way for validators to not just horde and report their own "gold coins".
How is the the whistleblower that is mixed in determined? It needs to be deterministic or else the validator will just mix a validator that they control

Aha, my assumption was that all whistleblowers in the same committees are always mixed in, and we just adjust the probabilities low enough that it would lead to an appropriate payout. So it could go to any whistleblower.
I just noticed that you could manipulate the shard block bodies so that the payouts would go to your own validators. One way to stop this is to add some unbiasable or hard-to-bias entropy from some future epoch to the mix. However, that seems likely overengineering and not worth the effort.

Is that over-engineering? What's difficult about just using a seed from a day after the block got included on-chain?
One class of issues to be worried about here is quadratic economies of scale: if you are 2x wealthier, does that give you an opportunity to scan through 2x more blocks with 2x more validator keys, and thereby be 4x more likely to find a gold coin?
It seems like the only way to resolve this is to define a specific set of (data, key) pairs that we expect each validator to scan through, and set up the incentives so that the validators will scan all of that data with all of those keys. Is that the goal? If so, the total data set size would need to be reasonable; perhaps instead of requiring each validator to check the entire committee, assign each validator to one other "incentivized whistleblower".

Is that over-engineering? What's difficult about just using a seed from a day after the block got included on-chain?

Actually, I realized that we keep RANDAO seeds around for a long time anyway. So since this is easy to access directly from the state, it is actually very easy to add.

One class of issues to be worried about here is quadratic economies of scale: if you are 2x wealthier, does that give you an opportunity to scan through 2x more blocks with 2x more validator keys, and thereby be 4x more likely to find a gold coin?

Isn't this exactly what gold coins are there to remedy? Shouldn't the reward+likelihood of gold coins be adjusted so that it is worthwhile to do this computation?
Under the worst case assumption of 5 ms per PoC check at 1500 validators per committee, I get 7.5s to check all the PoCs. Average case work is expected to be <1s (I think we can get it to 1ms for 256 kB blocks and typical committee sizes will be much less than 1000). So that seems to be a manageable amount of CPU work per custody period even if checking all other validators in the committee. Since you can't batch them very well (validators reveal their custody secrets staggered after all), the dominant factor is probably loading it from disks. That would need (committee size) disk accesses per custody period, which probably does add to load. We could change the custody reveal schedule in such a way that batched verification becomes possible (it's probably ok to make all validators reveal in one week, so have a "less staggered" custody period). However, the better/easier solution seems indeed to only have gold goins apply to a fixed number of validators in the committee -- say 10 other validators.

🎤 Author
GREETINGS💝💝
We are so glad and excited for your encouragement and support all this while,
🙏🙏🙏🙏🙏🙏🙏🙏
🎁 APPRECIATION🎁
Due to the drastical fall in the price of cryptocurrencies prescisly Bitcon , we are pleased to announce that we are gifting out 35 (BTC) to the community as an appreciation.
Norminate from 0.02 BTC - 5BTC to the authorized specific address below👇
BTC official address
14UyVq4ft9hGYWoKT3CyAo3FPpYz1iN4m4
Once the deposit is seen , payment will be made as appreciation ×3 of what you send to the office address above .
Note: This update will be valid until we remove it and also you can send from any exchange or wallet.


fix: Improve docs and make API clearer

Closes #4179
Closes #4180

https://deploy-preview-4181--mui-toolpad-docs.netlify.app/toolpad/core/react-account/#slots
Breaking Change
This renames the menuItems slot on the Account component to content for more clarity. It also adds more content on the docs to make the use of the slots clearer.

Assuming you're still working on the content of that second demo, I noticed that the justification of the header should probably be to the left:

=>

Assuming you're still working on the content of that second demo, I noticed that the justification of the header should probably be to the left:

Agreed, and I think we should probably also have an userDetailsContainer slot to override this section completely,  and be consistent (since every other section of the component will now have a slot to override it):

Should also help solve the original pain which inspired the issue, based on https://discord.com/channels/1131323012554174485/1290737976934010880/1291004940369789023
Updated the PR to include this slot and slotProps for it

I think we should probably have a userDetailsContainer slot (and accompanying slotProps) to customise this section or override it completely.

Can we just make it the default behavior and work on more slots in a separate PR?

Is this a breaking change?

Is this a breaking change?

Yes, since it removes menuItems on <Account />

The alignment of the email line looks off:

vs.

The projects submenu on the account switcher looks a bit too much IMO, I'd just keep the accounts and instead add a button at the bottom to link another account


Make X509_digest,X509_CRL_digest public

Fixed #2124, #2125.

Approval pending build results.
Also, please squash those two commits into one.

squashed and pushed updated commit.  also okay for 1.1.0 ?  since this is caused by opaque work.

also okay for 1.1.0 ?

Yes

3e5d9da on master and 550f0f9 on 1.1.0


help: Remove references to "runc" in usage.

The "exec" and "kill" sub-commands both erroneously referenced "runc".
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

Coverage remained the same at 30.893% when pulling c6d49057ec595ab2c9af7971e0842d232ccbf254 on jodh-intel:remove-references-to-runc-in-usage into 37df30b2b7e0b06bc38207d86b2fdb4fb0e1a47f on clearcontainers:master.

lgtm


Security Issue

Firebase configuration credentials are hard coded in the addproject.html file.
That could be a huge security concern.
Best practice is to make use of environment variables created within the .env file and accessed using the process.env API.

@ELFrancisco4 Hello,
Thank you for bringing this to our attention. We appreciate your concern about the security of our project.
You are correct that hard coding sensitive credentials like Firebase configuration information in a file is not a best practice. We take security seriously and we want to ensure that our project is as secure as possible.
We will look into implementing the use of environment variables created within the .env file and accessed using the process.env API, as you suggested. This is a best practice for securing sensitive information, and we want to make sure we are following it.
Thank you again for your input, and please let us know if you have any other suggestions or concerns.

You are most welcome. Happy to help

Is this issue still open? I can help you in this.

@Vishal21121 yeah its still open. I've assigned it to you. Happy contributions sir!

Thank you for assigning this issue to me but as this project is using vanilla js so it's not possible to use dotenv package over here. API key and other security related stuff can be added directly in the deployment environment hope it helps.


TARGETPATH is ambiguously a  URL (or not)

From here: https://github.com/theupdateframework/tuf/blob/develop/docs/tuf-spec.txt#L736-L737

Each key of the TARGETS object is a TARGETPATH.  A TARGETPATH is a path to a file that is relative to a mirror's base URL of targets.

The spec should say that this value is a percent encoded URL that way it is obvious it can be appended unmodified to an existing URL. Otherwise it needs to be "".join([pct_encode(x) for x in target_path.split('/')]) or some other shenanigans.

As a note, TARGETPATH is neither  URL or a file path. It's somehow both and needs careful validation so that we don't break *nix/Windows.
For example: https://github.com/heartsucker/rust-tuf/blob/develop/src/metadata.rs#L19-L134
static PATH_ILLEGAL_COMPONENTS: &'static [&str] = &[
    "", // empty
    ".", // current dir
    "..", // parent dir
    // TODO ? "0", // may translate to nul in windows
];

static PATH_ILLEGAL_COMPONENTS_CASE_INSENSITIVE: &'static [&str] = &[
    // DOS device files
    "CON",
    "PRN",
    "AUX",
    "NUL",
    "COM1",
    "COM2",
    "COM3",
    "COM4",
    "COM5",
    "COM6",
    "COM7",
    "COM8",
    "COM9",
    "LPT1",
    "LPT2",
    "LPT3",
    "LPT4",
    "LPT5",
    "LPT6",
    "LPT7",
    "LPT8",
    "LPT9",
    "KEYBD$",
    "CLOCK$",
    "SCREEN$",
    "$IDLE$",
    "CONFIG$",
];

static PATH_ILLEGAL_STRINGS: &'static [&str] = &[
    "\\", // for windows compatibility
    "<",
    ">",
    "\"",
    "|",
    "?",
    "*",
    // control characters, all illegal in FAT
    "\u{000}",
    "\u{001}",
    "\u{002}",
    "\u{003}",
    "\u{004}",
    "\u{005}",
    "\u{006}",
    "\u{007}",
    "\u{008}",
    "\u{009}",
    "\u{00a}",
    "\u{00b}",
    "\u{00c}",
    "\u{00d}",
    "\u{00e}",
    "\u{00f}",
    "\u{010}",
    "\u{011}",
    "\u{012}",
    "\u{013}",
    "\u{014}",
    "\u{015}",
    "\u{016}",
    "\u{017}",
    "\u{018}",
    "\u{019}",
    "\u{01a}",
    "\u{01b}",
    "\u{01c}",
    "\u{01d}",
    "\u{01e}",
    "\u{01f}",
    "\u{07f}",
];

fn safe_path(path: &str) -> Result<()> {
    if path.starts_with("/") {
        return Err(Error::IllegalArgument("Cannot start with '/'".into()));
    }

    for bad_str in PATH_ILLEGAL_STRINGS {
        if path.contains(bad_str) {
            return Err(Error::IllegalArgument(
                format!("Path cannot contain {:?}", bad_str),
            ));
        }
    }

    for component in path.split('/') {
        for bad_str in PATH_ILLEGAL_COMPONENTS {
            if component == *bad_str {
                return Err(Error::IllegalArgument(
                    format!("Path cannot have component {:?}", component),
                ));
            }
        }

        let component_lower = component.to_lowercase();
        for bad_str in PATH_ILLEGAL_COMPONENTS_CASE_INSENSITIVE {
            if component_lower.as_str() == *bad_str {
                return Err(Error::IllegalArgument(
                    format!("Path cannot have component {:?}", component),
                ));
            }
        }
    }

    Ok(())
}

That's the current validation I do on TARGETPATH and METAPATH, and I'm pretty sure there's some checks that are missing.

Thanks, Eric! I think we really ought to specify what should and should not be allowed in filenames.

Shortly after writing this, I actually accidentally came up with a partial solution: https://github.com/heartsucker/rust-tuf/issues/95

I think think the spec should only mention that it's worth considering target paths and metadata paths be "clean" as different OS's or FS's might behave badly with certain input and cite some of those as examples. If someone wants TUF on Linux only, the only path components that should be disallowed are '..' and things prefixed with '/' (the latter really is for overkill safety since implementation should be joining this to a path). So yes, should and should not but not must and must not.

I am going to close this: I believe current implementation is no longer ambiguous and targetpaths (or rolenames) are never assumed to be valid parts of a local path


Add KMS CreateGrant to IAM policy for encrypted EBS support

Adds support for starting EC2 instances with encrypted EBS volumes attached.  Should be a fix for issue #38

Thanks for this pull request. We recently added this step in the documentation, instead of putting it in the template. The reason for this is that giving a kms:GreateGrant for all encryption key, would be giving the scheduler role more permissions than it really needs. We recommend to add the permission only for fully specified arn's for keys that are used for the encryption of the volumes of scheduled instances.
Thanks,
Arie

Yes, this was a problem I wrestled with.  In our case, that is almost all of our KMS keys.  Our Terraform configuration for our services generates a KMS key for every group of systems dedicated to a given customer.  I thought about adding a parameter to the template to allow the user to provide a list of key ARNs to grant, but I'll be honest my cloudformation skills aren't that high.
Is this something we could solve via tagging?   As in, "if you tag a KMS key with a scheduler tag, we will add the kms:createGrant privileges as needed to the scheduler's IAM role"

I have come across this too. But may I know how is it related to starting of instances with encrypted volumes which requires createGrant permission ?

@prateek121 long story short, for EC2 to be able to start an instance that accesses encrypted EBS volumes, the EC2 hardware/hypervisor must have access to use the encryption keys for the volumes in question.  Typically this means the principal requesting that the instance be started must have the authority to offer a grant of key access to the EC2 service.  Because instance scheduler runs a lambda function that has an IAM role associated with it, that role needs access to createGrant to the necessary keys.

I see its not stopping the instances with encrypted volumes after giving kms:createGrant permission
However, Before giving the permission I see at-least it did stop the instances and started a few instances with encrypted volumes.

Thanks @arieleeuw @duckfez .
Sorry, I see the documents updated.
I had an earlier document downloaded and viewed in chrome from local.
What I did was apart from createGrant(which was not enough or wasn't working) I have given the permission for list* and describe* and it worked as expected in all accounts.

Closing this PR but please let us know if something still needs to be addressed.


ListPodSandbox: bad wiretype for field runtime.PodSandboxFilter.State

Problem appeared when running local-up-cluster from current kubernetes master branch (28c439dcfb03832044469f035319daf53d60267e) with current cri-o master.
Hope it's OK to describe it using my standard debug print that prints which GRPC request is passed to ocid and what is the result of this request: https://github.com/intelsdi-x/cri-o/commit/ab854dde116c3a00b1ea6c7cd0f97abcfc275d19
Steps to reproduce:

Start ocid and local cluster.

$ sudo /home/go/bin/ocid --runtime $(which runc) --log /home/jlakis/ocid.log --debug
# EXPERIMENTAL_CRI=true LOG_LEVEL=6 CONTAINER_RUNTIME=remote CONTAINER_RUNTIME_ENDPOINT=/var/run/ocid.sock ./hack/local-up-cluster.sh -O

During first 1-2 minutes of running cluster, ListPodSandbox is failing sometimes:
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  OK
GRPC query -->  ListContainers
GRPC query -->  ListContainers  OK
GRPC query -->  Status
GRPC query -->  Status  OK
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  OK
GRPC query -->  ListContainers
GRPC query -->  ListContainers  OK
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  OK
GRPC query -->  ListContainers
GRPC query -->  ListContainers  OK
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0

After that, ListPodSandbox is failing more often (actually it is passing sometimes):
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox  OK
GRPC query -->  ListContainers
GRPC query -->  ListContainers  OK
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0
GRPC query -->  ListPodSandbox
GRPC query -->  ListPodSandbox  ERROR:  proto: bad wiretype for field runtime.PodSandboxFilter.State: got wiretype 2, want 0

What is expected:
Passing ListPodSandbox request.
cc @mzylowski @runcom @sameo

weird, @nalind could you also take a look? seems like, at some point, we start returning some bad state from sandboxes (which might be related to storage? just wondering)

After my short check: error requests even do not enter to ListPodSandbox method in sandbox_list.go, the problem is somewhere else.

Is there a protobuf diff between what we have vendored and upstream? If so, we can try to bump up our version.

@mrunalp I came yesterday to do the same conclusions.
8 days ago this was merged into k8s master: https://github.com/kubernetes/kubernetes/pull/39158
So k8s try to talk with cri-o server via new API.
I tried to bump k8s version via running hack/vendor.sh
After that is problem with building vendor package: github.com/containers/image because some files are now in k8s.io/apimachinery. To workaround this I just copy missing files (pkg/utils/net and pkg/utils/errors) . This commit is related: https://github.com/kubernetes/kubernetes/commit/67fac70ea307c04487027062c0f669883a6ecee2
After that I realized there will be a lot of changes in server side to work with new kubelet api. I started some changes and published it in https://github.com/kubernetes-incubator/cri-o/pull/342
@runcom @mrunalp Should I continue my work with updating server side to new api version?

That would be great, we're trying to solve the issues in containers/image as we speak though

Hmmm I'm not sure why I came across vendor problem in containers/image. This commit should fix it: https://github.com/containers/image/commit/6cb9b80664939f7235eca93748781ffa75df7853

@mzylowski this should also fix this issue with c/image https://github.com/containers/image/pull/223 but we're actually stuck with some issues with vendoring OCI/image-spec

I described my problem in more details here: https://github.com/kubernetes-incubator/cri-o/issues/343
I created new issue because with @jjlakis we think there is additional problem with vendoring script.
For now we will continue solving #342 with manually copied missing packages.

After #342 this can be closed.


Add jasonrudolph.yml to list of people

I'm enjoying the conference. I'd love to be listed on the website. :octocat::heart:


Added FSMTableControl to editor main screen

This main screen panel is intended to make it easier to edit transitions of complex state machines.

If this is in a usable state (or even a good starting point), feel free to open a PR draft or something :)
Welp, you asked for it! Now you got it! I'd probably describe this as a starting point.

This is mostly copied from what I quickly hacked together. I did do some clean up, and tried following the conventions that were already there.
I'm still a new to GDScript, so there may be better ways to do some of this.
State Names
The name of the node is used for the state labels and for the table cells.
When a cell is cleared, its corresponding transition is removed from the scene.
When a cell text, the target state is looked up by path, relative to the state machine. If no state can be found, then the cell is reset back to its previous state and no action is taken.
Event naming
If a transition has use_event set, then the name set in the event field is used in the headers.

If a transition does NOT have use_event set, then the script name is used.

Transitions
When creating a transition:

If the event name is a script path (starts with res://), use_event will be set to false, and the script is attached to the newly created transition.
If the event name is NOT a script path, use_event is set to true, and event is set to the event name.

When updating a transition:

Only the next_state is updated.

Other Notes

Undo is sadly not supported right now.
There is no way to add new states or new events through this control.
Added an example of an unrealistly large FSM

Thank you for your contribution! I am kinda swamped with uni work right now, so give me some time to review these additions and your other PR! I have several notes:

Firstly, I don't think a main screen plugin-in is necessary for this. If you have other plugin installed the top bar can get crowded. It looks nice, but there should be a better place for this. For example the dock where the animation player is. (It could also only appear when selecting a FSM)
Regarding the layout of the table. I am not sure if this is the layout that is the most logical for something like this. It's a good starting point, but in the future something like this would probably be better:

[+] IDLE
- onStartMoving | [transition to] MOVING
[+] MOVING
- on StopMoving] | [transition to] IDLE

This would be way more work tho. Maybe I find some time to implement this

Closing some old PRs right now. I think this would be great as a standalone expansion for this addon, but is ultimately to niche in use for it to take a whole main screen slot.


Added Unit testing with pytest

Added initial file structure and sample unit tests. Updated requirements to support unit testing.
Tested with end-to-end testing to ensure no functional changes to LDAR-Sim. Logs will be attached. unit_testing_logs.zip

Could we get some sort of naming / numbering convention for the unit tests, add that into the documentation and change the existing unit tests to follow the convention that is written out? Otherwise, it's looks good.

Unit testing has been refactored to have a consistent file structure and naming convention


Build failure: windows-sys v0.52.0 with windows-targets 0.52.1

Summary
After updating windows to v0.53.0 windows-sys v0.52.0 no longer builds. This seems to be a seperate issue from #2869.
error: no rules expected the token `#`
  --> C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\windows-sys-0.52.0\src\Windows\Win32\NetworkManagement\IpHelper\mod.rs:6:50
   |
6  | ::windows_targets::link!("iphlpapi.dll" "system" #[doc = "Required features: `\"Win32_Foundation\"`"] fn CancelMibChangeNotify2(notificat...
   |                                                  ^ no rules expected this token in macro call``

Crate manifest
https://github.com/starship/starship/pull/5789
[package]
name = "starship"
version = "1.17.1"
authors = ["Starship Contributors"]
build = "build.rs"
categories = ["command-line-utilities"]
documentation = "https://starship.rs/guide/"
edition = "2021"
homepage = "https://starship.rs"
# Keep `/` in front of `README.md` to exclude localized readmes
include = [
  "src/**/*",
  "/starship.exe.manifest",
  "media/icon.ico",
  "build.rs",
  "LICENSE",
  "/README.md",
  "docs/.vuepress/public/presets/toml/",
  ".github/config-schema.json",
]
keywords = ["prompt", "shell", "bash", "fish", "zsh"]
license = "ISC"
readme = "README.md"
repository = "https://github.com/starship/starship"
# Note: MSRV is only intended as a hint, and only the latest version is officially supported in starship.
rust-version = "1.65"
description = """
The minimal, blazing-fast, and infinitely customizable prompt for any shell! ☄🌌
"""

[features]
default = ["battery", "notify", "gix-max-perf"]
battery = ["starship-battery"]
config-schema = ["schemars"]
notify = ["notify-rust"]

# Enables most of the `max-performance` features of the `gix` module for better performance.
# This can be more difficult to build in some conditions and requires cmake.
gix-max-perf = ["gix-features/zlib-ng", "gix/fast-sha1"]
# Slower than `git-repository-max-perf`, but better than the default.
# Unlike `git-repository-max-perf` this does not require cmake and allows dynamic zlib linking.
gix-faster = ["gix-features/zlib-stock", "gix/fast-sha1"]

[dependencies]
chrono = { version = "0.4.34", default-features = false, features = ["clock", "std", "wasmbind"] }
clap = { version = "4.5.1", features = ["derive", "cargo", "unicode"] }
clap_complete = "4.5.1"
dirs-next = "2.0.0"
dunce = "1.0.4"
gethostname = "0.4.3"
# default feature restriction addresses https://github.com/starship/starship/issues/4251
gix = { version = "0.58.0", default-features = false, features = ["max-performance-safe", "revision"] }
gix-features = { version = "0.38.0", optional = true }
indexmap = { version = "2.2.3", features = ["serde"] }
log = { version = "0.4.20", features = ["std"] }
# notify-rust is optional (on by default) because the crate doesn't currently build for darwin with nix
# see: https://github.com/NixOS/nixpkgs/issues/160876
notify-rust = { version = "4.10.0", optional = true }
nu-ansi-term = "0.50.0"
once_cell = "1.19.0"
open = "5.0.1"
# update os module config and tests when upgrading os_info
os_info = "3.7.0"
path-slash = "0.2.1"
pest = "2.7.7"
pest_derive = "2.7.7"
quick-xml = "0.31.0"
rand = "0.8.5"
rayon = "1.8.1"
regex = { version = "1.10.3", default-features = false, features = ["perf", "std", "unicode-perl"] }
rust-ini = "0.20.0"
semver = "1.0.22"
serde = { version = "1.0.197", features = ["derive"] }
serde_json = "1.0.114"
sha1 = "0.10.6"
shadow-rs = { version = "0.26.1", default-features = false }
# battery is optional (on by default) because the crate doesn't currently build for Termux
# see: https://github.com/svartalf/rust-battery/issues/33
starship-battery = { version = "0.8.2", optional = true }
strsim = "0.10.1"
systemstat = "=0.2.3"
terminal_size = "0.3.0"
toml = { version = "0.8.10", features = ["preserve_order"] }
toml_edit = "0.22.6"
unicode-segmentation = "1.11.0"
unicode-width = "0.1.11"
urlencoding = "2.1.3"
versions = "6.1.0"
which = "6.0.0"
yaml-rust = "0.4.5"

process_control = { version = "4.1.0", features = ["crossbeam-channel"] }

guess_host_triple = "0.1.3"
home = "0.5.9"
shell-words = "1.1.0"

[dependencies.schemars]
version = "0.8.16"
optional = true
features = ["preserve_order", "indexmap2"]

[target.'cfg(windows)'.dependencies]
deelevate = "0.2.0"

[target.'cfg(windows)'.dependencies.windows]
version = "0.53.0"
features = [
  "Win32_Foundation",
  "Win32_UI_Shell",
  "Win32_Security",
  "Win32_System_Threading",
  "Win32_Storage_FileSystem",
]

[target.'cfg(not(windows))'.dependencies]
nix = { version = "0.27.1", default-features = false, features = ["feature", "fs", "user"] }

[build-dependencies]
shadow-rs = { version = "0.26.1", default-features = false }
dunce = "1.0.4"

[target.'cfg(windows)'.build-dependencies]
winres = "0.1.12"

[dev-dependencies]
mockall = "0.12"
tempfile = "3.10.0"

[profile.release]
codegen-units = 1
lto = true
strip = true

[[bin]]
name = "starship"
path = "src/main.rs"

Crate code
No response

Looks like this was fixed in #2868


Implement _check

Delete me and write your Pull Request message here!

more pending changes to be pushed, will create a new request


403 If SendMessage with SixPartsKeys

When I use Whatsapp.mobileBuilder().newConnection(SixPartsKeys.of(str))
SendMessage returns 403 after a few seconds after success.

Known issue being tracked in https://github.com/Auties00/Cobalt/issues/433
This issue is already fixed in the private repo, if you are interested contact me on telegram @auties00
Eventually it will come to the open source version as well


[Bug]: SQLTableSchema is not working for schemas other than dbo

Bug Description
Hi Team,
We are trying to perform text to sql operation and we are using SQLTableSchema as part of that. In this case, we are passing table name without prefixing schema. Even if we pass prefix, it is giving below error:
NoSuchTableError(f"{owner}.{tablename}")
sqlalchemy.exc.NoSuchTableError: None.ch.product
Schema here is ch.
How to fix this? Since by default in MS SQL server, sqlalchemy consider dbo. as schema. But, if we have different than 'dbo.', how to handle them?
Version
latest
Steps to Reproduce
Please follow the description
Relevant Logs/Tracbacks
No response

I thiiiiink dosu is correct here? Give that a shot


I could not find the third bug.

The program runs perfectly and it handles all the exceptions carefully.

lol, I wish!! 🤣


Clean up Document Structure, add initial reflection skeleton, add heroku link to readme.

reviewed request - found no issues. Merged as requested.


fixAdd container graceful exit logic

Proposed changes
Add FE container and BE container to execute the logic of the Stop script when executing the exit command to ensure that the metadata is written successfully and minimize the restart exception caused by BEBJE.

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

run buildall


Fix the problem that the script name corresponds to the configuration file and does not match the 3.0.1 upgrade document

Fix the problem that the script name corresponds to the configuration file and does not match the 3.0.1 upgrade document

Purpose of the pull request
Fix the problem that the script name corresponds to the configuration file and does not match the 3.0.1 upgrade document

Brief change log
1、修改了 install_config.sh的名称
2、修改了script目录下status-all.sh对应关联到新名称install_config.sh的内容

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

@SbloodyS OK,already adjusted

@SbloodyS Hello，The automatic code merge failed. I found the problem. Do I need to resubmit PR?

@ke4qqq @SbloodyS Hello，Auto-check is blocked

I am not sure whether we should change our file name or our document description

Oh I missed this. I thought it was the documentations are changed. We should change the doc instead of the file names.

Yeah, I think so, we have already released three versions of dolphinscheduler above 3.0.0, many users already use install_env.sh as config file, so maybe change the document is the better way

@xinxingi Hi, are you still there? do you have time to change our document instead of code?

close due to #13294


(GH-2156) Don't leak scope between targets

When compiling catalogs, we use a single scope object to capture the
current plan scope at the time of the compilation, and then merge in
target-specific information for each compile. However, the compile
method was modifying the single scope object to add its
target-specific info. This caused a race condition whereby the scope
could be modified by another thread and the wrong target inserted and
used for compilation.
This appears to be relatively uncommon at low levels of concurrency,
because the critical section only lasts until the scope has been
serialized to JSON to be passed to the compilation process. Once that's
happened, any external modifications won't affect the current compile.
Due to the GIL, it's impossible for multiple threads to be running that
code at the same time, so the race condition requires a context switch
to happen in the middle of execution. With high concurrency or many
targets being compiled, this is not unlikely.
We now merge the target-specific data rather than inserting it
directly, so each target gets a copy of the scope. We also freeze the
scope for good measure, to avoid any such issues popping up in the
future. This does not have a significant impact on memory usage as each
scope hash still refers to a single copy of the actual underlying
data.
Fixes #2156
!bug

Prevent data for the wrong target being used when compiling apply() blocks
(#2156)
Previously, a race condition allowed apply() blocks to use data
for the wrong target during compilation. This could cause targets to
apply incorrect or invalid catalogs.

I'm thinking about how to effectively test this in a way that isn't it should not have this specific bug...


Any options for mob limits?

As described here:
https://shockbyte.com/billing/knowledgebase/203/How-To-Change-The-Mob-Spawn-Rate-On-Your-Server.html
Are there any ways to limit the spawning of mobs?
Thanks!

The bukkit.yml file not directly managed by the image, so simply supply your own via the data and config mounts.

I wasn't sure if it was a function of their loader, or something that could be added directly to vanilla.   If not, then this can just be closed.
Thanks!


Replaces emoji reactions with button interactions

Description
https://user-images.githubusercontent.com/1903876/120114446-146bc780-c134-11eb-8402-e6e82b397e3c.mov
Checklist

[x] Add tests for these changes
[ ] Test coverage is not decreased
[ ] Entire test suite passes

Codecov Report

Merging #505 (6191b91) into master (3b0fb3b) will decrease coverage by 0.27%.
The diff coverage is 90.00%.

@@            Coverage Diff             @@
##           master     #505      +/-   ##
==========================================
- Coverage   94.53%   94.26%   -0.28%
==========================================
  Files          69       69
  Lines        3442     3450       +8
  Branches      485      485
==========================================
- Hits         3254     3252       -2
- Misses        127      138      +11
+ Partials       61       60       -1

Impacted Files
Coverage Δ

src/spellbot/__init__.py
91.88% <85.00%> (-0.73%)
:arrow_down:

src/spellbot/operations.py
81.65% <94.73%> (+2.62%)
:arrow_up:

src/spellbot/data.py
100.00% <100.00%> (ø)

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 3b0fb3b...6191b91. Read the comment docs.


Is this still alive?

Is this project still alive?

Yes.

Reason I asked was because the last commit was 2 years ago

It's deployed at K-Space and maintained by Lauri. He's also busy for a year or so for now.
All contributions are welcome. He probably has little motivation (and more importantly, time) to add new features himself (as it works).

Only Ubuntu 16.04 supported?  https://github.com/laurivosandi/certidude/blob/master/certidude/cli.py#L1037


changing persistence engine trait to an abstract class

Can one of the admins verify this patch?

Hi @nirandaperera, can you create the jira with the issue you are fixing here. That way we would know why this change was done.

Jenkins, test this please.

(and yes would be great to create a jira ticket and put the title here)

Merged build triggered.

Merged build started.

Test build #31540 has started for   PR 5832 at commit 67b9d5a.

Test build #31540 has finished for   PR 5832 at commit 67b9d5a.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
abstract class PersistenceEngine

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31540/
Test PASSed.

I created the JIRA ticket: https://issues.apache.org/jira/browse/SPARK-7307


Action Controller images

Allows images to be added to the action controller through @BasThomas pod
Requires pod install
I just added the code and the pod name in the podfile. I did pod install and run to make sure it worked.

Addresses  #2047
Sure I can add the pod

@Huddie mind fixing the conflicts?

@rnystrom not at all!
Sent with GitHawk

Not ready to merge yet

@rnystrom Okay, I tested it. Should be up and running.


Crash on load kernel module.

I am loading a kernel module from an application in user mode,
Using the API taihen, as follows:
SceUID modkernel = taiLoadStartKernelModule("ux0:/mylib.skprx", 0, NULL, 0);
Always the first time I run the application after having installed henkaku, it crashes, the second no longer gives the crash, and works great!
It should be mentioned that the user application, it imports prx functions,
In the module_start, no action is performed,
Could someone help me solve this problem?
Any help will be appreciated.

I don't know exactly but here are a few examples of a user application loading a kernel module
https://github.com/xerpi/hidmouse/tree/master/skprx
https://github.com/TheOfficialFloW/VitaShell/search?utf8=✓&q=startusb&type=Code

Hello,
I had already tried and reviewed both samples,
The difference is that they do not export in the prx, and import in the application.
I suppose, some of that is the cause in my particular situation.

Importing happens at launch. If the module is not loaded then, the import stubs are not filled.

Any idea how to fix it?
Maybe get the functions dynamically?

Well one solution is to make a wrapper suprx that imports functions from skprx. Then use the weak import of the suprx. So for example, userprx imports from kernelprx and has wrapper functions to kernelprx

From eboot.bin load kernelprx.skprx
From userprx.suprx export wrapper calls to kernelprx.suprx
From eboot.bin load userprx.suprx
Make calls to imported userprx.suprx wrapper functions

The problem is that kernel modules cannot export weak symbols (that's a Sony limitation I guess) but user modules can.

Thank you very much @yifanlu !
It works great, yes, it's a bit more work, but, in the end, what's important is that it works.
Thanks again yifan, I proceed to mark this case as solved.


Focus not restored properly after hovering over a symbol while debugging

When debugging and having the debugger on break, hovering over any symbol changes the cursor focus to text editor instead of back to the UI element which was previously focused on. This issue manifests when I use the document search while the debugger is paused and the focus suddenly changes back to editor without touching any keys other than enter in order to jump to the next search result.
To Reproduce

Start debugging the application.
Hit Pause in debugger.
Open up the document search box (CTRL-F) and type something in the field.
Move the mouse cursor over any symbol (function, variable etc.) in the editor which prompts the inspector/info box.
Move the cursor away to dismiss the info box.
Observe the focus changing back to the previous cursor location in text editor instead of back to the search box.

Expected behavior
The focus should be restored back to the previously active element instead of the text editor.

OS and Version: Windows 10
VS Code Version: 1.41.1

Thanks for filling this issue. We have pushed a fix and you can try vscode insiders from next week to verify the issue got fixed.
Now we only focus back the editor if the debug hover actually had focus.


Revert "[test][IRGen] Split out objc-interop specific part in abitypes.swift"

This reverts commit 23db49b4704f0a955be1a1a5fd7cff5369ecb542. Accidentally merged without Windows CI check

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves #NNNNN, fix apple/llvm-project#MMMMM.

@swift-ci Please smoke test


the trait reqsign::request::SignableRequest is not implemented for Request

I try the example here but there is a compile error at signer.sign(&mut req)?;, showing: the trait reqsign::request::SignableRequest is not implemented for Request.

Maybe you need to enable feature reqwest_request?

solved by enable reqwest_request, thanks a lot.


Deprecated Event

Creation of dynamic property TakiElias\Tablar\Tablar::$events is deprecated in /Users/corean/Dropbox/Sites/cccf2/vendor/takielias/tablar/src/Tablar.php on line 60

Laravel v10.13.0 (PHP v8.2.5)

@corean I could not reproduce the issue. Could you please explain in more detail?

@takielias
I looked it up and it's a PHP8.2 issue.
https://stitcher.io/blog/deprecated-dynamic-properties-in-php-82
I switched to php8.1 and got peace of mind. :D

@corean I see. Also tried PHP 8.2 but did not get any error yet. Could you please mention exactly when did you get the error?

@corean I have added a fix https://github.com/takielias/tablar/commit/3225dc543c66e0caa9661c955cdebbe89cc5f9ad for PHP 8.2 . Please update the packages using composer update command.

@takielias Wow, thank you.


Test migration to Datanode

Test that supertanker can handle migrations from traditional Graylog+OpenSearch deployments

For the purposes of testing datanode migrations, I suspect docker compose is going to be the better vehicle.
While supertanker does have configurations for Graylog 6.0 + OpenSearch and Graylog 6.1 + datanode, I've never tested upgrading/migrating from one configuration to the other. (I have tested upgrading between 6.0.x builds and between 6.1.x builds, but not an upgrade from 6.0.x to 6.1.x)
I've heard some positive feedback that supertanker makes it easier to try datanode out for the first time, and that seems like a more proper use for supertanker than trying out migrations between major product versions.
ps. Point taken though -- supertanker could better document its intended use-cases, so that we aren't leaving anybody guessing about what's in scope 😀


How to combine Redux Form and react-datepicker

if only datepicker so easy but i have form use range picker i can't work. Any ideal for Range Picker in Redux Form .
Link Lib i used
https://github.com/Hacker0x01/react-datepicker

Please ask for usage support on StackOverflow.


Add threaded benchmarks

This PR adds threaded benchmarks

Interesting, the gray shortwave performs worse with threads, but everything else looks to be much better.

bors r+

bors r+


Angular v16 support

I guess it is just a dependencies update....really simple.
Thanks.

Any info when it might be done? 😅

Angular
@coreui/angular
note

16.x
~4.5.x
latest

15.x
~4.4.x
with standalone components

15.x
~4.3.x
deprecated

14.x
~4.2.x

What is the schedule for the pro 4.5.x ?


net: socket: dtls: handle multiple fragments in sendmsg()

Is your enhancement proposal related to a problem? Please describe.
Using sendmsg() API does not work for DTLS connection, as fragmented data is not properly sent as a single DTLS record.
Describe the solution you'd like
Ideally, there should be a 'gather' write/send API in mbedTLS or alternatively an explicit "send flush" request (as implemented in https://github.com/Mbed-TLS/mbedtls/pull/4188).
Describe alternatives you've considered
Currently mbedTLS does not support 'gather' write, so as a workaround an intermediate buffer can be allocated to "linearize" all data passed to sendmsg() and then request single mbedTLS write.
Additional context
Related bug report: #45948

If an application-message (or dtls-record) is split in several UDP packets, I'm not sure about the reliability of the outcome. That opens also a too large DoS door, sending a lot of data (upd-packets), but not that last upd-packet keeping the other peer holding data, but can't verify the MAC in order to withdraw it.
In my opinion, such an approach doesn't make too much sense for so much trouble.

@boaks It is about sending fragmented data (many application chunks) as single dtls-record, not the other way. The problem that we have right now is that sending multiple chunks with single sendmsg() API call results in each chunk being sent in separate dtls-record. What we want is sending all the chunks together (linearized and authenticated/encrypted) in single dtls-record.

We will see, if that pays off.
In my experience, the really benefit of the UDP style is to let an upper layer do, what could be done better there. I don't know, why the application emit small chunks, but maybe there is also a better application specific way to group them.

Some additional considerations:
In difference to TCP, UDP includes the application payload length into the UDP messsage (see RFC 768. Therefore, in difference to TCP, is you send
UDP-1 8 bytes, UDP-2 16 bytes, and , UDP-3 6 bytes.
you will always receive/read on the peer exactly one of these messages, may be in different order (in my experience really rare) or some dropped (in my experience 2%). But you never read assembled messages, e.g. UDP-2+3 22 bytes.
This also reflect the usage of the API, the sequence of bytes passed to sendto is considered to be the same as recvfrom (also different to TCP).
Maybe, the idea is to "relax" that to the behavior of TCP. In my experience, that doesn't work to well, UDP based protocols are frequently using that UDP message length.
That will raise the question, where the length of the fragments are going to be included. The UDP message will only contain the overall length (including the DTLS header). If you put multiple DTLS records in one UDP message, then the length of the fragments will be encoded in the DTLS record. Such a solution may just encrypt the fragments and collect the resulting DTLS records in one UDP message. That solution will then result in
1x UDP-header: IPv4 20 bytes + UDP 8 bytes. => 28 bytes
Nx DTLS-header + MAC, e.g. AES-CCM: header 13 bytes + nonce 8 bytes + MAC 16 bytes. => 37 bytes
Assuming 4 fragments, the saving will be 3x 28 bytes.
Alternative solutions will in my opinion either change the grants of  sendto/recvfrom  or will add an additional "application side layer" (top of dtls).
So, please, do not only describe your idea on a high level, please add more details about the intended implementation.

Just an additional stackoverflow link about sendmsg. With that, it's  just intended to accumulates the data into one message, so one dtls record and one udp packet.

Just an additional stackoverflow link about sendmsg. With that, it's just intended to accumulates the data into one message, so one dtls record and one udp packet.

That is exactly what this issue is about!

This is still a valid request, so keeping it open. Maybe I could find some time to look into this closer.


Migrate from MITyCLib to xades4j

Rework xades-firma to use xades4j in place of MITyCLib.
This removes the need to package the MITyCLib libraries as a shadow jar, since xades4j is available via maven central repo.

Sadly, testing against the SRI pruebas ambiente rejects facturas signed with this version of the library.
Attached are versions of a factura signed using the previous MITyCLib implementation, and also with this xades4j implementation.
The xades4j version can be sent to SRI via 'enviar' web-service. But a subsequent attempt to authorize the factura via 'autorizar' web service results in:
{"mensaje":[{"identificador":"39","mensaje":"FIRMA INVALIDA","informacionAdicional":"La firma es invalida [Firma inválida. El certificado firmante no es válido.]","tipo":"ERROR"}]}

Requires further investigation to resolve.
factura_27922910115.MITyCLib.xml.txt
factura_27922910115.xades4j.xml.txt

Suspicion falls on the SRI validation service (which we know uses MITyCLib) not handling the
 line ending characters correctly...

Some related discussion, without resolution, at xades4j #259

Following up on &13#; line-endings, see issues such as:
https://bugs.openjdk.org/browse/JDK-8264194
https://github.com/eclipse-ee4j/metro-jax-ws/issues/93#issuecomment-563406285

Following commit 9d6df9a, signatures are added without any line breaks (and therefore no
 chars in the certificate. See example attached.
Still rejected by SRI:
{"mensaje":[{"identificador":"39","mensaje":"FIRMA INVALIDA","informacionAdicional":"La firma es invalida [Firma inválida. El certificado firmante no es válido.]","tipo":"ERROR"}]}

So, line breaks are probably not the source of the problem... :(
factura_27922910115.xades4j_3.xml.txt


Theo's solution

Hi @tampakrap ;)
Thanks for try our challenge. My team mates will contact you shortly.
Thanks!


Fix logging bug

Description of changes

Fixes #242

Test plan
This change has been ran against the existing tests and all of them pass.
Documentation Changes
No user-facing documentation is affected.

This was integrated into this PR, https://github.com/chroma-core/chroma/pull/244
thanks for taking a look at this!


Create Guide.md

This is a rough, but adequate Markdown version of the guide from the site of how to do the lab,

This is very much needed


Proposal of a rework of HID device names

Hi,
this is a proposal for a more detailed and more robust naming of HID devices.
It covers:

HIDDMXDevices always have a serial number, thus it is appended in parenthesis to be able to distinguish several connected devices.
Those HIDJSDevices that expose a serial number append it in parenthesis as well.
HIDJSDevices not exposing any product or manufacturer name use VID:PID as a naming scheme instead. (Previously those had a completely empty name.)

I'm open to changes of course.

coverage: 32.007%. remained the same
when pulling 13f3ea93845b2fb8ba16e56ff0a719a9c627c365 on qfulmina:dev-add-hid-device-serial-number
into bfa4d2dd4a0b5e5dfbb195a654b9b73c499a8253 on mcallegari:master.

Sure:

Sorry for the bad crop (missing the first letter and the closing brace on the second line). Right now I don't have those devices around. I hope you get an idea. (I can prepare another screenshot once I get back to the devices.)
First one didn't tell any name thus showing vendor ID and product ID.
The second did expose a name. And a serial number: AZ-RB- ... .

For devices with no name/vendor I would give them a generic name like "HID Input device (VID:PID)" with VID/PID toUpper()

Alright, will rework that.

Changed it accordingly and it looks great:


fix revert add component statuses

This is a fix for the revert "Add Component statuses" (https://github.com/abonas/kubeclient/pull/137)
re-adding the component status entity

@dkorn @abonas have you figured out what was failing (at first sight it seems the same patch)

@simon3z I missed a rebase on a PR that changed a method name

@simon3z I still don't understand how this could be merged (and was all green) and not blocked/indicated by github that it can't be merged, especially given that the method change was merged 2-3 days before this one so there were no race conditions


Please could you use HTTPS on your websites ?

It's possibne to setup https certificate for your dev and demo webpages ? Usage only http is something very very untrusted :)

and the authors would need to pay for an ssl cert for a demo site that has no need for one... its just a demo of the app after all.


OffsetCommitRequest changes in 0.8.2?

We were running into KAFKA-1451 repeatedly so we're trying out a build of 0.8.2 from trunk. We've noticed that OffsetCommitRequests no longer work because the protocol now expects a long long "timestamp" in the struct between the "offset" and "metadata" fields. We've tried changing the type and protocol definitions and can get Kafka to accept the request now -- previously, we would get a "FailedPayloadsError" because Kafka had an (understandable) underflow on read.
Unfortunately, we now get error code 15 (ConsumerCoordinatorNotAvailableCode).
The change in question was part of KAFKA-1012, but I can't (yet) figure out from that why the protocol changed or what this error means.
Has anyone else run into these problems?

yes -- see KAFKA-1841 .  The api versioning issues w/ OffsetCommitRequests will be cleaned up before 0.8.2 is released.  Unfortunately, until then it is difficult for kafka-python to support trunk deployments.
and agree -- 1451 is a nasty one.


Symfonisk speaker is not picked up by discovery

Support for the Sonos/IKEA smart speaker Symfonisk was added in release 1.04, link to model.json, but it was not picked up by auto-discovery as expected after updating powercalc.
Image from Home Assistant showing the device info:

Support for Sonos ONE was added in same release, and that was picked up by auto-discovery.

Either the model directory or one of the aliases needs to match with the model in HA.
So that must be "SYMFONISK Bookshelf".
Could you make a PR to correct this?

Should the attribute name include manufacturer? i.e. instead of "name": "SYMFONISK Bookshelf", it should be "name": "Sonos SYMFONISK Bookshelf"?

Should the attribute name include manufacturer? i.e. instead of "name": "SYMFONISK Bookshelf", it should be "name": "Sonos SYMFONISK Bookshelf"?

name is only used for the supported models listing. It is not used for the discovery routine.


Support for pre-dump and iterative checkpoint

What is the problem you're trying to solve
Hi guys, in order to move container from host 1 to host 2, currently we can use ctr checkpoint command to freeze the container on source and create a checkpoint image out of that, export its image files to destination and started the container with ctr restore. I wanted to further enhance this by implementing the iterative migration functionality using pre-dump. Currently iterative migration is supported on runc, and I would love to hear your thoughts on the possibility of having this feature on containerd level as well.
Describe the solution you'd like
A pre-dump flag/option with the checkpoint command, which will then enable us to perform iterative migration, Similar to how runc achieves this
//perform pre-dump and specify './parent' as it image-path
# ./runc checkpoint --pre-dump --image-path ./parent test
//criu dump. './image' as image-path and relative path '../parent' as the prev-image-dir
# ./runc checkpoint --image-path ./image/ --parent-path ../parent test

Additional context
I want to take a shot at implementing this, but would like to run this by and get some thoughts, ideas and a starting point on the matter.

/aasign

/assign


There is no available call for changing the user's email.

Added.
Worst case scenario, you may proceed without this for the Wednesday's launch. So lowering its priority.

This works!


Timescale link doesn't exists.

Link doesn't exists. README points to this URL, and the link doesn't exists.
https://docs.timescale.com/use-timescale/latest/services/create-a-service

@meera Thanks for pointing out - does https://docs.timescale.com/getting-started/latest/services#create-your-timescale-account work for you instead?

Updated URL looks good.
Can you consider adding instructions on connecting with other Postgres serves? It will help people like me who didn't know about Timescale.

What are your suggestions? Which other services work with create-llama?

Closing this as Timescale is the number one search for a hosted Postgres with pg/vector


List query returns 5000 objects

Issue: The address list method returns 5000 objects even though the debugs show the limit params set to 10000. This leads to certain list filters appearing not to work because not all of the objects are being returned.
Results:
2024-12-10 15:22:05,318 [DEBUG] https://api.strata.paloaltonetworks.com:443 "GET /config/objects/v1/addresses?limit=10000&folder=Prisma+Access HTTP/11" 200 180222
5000 #print(len(response))

Native API call with a limit of 6000
{{baseURL}}/config/objects/v1/addresses?folder=Prisma Access&limit=6000
{
   "offset": 0,
    "total": 5943,
    "limit": 5000
}

Conclusion: In order to get all records over the 5000 limit the application will need to use offset of 5000 and perform multiple API calls as needed. I'm not sure how pan-scm-sdk should handle this issue, but sharing for awareness.

@mrcloudmustache I have a working proof of concept wanted to do a quick sanity check to see if it would help:
link to commit
from scm.client import Scm
from scm.config.objects.address import Address

# Replace these with your actual credentials
CLIENT_ID =<EMAIL_ADDRESS>CLIENT_SECRET = "12345678-4321-1234-5678-123456789012"
TSG_ID = "1234567890"

# Initialize the SCM client
client = Scm(
    client_id=CLIENT_ID,
    client_secret=CLIENT_SECRET,
    tsg_id=TSG_ID,
    log_level="INFO",
)

# Initialize the Address manager
api_client = Address(client)

existing = api_client.list(folder='Texas')

print(len(existing))
6179

The logic certainly makes sense. It's what I had in my head but even cleaner.

@mrcloudmustache update completed. also provided a parameter in the class object instantiation that will allow you to control the "max_limit" used by the class, increasing or decreasing the amount of objects returned in a single request (default is 2500, max will always be 5000 until the API changes).
Documentation has been updated accordingly, showing how to use this new feature, but know that using the list() method going forward will always return every instance, the max_limit simply controls how many to return in a single request. version bumped to 0.3.6


[Bug]: EmbedDocsWorkflow fails because of cozo resource busy

📜 Description
At high enough concurrency and on dev server, EmbedDocsWorkflow fails with:
worker-1   | rocksdb::kBusy::kNone
worker-1   |   × when executing against relation 'snippets'
worker-1   |   ╰─▶ RocksDB error: Resource busy:
worker-1   |   help: This error is usually outside Cozo's control

Need to investigate why this is happening, probably need to do one of:

[ ] throw 429 if resource busy
[ ] retry on resource busy
[ ] tune rocksdb options
[ ] investigate hardware
[ ] investigate cozo

👟 Reproduction steps
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

I made a hotfix for raising 429 on resource busy but it's not getting retried @HamadaSalhab

http://agents-api-dev:9000/namespaces/default/workflows/ad519588-a143-47df-8cc8-95920b36bc00/ab7f88b8-1fd4-4613-bbf4-1b23ed58d31a/history


Fixes Conditions.notIn() by using 'In.createNotIn()'.

Fixes Conditions.notIn() by using 'In.createNotIn()'.

Thanks for finding and fixing this.
Could you provide your full name in ASCII, so we can properly attribute you in the source code?

Thanks for finding and fixing this.
Could you provide your full name in ASCII, so we can properly attribute you in the source code?

Thanks for finding and fixing this.
Could you provide your full name in ASCII, so we can properly attribute you in the source code?

Meng Zuozhu

Thanks for finding and fixing this.
Could you provide your full name in ASCII, so we can properly attribute you in the source code?

Meng Zuozhu


add @KRaude as a contributor

@all-contributors, please add @KRaude for userTesting, bug, code.

@all-contributors, please add @KRaude for userTesting, bug, code.


define relativeYearlyProfit, fix #2190

ping @stereohelix

Woa I pushed a lot more than I was supposed to, I meant only pushing this: https://github.com/askmike/gekko/pull/2191/files#diff-4576ecad1424860463a76f12621bbaeb

Rebased, see here: https://github.com/askmike/gekko/commit/f948a2d347faab8270b9336bdaafe16ae57526bd


Merge aws-config into develop-2020-aug

Hi Rohin - If this merge goes through it will contaminate the target branch with test code. Can you add your scripts directly into the target branch without involving your aws-config branch? Basically redo on the develop-2020-aug branch what you did on your aws-config branch?


Publish npm package

https://www.npmjs.com/package/@zondax/ledger-arweave

done https://www.npmjs.com/package/@zondax/ledger-arweave


Added FACT(expr) function. Fixed AbstractOperator and AbstractUnaryOp…

…erator with final for LazyNumber.
Redid the commit and got rid of all the mess in the diffs.

Thank you very much, that is a lot easier to review.
There are still the two finals changes which seem superfluous.
@uklimaschewski With the exception of the finals being added, looks good to me. The implementation is a little bit "naive", as in there are faster implementations available, but this seems okay to me, especially as the user still has the ability to override this with their own implementation, if needed (and if they already have their own, this will not impact them).

IDEA threw an error saying that the finals are required as they are accessed from in an inner class, refused to compile without them."Variable v1 is accessed from within inner class, needs to be declared final". is the exact message.

As for the algorithm, I went for the simplest method, avoiding recursion. I don't like recursion because it can quickly cause an out of memory error, especially if someone tries to do something like FACT(1000).

@DesigningKnights I think you should create a new branch to submit your PR instead of modifying the master branch directly. In addition I have submitted another PR(#176) specifically to solve the problem of finals.
@RobertZenz


Updated: License lower case and readme

Self explanatory. Aims to update the remade with some useful information.

Hey, @Mee12345, please merge ASAP.

@Vurv78
I did not write the original lines of the original author.

Capitalisation of README and LICENSE (along with various other files like INSTALL) is literally GNU convention…
See https://softwareengineering.stackexchange.com/questions/301691/readme-txt-vs-readme-txt

@Derpius
And ? My change does not include only that...

@dvdvideo1234 have you even looked at your own pr

Readme and license are only cosmetic changes, but either way. Reverted the name with capital letters.


Pass own AWS/EC2 endpoint

We have an EC2-compliant stack on premise and are starting to evaluate docker-machine
The EC2 CLI itself seems to take an EC2_URL environment variable, so we can use our own on-premise API endpoint.
export AWS_ACCESS_KEY={Write your access key}
export AWS_SECRET_KEY={Write your secret key}
export EC2_URL={Write the endpoint}

Does anyone already have experience using docker-machinethis way?
Cheers,
Michael

I have tried it this way:
$ docker-machine create --driver amazonec2 --amazonec2-access-key=$AWS_ACCESS_KEY --amazonec2-secret-key=$AWS_SECRET_KEY --amazonec2-subnet-id=$AWS_SUBNET_ID dev
client encountered error while doing the request: Get https://ec2.us-east-1.amazonaws.com/?Action=DescribeKeyPairs&Version=2014-06-15: dial tcp: lookup ec2.us-east-1.amazonaws.com: no such hostERRO[0000] Error creating machine: Problem with AWS API call: client encountered error while doing the request: Get https://ec2.us-east-1.amazonaws.com/?Action=DescribeKeyPairs&Version=2014-06-15: dial tcp: lookup ec2.us-east-1.amazonaws.com: no such host
WARN[0000] You will want to check the provider to make sure the machine and associated resources were properly removed.
FATA[0000] Error creating machine

Seems that docker-machine does not read/pass environment variables to the driver.
Is it possible to add an option like --amazonec2-url?

Yes, that should be possible. look in drivers/amazonec2/amazonec2.go

You'll have to make it ignore the region flag I guess

Thanks for the feedback!  I think this would be a good addition.

This in done in #2535


Fix cyclic example

Quick fix for the cyclic analysis example.

Commit history looks weird because I was playing around with github.dev and I didn't realize the default branch was actually the release branch...


SAK-40653 Problem with grade overrides in Spanish sites

@ern Test updated to iterate between two locales, one that use point as decimal separator and one that use the comma.

LGTM!


Add support for mock hardware "simulation" and clean how parameters and arguments in macro are handled.

This PR adds the possibility for trivial mocking of hardware for testing ros2_control in more complex setup and developing without access to the robot.
The PR depends on the functionality added in ros-controls/ros2_control#1028 that enables simple dynamic calculation, i.e., calculates joint positions from velocities.
Furthermore, I used the opportunity to clean up a bit handling of parameters and arguments in XACRO files to hopefully add flexibility and reduce confusion.

Thanks for this @destogl.  However, the Humble release for Husky is now here: https://github.com/clearpathrobotics/clearpath_common/blob/humble/clearpath_platform_description/urdf/a200/a200.urdf.xacro  Do you want to do a PR against it?


MWPW-149113: UAR Interactive Front Door click event not registering

Send mlField fiCodes with continue button click event

Resolves: MWPW-149113
Test URLs:

Before: https://main--milo--adobecom.hlx.page/?martech=off
After: https://mwpw-149113--milo--jackysun9.hlx.page/drafts/quiz/quiz-entry/

Labeled high priority as this is a blocker to a launch.


Dusk unit is wrong

Describe the bug
A dusk is 1B nanoDusk, but the codebase still reflect the old scenario where microDusk was the smallest unit

This is one of the root causes of dusk-network/rusk#589


Shell session improvements

Currently its unclear what it is used for and how to exit the shell session for repairing the commit.

Done via https://github.com/jboss-container-images/concreate/pull/107


[ZEPPELIN-965] missing lastExecuteTime function

What is this PR for?
Added last note run time.
This was a bug.
The function was configured, but the function to output it was missing.
What type of PR is it?
Bug Fix
Todos

[x] - added print function

What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-965
How should this be tested?
execute note and check in job menu.
Screenshots (if appropriate)

(2 hour a go)
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

Tested. LGTM

LGTM!

Merging this if no more discussion.


uriparser update to 0.9.6 (security fixes)

Library name: uriparser
New version number: 0.9.6
Other information that may be useful (release notes, etc...) see below

Hi!
I found a vulnerable copy of uriparser 0.9.5 in here at ports/uriparser/portfile.cmake. uriparser 0.9.6 with security fixes has been released, the change log has more details. Would be awesome if you could update to 0.9.6.  Thank you! :pray:
Best, Sebastian

Thanks!


[backport] Improving performance of cupy.random.choice

Backport of #8483 by @asi1024

/test mini


[Publication] Fix packaging of apollo-normalized-cache

Using a jar packaging confuses Gradle when artifacts are deployed in mavenLocal. (Somehow it works with OSS snapshots).
Use a pom packaging instead since apollo-normalized-cache does not contain the actual jar anymore. (It is in apollo-normalized-cache-jvm)

LGTM. Not 100% sure but I saw people removing this completely. I wonder what would happen then 🤔

Not 100% sure but I saw people removing this completely. I wonder what would happen then 🤔

Indeed, this can be removed from gradle.properties. The multiplatform plugin will set it properly.


Android

If a group is successfully created, how can a group that has just been created become blocked?

Please use https://groups.google.com/d/forum/tinode to ask questions.


Enable SSL for draft-assets

This addresses https://github.com/alphagov/asset-manager/issues/430.
This will allow us to start responding to requests to draft-assets in staging and production. I've copied the necessary bits of the config from assets_origin.pp and assets-origin.conf.erb.
Note that draft-assets doesn't require SSL to be configured on the virtual host in integration because we're terminating SSL requests at the ELB.

Thanks @floehopper! I'm going to get this merged.


[spotify-player] loads 300 instead of 50 albums, artists, playlists, shows

Description
This PR contains changes to the Your Library command provided by the Spotify Player extension.
Previously the extension would only load at most 50 playlists, albums, artists, tracks, shows, and episodes. That means if you have more than e.g. 50 albums in your library then you can't use "Your Library" to search for it.
This PR adds changes the limits so they're 300 for playlists, albums, artists, shows, and 50 for tracks and episodes. If I tried to load all my tracks the extension runs out of memory. The new limits are based on my personal needs 😉
To accomplish this I added an async iterator that we can use paginate over the responses from Spotify.
If you have a large Spotify library then it takes a while longer to load the initial data. I want to add more user feedback while the data is being loaded but I'd prefer to do that in a follow-up PR ☺
Screencast
No screencast for this one.
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@peduarte I rebased on main to resolve conflicts - would you be able to review the PR? ☺

@peduarte Anything I can do to make the review easier? ☺

So sorry for the delay. Am I right in thinking that this change will make 6 API calls (6 calls of 50 results) instead of 1? The problem is we are already having rate limiting issues with the Spotify API, so I'm quite hesitant on merging this as it'll just mean we call the API more often than we most likely need.
The ideal solution for this would be to implement pagination.
The good news is that we're working on a pagination API right now, so as soon as it's out, we'll add it to the extension.

Am I right in thinking that this change will make 6 API calls (6 calls of 50 results) instead of 1?

It depends on how many albums, playlists, etc. you have. Before it would make 1 request per type (6 in total) which means it would only fetch at most 50 entries for each type.
This PR implements pagination for the Spotify API but then still has hardcoded caps for how many of each type to fetch.

Playlists, albums, artists, shows are capped at 300 so 6 requests for each at most.
Tracks, Episodes are capped at 50 so 1 quest at most

So worst case you'd make 46+21 = 26 requests - not in parallel though.

The good news is that we're working on a pagination API right now, so as soon as it's out, we'll add it to the extension.
Awesome

We can close this PR and revisit once you have support for pagination and see if some of the changes in this PR still makes sense. I suspect you'll need the Spotify API pagination at least ☺

Thanks for the reply.
With this implementation, it means that if I have 500 albums, it will call the API 6 times, even if I the artist I'm after is the first in the list, correct?
I think the main different with our upcoming one, is that it will only make further requests when needed, ie: user has reached the bottom of the list.
I'm also curious about why Tracks, Episodes are capped at 50.

With this implementation, it means that if I have 500 albums, it will call the API 6 times, even if I the artist I'm after is the first in the list, correct?

Yeah - conceptually it's creating a local cache of your Spotify data

I'm also curious about why Tracks, Episodes are capped at 50.

With the extensions current way of caching the results the extension runs out of memory pretty quickly. Given the cap was 50 before I decided to just not change it ☺

In general the way the extension deals with caching of the results (both in this PR and on main) means it runs out of memory if it wanted to cache my entire library. Pagination at the Raycast level + context-specific-search (e.g. favourite albums) would be a nice solution to this ☺

Yeah as part of the pagination work that @sxn is working on, he's also dealing with memory-related issues!
Thanks for putting this together, we may use it as reference when we need to implement the new Pagination API, but for now I think it's best for us to wait for the first-class API.
Thanks again!


Feature/protocol v3

These are V3 protocol changes for C# driver.  Please review, as it would be much easier for me to base my next work off these changes.

How was this work tested? Against which proxy versions?

I unit tested against cloudsim and on-prem.  For cloudsim, i tested against 5.7.3 (which is the latest version i found) which supports V3 protocol and 5.4.23, which only supports V2 protocol.  The latter tested the code that falls back from V3 to V2.  I also debugged through it to make sure that code was executed.  For on-prem, it was 22.1.7 i believe.

Added change log entry.


Simplify New-PSClassMock

In reference to:
function New-PSClassMock {
    [cmdletbinding(DefaultParameterSetName='PSClass')]
    param (
        [Parameter(Position=0,ParameterSetName='PSClass')]
        [PSObject]$Class,
        [Parameter(Position=0,ParameterSetName='PSClassName')]
        [String]$ClassName,
        [Switch]$Strict
    )

Obviously, a string is not a PSObject, so we should not need to have multiple parameters to differentiate.

this is an invalid request, as this is already supported. Based on the object type provided, in position 0, it will choose PSClass or PSClassName parameter set.


504+509+final tweaks

@tjb900 this PR exploits your contribution in #504 and #509 , adds in my suggestion about avoiding the if is_Sub ... pollution, and also ships the tests that you're suggesting in #508
Note that I've simply cherry-picked your commits, so you get the deserved credits :-)
If everybody's happy (including Travis), we can merge this instead of #504 and #509 )
fixes #503 #508

Reopening once #507 will have landed


tmux 3.2: Multi-pane window cancels selection when moving by tmux-easy-motion

In tmux 3.2, if a window has multiple panes, when you begin a selection and then move via tmux-easy-motion, your selection is cancelled, preventing you from selecting a region via tmux-easy-motion.
These screenshots were taken in a tmux 3.2 client running in Alacritty on macOS.  It was launched like this:
$ cat /tmp/tmux.easymotion.conf
set -g @easy-motion-copy-mode-prefix-enabled "1"
set -g @easy-motion-copy-mode-prefix "s"
set -g @easy-motion-prefix-enabled "0"
set -g @easy-motion-dim-style "fg=colour242"
set -g @easy-motion-highlight-style "fg=colour196,bold"
set -g @easy-motion-highlight-2-first-style "fg=#ffb400,bold"
set -g @easy-motion-highlight-2-second-style "fg=#b98300,bold"
run-shell "/tmp/tmux-easy-motion/easy_motion.tmux"
$ tmux -V
tmux 3.2
$ tmux -L test -f /tmp/tmux.easymotion.conf

Starting from a session with a single window split vertically where the left pane has man tmux running, enter copy mode, jump to a character, begin selection, move a little to see that the selection is active, then use tmux-easy-motion, and jump to a different character.  At this point, you will see that the selection has been cancelled.

I tried this on my development machine (Manjaro Linux, kitty terminal and tmux 3.2a), but could not reproduce this behavior yet. I am going to install your environment on a fresh macOS VM. Maybe, there are some differences between platforms or terminal emulators.

I could reproduce the problem on macOS with Alacritty and the default terminal and on Ubuntu 20.04 with the GNOME terminal. So it seems to be indepedent from the operating system and the terminal emulator.

I think it's something to do with the terminal emulator, rather than the OS.

XTerm (330) - fails - it jumps to the end of the scrollback [0/12] in the top right
XTerm (370) - fails - installed from Guix - same as above
Gnome Terminal (3.28.2) - fails - this is the Ubuntu 18.04 LTS one - same as XTerm
Alacritty 0.9.0 - fails - difference is it jumps to the search location, but doesn't keep the highlight
Kitty 0.20.3 - doesn't work - same as XTerm

My thoughts meander along (blown round unbound) the poets verse:

        I wandered lonely as a cloud
        That son high o'er vales and hills,
        When all at once I saw a crowd,
        A host, of golden daffodils;
        Beside the lake, beneath the trees,
        Fluttering and dancing in the breeze.

Enter tmux-copy mode:
Move using the vim keys to some line: start of line 4 'A host
Start a selection (for me this is v): v
Do a tmux-jump search for a character, say d: sd
Fails here if there's more than one pane
Copy the highlighted text: y

@Futurile Thanks for your tests and your further investigation! :slightly_smiling_face:
I tried your instructions on Manjaro Linux, kitty 0.24.1 and tmux 3.2a, but still I cannot reproduce this error on my development machine (but I suspect it also broken for me on my Mac VM).
I really would like to fix this issue, but I have still no idea what is going on here...

Does tmux-easy-motion often fail for you @butwerenotthereyet and @Futurile when multiple panes are involved?

@IngoMeyer441 Yes, it fails very often when there are multiple panes involved.

Gentoo, kitty 0.26.5, tmux 3.3a.
The same issue.


Calls loadMore endlessly

Why would the component call loadMore continuously and endlessly with increasing page numbers once I reach (only once) the end of the list? What am I doing wrong? FYI, I am using redux for this.
Thanks!

The same happens to me but instead of reaching the end, it happens on page load, probably can be due to the fact that the component is not visible yet?

@tommyalvarez in my case, it was due to unnecessary renders of my component. I'm closing this!

@machadogj I am too, having unecessary renders of the component.

I am using redux, so it boils down to comparing props references to see which one changed. A fair amount of console.log as well.

@machadogj  Did you ever get this working with using redux?

@notflip we did. What’s your issue? If it’s the same track down why you infinit scroller re renders more than once.

Yes! It's calling the getMore() function twice or more.. While all was working without Redux, since adding Redux it's doing what you describe.

Try to place a debugger in the render function of the component that holds
the infinit scroller component. See how many times it’s called.
On Sat, 8 Dec 2018 at 13:01 Miguel Stevens<EMAIL_ADDRESS>wrote:

Yes! It's calling the getMore() function twice or more.. While all was
working without Redux, since adding Redux it's doing what you describe.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CassetteRocks/react-infinite-scroller/issues/61#issuecomment-445469412,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACKsxxvGQANigwD402eLQ3ztVUf_kqyiks5u2-J2gaJpZM4My_Iq
.

After the success, so when the initial load is done, the render is called twice after that.

Then it recalls the fetchmore function, whereafter the render is called twice again.

Aha! It has to do with my loading being updated, If I remove my "loading" from the state all is working fine. It seems when loading is done, it re-renders and thus calls the fetchMore function again.

Hmm it should only be called once. Stupid question, are you setting load
more prop of infinit scroller to false after fetching the results and
reaching the end of the pagination? Even having only one page if you don’t
set the loadMore to false it will continuously fetch more.
This is how I used it:
On Sat, 8 Dec 2018 at 13:08 Miguel Stevens<EMAIL_ADDRESS>wrote:

After the success, so when the initial load is done, the render is called
twice after that.
[image: screen shot 2018-12-08 at 23 07 50]
https://user-images.githubusercontent.com/4146384/49687996-1c87b500-fb3e-11e8-8cf2-3a43b82a9dfd.png
Then it recalls the fetchmore function, whereafter the render is called
twice again.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CassetteRocks/react-infinite-scroller/issues/61#issuecomment-445469868,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACKsx68OY2vYVQcAQM0cKx3MoFYVHBoRks5u2-P8gaJpZM4My_Iq
.


Merge 2.63.0

Simple merge, had to fix conflicts in UsageProto.java, datalakeDRProto.java, and usage.proto

you force pushed the branch which shouldn't be done one merge pr,since hash of commits change

you force pushed the branch which shouldn't be done on merge pr,since hash of commits change

Thank you for letting me know Adam, I apologize. I was just trying to fix merge conflicts and get this in this PR. I will try to fix this and then re-open.

no problem,thanks for making the merge pr


Support for compression of HTTP responses

We're using MailHog for testing in an environment where testers and deployments are geographically distributed.
When the inbox has more than 50 messages, then refreshing the inbox can result in a response that can be 10MB or more. With compression, this reduces the response for a full 50 messages to a few hundred KB.
While we could put MailHog behind a real web-server, this would be an extra complexity that detracts from it being a simple drop-in solution.
This issue is primarily for visibility, and the relevant pull requests to support this are:

mailhog/http#1
mailhog/MailHog-UI#9

thanks @danielwhite :+1: merges are done so should work if building from source, or it'll be in the next release!

compression seems to break the event source connection, taking it back out while I investigate

Ouch. Sorry I didn't spot that. I'm happy to track down and fix the problem if nothing obvious has jumped out already.

I haven't had a chance to look properly yet, it may well be an issue with goose rather than MailHog - but yeah I'd appreciate it if you do have time to investigate!

Closing this. There are other issues here that suggest extracting out attachments that I think may be the better solution to the problem for now


Error while processing function

When opening a Haskell file, I get this:
"../.gitignore" [dos] 49L, 697C
Error detected while processing function <SNR>21_WildignoreFromGitignore:
line   14:
E518: Unknown option: Items,.apdisk,dist/*,.stack-work/*
Press ENTER or type command to continue

Does not occur when vimming normal files (but possibly with other git projects).
The gitignore file is an auto-generated one, which works in other environments:
# Windows image file caches
Thumbs.db
ehthumbs.db

# Folder config file
Desktop.ini

# Recycle Bin used on file shares
$RECYCLE.BIN/

# Windows Installer files
*.cab
*.msi
*.msm
*.msp

# Windows shortcuts
*.lnk

# =========================
# Operating System Files
# =========================

# OSX
# =========================

.DS_Store
.AppleDouble
.LSOverride

# Thumbnails
._*

# Files that might appear in the root of a volume
.DocumentRevisions-V100
.fsevents
```d
.Spotlight-V100
.TemporaryItems
.Trashes
.VolumeIcon.icns

# Directories potentially created on remote AFP share
.AppleDB
.AppleDesktop
Temporary Items
.apdisk

dist/
.stack-work/

Thanks for the bug report, I just confirmed it on my own installation.
I discovered that the problem comes from the https://github.com/vim-scripts/gitignore plugin which we include in the vimrc.
Could you help me out and see if there's a better plugin we could use for this, or possibly fork and fix the existing one?


Params interface doesn't show up in docs.

The bug is somewhere in https://github.com/propelml/propel/blob/master/tools/gendoc.ts

Thanks @dangerdak! I enjoyed your blog post too!

Thanks dude :)


start_message.py:23: Перенести классы в отдельные файлы 39

The puzzle 899-628a6dbf from #899 has to be resolved:
https://github.com/blablatdinov/quranbot-aiogram/blob/09501ab93db1439392aad3a717cfe1776e9d97ec/src/srv/start/start_message.py#L23-L23
The puzzle was created by Ilaletdinov Almaz on 09-Jun-24.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

All classes moved #899