Interest in inverse hessian-vector multiplication?

I figured out how to do a relatively fast (on the order of the inversion of the gradient finding step [the backpropagation or reverse mode autodiff or whatever] as opposed to the naive order of the gradient finding step ^ 2) version of it it a few months ago (documented here, here and here) and I was wondering if you folks would want it in your project. The basic outline of the method is to use the inverse function theorem, realize the hessian is a jacobian, and then go through the rest with the Pearlmutter hessian-vector multiplication. The impact would be facilitating straightforward relatively fast Newton's method stuff. The gradient function has to be practically invertible, which is weird.
I got a job after writing all that so it'll probably take me a pretty solid (3-4 months) amount of time on the weekends to actually execute. The way to do it would be basically analogous to the hessian-vector product you have in there already, just inversed, it's just that I don't understand much of the other code and it would be the usual month or so getting familiarized, etc etc. So instead of spending that time upfront I was just wondering if the maintainers were interested at all in the first place, or maybe I could do a small demo instead using autograd or something.

The gradient function has to be practically invertible

This is a non-trivial limitation, is it not?

It very much is a nontrivial limitation, yes.


qr_R induces a segmentation fault

Description:
Running qr_R on the included example induces a segmentation fault in CmdStan.
Reproducible Steps:
fail_example.zip
> ./fail_example sample data file=fail_example.data.R

Current Output:
Segmentation fault: 11

Expected Output:
Should run without seg faulting.
Current Version:
develop

I have found the bug. The question becomes do we want qr_Q and qr_R to return the "thin" QR factors or do we want them to return the "fat" QR factors with the segfault averted. Doing the "thin" one is kind of what I had in mind (hence the segfault) but would be a backward incompatible change to the current (broken) behavior.

I would support either — or even both.  Either way the doc
just needs to make it clear which is being applied and the
dimensions of the returned objects (which is missing from
the current doc).
On Apr 22, 2016, at 7:35 PM, bgoodri<EMAIL_ADDRESS>wrote:

I have found the bug. The question becomes do we want qr_Q and qr_R to return the "thin" QR factors or do we want them to return the "fat" QR factors with the segfault averted. Doing the "thin" one is kind of what I had in mind (hence the segfault) but would be a backward incompatible change to the current (broken) behavior.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

In the interest of getting this into 2.10, I think we should leave it as fat until 3.0. If someone is only using qr_Q currently, then it is fat but not broken.

It's OK to deprecate or even remove broken functions, but
whatever we do, they can't segfault.  That brings down the
R and Python process with it!
When you say the current behavior is broken, you just mean
for some inputs, or is it totally useless?  If the former,
can we detect the cases that would segfault before they do
and throw an exception instead?  If the latter, we should just
eliminate the function.

Bob

On Apr 22, 2016, at 2:35 PM, bgoodri<EMAIL_ADDRESS>wrote:
I have found the bug. The question becomes do we want qr_Q and qr_R to return the "thin" QR factors or do we want them to return the "fat" QR factors with the segfault averted. Doing the "thin" one is kind of what I had in mind (hence the segfault) but would be a backward incompatible change to the current (broken) behavior.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

The segfault is readily fixable; it is just a question of whether to do so
by breaking code that was using it without segfaulting. But we can wait for
3.0 to do that. Someone just needs to merge
https://github.com/stan-dev/math/pull/289

I

On Apr 23, 2016, at 6:04 PM, bgoodri<EMAIL_ADDRESS>wrote:
The segfault is readily fixable; it is just a question of whether to do so
by breaking code that was using it without segfaulting.

I wouldn't say that's a "fix", so much as a "change".  But see below.

But we can wait for
3.0 to do that. Someone just needs to merge
https://github.com/stan-dev/math/pull/289

I'm very confused.  This pull request says it
"Fix segfault when qr_R is called on a non-square matrix"
It doesn't mention breaking anything as a side effect.
So I don't see what's left to do for 3.0.

Bob

On Sun, Apr 24, 2016 at 2:32 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:

It doesn't mention breaking anything as a side effect.
So I don't see what's left to do for 3.0.

The PR doesn't break anything. For 3.0 we might consider a
backwards-incompatible change of returning the factors of the "thin" QR
decomposition of A where Q has the same dimensions as A and R is square. In
the current "fat" QR decomposition of A, Q is square and R has the same
dimensions as A.


Support array values for answer collector keys

I'm working on a project where I want to be able to keep a loop going, getting feedback from users and storing them all in the result returned from an AnswerCollector. This PR allows collector consumers to receive multiple values from key-ed prompts if the key name is shared.
I feel like there is value in this being optional - where the default behavior would be to override the value of a key if it appears multiple times - but couldn't figure out a clean way to implement an additional option to the key method; was thinking something like:
def key(name, multi: false, &block)
  @name = name
  @multi = multi
  # ...
end

ready for another peek @piotrmurach. I'm not really sure what to do about the coverage drop 😕 . I also tweaked the key and values methods to avoid using explicit block params. I have not problem reverting this back if you're not okay with it, I just wanted to keep the values method's signature as simple as possible.

Hi Danny,
Thanks for persisting with this! I'm happy with how it looks and behaves. Since you're making me review this during my current travel in India, as a punishment I will ask you to add some docs in readme explaining this feature 😛  After that I will defo merge!

Thanks! ❤


Update Readme.md

The title of the readme matches the npm module name, since this is a npm module.


Default tab style looks broken

The image shows the problem.

I'm using the nerd-fonts-jetbrains-mono font from the Arch User Repository, this same problem occurs in VTE based terminals, as well as in alacritty and konsole.
Using ttf-nerd-fonts-symbols from the Arch repos shows a similar problem with the glyphs:

Using other nerd font patched fonts like hack shows yet the same problem.

Alacritty config

And here's the current font setting for tilix (current VTE terminal I'm using, confirmed to be broken even with other terminals):

No point in showing you different font selections in a screenshot, in both alacritty and tilix I tried:

JetBrains Mono + ttf-nerd-fonts-symbols
JetBrains Mono NL (no ligatures) + ttf-nerd-fonts-symbols
JetBrains Mono patched for nerdfonts and this other variant as well

I have the same issue with the following iterm config.

For now,  I know the answers
@GabMus  You should use the matching need font, not a different font; for example, JetBrains Mono should use JetBrains Mono NerdFont, not ttf-nerd-fonts-symbols.
@chananababa In iTerm2，should use the Hack Nerd Font Mono


安装出现问题

Provide a description of requested docs changes

An error occurred while attempting to create the directory:
D:\Documents\PowerShell

Can you try the latest version? https://github.com/microsoft/PowerToys/releases/tag/v0.80.1
/needinfo


Multiple errors as kernel doesnt support some modules

Please fix this. Im trying to set up a cluster on scaleway but this is holding me back:
Setting up scylla-kernel-conf (1.2.1-20160623.c56fc99-ubuntu1) ...
sysctl: cannot stat /proc/sys/kernel/sched_tunable_scaling: No such file or directory
sysctl: cannot stat /proc/sys/kernel/sched_min_granularity_ns: No such file or directory
sysctl: cannot stat /proc/sys/kernel/sched_wakeup_granularity_ns: No such file or directory
sysctl: cannot stat /proc/sys/kernel/sched_latency_ns: No such file or directory
sysctl: cannot stat /proc/sys/kernel/sched_autogroup_enabled: No such file or directory
dpkg: error processing package scylla-kernel-conf (--configure):
subprocess installed post-installation script returned error exit status 255
dpkg: dependency problems prevent configuration of scylla:
scylla depends on scylla-kernel-conf; however:
Package scylla-kernel-conf is not configured yet.
dpkg: error processing package scylla (--configure):
This is for scylladb
Im running Ubuntu 14.0.4
Linux scw-b4 4.5.7-std-2
Thanks

Hi any news?

Hi @scorpnode,
The last week, I did not find the options to enable
sysctl: cannot stat /proc/sys/kernel/sched_min_granularity_ns: No such file or directory
sysctl: cannot stat /proc/sys/kernel/sched_wakeup_granularity_ns: No such file or directory
sysctl: cannot stat /proc/sys/kernel/sched_latency_ns: No such file or directory

@aimxhaisse, any idea about this ?

https://doc.opensuse.org/documentation/html/openSUSE_121/opensuse-tuning/cha.tuning.taskscheduler.html

https://en.wikipedia.org/wiki/Completely_Fair_Scheduler i think

Just following up on this

Hi @scorpnode
For now we can't use the CFS on our kernel because it turn all modules in static

Scheduler tunables section
http://www.scylladb.com/2016/06/10/read-latency-and-scylla-jmx-process/

We can't use the CFS scheduler.

seeing the same issue currently.

got it to work on scaleway c2s but should work on every X86 64bit machine.
apparently scylla-kernel-conf fails due to the scaleway's own kernel. Some settings can't be set. However, you can install the package manually and skip the postinstallation script of the package. Since these settings can not be altered anyway this should be safe to do.
apt-get download scylla-kernel-conf
sudo dpkg --unpack scylla-kernel-conf*.deb
sudo rm /var/lib/dpkg/info/scylla-kernel-conf.postinst -f
sudo dpkg --configure scylla-kernel-conf
sudo apt-get install -yf #To fix dependencies

from https://askubuntu.com/questions/482928/ignore-apt-get-postinstall-scripts-automatically
worked for me. Runnning scylla cluster on several c2 machines now (testing env).


Sorry, the response was filtered by the Responsible AI Service. Please rephrase your prompt and try again. Learn more.

Since this is not resolved and there does not seem to be a follow-up on this case, I will open it as many times as necessary.

Copilot Chat Extension Version: v0.21.2024090602 (pre-release)
VS Code Version: 1.93
OS Version: w11
Logs:

Steps to Reproduce:

copy the shadcn ui.shadcn.com/blocks#dashboard-03
use the SDK AI from vercel as common
in vscode chat copilot "@workspace #file:page.tsx  #file:route.ts" route.ts is part of api/chat example and page is the shadcn block
write "@workspace #file:page.tsx  #file:route.ts make the form works and send the model,temperature,top, role, content"

and get the message
Sorry, the response was filtered by the Responsible AI Service. Please rephrase your prompt and try again. [Learn more]
I hope this will be resolved this week, should be your top priority.

OK, just use the example block of shadcn dashboard03, and write that you want to validate the form with zod.
And you get "Sorry, the response was filtered by the Responsible AI Service. Please rephrase your prompt and try again".
I don't have logs

This is rubbish - I am getting this error almost every time I ask for a suggestion for HTML/CSS - I can see the answer as it is being generated but as soon as it finishes it removes it and displays the error...

Thanks for creating this issue! We figured it's covering the same as another one we already have: https://github.com/microsoft/vscode-copilot-release/issues/2625. Please refer to that one for updates and discussions. Feel free to open a new issue if you think this is a different problem.


Add support for parsing charset set in Content-Type header

In some cases, libraries add charset as part of the Content-Type header (https://www.rfc-editor.org/rfc/rfc9110.html#media.type)
The change here is to avoid failing on requests which have the entry for Content-Type: application/json; charset=utf-8 since we're currently doing an exact string look up

I'm going to need one of your help on this one 😂
I'm not confident that this is the right place we'd want the tests to be but I'm also getting an interesting invalid memory dereference :(

I agree with @timostamm - this is too lenient. We should immediately reject requests with Content-Types like application/json; content-type=shift-jis or application/proto; endianness=middle.
Can we instead use a combination of mime.ParseMediaType and mime.FormatMediaType to normalize the Content-Type in the request path? Then we can change the default configuration to register two JSON codecs: one for application/json and one for application/json; charset=utf8.

@akshayjshah Would this mean that users who want to support application/json; charset=utf-8 that they would need to register an additional handler? The client/handler params only permit for registering a single codec


Setting can not be reset.

I think you should have a reset button as other settings do.

I found that settings can not be saved .


Use checksummed addresses in RFQ config

Description
Use checksummed addresses instead of forcing strings.ToLower() usage for address comparisons.

Summary by CodeRabbit

New Features

Implemented enhanced token ID sanitization for improved security and consistency.

Bug Fixes

Corrected token ID comparison logic to ensure accurate processing of quote requests.

Refactor

Optimized token-related operations for better performance and reliability.

@trajan0x, can you take a look? this is the correct way to do it obvi.


Added the dice to the end of the observation tensor

Added the dice at the end of the observation tensor. If there is no dice, then a 0 is given. (Updated the comments of the functions to show this change too.)
I also changed the playthroughs of backgammon and hyper_backgammon to show these changes.

Seems like the tests are acting up. Give us a bit of time to fix some things, and I may ask you to merge from master once they are fixed. Thanks.

@lanctot done.


How to set up scanning of UDP ports?

UDP scanning will not be implemented. Check the other project I have: udpx


icons in sccm device view are not sortable

within the device view in sccm, you can clearly see an icon that appears to have functions. I observe the base differences to be:

It can be nothing, which means no client no data but discovered or added to sccm somehow.
client but not online
client but no discovery data
client and online

What's odd is that when you try to sort by this column, it lines up in no particular order. Odd. Either the icons mean something, and you can sort by them, or they don't.

Hi @chadparris
We already have client status documented here: https://docs.microsoft.com/sccm/core/clients/manage/monitor-clients#bkmk_indStatus
If you have concerns with the details of that article, please file feedback from that article (to properly link the article with the issue). For more information on filing doc issues, see https://docs.microsoft.com/sccm/core/understand/use-docs#bkmk_docfeedback
Otherwise, if the product currently doesn't allow sorting by that column, then that's product feedback. I want to make sure it gets directly into the hands of the engineering team. Fortunately, we've got dedicated channels for that very purpose. :) See the Product feedback section in our docs. I think it’s important that you submit it directly, because that allows you to receive notifications and more closely monitor the progress.
I'm closing this issue as there's nothing actionable for docs at this time.


MSL: Generates invalid shader code when argument buffers are enabled and trying to use bindless textures.

Im trying to use bindless textures like this in HLSL
Texture1D Texture1DTable[] : register(t12, space1);
Texture2D Texture2DTable[] : register(t13, space2);

PSOutput MainPS(PSIn ps)
{
    float3 color = Texture2DTable[0].Sample(BaseColor_Sampler, ps.TextureCoord).xyz;
    float x = Texture1DTable[VertexData.MaterialIndex].Sample(BaseColor_Sampler, ps.TextureCoord.x).x;
    ....
}

When argument buffers are disabled, it generated correct code and adds spvDescriptorArray<...> variables to properly read the data.
fragment MainPS_out MainPS(MainPS_in in [[stage_in]], constant type_PushConstant_FVertexData& VertexData [[buffer(0)]], device type_RWStructuredBuffer_FMaterial& buffer_materials [[buffer(1)]], const device spvDescriptor<texture1d<float>>* Texture1DTable_ [[buffer(12)]], const device spvDescriptor<texture2d<float>>* Texture2DTable_ [[buffer(13)]], sampler BaseColor_Sampler [[sampler(2)]])
{
    spvDescriptorArray<texture1d<float>> Texture1DTable {Texture1DTable_};
    spvDescriptorArray<texture2d<float>> Texture2DTable {Texture2DTable_};

    MainPS_out out = {};
    float4 _65 = Texture2DTable[0].sample(BaseColor_Sampler, in.in_var_TEXCOORD0);
    out.out_var_SV_Target0 = float4(_65.x + Texture1DTable[VertexData.MaterialIndex].sample(BaseColor_Sampler, in.in_var_TEXCOORD0.x).x, _65.yz, 1.0) + buffer_materials._m0[VertexData.MaterialIndex].Color;
    return out;
}

But when I enable argument buffers, everything will break.
I also need to modify the hlsl code so it genrates correct argument buffer variable binding.
So the modified hlsl code is:
Texture1D Texture1DTable[] : register(t0, space1);
Texture2D Texture2DTable[] : register(t0, space2);

now the metal shader looks like this:
...
struct spvDescriptorSetBuffer1
{
    const device spvDescriptor<texture1d<float>>* Texture1DTable [[id(0)]];
};

struct spvDescriptorSetBuffer2
{
    const device spvDescriptor<texture2d<float>>* Texture2DTable [[id(0)]];
};

fragment MainPS_out MainPS(MainPS_in in [[stage_in]], constant spvDescriptorSetBuffer0& spvDescriptorSet0 [[buffer(0)]], constant spvDescriptorSetBuffer1& spvDescriptorSet1 [[buffer(1)]], constant spvDescriptorSetBuffer2& spvDescriptorSet2 [[buffer(2)]], constant type_PushConstant_FVertexData& VertexData [[buffer(3)]])
{
    MainPS_out out = {};
    float4 _65 = spvDescriptorSet2.Texture2DTable[0].sample(spvDescriptorSet0.BaseColor_Sampler, in.in_var_TEXCOORD0);
    out.out_var_SV_Target0 = float4(_65.x + spvDescriptorSet1.Texture1DTable[VertexData.MaterialIndex].sample(spvDescriptorSet0.BaseColor_Sampler, in.in_var_TEXCOORD0.x).x, _65.yz, 1.0) + (*spvDescriptorSet0.buffer_materials)._m0[VertexData.MaterialIndex].Color;
    return out;
}

as you can see it now does not uses the helper variables and it generates an error when compiling msl
program_source:90:54: error: no member named 'sample' in 'spvDescriptor<metal::texture2d<float, metal::access::sample>>'
    float4 _65 = spvDescriptorSet2.Texture2DTable[0].sample(spvDescriptorSet0.BaseColor_Sampler, in.in_var_TEXCOORD0);

error: no member named 'sample' in 'spvDescriptor<metal::texture1d<float, metal::access::sample>>'
    out.out_var_SV_Target0 = float4(_65.x + spvDescriptorSet1.Texture1DTable[VertexData.MaterialIndex].sample(spvDescriptorSet0.BaseColor_Sampler, in.in_var_TEXCOORD0.x).x, _65.yz, 1.0) + (*spvDescriptorSet0.buffer_materials)._m0[VertexData.MaterialIndex].Color;

Yes, this is a known issue.
If a descriptor set only contains the runtime-sized descriptor array, it should work to just make that set a discrete descriptor set and you should end up with the helper struct. I'll try to figure out a way to make runtime-sized arrays work well with argument buffers.

One workaround you can do is to use the resource binding interface to force a fixed array size. E.g. this GLSL shader:
#version 450
#extension GL_EXT_nonuniform_qualifier : require
#extension GL_EXT_samplerless_texture_functions : require

layout(set = 0, binding = 0) uniform texture2D T;
layout(set = 0, binding = 1) uniform texture2D Ts[];
layout(set = 1, binding = 0) uniform texture2D T2;
layout(set = 1, binding = 1) uniform texture2D T2s[1024];

layout(location = 0) out vec4 FragColor;

void main()
{
	FragColor = texelFetch(T, ivec2(gl_FragCoord.xy), 0);
	FragColor += texelFetch(Ts[nonuniformEXT(int(gl_FragCoord.x))], ivec2(0), 0);
	FragColor += texelFetch(T2, ivec2(gl_FragCoord.xy), 0);
	FragColor += texelFetch(T2s[nonuniformEXT(int(gl_FragCoord.x))], ivec2(0), 0);
}

In your local integration:
		MSLResourceBinding binding = {};
		binding.count = 4096;
		binding.binding = 1;
		binding.desc_set = 0;
		binding.msl_texture = 1;
		binding.basetype = SPIRType::Image;
		binding.stage = spv::ExecutionModelFragment;
		msl_comp->add_msl_resource_binding(binding);

Generates this:
struct spvDescriptorSetBuffer0
{
    texture2d<float> T [[id(0)]];
    array<texture2d<float>, 4096> Ts [[id(1)]];
};

instead of:
struct spvDescriptorSetBuffer0
{
    texture2d<float> T [[id(0)]];
    const device spvDescriptor<texture2d<float>>* Ts [[id(1)]];
};

One workaround you can do is to use the resource binding interface to force a fixed array size.

FWIW...this is the mechanism that MoltenVK uses when mapping from Vulkan, based on knowledge of descriptor counts at pipeline creation time.

Alright, thank you for the info, I will meanwhile use the workaround.


[FEATURE] Add support to install ASEA on top of AWS Control Tower

The ASEA is designed to leverage as many capabilities of native AWS services or offerings as possible
It has always been planned to add an option to install the ASEA on top of Control Tower, when appropriate (i.e. service available in the Canadian region, assessed for PBMM compliance by the Canadian Cyber Center, etc.)
We are actively working with the Control Tower team to ensure our roadmaps are aligned and we have a path forward which will allow deploying the ASEA on top of Control Tower, while still allowing customers to meet the Gov't of Canada's PBMM security control requirements

NEW Installs Code Complete
TODO: SCP consolidation to fit in CT free space
TODO: Upgrade from SEA to CT+SEA (Blocked, require CT team assistance)

Waiting for this feature to be implemented.
ControlTower implementation is not quite "Production Ready" and aws-secure-environment-accelerator looks much better at least on paper.
Keen to try it when it's ready.

Specific items requiring detailed insight and/or roadmap timelines:

How should we reliably detect that Control Tower is deployed in a customer account? (Deployed/Not Deployed)
o	Further, how can we validate Control Tower Status through API (Healthy/Unhealthy)
How can we programmatically create a Control Tower managed OU?
How can we bypass the Control Tower guardrails for Accelerator deployed Control Tower augmentations?
o	Can we somehow add our roles as bypasses to your SCP's? (without sending CT into unhealthy status)
o	We will NOT modify Control Tower deployed objects as a core principal, but augment them, examples:
	we need to deploy Config recorders in non-CT regions - blocked
	we need to create and enable encryption on a new bucket in the log-archive account to centralize the all other logs not captured by CT, but it must be encrypted (s3:PutEncryptionConfiguration, s3:PutBucketLogging and s3:PutBucketPolicy) - blocked in core OU
What is the roadmap and can we prioritize CT reducing its SCP footprint? (common customer ask)
o	i.e. moving to 3 digit SID's, other consolidations in merging SCPs, even if ugly?
Status of improving CT CloudTrail support:
o	KMS CMK support? Org trail support? (ability to send to both S3 and CloudWatch Logs)
o	Plans to allow: S3 data plane logging? CT Insights?
Plans to enable Config Aggregator?
General question - any plans to apply guardrails to the root account?

Planned for next MAJOR (not minor) release i.e. v1.5

Is there any upgrade path from ASEA to ASEA+CT? What are the advantages if any?

CT baseline install Changes

Create Config Recorder Differently:

Create Config Recorder in regions where control tower is not deployed into (not CT regions)
Create Config Recorder in all supported regions in management account.
Stop Creating Config Aggregator, Control Tower is already deployed one.
Use global-options/organizationAdminRole (AWSControlTowerExecution) to createConfigRecorder

Apply Accelerator Password Policy
Deploy GuardDuty
Deploy CloudTrail (To get logs recorded in Log Archive S3 bucket)

rename global-options\aws-org-master to global-options\aws-org-management in config file (remove the word master)
add a new parameter to the above "section" named "separate-s3-dp-org-trail": true/false, optional, defaults to false,

when this parameter is set to true, create a new/second ORGANIZATION, multi-region, trail
use the settings from previous SEA trail deployment used in non-CT SEA version EXCEPT no mgmt events
i.e. send to CWL, validation, KMS CMK, our S3 bucket/path, no SNS, all accounts, all regions
log group name: /${ACCELERATOR_PREFIX_ND}/CloudTrailS3  ---> i.e. add S3 suffix
NO Mgmt events (means insights also not allowed) - Yes to DATA events, all current and future buckets, read/write
while I only expect this to be used with CT where we do not create the first trail, someone could turn this on in the non-ct version

Extend CloudWatch Metrics and Alarms to support "accounts": ["ALL"]

continue to support providing "accounts": ["management"] - for current SEA customers
add support for "ALL" to deploy to all accounts in the organization
I believe "accounts": [xxx] only supports deploying to the "management" account today
enable support for a list of named accounts i.e. "accounts": ["TheFunAccount", "Operations"]
continue to use the SNS topic in log-archive for all accounts.

Update the codebase to support all 4 account creation methods? (per CT design specs in quip)

Account(s) created via orgs, triggers SM after 2mins, SM calls Account Factory Service Catalog item for each new account, then finishes running SM
Account(s) created via SEA when SM runs because new account(s) added to config file, calls Account Factory Service Catalog item for each new account, then finishes running SM
Account created through CT Enroll account mechanism or by user directly running Account Factory Service Catalog item - we detect the account creation event, see that SC is already running, wait for it to complete, and then run SM

What does setting "ct-baseline": true flag do differently:

only deploys Config Recorders in the root account and non-ct regions in sub-accounts (as CT covers remainder)
does not create Config Aggregator in root account (as CT creates in Security account)
uses global-options/organizationAdminRole to createConfigRecorders (or blocked by CT SCPs)
Uses ServiceCatalog for account creation (CT Account Factory to properly ingest new accounts into CT)
does not create the Org Control Plane CloudTrail (as CT creates account based Control Plane Trails)

What settings need to be changed in the config file to install with Control Tower:

"organization-admin-role": "AWSControlTowerExecution" (MANDATORY)

ASEA will be blocked by CT SCPs and CT will be blocked from sub-account access

"control-tower-supported-regions": [ct regions...]   (MANDATORY)

MANDATORY - this allows for no code modifications as CT adds support for additional regions
REQUIRES full list of CT supported regions

"separate-s3-dp-org-trail": true (RECOMMENDED)

adds s3 data plane logging back like standalone ASEA deployments

metrics"accounts": ["ALL"] (NEEDED)

Control Plane trails are now distributed into all accounts, metrics must also be moved to all accounts (instead of root)

metrics\loggroup-name to "aws-controltower/CloudTrailLogs" (NEEDED)

need to target the Control Tower trail log group name

alarms"default-accounts": ["ALL"] (NEEDED)

Control Plane trails are now distributed into all accounts, alarms must also be moved to all accounts (instead of root)

Change Core OU to Security OU (for Security, Log Archive and root accounts) (RECOMMENDED)

align with AWS multi-account standards

Add Infrastructure OU (perimeter, shared network, Operations accounts) (RECOMMENDED)

align with AWS multi-account standards

Ensure all ASEA OOB account names match all CT OOB account names (MANDATORY)


(SERVER-847) jruby event callbacks

This PR introduces a function in the JRuby service protocol that allows consumers to register callback functions, to get a notification when a JRuby instance is requested, borrowed, or returned.

This replaces #658 and hopefully addresses all of the feedback from that PR.

:shipit:

:shipit:


Fix typo in guidance-for-the-configuration-of-private-registries-for-…

…dependabot.md
What's being changed (if available, include any code snippets, screenshots, or gifs):
Fixes a typo
Check off the following:

[x] For content changes, I have completed the self-review checklist.

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

@DamienCassou Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏

Going to check with the team on this failed status check - will return once we have more info!


scale-generator: implement exercise

Specification

Was just looking at this one, I see a scale-generator exercise in there already, merged  back in March. Close?

Closing as suggested; exercise already implemented.


Fix crash in tiled_layer_render(_CAImageProvider*, unsigned int, unsigned int, unsigned int, unsigned int, void*)

Version: 3.1.0 (2<IP_ADDRESS>) | net.artsy.artsy
Reason
objc_msgSend() selector name: release
Link to HockeyApp

https://rink.hockeyapp.net/manage/apps/37029/crash_reasons/158321338

Closing in favour of #2091.


Improve ORM

[x] Make sure failed calls throws exceptions
[x] Add better support for transactions

Fixed


[v11] Bump app-check dependency in Package.swift

Re-open following merge of https://github.com/google/GoogleAppMeasurement/pull/77


FIX-#6219: don't default to pandas for 'copy' on empty DataFrame/Series objects

What do these changes do?

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #6219
[x] tests added and passing
[x] module layout described at docs/development/architecture.rst is up-to-date

@YarShev looks like some problem with new unidist 0.4.0 while building docs:
reading sources... [ 38%] flow/modin/core/execution/unidist/implementations/pandas_on_unidist/dataframe
[mpiexec@build-21240760-project-224172-modin] match_arg (utils/args/args.c:163): unrecognized argument pmi_args
[mpiexec@build-21240760-project-224172-modin] HYDU_parse_array (utils/args/args.c:178): argument matching returned error
[mpiexec@build-21240760-project-224172-modin] parse_args (ui/mpich/utils.c:1642): error parsing input array
[mpiexec@build-21240760-project-224172-modin] HYD_uii_mpx_get_parameters (ui/mpich/utils.c:1694): unable to parse user arguments
[mpiexec@build-21240760-project-224172-modin] main (ui/mpich/mpiexec.c:148): error parsing parameters

Command killed due to timeout or excessive memory consumption

@anmyachev, this is not a problem with unidist. The issue is that we initialize the Modin engines (Ray, unidist) when building docs via the indirect calls to ray/unidist.put methods. Before unidist 0.4.0 the default backend was Ray, but starting since 0.4.0 the default backend is MPI. We build docs with the following command.
python -m sphinx -T -E -b html -d _build/doctrees -D language=en . $READTHEDOCS_OUTPUT/html

Most MPI implementations do not support execution if the user runs a program without mpiexec. So we see the issue when building docs now because MPI backend is trying to be initialized via the indirect call to unidist.put. What I think is we shouldn't initialize the Modin engines when building docs.

@anmyachev, this is not a problem with unidist. The issue is that we initialize the Modin engines (Ray, unidist) when building docs via the indirect calls to ray/unidist.put methods. Before unidist 0.4.0 the default backend was Ray, but starting since 0.4.0 the default backend is MPI. We build docs with the following command.
python -m sphinx -T -E -b html -d _build/doctrees -D language=en . $READTHEDOCS_OUTPUT/html

Most MPI implementations do not support execution if the user runs a program without mpiexec. So we see the issue when building docs now because MPI backend is trying to be initialized via the indirect call to unidist.put. What I think is we shouldn't initialize the Modin engines when building docs.

got it, thanks for the the explanation!

@anmyachev, will you handle the issue with docs build?

@anmyachev, will you handle the issue with docs build?

yes


mv hardlinks should be preserved when moving into a different directory

Testcase:
export C=/usr/bin/
export C="target/debug/coreutils "
dir=hlink
other_partition_tmpdir=/dev/shm/tmp769306

rm -rf $dir $other_partition_tmpdir
mkdir $dir $other_partition_tmpdir
> $dir/a
ln $dir/a $dir/b

${C}mv $dir "$other_partition_tmpdir"

ls -1i "$other_partition_tmpdir/$dir"

They should be equal. They aren't currently

That's very likely, mv can't do a simple rename across partitions, so it has some fallback procedure that's probably not working as expected here.

Ok thanks for your input, I will try to reproduce this with an USB key

I've tracked down the issue to move_dir here. But this function comes from webdesus/fs_extra so I will have a look there

There is a similar issue for symlink and a PR was proposed without reaction from the author. I wonder if we should "just" implement it directly on our side...

I've try to reproduce this:
❯ mkdir test
❯ mkdir test2
❯ > test/a
❯ ln test/a test/b
❯ target/release-small/coreutils mv test test2
❯ ls -1i test2/test/
4219332 a
4219332 b

Does your test only work when moving the folder to another partition?

Why do I get an error when trying to move the test into test2, but it is OKAY when using GNU mv?
nemesis@nemesis:~/Documents/Github/test/bin_3$ /home/nemesis/Documents/Github/Focus/util/coreutils_master/target/release/coreutils mv test test2
mv: cannot move 'test' to a subdirectory of itself, 'test2/test'

@allaboutevemirolive it's a bug, I opened a ticket for it: https://github.com/uutils/coreutils/issues/5481


Fix centos version and also pull always from centos registry

Signed-off-by: anmolbabu<EMAIL_ADDRESS>

Needs to be verified!!


OLED display support

Can we use this integration for OLED display to solve this issue
https://community.home-assistant.io/t/oled-display-support-for-raspberry-pi/444268

No, this integration is for exposing GPIOs as Switchers or Sensors.
You need an integration that supports I2C.
I highly recommend going for an ESP solution as there many projects based on ESP.

No, this integration is for exposing GPIOs as Switchers or Sensors. You need an integration that supports I2C. I highly recommend going for an ESP solution as there many projects based on ESP.
The ESPhome-based solution is a secondary backup but that would need a separate power supply.


Make the switches and LEDs on the Atlys board work

The old "Jahanzeb" firmware used the switches as described at https://github.com/timvideos/HDMI2USB/wiki/Digilent-Atlys-Board:-Switches,-Buttons-and-Status-LEDs#oldobsolete-stuff
It would be good for the new firmware to do something similar. Changing a switch should also cause a message / notification on the serial control interface.

Suggestions
Buttons

Button
Description

BTNU (N4)
Selects HDMI Input 0

BTNL (P4)
Selects HDMI Input 1

BTNR (F6)
???

BTND (P3)
Selects test pattern.

BTNC (F5)
Cycles through the outputs (HDMI Output 0, HDMI Output 1, Encoder)


migrate错误

'None' is not a callable or a dot-notation path
System check identified some issues:
WARNINGS:
?: (mysql.W002) MySQL Strict Mode is not set for database connection 'default'
HINT: MySQL's Strict Mode fixes many data integrity problems in MySQL, such as data truncation upon insertion, by escalating warnings into errors. It is strongly recommended you activate it. See: https://docs.djangoproject.com/en/2.2/ref/databases/#mysql-sql-mode
Operations to perform:
Apply all migrations: account, admin, auth, authtoken, captcha, cloud, config, contenttypes, count, feedback, goods, group_buy, homepage, qfile, qsmstoken, refund, sessions, shop, short_video, sms, trade, user, wx_logistics, wxapp
Running migrations:
Applying config.0037_auto_20200521_0958... OK
Applying trade.0037_auto_20190304_1542...Traceback (most recent call last):
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/utils.py", line 82, in _execute
return self.cursor.execute(sql)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/mysql/base.py", line 71, in execute
return self.cursor.execute(query, args)
File "/opt/anaconda3/lib/python3.7/site-packages/MySQLdb/cursors.py", line 209, in execute
res = self._query(query)
File "/opt/anaconda3/lib/python3.7/site-packages/MySQLdb/cursors.py", line 315, in _query
db.query(q)
File "/opt/anaconda3/lib/python3.7/site-packages/MySQLdb/connections.py", line 239, in query
_mysql.connection.query(self, query)
MySQLdb._exceptions.ProgrammingError: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'jsonb NULL)' at line 1")
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "manage.py", line 15, in
execute_from_command_line(sys.argv)
File "/opt/anaconda3/lib/python3.7/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
utility.execute()
File "/opt/anaconda3/lib/python3.7/site-packages/django/core/management/init.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/anaconda3/lib/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/anaconda3/lib/python3.7/site-packages/django/core/management/base.py", line 364, in execute
output = self.handle(*args, **options)
File "/opt/anaconda3/lib/python3.7/site-packages/django/core/management/base.py", line 83, in wrapped
res = handle_func(*args, **kwargs)
File "/opt/anaconda3/lib/python3.7/site-packages/django/core/management/commands/migrate.py", line 234, in handle
fake_initial=fake_initial,
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/migrations/executor.py", line 117, in migrate
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/migrations/executor.py", line 245, in apply_migration
state = migration.apply(state, schema_editor)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/migrations/migration.py", line 124, in apply
operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/migrations/operations/models.py", line 92, in database_forwards
schema_editor.create_model(model)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 307, in create_model
self.execute(sql, params or None)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 137, in execute
cursor.execute(sql, params)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/utils.py", line 67, in execute
return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers
return executor(sql, params, many, context)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/utils.py", line 89, in exit
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/utils.py", line 82, in _execute
return self.cursor.execute(sql)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/mysql/base.py", line 71, in execute
return self.cursor.execute(query, args)
File "/opt/anaconda3/lib/python3.7/site-packages/MySQLdb/cursors.py", line 209, in execute
res = self._query(query)
File "/opt/anaconda3/lib/python3.7/site-packages/MySQLdb/cursors.py", line 315, in _query
db.query(q)
File "/opt/anaconda3/lib/python3.7/site-packages/MySQLdb/connections.py", line 239, in query
_mysql.connection.query(self, query)
django.db.utils.ProgrammingError: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'jsonb NULL)' at line 1")

看了你们的代码，必须使用postgresql，不能用mysql吗？

Applying config.0004_auto_20181018_1108...Traceback (most recent call last):
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
psycopg2.errors.SyntaxError: syntax error at or near "WITH ORDINALITY"
LINE 6:                     FROM unnest(c.conkey) WITH ORDINALITY co...
^
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "manage.py", line 15, in
execute_from_command_line(sys.argv)
File "/opt/anaconda3/lib/python3.7/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
utility.execute()
File "/opt/anaconda3/lib/python3.7/site-packages/django/core/management/init.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/anaconda3/lib/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/anaconda3/lib/python3.7/site-packages/django/core/management/base.py", line 364, in execute
output = self.handle(*args, **options)
File "/opt/anaconda3/lib/python3.7/site-packages/django/core/management/base.py", line 83, in wrapped
res = handle_func(*args, **kwargs)
File "/opt/anaconda3/lib/python3.7/site-packages/django/core/management/commands/migrate.py", line 234, in handle
fake_initial=fake_initial,
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/migrations/executor.py", line 117, in migrate
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/migrations/executor.py", line 245, in apply_migration
state = migration.apply(state, schema_editor)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/migrations/migration.py", line 124, in apply
operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/migrations/operations/fields.py", line 249, in database_forwards
schema_editor.alter_field(from_model, from_field, to_field)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 535, in alter_field
old_db_params, new_db_params, strict)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/postgresql/schema.py", line 124, in _alter_field
new_db_params, strict,
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 543, in _alter_field
fk_names = self._constraint_names(model, [old_field.column], foreign_key=True)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 1115, in _constraint_names
constraints = self.connection.introspection.get_constraints(cursor, model._meta.db_table)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/postgresql/introspection.py", line 175, in get_constraints
""", ["public", table_name])
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/utils.py", line 67, in execute
return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/utils.py", line 76, in _execute_with_wrappers
return executor(sql, params, many, context)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/utils.py", line 89, in exit
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/opt/anaconda3/lib/python3.7/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: syntax error at or near "WITH ORDINALITY"
LINE 6:                     FROM unnest(c.conkey) WITH ORDINALITY co...
^
使用postgresql也报错。

换成postgresql-10，问题解决。


Add minimum lenght filter to mediathek listing

TV stations tend to split some news shows into single stories and publish them to the Web.
That leads to listings bloated by entries like "Verwirrung nach schwerem Unfall", 1m 25s.
An idea would be a slider in settings that allows to set a minimum length for Mediathek entries.
What do you think?
L.B.Q.R.
P.S.: Even with bloated listings, Zapp changed my tv watching life. It is very handy as a feeding remote to Kodi. Thank you.

I would like to have this feature myself, but the MediathekViewWeb-API is currently unable to filter by duration. Maybe I can implement this as soon as @bagbag releases version 2 of his API.
I would love a UI where the user can filter by different "duration slots", eg. "very short", "about half an hour", "about an hour" an "movie length". This way it would be very easy to filter for long movies, not so long documentations, rather short kids shows and very short teasers or news snippets.

Ops, I accidently had this project on "Ignoring".
The server parts concerning searching are more or less finsihed, if you want to start testing the API (and may even implement and release it - if it proves to be stable) just leave me a mail.
This would also close #106.

Duration would be a quite handy search filter. What do you think about others like the channel or publication date? (Should I open a separate issue for that?)

@dennmuel At this time filtering cannot be implemented anyway. I'll review all issues tagged with mvw-api-2.0 (including) comments and make a concept when the time comes.

Hi,
I love and enjoy your app much.
I have seen that at MediathekViewWeb it is possible to use advanced search syntax. But it looks like this is not working in the app.
Would be really helpful if it would be possible to use this filters in the zapp app. too.
May thanks.

I have seen that at MediathekViewWeb it is possible to use advanced search syntax. But it looks like this is not working in the app.
Would be really helpful if it would be possible to use this filters in the zapp app too.

Thank you for your feedback! I know Zapp needs a filter badly. This is on top of my priority list. However, I will not implement the search syntax of MediathekViewWeb as it not as self-explanatory as I would like it to be in Zapp.

Fixed in 6.0.0


Container hangs forever. hcsshim::ComputeSystem::WaitTimeout

I'm using Docker on Windows Server 2016. I run asp.net core (3.1) app in container. Application runs come hosted services (IHostedService). Container works well for some time and then hangs. Docker stop, docker kill, docker rm hang too. docker stats sometimes hangs, sometimes not. If docker stats reposnses, it shows, that container consumes 0 CPU, 0 RAM etc. In other cases it shows, that container consumes - CPU, - RAM etc. Trying to acceess the application by http results in hanging. The other containers on the same machine continue working. Restarting of docker service doesn't help. After restarting of computer either the container is removed (if I run docker rm before restart) or it becomes working (if I didn't remove it).
I noticed that when my container starts hanging there are 2 events from Docker in windows system log:

Error
hcsshim::ComputeSystem::WaitTimeout - End Operation - Error [cid=e88d27ae8fc4f935e0187b0252d35bec41686f94fbae510bdf11169ce514d595 error=WaitTimeout e88d27ae8fc4f935e0187b0252d35bec41686f94fbae510bdf11169ce514d595: hcsshim: timeout waiting for notification]
Warning
Syscall did not complete within operation timeout. This may indicate a platform issue. If it appears to be making no forward progress, obtain the stacks and see if there is a syscall stuck in the platform API for a significant length of time. [cid=e88d27ae8fc4f935e0187b0252d35bec41686f94fbae510bdf11169ce514d595 timeout=4m0s]

I create container with such parameters:
docker create -p $port -e "ASPNETCORE_ENVIRONMENT=$environment" -e "HOST_SERVER_NAME=${Env:COMPUTERNAME}" -v "c:\tns\COMMON:c:\mnt\tns" -v "${logsdir}:c:\logs" --name $contName --hostname $contName --restart unless-stopped --memory=4g my_private_container:$tag;
I use mcr.microsoft.com/windows/nanoserver:10.0.14393.2551 as base image for creating my image.
Some ideas, what should I do to prevent hanging?
Client:
Debug Mode: false
Plugins:
cluster: Manage Docker clusters (Docker Inc., v1.2.0)
docker info:
Server:
Containers: 5
Running: 1
Paused: 0
Stopped: 4
Images: 6
Server Version: 19.03.5
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics internal l2bridge l2tunnel nat null overlay private transparent
Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 14393 (14393.3442.amd64fre.rs1_release.191219-1727)
Operating System: Windows Server 2016 Datacenter Version 1607 (OS Build 14393.3443)
OSType: windows
Architecture: x86_64
CPUs: 4
Total Memory: 7.999GiB
Name: vm-scrol
ID: MNFQ:YSXQ:E6O5:FLOP:BFG2:MVMS:MO7V:S3HR:TSP5:MZ2T:GUGW:KWF4
Docker Root Dir: C:\ProgramData\docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false

We started running containers today on a new server and saw exactly the same messages in the event log.  I believe one for each container started from a YAML file.
Does anyone know where to start looking for the problem.?

We started running containers today on a new server and saw exactly the same messages in the event log. I believe one for each container started from a YAML file.
Does anyone know where to start looking for the problem.?

We have an assumption, that Windows edition may be important. The server, where docker hanged, was of *Data Center edition.


Don't use type variables in patterns

This PR is an attempt to fix part #13 (getting GHC 8.10.7 compatibility). But it doesn't work, because of an overlapping instance. The sad thing is that I think there really is an overlapping instance. I will report a GHC bug about this shortly.

The GHC bug is reported upstream. But we should still arrange not to have overlapping instances here.

Thanks a lot. Apologies for the conflict. Could you rebase and resolve the conflict so that CI tries out 8.10.7 and 9.0.2? Thank you.

Thank you. Now CI shows the overlap: https://github.com/Mikolaj/horde-ad/runs/5516892917?check_suite_focus=true#step:18:29
I don't understand much from this error message, though.

Might this be related to AllowAmbiguousTypes that was IIRC needed to define this SliceS constructor?

@goldfirere: while I'm clueless about the overlapping instances (all I know the class is defined here: https://hackage.haskell.org/package/orthotope-<IP_ADDRESS>/docs/Data-Array-Internal-Shape.html#t:Shape), I think the actual errors in 9.2.2 are due to a missing argument to From2S and so probably unrelated: https://github.com/Mikolaj/horde-ad/runs/5516892563?check_suite_focus=true#step:18:37
Do I get it right. Would it compile fine in GHC 9.2.2 once fixed? (And would the older GHCs compile fine with IncoherentInstances?)
How could we get rid of the overlapping instances?

Another, probably related, problem with SliceS: https://github.com/Mikolaj/horde-ad/blob/01f5b467d1b0ccf9e8e4244e0837829f857a6807/src/HordeAd/Core/HasDual.hs#L191
Uncommenting the type signature doesn't help:
src/HordeAd/Core/HasDual.hs:188:14: error:
    • Couldn't match type: (i0 + n) + k0
                     with: (i + n) + k
      Expected: Dual (OS.Array (((i + n) + k) : rest) Double)
                -> Dual (OS.Array (n : rest) Double)
        Actual: Dual (OS.Array (((i0 + n) + k0) : rest) Double)
                -> Dual (OS.Array (n : rest) Double)
      NB: ‘+’ is a non-injective type family
      The type variables ‘i0’, ‘k0’ are ambiguous
    • When checking that instance signature for ‘dSliceS’
        is more general than its signature in the class
        Instance sig: forall (i :: GHC.TypeNats.Nat)
                             (n :: GHC.TypeNats.Nat) (k :: GHC.TypeNats.Nat)
                             (rest :: [GHC.TypeNats.Nat]).
                      (KnownNat i, KnownNat n, KnownNat k, OS.Shape rest) =>
                      Dual (OS.Array (((i + n) + k) : rest) Double)
                      -> Dual (OS.Array (n : rest) Double)
           Class sig: forall (i :: GHC.TypeNats.Nat)
                             (n :: GHC.TypeNats.Nat) (k :: GHC.TypeNats.Nat)
                             (rest :: [GHC.TypeNats.Nat]).
                      (KnownNat i, KnownNat n, KnownNat k, OS.Shape rest) =>
                      Dual (OS.Array (((i + n) + k) : rest) Double)
                      -> Dual (OS.Array (n : rest) Double)
      In the instance declaration for ‘HasRanks Double’
    |
188 |   dSliceS :: forall i n k rest.

The dSliceS error from above is now reproducible on master branch (apologies for the merge conflicts again --- everything is now overhauled according to your ideas from last meeting --- the main class takes the dual component type as argument (e.g., Delta0 Double), not the primal (e.g., Double));
https://github.com/Mikolaj/horde-ad/blob/d069a45773ed849913b5ebd0345153072f304fd9/src/HordeAd/Core/DualClass.hs#L234-L238
Even the dSliceS signature alone suffices to cause an error. I wonder if the problem is going to vanish with the 9.0.2-compatible reformulation.

@goldfirere: I'm now blocked by this, because performance with GHC 9.2.2 is degraded and requires random hacks and with HEAD even more so (https://github.com/Mikolaj/horde-ad/issues/14), which makes performance measurements with GHC >= 9.2 suspect. Consequently, whenever I change anything in the code, I can't confidently benchmark the effects not having access to 9.0.2 at least. And I experienced with this codebase it's easy to gradually lose performance from little changes, feature additions or from optimizations that magnify unrelated pre-existing performance problems. If you are busy, I'd rebase and merge and try to complete this myself. I'm going to yell for help again, if I fail.

The rebase is going to be hopeless, so let me copy over the relevant bits and try to make it work.

I have manually rebased and completed this PR's work: d68277fb6b94907dfa8a7c5bebf0902f181f42a9 d68277fb6b94907dfa8a7c5bebf0902f181f42a9 cf6eaf7d392289bb7ebb14262a9c2e4439ee71b7
@goldfirere: That's so close to what you've proposed, including the IncoherentInstances under CPP that I'm not even asking for your review before closing. You may still have a chance to look at this code if you attempt to eliminate the auxiliary function that are needed only to capture proper types (I think the current proxies are not enough to fix that, but perhaps more proxies would be?) or to generally overhaul this type-level code if it's somehow fundamentally flawed.
Closing. Thank you!


Spot Client submitNewOrder() and testNewOrder() broken in 2.0.19+

We were chatting earlier directly on a commit message. I upgraded from 2.0.12 to 2.0.19 (and then 2.0.20) today, in an attempt to fix an issue around reconnecting to the spot UserData stream after a connection outage. I have a completely new issue now however. I'm getting the following whenever a new order is submitted:
{
  code: -1102,
  message: "Mandatory parameter 'symbol' was not sent, was empty/null, or malformed.",

This also happens with testNewOrder too. See below. It appears there's some double-encoding happening here?
I'm passing the exact same parameters as I was passing in 2.0.12, which was working nicely aside from the reconnect issue.
https://api.binance.com/api/v3/order/test?symbol%3DMIRUSDT%26side%3DBUY%26type%3DLIMIT%26newClientOrderId%3DREADACTED%26price%3D2.56800000%26quantity%3D62.30000000%26timeInForce%3DGTC%26newOrderRespType%3DFULL%26timestamp%3D1639114165191%26recvWindow%3D5000&timestamp=1639114165191&recvWindow=5000&signature=REDACTED

You can see here all the = and & syntax has been URL-encoded to %3D and %26, which completely breaks the request syntax.

Almost certainly this is wrong?
options.url += '?' + [encodeURIComponent(signed.serialisedParams),

That's encoding the entire params as a single URL-component, hence the issue. This means all "private" REST client endpoints that are not GET or DELETE will be broken I think.

Removed that encodeURIComponent() because AFAICT it's already encoded in the signed object, but then I get a Duplicate values for parameter 'timestamp'., which is true because that's also in the signed object too. I'll need to downgrade back to 2.0.12 I think as this feels a little too broken to feel confident fiddling with 🙏
I'll try and look closer at this later. I'm surprised nobody else has run into this at all. Are most people not using the spot client?

I'm also surprised nobody raised this...I'm dominantly in futures at the moment, but I'll also take a look as soon as I can. Your findings are very helpful in narrowing the scope - thank you for the time spent on this so far.

Almost certainly this is wrong?
options.url += '?' + [encodeURIComponent(signed.serialisedParams),

That's encoding the entire params as a single URL-component, hence the issue. This means all "private" REST client endpoints that are not GET or DELETE will be broken I think.

Looks like you were absolutely right (I was troubleshooting another issue with this already). It's only the values that should be encoded. Everything else should be in tact. I'll open a PR and push a beta version soon, could you help test it too? I have a system I can test with thoroughly on futures, but spot is a bit more manual for me to test.

@d11wtq Hi Chris, I've pushed a fix as a beta release - you can see it in #180 if you're curious. I'd appreciate if you could try it out and let me know if all endpoints you're interested in are now working for you: npm install binance@beta
Thanks!

@d11wtq following testing in #180 and confirmation in spot & futures, I've pushed it to stable release under v2.0.20. Would love to hear when you have a chance to test.

Hi @tiagosiebler so sorry for the delay in responding. Been a hectic weekend.
Installing 2.0.20 the error is still present.

Mandatory parameter 'symbol' was not sent, was empty/null, or malformed.

https://testnet.binance.vision/api/v3/order?symbol%3DBTCUSDT%26side%3DBUY%26type%3DLIMIT%26newClientOrderId%3Dx-U5D79M5BgC3PRHAtpxwHALk%26price%3D49010.00000000%26quantity%3D0.69470700%26timeInForce%3DGTC%26newOrderRespType%3DFULL%26timestamp%3D1639289425483%26recvWindow%3D5000&timestamp=1639289425483&recvWindow=5000&signature=REDACTED

But in 2.0.21, everything is working as expected, thank you ❤

Nice, thanks for confirming. Glad to hear it.


Move BuildStep out of corev1.Container

Idea:
From the last grooming session  and mainly based on the discussions in #516 ( as part of our API review ), we agreed on stop using corev1.Container in the definition of a Build step.
Main reasons for the above are explained in here, but in a nutshell is due to the amount of extra fields we do not use from corev1.Container.
The end-goal on this card is to leverage the usage of the Script feature of Tekton, as seen in their own Step definition. This means we would like to evolve our Build step to support Script.
We decided on a staged approach, which should look as follows:

[1] Remove the corev1.Container in favor of custom fields to continue supporting the fields we use today from corev1.Container
[2] Move to Tekton Script.

@sbose78 @ImJasonH  can you make sure the above reflects what we discussed previously, thanks in advance. @adambkaplan fyi.

Tekton seems to pass through core k8s Container object in each task step. Replacing core k8s Container with our own API means we need to be explicit about which fields we support, which is not inherently a bad thing. For instance, k8s rebases are safer because we control which new Kubernetes features are supported in the step spec.


Near Future Solar Core split should probably be removed

Similar to #9911 , but I haven't seen any examples of a mod doing NEEDS[NearFutureSolar] yet. However (due to CKAN not recognizing when mods are manually removed), this split does contribute to user frustration because it's a common culprit of B9PS errors: https://www.reddit.com/r/KerbalSpaceProgram/comments/1akzguu/endless_list_of_issues_reported_by_b9_part_switch/
I think that kind of problem would be less likely to occur if the split didn't exist - the user might notice that CKAN says they have Near Future Solar but it's not in their GameData, so they'd use CKAN to reinstall it and everything would be fine.
Also sorta related to https://github.com/KSP-CKAN/CKAN/issues/4017

what split?

what split?

NearFutureSolar is actually two packages in CKAN:
https://github.com/KSP-CKAN/NetKAN/blob/2992710bec6c0d1b6785ca939a4c0b886438cccb/NetKAN/NearFutureSolar.netkan
https://github.com/KSP-CKAN/NetKAN/blob/2992710bec6c0d1b6785ca939a4c0b886438cccb/NetKAN/NearFutureSolar-Core.netkan

Interesting, they both point to the same  download.  The core only installs the dll.

Interesting, they both point to the same download. The core only installs the dll.

Yes, it's the same situation as CryoTanks.  Nertea apparently decided to split the plugin from the content, with the forethought that perhaps the DLL could be used by other mods without the content being installed.  That's perfectly reasonable.  But no other mods are actually doing this, and the splits are causing issues.
I think there's a clue here: https://www.reddit.com/r/KerbalSpaceProgram/comments/1akzguu/comment/kpcicut/?utm_source=share&utm_medium=web2x&context=3

Yeah CKAN's ability to detect manually installed mods is pretty limited - it only works if the mod has a DLL with the same name as the CKAN identifier (e.g. scatterer works, EVE doesn't). I highly recommend using CKAN to install everything that's available there, and then manually installing things that aren't. That definitely gets a lot trickier with KSRSS and volumetric clouds, etc.
OMG I think you just cracked it. The DLL for NearFutureSolarCore is named NearFutureSolar. So CKAN incorrectly auto-detects this as NearFutureSolar being installed.

For better or worse, CKAN offers to "update" manually-installed mods to bring it under CKAN's control. I bet this is what happened:

You manually installed NearFutureSolar
CKAN auto-detects it as installed (so far so good)
You did the "update all" action in CKAN, which includes NearFutureSolar
Somehow this doesn't install NearFutureSolarCore (the dll)

Going to verify...


[WIP] gha: fix package repositories for nightly

mostly debugging for now; see https://github.com/containerd/containerd/pull/8714#issuecomment-1602329354

This is /etc/apt/sources.list on these machines;
## Note, this file is written by cloud-init on first boot of an instance
## modifications made here will not survive a re-bundle.
## if you wish to make changes you can:
## a.) add 'apt_preserve_sources_list: true' to /etc/cloud/cloud.cfg
##     or do the same in user-data
## b.) add sources in /etc/apt/sources.list.d
## c.) make changes to template file /etc/cloud/templates/sources.list.tmpl

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://azure.archive.ubuntu.com/ubuntu/ jammy main restricted
# deb-src http://azure.archive.ubuntu.com/ubuntu/ jammy main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://azure.archive.ubuntu.com/ubuntu/ jammy-updates main restricted
# deb-src http://azure.archive.ubuntu.com/ubuntu/ jammy-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://azure.archive.ubuntu.com/ubuntu/ jammy universe
# deb-src http://azure.archive.ubuntu.com/ubuntu/ jammy universe
deb http://azure.archive.ubuntu.com/ubuntu/ jammy-updates universe
# deb-src http://azure.archive.ubuntu.com/ubuntu/ jammy-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://azure.archive.ubuntu.com/ubuntu/ jammy multiverse
# deb-src http://azure.archive.ubuntu.com/ubuntu/ jammy multiverse
deb http://azure.archive.ubuntu.com/ubuntu/ jammy-updates multiverse
# deb-src http://azure.archive.ubuntu.com/ubuntu/ jammy-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://azure.archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse
# deb-src http://azure.archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse

deb http://azure.archive.ubuntu.com/ubuntu/ jammy-security main restricted
# deb-src http://azure.archive.ubuntu.com/ubuntu/ jammy-security main restricted
deb http://azure.archive.ubuntu.com/ubuntu/ jammy-security universe
# deb-src http://azure.archive.ubuntu.com/ubuntu/ jammy-security universe
deb http://azure.archive.ubuntu.com/ubuntu/ jammy-security multiverse
# deb-src http://azure.archive.ubuntu.com/ubuntu/ jammy-security multiverse

And /etc/apt/sources.list.d/microsoft-prod.list
deb [arch=amd64,arm64,armhf] https://packages.microsoft.com/ubuntu/22.04/prod jammy main

And /etc/apt/sources.list.d/ubuntu-toolchain-r-ubuntu-test-jammy.list
deb https://ppa.launchpadcontent.net/ubuntu-toolchain-r/test/ubuntu/ jammy main
# deb-src https://ppa.launchpadcontent.net/ubuntu-toolchain-r/test/ubuntu/ jammy main

Failures are;
Reading package lists...
E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/dists/jammy/main/binary-ppc64el/Packages  404  Not Found [IP: <IP_ADDRESS> 80]
E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-ppc64el/Packages  404  Not Found [IP: <IP_ADDRESS> 80]
E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/dists/jammy-backports/main/binary-arm64/Packages  404  Not Found [IP: <IP_ADDRESS> 80]
E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/dists/jammy-security/main/binary-s390x/Packages  404  Not Found [IP: <IP_ADDRESS> 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libc6:s390x : Depends: libgcc-s1:s390x but it is not installable
E: Unable to correct problems, you have held broken packages.

Perhaps it's not the mirrors that's the issue here, but actually a missing package for s390x?
 libc6:s390x : Depends: libgcc-s1:s390x but it is not installable

@thaJeztah Was looking into this issue recently. The issue occurs while installing the libseccomp-dev:s390x package. I have created a docker image with which you can reproduce the issue locally.
Have mentioned the steps here to create a container with which we can hit the issue. https://gist.github.com/akhilerm/ed0ac1bbef386bf740377c8508a7bfce
When using the archive.ubuntu.com instead of azure.archive.ubuntu.com, the problem does not occur.
Also it happens only on ubuntu:22.04. Works fine on ubuntu:20.04. As a quick workaround, we can change the ubuntu runner version in the github action just so that the test passes. But I think we should actually figure out the cause of the failure since the nightly does not block any contributions/releases to the project.

Thanks @akhilerm I also started looking what changed, and it looks like builds started failing between May 13 and May 14; see https://github.com/containerd/containerd/pull/8714#issuecomment-1613880004

closing, as this was superseded by https://github.com/containerd/containerd/pull/8768


Composing templates with slots?

Say I have a layout component as follows
<template>
  <quasar-layout>

      <left-menu ref="leftMenu"></left-menu>

    ...
  </quasar-layout>
</template>

Normally I would have one or more items inside the element with the slot="header", however to avoid huge components, I'd like to compose it.
However if I try to move it into a child component, I'm stuck with having to use a wrapper element (which doesn't work in my case due to strict CSS rules).
I don't think I can move the full element with the "slot=header" into the child component, as it would then apply to itself, and not the parent element. Any way to circumvent this composition limitation!?
<template>
   <-- Trying to avoid having to wrap like this. Any way to tell the template to use some kind of virtual wrapper node!? is this a limitation from web components? WTF!?
    <button
      class="hide-on-drawer-visible"
      @click="onClickLeft()"
    >
      menu
    </button>

    <quasar-toolbar-title :padding="1">
      Components
    </quasar-toolbar-title>

    <button
      class="hide-on-drawer-visible"
      @click="onClickRight()"
    >
      menu
    </button>

</template>

Please make sure to read the Issue Reporting Guidelines before opening new issues. Questions should be posted to the forum or StackOverflow. Thanks.


Updated README with project links/descriptions

Updated the repo's main README with links to and descriptions of our "foundational" projects, including ACE, Iter8, and Praxi.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm


Fix typos in README.md

Just a few typo fixes.
Hope you're having a great weekend! :)

Thanks! You too!


Suggestion: Allow user to choose mypy version manually

Sometimes people may not want to use the latest mypy for testing, because mypy can change its type checking output format (for example, Tuple[...] is changed to tuple[...] in 1.4, and Union[a, b] becomes a | b) . People who run automatic test suite would want to pin to a very specific mypy version.
Indeed, it is possible to pin to a specific action-mypy commit in GitHub workflow instead, but that also means people are unable to use any new features in latest action-mypy.
To be concise, I mean something like:
- name: workflow name
  uses: tsuyoshicho/action-mypy@v3
  with:
    mypy_version: '1.2.0'

Hi @abelcheung ,
I understand your suggestion.
However, I would like to hold off because the effect is limited.
The reasons are as follows.

The function to install a mypy is ancillary
Essentially, you should have your own requirements.txt for your environment and set it up yourself
If you want to use a fixed version of mypy, you need to fix it yourself and use the same one on local and on CI, otherwise you are likely to have problems

Note:
Now you can specify the version directly in setup_command.

* Essentially, you should have your own requirements.txt for your environment and set it up yourself
* If you want to use a fixed version of mypy, you need to fix it yourself and use the same one on local and on CI, otherwise you are likely to have problems

Yes, these 2 are the exact reason why I want to see action-mypy allowing users to specify mypy version. In a CI workflow all tools need some way to set tools versions.
Many python related tools use requirements.txt or pyproject.toml, tox has its own tox.ini to achieve the same effect, and so on. But I originally thought action-mypy doesn't have any.
You have pointed me to setup_command and it can achieve the same result, so I guess my suggestion can be closed, thanks a lot!


Add project documentation

Add project documentation in README.md to address:

Add a "how to cite this software" snippet
Installation procedure
- @raehik to do this once #13 is complete
Running procedure
Results

Do we need more detail? Sphinx or readthedocs? Probably not at the moment.

Some of this was addressed in #60 .
Still to do:

[ ] A CITATION.md file could be added providing a formatted citation snipped. (alternatively section in README)
[ ] More information on the model outputs should be provided.

CITATION.cff added in #99. I've elaborated on your model documentation in #106 -- in short, it exists in the paper, but it doesn't discuss implementation details, so we should add those.
Otherwise, with the readme writing and some extra stuff pending in #97 , I think this issue is OK to close.


Allocations Settings: Replace GAU picklist with lookup

When large numbers of GAUs exist, the picklist is unwieldy, and is also limited to 1000 values.

**lurch: add

Tracking W-008632

Included in beta release version 3.55 (Beta 3) and higher

Included in production release version 3.55


Fix open-metadata-conformance-suite

Signed-off-by: Bogdan Sava<EMAIL_ADDRESS>

To run Open Metadata Conformance Test, after successful build, run in terminal:
java -jar open-metadata-target/open-metadata-conformance-suite-1.1-SNAPSHOT.jar {server-name} {server-url}
Ex:
java -jar open-metadata-target/open-metadata-conformance-suite-1.1-SNAPSHOT.jar omas http://localhost:8080
Result is:
===============================
Open Metadata Conformance Test
===============================
Conformance Report for server: omas (http://localhost:8080)

Number of tests: 799
Number of tests passed: 799
Number of tests failed: 0
Number of tests skipped: 0

Congratulations, omas server at http://localhost:8080 is an open metadata repository

@bogdan-sava This fix does not seem to change the conformance suite itself.  Instead it is removing the use of GSON in other modules.  Is that right?  Does that mean we need to add a explicit requirement to the egeria method to ban the use of GSON?

Yes. It does two things: removes gson and replace the assembly plug-in with mavenj-jar-plug-in. After removing gson, worked from calling main method but still not from jar generated with assembly.
I know from experience that jar plug-in is more reliable, so I use it without more investigation.
I think mixing Jackson with gson is not good idea. However, if it is really needed, we can investigate about incompatibility and how to make them work.

Thanks for fixing this :)


Sound is still playing even insert coin window already close

Sound is still playing even insert coin window already close

Sir how about cancel buton when insercoin is on going?cancel button seems nit canceling the insert coin mode


MariaDB Server does not accept --public-network-access

Description:
Command Name
az mariadb server create
az mariadb server update

Errors:
az: error: unrecognized arguments: --public-network-access Disabled

To Reproduce:
Simply try to create or update a mariadb server and disabling the public network access
az mariadb server update --name $mariadbServerName --resource-group $rg --public-network-access 'Disabled'
Expected Behavior
Should be accepted as documented here: https://docs.microsoft.com/en-us/cli/azure/mariadb/server?view=azure-cli-latest#az-mariadb-server-create
and here: https://docs.microsoft.com/en-us/cli/azure/mariadb/server?view=azure-cli-latest#az-mariadb-server-update
Environment Summary
Linux-4.15.0-1075-azure-x86_64-with-debian-stretch-sid
Python 3.6.5

azure-cli 2.2.0 *

mariadb

@kummanish - can you take a look?

The CLI version needs to be changed to : azure-cli 2.3.0
It should work with that version.

Please use latest cli version 2.3.1
You can check if --public-network-access is a supported argument using the help option :
az mariadb server create -h
az mariadb server update -h

Thank you for your answer!
I am using cloud shell and I have no idea how to update the CLI there. Tried to restart my session but it did not change anything. And I can't install CLI on my own computer (company restrictions).
I guess this is another issue.

@yonzhan. @Juliehzl  : Why is Azure Cloud Shell still pointing to an older version of azure-cli 2.2.0 ?

https://github.com/Azure/azure-cli/milestone/85 We plan to build to Cloud Shell three days later.

Tested with latest version of cli, this is indeed working. Once updated in cloud shell, it'll all be ok.
Thank you!


Remove duplicated keys when showing plugin details

fix: #1343

Thanks @idorax. While it fixes this and future issue I'm not sure if we should allow duplicate keys at all. I can't think of use case when it is desired to have them listed at two (or more) places. @psss?

Agree with @lukaszachy. I'd also say that the same key should not be present multiple times in the key lists. Also, I guess list(set(...)) could possibly change the order? Would be good to keep the original order.

Please fix by removing the duplicate instead.

Hi @psss and @lukaszachy, I have updated the related code to remove the duplicated keys and keep the original order. Please help to review,  thanks!

@idorax Sorry, I meant to find in discover plugins code where I've added 'dist-git-source' second time and remove it from there. And check for other possible duplicates.

Hi @lukaszachy, dist-git-source and dist-git-type are removed from _keys in class DiscoverFmf, please help to review again, thanks!


raftstore: make the campaign after split happen faster

Hi,
This PR tries to fix issue #1639
PTAL @siddontang @BusyJay

seem that we can get random election timeout from raft directly

I don't like the idea behind this PR, which tries to guess the speed of sending messages to followers and what happens in followers in a friable non-intuitive way. It's try the best to make it to be high degree of possibility in an ideal environment, but it will still fail in a usual environment with package loss.
This issue should be a minus issue about optimizing the tikv service available time, which should be behind the hook of tidb cluster. It should not become a major issue about service breaking down and cause errors reported to end users.

PTAL @BusyJay

LGTM


How to stop recorder when app is killed

Please fill the template to help you out. Also, please try the Example project compare before submiting the issue when you have certain issue with your project setup.

Version of react-native-audio-recorder-player
2.5.1
Version of React Native
0.64.4
Platforms you faced the error (IOS or Android or both?)
Android
Expected behavior
When the app is removed, the recorder has to stop.
Actual behavior
When the app is removed, the recorder is still in process.
Steps to reproduce the behavior

@jonaxd1 Can you get the solution?


Add options.absolutePaths.

This fixes issues with single-page applications that use pushState.
The applications may serve up index.html for a URI with a long
path, such as http://mytodoapp.com/items/4
Generate cache files with absolute paths, /test.js instead of test.js.

Fixed with #31


Attributes 2.02.185 not being pulled with the chef-ruby-lvm-attrib gem version 0.2.7

We use GitHub issues to track bugs and feature requests. If you need help please post to our Mailing List or join the Chef Community Slack.

Chef Community Slack at http://community-slack.chef.io/.
Chef Mailing List https://discourse.chef.io/

Attributes 2.02.185 not being pulled with the chef-ruby-lvm-attrib gem version 0.2.7
ArgumentError: Unable to load lvm attributes [lvs.yaml] for version [2.02.185(2)]. The version/object may not be supported or you may need to upgrade the chef-ruby-lvm-attrib gem. Error [No such file or directory @ rb_sysopen - /opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-ruby-lvm-attrib-0.2.7/lib/lvm/attributes/2.02.185(2)/lvs.yaml]
I get this error it does'nt list in the attributes , see below

Also, one more question; I think the attributes version is getting incremented regularly; like we had 2.02.180 recently; but then its now expecting 2.02.185 ; I believe this from LVM2 PACKAGE ... if this attribute version keep changing it would affect our infrastructure run on server.
Is there a way to maintain at one stable version of attributes for the gem installed ?
Support issues opened here will be closed and redirected to Slack or Discourse.

I've release 0.2.8 which includes that version


[LOC] Back-Translation "コンテンツ"→"content"

https://docs.microsoft.com/ja-jp/nuget/create-packages/creating-a-package

The PR is not being built because the target branch live is filtered in .openpublishing.publish.config.json on live branch.

The PR is not being built because the target branch live is filtered in .openpublishing.publish.config.json on live branch.

@hyoshioka0128:
Thank you for your feedback and suggestion!
We agree with your suggestions, and we will include them into the next article update release.
Kind regards,
Microsoft DOCS Global Experience Team


Add ability to configure and deploy reasonably complete "server" from template

Since the cookbook does not actually provide hooks to configure and deploy a well formed "/etc/nginx/sites-available/[server] from options, it means that most sysadmins have to write their own customized cookbooks to wrap the LWRP's in nginx to deploy and activate their hand-constructed templates or config files.
May I suggest providing a recipe to read a hash that describes such a "server" from a role or other recipe? I'm working on such a recipe now for SSL enabled load balancer configurations and would be happy to work with you to make it available in the nginx cookbook.

@nkadel-skyhook I think I understand what you're saying, but the opinion of this cookbook is to be a building block, not an end-all cookbook - this style got us into trouble the first time around.
Considering that the way to control nginx sites and configuration is via an nginx config file, I do not see how putting data into node attributes/hashes/etc is any better than allowing a user to use this building block, and supply their own config file (template, cookbook_file, etc) similar to the working approach shown in the example recipe.
Can you explain why using a hash (which can have confusing behaviors when using node attributes and precedence levels) is better than leaving the common interface to a file that the end user controls explicitly?

I can certainly explain.  "Having a file that the end user controls explicitly" means that every single end user must devote time and effort to writing their own unique files, from scratch. This means a great deal of duplicated effort to write even the most basic and most commonly used of workable nginx configurations. A modest template and workable role could allow precisely the kind of accessible, tested, configuration access that would help make the nginx cookbook much more useful in itself. It also reduces the burden of maintaining compatible third party coookbooks which must be kept compatible with any upstream changes with the nginx cookbook itself.
I wouldn't suggest eliminating the current features, but rather an enhancement to support the most common usages. And I'd be happy to transform some of the application code I'm working with lately, for example for multiple virtual hosts behind a single Nginx instance, and offer it as a patch if that seems reasonable.

I agree with @miketheman in that this cookbook should just be a basic building block. There's so much variation in an nginx config file for a site, I don't think it's something this cookbook should be concerned with.
Nothing wrong with creating a new cookbook called nginx_site or something (in fact it looks like there are already some of these out there) whose only concern is to manage nginx site configs.

Based on previous responses here, it sounds the question has been answered. If not, please reopen.


Add a --token global flag

A user activating the 2FA on his/her account makes the hub-tool ask for 6-digit code in a regularly basis.
This behavior doesn't fit well with CI use cases.
We should add a global flag like --token which accepts a Personal Access Token (with its current limitations) to bypass 2FA login. We may also support an env var DOCKER_HUB_PERSONAL_ACCESS_TOKEN.

Something similar to docker's --password-stdin option would be very nice!


Use github-flavored markdown for note sections

See https://stackoverflow.com/questions/50544499/how-to-make-a-styled-markdown-admonition-box-in-a-github-gist for reference
Signed-off-by: Eduard Itrich<EMAIL_ADDRESS>

Very good idea! Are there any plans yet to condense something what @frosty-geek suggested, @maxwolfs?

Very good idea! Are there any plans yet to condense something what @frosty-geek suggested, @maxwolfs?

Yes we are working on it here: https://docs.scs.community/docs/contribute/styleguide#admonitions


PhotoSwipe does not load correctly with jQuery Mobile

I am using JQM 1.0.1 and PhotoSwipe 3.0.4, and the setup is
$("#bilder").live("pageinit", function() {
console.log("Instantiating PhotoSwipe ...");
var myPhotoSwipe = $("#img_gallery a").photoSwipe({ enableMouseWheel: false , enableKeyboard: false });
})
The #bilder div is a JQM page (data-role="page") and the #img_gallery div is the content div inside that page. It contains a ul-list with a couple of images linked the same way as in your example on www.photoswipe.com. The images just show up according to the static markup, no enhancement by PhotoSwipe. No errors encountered either, and the pageinit event is properly triggered according to the console log.
I notice that the examples in the distribution have a slightly more complex setup than the examples on www.photoswipe.com, is this an issue in my case?

I'm having this same problem, only it seems to occur randomly. Sometimes it works, sometimes it doesn't on the very same gallery. Ive spend hours to try and fix this problem, but I can't find anything. No errors nothing. It occurs in Chrome and Safari Mobile (haven't tested other browsers). Also using the markup from the jquery mobile example.


⚠ Bofrost.lu has degraded performance

In f56cb22, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1770 ms

Resolved: Bofrost.lu performance has improved in b7a0726 after 8 minutes.


The characters e., can be entered into number widgets with a valueType of int

- Do you want to request a feature or report a bug?
bug
- What is the current behavior?
The number widget seems to suppress all characters that aren't digits, e, ., +, -, or ,. (I assume the reason why e and + are allowed is to support exponential notation?)
However, these characters are also allowed for number fields with a valueType of int. An attempt is made to sanitize them later, but it doesn't quite work and can lead to the field containing the string .nan.
- If the current behavior is a bug, please provide the steps to reproduce.

Add a number field to a collection:

      -
        label: MyNumberField
        name: myNumberField
        widget: number
        valueType: int

Create a new item in the collection
Enter the text 123e in the field
Press 1

Observe that the e disappears and the 1 doesn't get added(?)

Press 1 again

Observe that the 1 does get added this time.

Press e twice, then 1

Observe that ee is left alone and the content is now 123ee1

Click Publish

Observe that the save is rejected with a MYNUMBERFIELD IS REQUIRED. message

Change the value to 123..1
Click Publish

Observe that the field gets persisted as:
myNumberField: .nan

- What is the expected behavior?

That ,, ., and e are suppressed when valueType is int. Alternatively that no keystrokes are suppressed and invalid numbers are dealt with when Publish is clicked.
That an accurate validation error is rendered when an invalid number has been entered
That garbage like .nan is never persisted :)
Maybe that e, + and , aren't allowed at all, even when valueType is float or not specified. It seems unlikely that anyone would want to use exponential notation in a CMS.

- Please mention your versions where applicable.

Netlify CMS version: 1.9.2
Browser version: Chrome 67.0.3396.87/OSX

Node.JS version: 10.4.1
Operating System: Mac OSX 10.13.5 (High Sierra)

The number widget really isn't doing anything here - HTML number inputs accept those characters for scientific notation, and no effort has been made to validate within the CMS. A validation method should be added, perhaps using a library that handles number validation comprehensively rather than reinventing the wheel.

@erquhart, ah, you're right about <input type=number> causing most of the weirdness. That thing seems terrible :)

I believe this is addressed in #2067, will release soon.


[Backward incompatible issues in 1.1] segmentAssignmentStrategy can be NULL after it is deprecated in SegmentValidationAndRetentionConfig

Due to #11869, now segmentAssignmentStrategy can be NULL, this seems a breaking change as it requires explicitly code change otherwise we will create TableInfo with NULL segmentAssignmentStrategy.

cc @Jackie-Jiang I also saw you commented in the pr that this is backward incompatible, do we have a fix for it?

Can you elaborate more on the problem? We didn't introduce backward incompatibility in the PR (I commented and the contributor reverted the change). Basically it is okay to have it as null. Are you using this field in your internal code?

yes, we control the table config creation so it's a big change for us. As long as leaving it as NULL works, we are fine with it. Thanks @Jackie-Jiang for taking a look at this issues, we can close it.


Incorrect mp3 playback

mp3 decoder implementation cannot play any mp3 file produced by ffmpeg.
AudioTest.java is the code i have tried to play mp3
AudioTest.zip

You didn't attach the mp3.


[$500] Distance - The title 'Distance' changing to 'Merchant' when toggling on Billable

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Pre-condition:

Go to old dot as admin
Navigate to collect Workspace settings--Expenses
Set "re-bill expenses to clients" to "default to Billable "
Steps:
Launch app
Open employee WS
Tap plus icon -- Request money
Tap distance request
Select start and finish waypoints
Tap next
Tap distance
Tap on distance request created to open distance request detail page
Note under distance heading, distance mentioned
Tapping on distance, user can add/change waypoints
Toggle on Billable
Note "distance" heading changed to "merchant "
Tap on merchant
Edit waypoints option not shown

Expected Result:
The title 'Distance' shouldn't change to 'Merchant' when toggling on Billable
Actual Result:
The title 'Distance' changing to 'Merchant' when toggling on Billable
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/076bbb79-2843-495c-ad5c-3cb2788cda13
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01629522855183a4d0
Upwork Job ID:<PHONE_NUMBER>378032640
Last Price Increase: 2023-11-09

Proposal
Please re-state the problem that we are trying to solve in this issue.
Distance-Title "Distance" changed to "merchant" when toggle on Billable
What is the root cause of that problem?
When toggle on Billable, isDistanceRequest will be false. It cause that we display merchant instead of distance
What changes do you think we should make in order to solve the problem?
We should update the TransactionUtils.isDistanceRequest function return true even when toggle on Billable
What alternative solutions did you explore? (Optional)

@DylanDylann Thanks for the proposal. Your RCA is correct but not complete. isDistanceRequest is being false indeed but that should not happen in the first place.

@Krishna2323 Thanks for the proposal. Your RCA is correct. The solution looks good to me 👍.
🎀 👀 🎀 C+ reviewed
Link to proposal

🎀 👀 🎀

🎀 👀 🎀 C+ reviewed

Not overdue. @iwiznia https://github.com/Expensify/App/issues/31128#issuecomment-1804776485

Proposal looks good, but it is kind of brittle to have to add that logic everywhere... like we already have it here.
Maybe we should expose just one method in JS that would have this logic in it then all callers would call that method and never call the updateDistanceRequest/editMoneyRequest directly.
Thoughts?

@iwiznia I agree! That would be better.

Cool @Krishna2323 can you update your proposal to do that please?

I think it would be better to:

Do not export the 2 methods we are using now
Instead, only export the new method
Update all existing usages of the 2 methods to use the new method

The PR that introduced the bug has been identified: https://github.com/Expensify/App/pull/27875
The offending PR has been commented on: https://github.com/Expensify/App/pull/27875#discussion_r1405001562
A discussion in #expensify-bugs has been started: Not needed
Determine if we should create a regression test for this bug: I don't think this is needed. It's seems like a one time bug.

Summary of payments:

Contributor: @Krishna2323 $500 paid via Upwork
Reviewer: @s77rt $500 paid via Upwork

All paid up


parse-uri breaks ES5 support

heya guys
just noticed that library dependency https://github.com/Kikobeats/parse-uri was upgraded and uses Arrow function expressions syntax now (v1.0.5), which breaks ES5 support (for version v2 and v3, which is used by pixijs@4 and pixijs@5)
don't know about correct way of fixing that: pinning the version here or asking them to fix theirs build

Unfortunate they would make a breaking change like that in a patch version.
Pinning the version here would help, but only if we release a new version here with the pin and then a new version of pixi using it. Alternatively you can pin the version in your project directly which will fix the issue for you immediately.


cranelift: Add a new, optional flag for preserving frame pointers

This flag is optional, but when it is set then Cranelift backends must preserve frame pointers (or ISA equivalent).
Preserving frame pointers -- even inside leaf functions -- makes it easy to capture the stack of a running program, without requiring any side tables or metadata (like .eh_frame sections). Many sampling profilers and similar tools walk frame pointers to capture stacks. Enabling this option will play nice with those tools.
Our x64 backend already unconditionally preserves frame pointers, so it is trivially conforming with this new flag.
Our aarch64 backend preserves frame pointers or not based on whether the machinst framework tells it to or not by calling gen_prologue_frame_setup, and the machinst framework looks at this new flag when deciding whether to call the backend's implementation of gen_prologue_frame_setup, so it is conforming with this new flag.
However, our s390x backend has an empty implementation of gen_prologue_frame_setup, and so it is not preserving frame pointers when this new flag is set. We will need a follow up PR that brings our s390x backend into conformance with this new flag.
cc @uweigand, your help with this last bit would be very appreciated, as I'm not familiar with s390x.
cc https://github.com/bytecodealliance/wasmtime/pull/4431

@cfallin

good to merge once we have s390x supported as well

As I just said over in https://github.com/bytecodealliance/wasmtime/pull/4431#issuecomment-1189597570 I think we can actually land this PR now, since it doesn't break anything by itself, as nothing is relying on the frame pointers yet.
But we shouldn't land https://github.com/bytecodealliance/wasmtime/pull/4431 until there is s390x support for this flag, for sure, as that would break Wasmtime on s390x.

Ah, my mistake, I had misunderstood the intended order of changes; yep, r+ for merging this now. Thanks!

cc @uweigand, your help with this last bit would be very appreciated, as I'm not familiar with s390x.

Sure, I will post a follow-up PR to add s390x support as soon as this is merged.

Sure, I will post a follow-up PR to add s390x support as soon as this is merged.

Thanks!