Add support for running on Cori

Codecov Report

Merging #32 (ae29abd) into master (3d5d691) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #32   +/-   ##
=======================================
  Coverage   93.72%   93.72%
=======================================
  Files           2        2
  Lines         239      239
=======================================
  Hits          224      224
  Misses         15       15

Continue to review full report at Codecov.

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


Change Documentation covergroups to cover points

In the current DV documentation, there is a list of covergroups.
unfortunately, this method is not practical in capturing the coverpoints.
as an example, in AES I have a cover point (currently documented as a covergroup)

I think this is a crucial cover point in terms of security - but I don't want to do a specific covergroup for this alone.
I already cover the 3 different registers in other covergroups, so I could easily add a coverpoint to each of those covergroups
which means this "covergroup" is now split into 3 coverpoints in three different groups.
I suggest we update the list to match the format for test points
covergroups: [
 {
      name: My_cover_point_a
      desc: '''
            Make sure that we cover this point '''
      covergroup: ["My_cover_group"]
    }
 {
      name: My_cover_point_B
      desc: '''
            Make sure that we cover this point also'''
      covergroup: ["My_cover_group",]
    }
{
      name: My_cover_point_C
      desc: '''
            Make sure that we cover this point also'''
      covergroup: ["my_cover_group","My_Other_cg"]
    }
]

I have not received any response to this issue - so I am adding more people to it.
thinking we can bring this up on next dv meeting @weicaiyang

This seems reasonable to me: maybe we'll need to come up with a format that allows the existing format too (to avoid having to migrate everything). How about the new format living in a dict called coverpoints (and everything gets merged when generating the documentation)?

I initially envisioned that it would enough to capture this at the covergroup granularity, since it not only captures individual coverpoints, but also crosses between them, which are at times, a lot more interesting. What is the limitation of doing the same here (i.e. documenting the covergroup which dut_busy_cg(p) coverpoint is a part of instead, and expressing this important coverpoint in the description)?

I initially envisioned that it would enough to capture this at the covergroup granularity, since it not only captures individual coverpoints, but also crosses between them, which are at times, a lot more interesting. What is the limitation of doing the same here (i.e. documenting the covergroup which dut_busy_cg(p) coverpoint is a part of instead, and expressing this important coverpoint in the description)?

@sriyerg I am not sure what you are saying?
My concern is there is not a 1 to 1 mapping between what we put in the documentation and what is actually implemented.
if you put a "dut_busy_cg" cover group in your coverplan and that does not exist in the implementation, this will look like something was not covered.
if you want to capture the crosses in the documentation I don't see any problem adding them as separate coverpoints that would match well with what is implemented

This whole area is under coverage tag.
Can we do something like this, then we don't need to update the tooling?
To specify a coverpoint, we'd better provide the covergroup name as well, as different covergroup may have a same name for coverpoint.
covergroups: [
 {
      name: My_cover_point_a
      desc: '''
            Make sure that we cover this point '''
      covergroup: ["My_cover_group.point_a"]
    }
  {
      name: My_cover_point_B
      desc: '''
            Make sure that we cover this point also'''
      covergroup: ["My_cover_group.point_B"]
    }
}

@rasmus-madsen any updates on this issue?


Please add groupBy

Do you want to request a feature or report a bug?
feature
What is the expected behavior?
Please add groupBy (like GROUP BY in SQL) in queries.
It may probably can be instead done with some composite structure of the query involving distinct (https://github.com/graphprotocol/graph-node/issues/1768).
See also this related theoretical issue: https://softwareengineering.stackexchange.com/q/412510/45576

See also https://dba.stackexchange.com/q/271601/5061 on the implementation (also in issue #1807).


Interactive window doesn't respect editor.cursorBlinking setting

Applies To

[ ] Notebooks (.ipynb files)
[X] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
Disable cursor blinking:
"editor.cursorBlinking": "solid"

This setting is respected almost everywhere including Jupyter notebooks but not in the input box inside the interactive window. Cursor is still blinking there.
Not sure if this is VSCode or extension bug.
Related:
https://github.com/microsoft/vscode/issues/131941
https://github.com/microsoft/vscode/pull/168217
https://github.com/microsoft/vscode/issues/180429
VS Code Version
Version: 1.78.2 (user setup)
Commit: b3e4e68a0bc097f0ae7907b217c1119af9e03435
Date: 2023-05-10T14:39:26.248Z
Electron: 22.5.2
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045
Sandboxed: No
Jupyter Extension Version
v2023.4.1011241018
Jupyter logs
No response
Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

seems to be fixed now


[tools] AndroidMavenArtifacts is a no-op if the Android SDK is unavailable, but it is unclear if it should be

Discovered while implementing #127354
https://github.com/flutter/flutter/blob/e8f5a51f79fc5dd2f8de38b4d9f504d09dca8197/packages/flutter_tools/lib/src/flutter_cache.dart#L411-L413
It is unclear if this null guard should be here.

Deprioritizing


Enable control over event propagation and default actions

There are lots of scenarios where this is needed. See descriptions in #715.
Since we don't want to rely on synchronous APIs, the solution will probably be a variation on event registration syntax, e.g.,
<button onclick=@MyHandler onclick-stop-propagation="true" />

We still need to design what terminology to use (e.g., "propagation" vs "bubbling") and what features to include (e.g., whether there is also control over "preventDefault").

OK, I've been reading through everything that's ever been written about this, and am formulating it into a proposed design.
Scenarios

Control over event bubbling

Example: Multiple nested
, each with onclick - maybe you want clicks on inner ones to also trigger events on outer ones, or maybe you don't. Same with onmouseover or anything else.
Example: Modal dialog, where if you click outside the dialog (which is a parent element) it should dismiss it, but clicks inside the dialog should not.
Overall, you need some way to control whether an certain event X bubbles upwards from a certain element Y (which is independent of whether or not you have a handler for event X on element Y)

Control over default actions

Example: on an  tag, to control whether the browser navigates on click (whether or not it's a client-side navigation). Maybe you want to run some async C# logic and then do the navigation.
Example: on a checkbox or select, to avoid changing state on click even though you do respond in another way
Example: on a text box, to block forbidden characters on keydown (and maybe also respond to them in some other way than appending the char to the box)

Constraint: Synchrony
The big limitation, which we've discussed many times, is that for this to work within the Razor Components programming model, we need to know in advance whether you want to cancel bubbling or preventDefault.
We can't have some .NET API for controlling this after the user has triggered the event, because code running on the server receives it later, and the browser APIs are synchronous. Nor can we have some system like suggested here where we block bubbling by default, but then re-raise the event asynchronously if the .NET code says we should - that doesn't work because many browser events can't be simulated from script (e.g., typing), nor are events treated the same if they are triggered asynchronously (e.g., attempting to open a popup). I know people want a way to do this, but there just isn't a way, so we have to come up with a nice design around it.
Design
Controlling propagation of bubbling events
Bubbling events propagate by default, so all we have to do is create a way to say if you don't want a certain event to bubble up from a certain element.

...

Note that we have to phrase it positively. We can't have it as "onsomeevent-bubble=false", because in Razor, a false bool attribute is shorthand for not emitting the attribute at all.
The use of onevent-stop-propagation is completely independent of whether you also have an onevent handler (C# or JS) on that same element, so this is very flexible.
If you need to use event-time logic to decide whether to bubble (e.g., whether the user is holding "shift" or not), your scenario is advanced and you can implement it with JS. Example:

...

    // Separately, in a `.js` file:
    function conditionallyStopPropagation(event) {
        if (!event.shiftKey) {
            event.stopPropagation();
        }
    }

It's not unreasonable to use JS for advanced scenarios like this, and given the synchrony limitation, is the only way you're going to be able to put in totally arbitrary logic that run synchronously.
Control over default actions
Currently, our behavior is that we automatically preventDefault for submit events that have a .NET handler, but don't for any other type of event (whether or not they have a .NET handler).
We can make it possible to prevent default in a similar way to preventing event propagation:
    <input type="checkbox" onclick="@DoSomething" onclick-prevent-default="true" />

Again, onX-prevent-default=true can be used independently of whether you also have an onX event on that element. Internally it will register its own event handler that calls event.preventDefault().
As with above, it's only possible to prevent default based on information that exists prior to the event. You can't use .NET logic to prevent default conditionally after the event has started, because of the synchrony limitation. If you really do need conditional logic, this is an advanced scenario and you'll solve it via JS interop.
Example:
   <input bind="@SomeString" onkeydown="blockDigits(event)" />

    // Separately, in a `.js` file:
    function blockDigits(event) {
        if (event.keyCode >= 48 && event.keyCode <= 57) {
            event.preventDefault();
        }
    }

Again, it's not unreasonable to use JS for advanced and uncommon scenarios like this.
Non-scenarios
Controlling event capture: In JS, it's possible to register event listeners that fire during the "capture" phase of event handling, instead of during the "bubble" phase. However with Razor Components we don't expose that distinction - we use a mixture of capturing and bubbling handlers, depending on the event type, to produce the desired behaviors. If, one day, we have a way of changing your listener to be capturing, then we would also want something like onclick-stop-capture-propagation. But that's not a scenario we have today.
Avoiding preventDefault for submit when there's a .NET handler It's just wrong to ever want to do that. It's just not a scenario.

This seems to be just what I expected 👍 concise and orthonogonal to other features.
One small nitpick - it should also be possible to write these examples with a minimized attribute, and maybe that's the preferred style.

...

It's obvious that there has to be some runtime component to this, do you imagine that there's a compiler/tooling angle as well?

it should also be possible to write these examples with a minimized attribute, and maybe that's the preferred style

Totally agree. I was only writing it with ="true" because I wanted to emphasise that you can specify a bool value if you want to, as people might want it to vary dynamically (e.g., onclick-stop-propagation=@shouldStopPropagation). But if it's given as a minimized attribute, that's interpreted as "true". Also I agree it's the natural and preferred style.

do you imagine that there's a compiler/tooling angle as well?

We can add tooling for intellisense, but I was expecting us not to do so. It's sufficiently advanced that people are only going to be doing this because they're following an example or read about it in docs - the value of discovery through intellisense is lower than for most features.
So how about in the first cut we do it as a runtime feature only, and leave open the option to add a built-in tag helper to provide intellisense later if we want? It will make this much cheaper to implement, and you know how much we need to do in the P5 timeframe.

OK, agreed on all points.

Will these attributes contribute to diffing? I'd like to be able to render either  or  based on some parameter, for asynchronous dynamism.

@gulbanana Yes, they will be normal attributes whose values can change. That's what I meant by this above:

you can specify a bool value if you want to, as people might want it to vary dynamically (e.g., onclick-stop-propagation=@shouldStopPropagation)

another way could be a syntax like:
<button onclick="@(x => x.StopPropagation().Then(() => IncrementCount2(x)))">aa</button>
and also
@for (var i = 0; i <= 2; i++)
{
    <button onclick="@(x => x.StopPropagation(() => i % 2 == 0 )
                             .Then(() => IncrementCount2(x)))">@i</button>
}

with a class like this
namespace WebApplication1.App
{
	public class JSLambda<T> : UIEventArgs where T: UIEventArgs
	{
		Action _action;

		public bool RequestStopPropagation { get; set; }

		public JSLambda<T> StopPropagation()
		{
			RequestStopPropagation = true;
			return this;
		}

		public JSLambda<T> StopPropagation(Func<bool> func)
		{
			RequestStopPropagation = func();
			return this;
		}

		public JSLambda<T> Then(Action action)
		{
			_action = action;
			return this;
		}
	}

	[EventHandler("js-click", typeof(JSLambda<UIMouseEventArgs>))]
	public static class EventHandlers
	{
	}
}

in this way you could be able to control the bubbling from the server side, and possibly also client side if JSLambda could turn c # into javascript (or a series of instructions to be interpreted in javascript), all in c # without dirtying the html

If you are able to do:
onclick-stop-propagation=@shouldStopPropagation
why can't @shouldStopPropagation be an annonymous function? And if that is the case, why can't we just have a property on UIKeyboardEventArgs (or whatever args)? Honestly, using attributes seems wrong and only covers a small portion of what is needed. Personally, I'd prefer to have this left out completely if it's not going to be implemented nicely and rely on interop rather than muddying the water.
I have always found that stopPropagation is something that is either set, or it isn't (typically, but not always). However, preventDefault I use ypically with conditions. Prevent key strokes, button presses based on other inputs ... Very seldom do I blindly override preventDefault for all paths in a control.
I really don't know the technical limitations, but if adding a parameter to the UIKeyboardEventArgs is possible (which I'm 99.9% sure you can't or it would have been done already) or using an annonymous function to be passed to event-stop-propagation instead of a boolean variable, this to me would be prefered.
I don't mean any of this to sound rude at all. I am primarily a front end developer, so not being able to have my conditions in the function that is handling the event seems wrong and limiting. Or maybe I just need to change how I am used to doing things.

@sbuchok It's because of the asynchrony. I know it's not immediately obvious, but it is explained above in this thread.

@SteveSandersonMS Stupid question, can we have both synchronous and asynchronous events? In the synchronous events, allow for preventDefault and stopPropagation. Chances are, this is not a minor change, so I'm guessing it won't go in, but throwing it out there.

No, it's async only.

@SteveSandersonMS
DOH! Ok, having preventDefault for a textbox though doesn't make sense without conditions as you won't be able to type in the textbox.
BTW, I'm loving working with Blazor/RazorComponents (I originally was using Blazor and switched to Razor Components) so far, with this exception ;)
I've primarily worked as a front end developer writing JS so having it work similarly is obviously ideal ... for me. Good luck and thanks.

Does that mean that one day when we are able to access the browser APIs directly from webassembly and we no longer need to write js,  we will still rely on js interop for the event propagation and preventDefault? I thought js interop is a temporary solution until webassembly gets mature enough and we get rid of all the js.

I fully agree with @sbuchok that we usually want to handle preventDefault and often stopPropagation conditionally. I understand that it is a problem in Blazor on the server, but I believe that people will prefer client side Blazor in the future (when it will be fully supported). For those of us it would be nice to have fully functional framework without artificial limitations.

@mkArtakMSFT @danroth27 Realistically I'm not going to be in a position to do this during preview 6.
It's been waiting for the new directive attributes feature so it could build on that, but since that isn't in yet so I couldn't start, and I'm unavailable next week, and I will still need the last bits of this week for auth, it just won't fit.
We can either punt the whole thing, or try to identify someone else to implement it. I hope my design description above would give enough info for someone else to implement it, though the final APIs would look a bit different since they need to align with the new directive attributes once done.
Let's talk about this during team sync today.

I personally would prefer to see this feature gone and force us to use JS Interop rather than bring in something that only works for a small set of desired scenarios.
When I first started using Blazor, I thought that it was going to be able to do everything that JS did. However, I'm guessing it won't and probably was never meant to. If that's the case, maybe forcing us to use JS Interop makes more sense rather than muddying the water.
That's my 2... 5 cents ;)
I also think I'm bias. I love JS. But I'm currently working on something (for myself) where I'm trying to do it 100% in Blazor without any JS. So far, this has been my biggest stumbling block, which really speaks to how much is already available in Blazor.
Thanks again

It's not unreasonable to use JS for advanced scenarios like this, and given the synchrony limitation, is the only way you're going to be able to put in totally arbitrary logic that run synchronously.

That makes me sad 😢

Has there been any news or progress on this? It's blocking me on a number of fronts. Is there any actual workaround currently besides handling the event in JS and invoking the C# handler manually?

If we have this syntax to stop event propagation will we have full control of stopping events in code-behind based on some condition?
<button @onclick="MyHandler" @onclick:stopPropagation="true" />

Maybe better solution is to have behaviour similar to events in WinForms where we can control parameters on event args. Like this:
public class MouseEventArgs : EventArgs
{
    // other properties

    public bool StopPropagation { get; set; }

    public bool PreventDefault { get; set; }
}

void OnClick( MouseEventArgs eventArgs )
{
    if ( someCondition )
    {
        eventArgs.PreventDefault = true;
        return;
    }

    // do something else
}

@stsrki
That's not possible because of the async event handling. The decision has to be upfront. Read Steve's comment above: https://github.com/aspnet/AspNetCore/issues/5545#issuecomment-469748054

@manigandham Thanks, I missed that comment. Steve said there is no way to preventDefault once the event has happened. It seems we're going to be stuck with JavaScript for a long time.

@danieldegtyarev  Could you please let me know about this issue's estimated arrival time?

@kameshrajandran .NET Core 3.1, which is scheduled for Nov/Dec of this year.

The runtime part of this is now done and was merged in https://github.com/aspnet/AspNetCore/pull/14509
The tooling part is going to happen in 3.1.0-preview2, so assigning to @ajaybhargavb for the remaining work.

In fact we have a different issue tracking the tooling work for this (https://github.com/aspnet/AspNetCore/issues/14517), so closing this one.

Was this finally added to the released Blazor 3.0?

Unfortunately it didn't make it into 3.0, but it has now been implemented for 3.1. We will have a preview of the functionality it a couple of weeks.

Awesome. :) I just started fiddling with Blazor and ran into this requirement for drag and drop functionality.

 I tried cancelling and then emulating mouse events but some browsers just wouldn't allow it.
A tricky problem indeed.

WPF has the same issue. You have to mark RoutedEventArgs as Handled before your event handler does anything async.

I wonder if the Blazor team has considered handling bubbling through the Blazor framework itself and bypassing Javascript event bubbling? Or would that just be too overwhelming for every DOM element to trigger an event in C# just for the possibility of bubbling it up to a parent?


Added optional token validation

On some endpoints I need to proxy a request with token and without token. For instance, GET /basket can be requested by guests and by authorized users. In order to use it, I added new option optional for auth/validator middleware.

Hi @a-tarhanov,
Thank you very much for your contribution. It is indeed an interesting approach.
Although I understand what you are trying to achieve, this "new feature" causes me several doubts. Having a flag that opens dual behavior will have consequences and misbehavior on other components that rely on validation, like security policies, CEL, url_pattern claim extraction and alike.
There are several ways to achieve this functionality without adding this new flag:

Use two different endpoints, /basket, and /basket-anonymous and let the client use one or the other
Using the same approach above, but instead of the client deciding the path, let KrakenD calculate it from the absence or presence of the token:

{
	"endpoints": [{
		"endpoint": "/basket",
		"input_headers": ["Authorization"],
		"backends": [{
			"url_pattern": "/foo",
			"host": ["backend.com"],
			"extra_config": {
				"validation/cel": [{
					"check_expr": "size(req_headers['Authorization'])==0"
				}]
			}
		}, {
			"url_pattern": "/private-basket",
			"host": ["localhost"],
			"extra_config": {
				"validation/cel": [{
					"check_expr": "size(req_headers['Authorization'])>0"
				}]
			}
		}, ],
		"extra_config": {
			"modifier/lua-proxy": {
				"post": "local r = response.load(); r:isComplete(true);",
			}
		}
	}, {
		"endpoint": "/private-basket",
		"input_headers": ["Authorization"],
		"backends": [{
			"url_pattern": "/foo",
			"host": ["backend.com"]
		}],
		"extra_config": {
			"auth/validator": {
				"alg": "RS256",
				"jwk_url": "https://albert-test.auth0.com/.well-known/jwks.json",
				"cache": true
			}
		}
	}]
}

I would ask other questions about the business case you are trying to solve, but they are unrelated to KrakenD.
I am closing the pull request because even I see the point and I don't dislike it, this will have many side effects, and I don't see it safe. Feel free to add any other additional comments.
Thanks
Thank you for the contribution

@alombarte, thank you for so advanced feedback. I'll try second variant you offered.


telemetry/alerts issue fix; dockerfile fix

ensuring protobuf compilation before kubearmor src compilation
upgraded Docker image to use of golang 1.17 from 1.15
upgraded Docker image to use of alpine 3.15 from 3.12
fixes to file/dir copy during image build
Removed use of docker tags for GITHUB_SHA ... using docker labels instead
added verbose log when Watch*() APIs break

Signed-off-by: Rahul Jadhav<EMAIL_ADDRESS>

Codecov Report

Merging #541 (0dcf73c) into main (43b8d7e) will decrease coverage by 31.98%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #541       +/-   ##
==========================================
- Coverage   37.93%   5.95%   -31.99%
==========================================
  Files          23      13       -10
  Lines        9165    6365     -2800
==========================================
- Hits         3477     379     -3098
- Misses       5297    5918      +621
+ Partials      391      68      -323

Impacted Files
Coverage Δ

KubeArmor/feeder/feeder.go
14.98% <0.00%> (-37.00%)
:arrow_down:

KubeArmor/monitor/processTree.go
0.00% <0.00%> (-83.65%)
:arrow_down:

KubeArmor/monitor/syscallParser.go
0.00% <0.00%> (-79.98%)
:arrow_down:

KubeArmor/monitor/logUpdate.go
0.00% <0.00%> (-75.48%)
:arrow_down:

KubeArmor/feeder/policyMatcher.go
0.00% <0.00%> (-40.42%)
:arrow_down:

KubeArmor/enforcer/runtimeEnforcer.go
0.00% <0.00%> (-33.34%)
:arrow_down:

KubeArmor/enforcer/appArmorProfile.go
0.00% <0.00%> (-30.53%)
:arrow_down:

KubeArmor/monitor/systemMonitor.go
27.23% <0.00%> (-4.67%)
:arrow_down:

KubeArmor/main.go

... and 10 more

Continue to review full report at Codecov.

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


Page is outdated and missing key information

This page does not explain the various settings of the Use New Teams Client drop down.
This page is linked from https://admin.teams.microsoft.com/policies/updatemanagement
The policy values for that drop down are explained in https://learn.microsoft.com/en-us/microsoftteams/new-teams-deploy-using-policies?tabs=teams-admin-center , which is listed in the Related Topics section, but it's not obvious when you are on the "Microsoft Teams Public preview" page that you need to go to the other page to learn about the options for the Use New Teams Client dropdown.
Given that this page is about the public preview, and New Teams is Generally Available, this page is obsolete and should probably just redirect to https://learn.microsoft.com/en-us/microsoftteams/new-teams-deploy-using-policies?tabs=teams-admin-center#set-the-policies-to-upgrade-to-the-new-teams-client

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: e5f1cdd1-09ff-f95d-6d50-e7880d34020f
Version Independent ID: 59219640-305b-30c1-bc10-87e2633d95db
Content: Public preview in Microsoft Teams - Microsoft Teams
Content Source: Teams/public-preview-doc-updates.md
Service: msteams
GitHub Login: @MicrosoftHeidi
Microsoft Alias: heidip

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


check compatibility for chart.js 2.9.x

fixed with https://github.com/sgratzl/chartjs-chart-error-bars/releases/tag/v1.2.0


Use localized numbers

Hi
If you set moment.locale("fa"); and use moment.loadPersian();, You see this:
m = moment('1360/5/26', 'jYYYY/jM/jD') // Parse a Jalaali date
m.format('jYYYY/jM/jD') // 1360/5/26

But I expect to see something like the below line, because I have configured moment to use fa locale.
m.format('jYYYY/jM/jD') // ۱۳۶۰/۵/۲۶

I thin it would be great if we could consider the locale instaed of moment.loadPersian(); ;-)

loadPersian is optional. If you don't need it, just don't use it. locale('fa') will be sufficient for your case.


feat: use junk value in Kernel.map, new class IsZeroOrMarkovKernel

Followup to #16130, doing this at the level of kernels instead of measures.

It looks like this PR contains some changes that are also in #16399 (in Independence/Kernel). Please merge master once that other one is merged.

I have merged master.

Thanks! The new map looks much easier to use.
bors r+


When the code will be final published and models?

I have got error:
python setup.py develop
Traceback (most recent call last):
File "C:\Users\mika\drct\setup.py", line 83, in
write_version_py()
File "C:\Users\mika\drct\setup.py", line 65, in write_version_py
with open(version_file, 'w') as f:
FileNotFoundError: [Errno 2] No such file or directory: 'hat/version.py'
When the code will be final published and models?
Thanks!

Hi, sorry for inconvenience, we will fix it up as soon as possible.
(note: our environment is based on HAT, you can install the enviroment as HAT's repository, then use our configuration for training and inference.)
The pretrained-model will be released in the future.

When we can expect Real_DRCT_GAN? Thanks

Hi, we are aiming to update Real_DRCT_GAN within the next month (or possibly in two to three weeks).
Due to our typically busy schedule, updates may be slower.
Thank you for your patience and understanding.

@ming053l
Any news about releasing models?
:) Thanks

@ming053l
Hi. Any news on when we can expect the models? I'm really excited for their release. Thanks a lot :)


vue-server-renderer: createBundleRenderer() sourcemaps

Hey!
Is there a way to pass in a sourcemap to createBundleRenderer()? There's an options argument, but it isn't documented (happy to write these docs if you point me towards the correct bit of source: I couldn't find it).
Currently, I'm getting this error, which isn't too understandable:
ReferenceError: window is not defined
    at e.__esModule.default (__vue_ssr_bundle__:1:478)
    at __vue_ssr_bundle__:1:1052
    at r.(anonymous function).exports (__vue_ssr_bundle__:1:146)
    at Object.<anonymous> (__vue_ssr_bundle__:1:285)
    at /Users/callumacrae/Sites/samknows/website-vue/node_modules/vue-server-renderer/build.js:6152:21
    at runInVm (/Users/callumacrae/Sites/samknows/website-vue/node_modules/vue-server-renderer/build.js:6144:10)
    at Object.renderToStream (/Users/callumacrae/Sites/samknows/website-vue/node_modules/vue-server-renderer/build.js:6175:9)
    at server.get (/Users/callumacrae/Sites/samknows/website-vue/server/index.js:29:35)
    at Layer.handle [as handle_request] (/Users/callumacrae/Sites/samknows/website-vue/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/callumacrae/Sites/samknows/website-vue/node_modules/express/lib/router/route.js:131:13)

It's currently not supported yet but on the roadmap.

Amazing! Just had to use git bisect to find the source of a bug.
Sorry for duplicate issue, searched the wrong words.


find/findAll produces unexpected results with stubbed components

Consider this component:
<template>

      <child></child>

      <child></child>

</template>

and this test:
import { shallow } from 'vue-test-utils'
import ComponentWithChild from '@/components/ComponentWithChild'

const ChildStub = {
  name: 'child-stub',
  render: () => {}
}

const wrapper = shallow(ComponentWithChild, { stubs: { 'child': ChildStub } })

it ('', () => {
  expect(wrapper.findAll(ChildStub).length).to.equal(2) // true
  expect(wrapper.find('.first-child').findAll(ChildStub).length).to.equal(1) // nope, it's 2
})

I would have expected the second expectation to pass, but instead, findAll returns both instances of the ChildStub component, not just the one in the .first-child div.

Yes, this should be fixed.

I've added a fix to the dev branch. It will be released in 1.0.0-beta.7

Awesome, thanks a bunch for the quick fix!


Per 622 add labels usage and k 8 s labels usage

Describe your changes
Add labels and k8s labels to fix according to controls c-0076, c-0077
Checklist before requesting a review

[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have performed a self-review of my code
[x] If it is a core feature, I have added thorough tests.
[x] New and existing unit tests pass locally with my changes

Please open the PR against the dev branch (Unless the PR contains only documentation changes)

I think the branch is wrong ;)


Set value returned via JSON

Hi, I'm trying to set a value to selectpicker, without success.
if I set this manually, it works:
ex:
$('.selectpicker').selectpicker('val', ['181', '45'] );
$('#formulario #idspessoacontato').selectpicker('render');
but when trying to set with dynamic value (in string), it didn't work:
ex:
var stringWithValue = "['181', '45']";
$('.selectpicker').selectpicker('val', stringWithValue );
$('#formulario #idspessoacontato').selectpicker('render');
What am I doing wrong??
Thanks.

in first code u gave an array, in second - string. Maybe problem with this types?

Sure. Great!
Thanks @DarkMerge !


KOGITO-4113 Move all jenkins files to .ci/jenkins

https://issues.redhat.com/browse/KOGITO-4113
Move all Jenkins related files to .ci/jenkins folder
Dependent PRs:

https://github.com/kiegroup/kogito-pipelines/pull/210
https://github.com/kiegroup/kogito-runtimes/pull/1434
https://github.com/kiegroup/kogito-apps/pull/932
https://github.com/kiegroup/kogito-examples/pull/781
https://github.com/kiegroup/kogito-images/pull/610
https://github.com/kiegroup/kogito-operator/pull/946
https://github.com/kiegroup/rhpam-kogito-operator/pull/69

Can you add also this PR in the description ? and they are more "related" than dependent

How the Jenkins job is configured ?

we don't have DSL for it, so for now we keep prod jobs up to date by hand. Once the PR is merged I will manually update the job.
I've additionally updated the description (from Dependant to related)
Task create to DSL prod jobs https://issues.redhat.com/browse/BXMSPROD-1443


How to do from oracle to delta? example?

How to do from oracle to delta? example?

Hi @juice411, sorry for the late response. Can you explain a little more about the meaning of "from oracle to delta"? Do you want to read data in an Oracle DB and save the output with delta lake?


aarch64: Migrate iadd and isub to ISLE

This commit is the first "meaty" instruction added to ISLE for the
AArch64 backend. I chose to pick the first two in the current lowering's
match statement, isub and iadd. These two turned out to be
particularly interesting for a few reasons:

Both had clearly migratable-to-ISLE behavior along the lines of
special-casing per type. For example 128-bit and vector arithmetic
were both easily translateable.

The iadd instruction has special cases for fusing with a
multiplication to generate madd which is expressed pretty easily in
ISLE.

Otherwise both instructions had a number of forms where they attempted
to interpret the RHS as various forms of constants, extends, or
shifts. There's a bit of a design space of how best to represent this
in ISLE and what I settled on was to have a special case for each form
of instruction, and the special cases are somewhat duplicated between
iadd and isub. There's custom "extractors" for the special cases
and instructions that support these special cases will have an
rule-per-case.

Overall I think the ISLE transitioned pretty well. I don't think that
the aarch64 backend is going to follow the x64 backend super closely,
though. For example the x64 backend is having a helper-per-instruction
at the moment but with AArch64 it seems to make more sense to only have
a helper-per-enum-variant-of-MInst. This is because the same
instruction (e.g. ALUOp::Sub32) can be expressed with multiple
different forms depending on the payload.
It's worth noting that the ISLE looks like it's a good deal larger than
the code actually being removed from lowering as part of this commit. I
think this is deceptive though because a lot of the logic in
put_input_in_rse_imm12_maybe_negated and alu_inst_imm12 is being
inlined into the ISLE definitions for each instruction instead of having
it all packed into the helper functions. Some of the "boilerplate" here
is the addition of various ISLE utilities as well.

Thanks for tackling this -- excited to see the fast progress!
I wanted to note specifically on

a lot of the logic in put_input_in_rse_imm12_maybe_negated and alu_inst_imm12 is being inlined into the ISLE definitions for each instruction

One of the things I had imagined when designing the compilation model (each internal constructor becomes a Rust function) is that we could actually replicate what we did in the handwritten code -- namely, we could have a helper that gives a ResultRSEImm12-like thing. I think doing so would help both from an expressivity point of view (less repetition, easier to understand) and code-size point of view.
An interesting question is whether this is an extractor (part of the pattern) or a constructor; IMHO it makes sense to do it as a constructor because it's infallible -- we know we can always do something, we can't fall back to other rules -- so something like (put_in_reg_shift_extend_imm12 value) would make sense to me, then that constructor can have (rule (put_in_reg_shift_extend_imm12 (imm12 val)) (ResultRSEImm12.Imm12 val)) etc. Thoughts?

An interesting question is whether this is an extractor (part of the pattern) or a constructor; IMHO it makes sense to do it as a constructor because it's infallible -- we know we can always do something, we can't fall back to other rules -- so something like (put_in_reg_shift_extend_imm12 value) would make sense to me, then that constructor can have (rule (put_in_reg_shift_extend_imm12 (imm12 val)) (ResultRSEImm12.Imm12 val)) etc. Thoughts?

Because addition is commutative, we want to use a fallible extractor here that we can try in both the left and right operands, and then have a fallback base case for putting everything into registers.
If this were subtraction, and we would want to just call this once for the right operand and accept whatever answer it gave, then I would agree that it should be a plain constructor.
This is analogous to why there is both put_in_reg_mem and the sinkable_load extractor and sink_load constructor in the x86 ISLE code.

This is definitely one of the things I went back and forth on a lot of how to design this support. I was originally thinking I would do something like:
(rule (lower (has_type (fits_in_64 ty) (iadd x (extract_rse_imm12 y))))
      (value_reg (alu_rse (iadd_op ty) (put_in_reg x) y)))

where extract_rse_imm12 basically corresponds to put_input_in_rse_imm. This gets kinda unfortunate I think relatively quickly for a few reasons:

One is that for add/subtraction we actually want extract_rse_maybe_negated_imm12 which has two outputs which is sorta wonky to describe in ISLE.
Currently I think extract_rse_imm12 can only be implemented in Rust, not in ISLE itself, which means that ISLE has no visibility into trees of expressions for a better trie to build. This also means that a lot of "pattern matching code" would still be present in Rust which I figured the goal was to move most of it to ISLE.

My end-conclusion was that for all the put_input_in_rs*-style functions we'd have custom extractors for each variant of the rs* (one for extending, one for shifting, one for immediates, etc). This gives ISLE more visibility into the entire trie. For cases like shifts and immediates ISLE has the entire trie, but for extends ISLE doesn't get any part of the trie because we want to match a suite of extending operations and ISLE extractors can only have one "arm" right now in a sense. But I was hopeful that maybe one day this could be worked out where ISLE has the whole trie and is able to optimize with that where Rust is doing the bare minimum of converting between immediates and such.
My conclusion was also the same as Nick's though where we want to have these as extractors rather than constructors. Today the AArch64 backend doesn't actually handle the case of an iadd with a left-hand-side immediate, that generates movement instructions and such. I think we might want to feasibly handle the commutative sides as well here in lowering.

Ah, good points. I agree that given the need to try both operand orders and pick the better one, and given subtle variations in some instructions, the current approach probably makes the most sense.
One thought that does strike me is: if there are instructions with exactly the same cases, modulo opcode itself (e.g., all of the logical insts -- and, or, xor as a group, and and-not / or-not / xor-not as a group), we could have an extractor that matches any of the group, and returns the opcode; then use this opcode in the (alu_rr_immlogical ...) or whatnot. Something like:
(rule (lower (aarch64_logical_inst op ...))
          (alu_rr_immlogical op (put_in_reg ...) (put_in_reg ...)))

with the N cases for immediates, shifts, etc., laid out here but only once for the and/or/not/... group.

Ah yeah I want to stay on the lookout for whether iadd/isub will have lots of duplication with other instructions, and if that's the case I think it's worth figuring out a different route here like the aarch64_logical_inst you mentioned @cfallin.
Otherwise should be updated with your review @fitzgen!

Thanks!


Lots of difficulties installing M3T - especially GLEW

Hi all,
I don't usually like posting about install issues because it clutters things, but the Build section of the readme.md in M3T doesn't explain a lot of steps e.g. how do we use CMake? How do we install Eigen 3, GLEW GLFW 3 and OpenCV 4. The links they point do don't really explain much either.
Where I am: I've gitcloned all the above, and can get to line 28 of CMakeLists.txt (find_package(Eigen3 3.3.2 REQUIRED)). This works fine, but I cannot figure out how to get further with GLEW:
PS ....\3DObjectTracking\M3T> cmake -S . -B ./build-dir -DCMAKE_BUILD_TYPE=Release -DUSE_AZURE_KINECT=FALSE -D CMAKE_C_COMPILER="C:\msys64\mingw64\bin\gcc.exe" -D CMAKE_CXX_COMPILER="C:\msys64\mingw64\bin\g++.exe"  -G "MSYS Makefiles" -D Eigen3_DIR="C:\Tools\eigen-3.4.0\build" -D GLEW_INCLUDE_DIRS="C:\Tools\glew-2.1.0\include" -D GLEW_LIBRARIES="C:\Tools\glew-2.1.0\lib"
CMake Error at C:/Program Files/CMake/share/cmake-3.31/Modules/FindPackageHandleStandardArgs.cmake:233 (message):
  Could NOT find GLEW (missing: GLEW_INCLUDE_DIRS GLEW_LIBRARIES)
Call Stack (most recent call first):
  C:/Program Files/CMake/share/cmake-3.31/Modules/FindPackageHandleStandardArgs.cmake:603 (_FPHSA_FAILURE_MESSAGE)
  C:/Program Files/CMake/share/cmake-3.31/Modules/FindGLEW.cmake:245 (find_package_handle_standard_args)
  CMakeLists.txt:29 (find_package)

-- Configuring incomplete, errors occurred!
....\3DObjectTracking\M3T>

Notice that the error mentions missing  GLEW_INCLUDE_DIRS GLEW_LIBRARIES, which is not true at all, I've clearly defined those two symbols in the command line:
-D GLEW_INCLUDE_DIRS="C:\Tools\glew-2.1.0\include" -D GLEW_LIBRARIES="C:\Tools\glew-2.1.0\lib"

I would guess we set GLEW_INCLUDE_DIRS to C:\Tools\glew-2.1.0\include\GL (where the GLEW header files live) and I'd guess we set GLEW_LIBRARIES to C:\Tools\glew-2.1.0\lib\Release\x64, but again this did not work either. Same error as above.
Any help appreciated please.
~Greg

Having similar difficulties with what seems like basic stuff. Probably need to learn more about cmake and dependencies...
Maybe someone can recommend a good source for learning?

Was able to successfully build the M3T library! I recommend installing all the dependencies with vcpkg.
Used mainly chatGPT to solve my problems error after error since I am not a developer.
Hope that helps!


DO NOT MERGE (PUP-5873) Contain generated resources

Adding this PR to get feedback about the approach. Note this is based on PR https://github.com/puppetlabs/puppet/pull/4660, which needs to be merged first.
Previously, we copied relationship parameters as strings from the parent
directory to each generated resource. This ensured somewhat accidentally
that generated resources were contained, meaning all of the generated
resources were evaluated before any resource downstream from the parent
directory.
However, if the parent had multiple relationships, we were calling
Array#to_s, causing the catalog to contain:
"before": "[Notify[hi]{:name=>\"hi\"}, Notify[there]{:name=>\"there\"}]"

This caused the agent run to fail, since there's no resource with that
name.
This commit ensures we copy the relationship object to the generated
resource. It can either be a String or Array depending on the number of
relationship edges.

Given a manifest like:
class ntp {
  file { '/tmp/foo':
    ensure => directory,
  }

  file { '/tmp/foo/dir':
    ensure  => directory,
    recurse => remote,
    source  => 'puppet:///modules/ntp/dir',
    before  => [Notify['hi'], Notify['there']]
  }

  notify { 'hi': }

  notify { 'there': }
}

Compiling the catalogs and running the agent with --graph generate the following graphs. The Resource and Relationship graphs are generated (on the agent) after parsing the resource catalog (using the resources and edges in the catalog):

The agent builds the expanded relationship graph and is what it uses when applying resources. Since the parent directory comes before both Notify resources, all of the generated resources come before them as well:

This doesn't cover auto-require relationships. But I'm not sure auto-requires on generated resources works anyway. /cc @branan

I'm not sure auto-requires on generated resources works anyway

Good question. Auto* relationships work for generated resources in static catalogs, because the resources are in the catalog before we build_autorelationship_dependencies. But they don't work with eval_generate or generate resources, since those resources are added to the catalog later.

@branan commented in meatspace that this doesn't handle the case where a non-file resources has a relationship on the recursive parent:
file { '/tmp/foo/dir':
  ensure  => directory,
  recurse => remote,
  source  => 'puppet:///modules/ntp/dir',
}

notify { 'hi':
  require => File['/tmp/foo/dir']
}

Need to create edge(s) going the other way from each generated resource, e.g. File['/tmp/foo/dir/file'] -> Notify['hi'] for full containment.

We are going to handle this a different way. See PUP-5114


API access for data in the LocalChangeEntity table

Is your feature request related to a problem? Please describe.
Currently there's no API to access data in the LocalChangeEntity table
Describe the solution you'd like
In the client app we'd like a way to obtain Read Only access to the LocalChangeEntity table data, specifically the SquashedLocalChanges.
We can add an interface in FhirEngine.kt and the corresponding implementation in FhirEngineImpl.kt
//FhirEngine.kt
suspend fun getUnsyncedLocalChanges(): List<SquashedLocalChange>

//FhirEngineImpl.kt
override suspend fun getUnsyncedLocalChanges() : List<SquashedLocalChange> = database.getAllLocalChanges()

Describe alternatives you've considered
Might be better to have an API that just returns the counts for the grouped changes per resource because if there's too much data in the LocalChangeEntity table it may lead performance issues since obtaining the counts with the above approach is an in memory operation.
Additional context
This will be useful when one wants have the visibility of the Synced/Unsynced resources on the device.
Here is a sample of what can be achieved by this:

Would you like to work on the issue?
Yes

Thanks for raising this. Haven't thought about this carefully, but is it possible at all to reuse the syncUpload API for this purpose? Maybe we could change the API so that if no result is returned from the lambda we do not delete the local changes from the local changes table - so that esesentially you're using that API to read local changes.

It is worth noting that the above functionality/implementation renders the dialog based on a user action rather than at the end of a Sync job

Additional note, we may need to refactor Database.getAllLocalChanges() API for optimisation since it reads all the records into memory before performing the squash operation and returning the results.
For a case where an application using the SDK is offline first, they might have collected a lot of data in the field and its months before they can get a working internet connection to sync upward to the server.
This might require a new ticket but is worth highlighting here cc @jingtang10

@anchita-g

as of the latest design changes in the sync module, we will be deprecating syncUpload and syncDownload methods. the normal sync APIs will still be functioning as usual but we have concluded the syncUpload and syndDownload APIs are not utilised by developers and are overly complex. this actually means we do need to provide sufficient capabilities to manage local changes. so we need to work on this more.

Is your feature request related to a problem? Please describe. Currently there's no API to access data in the LocalChangeEntity table
Describe the solution you'd like In the client app we'd like a way to obtain Read Only access to the LocalChangeEntity table data, specifically the SquashedLocalChanges.
We can add an interface in FhirEngine.kt and the corresponding implementation in FhirEngineImpl.kt
//FhirEngine.kt
suspend fun getUnsyncedLocalChanges(): List<SquashedLocalChange>

//FhirEngineImpl.kt
override suspend fun getUnsyncedLocalChanges() : List<SquashedLocalChange> = database.getAllLocalChanges()

Describe alternatives you've considered Might be better to have an API that just returns the counts for the grouped changes per resource because if there's too much data in the LocalChangeEntity table it may lead performance issues since obtaining the counts with the above approach is an in memory operation.
Additional context This will be useful when one wants have the visibility of the Synced/Unsynced resources on the device.
Here is a sample of what can be achieved by this:

**Would you like to work on the issue?** Yes

@ndegwamartin
//FhirEngine.kt
Could you provide more details on what information is expected in the SquashedLocalChange class?
We could consider including the following:

Resource type
resource IDs
The total count of local changes per resource
A list of local change IDs for each resource
The count of changes per operation type (e.g., Insert, Update, Delete)

Not sure if the following should be included :

Local changes per resource type (which could be fetched separately by the application)
Local changes per operation type and resource type (which can also be fetched separately using change IDs)

@santosh-pingle yeah I think we can enhance the returned results with all the above, but at the very basic level, at least for our use case we just needed the map of Resource type to the grouped(by resourced id) count of all local changes. That is for example, if the same Patient Resource has multiple updates it will show up as one unsynced Patient resource.


[Event Request] Table 39 Purchase Line – Description – OnValidate

Event Request] Table 39 Purchase Line – Description – OnValidate
Could we please have a publisher OnBeforeValidateDescriptionWithHandled in function Description – OnValidate() of Table 39 Purchase Line?
trigger OnValidate()
var
    Item: Record Item;
    ApplicationAreaMgmtFacade: Codeunit "Application Area Mgmt. Facade";
    FindRecordMgt: Codeunit "Find Record Management";
    ConfirmManagement: Codeunit "Confirm Management";
    ReturnValue: Text[50];
    DescriptionIsNo: Boolean;
    IsHandled: Boolean;
begin
    // >>>>
    IsHandled := false;
    OnBeforeValidateDescriptionWithHandled(var Rec, xRec, var IsHandled);
    if IsHandled then
        exit;
    // <<<<
    if Type = Type::" " then
        exit;

    if ("No." <> '') and (Type in [Type::Item, Type::"Charge (Item)"]) then begin
        case Type of
            Type::Item:
                begin
                    if (StrLen(Description) <= MaxStrLen(Item."No.")) and ("No." <> '') then
                        DescriptionIsNo := Item.Get(Description)
                    else
                        DescriptionIsNo := false;

                    if not DescriptionIsNo then begin

This search by description functionality fixed, probably you don't need to disable it anymore

Unfortunately, it's not just about the fix. We also have to deactivate the functionality due to our business logic like in table 37-„Sales Line.

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

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


latest_testflight_build_number should return 0 if no prior build exists

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I want using the same code snippet for new projects. It looks something like this:
increment_build_number({
        build_number: latest_testflight_build_number(app_identifier: 'com.foo.bar') + 1
})

Unfortunately it updates my build number to 2 instead of 1 when uploading the very first IPA to TestFlight.

It supports the initial_build_number param https://docs.fastlane.tools/actions/latest_testflight_build_number/
increment_build_number({
  build_number: latest_testflight_build_number(app_identifier: 'com.foo.bar', initial_build_number: 0) + 1
})

It supports the initial_build_number param https://docs.fastlane.tools/actions/latest_testflight_build_number/
increment_build_number({
  build_number: latest_testflight_build_number(app_identifier: 'com.foo.bar', initial_build_number: 0) + 1
})

Great. Thanks.


SPI Master driver crashes when using shared interrupts (ESP_INTR_FLAG_SHARED) (IDFGH-9467)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.0.1
Operating System used.
Windows
How did you build your project?
Eclipse IDE
If you are using Windows, please specify command line type.
PowerShell
Development Kit.
ESP32-S3-WROOM-1
Power Supply used.
USB
What is the expected behavior?
After instantiating the SPI master driver and passing ESP_INTR_FLAG_SHARED to spi_bus_config_t::intr_flags, SPI should work and use the shared interrupt.
What is the actual behavior?
This assertion is triggered when an SPI interrupt occurs.
Steps to reproduce.
Instantiate the SPI driver like this:
static spi_bus_config_t spiConfig = {
	...
	.intr_flags = ESP_INTR_FLAG_SHARED
};
ESP_ERROR_CHECK (spi_bus_initialize (SPI3_HOST, &spiConfig, SPI_DMA_CH_AUTO));

Perform some transactions like
spi_transaction_t trans {
	.flags = SPI_TRANS_USE_RXDATA,
	.cmd = static_cast<std::uint8_t> (0x80 | addr),
	.addr = 0,
	.length = 16,
	.rxlength = 8,
	.user = nullptr,
	.tx_buffer = nullptr,
	.rx_buffer = nullptr
};
ESP_ERROR_CHECK (spi_device_transmit (devHandle, &trans));

And simultaneously use some other periphery which uses the shared interrupt.
Debug Logs.
assert failed: spi_intr spi_master.c:592 (spi_hal_usr_is_done(&host->hal))

Backtrace: 0x403760ce:0x3fc96c20 0x4037d4fd:0x3fc96c40 0x40383c2d:0x3fc96c60 0x40378846:0x3fc96d80 0x40376735:0x3fc96db0 0x403773f5:0x3fc96dd0 0x400559dd:0x3fc9ce50 |<-CORRUPTED
0x403760ce: panic_abort at esp-idf-v5.0.1/components/esp_system/panic.c:423

0x4037d4fd: esp_system_abort at esp-idf-v5.0.1/components/esp_system/esp_system.c:153

0x40383c2d: __assert_func at esp-idf-v5.0.1/components/newlib/assert.c:78

0x40378846: spi_intr at esp-idf-v5.0.1/components/driver/spi_master.c:592 (discriminator 1)

0x40376735: shared_intr_isr at esp-idf-v5.0.1/components/esp_hw_support/intr_alloc.c:436

0x403773f5: _xt_lowint1 at esp-idf-v5.0.1/components/freertos/FreeRTOS-Kernel/portable/xtensa/xtensa_vectors.S:1118

More Information.
I think the issue is caused by using esp_intr_alloc for a (possibly) shared interrupt. The shared interrupt handler (shared_intr_isr) can't check whether the interrupt was actually triggered by the SPI periphery, so spi_intr is called even though there was no SPI interrupt. This then triggers the assertion.
So we should either:

state in the documentation that ESP_INTR_FLAG_SHARED in spi_bus_config_t::intr_flags is not supported (and possibly add an assertion to check that)
Change the assertion to a simple return instead of crashing: if (!spi_hal_usr_is_done(&host->hal)) return;
Use esp_intr_alloc_intrstatus instead and pass the SPI register to only call spi_intr when an SPI interrupt actually occured, e.g.:

err = esp_intr_alloc_intrstatus(spicommon_irqsource_for_host(host_id),
					bus_attr->bus_cfg.intr_flags | ESP_INTR_FLAG_INTRDISABLED,

					(uint32_t) &host->hal.hw->dma_int_raw,
					SPI_TRANS_DONE_INT_RAW,

					spi_intr, host, &host->intr);

This block then needs to be moved below the call to spi_hal_init.

@Erlkoenig90 Hello, not all interrupt source is able to be shared, it decided by chip hardware.
For example, SPI2 interrupt source of ESP32S3 is not able to be shared, only SPI2 can alert this interrupt, there is no means to share this, you may enter spi_intr by accident, but other peripherals you shared can't alert this interrupt.

Hi, in this case the SPI documentation should state that ESP_INTR_FLAG_SHARED in spi_bus_config_t::intr_flags is not supported, and an assertion to check for that would be helpful. Currently it is not clear from the IDF documentation that this interrupt can't be shared.

@Erlkoenig90's got a point. Such a check should also be replicated to other peripherals components' initialization routines.

@Erlkoenig90
You are right, it is understandable, I think espressif official can accept this.

@Erlkoenig90 Hello, Sorry for my last replay.
For the newest information, I heard that this interrupt can be shared, it is a bug on SPI_Master driver, and they will fix it recently :fire:

Great, I appreciate it!


Add jwt support.

This adds a jwtauth package which simplilfies the jwt handling for echo.
Included is a helper which sets an jwtauth.ActorKey on the echo context with the JWT Subject value.
Additionally, test helpers were added to simplify testing oauth in tests.
Tests were added to test auth conditions as well.

thanks, i thought of that too. but i think we'll just do the gin swap in a separate ticket. this also fixes some ci bits


Sorry to disturb again, now I'm stuck in this step.

I forward message from target group and that's ok. But then I forward message from source group and nothing happens.
The code give me an error in line 23. I tried to close bracket but doesn't help.
Thanks again

Originally posted by @VHCSBlast in https://github.com/Nunnito/PyWardBot/issues/5#issuecomment-1769645479

Hi again, VHCSBlast!
That's a really odd error. It seems that the JSON file wasn't closed properly.
You should try to delete the config/forwarding.json file and run the bot again. If the issue persists, please let me know!

Hi again,
I deleted the config/forwarding.json file and run the bot again. Error in the same step.
I deleted all the files, and did everything all over again. Now I get a diferent error but in the same step.
When I try to put the source channel the bot stop responding.
Error on LN 23 at forwarding.json.
Can you send me your forwarding.json to chek if I can copy the rest of the code manually and just replace the chat ID?

Could you please send the source and target chat you are entering? I think this is a issue that only occurs on Windows, but I can't replicate it.
And sure, you can see the format of the configuration here.
Mine looks like this:
{
    "forwarders": [
        {
            "name": "Nunnito",
            "target": 628910404,
            "enabled": true,
            "forwarding_mode": "copy",
            "incoming": true,
            "outgoing": true,
            "reply": true,
            "duplicated_text": false,
            "send_text_only": false,
            "translate": false,
            "translate_to": "en",
            "translate_from": "auto",
            "translate_show_original": false,
            "translate_original_prefix": "Original:",
            "translate_translation_prefix": "Translated:",
            "replace_words_mode": "word_boundary_match",
            "replace_words": {},
            "blocked_words": [],
            "source": {
                "628910404": "Nunnito"
            },
            "patterns": []
        }
    ],
    "blocked_images": []
}

Hi,
i got this message like this how to open the bot.
can u help me.

Hey, kalyanbkc123!
What's your issue? To open the bot just send your Telegram bot the command /start and you're done!

Hi, i am a beginner how to launch the bot from where can u help.. tq


incorrect rendering / no "rendering is incorrect" warning

http://stadtmusik-sursee.ch/phocadownload/2013_Chlausmaeaert/2013_Chlausmaert_A5.pdf
web console output (FF 26 Beta 8):
Unknown pseudo-class or pseudo-element 'fullscreen'.  Ruleset ignored due to bad selector. viewer.css:58
12:33:58.724 Unknown pseudo-class or pseudo-element 'fullscreen'.  Ruleset ignored due to bad selector. viewer.css:73
12:33:58.724 Unknown pseudo-class or pseudo-element 'fullscreen'.  Ruleset ignored due to bad selector. viewer.css:81
12:33:58.724 Unknown pseudo-class or pseudo-element 'fullscreen'.  Ruleset ignored due to bad selector. viewer.css:89
12:33:58.725 Unknown property 'box-sizing'.  Declaration dropped. viewer.css:822
12:33:58.725 Unknown pseudo-class or pseudo-element 'selection'.  Ruleset ignored due to bad selector. viewer.css:1225
12:33:59.157 "PDF cc0a252e7914bab8c28dce9e963f31 1.6 Adobe PDF Library 10.0.1 / Adobe InDesign CC (Macintosh) (PDF.js: 0.8.751)"

Probably the same issue as #6130.

http://stadtmusik-sursee.ch/phocadownload/2013_Chlausmaeaert/2013_Chlausmaert_A5.pdf

Since the link appears to be dead now, I'm attaching the file here: issue3988.pdf.


[otbn,dv] Wire up prim_count standardised DV for loop counter

Standardised DV Test for loop counter.
PR pending.
https://github.com/lowRISC/opentitan/pull/13956


Fix eslint errors in wms-time example

LGTM sorry about this @fredj I didn't think about the eslint changes

@bartvde no problem !


HAWQ-1550. Constrain max log file storage/duration

A) add guc 'log_max_size' to constrain max log storage
B) add guc 'log_max_age' to constraint log size

Thanks @kuien
I think we should delegate log rotation works to some outer tools, and the behavior is the same as GPDB/Posgres.

make sense

Thanks @kuien, welcome to propose more PRs.


ensure Morinlab fork of g3viz is installed as a dependency

It seems that the auto-installation of dependencies is relying on the main g3viz version, which doesn't handle MAFs the way we need for certain functions. For some GAMBLR functions to work we need users to have the version here:
https://github.com/morinlab/g3viz
Can GAMBLR be set up to automatically install from this fork?

I believe this can be done by adding the following lines to GAMBLR DESCRIPTION:
Remotes:
github::morinlab/g3viz
And then just add g3viz under Imports: section.
I am doing some testing...


Terminal goes black with no reason :(

VS Code Version:

Version: 1.53.2
Commit: 622cb03f7e070a9670c94bae1a45d78d7181fbd4
Date: 2021-02-11T11:48:44.518Z
Electron: 11.2.1
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.4.0-7642-generic

OS Version: Ubuntu 20.04 (Pop!_OS 20.04 LTS)

Steps to Reproduce:

Open VSCode, and open a terminal
Ramdonly face the bug :S

Does this issue occur when all extensions are disabled?: Yes

It looks like your report is missing some important information, See this wiki page for more info on how to report actionable terminal issues.
/label "needs more info" integrated-terminal

It happens randomly, this time I switched my view to Slack and when I come back, here it is, the dark terminals problem :(

This happens to me as well. I face this problem whenever I logged out for a night and get back.

duplicate #69665


Helm Installation Failed for Kong with "i/o timeout" Error

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
when I do
helm install kong kong/kong --namespace dev-backend -f values.yaml --timeout 10m
I got
Error: INSTALLATION FAILED: Get "https://github.com/Kong/charts/releases/download/kong-2.42.0/kong-2.42.0.tgz": dial tcp: lookup github.com on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:50228-><IP_ADDRESS>:53: i/o timeout
Expected Behavior
I am expecting it to start kong sucessfully.
Steps To Reproduce
Steps Followed:
1. Create the values.yaml for Kong Configuration: You prepared a values.yaml file for installing Kong in DB-less mode, which would specify the necessary configurations for the Kong gateway.
my values.yaml include

# values.yaml for Kong installation in DB-less mode

dbmode: off  # DB-less mode
image:
  repository: kong
  tag: "3.4"  # Adjust the version as necessary

ingressController:
  enabled: true
  installCRDs: false  # CRDs are already installed

proxy:
  type: ClusterIP
  http:
    enabled: true
    servicePort: 8000
  tls:
    enabled: false

admin:
  enabled: true
  http:
    enabled: true
    servicePort: 8001
  tls:
    enabled: false

env:
  database: "off"  # Disable database, enable DB-less mode
  declarative_config: "/var/kong/kong.yml"

replicaCount: 1

2. Created a kong.yml file for request forwarding

my file content is as below

# kong.yml for DB-less configuration

_format_version: "3.0"
services:
  - name: nodejs-demo
    url: http://nodejs-demo-service.dev-backend.svc.cluster.local:3000  # Node.js service in Kubernetes
    routes:
      - name: nodejs-demo-route
        paths:
          - /nodejs-demo  # Route path to match

Kong Ingress Controller version
No response
Kubernetes version
Client Version: v1.30.5+k3s1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.5+k3s1

Anything else?
I'm encountering an issue while trying to install Kong using Helm. The installation fails with the following error:
Error: INSTALLATION FAILED: Get "https://github.com/Kong/charts/releases/download/kong-2.42.0/kong-2.42.0.tgz": dial tcp: lookup github.com on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:50228-><IP_ADDRESS>:53: i/o timeout

Hi @sahilinfoviz 👋
This looks like a network issue on your side. You can try accessing the .tgz file that helm complains about in https://github.com/Kong/charts/releases/tag/kong-2.42.0. It is available and I can confirm it works on my end.
You can also retry to check if this was fixed on your end. There's nothing we can do on our side to fix / change this.
Hope this clears things up.


fix prop names and React names

Trying to help and speed up this feature

Change jsonFormat -> compatibilityJSON
react-i18next.d.ts -> i18next.d.ts

Hi @pedrodurek ! For this change you want to change the index.d.ts main file or create a ts4.1 folder and add to package.json ?


Output extra "invalid argument" but can get the right result

When I run the following line in  lib\faster_rcnn\train.py:
rpn_loss_cls_value, rpn_loss_box_value,loss_cls_value, loss_box_value, _ = sess.run([rpn_cross_entropy, rpn_loss_box, cross_entropy, loss_box, train_op], feed_dict=feed_dict, options=run_options, run_metadata=run_metadata)
the program does not report error but outputs "invalid argument" for 8 times, like this

Does someone know how to get rid of these "invalid argument"? Thanks!

Well as long as it still works?... I don't have this, so it must be something you changed? Did you add a weird thing to your bash script?


lxqt.lxqt-config: fix path of base.lst from xkeyboard-config

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/issues/150390
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Now it should be possible to add new keyboard layouts:

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/669

@ofborg eval

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 152345 run on x86_64-linux 1

1 package built:

lxqt.lxqt-config


[Dex lives Issue]

when using a pokemon's live dex it uses 2 instead of 1 and if it only has 1 left it just deletes the dex live (uses 1 dex as usual when catching the legendary) i
To Reproduce
Steps to reproduce the behavior:
1)have Pokemon with Dex lives
2)Pokegift or trade other person
3)should normally take 1 Dex lives but often takes 2
if it has 1 life left the life will disapear and it wont count for dex
Kung_Fu_Hustler
tried on atlas and titan double dexed on both
techniclauncher_2024-01-16.log
for some reason it doesn't always take 2 and even sometimes gains 1 randomly

Username: Temperestre
Server: Atlas
I traded pokemon with 1 dexlife left in the trade machine with Mitchkiller10 just now. My Enamorus lost its last life and Mitch did not get a dex entry. Mitch's zekrom was at 1 dex life left, then I did not get a dex entry for Zekrom.
No dex entry for Zekrom:
https://cdn.discordapp.com/attachments/1197439824970403961/1197440518074945566/image.png?ex=65bb4662&is=65a8d162&hm=2816dbbccffde9c613bc77064a67cc042c7dc5152bb04d34e9f2b50db8c15a39&
latest.log

I just tried this on live with a Chimecho via trade machine at 1 dexlife and reproduced it, forwarded it to our internal tracker.  Thanks for report!


list var

how to add 3 , 4 list var name ?

First zip lists 1 and 2
Then zip the result with 3
Then zip again the result with 4


fix: Fix the bug that the timeout will not be cleared when the compon…

…ent 'AddProgress' onFinished triggered
Owner

[ ] Nickname(Tuya): 钟离
[ ] Intra-group review（组内审阅人员）：无

Description
Fix the bug that the timeout will not be cleared when the component 'AddProgress' onFinished triggered.
Package
Please select the relevant package.

[ ] tuya-panel-animation-sdk
[ ] tuya-panel-api
[ ] tuya-panel-electrician-sdk
[ ] tuya-panel-ipc-sdk
[ ] tuya-panel-lamp-sdk
[ ] tuya-panel-lock-sdk
[ ] tuya-panel-robot-sdk
[ ] tuya-panel-outdoor-sdk
[x] tuya-panel-gateway-sdk

Type of change
Please select the relevant option.

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

Self CheckList
Please check all options.

[ ] Intra-group review
[x] ESLint lint
[x] Example Run
[x] Jest Run
[x] No Grammer Error
[x] No Spell Error
[x] No Merge Conflict

Codecov Report

Merging #162 (72ef19f) into main (9629786) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #162      +/-   ##
==========================================
- Coverage   62.60%   62.59%   -0.01%
==========================================
  Files         299      299
  Lines       11437    11437
  Branches     2597     2597
==========================================
- Hits         7160     7159       -1
- Misses       4260     4261       +1
  Partials       17       17

Impacted Files
Coverage Δ

...l-gateway-sdk/src/components/addProgress/index.tsx
48.07% <0.00%> (ø)

...outdoor-sdk/src/components/calendar-list/index.tsx
95.37% <0.00%> (-0.93%)
:arrow_down:

Continue to review full report at Codecov.

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


1.0.0-rc.3 compatibility

This is intended to add compatibility in for JSON API 1.0.0-rc.3 and close #27.
This pull request is not yet complete, but comments and code review is highly encouraged at any time.

Some parts of the project's documentation still refers to broken links and outdated information of jsonapi. (See #36)


Chromium (Aura) context menus do not hold window focus.

Steps to reproduce:

Open Chromium or Vivaldi and position another window to the right of it as in:

==================================================
|                       |                        |
|   chromium            |                        |
|                       |                        |
|                       |                        |
|                       |                        |
|                       |                        |
==================================================

Near the right side of the chromium window, right click to open a context menu. Move your mouse cursor to position A

==================================================
|                       |                        |
|   chromium            |                        |
|                   ----------                   |
|                   |      A |                   |
|                   |        |                   |
|                   ----------                   |
==================================================

Upon leaving the boundry of the Chromium window, the other window takes focus (even though the mouse is over the context menu), and the context menu is closed.
Expected behavior:
The chromium window retains focus as long as the context menu of the Chromium window is being hovered.
Log:
https://gist.github.com/Zach-Button/49cc069f56d96043ca076abb51391055
Version 0.13-rc1-37-gfd47a30

Does disabling "focus on mouse over" fix your issue?

The issue only occurs with focus on mouse over, because the issue occurs when the other window is focused.
So the issue is related to "focus on mouse over" specifically.

Issue updated with log and version.

I'm closing issues that are resolved by the yet-unreleased sway 1.0.


Documentation builder: fix relative paths for source code examples

This pull request adjusts the relative paths for the source code examples in the User guide so that they are properly included in the resulting html. See https://github.com/libuv/libuv/issues/1427

Sorry, I should have thought more carefully about the relative paths. There is still one warning during the build, a reference to an undefined label, but addressing that would require a change to the content of the guide, which I am not at this point qualified to make.
/home/anticrisis/dev/libuv/docs/src/guide/utilities.rst:191: WARNING: undefined label: libuv-work-queue (if the link has no caption the label must precede a section header)

No worries, thanks! I left one last comment. While you are at it, can you please squash your commits and make the commit log conform to the guidelines in CONTRIBUTING.md? Thanks!

Ok, corrected the last reference to 'libuv' in relative paths, and I hope I did the squash thing right. Using --force on any command always makes me nervous.

@anticrisis Yep, you got it right, thanks!

Landed in cf38297b, thanks!
I see this is your first libuv contribution, welcome aboard! 🚢


Added option to change prefix in config

The prefix needs to be changed in the DMSystem aswell as HauntSystem. Lines 62 and 49 respectively

dang it

sec

there


Does not work on Arch Linux (2)

I am using Parabola GNU/Linux-libre which is based on Arch Linux and I have the same issue as in #32.
I have set RUST_BACKTRACE=1, here is the result: https://termbin.com/51qp
On https://demo.yubico.com/playground, if I enable Passwordless, it does not crash, nor work.

RUST_BACKTRACE=full http://termbin.com/6cxk

Thanks for the report. I think there are a couple different issues here.
First, this program currently requires desktop notification support compatible with libnotify. You should be able to test you have such support with the notify-send program. I don't know your particular distro but the following wiki page from Arch may be useful: https://wiki.archlinux.org/index.php/Desktop_notifications
Second, this program does  not support passwordless login. That is part of the new Webauthn specification that was not finalized when I wrote this program. It should work as a normal security key on the playground (together with a password).

Also those logs seem to be debug logs which include raw payload data representing a U2F challenge (Logs from a release build would not include that data). While that should not reveal your secret keys, I would not recommend posting such data on the internet. Probably I should just remove those log statements entirely at this point.

It works!

Nice! I'm glad it's working for you. For my reference, were you just missing a notification server? Would be good to know what kind of dependencies to list if I ever get around to packaging this for Arch.

Looks like yes.


COVID-19 support

I lot of people have been impacted by COVID-19. Since this issue tracker has quite a few eyes on it, I thought it'd be another way to ask for help/support for those effected by the pandemic. If you have lost your job as a result of the pandemic or are working on a project related to the pandemic response, please feel free to add a comment below to ask for help.
Please only add requests that are related to web mapping/geo in some way, because that's relevant to our audience. There will be better places to ask for help for other areas. I obviously don't know if this will have any real impact, but I thought if it helped spread your message to a few more people, or helped one person that's probably worth it.
To start the thread off I noticed that the Humanitarian OpenStreetMap Team has a post suggesting ways to help out https://www.hotosm.org/updates/mapping-in-the-times-of-covid-19-and-how-you-can-help/

Thanks for this initiative, we have taken some time to setup this project https://github.com/kalisio/covid-19 during the outbreak in order to aggregate and map data related to COVID-19, it's specific to France however.
Good luck to all "mappers" in times of uncertainty !

Is anyone looking for remote work? I need to hire someone to integrate Maputnik into a commercial SaaS product as TomTom has done. The hosting app is a fork of https://github.com/ant-design/ant-design-pro plus Apollo Client for API communications.
Please reach out to RobertClaypool on Twitter or email<EMAIL_ADDRESS>

Trimble MAPS has released a free progressive web app to alert truck drivers to closures of truck services and allow for them to report back any closures they find themselves. This was built using our own vector maps platform.
http://covid19.trimblemaps.com
https://blog.maps.trimble.com/map-intelligence-to-support-the-transportation-community
https://developer.trimblemaps.com


Curious about --headless implementation

It's super fun project! Great job!
For fun, I was trying to run chrome in background using "--headless" option in session.py. When I ran it, I got the following error:
The resource https://tinder.com/static/build/fonts/0d4ec08dc6b105c09ea2f98b104ee5be.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate as value and it is preloaded intentionally.
I suppose it's not possible because chrome needs to display images, and in headless mode, the preloaded content isn't utilized. Any thoughts on whether if this issue can be fixed to allow running in background?

Hey @arvindsr7 ,
I'm glad you liked it so far. :)
Instinctively I'd think it wouldn't work headless, but I haven't tried it yet to be honest.
I'll definitely try and take a look at it, but I wouldn't get too high hopes about it.
Have a nice day,
Fred

Headless seems to work for me on latest version with Python 3.9.6, if that's helpful

Great! I'll close this issue then. Thanks for the update! :)


API to serve fragments and fragments with sugar

Expose API to generate fragments and fragments with sugar for a given set of smiles

I will temporarily close this and will reopen it if we receive further clarification later.


su: race while checking for incorrect password

When running with a heavily loaded box:
#!/bin/bash -ex

PROCS=$(grep -c ^processor /proc/cpuinfo)
NPROCS=$(( $PROCS * 6 ))

for i in `seq 1 $NPROCS` ; do
    python -c 'while 1: pass' &
    pids="$pids $!"
done

echo $pids
trap "kill $pids" EXIT
sleep 86400

mitogen.su can fail to spot an incorrect password prompt, because su calls write() twice, once to write "su: ", and again to write "incorrect password". It is possible for su to be preempted between writes and for su.py to observe the partial buffer.
^[[0;34m[pid 29881] 19:47:30.344160 D mitogen.ctx.ssh.localhost:2203: mitogen.su: mitogen.su.Stream(u'local.474'): received '\n'^[[0m
^[[0;34m[pid 29881] 19:47:35.858508 D mitogen.ctx.ssh.localhost:2202: mitogen.su: mitogen.su.Stream(u'local.2517'): received 'su: '^[[0m
^[[0;34m[pid 29881] 19:47:35.860656 D mitogen.ctx.ssh.localhost:2201: mitogen.su: mitogen.su.Stream(u'local.496'): received 'su: Authentication failure\n'^[[0m
^[[0;34m[pid 29881] 19:47:35.860912 D mitogen.ctx.ssh.localhost:2201: mitogen: mitogen.su.Stream(u'local.496'): child process still alive, sending SIGTERM^[[0m
^[[0;34m[pid 29881] 19:47:35.861723 D mitogen.ctx.ssh.localhost:2202: mitogen.su: mitogen.su.Stream(u'local.2517'): received 'incorrect password\n'^[[0m
^[[0;34m[pid 29881] 19:47:35.861997 D mitogen.ctx.ssh.localhost:2202: mitogen: mitogen.su.Stream(u'local.2517'): child process exit status was 32000^[[0m
^[[0;34m[pid 2770] 19:47:35.863444 D mitogen: mitogen.core.Stream(u'unix_listener.29881').on_disconnect()^[[0m
^[[0;34m[pid 2774] 19:47:35.863463 D mitogen: mitogen.core.Stream(u'unix_listener.29881').on_disconnect()^[[0m
^[[0;34m[pid 2774] 19:47:35.863985 D mitogen: Waker(Broker(0x7f2f0b32d190) rfd=19, wfd=20).on_disconnect()^[[0m
^[[0;34m[pid 29881] 19:47:35.864297 D mitogen: mitogen.core.Stream(u'unix_client.2774').on_disconnect()^[[0m
^[[0;34m[pid 29881] 19:47:35.864974 D mitogen: mitogen.core.Stream(u'unix_client.2770').on_disconnect()^[[0m
^[[0;34m[pid 2770] 19:47:35.864044 D mitogen: Waker(Broker(0x7f2f0ae854d0) rfd=19, wfd=20).on_disconnect()^[[0m
^[[0;31mfatal: /home/dmw/src/mitogen/tests/ansible/integration/become/su_password.yml:28: [target-centos6]: FAILED! => {^[[0m
^[[0;31m  msg: error occurred on host target-centos6: EOF on stream; last 300 bytes received: u'Password: \nsu: incorrect password\n'^[[0m

Fixed as part of #419


test-branch/execute-job/quoted-authorization/9f59890d-9066-4646-a8fd-d9fbef946e2d

PR for testing e38402c68810348202480d5a2460f29af03a6c09

/canonical/self-hosted-runners/run-workflows e38402c68810348202480d5a2460f29af03a6c09


Render lilypond32a (fermatas)

This PR renders fermatas, which is part of lilypond32a.
lilypond

vexml

Beat me to it — I was going to file a bug for this :)
I didn't see the corresponding articulation in vexflow tables nor the vexflow tests.
Next, I rendered lilypond32a in OSMD and saw that it's not supported there either. I came to the conclusion that it's not supported in vexflow.

@rvilarl, I filed an issue for the angled and square fermatas at https://github.com/0xfe/vexflow/issues/1608.

@jaredjj3 I am pretty sure that they are supported im Vexflow 5 I will look into that

@jaredjj3 they are there :) The fermataShortAbove/Below are the angled ones and the fermataLongAbove/Below is the squared ones.

I accidentally pushed directly to master, but I fixed it now. Thanks for your help @rvilarl!


Unify Either.bimap(Function,Funtion) vs. Functor2.map(Function, Function)

(Functor2 will be there soon)
We should use map instead of bimap.

Naming :-/
Scalaz
trait Bifunctor[F[_, _]] {
  def bimap[A, B, C, D](k: F[A, B], f: A => C, g: B => D): F[C, D]
}

object Bifunctor {
  import Scalaz._

  implicit def Tuple2Bifunctor: Bifunctor[Tuple2] = new Bifunctor[Tuple2] {
    def bimap[A, B, C, D](k: (A, B), f: A => C, g: B => D) =
      (f(k._1), g(k._2))
  }

  implicit def EitherBifunctor: Bifunctor[Either] = new Bifunctor[Either] {
    def bimap[A, B, C, D](k: Either[A, B], f: A => C, g: B => D) =
      k match {
        case Left(a) => Left(f(a))
        case Right(b) => Right(g(b))
      }
  }

  implicit def ValidationBifunctor: Bifunctor[Validation] = new Bifunctor[Validation] {
    def bimap[A, B, C, D](k: Validation[A, B], f: A => C, g: B => D) =
      k match {
        case Failure(a) => failure(f(a))
        case Success(b) => success(g(b))
      }
  }

  import java.util.Map.Entry
  import java.util.AbstractMap.SimpleImmutableEntry

  implicit def MapEntryBifunctor: Bifunctor[Entry] = new Bifunctor[Entry] {
    def bimap[A, B, C, D](k: Entry[A, B], f: A => C, g: B => D) = new SimpleImmutableEntry(f(k.getKey), g(k.getValue))
  }
}

I think we should stick with Functor2 in Javaslang. That goes along with Tuple and Function naming.
To reduce complexity, we should completely remove the (only on my local branch existing) method Functor2.map2(Function<Tuple2,Tuple2>).
It remains the question, how we should name the the Functor2 methods:
<U1, U2> Functor2<U1, U2> map(BiFunction<? super T1, ? super T2, ? extends Tuple2<? extends U1, ? extends U2>> f);

<U1, U2> Functor2<U1, U2> map(Function<? super T1, ? extends U1> f1, Function<? super T2, ? extends U2> f2);

I'm not a big fan of naming these methods map2 or bimap instead. The latter does not scale very well when map methods with more arguments are needed. The former is not consistent with many other functions in Javaslang, e.g. Function.of, Function.lift, Monad.lift, Validation.combine etc. These would need a cardinality number, too.
The only argument against naming the methods Functor2.map is raising ambiguities. But we know that only one of the Functor, Functor2 resp. Monad, Monad2 interfaces is implemented. Therefore we will name the methods just map.

Mmhh, or maybe Functor2.bimap because we will not have Functor, Monad etc. with cardinality > 2.

The right-biased Either<L, R> may implement Functor and Functor2 as well. If Functor2 has bimap instead of map it would clarify mapping behavior.

Not sure if we need
interface Monad2<M extends Kind2<M, ?, ?>, T1, T2> extends Kind2<M, T1, T2>, Functor2<T1, T2>

final class HashMap<K, V> implements Map<K, V>, Monad2<HashMap<?, ?>, K, V>

It should be instead
interface Monad<M extends Kind<M, T>, T extends Tuple> extends Kind<M, T>, Functor<T>

final class HashMap<K, V> implements Map<K, V>, Monad1<HashMap<?, ?>, Tuple2<K, V>>, Functor2<K, V>

If we need no Monad2, then I will rename Functor2 to BiFunctor. The cardinalities are not related to each other, i.e. a Monad is a Functor but also can be a BiFunctor.

See also #1018

We need Monad2 because we need a different Kind of flatMapM than Monad has. Otherwise we would loose the component types of the result.
public interface Monad2<M extends Kind2<M, ?, ?>, T1, T2> extends Kind2<M, T1, T2>, Functor2<T1, T2> {
    <U1, U2> Monad2<M, U1, U2> flatMapM(BiFunction<? super T1, ? super T2, ? extends Kind2<? extends M, ? extends U1, ? extends U2>> mapper);

    <U1, U2> Monad2<M, U1, U2> flatMapM(Function<? super Tuple2<? super T1, ? super T2>, ? extends Kind2<? extends M, ? extends U1, ? extends U2>> mapper);
}

Compared to Monad:
public interface Monad<M extends Kind<M, ?>, T> extends Kind<M, T>, Functor<T> {
    <U> Monad<M, U> flatMapM(Function<? super T, ? extends Kind<? extends M, ? extends U>> mapper);
}

Given that we will stay with Functor2.map methods instead of bimap, otherwise (some) implementing classes would have no map method which would be confusing because there are flatMap methods.

Convention:

map takes one argument, e.g. map(Function<T, R>) or map(BiFunction<T1, T2, R>)
bimap takes two arguments, e.g. bimap(Function<T1, R1>, Function<T2, R2>)

Given this we are consistent with Either and Validation.


Address warnings in printf.c

Hello, my compiler identified a few warnings that are easy to fix.

Didn't mean to include the catch update here - just needed that to add the tests to my CI server :)
For clang version:
clang version 6.0.1 (tags/RELEASE_601/final)
Target: x86_64-apple-darwin17.7.0

I generally turn on all warnings, so you may not see this with default levels.
Regarding uintptr_t trick: Didn't think about older C99 compiler support. I'll have to look into other warning suppressant methods. uintptr_t is used because it can safely store a pointer without truncation.


Option for pure JavaScript mode in new and existing projects?

Describe the feature
Hello Nuxt team,
I appreciate the powerful features and flexibility Nuxt provides. However, I've encountered a challenge when trying to use Nuxt with pure JavaScript, both for new projects and when integrating Nuxt into existing Vue.js projects.
Current situation:

When initializing a new project with pnpm dlx nuxi@latest init <project-name>, all generated files are in TypeScript.
There's no clear option to choose a pure JavaScript setup during project initialization.
Integrating Nuxt into existing Vue.js projects that use JavaScript (not TypeScript) is challenging.

Feature request:

Add an option during project initialization to choose between TypeScript and JavaScript setups.
Provide a clear guide or command to convert an existing Nuxt TypeScript project to pure JavaScript.
Offer documentation on how to integrate Nuxt into existing JavaScript-based Vue.js projects without requiring a full migration to TypeScript.

Thank you
Additional information

[ ] Would you be willing to help implement this feature?
[ ] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

Hey @gowy222 👋🏻
If you rename everything from .ts to .js and remove the tsconfig + types in each file, you can use Nuxt with pure JavaScript easily ☺


After upgrade to Angular 5.2.5, unwanted behavior occurs when calling setActiveAndVisible with async data

After upgrade to Angular 5.2.5, unwanted behavior occurs when calling setActiveAndVisible with async data (getChildren - http promise). All good when the tree initiate and I can expand down the tree. But when I replace the tree nodes and call setActiveAndVisible. It trigger "getChildren" on every level down. Before  Angular 5.2.5 this was not happening, please help?
angular: 5.2.5
angular/cli: 1.7.0
angular-tree-component: 7.0.1

Can you reproduce in the plunkr (from the issue template)? Thanks

Same for me! Any update on this?

Have you tried with latest version 7.1.0?
@zbeedatm @jesben can you please reproduce in Plunkr from issue template?

Its working fine with this version.
Thanks.
If I use it within a selected TreeNode from the tree itself it's working (didn't in old beta version).
But, I'm trying to do something else in my app... I'm building a file manager, and for that purpose I display in a left panel the tree and in a right panel children of selected node from the left.
When double click on a node from right panel I want to set it as active and visible in the tree, and that is not working for me.
The reason in my opinion is that when searching for that node in the tree it can't find it. I build an array of TreeNode to be displayed in the left programmaticlly and it's not the same as it appears in the tree probably.
this.tree.treeModel.setFocusedNode(node);   this.tree.treeModel.getFocusedNode().setActiveAndVisible();
I tried to search for it in the tree by using findBy / findByPath but didn't manage.

Closing this issue due to inactivity. Please open a new issue if the problem still exists.


Change draw_bounding_box() label input to allow different number of inter-batch boxes.

This is a question or feature request regarding the following function
tf.image.draw_bounding_boxes(images, boxes, name=None)
Current
The required bounding-box format is as follows:
[batch, num_bounding_boxes, 4], in which the labels are in [y_min, x_min, y_max, x_max] format.
If i understand correctly, this assumes that every image has the same number of bounding boxes.
Suggestion
Doesn't it make a lot more sense to change the input format to the following:
[num_labels, 5] in the following format [id, y_min, x_min, y_max, x_max] where id corresponds to the image in the batch.

@danmane, please consider this feature request.

Can we add also color and text to the interface?

I don't own the tf.image module and don't intend to work on this. Going to mark it contributions welcome.

@TimZaman, I believe it is this way so that ops can be created to produce tensors in a deterministic way. If a bounding box is unused it can be given dummy values. Most ops in TensorFlow work better with direct indexable dense formats rather than the id-based sparse format you suggest. So I am closing for now.


POC DataTable Bar align

Do not merge
Idea for https://github.com/evidence-dev/evidence/issues/2725
https://deploy-preview-2726--next-docs-evidence.netlify.app/components/data-table/#bar-chart-column---right-aligned

I worry about this implementation. I think this could be unexpected.

I think a better approach might be barAlign=right