[BEAM-9603] Enable UsesTimerMap tests for flink portable runner

Please add a meaningful description for your change here

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

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @boyuanzz @iemejia
Does it work for spark runner and samza runner?

Run Java Flink PortableValidatesRunner Batch

Run Java Flink PortableValidatesRunner Streaming

For Spark runner it does not work with the current code maybe some information is not being passed during the translation. Maybe @ibzib can give us some hints.
You can reproduce this easily locally by running
./gradlew :runners:spark:job-server:validatesPortableRunnerBatch --tests "*ParDoTest\$TimerFamily*" --scan

It seems like Flink doesn't support timer family either.

There is a bug tracking spark implementation: https://issues.apache.org/jira/browse/BEAM-9912. Opened https://issues.apache.org/jira/browse/BEAM-10120 for Flink.


Release Google.Cloud.AIPlatform.V1Beta1 version 1.0.0-beta08

Changes in this release:
New features

Add fast_tryout_enabled to FasterDeploymentConfig message in aiplatform v1beta1 endpoint.proto (commit 546a95b)
Add new PscInterfaceConfig field to custom_job.proto (commit ce7c3b6)

Created release for Google.Cloud.AIPlatform.V1Beta1-1.0.0-beta08


[golang pprof]failed to execute dot. Is Graphviz installed? Error: exec: "dot": executable file not found in $PATH

failed to execute dot. Is Graphviz installed? Error: exec: "dot": executable file not found in $PATH

https://graphviz.org/download/
ubuntu install:
sudo apt install graphviz

resolve it. ok!


Added Spanish locale for Portal

I made some changes to make certain phrases sound more natural (some expressions where directly translated from english and while they work I believe there are better options!). I am a spanish speaker from Spain so the dialect might be reflected in some instances –changed "acá" for "aquí", both are equally correct to my knowledge–. Cheers!

Closing due to age and unresponsiveness. Please open a new submission if you have translations to contribute.


Chroma Balancer (CB)

Sorry to bother you. Your work is great. I am more interested in Chroma Balancer (CB), but I can't find it in LighTDiff. Can you show me the location of the CB code?

It is named as "SpatialControlModule" in our code.


LOOP-1492: New Therapy Settings View: Correction Range, Temporary Correction Ranges

New Therapy Settings screen, Phase 1.
This PR is not the entire screen, nor is it the complete implementation.  It only incorporates the "Correction Range" and the "Temporary Correction Ranges" sections in the new screen.   It required a fair bit of refactoring so I would like this to go in as a first step in the implementation.  Some highlights:

it takes in a TherapySettingsViewModel whose purpose is to pass on the (mutable) TherapySettings object to sub-screens for editing
it calls out to a delegate TherapySettingsViewDelegate which is not wired to anything yet...but the intention is that this will be the hook for navigation
I had to carve out CorrectionRangeOverridesExpandableSetting so I could reuse it as a read-only widget
I decided to allow HKUnit to be optional in some of these widgets.  Seemed to work out okay.

Last but not least, I implemented 3 versions of this UI (A, B, & C, matching the naming in Figma), so that Design can evaluate which one they like best.  Long-pressing on the "Edit" button on the top-right will cycle amongst the three.
LOOP-1492

@mpangburn @novalegra Thanks so much for your great suggestions!  I took pretty much all of them.  The navigation bit is still work-in-progress...I am still not sure the right way for this to fit in both the onboarding flow and in settings.  Again, it seemed logical to me to delegate that responsibility given that the two flows might be different.  If the flows are almost identical, and the differences can be captured in the ViewModel, I can change it.

@mpangburn or @novalegra can you please take one more look at this, now that we've settled on "design choice B", can you please re-approve having removed the other design versions? (Hopefully should be quick...)  Thanks.


Update the logos, add a downloadable PNG and fix querySelector in IE8

This adjusts the positioning slightly of the CHEF type in the logo (the "C" was top-aligned with the H, E and F, so its bottom edge was getting cropped by a few pixels; it should be center-aligned, according to the typeface). It also adds a downloadable PNG, which is good for general use, but also required by IE8, which doesn't speak SVG. All for Ease of Use -- specifically support for IE8 in the Downloads site.

I am in no position to vet this, but how about high ten? :raised_hands:

:+1:


Sending env in param

Nice work @laniltee
Lets try to fix the issue in loading tiles when frontend scrolling (Y)


Azure AD PowerShell 2.0 is now in GA

Minor change. Remove preview part of the modul

Hi @PeterSelchDahl, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@PeterSelchDahl : Thanks for your contribution to the Azure documentation! The author, @MarkusVi, has been notified to review your proposed change.

Thanks a lot for catching this, @PeterSelchDahl
I have already fixed it.
#please-close


Gun auto state handlers

About the PR

for #15185
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Do guns still throw exceptions on debug

idk what you mean


SOS Forever Loading...

Please help...
Got permanetly Loading in Overview
Windows 10x 64
ripple-wallet-win64-1.4.1

Any luck on this?

nope. Desktop wallet is totally ofline.
Using the GateHub (


Unhandled exception: type 'Null' is not a subtype of type 'String' in type cast

I've been trying to get the orm to work. I am able to create the initial config files via "flutter pub run orm init" but when I try to use db push with the example models from the Website I get the following Errors.

Is this a common Issue or does it have to do with my System?
Im working on an M1 Mac. Just if that's a necessary info.

I'll fork your schema and create a project that uses sqlite for validation. Please wait.

@LucaBarden Fixed in 2.4.1 version


https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/all

Request type

[x] Correction or update

Details
Regarding this sentence in the Description:

[Promise.all] is typically used when there are multiple asynchronous tasks that are dependent on one another to complete successfully...

Isn't that the opposite of Promise.all's usage? It is used when there are multiple independent async tasks that can complete in parallel.

When the all promise fulfills is orthogonal to whether the async tasks it is awaiting are "dependent on one another to complete successfully".
For example, here are 2 async tasks that are dependent on one another:
const requesting = fetch(url)
const reading = requesting.then(res => res.json())

It wouldn't make sense to Promise.all([ requesting, reading ]); after all, reading won't even start unless requesting completes successfully.
In contrast, here are independent async tasks:
const fetching = Promise.all( urlArray.map(url => fetch(url)) )

They each can complete independently, and can run in parallel.

@spazmodius ah, thanks so much for the clarification. I can now see that the main problem is with the "dependant on one another" wording, and I understand why. I've rtied updating the wording again, to clarify:
https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/all#Description
Does this sound better?


Introduce a gate/check GHA job

This adds a GHA job that reliably determines if all the required dependencies have succeeded or not.
It also allows to reduce the list of required branch protection CI statuses to just one — check. This reduces the maintenance burden by a lot and have been battle-tested across a small bunch of projects in its action form and in-house implementations of other people.
It is now in use in aiohttp (and other aio-libs projects), CherryPy, attrs, coveragepy, some of the Ansible repositories, pip-tools, pydantic, spaceship-prompt, all of the jaraco's projects (like setuptools, importlib_metadata), some PyCQA, PyCA, PyPA and pytest projects, a few AWS Labs projects.
The story behind this is explained in more detail at https://github.com/marketplace/actions/alls-green#why.

This is really smart!

Cool! I have a question, what happens with the smokeshow coverage job that is triggered after the main test workflow finishes?

Nothing should change in that regard. Or do you have a specific concern on your mind?

I understand this helps require all the "test" workflow to pass, then I would add this to the branch protection instead of the other individual rules, right?
Then, I also have "smokeshow / coverage" as required in branch protection. But that's not part of the same "test" workflow. So this wouldn't cover that and I would still need to add that one manually to branch protection, right?

@tiangolo the answer to both questions is "yes".
By the way, I think you can now use reusable workflows in the same repo so you might be able to make them run in the same workflow run and make a common check gate. That's something someone could try experimenting with in the future.

Rebased it.

@tiangolo ready to give it a try? There's still no conflicts in the PR, so it's ready to be merged anytime.

Very cool!
I have been trying it in other smaller projects. The only thing I miss is if it could output in the logs what matrix versions it checked. Currently, it only outputs the name of the job, but not the matrix combinations. E.g.
📝 test → ✓ success [required to succeed]

But it doesn't have info about the Python versions tested, to confirm that it's indeed checking all the combinations that I would put on the protection branch rules.

I have been trying it in other smaller projects. The only thing I miss is if it could output in the logs what matrix versions it checked. Currently, it only outputs the name of the job, but not the matrix combinations. E.g.

GitHub does not provide any such job details in the ${{ needs }} context for the matrix jobs. It only exposes the names and the outcomes basically. Implementing heuristics seems fragile. You can control which matrix subjobs are allowed to fail via continue-on-error but other than that, there's really no way of lurking into the workflow.

@webknjaz I'm checking this and I see that the current file doesn't check for smokeshow, and that's a triggered workflow because it needs access to tokens, so it lives in a different workflow file. How do I add smokeshow as a need in this action?

You can't add cross-workflow deps.

@tiangolo extending the explanation: you pass the ${{ needs }} context which alls-green uses to analyze job outcomes. It is not only limited but also only exists in the job context of a workflow. Another workflow run will happen independently and won't have anything from that context.
Besides that workflow job's status does not even appear in the PR checks. Instead, it uses Checks API to report a custom check not matching the job name.
I'd recommend keeping that check in branch protection, just like the status from pre-commit.ci.
If you really want another aggregated check, you could try using https://github.com/WyriHaximus/github-action-wait-for-status which does status polling in a loop and could theoretically watch statuses reported by anything, not just GHA.
Note that you'd need to do this in a yet another separate workflow since it'd deadlock if you were to add this to the check job introduced here. I haven't tried doing this, though.

Cool, thanks for the explanation @webknjaz! :rocket:


🚀 - Mention extension usage example

Description
Would be nice to have an example of @tiptap/extension-mention extension usage example with tui-editor and tuiDropdown.
There is an example for ngx-tiptap but because of the way tuiDropdown directive works, creating sth similar with "Taiga UI" components seems a bit more tricky.
@waterplea

@splincode

it doesn't seem to be possible to select suggestion result using up/down arrows.
autocompletion list should appear after just entering @ instead of waiting for user to enter @a.
how do you assign custom CSS classes to the mention span tag?

how do you assign custom CSS classes to the mention span tag? what do you mean?

I want to have:
<span class="my-mention"<EMAIL_ADDRESS>

okey

@splincode it is still not possible to select autocompletion results by using up/down arrow keys like when using @tiptap/extension-mention extension.
See the following "Taiga UI" example: https://taiga-ui.dev/directives/dropdown-selection#textarea

it is still not possible to select autocompletion results by using up/down arrow keys like when using yes, I don't know how fix it

Well, if I can achieve this using the original @tiptap/extension-mention, it should be possible with your custom extension.
Not being able to select an option with arrow keys is a major accessibility issue.
mentions-list.component.ts

create-mentions-options.ts

Reopening since we need that keyboard support. However we're kind of short on time these days, trying to push Taiga UI 4.0 so this might take a while.

@waterplea https://taiga-family.github.io/tui-editor/mention
I fixed it, you can try paste @ and use keyboard

@splincode but now it's impossible to filter the list?

Also we need Esc to close the dropdown.

Also, there is a bug with dropdown placement:

To reproduce:

Put the cursor on the third line
Press "Ctrl + A" and "Delete"
Type "@"

but now it's impossible to filter the list?
why? you can
https://github.com/taiga-family/tui-editor/assets/12021443/03c1514c-c0c7-49eb-8f54-570f24f1290d

but now it's impossible to filter the list?
why? you can
Screen.Recording.2024-04-12.at.16.06.43.mov

Whenever I press @ focus shifts to the dropdown and remains there, I'm unable to type

After pressing @ it automatically focuses the dropdown. Typing anything after that to filter dropdown is impossible. It should only focus the dropdown when I press up or down arrow. Before that I should be able to filter the menu.

Our dropdowns in Taiga UI move focus back to the input when you start typing, maybe something like this can be added here as well.

Our dropdowns in Taiga UI move focus back to the input when you start typing, maybe something like this can be added here as well. I don't know, it doesn't work with [contenteditable]

This method takes care of it:
https://github.com/taiga-family/taiga-ui/blob/v3.x/projects/core/components/hosted-dropdown/hosted-dropdown.component.ts#L222


There's a compile error '$ is not a function'

How could I run dev in Windows?

I don't really think this repo works on Windows/Non Unix systems. The build step always failed for me.

Hi Mackkkk,
As listed in the requirements page https://github.com/bigcommerce/checkout-js#requirements, this repository work on an unix-based system. You might want to look into using a unix console for windows.

Is there any workaround for this or recommendations on steps to using a Unix console on Windows?

For Unix cole on Windows, think you might want to look into something called windows subsystem for linux.
I've found a doc from MS on https://docs.microsoft.com/en-us/windows/wsl/install.

This guide will show you how to install a Linux distribution (such as (Ubuntu, OpenSUSE, Kali, Debian, Arch Linux, and more) using the Windows Subsystem for Linux. WSL enables you to use Linux tools, like Bash or Grep, completely integrated with Windows tools, like PowerShell or Visual Studio Code, with no need to dual-boot.

Also, would you mind closing the new issue because it is eactly the same as this one?


In-game money not updating / auto sniper and scout (as far as I know) are black

fixed with https://github.com/Wando1423/Antario/commit/faa0c68d136ad574a18dc6f8732729d70edb3bd5


Can't access bundles in SharePoint Framework >=1.12.0 on Windows

Starting from the workaround that was suggested for fixing the mapping<EMAIL_ADDRESS>does not contain the lines that were suggested to replace. Hence, we cannot access the bundles.
here's how it was tested in Windows:

Run the following lines in PS:

md spfx112testwp02
cd spfx112testwp02
docker run -it --rm -v ${pwd}:/usr/app/spfx waldekm/spfx:1.12.0 yo @microsoft/sharepoint --solution-name helloworld --component-type webpart --component-name wello-world-webpart --component-description "HelloWorld web part" --is-domain-isolated --framework none --environment spo --skip-feature-deployment false

Agree to provide telemetry
After the project is created and modules installed, check<EMAIL_ADDRESS>file contents.

Hi, I tested these changes that you suggested with waldekm/spfx:1.13.0 and I managed to add a web part to the SPO hosted workbench! I did not even have to add the debugBasePath property to the config\write-manifests.json.

Actually, it even worked with just serve.json and WebpackConfigurationGenerator.js for me in Windows. I'm not sure if modification of write-manifests.json and SpfxServeTask.js is required for other OSes. Here's a PR: https://github.com/waldekmastykarz/docker-spfx/pull/55

Thanks for checking!

 I forgot to mention that I tested on waldekm/spfx:1.12.1 also, so everything looks good

Awesome! I appreciate your help 👏


Remove the need to manually update encTitlekeys.bin

Your problems with downloading from the titlekey site are due to the site enforcing https, which the stable release of lpp-3ds does not support. This leaves you with a few potential options:

Write a bash script or similar to automatically download the file and rehost it
Update to a newer version of lpp-3ds that does support https.

Typically it's best to not have to manually update these things.

I tried with the latest nightly but I couldn't get it to work. I'll try it again for 1.1.

If it doesn't work I could make a bash script that automatically downloads and rehosts the encTitleKeys.bin on my website.

Could you do that but for my gh-pages branch? I need the URL to stay the same so it continues to work across all versions.
I'm assuming you know vb.net? Here's the code I use to download the required zip to my PC. I would love it if you could convert it to batch and get it to auto-upload: encTitleKeysUpdater v1 zip handler.zip

Downloading and updating the encTitleKeys.bin should be fairly easy from a batch script:
cd <path-to-local-directory> git checkout gh-pages del /F /Q f4g5h6.zip del /F /Q encTitleKeys.bin wget https://3ds.titlekeys.com/downloadenc -O encTitleKeys.bin move encTitleKeys.bin a1s2d3.bin zip f4g5h6.zip a1s2d3.bin git add f4g5h6.zip git commit -m "Updated encTitleKeys.bin automatically git push
This requires wget installed to download, and ssh for git setup so it won't prompt you for your github login.

I patched up lpp-3ds with much better networking support, so you'll have working https:// if you upgrade what you're building with here.

It's not https://
Rinne said it's to with with subdomains, and that lpp-3ds can't resolve the host because titlekeys.com has "3ds." before it.

There's no reason it won't work, I revamped networking in LPP late last week, there's no reason it won't do exactly what you want now.

index.zip
This is the script I'm using, along with the .elf I'm using. The download always fails. I made sure to get the latest nightly. Do you know what's wrong? I've tried both http and https.

well I'll be damned, i'm not sure wtf is screwy, here's a copy of lpp built from my fork before anything was changed, it works for me.
http://home.intherack.com/lpp-stable.zip

There's also http://home.intherack.com/lpp-test.zip, which /might/ be better as .3dsx, I'm not really sure what the deal was but Wolvan stated the previous stable build was only solid for .cia versions, and this one was an attempt to increase the stack size to see if it helped with 3dsx.

Alright, I actually figured out what is going wrong here... When Rinnegatamante removed my use of full text request types, he actually configured the HTTP calls with a default value that causes a crash. To use the current version, you need to provide all of the new "optional" arguments...
downloadFile(url, file, "User-Agent: encTitleKeys.bin-Updater/1.3.1", 1, "") should work properly even with the nightlies, and also give an identifiable User-Agent header in the request. (I don't have time to check this to be 100% certain right now, just fwiw.)

Just downloaded your zip and it works.  Thanks!


Unable to use action on non-Github repositories

I have attempted to use this action on a self-hosted install of Gitea (using the act runner).
Unfortunately, it looks like this action has several hardcoded references to Github, so it won't work at all if the repo that the action runs from is not hosted on Github.com

I am assuming other actions take advantage of the existing environmental variables (like GITHUB_API_URL) to detect the environment's git server (Github, Github enterprise, or something alternative like self-hosted Gitea).
It also looks like @octokit/request defaults to Github's API if the baseUrl parameter isn't specified.
Is use in non-Github.com environments a feature you are willing to include in this action?

Thanks for reaching out, and for the question.
Unfortunately, as I am not a user of Gitea (and therefore have no testing environments), I don't think it's very practical for me to officially support their service with this Action.
However, there was only one hardcoded URL and I was using the default config for @octokit/request - updating those to be dynamic is easy enough.
Note that there's still no guarantee this will work for you in Gitea.
I will release those changes shortly.

Hi Michael,  @mikesprague
just wanting to give kudos to you for this excellent action.
I'm myself using GHES and tested various ones last week, yours is the only one which actually works as expected.
Everything else had issues like not maintained, wrong node version, no support for variables in title/text, not supporting GHES a.s.o.
Happy I found that one, MMD!
Thanks, Andre


fix(parser): reserved binding name in strict mode

Summary
Fix #5120
Test Plan

Added packages/rspack/tests/cases/parsing/issue-5120-xxxx

Require Documentation?

[x] No
[ ] Yes, the corresponding rspack-website PR is __

Looks almost good to me. But sorry to bother you again. Would you also add a diagnostic test here to avoid future error span regression since it's a graphical diagnostic? packages/rspack/tests/diagnostics/module-parse-failed. You may copy other test cases.

Looks almost good to me. But sorry to bother you again. Would you also add a diagnostic test here to avoid future error span regression since it's a graphical diagnostic? packages/rspack/tests/diagnostics/module-parse-failed. You may copy other test cases. Then I will say this PR is good to go :-)

Done


No keyboard only way to move the find widget

Testing #156100
I wonder if I should be able to tab-focus into the grab handle and press arrow keys to be able to move the find widget with keys only?

Verification:

In a tree, press Ctrl F
Shift Tab to focus the grabber
LeftArrow, RightArrow, Space to move the widget around


Show number on nearby loos

We'd like to reinstate numbering on the nearest loos.
The key to this seems to be to make a leaflet.divIcon for the purpose

This is implemented but unstyled at present.


feat(cicd): add provenance publishing

Current dependencies on/for this PR:

main

PR #92   👈

This comment was auto-generated by Graphite.


Wrong command for describing a pod.

The documentation is pointing to a command kubectl describe pods podName -c azwi-proxy but the sintax is wrong as there isn't any option to use -c on the describe object command from kubectl tool.
You can either use jquery and grab all the events from that particular namespace and query for that pod name/ container name

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

ID: 5264440a-1767-c0d7-6182-e21ab784c5c3
Version Independent ID: 19cfca50-e7d1-4306-e5aa-905fe8e72d89
Content: Modernize your Azure Kubernetes Service (AKS) application to use workload identity - Azure Kubernetes Service
Content Source: articles/aks/workload-identity-migrate-from-pod-identity.md
Service: azure-kubernetes-service
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@tmcmm - Thanks for bringing this issue to our attention. You are correct, that isn't a valid parameter for the Kubectl describe command and I'm not sure why someone added that. I'm going to create a PR to fix that and one other issue I just noticed while reviewing that section of the article. I'll have the article updated today. Thanks again!

#please-close


"command not found" when pipenv shell, .bashrc is empty

OS: macOS
As I understand from reading on SO and some issues here, pipenv launches non-login shells, which means it should ignore .bash_profile, and only use .bashrc:

"Because Pipenv only reads bashrc and that’s it. Use the above workarounds." - @uranusjr in #844

My .bashrc is empty.
I've been moving around stuff in my dotfiles just to get pipenv to work properly but I'm not having too much success. This is the error I see when pipenv shell is run in a project directory:
bash: prompt_git: command not found

prompt_git is a function defined in .bash_prompt, which is sourced in .bash_profile. So why is pipenv still complaining?
In .bash_profile, which pipenv seems to be using, I've also tried doing conditionally sourcing this .bash_prompt just to satisfy pipenv:
if shopt -q login_shell; then

	if [[ $- == *i* ]]; then
		if [ -f ~/.bash_prompt ]; then
	    	source ~/.bash_prompt
		fi
	fi
fi

But that isn't helping either.

I assume you use prompt_git in your prompt? The $PROMPT_COMMAND environment variable is executed for every prompt display, so the error is raised exactly because you don’t have the command defined.

So does pipenv read .bash_profile, after all?
Where and how should I define this env var so pipenv works?

No, the $PROMPT_COMMAND environment variable was inherited from the parent shell. The general recommendation is to make .bash_prompt available in both .bashrc and .bash_profile.

I don’t understand, so prompt command was inherited, pipenv uses bashrc which is empty in my case, and .bash_prompt should be available in both my .bash_profile and .bashrc?
What if .bash_profile sources .bash_prompt, and bashrc sources bash_profile, will that work?

The general recommendation is to make .bash_prompt available in both .bashrc and .bash_profile.

Ok, this worked, thank you.
But I'm still a little confused, let me see if I understand: pipenv's subshell inherited the  $PROMPT_COMMAND env var from its interactive login parent shell, and that variable had a reference for something that was only in .bash_profile, but since pipenv itself doesn't source that file, then basically $PROMPT_COMMAND was referencing an undefined command?

Yeah I know, it’s very confusing, that’s how Bash works. A child process inherits the parent’s environment (unless explicitly set otherwise),  so all environment variables are automatically available in a sub-shell without configuration. Bash functions, however, are not part of the environment, and are therefore not inherited.
Bash internally (as I understand it) stores $PROMPT_COMMAND as a string, and eval it for every prompt. It does not carry the referenced function with it when copied into the child shell (only the name, as a string), so the child shell gets a reference error when trying to eval it.
I read here that it is also possible to use export -f to make functions available in a child shell. I am not sure whether that works with pipenv shell, however.

Awesome, thanks for the explanation.


Will there be a Typescript/Javascript version?

I am using Node.js to code some ChatGPT-related functions.
Just wonder whether there will be a Typescript/Javascript version.
If ChatGPT can convert this repo from Python to Typescript, it will be amazing. So far in GPT-3.5, the token limit stops my converting. I have no access to GPT4-8k or GPT-32k.

Hey, I like the idea but probably not. If you do create one and put it up let me know though!
I'm not that good at all the async gotchas in javascript so it'd be a pretty big endeavor for me to make it as lightweight but capture the same essence. Additionally, A lot of the logic in this is based around python decorator concept as well as the hiccups of asyncio in python, which don't really translate. Also, I'm not sure if in javascript ecosystem if jinja templates are well known, there might be better templating solutions that are more natural.
All in all, I like the idea, and would likely use it if it did exist in javascript, so keep me in the loop if you do end up making it!


Add toIterable

This lib has toAsyncIterable, should it not also have toIterable?
callbag-to-iterable

I won't add it at this stage. This library is heavily async, and adding a synchronous API is a bit confusing.


@nosideeffects methods are not being removed - no warnings generated

Can someone setup to use git-bisect to figure out where this was introduced?
http://closure-compiler-debugger.appspot.com/#input0%3Dvar%2520foo%2520%253D%2520ns1.stringify('foo')%253B%26input1%26conformanceConfig%26externs%3D%252F**%2520%2540const%2520*%252F%250Avar%2520ns1%2520%253D%2520%257B%257D%253B%250A%250A%252F**%250A%2520*%2520%2540param%2520%257B*%257D%2520arg%250A%2520*%2520%2540nosideeffects%250A%2520*%252F%250Ans1.stringify%2520%253D%2520function(arg)%2520%257B%257D%253B%26refasterjs-template%26includeDefaultExterns%3D1%26CHECK_SUSPICIOUS_CODE%3D1%26CHECK_SYMBOLS%3D1%26CHECK_TYPES%3D1%26CHECK_UNREACHABLE_CODE%3D1%26CHECK_VISIBILITY%3D1%26DEAD_ASSIGNMENT_ELIMINATION%3D1%26LANG_IN_IS_ES6%3D1%26MISSING_PROPERTIES%3D1%26PRETTY_PRINT%3D1%26SMART_NAME_REMOVAL%3D1%26TRANSPILE%3D1

Did it ever use to work?

External methods marked with @nosideeffects removed? Yes it most certainly did. I remember @concavelenz adding @nosideeffects to Document.prototype.createElement because he wasn't are of the hidden side effects and breaking my builds.

I recreated it on the web service and the debugger, but it is successfully removed from all versions I can find (including master) on the command line. I'm not sure there's anything to do at this point ...

What command did you use?

Further experimentation leads me to believe that this isn't in fact an issue. It has to do with using the 'stringify' name in the recreation example.


Add NLU training data to the 'Weather' folder #15

Add more training data that relates specifically to weather.
https://github.com/RasaHQ/contributors/issues/15

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Update starburst-galaxy-quickstart.yaml

Add apiversion to the file.

Description

Adds apiversion to the starbust quickstart file
How Has This Been Tested?

Merge criteria:

[X] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] For commits that came from upstream, [UPSTREAM] has been prepended to the commit message.
[ ] JIRA link(s):
[ ] The Jira story is acked.
[ ] Live build image:
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work.
[ ] QE contact acknowledges that this has been tested and is approved for merge.

/lgtm

Adding  qe-approved label since it blocked auto-merge


refactor(common): Change reserved BytePos to u32::MAX

Description:
Related issue (if exists):

cc @bartlomieju @dsherret
Let's see which crate breaks

I decided not to do this as this causes some regression in source map.
I tried patching codes for sourcemap generation but I got no luck

@kdy1 does that indicate that some code is fragile because it is not explicitly relying on spans being dummy? Will that be fixed and this solution still explored?

Yeah, I think those codes should be updated to use is_dummy instead.
I may retry this in the future, but I'm not sure

Postponing as SourceMap is written under assumption BytePos(0) is dummy.
It compares BytePos using cmp::max or cmp::min


machine should tell the user if a drivers functionality is not implemented

For example, docker-machine upgrade on VMware Fusion. The command just returns. We should tell the user that its not implemented so they don't have to come here and read the code.

+1

Thanks for reporting.  The fusion driver needs to implement something like https://github.com/docker/machine/blob/master/drivers/rackspace/client.go#L50.
We should include this behavior in the core refactor as well.  Let drivers specify what is supported and what isn't.

upgrade now works in vmwarefusion, so I'm closing this.  Agree we need to be clearer about what's supported and not in general though.


Feature/improve library add factories

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
:information_source: You can also turn on project coverage checks and project coverage reporting on Pull Request comment
Thanks for integrating Codecov - We've got you covered :open_umbrella:


SVG foreignObject not working in Vue 2.0

Vue.js version
2.0.3
Reproduction Link
https://jsfiddle.net/Linusborg/4j2v4fm9/
Steps to reproduce

Run it once as is.
Once without var vue = new Vue({ el: '#body'});
Once with version 1.0.26 instead of 2.0.3.

What is Expected?

In version 2.0.3 you will see no text inside the rectangle.
When you run it without Vue the text will work fine.
In version 1.0.26 the text will also be fine.

What is actually happening?
I don't know, but the resulting HTML stays the same whether the text is seen or not.

Its happening consistently across all browsers (Chrome/FF/Safari), really weird.

The reason:

Vue 1.x parses the in-DOM template as-is, so everything is already having the correct namespace.

Vue 2.0 parses the template as a string and re-generates the DOM based on the generated virtual DOM. It has special treatment for the SVG namespace, but not for embedded XHTML, so the elements inside the foreignObject is generated with SVG namespace instead of XHTML.

Should be fixable by adding xmlns detection in the parser.

Thanks for the fix.
It works now, and makes me very happy :)

SVGs were working after the fix but have been broken again.
Vue.js version
2.1.5
Reproduction Link
https://jsfiddle.net/oqctnm08/
Steps to reproduce

Run it once as is
Once without var vue = new Vue({ el: '#body'});
Once with version 2.1.4 instead of 2.1.5.

What is expected?

In version 2.1.5 you will see no text inside the rectangle.
When you run it without Vue the text will work fine.
In version 2.1.4 the text will also be fine.

What is actually happening?
Some change between 2.1.4 and 2.1.5 reverted the fix to this.

Please open another issue for this. This issue is too far down the list ^^

Is this issue present again in Vue3 ?


Zig-Zag tree traversal

Is your feature request related to a problem? Please describe.
It is a method of traversing a binary tree in a specific pattern, where the nodes are visited level by level, and the order of nodes on each level alternates between left to right and right to left.
1
3        2
4      5 6      7
Input:- 1 2 3 4 5 6 7
ZigZag Order traversal is :- 1 3 2 7 6 5 4
I will do it in C++, please assign it to me.

I can do this in Python and C++ please assign this to me

Please assign this to me in cpp

You could better raise an issue to solve Splay Trees, it would cover Zig-Zag operations also. Please raise a new issue for Splay Trees

Okay Sure!


Remote Store but Local Search / Sort

I have a remote store (using MobX) and inject the data to the table component as props. I set the remote flag in the table accordingly.
Obviously I need to write my own onAddRow, onDeleteRow and onCellEdit to update the remote store, but I'd like to avoid rewriting the search and sort code.
Is there a way to use the default search / sort functionality with remote store?

@naorrosenberg, actually, it cant be done in current version, because inside the react-bootstrap-table, I always force a return if remote enabled for these operation. For example, this is a case of sorting.
However, I think your consideration is possible happen for the other user too, so I will gonna to support this feature and my solution will be like following:

remote = (remoteFunction) => {
    // remoteFunction is a object, default is all false,
    //  { insertRow: false, dropRow: false, cellEdit: false, sort: false, pagination: false, search: false, filter: false    }
    //
    remoteFunction.insertRow = true;
    remoteFunction.dropRow = true;
    remoteFunction.cellEdit = true;
    return remoteFunction;
}

render() {
    return {
        <BootstrapTable data={data} remote={this.getRemote}
    };
}

How about above example? is that much intuitive?

Thanks @AllenFang for such a prompt reply!
Yes - this solution would be great, thanks.
Do you expect this to enter the next beta version?

I can support this feature on next version(next week)

Fixed on v2.11.1, check https://github.com/AllenFang/react-bootstrap-table/blob/master/examples/js/remote/remote-store-alternative.js and https://github.com/AllenFang/react-bootstrap-table/blob/master/examples/js/remote/remote-alternative.js for how to use it, let me know if you got any trouble, thanks 👍

I'm not able to set defaultSearch in options when remote is enable. I get 'Maximum update depth exceeded' error. Is there a solution in "react-bootstrap-table": "4.3.1" ?


Undefined reference to symbol 'pthread_create@@GLIBC_2.4'

Hello
I've just installed the library on Raspbian Jessie.
I tried to compile the UseFaceDetection.cpp in /Simd/src/Use but it gives me:
Undefined reference to symbol 'pthread_create@@GLIBC_2.4'
I added -pthread to my compiler flags but It reproduced the error. What I should I do?

I think that you need to add linker option -lpthread.

Thanks for your reply
I also added -lpthread but the same error happens

Try to add  -pthread.

Hi,
It was a simple mistake. I was adding -lpthread to compiler options in my IDE while I had to add it to the linker options.
The code is now running. But the speed is shockingly fast! OpenCV runs and LBP Cascade at 40 FPS while SIMD runs it at 250-300 FPS!
Could you please introduce a reference to learn NEON? I couldn't find a good book or course.

To learn NEON I use official docs: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0472j/chr1360928373893.html

Thanks sir


Add more environment variables

In addition to adminUsername, adminPassword, and editorTheme, I had the idea that basic authentication could be turned off automatically if a blank username is provided through an environment variable.
(undefined != '') => true // basic auth enabled when undefined
('asdf' != '') => true // basic auth enabled when username is provided
('' != '') => false // basic auth disabled when the empty string

Looks awesome! Thanks! Could you please include updated documentation in your pull request?

Updated! :-D

Awesome! Thanks @knickers !


Failed to load tslint library.

I like the tslint extension, I use it with our vscode repo.
But I now get this error in every other workspace. I think this message should just be omitted.

@joaomoreno
Since you have installed tslint locally inside the vscode repository the vsode-tslint extension doesn't find tslint in the other workspaces. Workarounds:

install tslint globally
in the user settings disable tslint and in the vscode workspace settings enable tslint

"tslint.enable": false

@dbaeumer this issue shows up across all our linters when a user prefers to install a linter locally.

This issue was moved to Microsoft/vscode-tslint#32


[ci skip] adding user @rxm7706

Hi! This is the friendly automated conda-forge-webservice.
I've added user @rxm7706 as instructed in #13.
Merge this PR to add the user. Please do not rerender this PR or change it in any way. It has [ci skip] in the commit message to avoid pushing a new build and so the build configuration in the feedstock should not be changed.
Please contact conda-forge/core to have this PR merged, if the maintainer is unresponsive.
Fixes #13

Hi @Galileo-Galilei - I wanted to use your latest kedro-mlflow - but rely on the conda packaging. I am happy to help maintain the conda recipe ; and fix the outstanding issues here. Thank you.


处理excel读取时间过长时，amq报错[BUG]

Execute the command and paste the result below.
Command: uname -a && php -v && composer info | grep hyperf && php --ri swoole
Linux ce609befb314 5.4.72-microsoft-standard-WSL2 #1 SMP Wed Oct 28 23:40:43 UTC 2020 x86_64 Linux
PHP 7.4.14 (cli) (built: Jan 29 2021 01:54:10) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Zend OPcache v7.4.14, Copyright (c), by Zend Technologies
hyperf/amqp                        v2.2.6    A amqplib for hyperf.
hyperf/async-queue                 v2.2.0    A async queue component for hyperf.
hyperf/cache                       v2.2.0    A cache component for hyperf.
hyperf/circuit-breaker             v2.2.6    A circuit breaker component for hyperf.
hyperf/command                     v2.2.0    Command for hyperf
hyperf/config                      v2.2.0    An independent component that provides configuration container.
hyperf/config-aliyun-acm           v2.2.0    An aliyun acm adapter for Hyperf config component.
hyperf/config-center               v2.2.5    The abstraction component of config center
hyperf/constants                   v2.2.0    A constants component for hyperf.
hyperf/consul                      v2.2.0    A Consul Client for Hyperf.
hyperf/contract                    v2.2.0    The contracts of Hyperf.
hyperf/dag                         v2.2.0    Dag runner for hyperf
hyperf/database                    v2.2.5    A flexible database library.
hyperf/db-connection               v2.2.0    A hyperf db connection handler for hyperf/database.
hyperf/devtool                     v2.2.5    A Devtool for Hyperf.
hyperf/di                          v2.2.7    A DI for Hyperf.
hyperf/dispatcher                  v2.2.0    A HTTP Server for Hyperf.
hyperf/elasticsearch               v2.2.0    Elasticsearch client for hyperf
hyperf/engine                      v1.1.6
hyperf/event                       v2.2.0    an event manager that implements PSR-14.
hyperf/exception-handler           v2.2.0    Exception handler for hyperf
hyperf/framework                   v2.2.0    A coroutine framework that focuses on hyperspeed and flexible, specifically use for build microservices and middlewares.
hyperf/guzzle                      v2.2.0    Swoole coroutine handler for guzzle
hyperf/http-message                v2.2.0    microservice framework base on swoole
hyperf/http-server                 v2.2.4    A HTTP Server for Hyperf.
hyperf/json-rpc                    v2.2.0    A JSON RPC component for Hyperf RPC Server or Client.
hyperf/load-balancer               v2.2.0    A load balancer library for Hyperf.
hyperf/logger                      v2.2.0    A logger component for hyperf.
hyperf/memory                      v2.2.0    An independent component that use to operate and manage memory.
hyperf/metric                      v2.2.0    hyperf metric component
hyperf/model-cache                 v2.2.0    A model cache component for hyperf.
hyperf/model-listener              v2.2.0    A model listener for Hyperf.
hyperf/nacos                       v2.2.4    Nacos SDK
hyperf/pool                        v2.2.0    An independent universal connection pool component.
hyperf/process                     v2.2.3    A process component for hyperf.
hyperf/rate-limit                  v2.2.0    A rate limiter implemented for Hyperf or other coroutine framework
hyperf/redis                       v2.2.0    A redis component for hyperf.
hyperf/retry                       v2.2.0    A retry component for hyperf.
hyperf/rpc                         v2.2.0    A rpc basic library for Hyperf.
hyperf/rpc-client                  v2.2.0    An abstract rpc server component for Hyperf.
hyperf/rpc-server                  v2.2.0    An abstract rpc server component for Hyperf.
hyperf/server                      v2.2.0    A base server library for Hyperf.
hyperf/service-governance          v2.2.4    A service governance component for Hyperf.
hyperf/service-governance-consul   v2.2.4    A consul adapter for service governance.
hyperf/service-governance-nacos    v2.2.4    A nacos adapter for service governance.
hyperf/snowflake                   v2.2.0    A snowflake library
hyperf/swagger                     v2.2.0    A swagger library for Hyperf.
hyperf/swoole-tracker              v2.2.0    A swoole tracker library for Hyperf.
hyperf/testing                     v2.2.0    Testing for hyperf
hyperf/tracer                      v2.2.0    A open tracing system implemented for Hyperf or other coroutine framework
hyperf/utils                       v2.2.7    A tools package that could help developer solved the problem quickly.
hyperf/watcher                     v<IP_ADDRESS>  Hot reload watcher for Hyperf

swoole

Swoole => enabled
Author => Swoole Team<EMAIL_ADDRESS>Version => 4.5.2
Built => Oct 28 2021 09:02:38
coroutine => enabled
epoll => enabled
eventfd => enabled
signalfd => enabled
spinlock => enabled
rwlock => enabled
openssl => OpenSSL 1.1.1l  24 Aug 2021
zlib => 1.2.11
brotli => E16777225/D16777225
mutex_timedlock => enabled
pthread_barrier => enabled
futex => enabled
async_redis => enabled

Directive => Local Value => Master Value
swoole.enable_coroutine => On => On
swoole.enable_library => On => On
swoole.enable_preemptive_scheduler => Off => Off
swoole.display_errors => On => On
swoole.use_shortname => Off => Off
swoole.unixsock_buffer_size => 8388608 => 8388608

Description:

Steps To Reproduce:

即使不启用队列也时常报这样的错误

excel 处理占用大量 CPU 时间，导致协程无法切换。
最终导致心跳无法上报，导致报错。
最直接的办法，加大心跳间隔即可结局。


Make user affirm their pr follows guidelines

Description

The contributing guidelines also contain a part which requires contributions to follow the open source license.
This requires the user to agree that they do follow said guidelines when making a pr.
Did you:

[X] Join the Python Discord Community?
[X] Read all the comments in this template?
[ ] Ensure there is an issue open, or link relevant discord discussions?
[X] Read and agree to the contributing guidelines?

@onerandomusername I'll accept this PR, but next time please have an issue open. Thanks!


abseil: update to latest

Pulls in TSAN mutex fixes as well as works around false detection.
Signed-off-by: Matt Klein<EMAIL_ADDRESS>Risk Level: Low
Testing: Existing tests
Docs Changes: N/A
Release Notes: N/A

/retest

I will look at the error here.  I will see if I can do a quick fix here to unblock this.

@lizan @jmarantz fixed pre-existing test issue.

I already fixed this latest flake on my next branch, but I guess I should do some type of interim fix here since this will likely flake a lot. This is fun. :(


template parts latest update causes TypeError: Cannot read property 'behaviorInstructions' of undefined

i have updated to latest to fix this issue https://github.com/aurelia/templating/issues/139 and followed the docs example, now i get this error :
TypeError: Cannot read property 'behaviorInstructions' of undefined
if i remove replaceable error goes away, but naturally templates wont be replaced.

Can you attach a simplest possible sample for me? I will need to see it, possibly reproduced on the nav skeleton. Also, make sure you have the latest...latest. There were several patches for different edge cases released in the last day or two.

@EisenbergEffect
i downloaded the skeleton per your suggestions and added the sample, hope i am not doing something wrong!
http://www.megafileupload.com/dh7C/replaceParts.zip
thanks in advanced.

Got it fixed in master. Will go out in the next release either today or tomorrow I hope. Thanks for catching this!

you rock Rob :)


Could not find option with name js.polyglot-builtin.

java.lang.IllegalArgumentException: Could not find option with name js.polyglot-builtin.

on
      Context context = Context.newBuilder("js")
        .option("js.graal-builtin", "false")
        .option("js.polyglot-builtin", "false")
        .option("js.load", "false")
        .option("js.print", "false")
        .option("js.console", "false")
        .allowHostAccess(false)
        .build();

I am sorry, I am not able to reproduce this issue. Could you, please, tell us what GraalVM version do you use? Note that js.polyglot-builtin option has been added recently. Any chance that your version does not have this option yet?

@iamstolis

    <dependency>
      <groupId>org.graalvm.js</groupId>
      <artifactId>js</artifactId>
      <version>1.0.0-rc10</version>
    </dependency>
    <dependency>
      <groupId>org.graalvm.js</groupId>
      <artifactId>js-scriptengine</artifactId>
      <version>1.0.0-rc10</version>
    </dependency>
    <dependency>
      <groupId>org.graalvm.truffle</groupId>
      <artifactId>truffle-api</artifactId>
      <version>1.0.0-rc10</version>
    </dependency>

You are using rc10 but the option was added in rc11 (as you can see from the link in my previous comment).


Implementation of Date.java and jUnit tests

Thank you for the feedback! We made a few style changes and changed the name of the test folder. Regarding ne, do you mean not equal? We couldn't find ne implementation for the other data types.

For our pair's assignment they requested we added all comparisons, which I interpreted to include not equals. But if yours don't have that then I'll accept the PR. You mentioned style fixes but I only see the tests moving folders in the most recent commits. I'll accept either way as I said the style changes were a preference.


Hw-6 Test

@ryarza

When you compute yipo_str, instead of (227/14336)*k5 you should have (277/14336)*k5.

@Drixitel

@ryarza
Even after you sent me this, I stared at it for about 30 minutes, not able to see where it went wrong. You are amazing, and thank you for taking time to look through my code. I know looking through code is a hassle.
Tytytyty


viur build release should be part of viur deploy

while deploying the Tool should prompt us to build a new Version.

Should be handled with #98


[1.15.2-forge] cant connect to server ,cant 2mill + fit into 3

flux-4.11.1
forge: 1.15.2
FL: fl-3.1.3
once i disabled these version i could get into server and didnt get the packet over size error

http://puu.sh/Fn6wj/fa17783512.png

This doesn't say very much. Please send latest.log file from client connecting to server with Flux. Server logs can also be helpful.

Stale issue. Reopen if same thing happened.


fix pusher element show

Sidebar in push_mode works in a different way then in 0.1.x versions of Semantic UI.
In previous major version it did not make body wider then a screen but in current version I get constant overflow of body. I would like either to get back previous behavior or to have an option in settings that will make sidebar pushing behave in a way as in previous major version.
I think this effect can be achieved by something like:
.ui.visible.left.sidebar ~ .pusher {
  margin-right: 260px; //as you use less probably there should be a variable
}

If you specify useLegacy: true it will use page margins. 1.0 swapped to transform because it is GPU optimized.

Yes, but unlike useLegacy current transformation just translates the element without making it thinner that leads to overflowing the body tag.

I'm not sure what to tell you, we modified the core functionality of sidebar so that it is not inline with previous versions. I recommend using a cherry picked version of sidebar from legacy if you prefer the old code.
http://legacy.semantic-ui.com/modules/sidebar.html
https://github.com/Semantic-Org/Semantic-UI/tree/pre-release/src/modules


Possible vulnerability in PHP mail() function?

@michael-e @creativedutchmen Could this affect Symphony as well? Has been reported for PHPMailer and SwiftMailer, but looks more like a lower level PHP issue if I understand it correctly.

@creativedutchmen: It would be great If you could take a look.

I'm afraid we're not doing any additional checks on the email addresses we are sending to, for as far as I can see. I've not yet actually tried to run an exploit yet, but browsing through the code it seems it should be possible.
While this is a very dangerous vulnerability, the exploitability might be limited - in most cases where an email is to be sent to an "untrusted" address, there will be additional checks on the fields (which, if I recall correctly, do not permit the characters that allow the exploit).
However, all this is mostly speculation at this point. I will spin up a server tonight and really test this.

Great to hear that you check this!
You are talking about the recipient address only — the known issues with PHPMailer and SwiftMailer have to do with a faked sender address (typical for contact forms and the like), so please keep this on the radar.

Oh, my bad, I must have misread. However, I do not think we're doing anything different for the sender, so the issue still stands (although it is much harder to exploit, of course). I'll get back on this later today.

I can confirm this is a problem with Symphony, too. If you are using Sendmail as your method of sending email, and you are using a default event to send confirmation emails, please cherry-pick this fix ASAP, since Symphony is vulnerable.

Thanks a lot for taking care of this!

As pers: https://github.com/symphonycms/symphony-2/wiki/Security-Bug-Disclosure please write to<EMAIL_ADDRESS>for any security related issues before publicly disclose them.

As pers: https://github.com/symphonycms/symphony-2/wiki/Security-Bug-Disclosure please write to<EMAIL_ADDRESS>for any security related issues before publicly disclose them.

This was not Symphony specific and has already been publicly disclosed.

@jensscherbl I this case, I understand that it was already disclosed. But I watch that email account more than my github's notifications and would have acted sooner ;)
Anyhow, I've just pushed 2.6.9. See #2638

And thanks for sharing too @jensscherbl ;)

But I watch that email account more than my github's notifications and would have acted sooner

Understood.


Data classification&Value predication: Training failed with error "Object reference not set to an instance of an object." when only choosing "LGBM" algorithm to train "Tabular File" data source.

System Information (please complete the following information):
Windows OS: Windows-11-Enterprise-22H2
ML.Net Model Builder 2022: <IP_ADDRESS>2602 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.5.5)
.Net: 6.0, 7.0
Describe the bug

On which step of the process did you run into an issue:
Training failed with error "Object reference not set to an instance of an object." when only choosing "LGBM" algorithm.

TestMatrix
https://testpass.blob.core.windows.net/test-pass-data/wikipedia-detox-250-line-data.tsv
https://testpass.blob.core.windows.net/test-pass-data/taxi-fare.csv
To Reproduce
Steps to reproduce the behavior:

Select Create a new project from the Visual Studio start window.
Choose the C# Console App (.NET Core) project template.
Add model builder by right click on the project.
Select Data classification or Value predication scenario.
On Data page, choose the "Tabular File" data source.
On the Train page, click the "Advanced training options..." link.
Go to "Trainers" tab, only choose "LGBM" algorithm and save it.
The training would be failed with error "Object reference not set to an instance of an object.".

Expected behavior
Training successfully.
Screenshot

Additional context
The bug is not repro when choosing "LGBM" algorithm to train SQL Server data.

The bug has been fixed on the latest main build <IP_ADDRESS>5401.

The bug is repro again on the latest main build <IP_ADDRESS>6302.

how do I get the latest version (<IP_ADDRESS>5401)? I only see <IP_ADDRESS>2602

<IP_ADDRESS>5401 is the internal version for our tester. We haven't released the fixed version yet.

Looking for an update on this. Has the fix been released? I'm still having this issue.

having the same issue, is there any ETA on this?


Fix: Handle error when patch dir is empty

When the patch dir is empty the #PATCH_DIR/*.patch is not expanded and handled as a file name leading to "No such file or directory" error

Thank you!


Add ability to display depth buffer in editor 3d preview.

This pull request implements the ability to quickly display the depth buffer in editor 3d preview and fixes a bug in the copy.glsl shader related to how linear depth is calculated.

@Joxno You need to run godot --doctool to generate the XML documentation for the newly added enum entries.

Good idea! I think this will be nice addition and it makes sense seeing as how we already have a display mode for the normal buffer.
One thing I am unsure about is whether we actually need to invert the depth. I left some comments on implementation assuming we keep the inverted depth code, but to me it seems like it may make more sense for the debug mode to show users something closer to the actual value instead of inverting the range. Did you do it this way because non-inverted depth was too difficult to read?

Thanks!
Yeah, I can understand the argument to display closer to the truth values for debugging purposes although I think without an inversion it makes the visualisation harder to read.
Here's an example if you do not invert the values:

Obviously this is a trivial scene with an infinite background but I think in a more complex scene objects that occupy the middle-ground would be washed out. Possibly making it difficult to debug depth issues.
Maybe having 2 alternatives to choose from, one that displays the values as is, and a second one that is inverted could be a possibility?
"Depth Buffer"
"Depth Buffer (Inv)"
It could also be that I am biased to dark mode haha.

Discussed in the PR meeting today. Consensus was that this looks mostly good, but both non-inverse and inverse result in far away objects being difficult to see. Lawnjelly helpfully suggested (and the other contributors agreed) that we should use the non-inverted linear depth, but we should set the far plane to a fixed color so that far objects contrast well against it.
I am thinking a dark blue colour from this page would be good https://davidmathlogic.com/colorblind/#%23D81B60-%231E88E5-%23FFC107-%23004D40. There are a few colours suggested here that have good visibility for many different types of colourblindness.

@Joxno Could you look into applying clayjohn's suggestions above? The PR shoUld be good to merge afterwards.

Tested locally, there seems to be a mismatch between the UI in the Perspective menu and the actual debug draw mode you get:
https://github.com/godotengine/godot/assets/180032/31d4dd12-db45-4cea-acc1-84ac3d1d8605
Testing project: test_shadowmask.zip

Ah, I made a complete blunder when I reordered the debug_draw_modes array but forgot to take into account the order in display_options as well. Should be resolved in the latest commit.


Access query/mutation input via AWS Lambda function

Note: If your question is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum

Ref: https://aws-amplify.github.io/docs/cli/graphql#add-a-custom-resolver-that-targets-an-aws-lambda-function
Step 1 in this section "First create a function by running amplify add function..." When I create a function using amplify add function I have 3 options and I chose the Hello World one. Now when I follow these steps, regardless of the input i pass to this query, my graphql response will always be "Hello World". How can I access the input parameter in the request in my lambda function?
** Which Category is your question related to? **
Usage
** What AWS Services are you utilizing? **
Amplify
** Provide additional details e.g. code snippets **
n/a

the arguments passed should be available under event.arguments given that used the request resolver template from that tutorial:
{
    "version": "2017-02-28",
    "operation": "Invoke",
    "payload": {
        "type": "Query",
        "field": "echo",
        "arguments": $utils.toJson($context.arguments),
        "identity": $utils.toJson($context.identity),
        "source": $utils.toJson($context.source)
    }
}

so changing your lambda code at ./amplify/backend/function/YOUR_FUNCTION/src/index.js from
exports.handler = function (event, context) { //eslint-disable-line
  console.log(`value1 = ${event.key1}`);
  console.log(`value2 = ${event.key2}`);
  console.log(`value3 = ${event.key3}`);
  context.done(null, 'Hello World'); // SUCCESS with message
};

to
exports.handler = function (event, context) { //eslint-disable-line
  console.log(event);
  context.done(null, event.arguments.msgP1 + event.arguments.msgP2); // SUCCESS with message
};

should do.

@Shan4993 Closing this issue based on @ambientlight response. Please feel freee to respond on this thread or re-open the issue if you're still stuck.


HoverProvider appears in the wrong position

Issue Type: Bug
Actual behavior

when using the rust-analyzer plug-in, it will prompt the error code, the pointer hovering over the wrong code
The hover box appears in the wrong position and does not appear near the pointer

Expected behavior

Appear near the pointer

The detailed recording screen can be seen in this issue.
VS Code version: Code 1.59.1 (3866c3553be8b268c8a7f8c0482c0c0177aa8bfa, 2021-08-19T11:53:52.479Z)
OS version: Darwin x64 19.6.0
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
32.00GB (12.33GB free)

Process Argv
--crash-reporter-id e0440de6-b5ea-426f-9ba9-e175b8460637

Screen Reader
no

VM
0%

Extensions (12)

Extension
Author (truncated)
Version

bracket-pair-colorizer-2
Coe
0.2.1

gitlens
eam
11.6.0

copilot
Git
1.3.2425

rust-analyzer
mat
0.3.715

git-graph
mhu
1.30.0

indent-rainbow
ode
7.5.0

material-icon-theme
PKi
4.9.0

vscode-fileutils
sle
3.4.5

guides
spy
0.9.3

code-spell-checker
str
1.10.2

vim
vsc
1.21.6

material-theme
zhu
3.11.4

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
pythonvsuse255:30340121
vscod805cf:30301675
pythonvspyt200:30340761
vscextlang:30333561
binariesv615:30325510
vsccppwt:30329788
pythonvssor306:30344512
bridge0708:30335490
vstre464cf:30350173
bridge0723:30353136
vsdyn478:30354110

That flashing happens because the error also points to the top of the file, note the main.rs(1, 1) in the message, so vscode tries to move the diagnostic hover to the top first and then puts it back down for some reason.
The main problem here is VScode not handling multi span diagnostics too well which we create from rustc's output as it likes to point over the entire file with its diagnostics.

Originally posted by @Veykril in https://github.com/rust-analyzer/rust-analyzer/issues/9974#issuecomment-903142860
@Veykril it may help the VS Code devs understand this issue if you are able to post the JSON of the Diagnostic object(s) that Rust Analyzer will be returning in the example given by @liby

@gjsjohnmurray
Based on what Veykril has described here, I got the following information and I don't know if it can help.

Received notification 'textDocument/publishDiagnostics'
[Trace - 1:27:22 AM] Received notification 'textDocument/publishDiagnostics'.
Params: {
    "uri": "file:///Volumes/Code/Play/gui/src/main.rs",
    "diagnostics": [
        {
            "range": {
                "start": {
                    "line": 3,
                    "character": 17
                },
                "end": {
                    "line": 3,
                    "character": 23
                }
            },
            "severity": 1,
            "code": "E0422",
            "codeDescription": {
                "href": "https://doc.rust-lang.org/error-index.html#E0422"
            },
            "source": "rustc",
            "message": "cannot find struct, variant or union type `Screen` in this scope\nnot found in this scope",
            "relatedInformation": [
                {
                    "location": {
                        "uri": "file:///Volumes/Code/Play/gui/src/main.rs",
                        "range": {
                            "start": {
                                "line": 0,
                                "character": 0
                            },
                            "end": {
                                "line": 0,
                                "character": 0
                            }
                        }
                    },
                    "message": "consider importing this struct: `use gui::Screen;\n`"
                }
            ]
        },
        {
            "range": {
                "start": {
                    "line": 0,
                    "character": 0
                },
                "end": {
                    "line": 0,
                    "character": 0
                }
            },
            "severity": 4,
            "code": "E0422",
            "codeDescription": {
                "href": "https://doc.rust-lang.org/error-index.html#E0422"
            },
            "source": "rustc",
            "message": "consider importing this struct: `use gui::Screen;\n`",
            "relatedInformation": [
                {
                    "location": {
                        "uri": "file:///Volumes/Code/Play/gui/src/main.rs",
                        "range": {
                            "start": {
                                "line": 3,
                                "character": 17
                            },
                            "end": {
                                "line": 3,
                                "character": 23
                            }
                        }
                    },
                    "message": "original diagnostic"
                }
            ]
        },
        {
            "range": {
                "start": {
                    "line": 14,
                    "character": 21
                },
                "end": {
                    "line": 18,
                    "character": 13
                }
            },
            "severity": 1,
            "code": "E0308",
            "codeDescription": {
                "href": "https://doc.rust-lang.org/error-index.html#E0308"
            },
            "source": "rustc",
            "message": "mismatched types\nexpected struct `SelectBox`, found struct `Button`"
        }
    ],
    "version": 1
}

This has been fixed in the meantime via https://github.com/microsoft/vscode/issues/151235


Add ECR IAM permissions, Add user_data_base64 variable

what

Add ECR IAM permissions
Add user_data_base64 variable

why

Need the ability to run ECR based docker containers
Allows use of cloud_init based configurations

/test all

@osterman @htplbc just a thought on the ECR permissions. Some of the AWS API actions require repository name/ID so should this module tighten the permissions to target specific repository/ies? Or is it acceptable to be broad here?

@htplbc seems like we are overstepping here to @joe-niland point. Maybe this should be parameterized or not the responsibility of the module.

FWIW, I have often used the role output in the consuming module to add specific policies where it doesn't make sense for the module to manage certain IAM access.
That said, I don't understand the use case here.

FWIW, I have often used the role output in the consuming module to add specific policies where it doesn't make sense for the module to manage certain IAM access.
That said, I don't understand the use case here.

I've added an instance_profile to overwrite the current one if needed

/test all

/test all

/test all


Remove extra attempted heartbeat after stopping Bot normally

Summary
Changes the sequence of time delays in the heartbeat thread.
If the delay happens after checking the session, the session could be
suspended while the thread is sleeping, causing us to try to heartbeat on a
suspended session. Moving the sleep down sends the heartbeat right after the
check.

Changed

Gateway's @heartbeat_thread: Moved the heartbeat_interval delay to after raising the heartbeat event, before
checking if the session is suspended.

We need to do a few more things for this change. Ideally we would kill the heartbeat loop on disconnect, and allow it to restart on HELLO, so we also aren't trying to send a heartbeat without an active connection.
We also need to kill the thread that detects zombie connections, since that will continue to attempt to reconnect as well.

We need to do a few more things for this change. Ideally we would kill the heartbeat loop on disconnect, and allow it to restart on HELLO, so we also aren't trying to send a heartbeat without an active connection.
We also need to kill the thread that detects zombie connections, since that will continue to attempt to reconnect as well.


Locally Published Package Fails to Download Dependency

Hi,
I am working on a package that works with the Almond.sh kernel. My files are as follows:
build.sbt:
name := "example"

version := "0.1"

scalaVersion := "2.13.2"

// almond jupyter api
//resolvers += "jvm-repr" at "https://maven.imagej.net/content/repositories/public/"
libraryDependencies += "com.github.jupyter" % "jvm-repr" % "0.4.0" from "https://maven.imagej.net/content/repositories/public/com/github/jupyter/jvm-repr/0.4.0/jvm-repr-0.4.0.pom"
libraryDependencies += "sh.almond" %% "jupyter-api" % "0.9.1"

Example.scala:
import almond.interpreter.api.{DisplayData, OutputHandler}

object Example extends App {
    def f1() = {
      DisplayData(
        Map(
          // if we set up an extension for application/myapp+json, first element should be picked
          "application/myapp+json" -> """{"a": "A"}""",
          // else, text/html should be displayed
          "text/html" -> "<b>A</b>"
        )
      )
    }

    println(f1())
}

If I type:
publishLocal
in the SBT shell, it all compiles and publishes. However, if I import this into the Almond shell, I get the following issue:

So it seems that it's failing to download the non-Maven repo for some reason as the added resolvers are being ignored. Could someone please explain how this can be fixed?

@FA5I try to add the repo in ammonite also:
interp.repositories() ++= Seq(
  MavenRepository.of("https://maven.imagej.net/content/repositories/public")
)

Thanks @sake92


Limit pigpiox dependency to Raspberry Pi targets

This PR fixes an application crash due to a failure to start pigpiox on non-rpi Nerves targets:
15:17:35.667 [info]  Application pigpiox exited: Pigpiox.Application.start(:normal, []) returned an error: shutdown: failed to start child: Pigpiox.Port
    ** (EXIT) an exception was raised:
        ** (ErlangError) Erlang error: :enoent
            :erlang.open_port({:spawn_executable, nil}, [:binary, :exit_status, {:args, ["-g", "-x", "-1"]}])
            (pigpiox 0.1.2) lib/pigpiox/port.ex:21: Pigpiox.Port.init/1
            (stdlib 3.14.1) gen_server.erl:417: :gen_server.init_it/2
            (stdlib 3.14.1) gen_server.erl:385: :gen_server.init_it/6
            (stdlib 3.14.1) proc_lib.erl:226: :proc_lib.init_p_do_apply/3

Woah, I'm surprised that I didn't see that. Thanks for fixing.


Error Testing Fragments Introduced in v3.4.0

Describe the bug
Not sure if this is a bug or intended behavior/us doing something wrong. It seems that after upgrading to enzyme v3.4+ our tests for components with fragments have started failing.
To Reproduce
Consider the following example:
import React from 'react';
import { expect } from 'chai';
import { shallow } from 'enzyme';

class MyComponent extends React.Component {
  state = { isOpen: false };

  openMe = () => { this.setState({ isOpen: true }); }

  render() {
    return [
      <button onClick={this.openMe}>Click Me</button>,
      <div>Some div</Menu>
    ];
  }
}

// test....
describe('<MyComponent />', function() {
  it('initializes the state', function() {
    const wrapper = shallow(<MyComponent />);
    expect(wrapper.state('isOpen')).to.be.false;
  });
});

Expected behavior
This test worked prior to v3.4. wrapper.state() in that instance returned false as expected. It now causes an error. Namely: "Error: Method "state" is only meant to be run on a single node. 2 found instead."
Additional context

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

The support that was added in enzyme v3.4 is for React.Fragment - what's also confusingly referred to as "fragments" is the ability for components to render non-nodes - ie, to render arrays, strings, and numbers. This is not yet supported by enzyme - see #1213.
We're working on adding support for that, but in the meantime, you'll either need to not use this React feature, not test components that use it, or find a way to make the tests pass anyways.

@ljharb Thanks for the feedback. I switched to <React.Fragment> and my tests went back to passing as expected. I didn't realize that there were different flavors of 'fragment' - I thought the one was just syntactic sugar for the other. Apparently not the case.


docs: add README.md chinese-simplified translation

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[x] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[x] No

Hi @cherrol, thank you so much for putting this in! For the code-based repos we're keeping them in English for the sake of maintainability. If you'd like to help contribute to translations I'd recommend looking at the https://github.com/tauri-apps/tauri-docs repo which we have i18n set up already to accept translations.
If you'd like to add a one-liner to the top of the English readme to the Simplified Chinese website (https://tauri.app/zh-cn/) then it could help readers viewing the readme on to find the language more easily.
I will say that we're in the middle of a re-write there so we have frozen translations until we launch the new website in beta (aiming for this spring). You can follow along with the progress here: https://github.com/orgs/tauri-apps/projects/18
If you'd like to get more involved with Translations in general then feel free to put an issue on that repo to start a discussion or join our Discord where we can chat: https://discord.com/invite/tauri


images are not fetched

Hello,
thank you for your powerful tool, I really like it! great job ! it's big milestone to gitops :)
I have problem with fluxcd2 because during creating processes which would be automatically after pushing images to ECR repository, HelmRelease is not upgrading containers however ImageUpdateAutomation works great and helm values file is updated on git repository very well.
not upgrading containers - I mean that even in repository the image is in the newest version eg.(sdd9) container is still in wrong version...
do you have any ideas what it's wrong with those files?
flux logs doesn't return nothing special... I see only that every one minute updating working.
something like values.yaml are not valid recognize by kubernetes
Every 2.0s: flux get images all                                                                                iMac-Jakub.local: Sun Apr 11 09:45:36 2021

NAME                    READY   MESSAGE                         LAST SCAN                       SUSPENDED
imagerepository/podinfo True    successful scan, found 34 tags  2021-04-11T09:44:46+02:00       False

NAME                    READY   MESSAGE                                                                                LATEST IMAGE
imagepolicy/podinfo     True    Latest image tag for '247635813899.dkr.ecr.eu-central-1.amazonaws.com/hey-flux' resolved to: sdd9<PHONE_NUMBER>99.dkr.ecr.eu-central-1.amazonaws.com/hey-flux:sdd9

NAME                                    READY   MESSAGE                                                         LAST RUN                        SUSPENDED
imageupdateautomation/flux-system       True    no updates made; last commit 58dd783 at 2021-04-11T07:35:46Z    2021-04-11T09:44:53+02:00       False

structure (my-private-repo)
-file1.yml
-file2.yml
-file3.yml
---eks(directory)
-------heyflux(directory)
----------values.yaml
----------Chart.yaml
----------rest chart files
file1.yml
apiVersion: image.toolkit.fluxcd.io/v1alpha1
kind: ImageUpdateAutomation
metadata:
  name: flux-system
  namespace: flux-system
spec:
  checkout:
    branch: master
    gitRepositoryRef:
      name: podinfo
  commit:
    authorEmail<EMAIL_ADDRESS>    authorName: fluxcdbot
    messageTemplate: '{{range .Updated.Images}}{{println .}}{{end}}'
  interval: 1m0s
  push:
    branch: master
  update:
    path: ./eks/heyflux
    strategy: Setters

file2.yml
---
apiVersion: image.toolkit.fluxcd.io/v1alpha1
kind: ImageRepository
metadata:
  name: podinfo
  namespace: flux-system
spec:
  image:<PHONE_NUMBER>99.dkr.ecr.eu-central-1.amazonaws.com/hey-flux
  interval: 1m0s
  secretRef:
    name: aws-ecr
---
apiVersion: image.toolkit.fluxcd.io/v1alpha1
kind: ImagePolicy
metadata:
  name: podinfo
  namespace: flux-system
spec:
  imageRepositoryRef:
    name: podinfo
  filterTags:
    pattern: '^sdd[a-fA-F0-9]+'
  policy:
    alphabetical:
      order: asc

file3.yml:
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: GitRepository
metadata:
  name: podinfo
  namespace: flux-system
spec:
  interval: 1m
  url<EMAIL_ADDRESS>  secretRef:
    name: ssh-credentials
  ref:
    branch: master
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: heyflux
  namespace: flux-system
spec:
  interval: 1m
  upgrade:
    remediation:
      retries: -1
  chart:
    spec:
      chart: ./eks/heyflux
      valuesFile: ./eks/heyflux/values.yaml
      sourceRef:
        kind: GitRepository
        name: podinfo
        namespace: flux-system
      interval: 1m

eks/heyflux/values.yaml
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

replicaCount: 1
envName: "default"
strategy:
  type: RollingUpdate
  rollingUpdate:
    maxSurge: 25%
    maxUnavailable: 25%
muumeerp:
  image:
    repository:<PHONE_NUMBER>99.dkr.ecr.eu-central-1.amazonaws.com/hey-flux
    tag: sdd9 # {"$imagepolicy": "flux-system:podinfo:tag"}
    pullPolicy: Always
  service:
    type: ClusterIP
    port: 8080

Hey there guys! Enjoyed so far my fluxcd experience, though similarly to kadzielawa I have issues with automatic image updates to git repo.
Here is some info around it:
Repo structure
 ── cd
│   ├── flux-system
│   │   ├── gotk-components.yaml
│   │   ├── gotk-sync.yaml
│   │   └── kustomization.yaml
│   └── sync
│       ├── flagger
│       │   ├── blueGreen.yaml
│       │   └── load-tester
│       └── flux
│           ├── helm_release.yaml
│           └── helm_source.yaml
├── flagger
└── rest-api-app
    ├── Chart.yaml
    ├── charts
    ├── templates
    └── values.yaml

bootstrap was done like this
         flux bootstrap gitlab \
         --owner=dmitry_rachkov/cd \
         --repository=BlueGreen \
         --branch=master \
         --path=cd \
         --components-extra=image-reflector-controller,image-automation-controller \
         --token-auth

image creation
         flux create image repository rest-api-app \
         --image=registry.hub.docker.com/dmitryrachkov/rest-api \
         --interval=1m

image policy
          flux create image policy rest-api-app \
         --image-ref=rest-api-app \
         --select-semver=">=0.0.6"

image update automation
         flux create image update rest-api-app \
          --git-repo-ref=rest-api-app \
          --git-repo-path="./rest-api-app" \
          --checkout-branch=master \
          --push-branch=master \
          --author-name=dmitry_rachkov \
<EMAIL_ADDRESS>\
          --commit-template="{{range .Updated.Images}}{{println .}}{{end}}"

The update is expected to happen over helm release (based on GitRepository - helm source object)
helm_source.yaml
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: GitRepository
metadata:
  name: rest-api-app
  namespace: flux-system
spec:
  interval: 1m
  url: https://gitlab.com/dmitry_rachkov/cd/BlueGreen.git
  ref:
    branch: master
  ignore: |
    # exclude all
    /*
    # include charts directory
    !/rest-api-app/
    !/cd/sync/flux

helm_release.yaml
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: rest-api-app
  namespace: rest-api-app
spec:
  interval: 1m0s
  chart:
    spec:
      chart: ./rest-api-app
      sourceRef:
        kind: GitRepository
        name: rest-api-app
        namespace: flux-system
      valuesFiles:
        - ./rest-api-app/values.yaml
  values:
    deployment:
      image:
        tag: 0.0.16 # {"$imagepolicy": "rest-api-app:rest-api-app:tag"}

Unfortunately automatic commit just doesn't happen with this setup for me though as I've read above and in documentation it should, would be grateful for ideas or hints.
Cheers

@dmitry-rachkov Thank you for your report, but I do not think your issue is the same as the original poster of this issue.
It appears you may have placed your GitRepository source in a different namespace than the Image Automation resources (ImagePolicy, ImageRepository, ImageUpdateAutomation). At least the $imagepolicy tag indicates it to be so – if your ImagePolicy and related resources are in flux-system then the tag YAML setter comment should look like this instead:
tag: 0.0.16 # {"$imagepolicy": "flux-system:rest-api-app:tag"}

If your resources were created in the flux-system namespace, as I suspect from the commands you showed, then updating the tag to this structure should cause the automation to spring to life fairly quickly. Please give that a try.
Cross-namespace secret references are not currently a valid configuration in Flux and variations on this issue seem to be collectively the top most common error facing users of ImageUpdateAutomation. (You're not even the first person in this thread to have hit this problem: https://github.com/fluxcd/image-automation-controller/issues/180#issuecomment-818804583)
I have submitted a PR to add a note to the API docs (#200), but if this turns out to not have been your problem, please open a separate issue, as I think the top poster did not have this misconfiguration issue. I am also working on a way to elevate this to a higher prominence in the FAQ, or even better, with an error message, but some variants of the issue like the way this problem seems to be presenting for you will unfortunately not be able to signal an error. (You apparently referenced in your kyaml setter an ImagePolicy at a location that does not exist, and ImagePolicy/ImageUpdateAutomation resources only look for references to themselves when scanning for tags that they should update.)
Please also a note from the community support policy: if you are not sure if you are using the API correctly, rather than filing it as an issue or bug report, we think the Q&A section of the discussion board on fluxcd/flux2/discussions is the most appropriate place to post an inquiry like this. (Thanks for using Flux!)

I marked this as a documentation, because there is documentation I would like to see added as we've discussed before, the "recipe" book showing which ways you can configure ImageUpdateAutomation in formulaic ways, and how cross-namespace support is or is not ready for use in general availability.
But I've also given this issue the 'bug' label as for usability, we want Flux's image automation to be as easy to configure from the CLI as it was in Flux v1 (or even, say, in Weave Cloud.) Users should be able to detect images which can be updated, select from whether they have a semver format or some regex, receive feedback and guidance at the CLI which helps them know when image tags match the format, which images can be selected from, and which candidate is considered as the latest before they apply the image update policy to the cluster, and so on.
Maybe all that belongs in a separate issue, but there are already a couple of different issues open related to the usability, I think this story is already found in one or more of them.
It would be even better if the CLI could help you determine what updates can be applied to a file, and trace for you what image update automations would apply to this gitrepository path when reconciled, or lead you to notice when IUA is not correctly associated with the path you wanted. And even when your sourceRef is inappropriately specified with an invalid or not present GitRepo, which can often happen when users are first trying automation and have not been appropriately warned about the cross-namespace issues, namely that cross-namespace secret access is not currently supported, so as it was maybe already explained above, image update which are not in the same namespace as ImageRepo, or similar issues, #201
Right now the CLI helps you build the YAML and interact with the status, but it does not do most of all that.

I spent some time determining why my ImageUpdateAutomations stopped working after I moved my Deployment objects. For me, it was that I didn't have a Kustomization for the new location setup.
I found that flux logs -f wasn't verbose enough and turned up debug logging via flux install --log-level=debug and checked the pod logs in flux-system.
For example , this flux logs entry:
2021-11-22T23:43:19.873Z info Kustomization/dev-env.flux-system - server-side apply completed
corresponded to what I was expecting to happen
In the kustomize-controller logs, the output field in the JSON is what I found to be useful:
{"level":"info","ts":"2021-11-22T23:43:19.873Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"dev-env","namespace":"flux-system","output":{"Deployment/dev-env/dev-env-app1":"configured","Deployment/dev-env/dev-env-app2":"unchanged","Deployment/dev-env/dev-env-app3":"unchanged","Deployment/dev-env/dev-env-app4":"unchanged","ImageUpdateAutomation/flux-system/smoke-test":"unchanged"}}
in the earlier failed attempts to update the image, the log doesn't indicate failure:
{"level":"info","ts":"2021-11-22T18:32:49.146Z","logger":"controller.kustomization","msg":"server-side apply completed","reconciler group":"kustomize.toolkit.fluxcd.io","reconciler kind":"Kustomization","name":"dev-env","namespace":"flux-system","output":{"ImageUpdateAutomation/flux-system/smoke-test":"unchanged"}}
for this, I would need to check the path of the Kustomization to see that it wasn't checking the right directory.
for ImageUpdateAutomation, the flux log entries are also sparse:
2021-11-22T23:42:46.409Z debug ImageUpdateAutomation/smoke-test.flux-system - updating with setters according to image policies
2021-11-22T23:42:46.410Z debug ImageUpdateAutomation/smoke-test.flux-system - ran updates to working dir
which corresponds to:
{"level":"debug","ts":"2021-11-22T23:42:46.409Z","logger":"controller-runtime.manager.controller.imageupdateautomation","msg":"updating with setters according to image policies","reconciler group":"image.toolkit.fluxcd.io","reconciler kind":"ImageUpdateAutomation","name":"smoke-test","namespace":"flux-system","count":6,"manifests-path":"/tmp/flux-system-app-helm525809833/clusters/dev"}
{"level":"debug","ts":"2021-11-22T23:42:46.410Z","logger":"controller-runtime.manager.controller.imageupdateautomation","msg":"ran updates to working dir","reconciler group":"image.toolkit.fluxcd.io","reconciler kind":"ImageUpdateAutomation","name":"smoke-test","namespace":"flux-system","working":"/tmp/flux-system-app-helm525809833"}
for this I wanted to be able to check what files were getting pulled down into the working dir
I'm using the latest flux, 0.23.0. I found that I was able to run ImageUpdateAutomation in another namespace if I had all of the following in the different namespace: GitRepository, ImageRepository, ImagePolicy, ImageUpdateAutomation, and Kustomization.


Run status and header tests first so that body tests can be skipped

Forked from issue #3 by @gitblit
I'd like to see status and $h tests run first, always.
Currently if you define those in common they appear to be appended to the endpoint test list and run last. Perhaps prepend the common tests (in the order defined by the user) to the endpoint test list OR perhaps sort status & header tests first, regardless of where they are defined?
If status or $h tests fail, the $. body tests are likely to fail since the response shapes or types will be different than expected. Perhaps do not run $. tests if the status and/or $h. tests fail? I have example endpoints where 400 or 403 responses return strings instead of application/json and this creates noise when zzzapi attempts to parse JSON in these cases.

An option to stop further tests on the first failure would be very useful in addition to running common tests first and then the per-request tests.

Let us run the tests in the following order:

Status test
Header tests
Body tests

If there are tests defined in common as well as per-request, let us run the common ones first (no particular reason I can think of, but it seems intuitive). The order will only affect the "stop on failure" option.

zzapi v1.2.0 and zzapi-vscode v2.1.0 address this issue.

@vasan-agrostar how do I use stopOnFailure? VS Code allows me to specify it in the schema but running all requests or executing with CLI both fail.

A bug was introduced, we need to make a new release. I will do it sometime today.

zzapi-vscode 1.2.1 should fix the problem.

Confirmed. This is now not-failing on CLI and VSCode plugin.
I still have an issue where a body test expects & attempts to deserialize application/json for a 201 result but the endpoint is actually responding 403 and text/plain - response is "Forbidden". One motivation for fail-early was to avoid the attempt to JSON-parse a non-JSON response.
5/17/2024, 8:12:32 AM [ERROR] POST Creates Person status: 403 size: 9 B time: 6 ms parse error(Unexpected token F in JSON at position 0)

Maybe there should be some automatic, built-in validation to assert the response content-type is application/json before attempting to JSON deserialize?


Raspiblitz update script has a bug

It looks like the update script on raspiblitz has a bug as I can only upgrade to 0.5.0 even though we have already 0.5.1

I propose someone other than me tackles this to get familiar with the setup. Happy to hold hands at the beginning.

Mmhmm... after re-running it again it worked. Maybe it was just a glitch...


In sc_service/src/metrics.rs, detach the networking-related metrics from non-networking-related metrics

At the moment, metrics such as the CPU usage, disk writing, and so on are updated only when the networking periodically reports its status.
Unfortunately, that means that if the networking has an issue and freezes, then CPU usage, disk writing, ... are never updated. This is a problem, because they might be useful to understand why the networking freezes.

Closed by #6986.


Console not removing commands correctly when leaving a state

clearcommands to be moved to statedestructor

@h3nx please provide example of what state and when it is not removing commands correctly

Gamestate, earlier it did not remove commands for clients which did not issue gameover.


:rotating_light: ACTION REQUIRED: Confirm Repository Status for Migration by Dec 20 :rotating_light:

Hi @Naptimecoder @mundane-monica ,
The Developer Experience (DevX) team is moving code from the current BCDevOps GitHub organization to the new bcgov GitHub Enterprise organization, which is protected by single sign-on (SSO). To prepare for this migration, we need you to confirm the status of your repositories.
Here’s what you need to do:
Respond to this issue by December 20, 2024, to confirm if each of your repositories is:

Active and ready for migration to bcgov, OR
No longer needed and can be archived.

:bell: ACTION REQUIRED: Leave a comment on this issue with your repository status.
If we don’t hear back by December 20, we’ll proceed with archiving your repositories.
Questions? Email<EMAIL_ADDRESS>for help.
Thank you for your cooperation!
The Developer Experience Team, Digital Office

Hi @Naptimecoder @mundane-monica ,
This is a reminder to confirm the status of your repositories by December 20, 2024, as part of the migration to the bcgov GitHub Enterprise organization.
Please leave a comment on this issue to let us know if your repositories are:

Active and ready for migration, OR
No longer needed and can be archived.

If we don’t receive a response by the deadline, we’ll proceed with archiving your repositories.
Need help? Email<EMAIL_ADDRESS>Thank you for your attention!
The Developer Experience Team, Digital Office

Hi @Naptimecoder @mundane-monica ,
:rotating_light: Final call! This is your last chance to confirm the status of your repositories as part of the migration to the bcgov GitHub Enterprise organization.
Leave a comment on this issue by December 20, 2024, to confirm whether your repositories are:

Active and ready for migration, OR
No longer needed and can be archived.

If we don’t hear from you by the deadline, we’ll proceed with archiving your repositories.
Questions? Email<EMAIL_ADDRESS>Thank you for your prompt response!
The Developer Experience Team, Digital Office


Default rect mode setting

Should the default rect mode stay as the corner? Should it default to center instead?

Yes, this seems easy to make consistent with the other ellipse and image modes.

#26 PR to align RectMode


[bug]: input will stuck on git branch name when operating a huge repo(like chromium)

Describe the bug
input will stuck on git branch name when operating a huge repo(like chromium)
Steps to reproduce
go to chromium's repo and input git checkout branch name, it will stuck on branch name
Expected behavior
show branch name very quick
Screenshots and recordings
https://asciinema.org/a/aB5kTff6sT84Ev9b2Mr13IJXf
Operating System & Version
linux-gnu | pc | x86_64 | x86_64 | x86_64 x86_64
Zsh version
zsh 5.8 (x86_64-pc-linux-gnu)
Terminal emulator
xterm-256color
If using WSL on Windows, which version of WSL
WSL2 version: <IP_ADDRESS>
Additional context
No response

i am having the same issue. Will there be a fix soon?

Same here, any news?


The plot method returns the wrong xlabel if run on a folded light curve.

I'm not sure how to fix this. The plot method has xlabel as a keyword, but the default is Tim - BJDREF. This is usually fine but if you've folded it this should be Phase.

The only solution I can think of is to have an attribute which describes the quantity in flux and time which would then be used as x and y labels in all the plots.

This can be fixed by the user if they pass the xlabel keyword...but we're not doing it. And it's in all our docs and tutorials and gifs.

I've proposed a fix in #64.

#64 has been merged, meaning this issue should be fixed no!


[Bug?]: 0.7.2, solid-start repo examples can't find "@solidjs/start/client" types

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
I'm on the latest commit as of writing (0.7.2 release commit) - b2a7b2761d87bf683880027a65a5527af4252e50
Tried to update my clone of the solid-start repo, and run a fresh pnpm i, pnpm run build and pnpm run build:all, and the examples now all breaks due to some missing types of the "@solidjs/start/client" and "@solidjs/start/server":
│ ┌───────────────────────────────┐
│ │ 📦 Compiling ssr router...    │
│ └───────────────────────────────┘
│ vinxi building router ssr in http mode
│ vite v5.1.4 building SSR bundle for production...
│ transforming...
│ ✓ 4 modules transformed.
│ x Build failed in 173ms
│  ERROR  [vite]: Rollup failed to resolve import "@solidjs/start/server" from "/Users/admin/repos/solid-sta…
│ This is most likely unintended because it can break your application at runtime.
│ If you do want to externalize this module explicitly add it to
│ build.rollupOptions.external
│   This is most likely unintended because it can break your application at runtime.
│   If you do want to externalize this module explicitly add it to
│   build.rollupOptions.external
│   at viteWarn (/Users/admin/repos/solid-start/node_modules/.pnpm/vite@5.1.4_<EMAIL_ADDRESS>│   at onRollupWarning (/Users/admin/repos/solid-start/node_modules/.pnpm/vite@5.1.4_<EMAIL_ADDRESS>│   at onwarn (/Users/admin/repos/solid-start/node_modules/.pnpm/vite@5.1.4_<EMAIL_ADDRESS>│   at<EMAIL_ADDRESS>│   at Object.logger [as onLog]<EMAIL_ADDRESS>│   at ModuleLoader.handleInvalidResolvedId<EMAIL_ADDRESS>│   at<EMAIL_ADDRESS>│  ERROR  [vite]: Rollup failed to resolve import "@solidjs/start/server" from "/Users/admin/repos/solid-sta…
│ This is most likely unintended because it can break your application at runtime.
│ If you do want to externalize this module explicitly add it to
│2build.rollupOptions.external
│ │ ⚙  Building your app...    │n/repos/solid-start/examples/basic

Expected behavior 🤔
No response
Steps to reproduce 🕹
Steps:

Context 🔦
No response
Your environment 🌎
No response

build:all is running all the build tasks in parallel, including the task for start, which clears dist when it begins. As it stands the rest of the examples need to wait for start to build before they build.

Okay, so I can run pnpm run build first in root, and then in one example, and that will work, but build:all will break.