[Enhance] limit maximum length of JSON string to 16MB

What type of PR is this：

[ ] bugfix
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Limit the maximum length of JSON string to 16MB, to avoid memory allocation and storage issues.
Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

@Mergifyio backport branch-2.2 branch-2.3 branch-2.4

run starrocks_be_unittest

run starrocks_admit_test

run starrocks_admit_test


[GitHub] enable github issues and projects.

also enable dependabot alerts (but no PRs)
disable force push to main branch

As per mailing list discussion.

Following this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed
for the change (usually before you start working on it).  Trivial changes like typos do not
require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[X] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [SHIRO-XXX] - Fixes bug in SessionManager,
where you replace SHIRO-XXX with the appropriate JIRA issue. Best practice
is to use the JIRA issue title in the pull request title and in the first line of the commit message.
[X] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[X] Run mvn clean install apache-rat:check to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If you have a group of commits related to the same change, please squash your commits into one and force push your branch using git rebase -i.

Trivial changes like typos do not require a JIRA issue (javadoc, comments...).
In this case, just format the pull request title like (DOC) - Add javadoc in SessionManager.
If this is your first contribution, you have to read the Contribution Guidelines
If your pull request is about ~20 lines of code you don't need to sign an Individual Contributor License Agreement
if you are unsure please ask on the developers list.
To make clear that you license your contribution under the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

[X] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
[X] In any other case, please file an Apache Individual Contributor License Agreement.

We could also consider adding labels, other branch protection rules and/or dependabot PRs. Whatever you like.
See: https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-GitHubsettings

We could also consider adding labels, other branch protection rules and/or dependabot PRs. Whatever you like. See: https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-GitHubsettings

Good idea, we can add label like the Jira components we already have.


GH-39088: [Dev][Java] Add Dependabot configuration for Java

Rationale for this change
We can add MINOR: [Java]  prefix to PRs from Dependabot automatically.
What changes are included in this PR?
Add a configuration for Maven.
Are these changes tested?
No. I want to test this by merging this to main.
Are there any user-facing changes?
No.

Closes: #39088

@lidavidm What do you think about this? I don't want to prepend MINOR: [Java]  to PRs from Dependabot manually...


Problem when show/hide the canvas

I am having an issue when show/hide the canvas.
I created a page using bootstrap tabs, on each tabs, i have an signature canvas.
In first time page loaded, the canvas display well on 2 tabs, but when switch back tabs, the width/height of that canvas set to 0.
As i debugging it, the function calculateScale() called to calculate the width/height and ratio of canvas, but when the canvas is hidden, it can't get the width/height.
How can i re-call to init width/height from the values that passed as property param in the directive?
<div class="container" style="max-width: 700px; max-height: 300px">
    <signature-pad accept="accept" clear="clear" height="220" width="568" dataurl="dataurl"></signature-pad>

I've also been having this problem. I ended up with a workaround of sorts. If you set the height on the .signature class with !important, it should do the trick. Just make sure that value is bigger than the height you specified on the control itself as it limits it with max-height.

@ahovingh : Could you show your workaround? I also fixed it by the way added an timeout to calculate with/height of that canvas containner. But it raise another problem, when you clear, the scale set to 0, the cursor point to a place but signature draw another place( as you zoom in)

I was experiencing a similar problem where the signature-pad canvas was height: 0, width: 0. My workaround was adding a style to the <signature-pad style="min-height: 200px; min-width: 500px;" ...>


confirm not recognized

in the readme it states:

#Wait that the dump transaction get confirmed on your favorite exchange, then unlock your coin in your Bitcoin Core wallet
confirm 38348679e28c9df785dd0d70b5db5b45986ed107ebbe1248bb7bfbdca74cc063

but
>>> confirm
BCCSpliter 1.0.0
Copyright (C) 2017 BCCSpliter

ERROR(S):
  Verb 'confirm' is not recognized.
  --help       Display this help screen.
  --version    Display version information.

also tried confirm txid
meeanwhile BTC wallet listlockunspent yields an empty array

Nicolas removed that confirm command (and the lock/unlock stuff) in the most recent version, he just didn't update the howto yet.

I removed yes, it is not needed anymore as BTC transaction can't be replayed.


Add "list-images" and "image-delete" commands

Add some minimal image management commands.  Neither is really in scope for a building tool, but it reduces the number of use cases where we need additional tools.

I would prefer not to add additional verbs, just use buildah list and buildah delete.

LGTM.  For images docker uses 'images' for list and 'rmi' to remove.  For containers 'ps' and 'rm'.  Should we emulate that or do you think the code should recognize the object and do the right thing?

We can overload delete so that it looks for a container first, but with free-form names around, we're inevitably going to need some way to specify what type of thing was intended.  We have distinctly different things to display for images and containers, and every output format I can come up with that encompasses both just looks messier if you only care about one or the other.

Can't we just force user to specify --image or --container when their is conflict.

@rh-atomic-bot r+  	0e702d6


Issue with iOS Injection Modules

Adding various modules which are then imported DI.MainBuilder {} seems to crash when running the iOS app.
DI {
   import(module)
...
}

val module = DI.Module("module_name") {
...
}

This seems to work on Android, but running the same code on iOS crashes.

duplicates #295


SIngle Link Manipulator in ROS2 Humble

Hey! The ROS Noetic code is already in ROS2 Humble, different syntaxis and everything so give a check.

Thank you Jesus for your contribution


Why does GCC compiler using ARM64 format on Apple silicon compile X86_64 format?

I set platform=native on Mac M1 and it compiles using my native gcc compiler. Why is my native gcc compiler in ARM64 format and able to compile x86_64 files? This caused an error when linking to sdl2 in arm64 format that homebrew downloaded

I ran into the same problem.
For my situation, the Platform IO installed was Darwin_x86_64. I don't know why it happened. My guess is that when I first installed the PlatformIO IDE extension, I was in a VSCode running in Intel mode, which could be a result of starting the VSCode from an Intel mode shell.
pio  system info
--------------------------  ---------------------------------------------
PlatformIO Core             6.1.13
Python                      3.11.7-final.0
System Type                 darwin_x86_64

To fix, I did the following

Uninstall the PlatformIO ID extension from VSCode.
Remove the $HOME/.platformio created by the PlatformIO IDE
Reinstall the PlatformIO. Now I got the right version.

pio  system info
--------------------------  ---------------------------------------------
PlatformIO Core             6.1.13
Python                      3.9.6-final.0
System Type                 darwin_arm64

Just in case someone else stumbles upon this issue. I gave up on using the VSCode IDE and instead just installed paltformio via homebrew
brew install platformio

I also had to change python to python3 in the platformio.ini file (Or, you can set an alias from python -> python)

Closing this issue as it’s resolved


devon4j installation instructions should make a note on patching

Category: enhancement
Severity: Low
Description of issue / expected enhacement /Comments
The instructions how to install devonfw distribution on https://github.com/devonfw/devonfw-tutorial-sources/wiki/build-devon4j-application tell the user how to unzip the distribution and - in the next step - how to initialize it using update-all-workspaces.bat. After that, the instructions tell the user to start developing.
The instructions should tell the user to look for patches (e.g. win_accumulative_patch_20190115.zip) that should be applied to the distribution before starting to develop.
Your environment - windows/Linux, Devonfw version , component
irrelevant

With the new IDE that we are now linking it's not necessary to update workspaces manually anymore.


Add mergeMapConcurrently type definition

mergeMapConcurrently seems to be missing its type definition.
I have checked that copying-and-pasting these definitions into my project's<EMAIL_ADDRESS>seemed suggest types as documented, but not tested seriously.

Hey @gitusp thank you for taking the time to open this PR! I have a few small comments that I think will make these definitions ready for everyone.

The 2nd and 3rd overload should be reversed. If 3 parameters are not given, TypeScript will always match the 2nd overload given that one will always be able to match the first argument. Here's a quick example of what I mean. In general you'll want the most initial params declared towards the top and the least initial params declared towards the bottom.

After the current 2nd and 3rd overloads are switched, the then 3rd & 4th overloads likely should be merged in order to properly take advantage of them. Here's one more example of how the situation (after addressing the first point) that the types get us into when trying to use the parameters one-by-one. I believe the 3rd overload should become something like

declare function mergeMapConcurrently<A, B>(f: (a: A) => Stream<B>): {
  (concurrency: number, s: Stream<A>) => Stream<B>
  (concurrency: number): (s: Stream<A>) => Stream<B>
}

This will allow TypeScript to follow the overloads like a tree structure and allow all valid use of the function.

Hey @gitusp, thanks!  I just opened #290 to fix an issue with the mergeMapConcurrently flow defs.  It uses the same partial application technique @TylorS recommends, so even though it's Flow rather than TS, may be a good reference.

Thanks so much @TylorS and @briancavalier! I played around @TylorS's examples and confirmed what you mentioned. That was really good to know.
I ported @briancavalier's new flow defs into TypeScript and confirmed that the new definitions works on all the forms of partial application.
Before

After


Add exception handler in spec at_exit

Exceptions bubbling up from at_exit handlers are printed without backtrace by default, but since the entire spec run happens in an at_exit handler, we should make sure to have full error reporting.

Singlehandedly +10% to productivity when porting things to Windows

Can we change at_exit?

Maybe... I'm not sure about the reasoning for not skipping the backtraces. It basically has been like this since forever.
I just want to improve specs behaviour. Always printing backtraces from exit handlers would work for that.


Unable to set the width on the sidebar component

Have tried the following just to see if my class gets passed to the  element, but it does not seem to happen.
<Sidebar v-model:visible="visible" header="Sidebar" class="tester" :class="testertester">
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
         </Sidebar>
    "primeicons": "^6.0.1",
    "primevue": "^3.40.1",
    "vue": "^3.3.4"

Hi,
Thanks a lot for your report! But, I think this issue is related to PrimeVue core. Can you please create an issue with a sample stackblitz link in PrimeVue Github?
Best Regards,


Force PHP syntax highlight for stub files

This pull request makes nicery :)
Preview: https://github.com/szepeviktor/phpstan-prophecy/blob/patch-1/stubs/ObjectProphecy.phpstub 🤩

Thank you, @szepeviktor!

You're welcome.


Include package.json with external dependencies (node_modules) when using @ns3/nx-serverless/plugin

I have a task to run chrome inside aws lambda. For this I need a specific binary that can't be bundled as plain JS. So I have to deploy them as npm dependencies inside node_module package. Currently I didn't find a possibility to somehow include package.json in the function deployment as well as executing of npm i or npm ci before zipping

Hello. If you are using my experimental @ns3/nx-serverless/plugin you could use @nrwl/webpack:webpack executor to generate package.json and work with that.
Other way would be to probably use something like serverless-webpack/serverless-bundle and write your own webpack code to do it.
At the end of the day this is a more special case and needs to be handled that way. I hope it helps.

Hello. If you are using my experimental @ns3/nx-serverless/plugin you could use @nrwl/webpack:webpack executor to generate package.json and work with that.

How would you include the package.json in the zip package? @nx/webpack:webpack generates that file in the output path (usually dist/packages/my-app-name)

I've tried adding the globs to package.includes, namely ../../dist/packages/my-app-name/package.json since the includes path is relative to projectRoot. It turns out the packagin plugin copies it to an incorrect path, messing up the generated zip...
Also, is the includes property standard in serverless? I haven't found it documented anywhere.

I've got it working by hacking the plugin code.
These are the feature requirements I've found:

Even after generating package.json with nx webpack, it's necessary to generate node_modules for that given package. The current serverless executor won't allow it, as it requires the build target to be executed by itself in order to get the ouputs. I believe this could be fixed by allowing the user to add a postBuild target which the serverless executor would run
In some cases it's necessary to copy files from workspace node_modules (ie Prisma client), this also must be done after build. The same solution from above could be applied here
The plugin should be able to add extra files from outputPath to the package (namely package.json generated by webpack, any lock files and node_modules). This is discussed in https://github.com/Bielik20/nx-plugins/issues/93

Note that for this scenario it's better to deploy a Docker image to Lambda.


rewrite push_colname push_rowname

rewrite in a more idiomatic way:
pub(crate) fn push_colname(buf: &mut String, mut col: ucell);
pub(crate) fn push_rowname(buf: &mut String, mut row: ucell);
add test for this two functions(compatibility with the old one)
correction of the overflow bug  (fixes #6)

I forget pub(crate) sry


Work out user controller implementation

split up code into dedicated files
only accept validated input for user init/update
hash passwords
update dependencies
reduce use of "string" literals
add update route

@steffendsommer it turns out, the BCryptHasher already includes salt. So if you use drop.hash for the UserController and configure it correctly it should be secure enough.


Docs(french): Change getting started

What: Translation in french "Copy get-started part in readme into website" (Related #164)
Why: Documentation in several languages is better
How: Translate in french

cc @Macxim @bulby97 @etiennetalbot 🇫🇷
@kentcdodds Perhaps we'd like some of these people to be collaborators so we can assign reviews to them? If they are willing to contribute of course. 😄

@kentcdodds oh, and can we add labels for each of the languages please? Will make it easier to find relevant issues/PRs if people want to focus on a particular language of the site.

I am a volunteer for the reviews of translations in French (except of course my own translations)

Again, things have changed a little bit. We're no longer using js files, we're using markdown. Please see the updated docs :)
This should be much better! :tada:


INLINE [instead of Embedded] svg option : relative link issue

Hi.
INLINE SVG option
With embed tag, relative links inside the kroki diagram are resolved relative to the kroki server instead of the embedding document server.
I am using Kroki with Vitepress Static site generator.
The kroki team suggest "INLINE" SVG at the build time as the solution to  issue
Could you provide an option for inline svg please.
Issue History on Kroki
https://kroki.zulipchat.com/#narrow/stream/232085-users/topic/Relative.20link.3A.20relative.20to.20site.20base.20instead.20of.20kroki.20server
Sample repository:
https://stackblitz.com/edit/vite-sepohb?file=docs%2Findex.md
For correct rendering on stackblitz : use the button "Open in New Tab"
Besr regards,
Tshitshi

For correct rendering on stackblitz : use the button "Open in New Tab"

Konbanha.
I'm so sory, but I'll NOT implement INLINE SVG option.
I think mordern JS engines do NOT  allow to use sync-https request.
(Almost all API are implemented as callback-style, promise-style, or async-await style.
sync api obsolated or not recommended.)
To support INLINE SVG means that we have to down-load svg from kroki.io, and insert it into html on parsing markdown syntax.
But, markdown-it plug-in MUST be implemented sync style..... see here
Is there fine method to fetch svg from kroki with sync ?
I have no idea...... sory....

As far as I understand, this is a markdown-it limitation. You can use XMLHttpRequest to download the SVG from Kroki synchronously. markdown-it runs at build time (i.e., using Node.js or a headless browser) or at rendering time (client side) using the browser?
If it runs at build time, I guess it's fine to get content synchronously.
As a workaround, you could try output the SVG using an <img> tag. I'm not sure if links will resolve relative to the origin or relative to the target... But it's worth a try.
Another workaround, would be to prefix relative paths by the site base URL but your plugin probably doesn't know the base URL.

@ggrossetie
Thank you for your effort.
You are right !
As you said, the synchronously problem  is markdown-it limitation.
And as you said, to avoid the problem I can use XMLHttpRequest.
But I don't wanted to use the mehod by two reason.
First  of all, XMLHttpRequest is non-native method on nodejs environment.
If  we want to use this method, We have to use a third party library like this.
I wanted to implement this library to be light-weight as possible.
(see package.json).
Secondary, basic concept of this libary is to create link urls for krokii and to embed them to html,
NOT to bring the image data over network and embed them.
Conclusion
I'll consider for API, to be able to render yourself, like this.
md.use(require('@kazumatu981/markdown-it-kroki'), {
        entrypoint: "https://kroki.io",
        render: imageRender
});
function imageRender(krokiUrl, someKindAttribute) {
     // build htmlFragment.... like INLINE SVG
    return htmlFragment;
}

How do you thik ??

I'll consider for API, to be able to render yourself, like this.

I think it's an excellent idea to give users the choice to implement another strategy in order to integrate their diagrams into the HTML page 👍🏻

Thank you for the support.
Given the choice globally as well as per diagram inside each md could be
optimal.
Best regards,
Tshitshi
Le ven. 9 févr. 2024 à 09:14, Guillaume Grossetie @.***>
a écrit :

I'll consider for API, to be able to render yourself, like this.
I think it's an excellent idea to give users the choice to implement
another strategy in order to integrate their diagrams into the HTML page
👍🏻
—
Reply to this email directly, view it on GitHub
https://github.com/kazumatu981/markdown-it-kroki/issues/4#issuecomment-1935497513,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALX32WNXTTYFYK4WF274TV3YSXLFXAVCNFSM6AAAAABCXX76NCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVGQ4TONJRGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks all, I'll implement this interface. Just moment please....

Hi all.
I've implemented.
Read my memo and please enjoy.

Hi.
Thank you very much. Unfortunately I don't see how to use it in my case.
@Guillaume Grossetie  could you help please?
Best regards,
Ts
Le dim. 11 févr. 2024 à 11:58, Kazuyoshi Matsumoto @.***>
a écrit :

Hi all.
I've implemented.
Read my memo
https://github.com/kazumatu981/markdown-it-kroki/blob/main/memo/howToWriteRender.md
and please enjoy.
—
Reply to this email directly, view it on GitHub
https://github.com/kazumatu981/markdown-it-kroki/issues/4#issuecomment-1937568194,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALX32WLTMJTTEEFEQFPI2LDYTCP3JAVCNFSM6AAAAABCXX76NCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGU3DQMJZGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


DAT-11090. Added a line to readme to force a build.

THIS PR SHOULD BE CLOSED WITHOUT EVER MERGING! It is to force a liquibase/liquibase build of this branch and unblock internal Liquibase functional test execution.

This PR was created to enable the Liquibase internal functional tests to execute. Closing.


DeprecationWarning in README examples.

Environment

Qiskit Finance version:
qiskit                0.44.0
qiskit-algorithms     0.1.0
qiskit-finance        0.3.4
qiskit-optimization   0.5.0
qiskit-terra          0.25.0
Python version: 3.10.6
Operating system: Mac Ventura 13.4.1 (c)

What is happening?
This error appears when running the README example.

/Users/achicks/qiskit-f/finance_demo.py:2: DeprecationWarning: qiskit.algorithms has been migrated to an independent package: https://github.com/qiskit-community/qiskit-algorithms. The qiskit.algorithms import path is deprecated as of qiskit-terra 0.25.0 and will be removed no earlier than 3 months after the release date. Please run pip install qiskit_algorithms and use import qiskit_algorithms instead.
from qiskit.algorithms import AmplitudeEstimation

How can we reproduce the issue?
Run the README.md example.
What should happen?
The README.md should say this:
import numpy as np
import qiskit_algorithms
from qiskit.primitives import Sampler
from qiskit_finance.circuit.library import NormalDistribution
from qiskit_finance.applications import FixedIncomePricing

# Create a suitable multivariate distribution
num_qubits = [2, 2]
bounds = [(0, 0.12), (0, 0.24)]
mvnd = NormalDistribution(
    num_qubits, mu=[0.12, 0.24], sigma=0.01 * np.eye(2), bounds=bounds
)

# Create fixed income component
fixed_income = FixedIncomePricing(
    num_qubits,
    np.eye(2),
    np.zeros(2),
    cash_flow=[1.0, 2.0],
    rescaling_factor=0.125,
    bounds=bounds,
    uncertainty_model=mvnd,
)

# the FixedIncomeExpectedValue provides us with the necessary rescalings

# create the A operator for amplitude estimation
problem = fixed_income.to_estimation_problem()

# Set number of evaluation qubits (samples)
num_eval_qubits = 5

# Construct and run amplitude estimation
sampler = Sampler()
algo = qiskit_algorithms.AmplitudeEstimation(num_eval_qubits=num_eval_qubits, sampler=sampler)
result = algo.estimate(problem)

print(f"Estimated value:\t{fixed_income.interpret(result):.4f}")
print(f"Probability:    \t{result.max_probability:.4f}")

Please note changes on lines 2 and 35.
Any suggestions?
See Above

Yes, there a whole lot of other places in Finance here that need changing too - some in the code, in unit tests, in tutorials. This will all be switched over to qiskit_algorithms in the near future (as will the other application repos Nature, ML and Opt), ahead of releasing new versions.
The readme will get updated at that point since it needs other changes to ensure qiskit_algorithms is installed here in CI so that the readme passes the unit test - it's extracted from the readme and run to ensure it continues to work.
The change I would expect to do though would be more like this
from qiskit.algorithms import AmplitudeEstimation

to
from qiskit_algorithms import AmplitudeEstimation

where simply qiskit.algorithms is replaced by qiskit_algorithms.
I will note, though you refer to it as an error, its a warning - the code still works it's just advising the change, which as I noted above is planned to be done soon.


more visualization in AYS (Command Line Only)

to be defined how (Kristof)

@despiegk can you elaborate?


Add clickToShareAction

Add a clickToShareAction

This PR adds the navigator.share API as an action. This is an easier user experience given browser support, especially on mobile devices.
navigator.canShare can be used to determine if the browser supports the navigator.share method.
{#if navigator.canShare}
    <button use:clickToShareAction={{ text, title, url }}>
        Click to share
    </button>
{/if}

https://developer.mozilla.org/en-US/docs/Web/API/Navigator/share

@ankurrsinghal Would it be possible to call the clickToCopyAction as a backup?

Hey @rossrobino I will check this and get back to you later. Have a lot pending actions and utilities on plate.

@ankurrsinghal I can work on it I'll see what I come up with.


How to use?

How can I sign a txt file using this package?

Hi @emtudo .
Actually you can't sign any document with this package. Main purpose is manipulating existing cades signature.
Every country or vendor emplements own interface/application to sign documents.
But I'm gonna implement such feature in nearest future


Hello, the reverse imgur failed.

url：https://wsrv.nl/?url=https://i.imgur.com/n1jWucc.png
error：{"status":"error","code":404,"message":"The requested URL returned error: 429"}

Duplicate of #319


VIP Split: Resource Update Request - Referral Programme

Publish Date 1 May
Draft here
To note these are three tiny changes to an existing doc, should take less than a minute to review hopefully!

Bumped Ren in Slack, this one is ready for review / implementation

I'm ready to be assigned!

Perfect @ren-jones 👍 all yours

NB - we're in a deploy freeze now, so any PRs on this won't be merged until next week

Ren pointed out this is currently on Expensify Classic site rather than NewDot - I missed that detail, so we need to migrate this over to the correct hub.

thinking more about this, while I agree this should live on newdot, it's fine for us to push the simple changes now. I think the whole partner programme section will need to be migrated, but we can do that at a later point and this doesn't need to be blocked on that.


[BUG] Queued Jobs Incorrectly Showing Waiting on Temp Space

I have two 1 TB temp drives, so when I queue jobs I do 3 at a time for each drive. Occasionally one of the drives will only queue 2 at a time thinking there is not enough free space. When I check the temp drive it has over 500GB free. Manually quitting all the job queues and adding new ones does not resolve the problem as it will show the same status of "Waiting on Temp Space". The only way to fix it is either close the GUI or wait for all the queued plots to finished and start new job queues. Neither of these are a viable solution as I lose valuable plot time.

I also noticed that the # of Runs in incorrect in the this screenshot. It's showing 4 for drive D: but I'm only currently running 3. I was able to force the queue to start by use the "Ignore MaxParallel" option.


Update README.md

The following flag has been replaced but it is not mentioned in the main readme file and only in release notes which makes this prone for confusion. --es.cluster_settings has been renamed to --collector.clustersettings

Hi @xogoodnow can we also change this line https://github.com/prometheus-community/elasticsearch_exporter/blob/master/README.md?plain=1#L91 ?

Hi @clavinjune,
I didn't understand what you said.
Could you please explain what you mean exactly?

please also remove this one https://github.com/xogoodnow/elasticsearch_exporter/blob/patch-1/README.md?plain=1#L56

@SuperQ @sysadmind could you please help review this MR :bow:

please also remove this one https://github.com/xogoodnow/elasticsearch_exporter/blob/patch-1/README.md?plain=1#L56

This option "es.indices " is working fine, is there is particular reason on why to omit this line?

Hi @clavinjune, on "es.cluster_settings" (L56), I have mentioned that this flag has been deprecated as of v1.6.0.
So IMHO, I believe it would be better for backwards compatibility to keep this flag in the document.

in 1.6.0, if you use that flag, the exporter won't run. Since the said flag is also marked as breaking changes, I don't think we need to  have that on the readme, wdyt?
I guess we can leave that to the maintainer's judgement

in 1.6.0, if you use that flag, the exporter won't run. Since the said flag is also marked as breaking changes, I don't think we need to have that on the readme, wdyt?
I guess we can leave that to the maintainer's judgement

Yes I agree.
also since no other deprecated flag is mentioned in the readme file, for the sake of consistency I deleted the flag .
As an example in V1.4.0 >> Rename elasticsearch_process_cpu_time_seconds_sum to elasticsearch_process_cpu_seconds_total. But there is no mention of "elasticsearch_process_cpu_time_seconds_sum" in the main readme file (Metrics).
In the next release, the flag --es.snapshots could be renamed to --collector.snapshots. So if that happens, we need to change the readme for this flag as well.
Thank you @clavinjune


AssertionError: Cannot find .runfiles directory for bazel-bin/tensorflow/python/tools/freeze_graph

After I install the tensorflow from source, i'm trying to use freeze_graph tool, and it appear this error.
My OS is MacOS 10.12.5

hi,how can you deel with the problems, I meet it now

Hi, what Bazel version are you using? There's a whole list of tensorflow native builds and their accompanying requirements. https://www.tensorflow.org/install/install_sources


goog.ui.Dialog dragger prevent hidding the window outside of desktop browser

The structure of the dialog draggable title bar goes as follow:

Because the draggable is applied on the parent of the .close-btn it seems that no click event can be produced by close-btn due to touchStart being triggered and mouseDown being forbidden by dragger.js.
Step to reproduce:
http://google.github.io/closure-library/source/closure/goog/demos/dialog.html
DESKTOP BROWSER - Move over button, click (traces produced using the monitorEvents($0) method)
''mousemove MouseEvent {isTrusted: true, screenX: -364, screenY: 93, clientX: 1556, clientY: 8…}
focus FocusEvent {isTrusted: true, relatedTarget: null, view: Window, detail: 0, which: 0…}
mousedown MouseEvent {isTrusted: true, screenX: -364, screenY: 93, clientX: 1556, clientY: 8…}
mousemove MouseEvent {isTrusted: true, screenX: -364, screenY: 93, clientX: 1556, clientY: 8…}
mouseup MouseEvent {isTrusted: true, screenX: -364, screenY: 93, clientX: 1556, clientY: 8…}
blur FocusEvent {isTrusted: true, relatedTarget: null, view: Window, detail: 0, which: 0…}
click MouseEvent {isTrusted: true, screenX: -364, screenY: 93, clientX: 1556, clientY: 8…}''
IPAD EMULATION - Move over same button, click -> intercepted by dragger    - Can not produce a click event in this case, ever.
''touchstart TouchEvent {isTrusted: true, touches: TouchList, targetTouches: TouchList, changedTouches: TouchList, altKey: false…}
touchend TouchEvent {isTrusted: true, touches: TouchList, targetTouches: TouchList, changedTouches: TouchList, altKey: false…}''
A solution would be to restructure the dialog title bar (not really convenient in terms of positionning):

Your title

Another solution would be to let the mousedown event continue its bubbly phase instead of halting the event in dragger.js with this.preventMouseDown_.

Probably don't want to restructure the DOM. Happy the review a PR with a solution.
You might also be able to set hysteresis on the dragger.

This issue is being closed as a preparation step before archiving the repository.  See the README for more detail.


Refresh is broken on V8

Refresh causes NativeEngine's constructor to crash while attempting to access some static state inside BGFX while spinning up the new JavaScript runtime. Creating this issue to track; will update with more specific details when I have them.

Fixed in #157


It doesn't work with typescript v4.8.3

Describe the bug
It's not working with typescript v4.7.x ~ v4.8.x
How to Reproduce
Steps to reproduce the issue. Attach all resources that can help us understand the issue:
Please check typescript changes.

Screenshots
Link to GitHub repository with project that has issues
Files that can help reproduce the issue, like your AsyncAPI file, either paste inside the issue in a code block or in a sharable gist

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

@iamdenny feel free to open up PR with the fix, if it is only about bumping typescript dependency


separate original and translated text

As the title says, how can I separate the original text (Japanese) and the one that is already translated (English) from _AutoGeneratedTranslations.txt
since I want to translate the already translated text into Spanish
I'm sorry if you don't understand something since I'm using Google Translate.

Regex:^(.*)=
Works for most of my use cases, unless there is rich text and color codes, but I sort my translation files beforehand so I can catch it easily.
Anyway, use notepad++ Mark feature with regex and Copy Marked Text:


fix(docz-core): parse host when running serve

Description
When I start deploy docz project in my own server, i found that server publish ip address can not be access but localhost can, and after checkout gatsby cli command, i found the problem is host is always be localhost and can not be changed to others when use docz serve.

Thanks @ShinyLeee 👍


Improving contribution experience

Problem: It is difficult to find issues to contribute to because it is unclear if anyone is working on it. We have to read the entire conversation to figure out if someone is working on it or not.
Solution:
Assign folks to the issue or maybe add a label Up for grabs for issues which need new contributors and removing it when someone starts working on it.
Thoughts?

Definitely! Ideally we can setup some prow for this
Very good idea!
Also you looks like you just found issue which is not assigned to anyone
yet... ((:
On Tue, 21 Apr 2020, 17:22 Rajat Varyani<EMAIL_ADDRESS>wrote:

Problem: It is difficult to find issues to contribute to because it is
unclear if anyone is working on it. We have to read the entire conversation
to figure out if someone is working on it or not.
Solution:
Assign folks to the issue or maybe add a label Up for grabs for issues
which need new contributors and removing it when someone starts working on
it.
Thoughts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/thanos-io/thanos/issues/2493, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVA3O7WL4S6VYYDZKCOFVLRNXB4FANCNFSM4MNNDWEA
.

I can help in any way I can.  What would be the next steps?


Replace Google Fonts with locally served fonts

Add Lato, Ubuntu, and Ubuntu Mono to /public/fonts.
Replace references to Google Fonts API with that of a new fonts.css file, which contains the @font-face declarations for the above fonts.
I verified the changes in a temporary html file, but was unable to run the FCC repo locally and see if everything works. Will happily rework it if anything breaks.
Closes #3311.

Merged! Thanks for you help @leonfeng.
In the future, please name branches using the convention fix/some-bug or feature/add-cool-thing. see contributing
Thanks and Happy Coding.

@BerkeleyTrue Roger that. Cheers~


Data Table for Heartrate Data

Intgration of Data Table for Heartrate Parameters
Use MDL-Tables:
https://getmdl.io/components/index.html#tables-section

Fix bug with selection boxes, see:
https://codepen.io/Garbee/pen/wKpgNb

restyled and completed


Skip installing user dependencies for now dev

Skip installing user dependencies for now dev to speed up the processes.
This further fixes linting issues for @now/next.
Fixes https://github.com/zeit/now/issues/2792

Codecov Report

Merging #2926 into canary will increase coverage by 1.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           canary    #2926      +/-   ##
==========================================
+ Coverage   12.08%   13.24%   +1.16%
==========================================
  Files         267      267
  Lines       10268    10409     +141
  Branches     1239     1172      -67
==========================================
+ Hits         1241     1379     +138
- Misses       8937     8968      +31
+ Partials       90       62      -28

Impacted Files
Coverage Δ

src/util/dev/router.ts
82.69% <0%> (+4.12%)
:arrow_up:

src/util/dev/builder.ts
77.41% <0%> (+4.34%)
:arrow_up:

src/util/dev/yarn-installer.ts
90.74% <0%> (+5.02%)
:arrow_up:

src/util/dev/server.ts
67.07% <0%> (+5.68%)
:arrow_up:

Continue to review full report at Codecov.

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

@Timer This was turned off in #2914 to unify the formatting in this monorepo. The point of the monorepo is to move common stuff to the top and formatting is one of those things. This matches the now-cli settings.


[URGENT]Add service unavailability callout

Make a SORN and Vehicle Tax online services will be
unavailable from 11:15pm on 12 January to 8am on 13 January
This is a hack but the deploy slot is at 16.30 and anyway we will need to revert the changes tomorrow morning.
https://www.agileplannerapp.com/boards/105200/cards/9111

You will probably also need to copy over icon-important-2x.png and icon-important.png from static for the asset urls to work.

Do I? It works on preview/

The images are being provided by the frontend_toolkit. LGTM.


Show total Nightmare Zone points

When inside a Nightmare Zone dream (session) both the vanilla client Nightmare Zone interface and Runelite's Nightmare Zone plugin show the number of Nightmare Zone points earned within the dream you're currently in, but not the total points (i.e. points you had before you entered the dream + points earned during the current dream). This is inconvenient because it may take multiple dreams to get the number of points needed to imbue something, in which case you have to remember how many points you had before you entered the dream in order to know when you have earned enough points rather than being able to see it in the interface.
Would it be possible to show the total number of Nightmare Zone points in the Nightmare Zone plugin's overlay, in addition to the number of points earned just in the current dream already shown?

#6701

#6701


Singular transfomer model if L1=L2=M

Reported by otter on 8 Mar 2013 11:12 UTC
Model Modelica.Electrical.Analog.Basic.Transformer fails, if parameters L1=L2=M. The reason is that the number of states is reduced in this case and a tool might be not able to detect this during translation. As a result, simulation fails with a division by zero.

Migrated-From: https://trac.modelica.org/Modelica/ticket/1011

Comment by otter on 8 Mar 2013 11:17 UTC
Fixed in c2f552ffda7997e5519ac01f3732d2c59c69eeec
based on a suggestion by Sven Erik (use a relative potential formulation). Additionally, a test model included in ModelicaTest to verify that a transformer with L1=L2=M can be handled.

Modified by otter on 9 Mar 2013 05:42 UTC

Modified by majetta on 5 Apr 2013 12:53 UTC

Changelog modified by majetta on 5 Apr 2013 12:53 UTC
Error fixed in Electrical.Analog.Basic.Transformer

Modified by majetta on 10 Apr 2013 08:17 UTC

Changelog modified by majetta on 10 Apr 2013 08:17 UTC
Transformer equations changed to handle the case L1=L2=M. A test model for that case was included into ModelicaTest


SQLSTATE[HY000] [2002] in my face!!

Cant get koel to work for some godforsaken issue
any help will be greatly appreciated (btw m a beginner that's why i couldn't troubleshoot this by myself)

http://bfy.tw/3psD


Screenshot lightbox code broken

Under "Monitor with Update Compliance" the lightbox code is broken and does not display the screenshot correctly:
[[DO status](https://learn.microsoft.com/en-us/windows/deployment/do/images/uc_workspace_do_status.png)](images/UC_workspace_DO_status.png#lightbox)

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

ID: 6e39e363-99f3-a517-ef03-c4f177790551
Version Independent ID: 6e39e363-99f3-a517-ef03-c4f177790551
Content: Set up Delivery Optimization - Windows Deployment
Content Source: windows/deployment/do/waas-delivery-optimization-setup.md
Product: windows-client
Technology: itpro-updates
GitHub Login: @carmenF
Microsoft Alias: carmenf

Thanks @AdmiralTolwyn for catching that. @cmknox has an open PR in our private repo (https://github.com/MicrosoftDocs/windows-docs-pr/pull/7764) to make some changes to this article and others, so I injected a quick fix for that graphic. This issue will automatically close when that PR merges (although I don't have a specific timeline right now).


Site map

Initial design for sitemap for current content

Conflicting PR. Removed from build WWW-merge#259. See the console output for more details.
Possible conflicts:

PR #111 lunson 'propose styles for additional links in Hero sections'

css/openmicroscopy.css

PR #117 lunson 'Add Media'

css/openmicroscopy.css

PR #132 hflynn 'Social hub page'

css/openmicroscopy.css

@lunson I've merged the social hub PR so you can merge master into this PR to fix that conflict but the CSS is still conflicting for the other two PRs. Not sure how you want to handle that?
I'll exclude this for now so it doesn't report the conflict every day.

@hflynn Not sure how to best handle the other two PRs either -- they both need actual content/copy before I can move forward with either of them.

@lunson well, the extra link/button one could either be closed (and I could fetch the content if/when I need to add an extra link) or you could comment out the examples and we could merge it with both styles there for future use.
The Media one probably depends on what order you want things merged in. We could close it for now to get this in first? I don't think there'll be actual content for it for a few weeks yet.

@hflynn Closing both sounds good. This PR is closer to getting ready for merge than the other two.

Actually, I can just exclude them both and then we won't forget about them.

Staged at https://snoopycrimecop.github.io/www.openmicroscopy.org/site-map/

Closing since for some reason there's a merge of my branch into my branch.


Project showcase patches

Problem solved
Primarily moves the files from (dashboard) out to (apps), also added hero section back

PR-Codex overview
This PR focuses on refactoring the import paths in the page.tsx files for the project-showcase feature and updating the hero section layout in the ProjectShowcasePage component.
Detailed summary

Updated import paths for components in apps/dashboard/src/app/(dashboard)/project-showcase/[slug]/page.tsx and apps/dashboard/src/app/project-showcase/page.tsx.
Replaced <Image> component with <img> in both files, adding an ESLint disable comment.
Enhanced the hero section layout in ProjectShowcasePage with new structure and content.
Added two new <Link> components for "Get Started" and "View all case studies".

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Feel free to yell at me later, but due to time constraints and the minor nature of this change (primarily moving files from one directory to the other + cosmetic changes), going to merge this in. Will all be converted to framer as a next step


ENH: Input validation for sampling frequency in signal.filter (#14450)

Reference issue

Closes #14450
What does this implement/fix?

This PR adds input validation for the sampling frequency fs to the filters in signal.filter. Invalid inputs now raise an appropriate ValueError.
Additional information

My flake8 shows a list of code style issues in the files I touched. As far as I can tell I added no new code style issues, but I also didn't fix the existing ones.

It looks like all comments were addressed here. Sorry for the long wait @yetinam , would you like to merge main and resolve any conflicts? If so, we should be able to merge this some time soon.

Hi @lucascolley ,
I had totally forgotten about this. I'll merge main and resolve the conflict in the next days.

Turns out resolving all conflicts after 3.5 years of development is a bit of a hassle. I've created a new PR with identical changes instead in #19971.


Fix bug 19792:  Backstage does not immediately apply new schedules for scheduled items

Hey, I just made a Pull Request!

This PR fixes bug #19792
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Hi @freben, I've follow your recommendation and made another commit. Can you check?

Gonna go ahead and merge this despite the node 16 test failure which is unrelated.


[Feature] add automated UI test for UWP apps

What App Center service does this feature apply to?
Testing
Describe the solution you'd like
add automated UI test for UWP apps.
Describe alternatives you've considered
none.

Thanks for request @JanabiSoft. As I'm not familiar with the UWP UI Testing scene, is there a specific testing framework you would prefer?

hi @Oddj0b i'm not sure about the cloud but locally can be done with windows application driver and appium
https://medium.com/@yostane/automated-ui-testing-of-a-uwp-app-using-appium-dc10d8df6631

@JanabiSoft Thanks for the input, having UWP devices available is only half the work the other half is supporting a testing framework. Getting input from customers is an important step in making the right choice.

Appium already has support for UWP, but unfortunately AppCenter doesn't support the C# Appium client. (as per - https://github.com/Microsoft/appcenter/issues/102)
An alternative would be to add UWP support to Xamarin.UITest.
Either way, currently there is no possibility to write C# UI automated tests that can run on all three platforms: iOS, Android and UWP.

Can you consider the WinAppDriver ?

I'm not sure I understand the question. WinAppDriver is basically Appium, since it is used by Appium under the hood on UWP.

@cosminstirbu You mentioned earlier that it is not possible to write C# UI automated tests that can run on all three platforms, what about writing 2 test systems one for mobiles and one for windows, is it possible?

Well, right now we do in fact write C# UI automated tests for all three platforms using Appium and the .NET Appium Client.
However, we run the iOS and Android ones on emulators created on Azure Devops hosted macOS Agents and the UWP on a OnPremise Windows 10 Agent.
However, it would be great if we could run the iOS and Android tests on real devices on AppCenter.
Writing two UI tests codebases, one for iOS / Android and one for UWP is not an option for us - too much maintenance overhead.

Yes would be fantastic to use Xamarin UI Test for a Xamarin Forms project for all 3: iOS, Android, and UWP - seems logical. Will this be taken on any time soon?

Xamarin.UI test can work with UWP.
The Xamarin.Forms team implemented Xamarin.UI test for UWP:
https://github.com/xamarin/Xamarin.Forms/blob/master/Xamarin.Forms.Core.Windows.UITests/WinDriverApp.cs
It just hasnt been merged into the official Xamarin.UITest.
The way I see it working is using Xamarin.UITest as the testing framework and WinAppDriver, exactyl how the forms team currently do it:
https://github.com/xamarin/Xamarin.Forms/tree/master/Xamarin.Forms.Core.Windows.UITests
If you want to run on physical deviced attached you can run via an ethenet cable:
https://tomsoderling.github.io/Wired-Debugging-on-Surface/
Be nice if the appcenter team could play around with the idea of supporting UWP automated testing

Any movement on this? As a company we need to decide if we will go 'all-in' on Xamarin.UITest, but we will need test coverage in iOS, Android and UWP.

Any update on this?
Is this expected to be in soon or are there any alternatives?

Hi @AvaJV no updates yet but it's something we're considering. in the meantime, we recommend trying out WinAppDriver: https://github.com/microsoft/WinAppDriver. Happy to connect you to that team if you'd like to learn more.
Thanks!

@winnieli1  I've got UWP UI tests (using the WinAppDriver and the Xamarin.Forms implementation of the UWP wrapper https://github.com/xamarin/Xamarin.Forms/blob/master/Xamarin.Forms.Core.Windows.UITests/WinDriverApp.cs)
but I haven't found a way to automate them using Visual Studio Online.
Even following this: https://github.com/microsoft/WinAppDriver/wiki/WinAppDriver-in-CI-with-Azure-Pipelines
Still can't get them to automate

Hi @JKennedy24,
What kind of errors are you running into? Are you using a public "MS-hosted" agent or a private one?

The Xamarin.Forms team implemented Xamarin.UI test for UWP:
https://github.com/xamarin/Xamarin.Forms/blob/master/Xamarin.Forms.Core.Windows.UITests/WinDriverApp.cs
It just hasnt been merged into the official Xamarin.UITest.

Is there an issue or pull request that I can follow so I can be alerted when the merge completes?


Latest version is not updating from modio.

Mods latest version from modio is not right. The latest version displayed in the integrator app for twitch integration is 2.2.4. Whereas the actual version is now at 2.3.6.

And this was after clicking "update cache" to fetch updates?


Debian needs a package maintainer

The Debian package for Unbound seems to be going through a period of neglect: https://packages.debian.org/sid/unbound
As a great many people access Unbound via the Debian repository (and by extension the Ubuntu repository) I feel this neglect harms the Unbound project as a whole.
Is there any scope for one of the Unbound developers to maintain the Debian package?

I'm not a debian maintainer, nor am I an Unbound developer, but I have some packages wrapped up on https://deb.myguard.nl/pool/main/u/unbound/  (or https://deb.myguard.nl/openssl3/pool/main/u/unbound/ for openssl3 builds).

Hi @triatic, did you raise your concerns with the Debian maintainers?
We are not offering packages for Unbound and it is not in our immediate plans.
But maintaining Debian's own package is something completely different which is best left to the Debian community.

Hi @gthess ,
I am unsure of the best way of the best way to contact the Debian maintainers directly, perhaps it would be best coming from an Unbound developer?
My concerns were first raised when attempts were made to get Debian to compile dns-over-https support into the Unbound package. A bug report was filed in November 2020 and remains unresolved.
The latest package release is 1.13.1 and is over a year old.
I note that the ISC releases a PPA for bind: https://launchpad.net/~isc/+archive/ubuntu/bind
Although you say it is not in your plans, I do think it would be a useful service.

JFTR, as I was just stumbling over this issue here:
In the meantime the unbound package in Debian has found a new uploader, and the 1.15.0 release found its way in Debian Sid, as requested in several issues in the Debian Bug Tracking system. See https://tracker.debian.org/pkg/unbound for the current state of the package.
As such I believe this issue here could just be closed.

Yes, it does appear Debian has a long-awaited new maintainer, so I will close this now.


Is nesting of containers possible?

I'm wondering if this allows nesting of elements.
Example: a set of todo lists, each containing todo items. Todo lists may be rearranged, todo items may be rearrange within he same list and also moved between lists.
Thus, the todo lists are sortable but also containers for the todo items.
Would such functionality be a possibility?

#248

https://github.com/bevacqua/dragula/pull/358


Rename repo and update docs

As a developer, I'd like to rename the repo from spring-cloud-dataflow-admin-yarn to spring-cloud-dataflow-server-yarn.

Repo rename is ok, it's just docs.

@jvalkeal pushed doc changes.


CI: K8sServicesTest Checks service across nodes Tests NodePort (kube-proxy)

https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-K8s/3458/testReport/Suite-k8s-1/13/K8sServicesTest_Checks_service_across_nodes_Tests_NodePort__kube_proxy_/
test_results_Cilium-PR-Ginkgo-Tests-K8s_3458_BDD-Test-k8s-1.13.zip
CI dashboard has a lot of similar failures, but they all seemed to be caused by beforeAll failures. Note: The CI build (from backport PR #12990) with this failure occurrence had many other tests failing.
Stacktrace
/home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-K8s/1.13-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:514
Request from testclient-xx9rd pod to service tftp://<IP_ADDRESS>:10069/hello failed
Expected command: kubectl exec -n default testclient-xx9rd -- /bin/bash -c 'fails=""; id=$RANDOM; for i in $(seq 1 10); do if curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 20 tftp://<IP_ADDRESS>:10069/hello -H "User-Agent: cilium-test-$id/$i"; then echo "Test round $id/$i exit code: $?"; else fails=$fails:$id/$i=$?; fi; done; if [ -n "$fails" ]; then echo "failed: $fails"; fi; cnt="${fails//[^:]}"; if [ ${#cnt} -gt 0 ]; then exit 42; fi'
To succeed, but it failed:
Exitcode: 42
Err: Process exited with status 42
Stdout:

	 Hostname: testds-nw5sj

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=50720
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 16035/1 exit code: 0

	 Hostname: testds-nw5sj

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=50048
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 16035/2 exit code: 0

	 Hostname: testds-n2h9z

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=40414
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 16035/3 exit code: 0

	 Hostname: testds-n2h9z

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=43850
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 16035/4 exit code: 0

	 Hostname: testds-nw5sj

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=48103
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 16035/5 exit code: 0

	 Hostname: testds-n2h9z

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=49876
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 16035/6 exit code: 0

	 Hostname: testds-n2h9z

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=55372
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 16035/7 exit code: 0

	 Hostname: testds-nw5sj

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=42358
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 16035/9 exit code: 0

	 Hostname: testds-n2h9z

	 Request Information:
	 	client_address=<IP_ADDRESS>
	 	client_port=35092
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 16035/10 exit code: 0
	 failed: :16035/8=71

Stderr:
 	 command terminated with exit code 42

/home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-K8s/1.13-gopath/src/github.com/cilium/cilium/test/k8sT/Services.go:736

Standard Output
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Cilium pods: [cilium-9kcbb cilium-drwpd]
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:
Pod   Ingress   Egress
Cilium agent 'cilium-9kcbb': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 43 Failed 0
Cilium agent 'cilium-drwpd': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 25 Failed 0

BeforeAll failures usually suggest that something failed to clean up after a previous test :thinking:

Yep, but that's not the case here. I just wanted to highlight that other failures of the same test found in the CI dashboard are actually caused by BeforeAll failures so likely a different root case.


Add Alert API v2

Client has been rewritten and is now in version 3.00 (still release candidate). Client version 3.00 has now full Alert API implementation.


Inconsistent error styles between Get An Account and Playlist Creation Error Lists

These are quite similar, but use different classes .errorExplanation (notifications.scss) and .error_explanation (forms.scss)

I can take a look at the html on #1087 since every form needs to be looked at there.


update link to oc compliance plugin

The old link was pointing to a fork which was 192 commits behind the original repo.

Adding necessary labels since this is fixing an incorrect reference in documentation.


Updates bnc-notify version and adds support for GridPlus Lattice

Backgroud:
The Lattice is GridPlus' next generation hardware wallet. It is an always-online
device with physically separated compute environments which provide unmatched security.
For more information, see https://gridplus.io/lattice
About this PR
This PR adds the Lattice as a wallet option for bnc-notify. It also bumps the version of bnc-notify to the first version that includes Lattice support.
Note that a (nearly) identical integration was added to Curve. That pull request has a bunch of photos documenting what it is like to connect to an app.

Didn't realize this had diverged so much. Will close and replace with a fastforwarded branch.


Update pre-commit.yaml to use pre-commit/action

@sbidari Does this solve your issue with pre-commit?


Merging master into live

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/convert-model-winmltools.md
:white_check_mark:Succeeded
View

docs/get-onnx-model.md
:white_check_mark:Succeeded
View

docs/get-started-desktop.md
:white_check_mark:Succeeded
View

docs/get-started-uwp.md
:white_check_mark:Succeeded
View

docs/index.md
:white_check_mark:Succeeded
View

docs/integrate-model.md
:white_check_mark:Succeeded
View

docs/mlgen.md
:white_check_mark:Succeeded
View

docs/performance-memory.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


#141844943 Pending Backend Tests

What does this PR do?
Adds to the backend tests and increases coverage
What are the relevant pivotal tracker stories?
#141844943

Codecov Report

Merging #16 into develop will increase coverage by 11.37%.
The diff coverage is 77.77%.

@@             Coverage Diff             @@
##           develop     #16       +/-   ##
===========================================
+ Coverage    83.03%   94.4%   +11.37%
===========================================
  Files           17      17
  Lines          330     322        -8
  Branches        59      57        -2
===========================================
+ Hits           274     304       +30
+ Misses          56      18       -38

Impacted Files
Coverage Δ

server/middleware/Authentication.js
100% <ø> (+36.66%)
:arrow_up:

server/controllers/RoleController.js
95.12% <0%> (+2.26%)
:arrow_up:

server/controllers/DocumentController.js
93.84% <100%> (+29.91%)
:arrow_up:

server/controllers/UserController.js
87.5% <50%> (+9.09%)
:arrow_up:

Continue to review full report at Codecov.

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


Fontconfig error: Cannot load default config file

I don't really know how i got this error for some reason. It doesn't showed up before. The only thing i did was updating my node modules(without changing the version). I'm using the latest version. Anyways heres the code that i use:
const captchacode = randomBytes(32).toString("hex").substr(0, 6);
const { CaptchaGenerator } = require('captcha-canvas');
const captcha = new CaptchaGenerator()
.setDimension(150, 450)
.setCaptcha({text: captchacode, size: 60, color: message.guild.me.displayHexColor})
.setDecoy({opacity: 0.5})
.setTrace({color: message.guild.me.displayHexColor});
const buffer = captcha.generateSync();

And the captcha image looks like this

The issue here is canvas module. And maybe a problem with your computer. You can see an issue on this topic here.
You can also try to use solutions mention here

Hmm it doesn't really help much... I tried to reinstall it by using npm install --build-from-source canvas but it just keep failing. If i try to use npm rebuild nothing changes. Also updating the node-gyp but still nothing changed

@Veinify this seems to be a super late reply, but maybe you already solved it. I solved it by typing the command:
apt-get install fontconfig
Node-Canvas requires this package to do text writing. With installing that package the config file is automatically generated unter /etc/fonts and everything works after a restart.
Hope you have a great day,
David


Add a target for pikkr

https://github.com/pikkr/pikkr

What do we do about the Travis build? Pikkr requires AVX instructions which Travis does not expose.

If you want, feel free to add the bugs you found with this fuzz target to the trophy case https://github.com/rust-fuzz/trophy-case

Can you give it quick rebase? https://github.com/pikkr/pikkr/pull/65 has landed which allows AVX-less builds

Rebased. I kept the RUSTFLAGS bit so that on an AVX2 capable machine I can run it with the feature enabled.

Awesome, thanks!
bors r+


Cannot print a detail chart

If I want to print a detail chart, I get empty axis. The bars aren't on the screen.
Similiar problem is a print of the detail chart in full screen. Then I get the bars outside the axis.

Fixed. Thanks for the report.


DBUS IPC architecture[Do not merge]

Hi @Alexays , this PR is the try to make/organize first base service-client architecture among Waybar modules.
There are new base classes  - DBusService + DBusClient.  These classes are developed base on the DBus concept where service is a singleton.
Cava and Clock modules are working now under the new architecture.
Communication via DBus is organized through asynchronous calls(including making the DBus path registration)
Waybar introspection for DBus is presented in IDBUS interfaces. Necessary services are constructed by the DBusService using this introspection.
So.. once Waybar i starting Cava and Clock are registering their services on DBus. All next raised Waybar instances are trying to register DBus names but due to they are already busy by the current instance, new services are not working.
In the same time all clients are alive and can send necessary requests.
For example once Waybar started even user can ask DBus to provide result for Clock and Cava now

Even now concept is - one service <-> many clients such architecture doesn't reduce resource consumption for the heavy modules like cava under high load (but the difference is really is not significant).
In the same time such functionality exposes Waybar API for external modules using DBus. Even user can check what exact result is per services/module

That doesn't seem like a good idea overall. DBus communication will negate any possible performance benefits from the singletons and increase IO. Like some people say, DBus makes everything worse.
Have you considered just splitting the module presentation and logic and storing module backends in a global map bar id + module name + module id -> weak_ptr(module backend)? I had that idea for a while, but I don't have time to work on it cry

This is exactly what happened after development was finish. In the end I realized DBus layer doesn't bring some significant improvement. Moreover there is some not significant resource penalty
However ... when the system is not under the pressure work - new architecture even works a little efficient

It consumes less CPU...
But unfortunately under the loading... consuming CPU changes to the opposite

@alebastr  thank you a lot for you reviewing and opinion. Actually I had doubts about publishing this PR... due to I don't see significant benefits.... And I'm still thinking of .... is it really useful to split modules functionalities on the back and front....


Add Eclipse configuration files

Motivation:
There are contributors who use Eclipse as their primary IDE.
Modifications:

Add code formatter settings
Add code cleanup settings
Add save action settings (as a PNG image)

/cc @krisjey

Current coverage is 64.71% (diff: 100%)

Merging #302 into master will increase coverage by 0.07%

@@             master       #302   diff @@
==========================================
  Files           307        307
  Lines         12112      12112
  Methods           0          0
  Messages          0          0
  Branches       1781       1781
==========================================
+ Hits           7829       7838     +9
+ Misses         3448       3431    -17
- Partials        835        843     +8

Powered by Codecov. Last update cff9115...51372aa

@trustin Thank you!!

LGTM!


Fix featured card border

@fuhton The border color has been corrected and the variable removed.

@RachelRVasquez Looks like we didn't even remove the variable we set?

@fuhton Try now. Did another push.


Allow Users to Set Additional Guzzle Options

This PR will summarize the $config-based solution I'm thinking of for issue #2155, where we need to pass the proxy settings to the default HTTP client (i.e., the Guzzle client) because our server code doesn't have direct control of the Google\Client class (i.e., we can't create a custom HTTP client with the proper proxy settings and hand it over to Google\Client in our use case), and we can only interact with this client class via $config settings.

Just signed CLA, please relaunch the CLA scan again, thanks!

@googlebot I signed it!

There is no need for this as an option, when you can set the client to a custom Guzzle Client at any time using Google\Client::setHttpClient:
$client = new Google\Client();
$client->setHttpClient(new GuzzleHttp\Client($myGuzzleOptions));

I've seen this workaround somewhere else. However, this does not help our use case: our organization use the laravel-analytics package to query the analytics data, and the package does not expose the $client object to the package users. Consequently, we have no control or direct way of accessing the $client and providing a customized GuzzleClient to it. That's why we'd want a more direct way of passing Guzzle options when the HTTP client is created.

I don't understand... Passing the options to this class (what you suggest), or creating a NEW client and passing the new client to this class (what i suggest and what is currently supported) is functionally identical.

Yes, functionality-wise, the two options are identical. The problem is that there are legit use cases where the consumer has access to only one of the two options (i.e., via an option setting).
Let's consider an example -- say, there is a popular 3rd party package, which uses the Google API Client with the below implementation:
use Google\Client as GoogleClient;

namespace ThirdPartyPackage;

class ThirPartyClient
{
    protected $client;

    public function __construct(array $config)
    {
        $this->client = new GoogleClient($config['client_config_options']);
    }

    // ... and $client is never publicly exposed
}

And in our application code, we will create the ThirdPartyClient in our controllers. However, since $client is protected and hence not accessible, our application is not able to use the setHttpClient API from the $client object:
use ThirdPartyPackage\ThirdPartClient;

namespace App

class Controller
{
    protected $service;

    public function __construct()
    {
        $config = config('thirdPartyConfig');
        $this->service = new ThirdPartClient($config);

        // error: $client is a protected attribute, and it can't be accessed
        $this->service->client->setHttpClient(new GuzzleHttp\Client($config['client_config_options']));
    }
}

Our best bet for this use case is to let the default HTTP client be created with the options passed down in the dependency cascade without altering all the classes/packages to expose the Google\Client object along the way.


The requested module 'npm:@asteasolutions/zod-to-openapi' does not provide an export named 'OpenAPIGeneratorV3'

I thins OpenAPIGeneratorV3 in README is not correct.
Maybe OpenApiGeneratorV3?

Yes thank you. This has also been mentioned in #148. Fixed it for v5.2.0


Sleep longer to avoid exhausting api quota

/cc @uhoh-itsmaciek

+1
For context, calls to postgres-api.heroku.com must make a call as the calling user to authenticate (because addons don't really have a better auth mechanism). For users polling long-running backups, this can have a significant impact on their API usage vis-à-vis rate limits. We probably need to come up with a better authentication mechanism in general, but this should be a reasonable triage.

We probably need to come up with a better authentication mechanism in general

:+1:. If you have any ideas, I'd love to chat about this in the next couple of weeks when I'm in town. Next quarter we're likely working on a new integration and I'd love to incorporate auth changes into it if it makes sense.


Peek definition

[ ] Add a setting
[ ] Should it show metadata for external symbols?

My answer is yes for all questions. How do you solve the 3rd issue?

I' not sure the third one should be implemented. The nice thing about the current impl is that it opens instantly, compared to 2+ seconds for ordinar file opening. I'm afraid that if we make it a full fledged buffer, it will become equally slow.

Ok, let's finish the first two items. The last one should only be done if file opening is fast enough.

I'm not sure I'm ready to port Go to metadata code, it's tightly coupled with UI in GoToDefinition.fs. I'd rather leave it to implement in the future.

Fair enough.
The new Peek API isn't available on VS 2013. I've got this error when invoking Alt + F12 on VS 2013.

System.ComponentModel.Composition.CompositionException: The composition produced a single composition error, with 2 root causes. The root causes are provided below. Review the CompositionException.Errors property for more detailed information.

1) The export 'Microsoft.VisualStudio.Editor.Implementation.PeekResultFactory (ContractName="Microsoft.VisualStudio.Language.Intellisense.IPeekResultFactory")' is not assignable to type 'Microsoft.VisualStudio.Language.Intellisense.IPeekResultFactory'.

Resulting in: Cannot set import 'FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider..ctor (Parameter="peekResultFactory", ContractName="Microsoft.VisualStudio.Language.Intellisense.IPeekResultFactory")' on part 'FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider'.
Element: FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider..ctor (Parameter="peekResultFactory", ContractName="Microsoft.VisualStudio.Language.Intellisense.IPeekResultFactory") -->  FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider

Resulting in: Cannot get export 'FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider (ContractName="Microsoft.VisualStudio.Language.Intellisense.IPeekableItemSourceProvider")' from part 'FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider'.
Element: FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider (ContractName="Microsoft.VisualStudio.Language.Intellisense.IPeekableItemSourceProvider") -->  FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider

2) The export 'Microsoft.VisualStudio.Text.Implementation.TextDocumentFactoryService (ContractName="Microsoft.VisualStudio.Text.ITextDocumentFactoryService")' is not assignable to type 'Microsoft.VisualStudio.Text.ITextDocumentFactoryService'.

Resulting in: Cannot set import 'FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider..ctor (Parameter="textDocumentFactoryService", ContractName="Microsoft.VisualStudio.Text.ITextDocumentFactoryService")' on part 'FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider'.
Element: FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider..ctor (Parameter="textDocumentFactoryService", ContractName="Microsoft.VisualStudio.Text.ITextDocumentFactoryService") -->  FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider

Resulting in: Cannot get export 'FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider (ContractName="Microsoft.VisualStudio.Language.Intellisense.IPeekableItemSourceProvider")' from part 'FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider'.
Element: FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider (ContractName="Microsoft.VisualStudio.Language.Intellisense.IPeekableItemSourceProvider") -->  FSharpVSPowerTools.Logic.VS2015.PeekableItemSourceProvider

   at System.ComponentModel.Composition.Hosting.CompositionServices.GetExportedValueFromComposedPart(ImportEngine engine, ComposablePart part, ExportDefinition definition)
   at System.ComponentModel.Composition.Hosting.CatalogExportProvider.GetExportedValue(CatalogPart part, ExportDefinition export, Boolean isSharedPart)
   at System.ComponentModel.Composition.Hosting.CatalogExportProvider.CatalogExport.GetExportedValueCore()
   at System.ComponentModel.Composition.Primitives.Export.get_Value()
   at System.ComponentModel.Composition.ExportServices.GetCastedExportedValue[T](Export export)
   at System.ComponentModel.Composition.ExportServices.<>c__DisplayClass42.<CreateStronglyTypedLazyOfTM>b__1()
   at System.Lazy1.CreateValue()
   at System.Lazy1.LazyInitValue()
   at System.Lazy1.get_Value()
   at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.InvokeMatchingFactories[TExtensionInstance,TExtensionFactory,TMetadataView](IEnumerable1 lazyFactories, Func2 getter, IContentType dataContentType, Object errorSource)

Could we only enable the feature for VS2015+? It's even better to show it clearly in the setting e.g. Peek Definition (VS2015+).

I know, that is why I put it into Logic.VS2015 project. Maybe just hide or make "disabled" (gray and non interactive) the setting in VS2013?

We should make sure that Alt+F12 on VS2013 should do nothing. A clear label is OK. Of course, graying out the setting on VS 2013 is better :-).

Huh. I try to fit this trick https://github.com/fsprojects/VisualFSharpPowerTools/blob/master/src/FSharpVSPowerTools.Logic/NavigateToItem.fs#L277-L295, but the case is not the same because there's no IPeekableItemSourceProvider in VS2013 at all, so we cannot add a fake implementation in Logic, then select right one at runtime. Any ideas?

Try this first https://github.com/fsprojects/VisualFSharpPowerTools/blob/master/src/FSharpVSPowerTools/Commands/UnionPatternMatchCaseGeneratorSmartTaggerProvider.cs#L55-L57. It might be enough.

Done both disabling the setting and the trick with returning null (your last comment).
In VS 2015 everything works.

About the bug, it seems only Highlight refs stops working after single Peek Definitions invoked:

I think I understand why the bug: peek definition seems to reuse already open buffers and, when I close peek def window, it's Dispose is called, which disposes all our timers => most features stop working.
So, it seems we should use ITextView.Properties.GetOrCreateSingletonProperty instead of ITextBuffer.GetOrCreateSingletonProperty. Will check shortly.

No, it has not helped :(

Oh, no https://github.com/dotnet/roslyn/blob/a4e375b95953e471660e9686a46893c97db70b0e/src/EditorFeatures/Core/Shared/Extensions/ITextViewExtensions.PerSubjectBufferProperty.cs

It will be a long story.

The link looks scary :(
It throws errors on VS2013; we need another way.

Have fixed the bug with stopping all the features working after opening-closing a Peek Def view.

I have no idea how to get rid of the exception in VS 2013. I suggest:

stop supporting it
create different VSIXs for 2013 and 2015+

Let's merge this after addressing the last two comments. I'll try to disable the feature for VS2013 after merging the PR.

I think we should improve it significantly:

To fix the issue with OpenDocumentTracker it should keep number of views opened for concrete buffer and countdown it when a view is closing. When the counter is zero, remove it from opened docs map.
The root cause of the fact that no features work inside Peek Def view is that DTE returns main document as active over here https://github.com/fsprojects/VisualFSharpPowerTools/blob/master/src/FSharpVSPowerTools.Logic/VSUtils.fs#L252, then this case does not match if Peek view contains document different to the one opened in the main view https://github.com/fsprojects/VisualFSharpPowerTools/blob/master/src/FSharpVSPowerTools.Logic/VSUtils.fs#L262

Yes, we should eventually get rid of ActiveDocument thing. It has never been working well.


Show better error messages

When there is a SQL validation error, the error is shown on the screen. However, we always get a nested Java and Python exception, which might lead to confusion.
The blazingSQL project created their own SQL exception in Java for this - we might also get along with just catching and parsing the Java exception in python and printing out a piece of more useful information to the user in the Context.sql function.

I ran into this myself.  Here was a small/simple example
import dask
import dask_sql
context = dask_sql.Context()
df = dask.datasets.timeseries()
context.register_dask_table(df, "timeseries")
context.sql("SELECT * from timeseries where name=Tim")

As a user, nothing in the calcite stack trace means anything to me.  The error message itself is useful though.  I wouldn't mind chopping off everything in the cython/java side and just raising the exception without a meaningful traceback.  There is probably some value to devs in the traceback though I suppose.


uncapping the FPS is impossible

Describe the bug
You use to be able to uncap the fps by disabling vsync, but now no matter what you do, it does not work, even forcing vsync to off doesn't work
To Reproduce
Steps to reproduce the behavior:

Go to 'xenia settings'
Click on 'vsync'
Scroll down to 'off'
See error

Expected behavior
The Frame Rate will remain at 30 fps.
Screenshots

Additional context
no matter the game the feature that worked previously, doesn't work anymore.
Log File
xenia.log

Did you turn off Vsync in game profile or only in the default Xenia profile?

Did you turn off Vsync in game profile or only in the default Xenia profile?

in xenia log file framerate limit is 60 fps so xenia use 30 fps if needed more it needs 120 fps for 60 fps in xenia and so on
but i guess he forget to check game config file in xenia manager

Closing this issue due to lack of response.


group-exports: option for export at definition

The option enforces exports statements to happen at definition:
Pass:
export default function foo() {}
export function foo(){}
export const foo = 1;

Fail:
function foo() {}
export {
  foo,
}

The default option for group-exports will be called always, and the added option will be never.

This sounds like it might have a ton of unintended consequences.
group-exports is generally about the position in the file, not the form used to export. There’s all sorts of reasons why you might not be able to use the declaration/inline form, and why the curly-braced form is the only way you can export something. I worry such an option would be harmful.

What are some examples where curly based exports are necessary? I always use inline exports at my work and have not met a problem.
I prefer the inline form because I can tell whether the function is exported right at the definition, instead of having to find out whether it is exported elsewhere.
As a side note the inline syntax is the only way to export things in Golang.

I thought of one case where I use curly braced exports: reexports.

JS isn’t go, so im not sure that’s relevant; it’s a counterproductive goal to match coding styles across languages.
If the value being exported isn’t a declaration. Maybe it’s the return value of a function, or maybe it’s imported from somewhere else.


Sharing and converting QR code to Image

Hello, I read the feature of this awesome library that says:
Export to image data to save to file or use in memory
but in the example doesn't define how to do so, can you help me please?

I also wanted to Save the QR Image but with some extra Widget, so here is what I followed:

Wraped the Required widget with Screenshot Widget.

   Screenshot(
      controller: screenshotController,
      child: Container(
        padding: const EdgeInsets.all(10.0),
        child: ...
      ),
    );

Used ScreenshotController to take a screenshot and handed permission with Permission Handler.

    ScreenshotController screenshotController = ScreenshotController();

    screenshotController.capture().then((File imageFile) async {
      try {
        bool isGranted = await Permission.storage.isGranted;
        if (isGranted) {
          _saveToGallery(imageFile);
        } else {
          // Ask Permission
          PermissionStatus status = await Permission.storage.request();
          switch (status) {
            case PermissionStatus.undetermined:
              break;
            case PermissionStatus.granted:
              _saveToGallery(imageFile);
              break;
            case PermissionStatus.denied:
              debugPrint("Storage permission required to Save Image");
              break;
            case PermissionStatus.permanentlyDenied:
            case PermissionStatus.restricted:
              debugPrint("Storage permission required to Save Image, allow permissions in Settings");
              break;
          }
        }
      } catch (exp) {
        debugPrint("Storage Permission Error ${exp.toString()}");
      }
    }).catchError((err) {
      debugPrint("Image catchError ${err.toString()}");
    });

And finally saved the image using Image Gallery Saver

Future<void> _saveToGallery(File imageFile) async {
    try {
      final result =
          await ImageGallerySaver.saveImage(imageFile.readAsBytesSync());
      debugPrint("Image Stored Successfully !!");
    } on Exception catch (exp) {
      debugPrint("Image Exception ${exp.toString()}");
    }
  }

This has been answered many times in the closed issues. You can do a search for it and you'll find multiple examples.
You can also look here: https://github.com/lukef/qr.flutter/blob/78e3bbe19f24a34fdbbb89e1e7b7f698f561ad28/test/image_test.dart.
You can also ask the question on StackOverflow so that the Issue Tracker isn't full of redundant (non-issue) questions.


Removing Hipchat

Hipchat was shutdown in 2018
https://techcrunch.com/2018/07/26/atlassians-hipchat-and-stride-to-be-discontinued-with-slack-buying-up-the-ip/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAAHlVfvetlEJ2_NPscmD_Tw2JTdCe133GD4Opt3LKibv7Zub0qt1g3c963Srjs_Zgw5varmbX_QaiZ8q65daJBcnRZsdiHvVNIdJohn04Nuu1efXDUstiALbDrQ5rxeUpMK2VoTfaj2eMQDw3wsc9BGW8EM-lCTmL_U_Dxosp5nt3

This is generated by code on the original schemas, so to remove this we need to remove it from shared (Every time I run the program this will regenerate as place holders)


AWS deprovision: Plumb HostedZoneRole for shared VPC

The shared VPC flow added the need for the installer to use a HostedZoneRole to manage certain DNS records. This is provided at installation time via the install-config, and is included in the metadata.json produced by the installer when provisioning completes.
The uninstall process requires this HostedZoneRole during deprovisioning to perform the corresponding cleanup -- without it, those records are leaked. So we need to plumb that datum through from the metadata.json to the uninstall process.
To make this more general-purpose for adoption and disaster recovery, and for retrofitting existing clusters that were created before this commit, we also attempt to pull the HostedZoneRole out of the install-config if it is unset.
NOTE: We will refuse to proceed with deprovision if this field is not set. Once this change lands, we should audit existing clusters to make sure they all get retrofitted; and manually retrofit any others (with the empty string).
HIVE-2297

/assign @abutcher

NTR: This mostly follows the precedent established by #1997 / #2020.

Oh, btw, I do intend to add UT for this in a fup. For right now it's urgent that we get this landed and tested live.

D'oh, forgot to git add new files, rookie mistake :eyeroll:

e2e-pool: quota flake.
verify: fixed by latest push.
We're going to merge this manually assuming lgtm, as we're reasonably confident in the fix and it'll take some time to resolve the quota issue.

/lgtm

e2e logged:
time="2023-08-29T20:08:07.097Z" level=info msg="Found AWS HostedZoneRole in ClusterMetadata" hostedZoneRole=


4.10 ipynb + data + submission.csv

too many commits here. please understand this is the exact reason you should check out a new feature branch for different notebooks. Can't see why you've added Numerical Stability and Initialization notebook again. It is already there. Also no need to add a submission .csv.
Reopen this when the above corrections are made. @rsinghal757 please look into this.


Cosigned - Webhook are not trigger even if the namespace is correctly labeled

Version
App Version 1.8.0
Chart Version 0.1.23
Description
I have tried to deploy the last version of the cosigned chart and the pod are up&running but i see in the logs:
{"level":"info","ts":"2022-11-09T16:56:43.425Z","logger":"cosigned.DefaultingWebhook","caller":"controller/controller.go:550","msg":"Reconcile succeeded","commit":"9ef6b20","knative.dev/traceid":"8806c857-4187-45ae-9dac-c02459695500","knative.dev/key":"argocd/webhook-certs","duration":0.090687279}
{"level":"error","ts":"2022-11-09T16:56:43.432Z","logger":"cosigned.ValidationWebhook","caller":"controller/controller.go:566","msg":"Reconcile error","commit":"9ef6b20","knative.dev/traceid":"e2d47e24-3bdf-47e1-ac61-60bba46e58e1","knative.dev/key":"cosigned.sigstore.vdf","duration":0.091272538,"error":"failed to update webhook: Operation cannot be fulfilled on validatingwebhookconfigurations.admissionregistration.k8s.io \"cosigned.sigstore.vdf\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"knative.dev/pkg/controller.(*Impl).handleErr\n\tknative.dev/pkg@v0.0.0-20220325200448-1f7514acd0c2/controller/controller.go:566\nknative.dev/pkg/controller.(*Impl).processNextWorkItem\n\tknative.dev/pkg@v0.0.0-20220325200448-1f7514acd0c2/controller/controller.go:543\nknative.dev/pkg/controller.(*Impl).RunContext.func3\n\tknative.dev/pkg@v0.0.0-20220325200448-1f7514acd0c2/controller/controller.go:491"}
{"level":"error","ts":"2022-11-09T16:56:43.509Z","logger":"cosigned.DefaultingWebhook","caller":"controller/controller.go:566","msg":"Reconcile error","commit":"9ef6b20","knative.dev/traceid":"b8f7599f-00f8-4103-bf0f-08eb313f6d19","knative.dev/key":"cosigned.sigstore.vdf","duration":0.168674564,"error":"failed to update webhook: Operation cannot be fulfilled on mutatingwebhookconfigurations.admissionregistration.k8s.io \"cosigned.sigstore.vdf\": the object has been modified; please apply your changes to the latest version and try again","stacktrace":"knative.dev/pkg/controller.(*Impl).handleErr\n\tknative.dev/pkg@v0.0.0-20220325200448-1f7514acd0c2/controller/controller.go:566\nknative.dev/pkg/controller.(*Impl).processNextWorkItem\n\tknative.dev/pkg@v0.0.0-20220325200448-1f7514acd0c2/controller/controller.go:543\nknative.dev/pkg/controller.(*Impl).RunContext.func3\n\tknative.dev/pkg@v0.0.0-20220325200448-1f7514acd0c2/controller/controller.go:491"}
{"level":"info","ts":"2022-11-09T16:56:43.517Z","logger":"cosigned.ValidationWebhook","caller":"validation/reconcile_config.go:173","msg":"Updating webhook","commit":"9ef6b20","knative.dev/traceid":"bbad1e4a-a0d8-4102-abfa-2df856fe1a16","knative.dev/key":"cosigned.sigstore.vdf"}
{"level":"info","ts":"2022-11-09T16:56:43.611Z","logger":"cosigned.DefaultingWebhook","caller":"defaulting/defaulting.go:253","msg":"Updating webhook","commit":"9ef6b20","knative.dev/traceid":"ff81aac0-f467-4175-b483-52ea2edc8ed3","knative.dev/key":"cosigned.sigstore.vdf"}
{"level":"info","ts":"2022-11-09T16:56:43.612Z","logger":"cosigned.ValidationWebhook","caller":"controller/controller.go:550","msg":"Reconcile succeeded","commit":"9ef6b20","knative.dev/traceid":"bbad1e4a-a0d8-4102-abfa-2df856fe1a16","knative.dev/key":"cosigned.sigstore.vdf","duration":0.179883746}
{"level":"info","ts":"2022-11-09T16:56:43.713Z","logger":"cosigned.ValidationWebhook","caller":"validation/reconcile_config.go:173","msg":"Updating webhook","commit":"9ef6b20","knative.dev/traceid":"18a641ae-b226-4747-b385-126683c79f89","knative.dev/key":"cosigned.sigstore.vdf"}
{"level":"info","ts":"2022-11-09T16:56:43.713Z","logger":"cosigned.DefaultingWebhook","caller":"controller/controller.go:550","msg":"Reconcile succeeded","commit":"9ef6b20","knative.dev/traceid":"ff81aac0-f467-4175-b483-52ea2edc8ed3","knative.dev/key":"cosigned.sigstore.vdf","duration":0.204078579}
{"level":"info","ts":"2022-11-09T16:56:43.809Z","logger":"cosigned.DefaultingWebhook","caller":"defaulting/defaulting.go:253","msg":"Updating webhook","commit":"9ef6b20","knative.dev/traceid":"f99054cc-1f4b-4564-97e7-1adb63cdcb4e","knative.dev/key":"cosigned.sigstore.vdf"}
{"level":"info","ts":"2022-11-09T16:56:43.810Z","logger":"cosigned.ValidationWebhook","caller":"controller/controller.go:550","msg":"Reconcile succeeded","commit":"9ef6b20","knative.dev/traceid":"18a641ae-b226-4747-b385-126683c79f89","knative.dev/key":"cosigned.sigstore.vdf","duration":0.198162737}
{"level":"info","ts":"2022-11-09T16:56:43.817Z","logger":"cosigned.DefaultingWebhook","caller":"controller/controller.go:550","msg":"Reconcile succeeded","commit":"9ef6b20","knative.dev/traceid":"f99054cc-1f4b-4564-97e7-1adb63cdcb4e","knative.dev/key":"cosigned.sigstore.vdf","duration":0.104080899}

I also tried to create a namespace and label it and install it the nginx chart:
kubectl label namespace test cosigned.sigstore.vdf/include="true"

helm install my-ingress-nginx ingress-nginx/ingress-nginx --version 4.3.0 -n test

The chart is installed and the webhooks are not triggered.
Below the values.yaml used to install cosigned chart:
cosign:
  secretKeyRef:
    name: "cosign-kms-pub"
    #name: "mysecret"
  # add the values in base64 encoded
  cosignPub: ""
  webhookName: "cosigned.sigstore.vdf"

policywebhook:
  image:
    repository: myregistry/projectsigstore/policy-webhook
    #version: sha256:5eee36d3e0a7b2ebd92da9cff183e77dd3e9e9e33d94cbe9bc171d084135158a
    version: 1.0.0
    pullPolicy: IfNotPresent
  env: {}
  extraArgs: {}
  resources:
    limits:
      cpu: 100m
      memory: 256Mi
    requests:
      cpu: 100m
      memory: 128Mi
  serviceAccount:
    annotations: {}
  securityContext:
    enabled: false
    runAsUser: 65532
  podSecurityContext:
    enabled: true
    allowPrivilegeEscalation: false
    readOnlyRootFilesystem: true
    runAsNonRoot: true
    capabilities:
      drop:
        - all
  service:
    annotations: {}
    type: ClusterIP
    port: 443
  webhookNames:
    defaulting: "defaulting.clusterimagepolicy.sigstore.vdf"
    validating: "validating.clusterimagepolicy.sigstore.vdf"

webhook:
  name: webhook
  image:
    repository: myregistry/projectsigstore/cosigned
    #version: sha256:784518ff3ee755ce42e174e61036094af771c43bdc76b65a8f0e52481ed450ac
    version: 1.0.0
    pullPolicy: IfNotPresent
  env: {}
  extraArgs: {}
  resources:
    limits:
      cpu: 100m
      memory: 256Mi
    requests:
      cpu: 100m
      memory: 128Mi
  securityContext:
    enabled: false
    runAsUser: 65532
  podSecurityContext:
    enabled: true
    allowPrivilegeEscalation: false
    readOnlyRootFilesystem: true
    runAsUser: 1000
    capabilities:
      drop:
        - all
  serviceAccount:
    annotations: {}
  service:
    annotations: {}
    type: ClusterIP
    port: 443
    # For nodeport, specify the following:
    #   type: NodePort
    #   nodePort: <port-number>

## common node selector for all the pods
commonNodeSelector: {}
#  key1: value1
#  key2: value2

## common tolerations for all the pods
commonTolerations: []
# - key: "key"
#   operator: "Equal"
#   value: "value"
#   effect: "NoSchedule"

## serviceMonitor makes cosigned metrics discoverable to prometheus
serviceMonitor:
  enabled: false

Can you (or someone) help to understand which is the issue?
Thanks a lot!

@quadrinho Please, could you move this issue to sigstore/policy-controller ? As detailed in the Chart, that repository is more appropriated to report any issues with this helm chart https://github.com/sigstore/helm-charts/blob/main/charts/policy-controller/Chart.yaml#L6.

Hello @hectorj2f ,
I have opened this one:
https://github.com/sigstore/policy-controller/issues/369
Can you help me on that issue?