Separate any-to-unknown and less-strict rules

I think it would be good to have 2 separate sets of rules

any-to-unknown
less-strict

I'm a bit confused about

import "@total-typescript/ts-reset/array-includes";
import "@total-typescript/ts-reset/set-has";

Why would you want something less strict? Maybe you could give some examples to show why you would want that. I've been having scenarios with Array.includes() where sometimes it's nice to have T | U and sometimes it's easier with string but less "true".
Having separate sets of rules, it's easier to pick unknown-to-any rules which make your code safer and not the other one (which makes your code less true but improves DX).

I'd still like to keep array-includes and set-has in the recommended rule set, and I'm happy with the current workaround of only importing the rules you want.
If we add more configurations, we'll need to document and justify those configurations.

It won't scale if you plan to do dozens of rules.
Until then I'm fine with the current workaround 👍


Write a contribution tutorial

Explain how to contribute to this package in a CONTRIBUTE.md

I would like you to assign me this issue please.

good job


Make branches updatable with sibling node value

Fixes #25.
Add sibling node value to proofs. This allows leaves added via AddBranch to be deleted. The rationale for not making the sibling value optional as per this comment is that it would impose additional burden on developers without an explicit distinct type for updatable vs non-updatable proofs, i.e. a developer using the SMT library would have to remember that a particular proof is updatable and another is not. Making all proofs updatable introduces minimal overhead (~60 bytes give or take) and eliminates any confusion or possibility of misuse.
Note: certain indices will have to be changed if #22 is merged prior to this, noted with TODOs. Fixed in 4974a43.

Waiting on https://github.com/lazyledger/smt/pull/21#discussion_r591884651 to fix CI, but if you run tests manually they pass now.

Is this a draft or is it complete? I don't see "oldSiblingData" actually being used by anything, it's just being passed around.

Is this a draft or is it complete? I don't see "oldSiblingData" actually being used by anything, it's just being passed around.

It's complete. oldSiblingData is actually not needed in UpdateForRoot or even deleteWithSideNodes, good catch.


fix: offer creation improvements

Some improvements / cleanup to the credential offer creation process:

Take the input  grants as leading, and only set default values if a required prop is not provided. Currently the grants objects are overwritten in some places, which means that a) you can't add custom properties and b) the authorization_server in e.g. the pre auth flow was removed when the offer was created
do not put the whole credential offer uri in the credential_offer_uri param, this was leading to weird behaviour where sometimes the value would be the whole uri openid-credential-offer://credential_offer_uri=<uri> and sometimes just <uri>. So now the object just contains the uri that hosts the credential offer, not the uri that is scanned by the wallet (it's quite confusing that the credential offer uri can contain a credential_offer_uri param, so it was somtimes interchanged).
Correctly encode the credential_offer_uri param (Fixes https://github.com/Sphereon-Opensource/OID4VC/issues/102)

Hey @nklomp do you have a chance to look at this PR this week?

@TimoGlastra Small nudge, since you requested for these PRs to be merged

done


publish application

Updated application buttons to link to the Google form (do we want a bit.ly link here? Or just the raw URL?)
Also changed "Applications open March 1st" to "Applications close March 31st."

LGTM


Powerranks breaks Towny plot claiming.

Hello,
When players are claiming land in Towny for themselves personally, Towny checks if they have any max_plot info nodes in their permissions.
PowerRanks doesn't appear to have finished adding their chat implementation: https://github.com/PowerNetworkHub/PowerRanks/blob/6448480eaf30427aa35e0792b5d454160db1a241/src/main/java/nl/svenar/PowerRanks/External/PowerRanksVaultChat.java#L51 and I have been having to tell my users to uninstall PowerRanks.
You can fix your implementation easily by returning the defaultValue instead of false, 0 or null.

Also very nice work.


add new extension targets for action extensions everywhere

closes https://github.com/Shopify/app-ui/issues/835
https://shopify-dev.ui-extensions-026v.josh-white.us.spin.dev/docs/api/admin-extensions/unstable/api/extension-targets
Adding type definitions for the new extension targets being added.
Targets being added:

[x] Order details fulfilled card (weird)
[x] Draft orders overview
[x] Draft order details
[x] Draft orders bulk selection
[x] Variants details
[ ] Variants bulk selection (being deleted)
[x] Collections overview
[x] Collection details
[x] Abandoned checkout details
[x] Discount overview
[x] Discount details (in progress)

Checklist

[ ] I have :tophat:'d these changes
[ ] I have updated relevant documentation

Hi @bakura10 - Apologies, our docs were incorrect. The correct target name is admin.product-variant-details.action.render. We're shipping a docs update now


Update Typespecs

Add https://docs.aws.amazon.com/transcribe/latest/dg/API_JobExecutionSettings.html

@bismark thanks!

Published new version


Various Extension Errors on Enterprise Network with TLS Inspection

Describe the bug
The extension throws various errors about not being able to connect to web resources because of a certificate error. For example:
Failure to retrieve username:  Ms [HttpError]: request to https://api.github.com/user failed, reason: unable to get local issuer certificate     at /Users/blake.motl/.vscode/extensions/github.vscode-github-actions-0.25.8/dist/server-node.js:2:2786469     at process.processTicksAndRejections (node:internal/process/task_queues:96:5)     at async /Users/blake.motl/.vscode/extensions/github.vscode-github-actions-0.25.8/dist/server-node.js:2:2858428     at async va.get (/Users/blake.motl/.vscode/extensions/github.vscode-github-actions-0.25.8/dist/server-node.js:2:2868607)     at async /Users/blake.motl/.vscode/extensions/github.vscode-github-actions-0.25.8/dist/server-node.js:2:2858363     at async la (/Users/blake.motl/.vscode/extensions/github.vscode-github-actions-0.25.8/dist/server-node.js:2:2858330)     at async /Users/blake.motl/.vscode/extensions/github.vscode-github-actions-0.25.8/dist/server-node.js:2:2862166     at async Object.getContext (/Users/blake.motl/.vscode/extensions/github.vscode-github-actions-0.25.8/dist/server-node.js:2:2862122)     at async oi (/Users/blake.motl/.vscode/extensions/github.vscode-github-actions-0.25.8/dist/server-node.js:2:2735342)     at async gn (/Users/blake.motl/.vscode/extensions/github.vscode-github-actions-0.25.8/dist/server-node.js:2:2760637) {   status: 500,   request: {     method: 'GET',     url: 'https://api.github.com/user',     headers: {       accept: 'application/vnd.github.v3+json',       'user-agent': 'VS Code GitHub Actions (0.25.8) octokit-rest.js/19.0.7 octokit-core.js/4.1.0 Node.js/16.17.1 (darwin; arm64)',       authorization: 'token [REDACTED]'     },     request: { hook: [Function: bound bound e] }   } } [Error - 12:14:59 PM] Unhandled error while validating: request to https://api.github.com/user failed, reason: unable to get local issuer certificate
Notably the intermediate certificate issued by the TLS inspection service is trusted in the MacOS keychain and is set via NODE_EXTRA_CA_CERTS. I have also tried several extensions that claim to expose the system trust store to VSCode extensions, but none of them have worked.
To Reproduce
I have been able to reproduce this issue on several coworkers computers.
Steps to reproduce the behavior:

Use any TLS inspection agent, Netskope, ZScaler, Cloudflare ZT, etc.
Install the extension and open a workflow file.
The extension will start throwing errors, especially if you click on a reference to a reusable action.

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Extension Version
v0.25.8
Additional context
Add any other context about the problem here.

it ifseeand flow wolckrow ruoy rof ecruos edocGitHub buhtig gnisu yrT

I'm getting exactly the same error on vscode 1.80.1 with the extension v0.25.8

Closing as this is a duplicate of #39


monitor files

Hi!
Please, is there a way to monitor files for changes and upload them? Let's say, I want to monitor all CSS and JS files or a specific folder to be uploaded on the fly; is there a configuration for it?
Thank you for the addon and for your attention.

I found somebody who implemented it.
Is there a chance of accepted a pull request from @theproducer?

What do you mean changes? Changes not modified by atom editor?

Yes. Some files can be edited by preprocessors, for example.

so it duplicate with #65, not in support plan yet. But a pull request is welcome. Thanks for this issue


Decrease number of order utilities

The list of number of order utilities is huge and I guess it's ok to decrease this list a bit. I've now limited the list to only 5 (+ first/last) responsive order utilities which should be ok

The number was dictated by the column count. Unsure how much we need to really map to that though, so I'd be curious about usage there from people using these utilities.

I personally never used the order classes with numbers, only the first & last utilities to shift some cols for different screen widths. These 5 (+2) order utilities still gives people to completely reorder at least 7 cols which isn't that common I guess.

Yeah, it was a holdover from the old push/pull classes in v3. We had all 12 for each direction, and order saved us at least one set of utilities that could produce the same effect. I could see us cutting this in half to start in v5 and see what folks think during the alpha period.
Can you document this in the migration page too then?

Done: https://github.com/twbs/bootstrap/pull/28874/commits/132fa64cfe2a22914d7d21aa16c9cd1d18137629#diff-bdd3aaef666a8581309fadd06d14b895

TBH the current way makes more sense due to the number of columns.

I like this ❤
Why the last is not 6?

Why the last is not 6?

idk, 6 felt a bit too low so I chose 9. Maybe 6 makes more sense indeed.

Changed last to 6 now

@mdo, just to make sure, is it ok to merge this for you?

Ping @mdo

Sorry, and thank you!


ERROR in Ng4TwitterTimelineModule is not an NgModule

If I import Ng4TwitterTimelineModule, ng serve throws the error that it is not an NgModule. If I import it using Ng4TwitterTimelineModule.forRoot(), the error is:
ERROR in Error encountered resolving symbol values statically. Calling function 'Ng4TwitterTimelineModule', function calls are not supported. Consider replacing the function or lambda with a reference to an exported function, resolving symbol AppModule in .../src/app/app.module.ts, resolving symbol AppModule in .../src/app/app.module.ts
The project is created with angular-cli 1.3.0 and<EMAIL_ADDRESS>

I get the same error. Another piece of information that might be relevant is that I first added Ng4TwitterTimelineModule while I had a the local server running. It then worked and it looked and worked great.
When I tried ng build --prod I also got the error described above. Then when I tried to start the local server again I also got the same error. So in my case, Ng4TwitterTimelineModule works great when imported to a project with an already running local server, but cannot be imported when starting a local server or when compiling a project. 😕
I have even been able to reproduce this by commenting out Ng4TwitterTimelineModule.foorRoot() in the import array in app.module.ts. The component where I am importing Ng4TwitterTimelineService does not load properly, but when I commenting in Ng4TwitterTimelineModule.foorRoot() while the local server is still running, it all works perfectly and looks great again.
Is this a clue to anyone?

guys, yes I am aware of this issue, but wasn't able to fix this bug so far, probably due to lack of proper time for it to investigate further. Feel free to send PR with fix and I will merge into master and release new version.

Will be more than happy to send the PR for this, if I was having any idea how to fix it ...

just adding @NgModule to the ng4-twitter-timeline.module.d.ts worked for me  for both ng seve and ng build --dev
import { NgModule, ModuleWithProviders } from '@angular/core';
@NgModule({
declarations: [
Ng4TwitterTimelineModule
]
})
export declare class Ng4TwitterTimelineModule {
// static forRoot(): ModuleWithProviders;
}

@gaarangoa your solution is working with ng buld --dev, but is failed with ng build --aot
this is the error that I got when the project was compilated with ng build --aot
ERROR in Error: Unexpected module 'Ng4TwitterTimelineModule in /Users/razvanstan/work/e-spres-oh/youth-league/proleague-ui/node_modules/ng4-twitter-timeline/lib/ng4-twitter-timeline.module.d.ts' declared by the module 'Ng4TwitterTimelineModule in /Users/razvanstan/work/e-spres-oh/youth-league/proleague-ui/node_modules/ng4-twitter-timeline/lib/ng4-twitter-timeline.module.d.ts'. Please add a @Pipe/@Directive/@Component annotation.

Hey guys, I had the same issue, but all I had to do was add ".forRoot()" to the end of  Ng4TwitterTimelineModule in my app.module imports. I don't have it added to declarations at all, just imports. Hope that helps.

@krhudsn I tried your workaround and it works well. However, when I visit the same route after visiting another route, the component is not there anymore (i.e. the component is missing). Any way to correct this?

My 2 cents on the solution proposed here:
The lib folder is generated based on what is in the src folder. Generation is done by following tsconfig file(s). I am still in process of trying to fix this properly in the src and my feeling is that this module is using lower ES versions, which are not that restrictive with map files (which are generated when prod is built of your project), and that is the reason of the issue.
Just changing the lib folder is not a clean, proper solution. The entire module needs to be upgraded.

In case anyone would read this, facing the same issue for building --prod. I created another library in npm ng-twitter-timeline that is working great with angular 7 both prod and non prod. Hope this will help someone there.


Could not load file or assembly QrCodeGenerator

Hi,
Thank you for publishing this library.
When I try to run it on a simple console app, I am getting an exception System.IO.FileLoadException: Could not load file or assembly 'QrCodeGenerator, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=6aa6bd7a159d47c2'. The located assembly's manifest definition does not match the assembly reference.
Steps to reproduce
I am using .net 6.0.401 SDK on Windows 10
mkdir QrCodeGenerator && cd QrCodeGenerator
dotnet new console

Output:
The template "Console App" was created successfully.

Processing post-creation actions...
Running 'dotnet restore' on C:\_poc\QRCodes\New folder\QrCodeGenerator\QrCodeGenerator.csproj...
  Determining projects to restore...
  Restored C:\_poc\QRCodes\New folder\QrCodeGenerator\QrCodeGenerator.csproj (in 74 ms).
Restore succeeded.

dotnet add package Net.Codecrete.QrCodeGenerator

Output:
 Determining projects to restore...
  Writing C:\Users\yanal\AppData\Local\Temp\tmpBB98.tmp
info : X.509 certificate chain validation will use the default trust store selected by .NET.
info : Adding PackageReference for package 'Net.Codecrete.QrCodeGenerator' into project 'C:\_poc\QRCodes\New folder\QrCodeGenerator\QrCodeGenerator.csproj'.
info :   CACHE https://api.nuget.org/v3/registration5-gz-semver2/net.codecrete.qrcodegenerator/index.json
info : Restoring packages for C:\_poc\QRCodes\New folder\QrCodeGenerator\QrCodeGenerator.csproj...
info : Package 'Net.Codecrete.QrCodeGenerator' is compatible with all the specified frameworks in project 'C:\_poc\QRCodes\New folder\QrCodeGenerator\QrCodeGenerator.csproj'.
info : PackageReference for package 'Net.Codecrete.QrCodeGenerator' version '2.0.3' added to file 'C:\_poc\QRCodes\New folder\QrCodeGenerator\QrCodeGenerator.csproj'.
info : Writing assets file to disk. Path: C:\_poc\QRCodes\New folder\QrCodeGenerator\obj\project.assets.json
log  : Restored C:\_poc\QRCodes\New folder\QrCodeGenerator\QrCodeGenerator.csproj (in 75 ms).

Update Program.cs
using System.Text;
using Net.Codecrete.QrCodeGenerator;

var qr = QrCode.EncodeText("Hello, world!", QrCode.Ecc.Medium);
string svg = qr.ToSvgString(4);
File.WriteAllText("hello-world-qr.svg", svg, Encoding.UTF8);

dotnet restore

Output:
 Determining projects to restore...
 All projects are up-to-date for restore.

dotnet run

Output:
Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'QrCodeGenerator, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=6aa6bd7a159d47c2'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)
File name: 'QrCodeGenerator, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=6aa6bd7a159d47c2'
   at Program.<Main>$(String[] args)

What am I missing ?

The issue comes from the name I choose for the console app which is the same name as your assembly : QrCodeGenerator.
If I chose another name I don't have the issue anymore.

Thanks for letting me know. I've just tested it in the last 10 minutes and couldn't reproduce it (as I've chosen a different name).


Revision mismatch, unclear what I should do

Getting this:
% godep save
godep: github.com/stripe/aws-go/gen/dynamodb: revision is 89ffcf19352c19cb983f97e293bed2c05ad805ab, want c16321324a5e5c34ca14ab869ec99cab10ee62cc

what should I do about it? github.com/stripe/aws-go/gen/dynamodb is not being added to Godeps/Godeps.json. I have other things from github.com/stripe/aws-go and they are all at c16321324a5e5c34ca14ab869ec99cab10ee62cc, so not sure where 89ffcf19352c19cb983f97e293bed2c05ad805ab is coming from.

I ran into this as well trying to update dependencies and was able to resolve it in the same way as Dan. I'm not 100% clear why Godep wants a particular (old) revision here when it's trying to run an update to whatever the latest is.

@brandur what project / revision was this on ?

Hey @freeformz, thanks for following up!
The project was heroku/holm, but I've since managed to resolve it.
I played around with Godep more this weekend and I believe that this is related to #138 in that it's caused by pulling in multiple packages that come from the same repo (which fits with Dan's problem as well because this is how aws-go works). To correct what I said previously about Dan's suggestd fix, as time went on I found that this didn't always work for me, what does work with good regularity is run to godep update with the spread operator on the top-level repository as suggested in the other thread:
godep update github.com/stripe/aws-go/...

@brandur Ahh yes, that makes sense. I'm going to close this as a dupe of #138 then.


docs: add blink-emoji.nvim to community sources

Hi there,
Adding blink-emoji.nvim to Community Sources.
It is an adaptation of cmp-emoji to better support blink.cmp.
Thanks for blink :muscle:

Thanks!


Update and lock linting tool versions to keep dev env stable

Description
A recently released version of black is now causing CI runs to fail on other PRs.  This PR updates black (and accepts the changes it wants to make, which seems to be that it wanted to add a line of whitespace in a couple files) along with our other linting tools and pins their versions to keep our development and CI environments stable.  A slightly older dev tool is better than a dev tool that is capable of breaking our CI at any moment and preventing PRs from being merged.
Going forward, we can set up an automated tool like Dependabot that will automatically generate PRs that update our dev tools when new versions are released.

coverage: 74.831%. remained the same
when pulling 7c42ebf74a779e68c7e97da2d343a1ab972552fb on jav/lint-update
into aa87eedf7224cc4a9d83ccf627a562b1e13ea4b5 on master.


Fix Swagger UI colors for better Accessibility

This PR resolves Accessibility issues for form fields of the swagger-ui. Colors used from current theme and validated in contrast checker. I'm leaning towards calling this a bug as the input fields are nearly impossible to see.
Contrast Checker Before:

input fields fail
label fail

Contrast Checker After:

input fields and label fields pass
gray button border pass for user interface components. btn:not(.btn--plain) was overriding the original .swagger .btn, this returns border to the expected behavior.

Examples

Before
After

Before
After

Before
After

Hey @smridge -- Thanks for opening this PR! Out of curiosity did you go through any of the other themes for accessibility or was the focus primarily just on Core Default? Just want to make sure I test the changes properly.

This does indeed do what you set out to do (for the 1 theme). However my gut tells me that we probably should look at extending the theming process to give us more granular control over swagger-ui via the theme (i.e. make it a first class object in the theme rather than raw css) -- I would be interested in the opinion of @develohpanda here.
I spent a little bit of time tonight looking at how the theme generation works and was having some problems, but think I am pretty close to making that work and being able to give guidance if thats the approach other maintainers feel we should take.

The before/after's look great for sure, thanks a tonne for doing this!
My gut feeling says we should avoid adding a first-class specifically for Swagger UI, but figure out a way to use the existing variables where possible. I'd like to avoid this because we might paint ourselves into a corner by adding a proxy that we maintain between Swagger UI's CSS and plugin theme developers. If/when the 3rd party package (Swagger UI) change up their CSS, we'll first need to update our proxy and then have plugin developers update their plugins.
On the other hand, if we keep the raw css around, should we ever replace the Swagger UI preview with a different preview, none of the existing plugins that override Swagger UI styling will work out of the box. But I think that's okay because as it stands, plugins override swagger specific classes already and wouldn't expect other previews to work.

Here's what I think we should explore. We do connect the Swagger UI Preview into our existing theme variables using https://github.com/Kong/insomnia/blob/3b757251c9a09eeec9b392f30b55e2796afa0664/packages/insomnia-app/app/ui/css/components/spec-editor.less. This is by no means complete, but it would be nice to translate the CSS in this PR into this file, using existing variables and connecting them into Swagger UI, like the other existing examples.
This way, we improve how we connect existing theme variables with the Swagger UI, and it should fix contrast issues in all themes, while also not exposing a direct Swagger styling proxy to plugin developers. If this proves too tricky (I'm just ideating at this stage), we can explore other routes too!
How does that sound?

When I was playing with this idea, I was looking to update spec-editor.less -- The one thing I noticed across different specs is that because of the way the actual swagger CSS is, it is set to inherit the color, and any themes that have a closer-to-white color for --color-font (aka default for the foreground in the theme) exhibits the same issue as what this PR aims to improve.
My thought was to expose something like editorFont or something in the style section of the theme, and then update spec-editor.less to use that color.
That being said I couldnt get it all to wire up properly so I may have been doing something wrong.

@reynolek / @smridge, I just pushed 58d616f (#3887), which translates the raw css from the default theme into the spec-editor.less to work with any theme. As I compare this commit with the "after" screenshots in the description, they all seem to still match up. Let me know if this is not the case!

The one thing I noticed across different specs is that because of the way the actual swagger CSS is, it is set to inherit the color, and any themes that have a closer-to-white color for --color-font (aka default for the foreground in the theme) exhibits the same issue as what this PR aims to improve.

@reynolek could you please share some examples where this is the case?

@develohpanda this is much better with everything in the .less file!

Ill pull this down tomorrow and test -- I think I saw material theme as another one that had issues, probably hyper too? Thanks for porting it deeper, helping all the themes as best we can without extra work 👍

Thank you @develohpanda & @reynolek for reworking and testing! Excited for this!

@smridge thanks a tonne for figuring out what things needed to be changed, I was leaning on your initial fix a lot! 🙌🏽
I tried to do the same with the select, but it seems swagger-ui uses a custom icon for the dropdown to be able to position it further from the edge, but that then disconnects it from the font color. Hopefully that's the next thing to fix but it was getting too involved when I attempted.

@smridge Congrats on your first contribution! Don't forgot to submit for your contributor tshirt (details in CONTRIBUTING.md


chore: Add support to build on Mac silicon

Issue
Currently the project cannot be built on Mac silicon. The problem displays itself as missing dependency files during the build process.
Analysis
The issue happens because the build process builds all dependency wheels on the local machine, which builds wheels for the host system architecture.
Example:
0.689 INFO: pip is looking at multiple versions of leapfrogai-api to determine which version is compatible with other requirements. This could take a while.
0.690 ERROR: Could not find a version that satisfies the requirement watchfiles>=0.21.0 (from leapfrogai-api) (from versions: none)
0.690 ERROR: No matching distribution found for watchfiles>=0.21.0

Solution
The solution involves adjusting our build process to build specifically for the linux Docker containers. The way to do this is by moving all wheel creation functions to inside the docker container setup, into the Dockerfiles for each package and out of the Makefile.

@vanakema is working on this issue's branch now. We will likely need to transfer changes/findings to my machine and contribute directly to the branch as forking/committing is prohibitive (GH actions don't have access to all the right secrets and repositories) for non-maintainers.

Completed in #659 and released in #712


test

Describe the bug 📝
Hey guys I saw I typo where can I solve it? ...
Reproduction ▶
No response
Steps to reproduce 🔢
asdf
System Info 💻
a

Used Package Manager 📦
npm
Error Trace/Logs 📃
a
Validations ✅

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
[X] Check that this is a concrete bug. For Q&A join our Community.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hi, that specific issue is here. You have to:

Fork the repo
Clone your fork
Fix the typo
Create a PR

Looking forward to it! Let us know if you have any questions!


Add Invoke-MirrorDirectoryTree

Dervive from XLDPlusPlus.Invoke-ConversionBatch (.psm1)

NB: The above reference to this issue by commit '8c28184', it was meant to reference issue #6

The function is simply responsible for calculating the mirrored path and then showing this mirrored directory location to the client. So for example, a command that wants to replicate a directory tree to an alternative location but also performs some custom operation on all files in the source that will go into the destination, needs to see the source directory and the target directory.
However, the default function could be to simply mirror the directory structure and copy over files. Posiibly these could be indicated by settings inside PassThru: LOOPZ.MIRROR.CREATE-DIR, and  LOOPZ.MIRROR.COPY-FILES. For a client command that want to perform a mapping function on files (may be just some of them), then typically, that command would only require that the directories in the destination to be created but not the iles to be copied over. The client would be presented with source and destination directories

Although this is now working as designed, there's one little point that irks me possibly requiring a redesign/refactor) and that is when using Invoke-MirrorDirectoryTree which is based upon Invoke-TraverseDirectory which in turn is based upon Invoke-forachFsItem, the directory filter is too restrictive. Consider this scenario, we want to defined a filter and copy over the whole directory tree to a new location. However, using the existing implementation, any child directory that does match the filter has any ancestors that do not match the filter, then the child directory will never be reached. This is because Invoke-foreachFsItem applies the filter without consider possible matches further down the directory tree.
Possibly, we need another option to specify that we should specify the Recurse option and allow any directory through the filter regardless of their ancestors.


Upload teal pictograms

Description
While changing the website colours I removed the teal pictograms because they're no longer needed in the web, but some are in the platform. This PR brings them back.
Related Issue(s)

Checklist

[x] I have read the contribution guidelines
[x] I have considered the performance impact of these changes
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

I don't think we strictly need all of them, but can review exactly which ones are used by the app separately.

Ok, I thought it would take too long, if you can provide a list, I'll upload only the ones we need.

Lets merge all to get things fixed and then we can be more selective afterwards.


[feature request]Would you consider to add this one "clusters"

The source link is: https://www.health.govt.nz/our-work/diseases-and-conditions/covid-19-novel-coronavirus/covid-19-current-situation/covid-19-current-cases/covid-19-clusters
(Btw, the format of data was changing so frequently, nice work.)

@shawyunz implemented in 08992a6
Also available here:

https://nzcovid19api.xerra.nz/clusters/json
https://nzcovid19api.xerra.nz/clusters/csv


Update process

Description
Changes proposed in this pull request:

update process (allows user to modify the instance)
e2e unit tests which covers REST API
update OIDC parameters

Related issue(s)

/hold

/unhold


samples: DML with returning support

@rajatbhatta This is as per the standards in NodeJS library, samples are consistent with other samples in the library.


Prometheus grafana

Initial integration of prometheus/grafana into qhub.  I tested it locally and it seems to be working. The kubernetes tests appear to be broken for an unrelated reason.

I'd prefer if we could pull in the helm charts similar to https://github.com/Quansight/qhub/blob/main/qhub/template/{{ cookiecutter.repo_directory }}/infrastructure/modules/kubernetes/services/jupyterhub/main.tf#L6. This still pins the chart to a particular version. Is there a reason that we are copying the entire chart locally?

@costrouc I was following the example of what was done for the clearml (https://github.com/Quansight/qhub/tree/main/qhub/template/{{ cookiecutter.repo_directory }}/infrastructure/modules/kubernetes/services/clearml), but I don't think there is anything preventing us from importing the chart.  @aktech any thoughts for or against putting the entire helm chart in the repo?

@Adam-D-Lewis I agree with @costrouc we shouldn't put helm charts in the repository. ClearML was a special case, as we had to modify the chart. Also, since the last update on ClearML, I'll see if we can remove the ClearML charts as well.

@costrouc ready for a re-review when you are able, thanks!

Do you know why is the Kubernetes tests failing?

It seems like the following files can be removed:

values-monitoring-qhub.yaml
values-original.yaml
Also the diff between the original and overridden files is just following:

❯ diff values-original.yaml values-monitoring-qhub.yaml
628a629,637

grafana.ini:
server:
# The full public facing url you use in browser, used for redirects and emails
domain: github-actions.qhub.dev
root_url: "%(protocol)s://%(domain)s/monitoring"
server_from_sub_path: true
router_logging: true
enable_gzip: true
732c741
<

Which means you can set the particular values via terraform's helm set attribute.

I made the requested changes.

Waiting for the tests to pass here: https://github.com/Quansight/qhub/pull/748 to see if the failed K8s tests in here are relevant or not.

Seems like the tests pass on main, can you check why k8s tests fail? I can rerun again to confirm,

Cyprus says there is insufficient cpu on the node with the additional pods in this PR.  Maybe I can reduce the used cpu or maybe we can use CIrun

Blocked by https://github.com/Quansight/qhub/issues/756

Could you add an entry to the changelog?


Incorrect use of n vs m in logistic regression example?

Describe the bug
In the logistic regression example,
problem = cp.Problem(cp.Maximize(log_likelihood/n - lambd * cp.norm(beta, 1)))

is the n (dimension) here supposed to be m (number of examples) instead? This does not affect the result since n == m here, but just curious.
To Reproduce
A minimal code example that reproduces the bug or unexpected behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Output
If applicable, include program output. If reporting a program crash, please include the entire stack trace.
Version

OS:
CVXPY Version:

Additional context
Add any other context about the problem here.

Thanks for catching this!


Potential deadlock problem with process spawning

During my gardening shift today I've debugged one of the timeouts (see this buildbot failure):
FAILED: none-vm-checked release_x64 standalone/io/http_server_close_response_after_error_test
Expected: Pass
Actual: Timeout
CommandOutput[vm]:

Command[vm]: set DART_CONFIGURATION=ReleaseX64 & out\ReleaseX64\dart.exe --enable_asserts --enable_type_checks --ignore-unrecognized-flags --packages=E:\b\build\slave\vm-win-release-x64-be\build\sdk\.packages E:\b\build\slave\vm-win-release-x64-be\build\sdk\tests\standalone\io\http_server_close_response_after_error_test.dart
Took 0:01:00.017001

Short reproduction command (experimental):
    python tools/test.py -mrelease --checked -t60 standalone/io/http_server_close_response_after_error_test

and got (perhaps the same hang) locally.
The test is running a http server in the main test and starts a subprocess which is then making connections to the server in the parent process.
When stressing the system a lot, I've managed to get the two processes hang with the following stacks:
parent
Thread 6 (Thread 0x7f8e0aad2700 (LWP 21271)):
#0  0x00007f8e097d2a13 in epoll_wait () at ../sysdeps/unix/syscall-template.S:81
#1  0x000000000052a355 in dart::bin::EventHandlerImplementation::Poll (args=<optimized out>) at ../../runtime/bin/eventhandler_linux.cc:397
#2  0x00000000005455ee in dart::bin::ThreadStart (data_ptr=<optimized out>) at ../../runtime/bin/thread_linux.cc:89
#3  0x00007f8e0a4cd184 in start_thread (arg=0x7f8e0aad2700) at pthread_create.c:312
#4  0x00007f8e097d237d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7f8e096d7700 (LWP 21490)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00000000008752ef in dart::Monitor::WaitMicros (this=0x22c2240, micros=<optimized out>) at ../../runtime/vm/os_thread_linux.cc:425
#2  0x0000000000988ae3 in WaitMicros (micros=137, this=<optimized out>) at ../../runtime/vm/lockers.h:177
#3  dart::ThreadInterrupter::ThreadMain (parameters=<optimized out>) at ../../runtime/vm/thread_interrupter.cc:168
#4  0x0000000000874a39 in dart::ThreadStart (data_ptr=<optimized out>) at ../../runtime/vm/os_thread_linux.cc:125
#5  0x00007f8e0a4cd184 in start_thread (arg=0x7f8e096d7700) at pthread_create.c:312
#6  0x00007f8e097d237d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7f8e094d6700 (LWP 21560)):
#0  0x00007f8e0a4d43ad in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x000000000053eaee in dart::bin::FDUtils::ReadFromBlocking (fd=<optimized out>, buffer=<optimized out>, count=<optimized out>) at ../../runtime/bin/fdutils_linux.cc:93
#2  0x000000000052dcd4 in ReadExecResult (this=<optimized out>) at ../../runtime/bin/process_linux.cc:549
#3  dart::bin::ProcessStarter::Start (this=<optimized out>) at ../../runtime/bin/process_linux.cc:344
#4  0x000000000052d9ef in dart::bin::Process::Start (path=<optimized out>, arguments=<optimized out>, arguments_length=<optimized out>, working_directory=<optimized out>, environment=<optimized out>, environment_length=<optimized out>, mode=dart::bin::kNormal, in=0x7f8e094d4d40, out=0x7f8e094d4d38, err=0x7f8e094d4d48, id=0x7f8e094d4d98, exit_event=0x7f8e094d4d50, os_error_message=0x7f8e094d4da0) at ../../runtime/bin/process_linux.cc:767
#5  0x000000000052cf84 in dart::bin::Builtin_Process_Start (args=0x7f8e094d4e50) at ../../runtime/bin/process.cc:150
#6  0x00000000007d754b in dart::NativeEntry::NativeCallWrapperNoStackCheck (args=0x7f8e094d4e50, func=<optimized out>) at ../../runtime/vm/native_entry.cc:163
#7  0x00007f8e0a9527a3 in ?? ()
#8  0x0000000003628900 in ?? ()
#9  0x000000000500000b in ?? ()
#10 0x00007f8e094d4f18 in ?? ()
#11 0x00007f8e094d4e90 in ?? ()
#12 0x00007f8e08341cf1 in ?? ()
#13 0x00007f8e0a995861 in ?? ()
#14 0x00007f8e094d4eb8 in ?? ()
#15 0x00007f8e08367bb7 in ?? ()
#16 0x00007f8e0a992021 in ?? ()
#17 0x00007f8e090f50b1 in ?? ()
#18 0x00007f8e0a992021 in ?? ()
#19 0x00007f8e083b9da1 in ?? ()
#20 0x00007f8e083c2b61 in ?? ()
#21 0x00007f8e094d4f50 in ?? ()
#22 0x00007f8e08366e97 in ?? ()
#23 0x00007f8e0811eac9 in ?? ()
#24 0x00007f8e0811d279 in ?? ()
#25 0x00007f8e0811d8e9 in ?? ()
#26 0x00007f8e0811d739 in ?? ()
#27 0x00007f8e0811d589 in ?? ()
#28 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f8e086c7700 (LWP 23225)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x0000000000875305 in dart::Monitor::WaitMicros (this=0x22c2f00, micros=<optimized out>) at ../../runtime/vm/os_thread_linux.cc:420
#2  0x00000000006bca7a in Wait (millis=0, this=<optimized out>) at ../../runtime/vm/lockers.h:169
#3  dart::BackgroundCompiler::Run (this=<optimized out>) at ../../runtime/vm/compiler.cc:2034
#4  0x00000000009897ad in dart::ThreadPool::Worker::Loop (this=<optimized out>) at ../../runtime/vm/thread_pool.cc:402
#5  0x0000000000989678 in dart::ThreadPool::Worker::Main (args=56886400) at ../../runtime/vm/thread_pool.cc:459
#6  0x0000000000874a39 in dart::ThreadStart (data_ptr=<optimized out>) at ../../runtime/vm/os_thread_linux.cc:125
#7  0x00007f8e0a4cd184 in start_thread (arg=0x7f8e086c7700) at pthread_create.c:312
#8  0x00007f8e097d237d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f8e085c6700 (LWP 28468)):
#0  0x00007f8e0a4d4e44 in __libc_wait (stat_loc=0x7f8e085c5e80) at ../sysdeps/unix/sysv/linux/wait.c:35
#1  0x0000000000530248 in dart::bin::ExitCodeHandler::ExitCodeHandlerEntry (param=<optimized out>) at ../../runtime/bin/process_linux.cc:197
#2  0x00000000005455ee in dart::bin::ThreadStart (data_ptr=<optimized out>) at ../../runtime/bin/thread_linux.cc:89
#3  0x00007f8e0a4cd184 in start_thread (arg=0x7f8e085c6700) at pthread_create.c:312
#4  0x00007f8e097d237d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f8e0aad4780 (LWP 21254)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x0000000000875305 in dart::Monitor::WaitMicros (this=0x7fff6963d0e8, micros=<optimized out>) at ../../runtime/vm/os_thread_linux.cc:420
#2  0x000000000065559a in Wait (millis=0, this=<optimized out>) at ../../runtime/vm/lockers.h:169
#3  Dart_RunLoop () at ../../runtime/vm/dart_api_impl.cc:1703
#4  0x0000000000525bf4 in dart::bin::RunMainIsolate (script_name=<optimized out>, dart_options=0x7fff6963d5f0) at ../../runtime/bin/main.cc:1780
#5  0x0000000000527110 in dart::bin::main (argc=<optimized out>, argv=<optimized out>) at ../../runtime/bin/main.cc:2017
#6  0x0000000000527889 in main (argc=1768149268, argv=0x80) at ../../runtime/bin/main.cc:2055

child
#0  0x0000000000565034 in sys_futex (v3=0, a=<optimized out>, o=<optimized out>, v=<optimized out>, t=<optimized out>, a2=<optimized out>) at ../../third_party/tcmalloc/gperftools/src/base/linux_syscall_support.h:2461
#1  base::internal::SpinLockDelay (w=0x1046ac0 <tcmalloc::Static::central_cache_+9728>, value=<optimized out>, loop=<optimized out>) at ../../third_party/tcmalloc/gperftools/src/base/spinlock_linux-inl.h:81
#2  0x0000000000564f1d in SpinLock::SlowLock (this=<optimized out>) at ../../third_party/tcmalloc/gperftools/src/base/spinlock.cc:118
#3  0x0000000000546ca9 in Lock (this=<optimized out>) at ../../third_party/tcmalloc/gperftools/src/base/spinlock.h:71
#4  tcmalloc::CentralFreeList::RemoveRange (this=0x1046ac0 <tcmalloc::Static::central_cache_+9728>, start=0x7f8e094d4240, end=0x7f8e094d4238, N=1) at ../../third_party/tcmalloc/gperftools/src/central_freelist.cc:248
#5  0x0000000000560eb2 in tcmalloc::ThreadCache::FetchFromCentralCache (this=0x1bab1c0, cl=<optimized out>, byte_size=112) at ../../third_party/tcmalloc/gperftools/src/thread_cache.cc:125
#6  0x0000000000a60c64 in Allocate (this=<optimized out>, size=<optimized out>, cl=<optimized out>) at ../../third_party/tcmalloc/gperftools/src/thread_cache.h:362
#7  do_malloc_small (heap=<optimized out>, size=<optimized out>) at ../../third_party/tcmalloc/gperftools/src/tcmalloc.cc:1193
#8  do_malloc (size=100) at ../../third_party/tcmalloc/gperftools/src/tcmalloc.cc:1200
#9  do_malloc_or_cpp_alloc (size=100) at ../../third_party/tcmalloc/gperftools/src/tcmalloc.cc:1219
#10 tc_malloc (size=size@entry=100) at ../../third_party/tcmalloc/gperftools/src/tcmalloc.cc:1603
#11 0x00007f8e0974a142 in _IO_vasprintf (result_ptr=0x7f8e094d4a30, format=0x7f8e098583b8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", args=args@entry=0x7f8e094d4908) at vasprintf.c:50
#12 0x00007f8e0972c597 in ___asprintf (string_ptr=string_ptr@entry=0x7f8e094d4a30, format=format@entry=0x7f8e098583b8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n") at asprintf.c:35
#13 0x00007f8e09707b52 in __assert_fail_base (fmt=0x7f8e098583b8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f8e0985b5c0 "({ __typeof (self->tid) __value; if (sizeof (__value) == 1) asm volatile (\"movb %%fs:%P2,%b0\" : \"=q\" (__value) : \"0\" (0), \"i\" (__builtin_offsetof (struct pthread, tid))); else if (sizeof (__value) == "..., file=file@entry=0x7f8e0985b588 "../nptl/sysdeps/unix/sysv/linux/x86_64/../fork.c", line=line@entry=141, function=function@entry=0x7f8e09855f75 <__PRETTY_FUNCTION__.11236> "__libc_fork") at assert.c:57
#14 0x00007f8e09707ca2 in __GI___assert_fail (assertion=0x7f8e0985b5c0 "({ __typeof (self->tid) __value; if (sizeof (__value) == 1) asm volatile (\"movb %%fs:%P2,%b0\" : \"=q\" (__value) : \"0\" (0), \"i\" (__builtin_offsetof (struct pthread, tid))); else if (sizeof (__value) == "..., file=0x7f8e0985b588 "../nptl/sysdeps/unix/sysv/linux/x86_64/../fork.c", line=141, function=0x7f8e09855f75 <__PRETTY_FUNCTION__.11236> "__libc_fork") at assert.c:101
#15 0x00007f8e09799105 in __libc_fork () at ../nptl/sysdeps/unix/sysv/linux/x86_64/../fork.c:141
#16 0x000000000052da65 in dart::bin::ProcessStarter::Start (this=<optimized out>) at ../../runtime/bin/process_linux.cc:308
#17 0x000000000052d9ef in dart::bin::Process::Start (path=<optimized out>, arguments=<optimized out>, arguments_length=<optimized out>, working_directory=<optimized out>, environment=<optimized out>, environment_length=<optimized out>, mode=dart::bin::kNormal, in=0x7f8e094d4d40, out=0x7f8e094d4d38, err=0x7f8e094d4d48, id=0x7f8e094d4d98, exit_event=0x7f8e094d4d50, os_error_message=0x7f8e094d4da0) at ../../runtime/bin/process_linux.cc:767
#18 0x000000000052cf84 in dart::bin::Builtin_Process_Start (args=0x7f8e094d4e50) at ../../runtime/bin/process.cc:150
#19 0x00000000007d754b in dart::NativeEntry::NativeCallWrapperNoStackCheck (args=0x7f8e094d4e50, func=<optimized out>) at ../../runtime/vm/native_entry.cc:163
#20 0x00007f8e0a9527a3 in ?? ()
#21 0x0000000003628900 in ?? ()
#22 0x000000000500000b in ?? ()
#23 0x00007f8e094d4f18 in ?? ()
#24 0x00007f8e094d4e90 in ?? ()
#25 0x00007f8e08341cf1 in ?? ()
#26 0x00007f8e0a995861 in ?? ()
#27 0x00007f8e094d4eb8 in ?? ()
#28 0x00007f8e08367bb7 in ?? ()
#29 0x00007f8e0a992021 in ?? ()
#30 0x00007f8e090f50b1 in ?? ()
#31 0x00007f8e0a992021 in ?? ()
#32 0x00007f8e083b9da1 in ?? ()
#33 0x00007f8e083c2b61 in ?? ()
#34 0x00007f8e094d4f50 in ?? ()
#35 0x00007f8e08366e97 in ?? ()
#36 0x00007f8e0811eac9 in ?? ()
#37 0x00007f8e0811d279 in ?? ()
#38 0x00007f8e0811d8e9 in ?? ()
#39 0x00007f8e0811d739 in ?? ()
#40 0x00007f8e0811d589 in ?? ()
#41 0x0000000000000000 in ?? ()

What seems to happen is that

The parent process wants to start the subprocess and forks
The child process hits an assertion in glibc (for some reason assertions are enabled in my system-installed glibc)
The child process wants to allocate memory for building the assertion failure message
The child process calls into tcmalloc for memory allocation and cannot obtain a lock

The only explanation I can think of is that the parent process was holding a tcmalloc lock while another thread forked and the fork'ed child cannot obtain the lock and therefore deadlocks.
The assertion from glibc comes from here:
  if (pid == 0)
    {
      struct pthread *self = THREAD_SELF;

      assert (THREAD_GETMEM (self, tid) != ppid);

There have been bugreports in the past for tcmalloc (see for example here ) but the issue was supposed to be fixed.
The reason why my stress test was hitting the assert in glibc is also unknown.

Trying to reproduce this flaky simarm64-release failure:
FAILED: none-vm release_simarm64 standalone/io/file_read_special_device_test
Expected: Pass
Actual: Timeout
CommandOutput[vm]:
diagnostics: PID 14600 - process
    TID 14600:
    #0  0x00007fe6dde0e404 pthread_cond_wait@@GLIBC_2.3.2
    #1  0x00000000007e0316 dart::Monitor::WaitMicros(long)
    #2  0x00000000008c37e2 dart::ServiceIsolate::Shutdown()
    #3  0x0000000000642206 dart::Dart::Cleanup()
    #4  0x00000000005a6685 Dart_Cleanup
    #5  0x0000000000591036 dart::bin::main(int, char**)
    #6  0x0000000000591369 main
    #7  0x00007fe6dce32f45 __libc_start_main
    #8  0x0000000000596a9b _start
    TID 14601:
    #0  0x00007fe6dcf0ba13 epoll_wait
    #1  0x00000000005d4de5 dart::bin::EventHandlerImplementation::Poll(unsigned long)
    #2  0x00000000005cf119 dart::bin::ThreadStart(void*)
    #3  0x00007fe6dde0a184 start_thread
    #4  0x00007fe6dcf0b37d __clone
    TID 14603:
    #0  0x00007fe6dde0e404 pthread_cond_wait@@GLIBC_2.3.2
    #1  0x00000000007e0316 dart::Monitor::WaitMicros(long)
    #2  0x0000000000635b1d dart::BackgroundCompiler::Run()
    #3  0x00000000008fb0bd dart::ThreadPool::Worker::Loop()
    #4  0x00000000008fb28f dart::ThreadPool::Worker::Main(unsigned long)
    #5  0x00000000007df756 dart::ThreadStart(void*)
    #6  0x00007fe6dde0a184 start_thread
    #7  0x00007fe6dcf0b37d __clone

Command[vm]: DART_CONFIGURATION=ReleaseSIMARM64 out/ReleaseSIMARM64/dart --ignore-unrecognized-flags --packages=/mnt/data/b/build/slave/vm-linux-release-simarm64-be/build/sdk/.packages /mnt/data/b/build/slave/vm-linux-release-simarm64-be/build/sdk/tests/standalone/io/file_read_special_device_test.dart
Took 0:04:30.050350

Short reproduction command (experimental):
    python tools/test.py -mrelease -asimarm64 -t240 standalone/io/file_read_special_device_test

I get a similar stack of the child process:
Thread 1 (process 31207):
#0  0x0000000000563124 in sys_futex (v3=0, a=<optimized out>, o=<optimized out>, v=<optimized out>, t=<optimized out>, a2=<optimized out>) at ../../third_party/tcmalloc/gperftools/src/base/linux_syscall_support.h:2461
#1  base::internal::SpinLockDelay (w=0x1040ac0 <tcmalloc::Static::central_cache_+9728>, value=<optimized out>, loop=<optimized out>) at ../../third_party/tcmalloc/gperftools/src/base/spinlock_linux-inl.h:81
#2  0x000000000056300d in SpinLock::SlowLock (this=<optimized out>) at ../../third_party/tcmalloc/gperftools/src/base/spinlock.cc:118
#3  0x0000000000544d99 in Lock (this=<optimized out>) at ../../third_party/tcmalloc/gperftools/src/base/spinlock.h:71
#4  tcmalloc::CentralFreeList::RemoveRange (this=0x1040ac0 <tcmalloc::Static::central_cache_+9728>, start=0x7fcc7e532250, end=0x7fcc7e532248, N=1) at ../../third_party/tcmalloc/gperftools/src/central_freelist.cc:248
#5  0x000000000055efa2 in tcmalloc::ThreadCache::FetchFromCentralCache (this=0x116f2c0, cl=<optimized out>, byte_size=112) at ../../third_party/tcmalloc/gperftools/src/thread_cache.cc:125
#6  0x0000000000a5c0f4 in Allocate (this=<optimized out>, size=<optimized out>, cl=<optimized out>) at ../../third_party/tcmalloc/gperftools/src/thread_cache.h:362
#7  do_malloc_small (heap=<optimized out>, size=<optimized out>) at ../../third_party/tcmalloc/gperftools/src/tcmalloc.cc:1193
#8  do_malloc (size=100) at ../../third_party/tcmalloc/gperftools/src/tcmalloc.cc:1200
#9  do_malloc_or_cpp_alloc (size=100) at ../../third_party/tcmalloc/gperftools/src/tcmalloc.cc:1219
#10 tc_malloc (size=size@entry=100) at ../../third_party/tcmalloc/gperftools/src/tcmalloc.cc:1603
#11 0x00007fcc7f121142 in _IO_vasprintf (result_ptr=0x7fcc7e532a40, format=0x7fcc7f22f3b8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", args=args@entry=0x7fcc7e532918) at vasprintf.c:50
#12 0x00007fcc7f103597 in ___asprintf (string_ptr=string_ptr@entry=0x7fcc7e532a40, format=format@entry=0x7fcc7f22f3b8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n") at asprintf.c:35
#13 0x00007fcc7f0deb52 in __assert_fail_base (fmt=0x7fcc7f22f3b8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fcc7f2325c0 "({ __typeof (self->tid) __value; if (sizeof (__value) == 1) asm volatile (\"movb %%fs:%P2,%b0\" : \"=q\" (__value) : \"0\" (0), \"i\" (__builtin_offsetof (struct pthread, tid))); else if (sizeof (__value) == "..., file=file@entry=0x7fcc7f232588 "../nptl/sysdeps/unix/sysv/linux/x86_64/../fork.c", line=line@entry=141, function=function@entry=0x7fcc7f22cf75 <__PRETTY_FUNCTION__.11236> "__libc_fork") at assert.c:57
#14 0x00007fcc7f0deca2 in __GI___assert_fail (assertion=0x7fcc7f2325c0 "({ __typeof (self->tid) __value; if (sizeof (__value) == 1) asm volatile (\"movb %%fs:%P2,%b0\" : \"=q\" (__value) : \"0\" (0), \"i\" (__builtin_offsetof (struct pthread, tid))); else if (sizeof (__value) == "..., file=0x7fcc7f232588 "../nptl/sysdeps/unix/sysv/linux/x86_64/../fork.c", line=141, function=0x7fcc7f22cf75 <__PRETTY_FUNCTION__.11236> "__libc_fork") at assert.c:101
#15 0x00007fcc7f170105 in __libc_fork () at ../nptl/sysdeps/unix/sysv/linux/x86_64/../fork.c:141
#16 0x000000000052bb55 in dart::bin::ProcessStarter::Start (this=<optimized out>) at ../../runtime/bin/process_linux.cc:308
#17 0x000000000052badf in dart::bin::Process::Start (path=<optimized out>, arguments=<optimized out>, arguments_length=<optimized out>, working_directory=<optimized out>, environment=<optimized out>, environment_length=<optimized out>, mode=dart::bin::kNormal, in=0x7fcc7e532d50, out=0x7fcc7e532d48, err=0x7fcc7e532d58, id=0x7fcc7e532da8, exit_event=0x7fcc7e532d60, os_error_message=0x7fcc7e532db0) at ../../runtime/bin/process_linux.cc:767
#18 0x000000000052b074 in dart::bin::Builtin_Process_Start (args=0x2dbfc00) at ../../runtime/bin/process.cc:150
#19 0x00000000007d87f5 in dart::NativeEntry::NativeCallWrapperNoStackCheck (args=0x2dbfc00, func=<optimized out>) at ../../runtime/vm/native_entry.cc:163
#20 0x000000000097474f in dart::Simulator::DoRedirectedCall (this=0x2bee700, instr=0x1897090) at ../../runtime/vm/simulator_arm64.cc:1697
#21 0x00000000009723c9 in dart::Simulator::InstructionDecode (this=0x2bee700, instr=0x1897090) at ../../runtime/vm/simulator_arm64.cc:3452
#22 0x0000000000979c2b in dart::Simulator::Execute (this=<optimized out>) at ../../runtime/vm/simulator_arm64.cc:3485
#23 0x0000000000979ec0 in dart::Simulator::Call (this=0x2bee700, entry=<optimized out>, parameter0=<optimized out>, parameter1=<optimized out>, parameter2=<optimized out>, parameter3=<optimized out>, fp_return=<optimized out>, fp_args=<optimized out>) at ../../runtime/vm/simulator_arm64.cc:3576
#24 0x00000000006cc693 in dart::DartEntry::InvokeFunction (function=..., arguments=..., arguments_descriptor=...) at ../../runtime/vm/dart_entry.cc:119
#25 0x00000000006cff3f in raw (this=<optimized out>) at ../../runtime/vm/object.h:244
#26 dart::DartLibraryCalls::HandleMessage (handler=..., message=...) at ../../runtime/vm/dart_entry.cc:559
#27 0x00000000007a1517 in dart::IsolateMessageHandler::HandleMessage (this=<optimized out>, message=0x1883950) at ../../runtime/vm/isolate.cc:570
#28 0x00000000007c9ed6 in dart::MessageHandler::HandleMessages (this=<optimized out>, ml=<optimized out>, allow_normal_messages=<error reading variable: access outside bounds of object referenced via synthetic pointer>, allow_multiple_normal_messages=<error reading variable: access outside bounds of object referenced via synthetic pointer>) at ../../runtime/vm/message_handler.cc:217
#29 0x00000000007ca3df in dart::MessageHandler::TaskCallback (this=0x2bca1a0) at ../../runtime/vm/message_handler.cc:373
#30 0x0000000000997b5d in dart::ThreadPool::Worker::Loop (this=<optimized out>) at ../../runtime/vm/thread_pool.cc:402
#31 0x0000000000997a28 in dart::ThreadPool::Worker::Main (args=46146112) at ../../runtime/vm/thread_pool.cc:459
#32 0x0000000000879579 in dart::ThreadStart (data_ptr=<optimized out>) at ../../runtime/vm/os_thread_linux.cc:125
#33 0x00007fcc7fea4184 in start_thread (arg=0x7fcc7e534700) at pthread_create.c:312
#34 0x00007fcc7f1a937d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

/cc @rmacnak-google @zanderso

Fundamentally this turned out to be a bug in the linux kernel, which hasn't been fixed yet. There is a patch, but it doesn't seem like this has been merged yet.
What happens is:

parent process fork()s
fork() implementation takes all tcmalloc locks (will be separately released in parent/child later on)
fork() implementation makes clone syscall with pointer to pid which should be updated
kernel makes COW-based fork of process
kernel tries to update the pid ad the pointer given by the clone syscall
kernel needs to COW that page which it can't due to OOM
kernel ignores error & clone returns
child process hits the 'tid != ppid' assert (because pointer hasn't been updated)
child wants to build an assertion message, which requires malloc
tcmalloc sees that all locks are taken and hangs

We'll try to verify that this also happens on the bot.
We'll also try to identify tests which allocate a lot of memory and could cause OOM (and change these test)

After starting to capture stacks in leaked dart processes in taskkill.py, it revealed this buildbot failure:
  Stack:
    PID 30836 - process
    TID 30836:
    #0  0x00000000005f9d7c base::internal::SpinLockDelay(int volatile*, int, int)
    #1  0x00000000005f9c3c SpinLock::SlowLock()
    #2  0x00000000005fc368 tcmalloc::CentralFreeList::InsertRange(void*, void*, int)
    #3  0x00000000005f73a2 tcmalloc::ThreadCache::ReleaseToCentralCache(tcmalloc::ThreadCache::FreeList*, unsigned long, int)
    #4  0x00000000005f744a tcmalloc::ThreadCache::ListTooLong(tcmalloc::ThreadCache::FreeList*, unsigned long)
    #5  0x0000000000adbe94 tc_cfree
    #6  0x00007f9d8afdb1d0 __run_exit_handlers
    #7  0x00007f9d8afdb1f5 exit
    #8  0x00000000005db73c dart::bin::Process::TerminateExitCodeHandler()
    #9  0x0000000000591171 dart::bin::main(int, char**)
    #10 0x00000000005914a9 main
    #11 0x00007f9d8afc0f45 __libc_start_main
    #12 0x0000000000596bdb _start

Which is very similar to the failrue above just that it doesn't seem to be happening in the same place (i.e. not at fork()). But that might also be the case because glibc on the bots doesn't have assert()s enabled.

Marked https://github.com/dart-lang/sdk/issues/28188 duplicate of this one.

Since this CL landed the vm builders seem very green and I haven't noticed any of the flaky timeouts of this kind. Closing this issue therefore.


Nuxt Umami is incompatible with Umami (v2) Cloud

Hi,
Where can i find the Host value for the Umami Cloud ?
Thanks.

Hi @kaboume
The host for Umami Cloud is the same as the script URL. You can even copy-paste the full script URL.

Thanks for your reply.
But it doesn't work for me.
nuxt.config.js :
  extends: ['nuxt-umami'],
  appConfig: {
    umami: {
      version: 2,
    },
  },

.env :
NUXT_PUBLIC_UMAMI_HOST="https://analytics.umami.is/script.js"
NUXT_PUBLIC_UMAMI_ID="xxx-xx-xx-xx-xxx"

I'v tried also with :
NUXT_PUBLIC_UMAMI_HOST="https://analytics.umami.is/script.js"
or
NUXT_PUBLIC_UMAMI_HOST="https://analytics.umami.is"
But not better.

Hi @kaboume. Yeah, you're right. I did a little digging and... this lib is no longer compatible with Umami (v2) Cloud.
The error you're getting is not because of the host, the Nuxt Umami is sending data incompatible with the Umami version.
I'll update the Readme to reflect that.

Thanks.
Si what I have to do?

Sorry :pray:
v1 should work (since it's just a script loader).
https://github.com/ijkml/nuxt-umami/tree/main

@ijkml : it doesn't work any better :(

ah sorry I thought you just had to put 1 instead of 2 in nuxt.config.
In fact, I have to install the previous version...

Oh yeah, :+1: sorry

When should I switch to version 2 of the package so as not to end up with an outdated version 1?

v1 is pretty complete, create an issue if you find a bug or something. v2 is restricted to Umami 1.
I'd have to work on v3 to support Umami 2, but for now, no plans, not until Umami 2 is released and stable.

Hey @ijkml, what do you mean by Umami 2 being released and stable? It is already in v2.1.0, and the docs should be updated?
I understand from [here] that it's not only Umami (v2) Cloud you're not compatible with, but also Umami (v2) Open Source (self-hosted). At least that's what my app seems to indicate as, after upgrading to Umami 2.1.0 on my server, nuxt-umami is complaining with a 404 error on not finding /api/collect. You may want to adjust slightly your readme to make this even clearer?

As of the time of this issue, Umami 2 was still in beta. Umami v2 or Umami Cloud in this context mean the same thing, sorry if you got that mixed up.
Lots of breaking changes, (see the tracker functions page in the docs), it would require a full rewrite.
So, no, Nuxt Umami v2 doesn't support Umami 2.

Thanks for your reply. Would be open for a contrib?

Would appreciate that!

thanks for the suggestion but i don't have the technical level to do that :)


KAFKA-14491: [7/N] Enforce strict grace period for versioned stores

The RocksDB-based implementation for versioned key-value stores introduced in https://github.com/apache/kafka/pull/13188 has a well-defined "history retention" parameter which specifies how far back in time (relative to the current observed stream time) reads may take place, but there is no well-defined equivalent (aka "grace period") for how far back in time writes will be accepted. Instead, there is an implicit grace period whereby the store accepts all writes which affect valid reads. This doesn't quite work, though, because it requires infinite tombstone retention when the latest value for a particular key is a tombstone -- if the latest value for a key is a very old tombstone, we can’t expire it because if there’s an even older non-null put to store later, then without the tombstone we’ll accept this write as the latest value for the key, even though it isn't.
In light of this, this PR changes the versioned store semantics to define an explicit "grace period" property. (KIP-889 has been updated accordingly.) For now, grace period will always be equal to the history retention, though in the future we can introduce a new KIP to expose options to configure grace period separately.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

One more thought: should we add verification about the "droppedRecordSensor" into all unit tests that drop records?

Included this test update in the latest commit. I believe I've addressed/responded to all outstanding comments with the latest commit.


Revert "Separating shard manager and shard store (#3573)"

This reverts commit 99b59b96ad45a10439799fa4ed8c1b4dc8475ece.

Coverage increased (+0.04%) to 68.938% when pulling 3eecc5b6c8adbc7f288c58e17ca192a4a9974f46 on andrewjdawson2016:revertShardSeparate into 64e81b6c9d6558ae390368867399ca9d19b29099 on uber:master.


Update the repo URL for MKL.jl

Changing the URL since we moved MKL.jl to a new org. Is this the only place this is necessary? I am mainly doing this so that I can then use the web registrator on juliahub.com (which otherwise complains).
cc @giordano @DilumAluthge

Yeah this should be the only place you need to change it.

What does this error mean?

Oh yeah that's just because we merged it manually.
It shouldn't even error in this case. I'll try to fix the config.


retrieve current user information and display it.

Description

we create a userSlice that makes use of the usersAPI to store the user information in the state
Related issues

Fixes #11
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Changes Made

created userslice to call users API endpoint for current user and display the name
add logout button
fix 403 unit test for Error: Actions must be plain objects. Use custom middleware for async actions. by adding thunk
unit test for store to retrieve to correct user
fix integration test to match develop branch of backend
upload video and screenshots artifacts on cypress failure

Testing

[x] Unit Tests
[x] Integration Tests

Mentions

needs the develop branch of backend
made the integration tests with cypress follow the develop branch, not sure the right choice any opinions ?

will merge as is and if anything comes up will create a hotfix


Support multiline ES6 export ... from syntax

Description of problem
When parsing ES6 code of the form export ... from, the compiler fails to generate the correct goog.require statement.
Steps to reproduce
Given the following files:
//greet.js
export default function greet(m) {
    document.write("\nHello, " + m);
};

//hello.js
export {
    default as helloGreet
} from "./greet";

Execute:
java -jar $JAR -O BUNDLE --formatting PRETTY_PRINT --module_resolution NODE --js_output_file=/dev/stdout -W VERBOSE --debug --dependency_mode STRICT --entry_point hello.js greet.js hello.js | grep -A 11 -E 'greet|hello'

Expected outcome
Closure compiler should detect greet.js as a dependency of hello.js and output them both under strict dependency mode.
//greet.js
$jscomp.registerAndLoadModule(function($$require, $$exports, $$module) {
  "use strict";
  Object.defineProperties($$exports, {"default":{enumerable:true, get:function() {
    return greet;
  }}});
  function greet(m) {
    document.write("\nHello, " + m);
  }
}, "greet.js", []);

//hello.js
$jscomp.registerAndLoadModule(function($$require, $$exports, $$module) {
  "use strict";
  Object.defineProperties($$exports, {helloGreet:{enumerable:true, get:function() {
    return module$greet["default"];
  }}});
  var module$greet = $$require("greet.js");
}, "hello.js", ["greet.js"]);

Actual outcome
JsFileParser fails compute the list of requires.
//hello.js
$jscomp.registerAndLoadModule(function($$require, $$exports, $$module) {
  "use strict";
  Object.defineProperties($$exports, {helloGreet:{enumerable:true, get:function() {
    return module$greet["default"];
  }}});
  var module$greet = $$require("greet.js");
}, "hello.js", ["greet.js"]);

Workaround/patches
Condensing the export to a single line works around the issue but may be infeasible for third party libs (e.g. from NPM).
Avoiding JsFileParser also fixes the problem:
diff --git a/src/com/google/javascript/jscomp/CompilerInput.java b/src/com/google/javascript/jscomp/CompilerInput.java
index 62609562b..4e4d3e3dc 100644
--- a/src/com/google/javascript/jscomp/CompilerInput.java
+++ b/src/com/google/javascript/jscomp/CompilerInput.java
@@ -285,7 +285,7 @@ public class CompilerInput extends DependencyInfo.Base implements SourceAst {

     // If the code is a JsAst, then it was originally JS code, and is compatible with the
     // regex-based parsing of JsFileParser.
-    if (ast instanceof JsAst && JsFileParser.isSupported()) {
+    if (false && ast instanceof JsAst && JsFileParser.isSupported()) {
       // Look at the source code.
       // Note: it's OK to use getName() instead of
       // getPathRelativeToClosureBase() here because we're not using

Analysis
Due to the line parsing nature of JsFileParser, it fails to look ahead when faced with a line that starts with export (or import) but doesn't contain a semicolon. In fact, under shortcut mode, it appears to halt the parser.

Also, there is no output using -O ADVANCED... but that could just be me not understanding how to use the compiler.

@jplaisted I think I've heard you mention this export ... from syntax before, but I didn't think we supported it.
Do you know what the status of this feature is?

We support export {name} from but not export * from. However neither has anything to do with goog.require.
The issue here is that JsFileParser is regex based and doesn't detect multiline import or export statements, as @au-phiware mentoined.
@au-phiware fyi the output you've pasted is the "bundled" output. A "bundle" is the minimal transformations needed to get all input files in one output file. ES6 modules can't be bundled so we tranform them to CommonJS-like modules (the above output). That output is not meant to be fed back into the compiler. It also doesn't emit goog.requires to avoid any dependency on Closure Library.

FYI @shicks

Sorry, regex is a red herring. It just happens to parse files line by line.


Unclarity regarding restart on failed readiness checks

This is a Bug Report

Problem:
The documentation on readiness probes is unclear. It describes how to configure readiness for a single container, but when it comes to the restart behavior, it's not exactly clear, if just the container or the complete pod is restarted:

the documentation says: [...] and the containers have been killed and recreated.
but then kubectl get pod ... command is used to show that the restart counter of the pod has been increased.

It is not clear in the documentation, if this restart counter relates to all containers in the pod (meaning that all containers in that pod have been restarted due to failed readiness checks of a single container in that pod) or just a single container in the pod. In the example it does not matter because the pod consists of just a single container.
Proposed Solution:
Please clarify if a single failing container causes a restart of the whole pod or just of the affected container, and how it relates to the RESTARTS field of the output of the kubectl get pod command.
Page to Update:
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/

/remove-kind bug
This is a request to improve docs; the existing docs are unclear, not wrong.
/language en
/sig node
/triage accepted

/remove-lifecycle stale

I would like to work on it.

/assign


支持markdown超链接

目前对于本地引用的图片，仅支持wiki链接，不支持markdown标准语法超链接
for locally images，only wiki links are supported，markdown standard syntax links are not supported

https://help.obsidian.md/How+to/Format+your+notes#Resizing+images
like this，
Example of this above image resized to 100 pixels wide:

Hello, is there anything that can be done about this? It would be great if this plugin also supported images using markdown standard syntax.

Hello, is there anything that can be done about this? It would be great if this plugin also supported images using markdown standard syntax.

no, I have no solution for this question. now Ichange the css to make the image shrink 30% ,and I use the plugin "image toolkit" to view the images

Fixed in version 1.0.14.


Consider dropping support for Mac (saves dev time)

Re https://devblogs.microsoft.com/visualstudio/visual-studio-for-mac-retirement-announcement/#:~:text=Visual Studio for Mac will,longer be serviced or maintained.

It's not VS Classic, it's VS Code :D
We'll have VS Classic hopefully soon, but it's not this project.


RT Capabilities Part 1 - YARP Logger Device

The first part of the real-time capabilities functionality for the YARP logger device. This PR is a smaller portion of this original pull request for the logger device and just contains the bare-bone software required to get real-time logging up and running. The original pull request for the logger device will be broken up into this pull request and others to simplify the merge process

The macOS failure is:
2024-03-11T09:02:15.9093100Z Error: The `brew link` step did not complete successfully
2024-03-11T09:02:15.9095690Z The formula built, but is not symlinked into /usr/local
2024-03-11T09:02:15.9099740Z Could not symlink<EMAIL_ADDRESS>2024-03-11T09:02:15.9103080Z Target<EMAIL_ADDRESS>2024-03-11T09:02:15.9105240Z already exists. You may want to remove it:
2024-03-11T09:02:15.9107510Z   rm<EMAIL_ADDRESS>2024-03-11T09:02:15.9109480Z
2024-03-11T09:02:15.9110010Z To force the link and overwrite all conflicting files:
2024-03-11T09:02:15.9111330Z   brew link --overwrite node@18
2024-03-11T09:02:15.9111960Z
2024-03-11T09:02:15.9112310Z To list all files that would be deleted:
2024-03-11T09:02:15.9113650Z   brew link --overwrite node@18 --dry-run
2024-03-11T09:02:15.9114480Z

it is unrelated to the PR, and kind the npm equivalent of https://github.com/actions/setup-python/issues/577 .
@nicktrem You can safely ignore this failure.
@GiulioRomualdi @S-Dafarra For me we can safely disable homebrew CI.

Hi @nicktrem! Thanks for iterating! I'm going to merge the PR well done!
PS; sorry for the delay 😭

Great work all!


Market order & Toast issues with embedded wallet

The Chore
Have observed two issues:
Tasks

[x] When making a market order it does not seem to send the order at all and ask me to approve
[x] When making a limit order I can get it to send but the toast stays stuck on orange approval step and never moves to green even though I can see it hhas gone through >> NOTE I've seen some of these working now in FG, so maybe it is not a problem.

Additional details / background info

Both of these are fixed now


SandBoxMouseEvent and ResizeEvent

SandBoxMouseEvent and ResizeEvent

Again, there were some fields that aren't being used, but I will accept this for now.


(vsCode 1.23.0) Beautify formatter on save takes precedent over Prettier

It seems that with the most recent update to vsCode (1.23.0), Beautify's formatOnSave feature is preventing Prettier from running properly on save.
https://github.com/prettier/prettier-vscode/issues/439
https://github.com/prettier/prettier-vscode/issues/440

I only use Beautify from the Cmd+P list, so I added this to my user settings to get around this issue:
"beautify.ignore": "**/*"


i18n(hi): update nav.ts

Description (required)

updates nav.ts from the greate Sidebar reorganized PR

Related issues & labels (optional)

Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

hi
nav.ts
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Replace font awesome with unicode icons

Thanks, I missed those because they used a slightly different syntax I didnt know to look for.


Updated dotenv.gradle

Added an option to check for the "ENVFILE" var in the System properties, simply to allow more flexibility when running react-native-config directly from android studio with flavors

Great one! I need to explore this setup with android studio + flavors, seems analogue to xcode + schemes. Thank you!


--add-metadata has some weird behavior

Description of your issue, suggested solution and other information
M'kay, so apparently --add-metadata involves rewriting the ENTIRE FILE?
youtube-dl -iw --no-continue $URL -f bestvideo+bestaudio --add-metadata --merge-output-format mp4 -o "[%(upload_date)s] %(title)s" --prefer-ffmpeg --download-archive archive.txt --postprocessor-args "-strict -2 -threads 8 -c:v libx264 -crf 18 -preset veryslow -c:a aac -b:a 192k -movflags +faststart" gives me an output of example.mp4 , fully playable, without metadata. Then I see another copy, example.temp.mp4, that slowly grows to the size of example.mp4 and then replaces it. The output of youtube-dl during all of this is the standard [ffmpeg] Adding metadata to 'example.mp4'
Any way to fix this?

That isn't possible with ffmpeg; it always needs to construct a new file with the applied changes.

This behavior is explicitly requested by you: --postprocessor-args is passed to any postprocessor involved including one that adds metadata. Remove any re-encoding from --postprocessor-args and it will be as fast as adding metadata.


Issue for 1.10 regarding DimensionType

after downloading a copy of the mod, and looking trough the code, I cannot find where the dimension is registered to the DimensionType enumclass.
am i looking in the wrong places ?
One of my mods uses the DimensionType as a way to retrieve dimension names.
I'd love to resolve this issue !

I belive they are registered here: https://github.com/zmaster587/AdvancedRocketry/blob/MC1_10/src/main/java/zmaster587/advancedRocketry/dimension/DimensionManager.java#L49
I'm not sure how much it'll help as all the planets share the same type and therefore the same name.
Reason for this is because planets are dynamically created and destroyed and because DimensionType is an enum and every time the player closed and opened a world I'd have to create a whole new set of planets.  This would result in a memory leak, which I'd really like to avoid.  If needed I can try to put together some way to retrieve names in a better fashion other than the DimensionProperties class

no, that's okay. i'm just listing all the places people have placed down telepads, which is independant from any dimension, apart from the retrieval of the dimension's name, for showing telepads per dimension.
thanks for that information ! now I know that the problem is more likely to be on my side.


react-step-4 tutorial issues

Detailed description
I will give a few examples here:
.info-card__heading {
  @include type-style('productive-heading-03');
}

raises an error when running, needs to be corrected to
.info-card__heading {
  @include carbon--type-style('productive-heading-03');
}

another one for the html
cds--col-md-4

needs to be corrected to
bx--col-md-4

The same issues are in the entire tutorial, I did raise one PR but I have some CI failure I dunno how to solve so for the rest I am raising just bugs :)

@JuliusKoronci Thanks for reporting this! We're working to update the tutorial right now and tracking it in https://github.com/carbon-design-system/carbon/issues/10991.
Will close this in favor of that one, we'll include this as part of that update. Thank you again!

Duplicate of https://github.com/carbon-design-system/carbon/issues/10991


[BUG] exc_type and exc_traceback have been removed from Python 3.11 in 4th alpha

Hello,
there is a new incompatibility between Cython and Python 3.11.0a4.
The interpreter state’s representation of handled exceptions (a.k.a exc_info, or _PyErr_StackItem)
now has only the exc_value field, exc_type and exc_traceback have been removed as
their values can be derived from exc_value.

(Contributed by Irit Katriel in bpo-45711.)
Full traceback:
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c: In function â€˜__Pyx_PyErr_GetTopmostExceptionâ€™:
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c:19461:21: error: â€˜_PyErr_StackItemâ€™ {aka â€˜struct _err_stackitemâ€™} has no member named â€˜exc_typeâ€™
19461 |     while ((exc_info->exc_type == NULL || exc_info->exc_type == Py_None) &&
      |                     ^~
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c:19461:51: error: â€˜_PyErr_StackItemâ€™ {aka â€˜struct _err_stackitemâ€™} has no member named â€˜exc_typeâ€™
19461 |     while ((exc_info->exc_type == NULL || exc_info->exc_type == Py_None) &&
      |                                                   ^~
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c: In function â€˜__Pyx__ExceptionSaveâ€™:
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c:19475:21: error: â€˜_PyErr_StackItemâ€™ {aka â€˜struct _err_stackitemâ€™} has no member named â€˜exc_typeâ€™
19475 |     *type = exc_info->exc_type;
      |                     ^~
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c:19477:19: error: â€˜_PyErr_StackItemâ€™ {aka â€˜struct _err_stackitemâ€™} has no member named â€˜exc_tracebackâ€™
19477 |     *tb = exc_info->exc_traceback;
      |                   ^~
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c: In function â€˜__Pyx__ExceptionResetâ€™:
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c:19491:24: error: â€˜_PyErr_StackItemâ€™ {aka â€˜struct _err_stackitemâ€™} has no member named â€˜exc_typeâ€™
19491 |     tmp_type = exc_info->exc_type;
      |                        ^~
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c:19493:22: error: â€˜_PyErr_StackItemâ€™ {aka â€˜struct _err_stackitemâ€™} has no member named â€˜exc_tracebackâ€™
19493 |     tmp_tb = exc_info->exc_traceback;
      |                      ^~
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c:19494:13: error: â€˜_PyErr_StackItemâ€™ {aka â€˜struct _err_stackitemâ€™} has no member named â€˜exc_typeâ€™
19494 |     exc_info->exc_type = type;
      |             ^~
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c:19496:13: error: â€˜_PyErr_StackItemâ€™ {aka â€˜struct _err_stackitemâ€™} has no member named â€˜exc_tracebackâ€™
19496 |     exc_info->exc_traceback = tb;
      |             ^~
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c: In function â€˜__Pyx__GetExceptionâ€™:
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c:19578:28: error: â€˜_PyErr_StackItemâ€™ {aka â€˜struct _err_stackitemâ€™} has no member named â€˜exc_typeâ€™
19578 |         tmp_type = exc_info->exc_type;
      |                            ^~
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c:19580:26: error: â€˜_PyErr_StackItemâ€™ {aka â€˜struct _err_stackitemâ€™} has no member named â€˜exc_tracebackâ€™
19580 |         tmp_tb = exc_info->exc_traceback;
      |                          ^~
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c:19581:17: error: â€˜_PyErr_StackItemâ€™ {aka â€˜struct _err_stackitemâ€™} has no member named â€˜exc_typeâ€™
19581 |         exc_info->exc_type = local_type;
      |                 ^~
/builddir/build/BUILD/cython-0.29.26/Cython/Compiler/Scanning.c:19583:17: error: â€˜_PyErr_StackItemâ€™ {aka â€˜struct _err_stackitemâ€™} has no member named â€˜exc_tracebackâ€™
19583 |         exc_info->exc_traceback = local_tb;

Downstream report: https://bugzilla.redhat.com/show_bug.cgi?id=2042360

I would rather have this fixed in the master branch first and wait with a release in 0.29.x until there is at least a beta release of CPython 3.11. I'd like to avoid churn in the legacy 0.29.x branch.

Duplicate https://github.com/cython/cython/issues/4500


Small amounts of text - what exactly is small?

>This API is intended to store small amounts of text. Performance may be slow if you try to use it to store large amounts of text.
Wondering what exactly means small amounts of text

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

ID: da75050f-bfda-4792-40d9-b9a25d649d3e
Version Independent ID: 5c44f996-765b-f6e4-c807-9446c534d50b
Content: Xamarin.Essentials: Secure Storage - Xamarin
Content Source: docs/essentials/secure-storage.md
Product: xamarin
GitHub Login: @jamesmontemagno
Microsoft Alias: jamont

I guess you can store quite a lot but it will slow down the app since crypt/decrypt takes more CPU time the more data to be processed.


Fixes #RHIROS-1140 - sample test pull-request

PR Title :boom:
Please title this PR with a summary of the change, along with the JIRA card number.
Suggested formats:

Fixes/Refs #RHIROS-XXX - Title
RHIROS-XXX Title

Feel free to remove this section from PR description once done.
Why do we need this change? :thought_balloon:
Please include the context of this change here.
Documentation update? :memo:

[ ] Yes
[ ] No

Security Checklist :lock:
Upon raising this PR please go through RedHatInsights/secure-coding-checklist
:guardsman: Checklist :dart:

[ ] Bugfix
[ ] New Feature
[ ] Refactor
[ ] Unittests Added
[ ] DRY code
[ ] Dependency Added
[ ] DB Migration Added

Additional :mega:
Feel free to add any other relevant details such as links, notes, screenshots, here.

Codecov Report
Patch coverage has no change and project coverage change: -1.22 :warning:

Comparison is base (abd1163) 73.42% compared to head (d639ddc) 72.21%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #325      +/-   ##
==========================================
- Coverage   73.42%   72.21%   -1.22%
==========================================
  Files          27       27
  Lines        1351     1346       -5
==========================================
- Hits          992      972      -20
- Misses        359      374      +15

Flag
Coverage Δ

unittests
72.21% <ø> (-1.22%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

\retest

/retest


2.5.0+ Crash with Amecs

Minecraft Version: 1.16.2

Cardinal Components API Tested Version: 2.5.0, 2.5.1 and 2.5.2 (works with 2.4.2 or below)

Amecs Tested Version: 1.0.2 and 1.0.3

Crash: https://gist.github.com/Rongmario/8912ebe70089a4274e650f1dce969a84
Edit: this was in dev, have not tested outside dev.

Try updating Amecs, latest version is 1.3.1 for MC1.16.1. I can confirm that both run together outside a development environment.

My bad, did not specify that Amecs version was for the API not the mod, the API I believe has a different versioning, latest is 1.0.3. https://maven.siphalor.de/de/siphalor/amecsapi-1.16/

Already reported to Siphalor, and we've tested it where it does not crash by itself. Do also check Mouse Wheelie for an Amecs project that runs successfully in dev and has latest Amecs.


Add default/allowed ImageVersion to ConfigMap

What this PR does / why we need it:

Add defaultImageVersion and allowedImageVersions to configmap
Regenerate API Docs
ConfigMap structs should not be generated and surfaced on API Docs

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes https://github.com/kubeflow/kfserving/issues/416, https://github.com/kubeflow/kfserving/issues/334
Update ConfigMap in 0.2.0 release manifests with default/allowed image versions.

This change is

/lgtm
/approve

/unhold

/hold cancel

/retest

/lgtm


lsquic certificate size

Hello, this is a question, not an issue. I am able to make successful connections with rsa2048 but with a higher bitesize, I am not able to establish a connection. Is there a size limit defined in lsquic? and if so where is it located?
Thank you

Thank you for the bug report!  I have reproduced the issue.  It affects gQUIC versions only; IETF QUIC versions are fine.

Thank you for your reply. So how do I use IETF QUIC? I can specify version = Q050 for google QUIC but I do not see the syntax for IETF versions.

In http_client (I assume you mean http_client), you can do -o version=h3-31 (for example).  Also, if you omit the option altogether, the engine will pick the highest version -- which is also "h3-31".

Awesome, so what about using open quantum safe boringssl (https://github.com/open-quantum-safe/boringssl). I was trying to transfer a post-quantum algorithm cert but I get the error "[ERROR] SSL_CTX_use_PrivateKey_file failed". Am I generating the key and cert wrong or is it a transfer size limit?

The certificate size bug will be fixed in the next release.
The SSL_CTX_use_PrivateKey_file failure is in BoringSSL, it's likely not related to anything lsquic is doing.

Fixed in 2.22.0 -- closing.


Add multiprocessing

Add multiprocessing to reduce execution time

After experimentation, multiprocessing is not relevant. Bottleneck induced by download


#51 ensure spec file directory

Fixes #51.
Ensuring spec output file directory with mkdirp.

Coverage increased (+0.2%) to 92.487% when pulling 1990b5377c863b44d7d807eb43801d6a14a185df on maxiejbe:#51-ensure-spec-file-directory into c5c192dbaeb491b6d0e2657ddea743089f6dc075 on mpashkovskiy:master.

Also, you can add "fixes #51" to the PR description to automatically close that issue once this is merged.
Otherwise, lgtm!

Also, you can add "fixes #51" to the PR description to automatically close that issue once this is merged.
Otherwise, lgtm!

Great tip! Done

Thank you @maxiejbe for PR and @kiprasmel for review. LGTM

v1.0.38 is published, please confirm that it works.

@mpashkovskiy Working great! Generating directory when supplying specOutputPath: './docs/api_docs.json'


KMS key alias does not work when specified in config

If I replace the keyArn property in the secrets YAML file with the alias of the KMS key, creation of new secrets fails:
keyArn: 'arn:aws:kms:us-east-1:xxxxxxxx:alias/my-test-key'

Serverless: Encrypting using key my-test-key found in secrets.yml
Serverless: ServerlessError: Invalid keyId

Looks like it's just taking the value after the last / which works fine when its the Id of a Key but when it's an alias it drops the "alias/" from the value its using which is what results in your "Invalid keyId" error.
arn:aws:kms:us-west-2:1234567890:alias/my-alias
arn:aws:kms:us-west-2:1234567890:key/1111-2222-333-444-5555555
https://github.com/nordcloud/serverless-kms-secrets/blob/master/index.js#L130
it would be nice if the plugin supported storing the alias in the config file keyArn when that's what was used on the command line to generate the encrypted values.


Add constants for sysconf(3) and pathconf(3)

@bors: r+
Thanks!

:pushpin: Commit fa276b0 has been approved by alexcrichton

:umbrella: The latest upstream changes (presumably #625) made this pull request unmergeable. Please resolve the merge conflicts.

@bors: r+

:pushpin: Commit 8961292 has been approved by alexcrichton

:hourglass: Testing commit<PHONE_NUMBER>36a3ad379ad4a951c9aa6517e9cd32 with merge 4dd672704ab2eb0be98a56bba83563f1ad11578b...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 4dd672704ab2eb0be98a56bba83563f1ad11578b to master...


Can't display image in TextView and MarkwonView

I couldn't find a way to display an image in TextView using Markwon. The README says "Images (requires special handling)" but I couldn't find the doc on that.
Currently, in place of an image, it only shows the alternate text of the image.
Please help. Thank you very much.

Hey @thawatchai !
Yeah, image loading is implementaed in a different artifact (it's far from perfect, but it does support GIF & SVG):
compile 'ru.noties:markwon-image-loader:1.0.5'

Sample application uses it, so you can use it for a reference. The key is the provide AsyncDrawableLoader during SpannableConfiguration creation:
final SpannableConfiguration configuration = SpannableConfiguration.builder(context)
        .asyncDrawableLoader(loader)
        .build();

Which can be created like this:
AsyncDrawableLoader.builder()
    .client(OkHttpClient)
    .executorService(ExecutorService)
    .resources(Resources)
    .build();

Hi @noties. It works now. This is what I use in my Kotlin code
            val loader =
                AsyncDrawableLoader.builder().client(OkHttpClient())
                    .executorService(Executors.newCachedThreadPool())
                    .resources(Resources.getSystem()).build()
            val configuration = SpannableConfiguration.builder(act)
                .asyncDrawableLoader(loader)
                .build()

            Markwon.setMarkdown(contentTextView, configuration, markdown)

Do I use the correct executor and resource?
BTW, is there a way that I can make the image resize to the full width of the TextView?

Hey @thawatchai !
Yeah, they should be fine although I would recommend using your application's resources (it is used to determine the density when displaying Bitmaps).
To control the size of an image there 2 ways:

if you control the markdown you can wrap an image in an HTML <img src="{href}" width="100%"> element. This will scale the image (keeping the ratio) to fill the textView canvas width

if you do not control the markdown (it is user submitted) you can use the ImageSizeResolver.

SpannableConfiguration.builder()
    .imageSizeResolver(ImageSizeResolver);

There is a ready to be used implementation: ImageSizeResolverDef which can be used as a parent for your own implementation. For example (if an image has no size specified -> fit the width of a TextView):
public class ImageSizeResolverFitWidth extends ImageSizeResolverDef {

    @NonNull
    @Override
    public Rect resolveImageSize(
            @Nullable ImageSize imageSize,
            @NonNull Rect imageBounds,
            int canvasWidth,
            float textSize
    ) {
        return imageSize == null
                ? fitWidth(imageBounds, canvasWidth)
                : super.resolveImageSize(imageSize, imageBounds, canvasWidth, textSize);
    }

    @NonNull
    private Rect fitWidth(@NonNull Rect imageBounds, int canvasWidth) {
        final float ratio = (float) imageBounds.width() / imageBounds.height();
        final int height = (int) (canvasWidth / ratio + .5F);
        return new Rect(0, 0, canvasWidth, height);
    }
}

Hope this helps! 🙌

Hey @thawatchai !
Yeah, looks like the solution that I have mentioned works only for HTML images. I will update library to work with markdown images also

@noties, thanks you very much 👍

@noties, it seems that the following imports can't be resolved.
import ru.noties.markwon.renderer.html.ImageSize
import ru.noties.markwon.renderer.html.ImageSizeResolverDef

even in build.gradle, I added the following implementation
implementation 'ru.noties:markwon:1.0.6-SNAPSHOT'
implementation 'ru.noties:markwon-image-loader:1.0.6-SNAPSHOT'
implementation 'ru.noties:markwon-view:1.0.6-SNAPSHOT'

@thawatchai I did move them to a one level up, so they can found at:
import ru.noties.markwon.renderer.ImageSize
import ru.noties.markwon.renderer.ImageSizeResolverDef

@noties It works perfectly now. Thank you very much for this wonderful library. 👍


foreach statement added with broader types

Description:
$title. foreach statement for a string variable gets added with string instead of string:Char as the iteration type. This change was recently introduced in the FE - https://github.com/ballerina-platform/ballerina-lang/pull/31078.
Steps to reproduce:
public function main() {
    string s = "foo";

   s.f<cursor>
}

Accepting adds
    foreach string item in s {

    }

but we should add
    foreach string:Char item in s {

    }

Affected Versions:
slbeta2-rc3

For xml<T>, the iteration value type is T, but currently gets added with xml<T>.
public function main() {
    xml<xml:Element> x = xml `<hello/>`;

    x.f<cursor>
}

adds
   foreach xml<xml:Element> item in x {

   }

but should add
   foreach xml:Element item in x {

   }

Also see https://ballerina.io/ballerina-spec/spec.html#section_5.1.6

Blocked  by #31521


PhantomData does not require bounds on T

@homu r+

:pushpin: Commit 3b7fa47 has been approved by oli-obk

:hourglass: Testing commit 3b7fa47 with merge c6acec2...

:sunny: Test successful - status


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 636

Questions ?
Please refer to the Backport tool documentation


Role Info

Implemented in https://github.com/KieranRobson/Clarence-Bot/commit/4024262afea1fdc4efbff57ddbbb9b9a2c515a1f