Need use cases

I found my way here because of this https://dev.to/laurieontech/at-coming-soon-to-ecmascript-1k91
From there I learned last() is dead...or dying because at() is now at Stage 3 https://github.com/tc39/proposal-array-last
Even if the disclaimer on that proposal doesn't really mean what it says it means (it should be removed if it's not to be taken literally), there is still the unspoken truth that at(-1) is very likely to be deemed sufficient by TC39 and therefore last() is no longer worth consideration.
So, I'm trying to understand the real world examples behind at(). The proposal ironically only gives "last" as a use case. What other use cases does this proposal solve for?

There are a number of use cases for being able to look at things arbitrarily far from the end of an array. For instance, if you wanted to iterate through two arrays in reverse order:
function doSomething(arr1, arr2) {
  assert(arr1.length === arr2.length);
  for (let i = 0; i < arr1.length; i++) {
    doSomethingElse(arr1[i], arr2.at(-1 - i));
  }
}

look at things arbitrarily far from the end of an array

I understand arbitrary lookup from the end is the idea, but iterating in reverse order is not an example of that. Reverse is deliberate and linear not arbitrary (and only a few characters more). at(-1) is also very deliberate.
Maybe a better way to ask the question is, "What are people doing in Python with negative indices that we hope to do in JavaScript with at()?"

Yeah, fair enough, you could also have done it with just array2.reverse() and then iterating the array normally.
Although if you don't care about performance, .at(-1 - ...) can always be replaced with .reverse()[...]

Anyway, going through my own codebase and grepping for .length -, I find one result that would be improved by .at but not .last:
const target = pokemon.side.foe.active[pokemon.side.foe.active.length - 1 - pokemon.position];

This is because in a doubles/triples game of Pokémon, the Pokémon are numbered like this:
foe 2    foe 1
ally 1   ally 2

So mechanics affecting "the pokemon directly across from you" need to index from the back.

Thanks for sharing. Still another example of starting from last rather than nth-from-last, but a good example nonetheless.

I don't understand what you mean? My example uses nth-from-last. If it helps, here's some additional context:
onStart(pokemon) {
	// Imposter does not activate when Skill Swapped or when Neutralizing Gas leaves the field
	if (!this.effectState.switchingIn) return;
	// copies across in multibattle and diagonally in free-for-all
	// fortunately, side.foe already takes care of all that
	const target = pokemon.side.foe.active[pokemon.side.foe.active.length - 1 - pokemon.position];
	if (target) {
		pokemon.transformInto(target, this.dex.abilities.get('imposter'));
	}
	this.effectState.switchingIn = false;
},

Oh, it's nothing. All I mean is, similar to reverse traversal, that use case always starts from the last index (-1) and goes from there. Which is subtly different than a use case where you don't always start from last, e.g. pokemon.side.foe.active.at(randomNegNum).

What makes -1 - pokemon.position different from a random negative number?

Oh! You're saying that you'd prefer an atFromLast(i) function instead of at(-1 - i)?

Well, why aren't you using a random number then? Because you know pokemon.position is fixed from the end of the active list.

You're saying that you'd prefer an atFromLast(i) function instead of at(-1 - i)?

Not at all haha! at() with a negative number is already "from last". In your case it seems like position is always a fixed number from the end of active, so this makes sense.

I think the confusion here is that "random access" in a computer science context usually does not literally mean "access an index determined by RNG" but simply "access something in a specific position without needing to go through the array in order". That's the sense in which RAM is "Random Access Memory".
If you actually wanted to access an element randomly, it doesn't really matter if you're going from the back or the front, anyway.
I thought we were talking about use cases for Array.prototype.at though? What do random number generators have to do with accessing an array from the back?


Move no smoking symbol to the right a bit on QR 4in

URL: https://muni-sign.safestreetrebel.com/#15836?foot=1

Cancelling this. 1-1/2 in corner radius would be closer if moved


PR: Interpret -p project argument relative to the directory of invocation

Description of Changes
When Spyder is invoked with -p project, this resolves project relative to the directory of invocation. IMO this is generally expected behaviour for running CLI tools. Currently it is interpreted relative to Spyder's working directory, which is generally my home directory.
E.g. if I am in /home/akdor1154/src/python, if I type spyder -p folder1 or spyder -p ., I expect these to be interpreted as /home/akdor1154/src/python/folder1 and /home/akdor1154/src/python, respectively. Currently they are interpreted as /home/akdor1154/folder1 (surprising) and /home/akdor1154 (really surprising).
N.B. existing behvaiour of -p, to create a project if it does not exist, is unchanged.
Issue(s) Resolved
Fixes #11363
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: akdor1154

thanks for the review guys :)


i18n(es): update tailwind.mdx

Description (required)

The problem with the closing of the highlighted part has been solved.
Changed the extension from cjs to mjs.
The export default has been corrected.

Could you add the changes from this PR here? https://github.com/withastro/docs/pull/6662
After it's done this one is good to merge, thanks 🙌

How can I do what you tell me to do?


V11 CE Error when creating effects

On launch, the necessary effects fail to create which causes the canvas to crash

I have been unable to repro with latest builds, and believe this is no longer occurring.  Please reopen if that is not correct.


Re-order settings in package.json alphabetically

Having the settings in alphabetical order makes it easier to scan through the list when looking for a setting.

Hey @luabud !
I would like to contribute to this issue.
Just wanted to ask that if you are talking about both package.json and package.nls.json  files

@luabud please assign it to me as part of GHC open source day.


Add Hooks::before_routes to give user control over initial axum::Router construction

This function can be implemented by the user to fully control the construction of the axum router before it is handed back to loco. This is necessary in order to create a fallback handler that is covered by the loco middleware, as any fallback that is added in after_routes gets initialized after all the middleware in to_router. The default implementation of Hooks::before_routes results in the same behavior as before, but the user can override the implementation like so:
impl Hooks for App {
    // ...
    async fn before_routes(ctx: &AppContext) -> Result<AxumRouter<AppContext>> {
        // Anything that we want to add to the router before the middleware is initialized
        let router = AxumRouter::new().fallback(/* some fallback_handler */);
        Ok(router)
    }
    // ...
}

Resolves https://github.com/loco-rs/loco/issues/643

@swlody this is really great!
I always try to think in terms of process with the hooks, it keeps them more agile. So think:
"before lunch" (getting food, getting place to eat)
"having lunch" (eating)
"after lunch" (cleaning up, doing some exercise)
It doesn't always work to "force" things into that kind of shape and form but in this case, I think it might be.
I feel this PR (covering how to customize fallbacks, etc), is actually:
before_routes(ctx: &AppContext) -> Result<AxumRouter>
Where the user will

Customize / build / create their own initial version of Axum router, and finish at that
We (loco framework) take that router, and add the routes on it, while continuing to add the rest of the layers internally

if the user wants to add stuff "after", they can use after_routes, as you've already identified
This keeps the complexity of "wait, after I built a new router, how to I add the routes?, what are the steps I need to follow to get to a fully working router? do I need to also call after_routes myself?" - this is a cognitive overhead that most users will have but "pro" users will probably manage (by viewing the source code or experimenting). We want to make sure most users actually do the right thing always ("the pit of success").
By offering the user just the thing they need ("e.g. use before_routes, create your own router and give it to us, we'll take it from there), we're ensuring a higher chance of success, and also we're making sure the framework (Loco) is always able to change things behind the scenes (order of initialization, adding more stuff into a router, etc.)
So to summarize:

Change router to before_routes, keep same signature, expect the user to only return a custom-initialized router (with fallback or etc.)
On the framework side, use this as a router construction method, and continue from there

Hope this wasn't too long, makes sense?

Thanks for the detailed feedback @jondot. I've renamed to before_routes as you suggested and added a reference to the function in the docs.

thanks @swlody


Great Project - Many Questions

Hi,
my first computer didn't have graphics, and the only games were text adventures where you typed F L R B to move and you got some short text responses, telling what's happening or why you have died, Luckily, the world is evolving and new technologies and ideas are allowing us to work or play in increasingly better better and more efficient ways.
Retroactive behaviors have always existed in history - but seeing many a certain group of software developers being fixated on ancient and inefficient procedures to work an collaborate....I don't get this together.
Doing some ffmpeg development at times and a bit more recently, their e-mail based GIT workflow has always been an annoyance to me for a number of reasons. So it should be no surprise that I like this project. I had a similar idea a while ago, but found GitGitGadget just about this summer. From a quick look, I had seen that it would take more than a few hours to adopt this for ffmpeg, so I had put it aside but kept thinking about it.  What should I say - the level of annoyance had approached another high and so I decided to give it a go :-)
It wasn't too difficult from a large scale view. There are lots of good information on the Wiki page and in the recent conversation about adoption, just that the it's all mixed up a bit and you need to read more than twice
to get all the important bits.
Adapting the code was really easy and took the least time actually. Setting up the git e-mail server took a while, it's not really well documented and information about public-inbox is rare.
The really unfortunate part is that the Azure pipeline definitions cannot be viewed. Even though the bash scripts are posted and explained here, it wasn't easy to infer how all these pipelines are meant to work and need to be set up.
I was able to figure out how it's meant to work in most cases, but a number of things are still a but unclear.
tbc..

Let's start with those thing that I already got completed:

[x] Fresh new server with

Debian
Postfix
.com domain + dns setup
new mail account for receiving from the ML

[x] Installed the latest version of public-inbox
configured and working
[x] Created a new GitHub organization
allowing for flexibility in terms of ownership
[x] Forked ffmpeg
[x] Forked GitGitGadget
[x] Created a new Azure DevOps organization
[x] Registered a Gmail account
[x] Created GitHub and Azure accounts, with access tokens
[x] Registered a new GitHub App
- created a public/private key pair
- installed to the forked ffmpeg repo
[x] Set up and installed a private Azure DevOps build agent

(the checkboxes are somewhat pointless now, but it's just a copy/paste)
tbc..

The most important question I have at this point is about that "Azure Function".
There are so many different components involved already (and it's a whole different thing than DevOps piipelines).
We have the DevOps piipelines, we have GitHub and we have our own build agent.
Why did you choose once another service over the one's that are already part of  the setup?
Couldn't this be just run as an Azure pipeline like the others?
Thanks,
softworkz

The really unfortunate part is that the Azure pipeline definitions cannot be viewed.

It is here: https://github.com/gitgitgadget/gitgitgadget/tree/HEAD/azure-function/. If you search for process.env, you see that it uses the environment variables GITHUB_WEBHOOK_SECRET and GITGITGADGET_TRIGGER_TOKEN, they need to be configured in the "Configuration" blade of the Function App, in the "Application settings" tab. In the same blade, under "Function runtime settings", the "Runtime version" is set to ~2. The Function App is registered as running on Windows, but I think it might not even matter.

What I didn't understood initially was the part "GitHub App backed by an Azure Function".

What that means is that the URL specified when registering the GitHub App points to the Azure Function, and the Azure Function then does some rudimentary processing and validating, and if everything is okay, triggers the corresponding Azure Pipeline (which is a Pipeline that is set up to also be triggered on pull_request events, so that it runs both "automatically" when someone opens a PR and "manually" when the Azure Function processes e.g. a /preview).

A problem is, that there's no option for polling in case of GitHub repos.

In Azure Pipelines, you can specify "Other" and then use a GitHub URL, which polls. That's what I use.

Pipeline: Mirror Git Inbox to Azure Git Repo

There is no code shown for this, but from the log output of the gitgitgadget Azure task, one could see that it does pull/push from the Git inbox to an Azure Git repo.

If you have a stable enough Git Inbox, you don't really need the mirror on Azure Repos. GitGitGadget started out using public-inbox.org, which runs on a relatively weak machine, and eventually switched to lore.kernel.org, which was not originally available and is a lot more stable.

Later I found out that the data in the Azure repo is not used anywhere, so I assume this is just for backup?

I think we still start out new agents by cloning from Azure Repos, and only update from lore.kernel.org/git, but I might misremember.

3 Mirror Mailing List to GitHub PRs

I don't remember whether I documented this anywhere yet (wiki, maybe? I could look, but then I would not have time to send this reply), so here is what the Pipeline looks like here:

The Variables tab defines GIT_CONFIG_PARAMETERS='user.name=GitGitGadget'<EMAIL_ADDRESS>'gitgitgadget.workDir=$(Agent.HomeDirectory)/../git-worktree' 'gitgitgadget.loregitdir=$(Agent.HomeDirectory)/../lore-git' and the two secret variables gitgitgadget-git.privateKey and gitgitgadget.privateKey (since you will only have to deal with one repository, not two, like git/git and gitgitgadget/git, you will only need the latter, I think). The individual steps:
Pull GitGitGadget, npm install & build
test -d .git || git init || exit 1

git rev-parse HEAD >.git/PRE_FETCH_HEAD
git fetch https://github.com/gitgitgadget/gitgitgadget main

# If the lore-specific adjustments are not yet in master, use Dscho's branch
#git grep -e -U99999 FETCH_HEAD lib/mail-archive-helper.ts ||
#git fetch https://github.com/dscho/gitgitgadget fix-lore-parsing

git reset --hard FETCH_HEAD

# If nothing was pulled, and misc-helper.js is up to date, we already built it
test ! -f build/script/misc-helper.js ||
test script/misc-helper.ts -nt build/script/misc-helper.js ||
test "$(git rev-parse HEAD)" != "$(cat .git/PRE_FETCH_HEAD)" ||
exit 0

npm install &&
npm run build ||
exit 1

Force-fetch refs/notes/gitgitgadget
test ! -d $HOME/git-worktree ||
git -C $HOME/git-worktree fetch $(git config gitgitgadget.publishremote) +refs/notes/gitgitgadget:refs/notes/gitgitgadget

Fetch latest lore.kernel.org/git updates
die () {
    echo "$*" >&2
    exit 1
}

# (transition-only) make sure we have an up to date https://public-inbox/git mirror
#export PUBLIC_INBOX_DIR="$HOME/public-inbox-git"
#test -d "$PUBLIC_INBOX_DIR" ||
#git clone --bare https://git-for-windows.visualstudio.com/git.public-inbox/_git/git.public-inbox "$PUBLIC_INBOX_DIR" ||
#die "Could not clone public-inbox/git to $PUBLIC_INBOX_DIR"
#git -C "$PUBLIC_INBOX_DIR" fetch https://public-inbox.org/git master:master ||
#die "Could not update $PUBLIC_INBOX_DIR to remote's master"

# make sure we have an up to date lore.kernel.org/git mirror
export LORE_GIT_DIR="$HOME/lore-git"
test -d "$LORE_GIT_DIR" ||
git clone --bare<EMAIL_ADDRESS>"$LORE_GIT_DIR" ||
die "Could not clone lore-git to $LORE_GIT_DIR"
git -C "$LORE_GIT_DIR" fetch https://lore.kernel.org/git/0 master:master ||
die "Could not update $LORE_GIT_DIR to remote's master"

Obtain GitHub App token
GIT_CONFIG_PARAMETERS="$GIT_CONFIG_PARAMETERS $EXTRA_CONFIG"
node build/script/misc-helper.js set-app-token $(git grep -q "'dscho': 12"  azure-function/index.js && echo "git dscho") &&
git config gitgitgadget.publishRemote \
    https://x-access-token:$(git config<EMAIL_ADDRESS>git config gitgitgadget.loregitdir "$HOME/lore-git"

Here, the step-specific environment variable EXTRA_CONFIG='gitgitgadget.privateKey=$(gitgitgadget.privateKey)' 'gitgitgadget-git.privateKey=$(gitgitgadget-git.privateKey)' is defined, to get make the secrets available to the script
Process new mails
node build/script/misc-helper.js handle-new-mails

Push refs/notes/gitgitgadget
git -C $HOME/git-worktree push $(git config gitgitgadget.publishremote) refs/notes/gitgitgadget

Here, the step has the Control Option "Run this task" set to "Even if a previous task has failed, unless the build was canceled".

The other problem (found after hours) was the second line in the scripts:
EXTRA_CONFIG = 'section.variable=value'

GIT_CONFIG_PARAMETERS="$GIT_CONFIG_PARAMETERS $EXTRA_CONFIG"

When GIT_CONFIG_PARAMETERS is empty before the first assignment, we get this result:
GIT_CONFIG_PARAMETERS =>" 'section.variable=value'"

Right, the assumption here is that the GIT_CONFIG_PARAMETERS variable configures user.name and user.email so that Git notes can be created with git notes add.

Why did you choose once another service over the one's that are already part of the setup?

The problem is that the GitHub App needs a URL, and it sends signed webhook payloads to that URL. No Azure Pipeline can be triggered using that method. Hence the Azure Function that simply parses the payload and turns it into a ("manual") trigger via an Azure Pipeline PAT.
Thank you for writing up your journey. And sorry that there were so many obstacles.
If you have any ideas how this could be documented better/streamlined better (we could potentially turn at least some Azure Pipelines into GitHub workflows using PATs as secret variables to access the repository, or even the GitHub App secrets), I would be delighted to see that contributed back to this here project.

If you have any ideas how this could be documented better/streamlined better (we could potentially turn at least some Azure Pipelines into GitHub workflows using PATs as secret variables to access the repository, or even the GitHub App secrets), I would be delighted to see that contributed back to this here project.

Thanks a lot for replying.
I think that the pieces you have written are quite good. Problems:

These are just spread over multiple places (Design.md, Wiki, Issues) and unordered
They have a high density of information where you can easily overlook important bits
A few gaps exist in some areas (I can fill some of those)

A lot of improvement could be achieved already without writing a single line, only by moving all to a single place, adding a few more headings, paragraph and line breaks around important information.
A step-by-step prerequisite list might be useful as well (similar to the checkbox-list above, it's not the exact order I did, but close.

The really unfortunate part is that the Azure pipeline definitions cannot be viewed.

It is here: HEAD/azure-function/. If you search for process.env, you see that it uses the environment variables [GITHUB_WEBHOOK_SECRET]

No, I meant the job definitions on DevOps. I was often wondering where you might have which variables defined or whether you have working folders defined  for certain bash scripts.
Actually I'm still not clear about the folder structure you are using. (Too) late I've seen the workDir definition pointing to a sibling folder of the agent installation, but I wasn't sure whether that also the Git repo or whether the Git repo is located elsewhere and the work-tree is just a working tree outside the repo folder?
Also, I have no idea to which folder you are cloning gitigitgadget and the mailbox repo.
I have something totally different right now. It works, but is probably sub-optimal. I haven't looked at the details you posted above, so maybe it's already explained, though.
So that's what I meant was the the biggest obstacle, not being able to see the jobs and tasks in all detail.
Not out of laziness wishing for a copy/paste solution, but rather because many questions are left open without seeing it.
You are probably one of a few dozen people on earth who know about custom git notes storage :-)
I could only find out because in a few cases the pipeline log files are showing some commands...

PS: Right now I'm checking out whether the Azure functions could be eliminated in a way that a GitHub action triggers the Azure pipeline directly: https://github.com/Azure/pipelines (the V2 version supports a "variables" parameter, so hopefully the GitHub event payload can be submitted to the pipeline directly. The index.js code from the function can be called inside the pipeline and the frequency of event invocations could be reduced by conditions in the GitHub action yml.
I think this could work... let me see..

I think that the pieces you have written are quite good. Problems:
* These are just spread over multiple places (Design.md, Wiki, Issues) and unordered

* They have a high density of information where you can easily overlook important bits

* A few gaps exist in some areas (I can fill some of those)

A lot of improvement could be achieved already without writing a single line, only by moving all to a single place, adding a few more headings, paragraph and line breaks around important information. A step-by-step prerequisite list might be useful as well (similar to the checkbox-list above, it's not the exact order I did, but close.

Those are good points. TBH I never really thought that GitGitGadget would be used for anything else than git.git (hence the name: "git.git gadget").
I guess a good first step to remedy this would be to move the documentation from the wiki's "GitGitGadget's Azure Function and Azure Pipelines" page to a new docs/ file?

I meant the job definitions on DevOps. I was often wondering where you might have which variables defined or whether you have working folders defined for certain bash scripts.
Actually I'm still not clear about the folder structure you are using. (Too) late I've seen the workDir definition pointing to a sibling folder of the agent installation, but I wasn't sure whether that also the Git repo or whether the Git repo is located elsewhere and the work-tree is just a working tree outside the repo folder? Also, I have no idea to which folder you are cloning gitigitgadget and the mailbox repo. I have something totally different right now. It works, but is probably sub-optimal. I haven't looked at the details you posted above, so maybe it's already explained, though.

The idea is to share a persistent ~/lore-git mirror, as well as a persistent ~/git-worktree mirror (which is a misnomer because it is actually a bare clone), between the Azure Pipelines jobs. This requires a single agent to be in the gitgitgadget pool, of course, to serialize the work in order to prevent concurrent updates to said mirrors.

So that's what I meant was the the biggest obstacle, not being able to see the jobs and tasks in all detail.

I can see that. The most obvious way forward would be to move to YAML-based definitions of the Azure Pipelines, or to move to GitHub workflows altogether.
The reason why I did not do that yet is simple: such a YAML-based definition would have to live in gitgitgadget/git's main branch, which would require the Git maintainer to change their ways (and from vast past experience I want to avoid that).
If we moved to, say, a GitHub workflow that lives in gitgitgadget/gitgitgadget's main branch, it would no longer be present in the Checks tabs of the Pull Requests in gitgitgadget/git.

Right now I'm checking out whether the Azure functions could be eliminated in a way that a GitHub action triggers the Azure pipeline directly: https://github.com/Azure/pipelines

I do not really like that direction much because Azure Pipelines runs come with a large overhead. And you would have runs for every single PR comment, not only the pre-filtered ones that make it past the Azure Function. But maybe that's something you can live with? If so, I would like to learn from your experience, and we might then change gitgitgadget/gitgitgadget to do the same.

I think we have gone past those initial questions, so I hope it's in your sense when I'm closing this.
And also: Thanks for welcoming me!


[Feature] Const constructors?

It would be really handy to be able to build a parser as a static item, and this doesn't seem to be precluded by anything obvious so long as we don't try to do the parsing itself in a static context.
I'm quite happy to have attempt a PR to do this myself. Would this be a welcome feature, or is there some reason it isn't desired?

Definitely welcome! I believe that some of them are already const, but if there are any that aren't but can be made const, I'd be very happy to accept a PR for that!

I've tried this before, and the big roadblocks I run into are:

The fact that parser types are so big makes naming them difficult
Can't use any boxed or recursive parsers, due to allocation
sync feature needs to be active
Not a block, but make sure to store a dyn for<'a> Parser<'a, ...>, not a dyn Parser<'static, ...>

You can avoid the first two with Lazy, but then you don't need const-construction anyways

Right, and I forgot, since last time I did this, that you may also run into 'implementation is not general enough', which I haven't figured out how to work around.

Unfortunately, it turns out I did miss something in the OP, which is that while you usually know the concrete types involved, the combinators are nonetheless defined on the Parser trait, so can't be called in a const context. They also can't be hoisted out of the trait because they're routed through the default impl, you'd end up redefining them for every concrete combinator class.
I had a look through the free functions, and the only ones I found that could easily be const but aren't are skip_then_retry_until and via_parser which I don't expect have much use in a const context. todo could be const if Location::caller were const on stable, which is presumably planned.
The functions in text.rs in principle could be const, but they would have to "manually" build the combinators involved, which seems like a lot of code overhead.

We'll just have to wait on const trait methods then, I guess. Unfortunate.


Weekly render sometimes fails

Weekly render sometimes has following error:
TypeError: Cannot read property 'url' of undefined
    at /usr/src/app/.next/server/static/mrCX9iF_GNHUGgVV_nqc4/pages/weekly.js:1:29053
    at tryCatch (/usr/src/app/node_modules/regenerator-runtime/runtime.js:62:40)
    at Generator.invoke [as _invoke] (/usr/src/app/node_modules/regenerator-runtime/runtime.js:288:22)
    at Generator.prototype.(anonymous function) [as next] (/usr/src/app/node_modules/regenerator-runtime/runtime.js:114:21)
    at i (/usr/src/app/.next/server/static/mrCX9iF_GNHUGgVV_nqc4/pages/weekly.js:1:6664)
    at a (/usr/src/app/.next/server/static/mrCX9iF_GNHUGgVV_nqc4/pages/weekly.js:1:6858)
    at processTicksAndRejections (internal/process/next_tick.js:81:5)

No longer an issue


VRP Payment - ControlParameters - Periodic limits validation

Description

The ASPSP must ensure that the payment instruction adheres to the limitations set by the corresponding VRP consent's ControlParameters.
When a payment would breach a limitation set by one or more ControlParameters, the ASPSP must return an error with code UK.OBIE.Rules.FailsControlParameters and pass in the control parameter field that caused the error in the Field field of the error message.

It means that the bank service simulation must be implemented a logic to store the payments to calculate the limits defined in the consent in the object ControlParameters.

Current Sandbox behaviour

Currently the Sandbox doesn't implement a real bank behaviour logic to manage the different actions done over accounts and payments, only implements the machine status pattern to change some consent status and payments status.

Allow TPPs to test periodic sums for VRPs.
We have implemented the 3.1.8 version of the OB APIs so we can support you when you need that version, and in particular VRP payments. We can deploy this in our Q1 release next year. However, I have some questions for you.
It was stipulated in the contract that simulation is turned off, i.e. that the payments etc are not processed and payment simulation is not done. This provides TPPs with the assurance that data returned will always be the same and makes testing easy for them.
This does raise some challenges with VRP payments though, as we need to come up with a suitable way of allowing TPPs to test the periodic control parameters. For example it is possible to set a maximum limit for payments during a specific period, e.g. £2000 per month. Then VRPs will be allowed until such time as a VRP would mean that the total VRP payments exceed £2000 in a particular month.
Bearing in mind that we don't process the VRP payments and simulate the payments, all of the transaction data in the account data you provide us, will fall outside of the control periods specified by the VRP consent. In order to allow TPPs to test this we have the following options;
a) Not test the periodic control parameters. It may be enough for TPPs to be able to create a consent and make a VRP payment.
b) Total up the value of the VRP payment submissions during the period specified in the VRP Consent Control Parameters and use that as a total and fail VRP payment submissions that would breach the control parameters.
c) Look in the headers of each VRP payment submission request and determine behaviour based on that header value. This woudl need to be documented on your developer portal. So for example we might have a header like x-vrp-payment-submission-response and we could define values that would control what responses a TPP would get from a VRP payment submission.
Of all of these options I least like b) as from a TPPs perspective behaviour of the VRP payment submission endpoint would change based on the number of VRP payments made during the control period. This would make it very hard for them to run any automated tests against the sandbox.
For these reasons, a or c are the best options we think.

We start to implement the solution C.

Documentation for this functionality has been added to the wiki: VRP Payments - Periodic Limit Breach simulator for TPP testing


ext_authz filter: allowed_authorization_headers enhancement

Hi,
allowed_authorization_headers option for the ext_authz filter has been added recently. The problem is that all headers must be specified in this option in order to be added to the original request. I am using external auth service to generate various headers (like opentracing baggage which consists of multiple headers with various names). All of these names however start with the same prefix, like "ot-baggage-*******". What I am trying to do, is to add a functionality similar to the one used in route configuration.
{
  "start": "...",
  "end": "..."
}

So the filter will add every header whose name is beginning or ending by this prefix/suffix.
I am trying to do this on my own, although i would appreciate any help or suggestions.

@gsagula


ALE can lint sometimes when lint_on_enter is off, but lint_on_filetype_changed is on

From #1273 I've seen this kind of issue before. I wouldn't be surprised if it's happening again.
@alextrastero provide some details for this.

Thanks @w0rp

let g:ale_lint_on_enter = 0
let g:ale_linters_explicit = 1
let g:ale_linters = {
\   'javascript': ['eslint'],
\}
let g:ale_sign_error = '✗'
let g:ale_sign_warning = '!'
let g:ale_lint_on_text_changed = 'never'
" --- Up to here ALE still lints on buffer open ---
" This fixed it for me: maybe vim is opening and then changing filetype...
let g:ale_lint_on_filetype_changed = 0

p.s. thanks for this awesome project :)

Which type of file were you editing at the time, how did you open it, and which linters ran?

vim some-js-files.js and I have explicit set so I only run eslint

Cheers. I'll try to repeat the bug myself later.

I think this relates to the problem I commented on here: https://github.com/w0rp/ale/issues/1619

I don't think this happens any more.


Can't Access Accounts in nYNAB

Defective ToolKit Feature Name: Toolkit for YNAB
Expected Behavior
Click on account to left of main screen to access account register.  Had same error a few weeks ago but came out of it - didn't this time.
Actual Behavior
Continually comes up with message box: "Uh-oh! Something has gone wrong likely having to do with internets and tubes. Refresh your browser to get back in business. [Refresh now].
Steps to Reproduce the Behavior

 Comes up fine in budget view / Report view
Switch to home view
Click on any account or tracking account

Export of Toolkit Settings (Bottom Left of Settings Page)
[{"key":"accountTransactionSearch","value":true},{"key":"accountsDisplayDensity","value":"0"},{"key":"accountsEmphasizedOutflows","value":false},{"key":"accountsSelectedTotal","value":true},{"key":"accountsStripedRows","value":false},{"key":"activityTransactionLink","value":true},{"key":"budgetBalanceToZero","value":true},{"key":"budgetProgressBars","value":"0"},{"key":"budgetRowsHeight","value":"2"},{"key":"categoryActivityPopupWidth","value":"0"},{"key":"changeEnterBehavior","value":false},{"key":"checkCreditBalances","value":false},{"key":"collapseExpandBudgetGroups","value":true},{"key":"collapseSideMenu","value":true},{"key":"colourBlindMode","value":false},{"key":"currentMonthIndicator","value":true},{"key":"daysOfBuffering","value":true},{"key":"daysOfBufferingHistoryLookup","value":"0"},{"key":"editButtonPosition","value":"0"},{"key":"enableRetroCalculator","value":true},{"key":"enlargeCategoriesDropdown","value":true},{"key":"exportTransactions","value":false},{"key":"goalIndicator","value":true},{"key":"goalIndicatorWarningColor","value":false},{"key":"googleFontsSelector","value":"0"},{"key":"hideAOM","value":false},{"key":"highlightNegativesNegative","value":false},{"key":"importNotification","value":false},{"key":"incomeFromLastMonth","value":"0"},{"key":"l10n","value":"0"},{"key":"largerClickableIcons","value":false},{"key":"monthlyNotesPopupWidth","value":"0"},{"key":"moveMoneyAutocomplete","value":true},{"key":"moveMoneyDialog","value":false},{"key":"options.dark-mode","value":false},{"key":"pacing","value":"0"},{"key":"printingImprovements","value":true},{"key":"privacyMode","value":"0"},{"key":"reconciledTextColor","value":"0"},{"key":"removePositiveHighlight","value":false},{"key":"removeZeroCategories","value":true},{"key":"reports","value":true},{"key":"resizeInspector","value":true},{"key":"rightClickToEdit","value":true},{"key":"runningBalance","value":true},{"key":"seamlessBudgetHeader","value":false},{"key":"splitKeyboardShortcut","value":true},{"key":"splitTransactionAutoAdjust","value":true},{"key":"squareNegativeMode","value":false},{"key":"swapClearedFlagged","value":false},{"key":"toBeBudgetedWarning","value":false},{"key":"toggleSplits","value":false},{"key":"toggleTransactionFilters","value":"0"},{"key":"warnOnQuickBudget","value":false}]
System Settings
ToolKit Version:
Operating System (Mac/Windows/Etc): Windows 10
Browser (Chrome/Firefox/Safari): Chrome
Browser Version: 51.0.2704.103 m
Other Extensions: Logitech Smooth Scrolling; Google Docs Offline; Google Dictionary (by Google); Fox News

After leaving open while typing this issue, it finally came out of it.  I am still concerned however for future attempts.  Thanks!

@daltonh2002 You left out the version of the toolkit you're using in your report but it sounds like you're still on 0.5.1 because you're describing a bug that happened after a breaking change by YNAB. Could you confirm that this is the case and if it is please report back that this is resolved with an upgrade to 0.5.2?
Thanks!

Thank you Josh.  When I clicked on the Toolkit icon, it stated "Welcome to
Toolkit for YNAB version 0.5.2!" though I'm not sure I upgraded it.  Is
that something that happens automatically?  I don't see a place where to
upgrade unless it only shows when there is one available and I may have
done it then.  Thanks again for the help!
Dalton Hodgins
On Mon, Aug 1, 2016 at 10:44 AM, Josh Madewell<EMAIL_ADDRESS>wrote:

@daltonh2002 https://github.com/daltonh2002 You left out the version of
the toolkit you're using in your report but it sounds like you're still on
0.5.1 because you're describing a bug that happened after a breaking change
by YNAB. Could you confirm that this is the case and if it is please report
back that this is resolved with an upgrade to 0.5.2?
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/452#issuecomment-236601653,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATz-xcEaYT5oPebzbCOJOMDaEO-y7M2_ks5qbgZPgaJpZM4JZpbb
.

Extensions do update automatically on Chrome though they may not happen immediately. Are you still seeing an issue now that you're on 0.5.2?

Not at the moment.  I'm at work trying it with a different computer using
Chrome and it seems to work fine here.  It has 0.5.2  I will let you know
if something changes; thanks again for all the help!
Dalton Hodgins
On Mon, Aug 1, 2016 at 11:02 AM, Josh Madewell<EMAIL_ADDRESS>wrote:

Extensions do update automatically on Chrome though they may not happen
immediately. Are you still seeing an issue now that you're on 0.5.2?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/452#issuecomment-236607060,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATz-xR6odeNxU49HgfLxuQoHCHn8-0XKks5qbgp3gaJpZM4JZpbb
.

I'm going to go ahead and close this issue as I believe it's fully resolved in 0.5.2.


Training data of the segmenter

Hi @bshall, thanks for the great work!
I am wondering what is the training data of the pre-trained segmenter, as it is not described in the paper or this repo.
Thanks!

Hi @unilight, thanks for the feedback! Sorry about the delay getting back to you. The pre-trained segmenter was trained on p225. But I've tested it out on the other speakers and the learned mapping from clusters to sonorants, obstruents, and silences seems to be consistent. Let me know if you've found something different.

@bshall Thank you for the reply! I do find that segmenter works well on other speakers. I am just wondering how you found the mapping from cluster index to sonorants, obstruents, and silences. Do I need to manually find the correspondence by looking at the phoneme labels and the cluster indices? Asking this because I want to apply the same method to some atypical speech (say, accented speech). I found that the pre-trained segmenter works well on normal speech but has some problems with such atypical speech, so I wonder whether it is possible to train my own segmenter.


#243 Fix for search glitch

This is a fix for https://github.com/Dimillian/ACHNBrowserUI/issues/243

I'll need to look into it, the ItemsListView is reused quite a lot and there is some cases where we don't want to allow search. You fiw work but will put search on every screen. I'll try to fix it a different way.


Add support for verbose trace level logging

Describe your changes
The most verbose log level at the moment is LogLevel::Debug, and while this serves its purpose, it is not suitable for trace-level logging, as it would end up with too much log spam, along with the possibility of revealing information that otherwise should not be revealed in a release/production version of an application.
This PR adds LogLevel::Trace, which is specifically for the purpose of verbose logging.
@halx99 If you accept this PR, do you want a color associated with the trace messages? If so, which color should be used for this?
Issue ticket number and link
Checklist before requesting a review
For each PR

[ ] Add Copyright if it missed:
- "Copyright (c) 2019-present Axmol Engine contributors (see AUTHORS.md)."

[x] I have performed a self-review of my code.
Optional:

[ ] I have checked readme and add important infos to this PR.
[ ] I have added/adapted some tests too.

For core/new feature PR

[ ] I have checked readme and add important infos to this PR.
[ ] I have added thorough tests.

about color, I think we can refer to spdlog.

about color, I think we can refer to spdlog.

They seem to use white foreground color for the trace level "\x1b[37m", which seems to be common for trace messages.  I'll set it to that unless there are any objections.

Debug level output is set to cyan, and Trace level output is set to white, both of which seem to be used in other apps (spdlog and Android etc.)


Data Science with Python :  Getting started with Linear Algebra

Welcome to 'DSWP' Team, good to see you here
This issue will helps readers in getting the overall0 guidance that one needs to learn about getting started with Linear Algebra. Tutorial to Getting started with Linear Algebra and how it's applied.
To get assigned to this issue, add your serial numbers mentioned in the spreadsheet of "Data Science with Python", the approach one would follow and choice you prefer (Documentation, Audio, Video). You can go with all three or any number of options you're interested to work on.
If you had referred any resources, add them up in "DS Resources". Similarly if you had used datasets, include them in "DS Datasets".
Domain : Linear Algebra
Mentors Assigned : Aishani Singh / Dhruv Bajaj
Points to Note :
The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Changes should be made inside the Datascience_With_Python/ directory & Datascience_With_Python branch.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'GWOC' contributors of 'DSWP' domain.
All the best. Enjoy your open source journey ahead. 😎

i want to contribute in this issue
DS python batch 20

Kindly provide all the details.
To get assigned to this issue, add your serial numbers mentioned in the spreadsheet of "Data Science with Python", the approach one would follow and choice you prefer (Documentation, Audio, Video). You can go with all three or any number of options you're interested to work on. @Malvikakaushal2001

I would like to contribute to this issue.
Name: Jeffy Johnson
Serial number: 713
Approach: Documentation

@Sera001 Kindly let me know of your approach that you would follow up.

@prathimacode-hub
I would like to contribute to this issue.
Name: Priyanshi Naredi
Serial number: 720
Type: Documentation
Approach: The document will include the importance of Linear Algebra in Data Science and then the explaination of the important topics to be known like:
Matrices and Vectors
Matrix Operations
Matrix Inverse
Orthogonal Matrix
Applications of Linear Algebra within Data Science
along with the theoretical explanation, there also will be the application of NumPy for some topics here.

Issue assigned to @Sera001 for documentation.
@priyanshinaredi, You just missed up with few mins. Many more issues coming up. Or for this issue, you cna choose video / audio.

@prathimacode-hub add me as assignee please


Blur semitransparent backgrounds

JIRA ticket number
N/A - discussed in the design session
Context
Some text over busy background images is tricky to read
Changes proposed in this pull request
Blur the background slightly to prevent 'hard edges' from the image showing through. This is applied via a rotated-block utility function and can be adjusted in one place and overridden where necessary.
Also remove some duplication from the colours file.
Guidance to review
Does it look good?

Before
After

In older browsers it looks exactly as it does now, this just enhances for those that support it.


Document unexpected behavior in SortRepeated and SortRepeatedFields

SortRepeated and SortRepeatedFields do not respect IgnoreFields and IgnoreOneOfs, with the surprising result that ignored fields show up in the sorted fields.  This isn't trivial to fix, but documenting it would help.
For instance:
// SortRepeatedFields sorts the specified repeated fields.
// Sorting a repeated field is useful for treating the list as a multiset
// (i.e., a set where each value can appear multiple times).
// It panics if the field does not exist or is not a repeated field.
//
// The sort ordering is as follows:
//   - Booleans are sorted where false is sorted before true.
//   - Integers are sorted in ascending order.
//   - Floating-point numbers are sorted in ascending order according to
//     the total ordering defined by IEEE-754 (section 5.10).
//   - Strings and bytes are sorted lexicographically in ascending order.
//   - [Enum] values are sorted in ascending order based on its numeric value.
//   - [Message] values are sorted according to some arbitrary ordering
//     which is undefined and may change in future implementations.
//
// The ordering chosen for repeated messages is unlikely to be aesthetically
// preferred by humans. Consider using a custom sort function:
//
//	FilterField(m, "foo_field", SortRepeated(func(x, y *foopb.MyMessage) bool {
//	    ... // user-provided definition for less
//	}))
//
// This option does not ignore fields specified in [IgnoreFields] or
// [IgnoreOneofs].
//
// This must be used in conjunction with [Transform].

Thanks, documenting this sounds good. I agree it's surprising behavior, but it is indeed something hard to fix. The fact that cmp options are Turing complete is both super powerful, but also makes it impossible to statically analyze what all the options may do. In this particular case, SortRepeated doesn't know about what other options exist, and even if it did, it can't know how each option would be evaluate it's behavior.


From private repo

@huypub : Thanks for your contribution! The author(s) have been notified to review your proposed change. @hsuzuki, @cosmosdarwin


pod 'DatadogSDKCrashReporting' is missing as of 1.7.3

#95 does not add pod 'DatadogSDKCrashReporting' as a dependency. See: https://github.com/DataDog/dd-sdk-ios/issues/778
This causes a crash during builds:
Swift Compiler Error (Xcode): No such module 'DatadogCrashReporting'
/opt/flutter/.pub-cache/hosted/pub.dartlang.org/datadog_flutter-1.7.3/ios/Classes/SwiftDatadogFlutterPlugin.swift:5:7

Just when I think all the bugs are resolved. This is fixed in 1.7.3+1 via #100 .
Thanks for filing @dballance . cc @karthik-js @fabricio-sisplan @neelansh-creatorstack

I'm getting an error with 1.7.3+1 – first time install so haven't had earlier versions.

[!] The 'Pods-Runner' target has transitive dependencies that include statically linked binaries: (DatadogSDKCrashReporting)

If tried pod deintegrate, rm Podfile.lock, pod install --repo-update without any improvement.

@tshedor I don't think this should be closed. it's broken on the latest build 1.7.3+1.

@scopendo I was able to successfully run this yesterday. I ensured 1.7.3 was installed and datadog_flutter 0.0.3 was the version in Podfile.lock. Your error, however, indicates that there's something in the building in Xcode. I'll most likely need to do something with s.static_framework or s.vendored_libraries.
I don't have time to reasonably deal with maintenance right now, so I'm rolling back 1.7.3+1 and 1.7.3. 1.7.3+2 is effectively .1.72. cc @Dachmian via #92 .
If anyone can help on Xcode compilation, I'd really appreciate it. Otherwise I'm going to re-close this issue Friday afternoon PST.

@tshedor We are testing a fix in the mentioned forked repo. If it works we can post a PR here.

@damir-fell looks like we were on the same track. I'll be merging this in shortly and publishing a pre release.

@tshedor Awesome, even better.

@damir-fell this is available in 2.0.0-beta.1


TestLabelsDemoApp: Replace isovalent/jobs-app by Google onlineboutique

Migrate e2e labels test from isovalent/jobs-app to Google's microservices demo Online Boutique

Change the ways to install Online Boutique by using OCI registry
Fix the labels checker

Fixes: #1976, #2176

make the label a bit more explicit maybe (add more of them if they are any)

Those are the only ones set by the default helm chart install, so let's keep this it's plenty enough and it simplifies how they are checked!

make the label a bit more explicit maybe (add more of them if they are any)

Those are the only ones set by the default helm chart install, so let's keep this it's plenty enough and it simplifies how they are checked!

As mentioned in https://github.com/cilium/tetragon/pull/2176#issuecomment-2063497524, I replaced labels to be checked by looked into https://github.com/GoogleCloudPlatform/microservices-demo/tree/90b81cca772eb61b8695a638e44b9b2cde70853f/helm-chart/templates and saw only the app label :D
So just let it simple like this, right? @mtardy :D

As mentioned in #2176 (comment), I replaced labels to be checked by looked into https://github.com/GoogleCloudPlatform/microservices-demo/tree/90b81cca772eb61b8695a638e44b9b2cde70853f/helm-chart/templates and saw only the app label :D
So just let it simple like this, right? @mtardy :D

This is perfect like this, thanks a lot!

So we have a failure on e2e tests but I think it's unrelated https://github.com/cilium/tetragon/actions/runs/8752369371/job/24019870334?pr=2345#step:7:1061. Since all the checkers have matched, I don't think it's related to your changes. Let me just investigate a bit before merging this.

By the way, it seems the deployment time and checker time is a ~50% (or a bit more) gain from before, that's great for CI speed.

By the way, it seems the deployment time and checker time is a ~50% (or a bit more) gain from before, that's great for CI speed.

Relate to the CI speed, I have a concern why we need -p 1 -parallel 1 flags here https://github.com/cilium/tetragon/blob/main/Makefile#L257?
As I understand, -p 1 means only 1 build command (for the test package) can run at a time, -parallel 1 means only 1  execution of test functions that call t.Parallel running.
An with my experience, the -parallel 1 seems redundant with -p 1. In case we want to make sure the tests do not run in parallel, we can set the -parallel 1 and let the compiler build the test packages in parallel. That could reduce the waiting time when running testing (https://github.com/cilium/tetragon/actions/runs/8752369371/job/24024402667?pr=2345#step:7:10 to https://github.com/cilium/tetragon/actions/runs/8752369371/job/24024402667?pr=2345#step:7:12)

So we have a failure on e2e tests but I think it's unrelated https://github.com/cilium/tetragon/actions/runs/8752369371/job/24019870334?pr=2345#step:7:1061. Since all the checkers have matched, I don't think it's related to your changes. Let me just investigate a bit before merging this.

So in the end, even if the output is very confusing, it was related to this. Unfortunately the microservices-demo does not ship arm64 images for all the microservices and it seems now it builds okay, they just don't want to publish the image for some reason https://github.com/GoogleCloudPlatform/microservices-demo/issues/622.
It worked fine locally on my computer since I use a rosetta share between my OS and the Linux VM I use and didn't realize the arch issue...

So yeah again I'm sorry, you did a really good job and helped us a lot on something we have been postponing forever and you just bumped into this not being the ideal solution in the end.
At least now we know it, and we can see what actions should be taken:

we can see if Google moves quickly on publishing the arm64 images;
or if we should find an alternative real-life deployment;
or just use something made-up that is simpler.

Thank @mtardy for supporting me :D. While waiting for support from Google microservices demo, let me check that may we reduce the go test time 💪

Hey, @lambdanis suggested I use this demo instead https://github.com/open-telemetry/opentelemetry-demo, apparently, it's a fork of the Google microservice demo and I tested it on arm64, and it works fine! You can find the doc here https://opentelemetry.io/docs/demo/kubernetes-deployment/.
If you still have the motivation to switch the e2e tests to use this one it would be amazing, otherwise, I can update the issue with the new desired deployment and someone can pick this up.

Hey, @lambdanis suggested we use this demo instead https://github.com/open-telemetry/opentelemetry-demo, apparently, it's a fork of the Google microservice demo and I tested it on arm64, and it works fine! You can find the doc here https://opentelemetry.io/docs/demo/kubernetes-deployment/.
If you still have the motivation to switch the e2e tests to use this one it would be amazing, otherwise, I can update the issue with the new desired deployment and someone can pick this up.

Thank you for your suggestion. Let me change the Helm charts, that would be a great start for me 💪

Hi @mtardy , I have update the labelsEventChecker to match the otel-demo.
Since we have split e2e-tests to run separately, I suggest removing -p 1 -parallel 1 so that the go's compiler can compile the test package in parallel (which is limited by -p 1)

LGTM we can follow up with the -p * if we need/want to.

Lovely thanks!


Fake a hosts file for the tests

Signed-off-by: Patrick Uiterwijk<EMAIL_ADDRESS>

No longer required since we switched to .localhost.localdomain hostnames.


Deprecated

Its usless https://wiki.facepunch.com/gmod/steamworks.RequestPlayerInfo can be used for request steam name

Makes sense thanks!


backport: Fix PROFILE argument in combination with CRATES

Do not forward the PROFILE argument from corrosion_import_crate to _generator_add_cargo_targets.
The PROFILE argument is forwarded via a target property set during corrosion_import_crate. The remaining argument forwarding can cause issues when combined with a multi-value-argument, such as CRATES.

Co-authored-by: Jonathan Schwender<EMAIL_ADDRESS>(cherry picked from commit d5bdbfacb4d2c013f7bebabc6c95a118dc1e9fe1)

The failure on nightly is a change in cargo-metadata output on nightly rust, and not related to corrosions stable branch or this change.


COBOL Parsing Error because of Period in 72 and Standard Numbering Present

Development environment used
Version: 1.63.1 (user setup)
Commit: fe719cd3e5825bf14e14182fddeb88ee8daf044f
Date: 2021-12-14T02:13:54.292Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.17763
Problem Description
Detailed steps for reproducing the problem:

Open a COBOL source that has standard numbering in position 73-80.
Create a line of code in the Data Division that ends with it's period in position 72.
This should produce a parsing error that isn't accurate.

Observed behavior
Data Division statement that creates a parsing error

When the Unnumbering action is applied so that numbering is removed then the errors go away.

Procedure Division Code works correctly

Expected behavior
Expected no parsing errors as if no numbers were present.
COBOL Compile Listing of lines above with no errors.

Hi,
I think this issue can be resolved by applying enhancement describe in #182 COBOL - Improve text colorization for syntax highlighting by textmate grammar.

Thank you for the information!
Apologies, but I am not familiar with TextMate.  I will be reading about it as I can to learn it but in your response in #182https://urldefense.com/v3/__https:/github.com/IBM/zopeneditor-about/issues/182__;!!OgnrLJOUc50AAzM!em86hQfzZGXaC9UCHi1AH14gbkhiFIGqc6aM1BWM5RI6XS2VETnHBgXS7NRpiDKvrg$ COBOL - Improve text colorization for syntax highlighting by textmate grammarhttps://urldefense.com/v3/__https:/github.com/IBM/zopeneditor-about/issues/182__;!!OgnrLJOUc50AAzM!em86hQfzZGXaC9UCHi1AH14gbkhiFIGqc6aM1BWM5RI6XS2VETnHBgXS7NRpiDKvrg$ I see your example and what to do but where do I make the changes and what is the TextMate code to divide the line into 3 sections. I tried looking up TextMate in the Command Palette and clicking on the settings but don’t yet understand the result that I am looking at. Am I missing something obvious?
Thank you,
@.***
From: Denis FALLAI @.>
Sent: Friday, December 17, 2021 12:42 AM
To: IBM/zopeneditor-about @.>
Cc: Coblentz, David @.>; Author @.>
Subject: Re: [IBM/zopeneditor-about] COBOL Parsing Error because of Period in 72 and Standard Numbering Present (Issue #202)
Hi,
I think this issue can be resolved by applying enhancement describe in #182https://urldefense.com/v3/__https:/github.com/IBM/zopeneditor-about/issues/182__;!!OgnrLJOUc50AAzM!em86hQfzZGXaC9UCHi1AH14gbkhiFIGqc6aM1BWM5RI6XS2VETnHBgXS7NRpiDKvrg$ COBOL - Improve text colorization for syntax highlighting by textmate grammarhttps://urldefense.com/v3/__https:/github.com/IBM/zopeneditor-about/issues/182__;!!OgnrLJOUc50AAzM!em86hQfzZGXaC9UCHi1AH14gbkhiFIGqc6aM1BWM5RI6XS2VETnHBgXS7NRpiDKvrg$.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/IBM/zopeneditor-about/issues/202*issuecomment-996503689__;Iw!!OgnrLJOUc50AAzM!em86hQfzZGXaC9UCHi1AH14gbkhiFIGqc6aM1BWM5RI6XS2VETnHBgXS7NSi6GRkHQ$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ATC2YG64NRGN4J4MZTLRLPLURLSVFANCNFSM5KB6ZEDA__;!!OgnrLJOUc50AAzM!em86hQfzZGXaC9UCHi1AH14gbkhiFIGqc6aM1BWM5RI6XS2VETnHBgXS7NTFajfptA$.
Triage notifications on the go with GitHub Mobile for iOShttps://urldefense.com/v3/__https:/apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!OgnrLJOUc50AAzM!em86hQfzZGXaC9UCHi1AH14gbkhiFIGqc6aM1BWM5RI6XS2VETnHBgXS7NRaqseiZQ$ or Androidhttps://urldefense.com/v3/__https:/play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign*3Dnotification-email*26utm_medium*3Demail*26utm_source*3Dgithub__;JSUlJSU!!OgnrLJOUc50AAzM!em86hQfzZGXaC9UCHi1AH14gbkhiFIGqc6aM1BWM5RI6XS2VETnHBgXS7NRLUW74zA$.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Hi @davidkcoblentz,
You can't really make any changes because COBOL textmate grammar comes with the Z Open Editor extension.
Optionally you could extend the textmate grammar that comes with the Z Open Editor extension by developing another extension, but it is still complicated and it is not certain that this solves the problem.
In issue #182, I developed a minimal textmate grammar, and overwrite the file that came with the extension. This is something that is still possible for testing, but not for production use.

Regarding the management of the COBOL point, I searched in the reference documentation, but I did not find the information sought.
The COBOL end-of-sentence delimiter is the dot-space sequence, not the dot alone.
However, it seems to me that there is a tolerance when this point appears in column 72: in this case it does not have to be followed by a space.

Fixed in Z Open Editor v2.0.0


Unable to read LinkedHashMap jmx data

Sometimes I see that value in the QueryAttribute::collectMetrics is the instance of the LinkedHashMap instead of CompositeData or Number/String/Date and jmxtrans is unable to parse it.

@ykapustin do you have more details? What's the Objectname? Could it be an MBean that does not respect the MBean API and returns an HashMap instead of CompositeData ?


feat: --about to list the python versions supported by the connector

It would be great if SDK plugins would advertise their supported python versions. This way we can scrape them for:

listing on the hub
analyzing the ecosystem i.e. identifying taps that should be upgraded to support newer python versions or remove support for deprecated versions

I'm not exactly sure what format this should be in but something like whats in the pypoetry.toml would probably work python = "<3.12,>=3.7.1"
cc @WillDaSilva

If you don't need the parsed version range, then this a relatively low effort as we're already using importlib.metadata to extract the version information, and we could use it to extract the Requires-Python key from the package metadata.

This is related to:

https://github.com/meltano/hub/issues/126

We'll need to align the Hub with the SDK on this but I'm very supportive of making this happen!

Getting the Requires-Python string from the package metadata should work well. It'd be nice if we could normalize it (e.g. transforming ~= specifiers into a >= and < pair), but I'm not aware of any simple way of doing that. We won't be able to get a "fully" normalized form no matter what we do since the field can be very complex, and we don't know what all of the allowed values are (e.g. what versions of Python might exist in the future).
@edgarrmondragon @pnadolny13 In light of the above, here are two approaches we should consider:

Instead of (or in addition to) reporting the Requires-Python string as-is, we report a boolean value for each version of Python we care to check for whether the plugin supports it. This would look something like this:from importlib.metadata import metadata

from packaging.specifiers import SpecifierSet
from packaging.version import Version

supported_python_versions = SpecifierSet(metadata("plugin_name")["Requires-Python"])
for v in ("3.7", "3.8", "3.9", "3.10", "3.11", "3.12", "3.13")
    if v in supported_python_versions:
        report_supported_python_version(v)

Alternatively, we don't perform the above checks within the plugin, and instead defer this processing to the Hub or whatever else is consuming this data. Ultimately whatever is processing Requires-Python will likely need to use the packaging library as shown above in order to be accurate.


Documentation from contributor days

At RxJS contributor days we talked about additions we could make to the documentation / github readme to help people understand RxJS. Here are the suggestions we came up with:

[ ] Add tiny use case examples to the github README (maybe an event handler and API call with retry logic)
[ ] Move the /docs folder out to a docs branch so github users can't click on broken links
[ ] Add a link to http://reactivex.io/rxjs/ on the README
[ ] Find and fill in missing documentation for operators
[ ] Add a glossary of RxJS specific terms (Observable, Operator, Scheduler, etc)

I made a pr where I make docs for certain operator (bindCallback) much more in depth, compared it to other similar operators and added more examples with different ways you can use it.
I was planning to go over every operator (as a challenge to learn rx.js as well as possible) and do the same in each doc.
Please let me know if such effort would be in line with what you had in mind.

Thank you for adding this, @jkup!

So, I know we're all busy, but I want to ping you again. @jkup, have you messed with this at all. @Yonet, are you still interested in this? I'm not sure who else was involved in the discussion.

@benlesh Sorry I got distracted! I haven't worked on this at all. It might be cool to break some of these out into separate issues so people can grab them if they want? Also I think some of the items (like adding a glossary) are a bit intimidating since I don't know the lib as well and don't want to misspeak.

companies that use RxJS
how tos
fix the import stuff
codelinks link to lines in github

@benlesh yes I am interested. We have not come to a conclusion to how to display the examples. Should I just follow @mpodlasin's pull request as an example?
@jkup it is a great idea to separate into different issues.

@ladyleet we should make sure the docs team knows about this issue as well.

@benlesh which part? this?
Add tiny use case examples to the github README (maybe an event handler and API call with retry logic)
Move the /docs folder out to a docs branch so github users can't click on broken links
Add a link to http://reactivex.io/rxjs/ on the README
Find and fill in missing documentation for operators
Add a glossary of RxJS specific terms (Observable, Operator, Scheduler, etc)

FINALLY working on a better guide here: #5592


[CNI] In AKS make azure-cni pod run with dedicated ServiceAccount instead of default ServiceAccount

Component (Azure NPM or Azure CNI): Azure CNI
Describe in detail the feature/behavior/change you'd like to see:  azure-cni pods run with dedicated ServiceAccount
Orchestrator(e.g. Kubernetes, Docker):  Kubernetes
Operating System (Linux/Windows):  Linux
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
The azure-cni pods, along with the azure-ip-masq pods, are deployed automatically by Azure when we use the "azure" network policy when creating an AKS cluster. Currently these pods are deployed with the "default" ServiceAccount instead of a dedicated one like it's the case for azure-npm for example, and there seems to be no parameter to set a custom ServiceAccount.
Is there a justification for using the default SA for azure-cni and azure-ip-masq? If not can you natively deploy it with a dedicated SA please? Meanwhile, how can we set a custom one since these pods are deployed by Azure without available customisation parameters ?
The reason why I am asking this is because using the "default" SA is against kubernetes security best practices.
Thank you,

@khbafl azure-cni doesn't run in any pod. It runs as a process in vm namespace. Regarding, azure-ip-masq, AKS manages it, can you please open this in aks github https://github.com/Azure/aks


Apply lowercase, and delete spaces #434

Apply lowercase, and delete spaces
closes #434
What does this PR do?

Apply lowercase, and delete spaces in this secctions

Login
Credential recovery
Donations dashboard

How should this be tested?

Run make run
Go to localhost:3000
Go to login, credential recovery and donations dashboard

@AngeloCG97 take a look at this conflict


Added fix and tests to issue 267

I added a check if the name of the file which should be generated is empty. If so, we do not generate the file and log this behaviour.

Sorry for the delay @iljabauer. This is great. Merging...


New version: OK1DIX.VUSC4WIN version 7.07

Created by 🥟 Dumplings.
Microsoft Reviewers: Open in CodeFlow

@stephengillie Could you merge this PR?


develop changes to master for next release

deprecated usage removed
updates for 5.6

@amcamd can you review as Daine reviewed the original (everything expected has passed)


Added macOS testing to GitHub Actions

I have modified the GitHub Actions script to now also run a parallel job to build the model in macOS. Once we eventually work out how to implement the fix to Google Test stated in SCRC-120 this will ensure compatibility with both Mac and Linux.

Issue now fixed adding tag of latest release to CMakeLists.txt:
GIT_TAG release-1.10.0


python worker: fix broken link

Update the link pointing to the python polyfill

Thank you very much for your contribution @flavio!


SPIKE: Azure Cost Details API Migration

Related issue with context: #1175
The purpose of this spike is to research necessary implementation details needed for implementing support for the Azure Cost Details API. This API will be replacing the Usage Details API.
it should cover the following:

Verifying process of enabling Cost Details API access (if any)

Azure subscription types supported (For documentation)
Permissions needed (for documentation)

Verify structure of Cost Details API response contains data needed for CCF estimates
Implementation steps for querying Cost Details API for a given date range

Any pagination logic needed (i.e. does it return an  async iterable response)
Libraries/packages needed

Potential migration steps

What parts of the Azure package can be converted vs what needs to be rewritten

Scalability for large usage

Maximum boundary before needing to recommend Exports method

After looking into this, I found the following:

The Cost Details API is the official replacement for the previous Consumption Management’s “Usage Details List” API – the main endpoint that we used to query usage data for a subscription.
Using this API will require installing the “@azure/arm-csotmanagement” library to replace the “@azure/arm-consumption” library.
It is recommended to chunk calls into small date ranges for more manageable files. We will need to decide what an appropriate maximum should be (and provide a config to customize this maximum)

Important Limitations:

Maximum time range of one month per report is supported
Historical data is only supported for up to 13 months prior

I.e. seeding 13 months of historical data is recommended to be done using 13 calls for one month datasets

The Cost Details api serves as a job creator via a polling endpoint that you can interact with via the cost management API. Using the sdk-for-js, you can use the costManagementClient.generateCostDetailsReport.beginCreateOperation to initiate a report for a given start and end date. You can have this kick off the task in the background and check back for results later using costManagementClient.generateCostDetailsReport.beginGetOperationrResults to fetch the status/results or by simply waiting for a response by calling beginCreateOperationAndWait instead.
The reports can be scoped at the billing level using a direct billing account ID (more performant, less requests) or at the subscription level as we do now (less performant, more requests/reports). The subscription level would require gathering a list of subscriptions as we currently do and then creating a report for each scoped subscription.
The report is confirmed to have all of the same properties that CCF needs for calculating estimates and parsing usage data. The following steps can be taken after a report is generated:

The Response will include a blobs property with an array of links (typically one unless response needs to be split) to download the generated csv file with the cost & usage data
This response can be fetched (using node-fetch or axios) to get the csv file’s content using response.text(). This content can then be parsed to JSON using csvtojson to convert it synchronously or streams for reading content line-by-line
The JSON response can be used to create new “ConsumptionRow” objects (probably renamed to CostDetailsRow)

Some future improvements after first implementation (out of scope for now):

Storing historical rows either within the user’s own storage account or within the cache (i.e. MongoDB)

Important to note that reports are only available for 24 hours. Azure recommends storing them instead of repeating requests for the same start/end date

Note on permissions and scale:

Cost Details and the Cost Management API equires Azure Enterprise Customer account
Recommended for small cost datasets (2GB or 2million rows maximum)
Azure recommends Cost Exports for larger scopes
Not recommended for ongoing data ingestion
Azure recommends Cost Exports for recurring datasets
Rate limits have the same retry-after field to implement retry logic when they’re encountered.
API only supports Enterprise or Customer Agreements

Pay-As-You-Go is not supported – recommended to use Exports
Cost Management Reader (Read Only) access is required

RBAC - “Cost Analysis / Forecast / Query / Cost Details API”


Update README.md

Updating README.md for Aug2021  release

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 41.359%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
26439

Relevant Lines:
57961

💛  - Coveralls


Update HasAjax.php

Changed url()->full() to url()->current() in minifiedAjax() function
fixes #193

Okay. Totally my bad. Didn't see there was already a commit #186 waiting to be merged on this same issue.
Do the needful to close this. Really sorry to have missed that.

Duplicate of #186, closing thanks!


Investigate Dependent Resource Ready Status Check Issue

see details in discussion: https://github.com/java-operator-sdk/java-operator-sdk/discussions/1680#discussioncomment-4581631

Check the discussion for further updates.

Will close, since it does not seems to be an issue with the SDK.


[Bug Report] Please redact sensitive information from the logs

Have you read the Important information text above

[X] Yes i did

Current behavior
These fields shouldn't be logged: https://github.com/jammsen/docker-palworld-dedicated-server/blob/bb8e0a1fcda6737e69b80513d6270499974461fa/includes/config.sh#L268-L275
Desired behavior
They should instead say [REDACTED] or not be included at all.
Links to screenshots
No response
To Reproduce
n/a
Software setup
n/a
Hardware setup
n/a
Additional context
Someone posted their creds here: https://github.com/jammsen/docker-palworld-dedicated-server/issues/193

I think that as more users use this docker image it will be beneficial to redact these fields. I think palworld will bring a lot of newer people to docker who could easily give their details away. I support redacting the info.


MAPREDUCE-7494. File stream leak when LineRecordReader is interrupted

Description of PR
In LineRecordReader, we may open a filestream:
fileIn = FutureIO.awaitFuture(builder.build());

However, we may be interrupted or otherwise throw an error before in is initialized, for example here:
fileIn.seek(start);

If this happens, the caller has no way to close this file stream causing it to leak.
How was this patch tested?
Existing tests.
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
12m  0s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.4 Compile Tests _

+1 :green_heart:
mvninstall
44m 37s

branch-3.4 passed

+1 :green_heart:
compile
0m 44s

branch-3.4 passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
compile
0m 40s

branch-3.4 passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
checkstyle
0m 42s

branch-3.4 passed

+1 :green_heart:
mvnsite
0m 47s

branch-3.4 passed

+1 :green_heart:
javadoc
0m 35s

branch-3.4 passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 30s

branch-3.4 passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m 27s

branch-3.4 passed

+1 :green_heart:
shadedclient
34m  8s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 32s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
compile
0m 31s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
javac
0m 31s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 30s

hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core: The patch generated 0 new + 10 unchanged - 1 fixed = 10 total (was 11)

+1 :green_heart:
mvnsite
0m 36s

the patch passed

+1 :green_heart:
javadoc
0m 20s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 20s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
1m 24s

the patch passed

+1 :green_heart:
shadedclient
38m  1s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
23m 49s
/patch-unit-hadoop-mapreduce-project_hadoop-mapreduce-client_hadoop-mapreduce-client-core.txt
hadoop-mapreduce-client-core in the patch passed.

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

164m 16s

Reason
Tests

Failed junit tests
hadoop.mapreduce.split.TestJobSplitWriterWithEC

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7119/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7119

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux b4cfc560ba5e 5.15.0-117-generic #127-Ubuntu SMP Fri Jul 5 20:13:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.4 / 8e0646e88e33223a0142a79a4bdc528d301e8f14

Default Java
Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7119/1/testReport/

Max. process+thread count
1047 (vs. ulimit of 5500)

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7119/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
6m 49s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.4 Compile Tests _

+1 :green_heart:
mvninstall
31m 57s

branch-3.4 passed

+1 :green_heart:
compile
0m 27s

branch-3.4 passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
compile
0m 24s

branch-3.4 passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
checkstyle
0m 27s

branch-3.4 passed

+1 :green_heart:
mvnsite
0m 32s

branch-3.4 passed

+1 :green_heart:
javadoc
0m 22s

branch-3.4 passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 20s

branch-3.4 passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
0m 57s

branch-3.4 passed

+1 :green_heart:
shadedclient
20m 12s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 18s

the patch passed

+1 :green_heart:
compile
0m 21s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javac
0m 21s

the patch passed

+1 :green_heart:
compile
0m 17s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
javac
0m 17s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 17s

hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core: The patch generated 0 new + 10 unchanged - 1 fixed = 10 total (was 11)

+1 :green_heart:
mvnsite
0m 22s

the patch passed

+1 :green_heart:
javadoc
0m 15s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 14s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
0m 52s

the patch passed

+1 :green_heart:
shadedclient
20m  8s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
6m 21s

hadoop-mapreduce-client-core in the patch passed.

+1 :green_heart:
asflicense
0m 26s

The patch does not generate ASF License warnings.

93m  2s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7119/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7119

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 3e30e8a9786f 5.15.0-116-generic #126-Ubuntu SMP Mon Jul 1 10:14:24 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.4 / 516c73c1de6409c535219318ebebdc51522b9440

Default Java
Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7119/2/testReport/

Max. process+thread count
1617 (vs. ulimit of 5500)

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7119/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 20s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.4 Compile Tests _

+1 :green_heart:
mvninstall
31m 54s

branch-3.4 passed

+1 :green_heart:
compile
0m 26s

branch-3.4 passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
compile
0m 23s

branch-3.4 passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
checkstyle
0m 23s

branch-3.4 passed

+1 :green_heart:
mvnsite
0m 32s

branch-3.4 passed

+1 :green_heart:
javadoc
0m 24s

branch-3.4 passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 21s

branch-3.4 passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
0m 57s

branch-3.4 passed

+1 :green_heart:
shadedclient
20m 30s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 20s

the patch passed

+1 :green_heart:
compile
0m 20s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javac
0m 20s

the patch passed

+1 :green_heart:
compile
0m 16s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
javac
0m 16s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 16s

hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core: The patch generated 0 new + 10 unchanged - 1 fixed = 10 total (was 11)

+1 :green_heart:
mvnsite
0m 20s

the patch passed

+1 :green_heart:
javadoc
0m 13s

the patch passed with JDK Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04

+1 :green_heart:
javadoc
0m 14s

the patch passed with JDK Private Build-1.8.0_422-8u422-b05-1~20.04-b05

+1 :green_heart:
spotbugs
0m 51s

the patch passed

+1 :green_heart:
shadedclient
20m 18s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
6m 18s

hadoop-mapreduce-client-core in the patch passed.

+1 :green_heart:
asflicense
0m 25s

The patch does not generate ASF License warnings.

86m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7119/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/7119

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 6083137a0dde 5.15.0-116-generic #126-Ubuntu SMP Mon Jul 1 10:14:24 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.4 / ee28a825c8e0a688520533289315bc6d00ab2540

Default Java
Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.24+8-post-Ubuntu-1ubuntu320.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_422-8u422-b05-1~20.04-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7119/3/testReport/

Max. process+thread count
1600 (vs. ulimit of 5500)

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-7119/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


catchall does not generate additionalProperties

When using catchall on a ZodObject, I would expect the resulting OpenAPI schema to contain additionalProperties based on what the catchall specifies.
For example, with z.object({}).catchall(z.union([ z.boolean(), z.number(), z.string() ])) I would expect:
additionalProperties:
  anyOf:
    - type: boolean
    - type: number
    - type: string

https://runkit.com/mattipv4/649f42bb14551b0008a9ca8f

@MattIPv4  thank you for bringing this up. I'll take a look now on how we can make that but it should be possible

Thank you once again!


deepspeed_light.py bug: 'global_step' should be 'global_steps' in _load_checkpoint()

In the following line, it seems to me that 'global_step' should be 'global_steps'. If so, can you fix it?
https://github.com/microsoft/DeepSpeed/blob/master/deepspeed/pt/deepspeed_light.py#L983
deepspeed_states = [
'module',
'optimizer',
'csr_tensor_module_names',
'skipped_steps',
'global_step'
]

Thanks for the bug report! I just submitted a PR.

@ShadenSmith can we close this issue?

Ah sorry, not yet. There's a working PR that's missing unit tests. I'll get back to it ASAP.


Create papermilled notebook of example BCDP execution.

Inputs to the notebook need to be moved to their own cell near the top of the notebook.  That cell needs to be tagged with parameters.  Papermill will substitute values for these parameters at run-time, so in the notebook the input variables should be assigned default values with the expectation that the values will change with each run.

An example Papermilled notebook is https://github.com/pymonger/downsample-landsat/blob/main/downsample_landsat.ipynb.

Example notebook has been placed in https://github.com/unity-sds/unity-analytics-bcdp/blob/main/cordex_example_papermill.ipynb, so I will now close.


Links Converted to Emoji

I'm having an issue with the following:
[https://api.sailthru.com](https://api.sailthru.com)
This gets converted to:
https:😕/api.sailthru.com

Can not reproduce.


darwin: use runtime check for file cloning

Using #ifdef guards is not reliable because libuv may have been compiled
on a newer system than what it runs on, or vice versa.
Fixes: https://github.com/libuv/libuv/issues/2088
Fixes: https://github.com/nodejs/node/issues/24521
CI: https://ci.nodejs.org/job/libuv-test-commit/1115/
CI: https://ci.nodejs.org/job/libuv-test-commit/1116/

Thanks for the reviews, Santiago and Colin. Landed in 77c30f24f.


[WIP][BEAM-8106] Release Java 11 container image

Rename existing Java8 docker container and add separate gradle task for Java 11 container
Follow-up PR will actually add Java 11 container to release and a validateRunner test suite.

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).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] 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.

GitHub Actions Tests Status (on master branch)

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

Run Java Dataflow V2 ValidatesRunner

R: @TheNeuralBit
R: @kennknowles
From what I can tell, the only suite that actually tests the containers is the very large long running beam_PostCommit_Java_VR_Dataflow_V2.

Run Java Dataflow V2 ValidatesRunner

Run Java_Examples_Dataflow PreCommit

Run Java PreCommit

Run Java Dataflow V2 ValidatesRunner

Run Java Dataflow V2 ValidatesRunner


feat(fastify)!: Support Fastify v5

Description
This PR will trigger a new major release for @clerk/fastify. The reason is that Fastify v5 isn't backwards compatible with our current plugin as we allow Node.js 18 and they now require Node 20. So we need to bump our engines.
Therefore the new major version of @clerk/fastify will only support Fastify v5, users of older versions need to stick with the current major version.
Fixes https://github.com/clerk/javascript/issues/4229
Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

@BRKalow Good catch! That's not needed at the root since I've put it into the plugin. Weird that it was there in the first place

Hello! 👋
@LekoArts i installed latest version using fastify v5
and i get the following error
FastifyError [Error]: fastify-plugin: @clerk/fastify - expected '4.x' fastify version, '5.0.0' is installed
    at Object.checkVersion (/Users/sebastian/Desktop/TEMP/secure/fast/node_modules/fastify/lib/pluginUtils.js:125:11)
    at Object.registerPlugin (/Users/sebastian/Desktop/TEMP/secure/fast/node_modules/fastify/lib/pluginUtils.js:148:16)
    at Boot.override (/Users/sebastian/Desktop/TEMP/secure/fast/node_modules/fastify/lib/pluginOverride.js:28:57)
    at Boot._loadPlugin (/Users/sebastian/Desktop/TEMP/secure/fast/node_modules/avvio/boot.js:425:25)
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'FST_ERR_PLUGIN_VERSION_MISMATCH',
  statusCode: 500
}

Steps to reproduce the issue
run
npm install @clerk/fastify
version installed
"version": "1.0.51"
Maybe the CI did not picked up the latest changes and build the new package with the old code 🤔
Please let me know if i can help or submit a PR i would appreciate a little bit of guidance for it
Thanks.

@jvelezpo we did not publish a new version yet. Stay tuned tomorrow.
For now, you can try the canary version
npm install<EMAIL_ADDRESS>

@jvelezpo Once https://github.com/clerk/javascript/pull/4307 is merged it'll be released 👍

Amazing
Thanks

@jvelezpo That PR has been released, you can upgrade now with npm install @clerk/fastify@latest.


Forbidden right side of house

Forbidden right side of house created by<EMAIL_ADDRESS>on 2018-02-11 22:10:37

<EMAIL_ADDRESS>replied, Charl says that it is forbidden (MEKULL) to walk alongside the right side of a house. She thought maybe the word for this is ODESONGEL but the current definition doesnâ€™t support this.  Then she thought maybe it was UCHUL A ORENGODEL but the current definition also doesnâ€™t support that.
Anyone?  According to Ulang, seems like we need to at least expand the definition of UCHUL A ORENGODEL to include something about respected part of the house.  Right now it just says, â€œpart of house where orengodel beam is first laidâ€

<EMAIL_ADDRESS>replied, Yes, if it's not your house, you can't just walk up along side the Uchul a Orrengodel. Double R.  To me, it would be the equivalent of being in a house not your own and walking uninvited right into the master bedroom. Yes, supposed to say Alii before the odesongel and approach the house perpendicularly to the broad side.
ï£¿souang

I left it single R since that's how it already was. But added this definition.


Mariadb: exception when showing app groups

Caused by brackets around the first part of a union all statement.  Docs indicate may be remedied  from version 10.4.0:
https://mariadb.com/kb/en/library/union/#parentheses
Will upgrade and test.
@rovats - looping you in as potentially relevant to your installation

If tests are successful ensure the new minimum version info is captured in documented Waltz requirements.

Bumping to 1.19 as the attempted fix in 1.18 did not work for SQLServer

Having another go....

The following approach (using a new table) seems to work:
        SelectWhereStep<Record1<Long>> appIds = DSL
                .selectFrom(directApps
                        .union(applicationIdsFromAssociatedOrgUnits)
                        .asTable());


Added osx support to travis ci

Out of curiosity, is there any specific reason you added these in? The only time I usually have OS-specific issues is on Windows boxes, with invalid paths.

Got it. Should close this then.

Note: it's not that I planned to close it, I just didn't know if there was a specific reason, or just general coverage.

It was just to be safe.

OK, in that case, I don't really want to make the tests take longer unnecessarily.  Since run-sequence doesn't really do anything outside the Node universe, any OS-specific issues would be a Node problem, and not with this library.
Thanks, though!


Lil spelling error

Hi,
I am guessing, is this screen the comes when trying to install from the .deb package file? If so, I tried doing that and didn't fount this. I also checked the files, all are looking good. Can you share your OS details, I will try to regenerate it on VM in that case.

Yes,
OS: Kubuntu 20.10 x86_64
Kernel: 5.8.0-44-generic
Resolution: 3440x1440
DE: Plasma 5.19.5
WM: KWin
WM Theme: Breeze
Theme: Breeze Dark [Plasma], Breeze [GTK2/3]
Icons: breeze-dark [Plasma], breeze-dark [GTK2/3]
CPU: Intel i7-6700K (8) @ 4.200GHz
GPU: NVIDIA GeForce GTX 1070
Memory: 25555MiB / 32063MiB

This is an issue with Qapt app, confirmed by using Gdebi. Sadly I don't know where can I report them this.


Validate timeout and timeunit values

Ensure that users can't accidently set a 0 value
which in CSOT represents infinite timeouts.
JAVA-5351

Doh! My search missed all the withTimeout methods - thanks.


What happens if a directory already exists when copying a directory?

Question
If a GitHub action copies a build directory into a bucket using this action; what happens if a directory with the same name already exists in the target bucket?
Does it get replaced, merged, or does it simply fail?

@kruncher The action deals with files in directory individually. If the target bucket has foo/bar.txt and you try to upload to foo/bar.txt, it will be replaced. If you try to upload foo/baz.txt, the bucket will now contain foo/bar.txt and foo/baz.txt. Hope that answers the question.


Access Violation during Grow()

Hey thanks for fixing the last issue. I ran into another problem. Sometimes your code crashes for me during Matching::Grow calls.
I attached a small python fuzzer that tries to match random graphs with 50 nodes. After a few seconds it crashes for me. Again compiled with gcc version 7.3.0 (x86_64-posix-seh-rev0, Built by MinGW-W64 project).
Minimum-Cost-Perfect-Matching.zip

Thank you. I'll look into it.

Fixed. Small bug on the function for augmenting blossoms.
The original code I wrote for my thesis is very reliable, but also ugly. So, before submitting it here I tried reorganizing it. It seems I inserted a few bugs in the process.
Let me know if you have any other issue.


split up mono file, wrapper for port

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#12  👈
#11
#10
#9
#8
#7
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Cohors1316 and the rest of your teammates on  Graphite