Recommended envs for compiling 19_large_depthwise_conv2d_torch_extension?

Hi! Congrats for the wonderful work. I'm wondering what's the Recommended envs for compiling 19_large_depthwise_conv2d_torch_extension?
My Envs are as follows:
python 3.7
CUDA 10.2
gcc 5.4.0
torch 1.11.0
But when i implement "./setup.py install --user", I got errors like:
lib/python3.7/site-packages/torch/include/torch/csrc/api/include/torch/nn/cloneable.h:57:59: error: invalid static_cast from type ‘const torch::OrderedDict<std::basic_tring<char>, at::Tensor>’ to type ‘torch::OrderedDict<std::basic_string<char>, at::Tensor>&’
...
/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1756, in _run_ninja_build                                                                          raise RuntimeError(message) from e
RuntimeError: Error compiling objects for extension

I found it will works under torch.1.8.1. Thank you anyway.


Add support for compose-cli

https://github.com/docker/compose-cli
This is not docker-compose netiher, docker-compose v2, this is a different cli tool to run containers on cloud providers and k8s, using a docker-compose like file.
Expected Behaviour
arkade get compose-cli installs it.
Current Behaviour
Not implemented.
Are you a GitHub Sponsor (Yes/No?)
Check at https://github.com/sponsors/alexellis

[ ] Yes
[X] No

Possible Solution
Add compose-cli to pkg/get/tools.go.
Context
Since v2 it has been moved to a separate repository, under heavy development, with support for Kubernetes! (Yaay!)
Your Environment

What Kubernetes distribution are you using?

Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.2", GitCommit:"8b5a19147530eaac9476b0ab82980b4088bbc1b2", GitTreeState:"clean", BuildDate:"2021-09-15T21:38:50Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.2+k3s2", GitCommit:"3f5774b41eb475eb10c93bb0ce58459a6f777c5f", GitTreeState:"clean", BuildDate:"2021-10-05T20:29:33Z", GoVersion:"go1.16.8", Compiler:"gc", Platform:"linux/amd64"}

Operating System and version (e.g. Linux, Windows, MacOS):

Linux pop-os 5.13.0-7620-generic #20~1634827117~21.04~874b071-Ubuntu SMP Fri Oct 29 15:06:55 UTC  x86_64 x86_64 x86_64 GNU/Linux

What arkade version is this?

Version: 0.8.3-40-g4bf1460
Git Commit: 4bf14606fcb64e19b050b277ba36226df6c632d6

/add label: enhancement

/edit title: Feature request: Add support for compose-cli


remove JupyterWgpuCanvas from imports, allow minimal install to work

tested and work with just glfw, docs also build


add custom native options to move prover backend #246_136

Motivation
This PR adds one more field to BoogieOptions so that users of move prover are able to supply Boogie implementations of their own custom Move native functions.
Have you read the Contributing Guidelines on pull requests?
Yes

/canary

:sunny: Canary successful

/land


CocoaPods latest versions

RKNotificationHub 2.0.2, 2.0.3 and 2.0.4 podspecs are missing on CocoaPods/Specs repo, therefore latest version that gets downloaded is 2.0.1

looking into this now. sorry for the delay

fixed


<EMAIL_ADDRESS>update from 1.91.1

[x] I have read the Contributing Guide.

Already updated automatically by bot.


Add pa11y-ci accessibility checks against PR preview env

Add pa11y-ci  accessibility checks against PR preview env

Wait for PR preview env to load
Run basic tests against env

Original ticket on the nextjs template:
https://github.com/navapbc/template-application-nextjs/issues/347

We ended up using playwright a11y checks instead of pa11y - closing this


Project license

Can you please identify this project's license? Thank you!

I wanted to follow up on my question.  I found this: https://github.com/chrisdickinson/cssauron/blob/ae57ae70c65961457f1f7481d945ed47dfdd2f20/package.json but wanted to confirm that this is MIT licensed.  Any help is greatly appreciated!


fix: Add missing React 18 reconciler function

Context
This adds a missing detachDeletedInstance function to @remote-ui/react/reconciler, which is invoked during React's clean up phase. Prior to this change you'd get an exception / broken app when a component is removed (like the example in the unit test of toggling an image component).
I created a minimal repro case on codesandbox and this is what that looks like in action:

Other notes

That function was added to react-reconciler in PR #21039
It is only intended to be called for "Host Components" / native DOM elements, but from tracing the behavior at runtime I noticed that all createRemoteReactComponent-generated components seem to e classified as Host Components by the reconciler
This behavior only occurs when removing previously-rendered components
Full exception stack trace:

Uncaught TypeError: detachDeletedInstance is not a function
    at detachFiberAfterEffects (react-reconciler.development.js:15352:9)
    at detachFiberAfterEffects (react-reconciler.development.js:15329:5)
    at detachFiberAfterEffects (react-reconciler.development.js:15329:5)
    at commitPassiveUnmountEffectsInsideOfDeletedTree_complete (react-reconciler.development.js:16750:7)
    at commitPassiveUnmountEffectsInsideOfDeletedTree_begin (react-reconciler.development.js:16735:7)
    at commitPassiveUnmountEffects_begin (react-reconciler.development.js:16634:11)
    at commitPassiveUnmountEffects (react-reconciler.development.js:16619:3)
    at flushPassiveEffectsImpl (react-reconciler.development.js:19181:3)
    at flushPassiveEffects (react-reconciler.development.js:19127:14)
    at react-reconciler.development.js:18912:9

Released in<EMAIL_ADDRESS>


[Issue]: Email send logs are too long in Cloudwatch and Datadog

Why is this issue important?
Reducing the number of lines will ensure cleaner logs when debugging issues.
Current State

Expected State
Compress the above to a single line similar to:

Implementation Plan
use JSON.stringify()
Relevant Code Snippets
No response

Proposal: Use a library like bunyan for structured logs, which would resolve any issues related to log length as well as make all logs easier to search in Datadog.
Example commit: https://github.com/usdigitalresponse/usdr-gost/commit/d512d4a568503748d8e2b331d744da3795f55624


What should an a11y RC test look like

As we remade the RC template (phetsims/QA/issues/19) we noticed that the a11y section seems a bit sparse.  It has, in the past, been included in the general RC and simply included making sure everything reads or functions correctly, nothing interferes with the sim, and looking at the "script" to see if anything is left out.  I wanted to ask relevant parties if they feel this level of testing is sufficient for an RC test, and looking for suggestions and input for a more structured test.
See https://github.com/phetsims/QA/issues/19#issuecomment-414755616 for the new RC test template.

@KatieWoe Thanks for including us in this discussion! Before I comment further, it would be helpful for some clarification - forgive my ignorance of this - on how touch vs cursor-based interactions are tested? Is it just that on certain touch-specific devices the touch interface is tested, and on other devices a cursor-interaction is used?

In general at the moment, on devices that support touch and cursor we try to test both, but we probably focus a bit more on cursor-interaction.  On devices that only support one, we only test that one method.

I'm going to suggest a structure where the "General RC Test" category is expanded to include different specifics on different modalities - rather than having a "General" and an "A11y" category.
For example - in the first bullet of the current "General" category is "click every single button".  You can get to each button in multiple ways - moving your cursor and possibly getting a hover state change, tapping with finger (no cursor movement, no hover state), moving focus with keyboard keypresses (getting moving focus highlight, and possibly a 'hover' state), etc.
What do you think about being explicit about mouse, touch, keyboard (no screen reader), and screen reader testing (each with a collapsible section), each possibly specifying devices/browser options or requirements, and each with a bullet list of testing steps. Then at the top of the testing request, it can be specified which set of these modalities need to be completed.

The idea we had was that the developer making the request would delete whatever section is not included in the test.  So, if there is no keyboard support the QA team wouldn't even see those instructions.  This is meant to both cut down on the length of the final issue and prevent confusion as to whether something should be included or not.
I like the idea of making a list of the types of interactions to check on a device.  Once a11y testing is happening with most RC tests I think we should combine it with general (same with phet-io) but until then I think the risk of miscommunication as to what should be tested can be avoided by putting it in a section that can be simply added or taken away.
In regards to the method of testing, it sounds like you would like some type of matrix that keeps track of methods of interaction on supported platforms.

@KatieWoe
Again - forgive me for asking a really basic question...
When a tester is doing RC testing, in what contexts/platforms/etc. are they doing the 'play with sim normally' and 'try to break the sim'. Are they doing this type of testing across all device/browser/etc listed? Or are they doing this rigorously in some environments, and then doing spot checking in others?

Should we close this issue?

I think so, unless @emily-phet and @terracoda have more to add.


Reference page incorrectly citing misc reference

example:

should be

I could be wrong here, but its missing the url....

Perhaps it would be as easy as changing to \bibliographystyle{IEEEtran} instead of \bibliographystyle{unsrt}

definitely agree that the urls need to display in the bib, only problem is the giant spacing inbetween stuff. Perhaps it is because the bib is defaulting to justified text... will investigate

I see what youre saying. The standard looks like its left justified. You could do:
	\begingroup
		\raggedright
		\bibliography{references}
	\endgroup

@benjamincaldwell done in https://github.com/Erik-J-D/sydetex/pull/10

@Erik-J-D this issue will be fixed once https://github.com/Erik-J-D/sydetex/pull/10 gets merged


WIP sanity with prints

Signed-off-by: Or Shoval<EMAIL_ADDRESS>

/uncc @enp0s3 @vladikr

/test pull-kubevirt-e2e-k8s-1.21-sig-network

here it pass because its the presubmit not the periodic


p5 notebook

Hey folks,
Really cool stuff here. Just a quick post to let you know that I've recently been experimenting with similar ideas to build a notebook interface for p5.js: https://github.com/jtpio/p5-notebook
The approach is similar (using IFrames for the kernel), with slight differences:

the p5 notebook is a custom frontend built using lab components, started from the notebook example in core lab
it also uses its own (incomplete) "Jupyter Server in the browser", since the goal would be to eventually store and manage notebooks in the browser (for example using localStorage), manage kernels, and to some extent cover most of the notebook server API.
the focus is to build a very minimal notebook UI for p5.js users, kind of similar to this proof of concept but giving it a "Jupyter look": https://github.com/aparrish/nb5js-proof-of-concept. Also with the idea of having something similar to the p5 online editor but for notebooks, that runs entirely in the browser.
for now it inlines IFrames in the cell outputs to make it look like a real output. Although technically these other IFrames are copies of the real one used by the kernel. Each time a cell is executed in the main kernel, it is also executed in the other IFrames (they act as "views").
most of this is not really specific to p5 and could be extracted into separate packages, a bit like what jyve does. But for now having it all in one place makes it easier to iterate on.

Anyway I just wanted to share this so that we can try to make all of this work together at some point!

Cool, thanks for the heads-up.
We should definitely figure out how to work the concept of browser kernels,
which understand the full kernel spec, into a lab core PR... I've found it
challenging to keep the API up properly, and there's a lot it could offer.
I've also been percolating on how to get frontend language servers into
jupyterlab-lsp, as well... And having that with p5 would be helpful, no
doubt.
The iframe approach is a great jump start... But eventually i think this
kind of work will need a way to move into a worker. Even loading Pyodide,
which is still the brass ring jyve is striving for, can definitely be
taxing.
I have toyed with doing a bespoke frontend (e.g start with a text box and a
Jyve kernel, and build UI from there), but eventually the thought tends
towards features that lab just already has. I think there's a lot of space
for theme-only reduction and plugin replacement to get to more pleasing
minimalism, such that other peoples' plugins just work. Maybe the best hook
for that right now is probably "presentation mode"?
On Mon, Mar 23, 2020, 10:40 Jeremy Tuloup<EMAIL_ADDRESS>wrote:

Hey folks,
Really cool stuff here. Just a quick post to let you know that I've
recently been experimenting with similar ideas to build a notebook
interface for p5.js: https://github.com/jtpio/p5-notebook
The approach is similar (using IFrames for the kernel), with slight
differences:

the p5 notebook is a custom frontend built using lab components,
started from the notebook example in core lab
https://github.com/jupyterlab/jupyterlab/tree/master/examples/notebook
it also uses its own (incomplete) "Jupyter Server in the browser",
since the goal would be to eventually store and manage notebooks in the
browser (for example using localStorage), manage kernels, and to some
extent cover most of the notebook server API.
the focus is to build a very minimal notebook UI for p5.js users,
kind of similar to this proof of concept but giving it a "Jupyter look":
https://github.com/aparrish/nb5js-proof-of-concept. Also with the idea
of having something similar to the p5 online editor
https://editor.p5js.org/ but for notebooks, that runs entirely in
the browser.
for now it inlines IFrames in the cell outputs to make it look like
a real output. Although technically these other IFrames are copies of the
real one used by the kernel. Each time a cell is executed in the main
kernel, it is also executed in the other IFrames (they act as "views").
most of this is not really specific to p5 and could be extracted
into separate packages, a bit like what jyve does. But for now having it
all in one place makes it easier to iterate on.

Anyway I just wanted to share this so that we can try to make all of this
work together at some point!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/deathbeds/jyve/issues/45, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAALCRDSZWOPPYQJRH2MV3LRI5YEHANCNFSM4LR5PSBA
.

Also on the file system: my original goal for jyve was to support dat or
ipfs, and indeed I got a demo working in the beaker browser, back when it
supported both stacks. The nice thing about these is that they would
provide an ideal mechanism to serve both the "host" application (jyve, p5n,
etc) as well as user data... Once you hit "publish" and get that hash, you
could easily share your app/content, and with day, you could even update
it, and subscribers would be notified.
Since then, both APIs have been rounded out a lot, and we did a pretty cool
demo with jupyterlab-dat for a sort of "notecast". This also provided a
chat-per-dat, built as a bespoke notebook/servicemanager, which could be
used to share additional notebooks.
On Mon, Mar 23, 2020, 16:36 Nicholas Bollweg<EMAIL_ADDRESS>wrote:

Cool, thanks for the heads-up.
We should definitely figure out how to work the concept of browser
kernels, which understand the full kernel spec, into a lab core PR... I've
found it challenging to keep the API up properly, and there's a lot it
could offer.
I've also been percolating on how to get frontend language servers into
jupyterlab-lsp, as well... And having that with p5 would be helpful, no
doubt.
The iframe approach is a great jump start... But eventually i think this
kind of work will need a way to move into a worker. Even loading Pyodide,
which is still the brass ring jyve is striving for, can definitely be
taxing.
I have toyed with doing a bespoke frontend (e.g start with a text box and
a Jyve kernel, and build UI from there), but eventually the thought tends
towards features that lab just already has. I think there's a lot of space
for theme-only reduction and plugin replacement to get to more pleasing
minimalism, such that other peoples' plugins just work. Maybe the best hook
for that right now is probably "presentation mode"?
On Mon, Mar 23, 2020, 10:40 Jeremy Tuloup<EMAIL_ADDRESS>wrote:

Hey folks,
Really cool stuff here. Just a quick post to let you know that I've
recently been experimenting with similar ideas to build a notebook
interface for p5.js: https://github.com/jtpio/p5-notebook
The approach is similar (using IFrames for the kernel), with slight
differences:

the p5 notebook is a custom frontend built using lab components,
started from the notebook example in core lab
https://github.com/jupyterlab/jupyterlab/tree/master/examples/notebook
it also uses its own (incomplete) "Jupyter Server in the browser",
since the goal would be to eventually store and manage notebooks in the
browser (for example using localStorage), manage kernels, and to some
extent cover most of the notebook server API.
the focus is to build a very minimal notebook UI for p5.js users,
kind of similar to this proof of concept but giving it a "Jupyter look":
https://github.com/aparrish/nb5js-proof-of-concept. Also with the
idea of having something similar to the p5 online editor
https://editor.p5js.org/ but for notebooks, that runs entirely in
the browser.
for now it inlines IFrames in the cell outputs to make it look like
a real output. Although technically these other IFrames are copies of the
real one used by the kernel. Each time a cell is executed in the main
kernel, it is also executed in the other IFrames (they act as "views").
most of this is not really specific to p5 and could be extracted
into separate packages, a bit like what jyve does. But for now having it
all in one place makes it easier to iterate on.

Anyway I just wanted to share this so that we can try to make all of this
work together at some point!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/deathbeds/jyve/issues/45, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAALCRDSZWOPPYQJRH2MV3LRI5YEHANCNFSM4LR5PSBA
.

Thanks @bollwyvl for the input!

I've found it challenging to keep the API up properly

You mean the Lab API and the changes with new major releases?

The iframe approach is a great jump start... But eventually i think this
kind of work will need a way to move into a worker. Even loading Pyodide,
which is still the brass ring jyve is striving for, can definitely be
taxing.

Having support for Pyodide would be the killer feature :+1:  (and I see that https://github.com/deathbeds/jyve/pull/27 is getting there progressively).
It should be relatively straightforward to have a generic worker kernel for JavaScript. With of course the caveat of not being able to access the DOM (unless some proxy / virtual dom is used maybe). But it would still be interesting to have it as a plain JS kernel and as an alternative to the other JS kernels out there.

towards features that lab just already has. I think there's a lot of space
for theme-only reduction and plugin replacement to get to more pleasing
minimalism, such that other peoples' plugins just work. Maybe the best hook
for that right now is probably "presentation mode"?

This is something that has come up quite often indeed. Many folks like the simpler look and features of the classic notebook, and it sounds like there could be good reasons for having more minimal frontends. Presentation mode is a good compromise but it still leaves a bit of chrome on the screen.

You mean the Lab API and the changes with new major releases?

Right: the kernel/session stuff seems to be particularly volatile, and does change on point releases in ways that break jyve, because of the weird monkeypatches. I took a serious swing at 1, and gave up (not a lot of extra time for it). Will be taking a look at lab 2. I've lobbied in the past for additional API extension points to make things more composable, it's a matter of a) having time, b) getting jyve stuff working with something like master, c) doing the pr and d) waiting for a release so people can actually use the stuff.

bit of chrome on the screen.

Right: here's (one of) the kernel-side examples we've used to cut down the noise:
https://gist.github.com/tonyfast/e2e574e6fa3dcc4a4557f486d8bf0d70
It's mostly hygeinic, only firing when presentation mode is hot. It would not be a big deal to package this into an extension, plus a little more fancy stuff, but the key thing is when you're presenting/working, you can focus on the goods. But you're still paying for 5mb on the wire.
From a size-on-wire perspective: the p5notebook bundle.js is 1/5 the size of core lab, which is certainly good, but it still blocks that screen until blueprint, codemirror, react, etc. are loaded. The truly minimal thing (that would still work with lab app extensions) is probably something like:

@jupyterlab/services 100k
@lumino/application 50k
codemirror 50k

and have everything be built from there, with a lot more laziness... but building up an app is not everyone's cup of tea.

Closing since there is now a reboot happening in https://github.com/jtpio/jupyterlite.
And the p5-notebook use case will be just a custom JupyterLite distribution with p5 branding and p5 related kernels.

Yup, is cool. Would also see offering the "slow reveal" iframe approach vs
build-and-then-do-nonjs-magic, but that's another issue.
Once lite supports federated extension, certainly consider making the p5
kernel one! While it will be nice to have a distribution just for p5, being
able to combine multiple things is fun! Indeed, there's the opportunity to
show interesting interactions between client kernels in a way that isn't
straightforward with zmq kernels.


add(tools): Tails Devtools

Name
Link

Tails Devtools
https://github.com/vechai/tails-devtools

All-in-one browser extension for Tailwind CSS Developer.

[x] My item is in the right category
[x] My item is logically grouped below similar items
[x] My item's name and description respects the conventions of the list
[x] My item is awesome
[x] My item is in line with the Tailwind brand usage guidelines
[x] I have read and followed the contribution guidelines

Thanks!


Could/Should this cover updates across Visual Studio versions?

Having discussed the process of updating a dev VM from VS2019 to VS2022, I understand that it's necessary to specify Visual Studio Extension Development workload, with the Modelling SDK option checked, during installation of Visual Studio, in order to use the F&O Development tools. Is that worth capturing here?

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

ID: f9eb8e0d-73de-5530-5966-67b151ed89f3
Version Independent ID: 1e98b55e-bced-af14-8a34-373c38af5365
Content: Update the Visual Studio development tools - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/dev-tools/update-development-tools.md
Service: dynamics-365-cross-app
GitHub Login: @gianugo
Microsoft Alias: gianura

Thanks @rrhkpmg for the suggestion.
That's correct and the article has been updated. New changes should publish at some point today.
Many thanks.


bug: Comments are still broken

Inline comments and others really mess up both logging and parsing. A better way to cleanly remove them, as well as duplicate newlines would be good. Currently we just do some weird hack in the parser with saturating_sub but this solution is not good.

resolved by #1df513e


Divider widget's line width does not match Material design guidelines

Steps to Reproduce
Create a Divider widget and observe how it's rendered. Here is a screenshot from iOS simulator running iPhone 7 in front of Material design documentation page on Dividers:

Setting divider height to < 1.0 seems to be restricted by assertion.
The same behavior can be observed in ListTile.divideTiles which uses DecoratedBox with border decoration of 1.0 width.
I did some experimentation and was able to get better rendering by implementing custom divideTiles method and setting border width to 0.5. Result:

Logs
N/A
Flutter Doctor
N/A

Thanks for the feedback!

I'd be happy to work on a PR if I can get some hints around what would be a good solution or where to look to start with.
Yesterday I noticed that this also affects user account drawer header. It seems like this may be an issue of underlying rendering engine?

It looks like the bug is just that we misread the Material specification. :-)
The core fix is to change this line:
https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/material/divider.dart#L71
...to specify that the border width is 0.0 (which is always painted as one device pixel).
The problem is then trying to figure out what the right behaviour is beyond that. For example, we should probably change how the rest of that build function applies the height so that it's applied on the outside and then the line is drawn automatically centered (SizedBox -> Center -> DecoratedBox or some such). We should probably also remove the restriction on the height so that it can be less than 1.0 (though not less than 0.0) and update all the documentation and then add a test.

Sounds like something I can take on.
Any objections if I also cover ListTile.divideTiles and potentially UserAccountDrawerHeader dividers?

Not at all, please go ahead!


RR.debugOn broken

Interesting, it works for me.
A few questions:

What browser? That's not IE is it? IE isn't supported.
If you go into this code sandbox, and set the scope of the console to the sandbox, and try __RR__.debugOn() there, does it work for you?

What version of react-recollect?

Also worked for me on the latest version of recollect:
__RR__.debugOn()

It is working fine latest chrome browser. I think issue with browser version. Closing the issue


Add option to return a promise

Returning a promise would be really useful as that way I wouldn't have to use deferreds every time I use Tabletop and would allow things like resolving multiple datasets with $.when(def1, def2).

+1

+1

+1

+1


Add language navigation to retired releases page

Add the standard language navigation bar to the retired releases page. Without it, you could be scrolling for days.

@mario-guerra As of right now, there are no retired packages to list for non-Tier 1 languages. Do you want those non-Tier 1 languages removed from this navigation bar?

@scottaddie yes, let's remove the non-Tier 1 language links from the navigation bar.

Here's how it looks with my latest changes:

@scottaddie LGTM

I'm Ok having this but I explicitly excluded it because I added them to the sidebar but we could have it up top on the page as well.


feat: Add lifecycle ignore userdata as otherwise reboots existing instances

Description
Add instance Lifecycle rule to ignore user_data changes.
Motivation and Context
There are times when I want to update the userdata and not replace the existing instances (which can be achieved with  user_data_replace_on_change) but also not reboot the existing instances which is the case if not replaced.  We can't be rebooting tens of instances for a small change we want applied to any new instances and if we want it applied to all instances then a replace is required anyway
Breaking Changes
No
How Has This Been Tested?

[ X] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[X ] I have tested and validated these changes using one or more of the provided examples/* projects
[X ] I have executed pre-commit run -a on my pull request

Sorry, I know it is not good having more resources just to be able to add this "lifecycle ignore" entry  but as it is not possible to pass  anything but a static list it would seem like the only way. I would have loved to make it dynamic if that was supported.

unfortunately, this doesn't make sense. perhaps a different architecture is better suited (i.e. - using autoscaling groups)


Analytics rationalisation and update

Context
The analytics audit showed that there was a lot of tracking where it wasn't needed, and an absence of tracking where it was needed.
Changes proposed in this pull request

Events no longer fire when links the header and the footer of the page are clicked
Events no longer fire when a register is sorted
The feedback form now includes the 'No' sub-options, and only fires when the form is submitted
Accordions only fire an event when opened, not when closed
Unsuccessful searches now fire an event to let us know what query wasn't found

Guidance to review
(Apologies for the mass of linting changes that have become inextricably linked to this PR).
This has been tested in all of the supported browsers - but extra eyes are always welcome!

Can we use XO linter as this is the GDS way: https://gds-way.cloudapps.digital/manuals/programming-languages/nodejs/#source-formatting-and-linting

This has snowballed, as the accidental reformatting has highlighted things that neatened up. I'm closing this, and I'll put in a set of pull requests that will fix all of @gidsg comments and suggestions.


Metrics: Add kafka delivery error metric

We currently report metrics on "data loss errors" by detecting if the producer buffer is full.
This PR adds an additional metric kafka_delivery_errors. These errors are produced when the Kafka producer permanently fails delivery of a message.
Delivery errors may eventually be captured by the existing "data loss errors" metric, but the new metric is a more direct way of capturing them, and can probably capture other errors ignored until now.

Codecov Report

Merging #235 (bffa582) into main (a8c5193) will increase coverage by 0.02%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #235      +/-   ##
==========================================
+ Coverage   88.82%   88.85%   +0.02%
==========================================
  Files          25       25
  Lines         886      888       +2
  Branches       99       99
==========================================
+ Hits          787      789       +2
  Misses         75       75
  Partials       24       24

Impacted Files
Coverage Δ

forwarder/repeat_timer.py
83.87% <ø> (ø)

forwarder/statistics_reporter.py
90.62% <100.00%> (+0.62%)
:arrow_up:


Should we ignore the ERROR warning about pandas version in getting_started/part3_exploring_cohorts.ipynb?

While setting up a GitHub actions workflow to automatically test if getting_started notebooks are running properly in colab docker container runtime, I came across this error warning in itkwidgets section while running this command.
!pip install -q pydicom-seg "itk-io>=5.3.0" "itkwidgets[all]>=1.0a32"
The command itself returns exit code 0 which I guess does not indicate any problem and the rest of the notebook still runs but I'm unsure if there are issues with the widget. @bnmajor whenever possible --not in any rush at all, could you run the notebook and let us know if we can ignore this error?

I found a similar issue in some other repo and they advise to ignore this error, but would be great to just confirm it. https://github.com/huggingface/autotrain-advanced/issues/265

@vkt1414 You are correct, this message is safe to ignore for now! Just to note what is going on here: itkwidgets depends on ngff-zarr[dask-image] and dask-image requires pandas >=2.0.0 - hence the conflict with Colab's 1.5.3 requirement.
At this point it looks like there is no reason we can't downgrade Pandas to 1.5.3 if needed but if there is a need for Pandas in this notebook in the future and there are any issues around that I am happy to help!

Excellent. Thank you very much for the prompt response!
@fedorov I'll close this issue.

Thank you @bnmajor - it is good to have this documented here!


[FEATURE] Expose iSCSI targets to clients outside of the cluster

Is your feature request related to a problem? Please describe.
iSCSI clients outside of the Kubernetes cluster in which Longhorn is installed should be able to connect to volumes created and presented as iSCSI targets.
Describe the solution you'd like
Existing documentation and steps are followed.  The volume details should be published with an external IP address instead of the internal cluster IP.
iSCSI initiators should be able to discover and connect to Longhorn volumes via this published cluster external address.
Additional context
A similar request is described in #906, however the workaround in this case was to deploy VMs on the same nodes as Kubernetes workers and plumbing in their networking into the overlay.  A better solution would be to enhance Longhorn's functionality to properly expose iSCSI targets externally.
It's possible to at least define a Service of type NodePort that refers to an Endpoint with the IP and port returned by Longhorn when you create a volume with the iSCSI frontend option, for example:
kind: "Service"
apiVersion: "v1"
metadata:
  name: "external-iscsi"
spec:
  type: NodePort
  ports:
    - name: "iscsi"
      protocol: "TCP"
      port: 3260
      targetPort: 3260
      nodePort: 0
  selector: {}
---
kind: "Endpoints"
apiVersion: "v1"
metadata:
  name: "external-iscsi"
subsets:
  - addresses:
      - ip: "<IP_ADDRESS>"
    ports:
      - port: 3260
        name: "iscsi"

An external client can then perform target discovery using this NodePort, for example:
% sudo iscsiadm --mode discoverydb --type sendtargets --portal <IP_ADDRESS>:32615 --discover
<IP_ADDRESS>:3260,1 iqn.2019-10.io.longhorn:external

However, the IP address and port returned from this discover refers back to the cluster internal address, so attempts to connect to this from outside Kubernetes eventually just timeout.  In addition, even if this did work it'd be targeting a single internal service and so would not be HA.

slightly related support for dedicated storage networks #2285

We also have this need. Any further plan?

Lonhorn 1.3 will support multi-network based on multus cni. I would like to known if it is possible to replace the IP in the endpoint of iscsi frontend volume with Storage IP ? Then I can access the iscsi target outside the cluster.
Have time to look at this question ? @c3y1huang
Related code as follows.
https://github.com/longhorn/longhorn-manager/blob/3ca585fd3a36f57fea36e37f2109f6c5c823e9e0/controller/engine_controller.go#L802
endpoint, err := engineapi.GetEngineEndpoint(volumeInfo, engine.Status.IP)

...

func GetEngineEndpoint(volume *Volume, ip string) (string, error) {
	if volume == nil || volume.Frontend == "" {
		return "", nil
	}

	switch volume.Frontend {
	case devtypes.FrontendTGTBlockDev:
		return volume.Endpoint, nil
	case devtypes.FrontendTGTISCSI:
		if ip == "" {
			return "", fmt.Errorf("iscsi endpoint %v is missing ip", volume.Endpoint)
		}

		// it will looks like this in the end
		// iscsi://<IP_ADDRESS>:3260/iqn.2014-09.com.rancher:vol-name/1
		return "iscsi://" + ip + ":" + DefaultISCSIPort + "/" + volume.Endpoint + "/" + DefaultISCSILUN, nil
	}

	return "", fmt.Errorf("unknown frontend %v", volume.Frontend)
}

Lonhorn 1.3 will support multi-network based on multus cni. I would like to known if it is possible to replace the IP in the endpoint of iscsi frontend volume with Storage IP ? Then I can access the iscsi target outside the cluster.

Currently, the iscsi endpoints are not over the storage network because it needs to be local. We will look at this when we start working on this issue.


computer crashes when opening and running second interactive pane on different file

Environment data

VS Code version: jan 2021
OS and version: windows 10
Python version : 3.8

Expected behaviour
open file run cells in interactive pane
open second file and run cells in interactive pane
Actual behaviour
on running cells in second file while first pane is still open
second pane opens but then computer crashes with blue screen

Thanks for the bug. Very strange that our window could cause a blue screen. What code were you running?

A blue screen would be an indication of a bug in a driver or other component that we have no control over.

Maybe a driver was the cause but I'm not sure.  I was running the Wise System Monitor and the blue screen reported that was the cause. So I uninstalled it and rebooted.  But it happened again with a different cause (more generic - forgot the label).  So I rebooted again and tried opening a blank notebook.  That was stable.  I then tried opening more notebooks from files.  I opened 6 and they were all stable.  You can close this if you want and I will reopen an issue if I see it again.


Replace keep_running by tail -f /dev/null

https://github.com/300481/rancheros-firewall/blob/2e38fa146c11eedb324375f18143b4a05b5596c7/configure-firewall.sh#L101

done with https://github.com/300481/rancheros-firewall/commit/578c35b6d984a7ccb9ebae9ac1253ab82fff5d95


signal.bilinear() can't handle leading zeros

It looks to me that bilinear(b, a) can't handle cases where there is leading zeros in arrays a and b. Here is some examples:
In [57]: signal.bilinear(1, [2], 1)
Out[57]: (array([ 0.5]), array([ 1.]))

In [58]: signal.bilinear(1, [0, 2], 1)
Out[58]: (array([ 0.5,  0.5]), array([ 1.,  1.]))

In [59]: signal.bilinear([0,1], [0, 2], 1)
Out[59]: (array([ 0.5,  0.5]), array([ 1.,  1.]))

In [60]: signal.bilinear([0,1], [2], 1)
Out[60]: (array([ 0.5,  0.5]), array([ 1.,  1.]))

What is expected that all return the same answer as first one. One may not review it as an issue. However, in cases that b and a are computed on-the-fly, one can't predict when we have leading zeros because of limited computational precision. IMO, it's better removing the leading zeros inside bilinear()

The result is not strictly wrong it is just not a minimal realization. So I don't think it actually promises a result with minimal realization anyways.
But until the developers chime in, you can also pass them through numpy.trim_zeros
sig.bilinear(*map(np.trim_zeros,([0,1], [0, 2])), 1)
(array([ 0.5]), array([ 1.]))

There exists the function scipy.signal.normalize, which trims leading zeros from a (b, a) transfer function; it is automatically used in the construction of a TransferFunction object. If you'd like bilinear to call this automatically on its input, a PR is welcome!


Inherit user site with --inherit-path

How do people feel about also inheriting the user site when --inherit-path is used?

seems reasonable to me and the change itself looks good - how would you feel about adding a basic test to exercise and enforce the behavior going forward?

Just extended the (minimal) existing tests covering --inherit-path.

thanks @brbsix - this one is also in.


⚠ Fortnite has degraded performance

In 1d27b9b, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1519 ms

Resolved: Fortnite performance has improved in b8ac59c.


Standardize the use of the proxy's ID as the request ID for the LSP.

[ ] Added an entry to CHANGELOG.md if this change could be valuable to users

Could you please make the request id the first param of a function


Preventing from prefetch in data save mode 🌐

Preventing from prefetch in data save mode and in 2g connections 🌐

window.docusaurus.prefetch already checks isSlowConnection. See:
https://github.com/facebook/docusaurus/blob/2e66e1cbbabb70abd8968ae2c3999d9a1056bd14/packages/docusaurus/src/client/docusaurus.ts#L49-L52

window.docusaurus.prefetch already checks isSlowConnection. See:
https://github.com/facebook/docusaurus/blob/2e66e1cbbabb70abd8968ae2c3999d9a1056bd14/packages/docusaurus/src/client/docusaurus.ts#L49-L52

sorry :(


Fix: update homebrew before install kubevela client

Install the client via brew should update brew itself firstly.
Linked: https://github.com/oam-dev/kubevela/issues/1391

The docs laid on there: https://github.com/oam-dev/kubevela/tree/master/docs please send a PR there

thanks, closing

Has sent PR.


Update README.md

Link to CodeMeta to CFF conversion tooling from openCARP-CI

Thanks for updating the PR, @axel-loewe! I'm waiting for the tests to pass (Python 3.6 tests will fail due to https://github.com/actions/setup-python/issues/544, to be fixed in https://github.com/citation-file-format/citation-file-format/pull/424), and some link checking may fail as well, which I'll check. Happy to merge after that.


Updated version to 4.0.0--Beta.11

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ArticleCard: new component

ArticleCard: new component

This update creates a new component that will enhance the current Card component. The ArticleCard component contains multiple placeholders that can render either a text or a more complex child component. All text placeholder (title, content) will be truncated based on the prop limit. This component follows the new file organization structure as well as the latest Blue conventions (styled() and mount based testing).

Coverage remained the same at 100.0% when pulling 25b87c3fb65caf83762f5c6d24d2c2e4f5e2e883 on feature/new-article-card into e440101a70e103bdc578e9cd0b29917a18415b2a on master.

@plbabin Nice!! Will take a look at this in a few 🙌

@plbabin Amazing work! Thank you so much for your help on this 😍
Merging


Don't send email notifications

Title kinda says it all
I get an email notification for pull requests.
would b nice to have a way to config that.
I c 2 places for configuring this:

in every email, add a "don't send me more emails" button
When enabling a repo

Thoughts?

Are you sure this isn't GitHub itself notifying you? As far as I know Greenkeeper doesn't send any emails.

Are you sure this isn't GitHub itself notifying you? As far as I know Greenkeeper doesn't send any emails.

@Arcanemagus thanks for your quick reply
u r right, I should've been more clear.
It is github notifying me, however i only get emails for PRs from GK. maybe it's because it's a different user then me opening the PR?
and if so, is there a way around that?

@Arcanemagus thanks for your quick reply
u r right, I should've been more clear.
It is github notifying me, however i only get emails for PRs from GK. maybe it's because it's a different user then me opening the PR?
and if so, is there a way around that?

You can simply change your notification preferences here.

You can simply change your notification preferences here.

yes but AFAIK there's no way to disable notifications from specific users

yes but AFAIK there's no way to disable notifications from specific users

Hey @goldylucks,
yeah this is an issue with GitHub. I recommend setting up a local email filter to manage the load. But we hope Github will improve their settings in the future.
Best,
Finn


[Concurrent Segment Search] Experimental release readiness for 2.10

We want to announce the experimental release of concurrent segment search in 2.10. This issue is to track items needed for that. All the changes are merged in with fixes for known issues. With experimental release, users should be able to enable the feature and try it out for their search workload on non-production setup and provide their feedback.
Doc update:

How to use enable/disable this experimental feature and other settings available
New profile API stats that are added in 2.10
New search stats that are added for concurrent search
How terminate_after is handled differently with concurrent segment search
Add the link to project board to track all the open items

https://github.com/opensearch-project/documentation-website/issues/4989

@sohami Is this still targeting 2.10? If the feature is not already merged, then it is past code-freeze and we should move it to 2.11?

@DarshitChanpura We are tracking for experimental release and not GA. So changes already in 2.10 branch has majority of functionality already in it.

Closing as the experimental feature is launched in 2.10.


Pass configuration to source and executor plugins

Description
Changes proposed in this pull request:

Pass configuration to source and executor plugins

Testing
Manual testing is not needed as both cases are covered by e2e tests.
Related issue(s)
Fix #872

Hi @josefkarasek!
Thanks for valuable feedback 🙂 In this commit, I updated the gRPC according to our discussion.
I spot and updated the old plugin repository definition too.


Refactor: walk dependency graph rather than folder tree

:tada: This PR is included in version 1.3.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


various fixes

1. Tell us something about your changes.
various fixes:

add folder for firmware known as working with hyperion
rs232: add debug message for close and do not repeat "port not found" message more than necessary
v4l2: fix grabber started on creation when set to disabled
cmake: add new platform x86-dev - this as most code coverage and is usefull for test/development. This is not for release
config.commented: add hints for effect-args

2. If this changes affect the .conf file. Please provide the changed section
no
3. Reference a issue (optional)
#126 #87
Note: For further discussions use our forum: forum.hyperion-project.org

@penfold42 I would add your udp sketch for esp8266, where I can find that? Did we have other firmware, e.g. adalightAPA?

Yep - and my 2 "SPI to 281x" sketches
https://github.com/penfold42/stuff/blob/master/README.md

@penfold42 canyou test my latest changes regarding v4l. Now disable should work


Crash in new version of Create

Crash in new version of Create

It is expected behavior since there is so much change between 2 Create version. We are working on it now.

New release has been uploaded to curseforge and modrinth.


Wondering if there's a safe way to shutdown the ESP services?

Hi, Maintainers,
How can we shutdown ESP services safely after I finished the node provisioning?
There's no script to tear down the services.
I tried to run "docker-compose down", but after the service containers are down, I failed to delete the ESP folder and got the following "Device busy" issue:
rm: cannot remove 'esp/template/nginx/index.html': Device or resource busy
rm: cannot remove 'esp/data/srv/tftp': Device or resource busy
rm: cannot remove 'esp/data/usr/share/nginx/html/tftp': Device or resource busy

I have to manually "sudo umount" those locations, then I can clean up the folders.
Please help to check this issue and let me know if anything wrong.
Thanks!

The tested version is 1.6.2.

the following worked for me
umount /root/dek/esp/data/usr/share/nginx/html/tftp
rm -rf /root/dek/esp/data/usr/share/nginx/html/tftp

Yep, this works. But I think the script should take care of these mounts.

@ychen2u
Patch for this issue:
https://github.com/intel/Edge-Software-Provisioner/pull/30


Add new rule that detect retrieving environment variables from /proc files

These days, it's common to pass a secret to an application running on a container via an environment variable. Secrets store very sensitive information such as cloud credentials and JWT secretkeys, so it is important to detect when environment variables have been retrieved by an attack.
And if the application has SSRF or path traversal vulnerabilities, the attacker can steal the environment variables of the application process by reading /proc/self/environ and /proc/1/environ under the /proc directory.
https://linux.die.net/man/5/proc
For example, SSRF:
curl -X POST -d "url=file:///proc/self/environ" https://example.com/ssrf
curl -X POST -d "url=file:///proc/1/environ" https://example.com/ssrf

Path traversal:
curl --path-as-is https://example.com/path/../../proc/self/environ
curl --path-as-is https://example.com/path/../../proc/1/environ

In MITRE ATT&CK, this technique is categorised as T1552 : Unsecured Credentials, and Sub-technique T1552.001 : Unsecured Credentials: Credentials In Files, and Detection is DS0022 - File - File Access, and component is T1003.007 OS Credential Dumping: Proc Filesystem.
I propose the following as a rule to detect environment variable reading from files under the /proc directory.
- list: proc_environ_file_names
  items: [/proc/self/environ, /proc/1/environ]

- macro: proc_environ_files
  condition: >
    fd.name in (proc_environ_file_names)

- rule: Read environment variable from /proc files
  desc: An attempt to read process environment variables from /proc files
  condition: >
    container and open_read and proc_environ_files
  enabled: true
  output: >
    Environment variables were retrieved from /proc files (user=%user.name user_loginuid=%user.loginuid program=%proc.name
    command=%proc.cmdline file=%fd.name parent=%proc.pname gparent=%proc.aname[2] ggparent=%proc.aname[3] gggparent=%proc.aname[4] container_id=%container.id image=%container.image.repository)
  priority: WARNING
  tags: [filesystem, mitre_credential_access, mitre_discovery]

Adding a host to the detection target causes false positives by systemd, so limited to container.

I'm waiting for your comments on detecting reading these files and my proposed rules.
I would appreciate it if I could create a Pull Request about this rule.
Thank you.

Hey @hi120ki, there's no need to open an issue first if you already have change proposals ready like in this case. Please go ahead and open a PR for this so that we can continue the discussion there! Thank you for addressing this point, and great explanation too 👍

Thank you!
I created PR #2193, and close this issue.


Add Linseed RBAC,envvars for eks log forwarding

Related PR:
fluentd-docker: https://github.com/tigera/fluentd-docker/pull/402
For token generation:
Linseed:https://github.com/tigera/calico-private/pull/6946
RBAC, env variable to connect to linseed
https://github.com/tigera/operator/pull/3018

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

@caseydavenport Ready for review

@caseydavenport Made additional changes to fix "tigera-eks-log-forwarder-tls secret not available yet, will add it if/when it becomes available" Info log in operator pod for non EKS environment,
https://github.com/tigera/operator/pull/3018/commits/2933dd3ea21ad9ccac8a6f699368f812ee500d9a
Please take a look.

@caseydavenport Done :+1:

/sem-approve


Make Gradle's own build reproducible

When running two builds of the same sources of Gradle,
outputs were not binary equivalent, this was primarily
due to zip files not being equivalent due to both
file ordering and timestamps in the file metadata.
This changes makes it so that running two gradle builds
with the same buildTimestamp
(e.g. -PbuildTimestamp="20181220000000-0800") produce the same output.
Having a reproducible build will make it easier to verify that
the official distributions match the sources on github.
Following changes were needed:

switch to the kotlin-dsl provided zipTo methods instead of Ant's
zip helper for the tasks that package the kotlin-dsl dependencies as zipTo
correctly ignores file metadata
set all AbstractArchiveTasks preserveFileTimestamp=false
& reproducibleFileOrder=true to ensure jars created do not have file ordering
or metadata changes from build to build

Context
A chain of custody from source to binary is a great thing to have so people can verify for themselves that the distribution matches the sources.
Contributor Checklist

[X] Review Contribution Guidelines
[X] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[X] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[X] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

Not sure how to add tests for this other than manually testing that "diff --brief -r" shows no differences between 2 clean builds

Closing in favor of #8541.


Work with IONIC 3?

please update to work's with IONIC 3

@TheBosZ please help us

There's no reason the plugin won't work with Ionic 3.
Here's an example of someone using a different plugin with Ionic 3: https://stackoverflow.com/questions/45153570/ionic-3-how-to-use-cordova-plugins

import { Injectable } from '@angular/core';
import 'rxjs/add/operator/map';
import { JwtClientProvider } from "../jwt-client/jwt-client";
import { JwtPayload } from "../../models/jwt-payload";

import { UserResourceProvider } from "../user-resource/user-resource";
import { BehaviorSubject } from "rxjs/BehaviorSubject";

import { Facebook, FacebookLoginResponse } from  '@ionic-native/facebook';
import { GooglePlus } from '@ionic-native/google-plus';
import { TwitterConnect, TwitterConnectResponse } from '@ionic-native/twitter-connect';

@Injectable()
export class AuthProvider {

  private _user = null;
  private _userSubject = new BehaviorSubject(null);

  constructor(private jwtClient: JwtClientProvider,
              private fb: Facebook,
              private googlePlus: GooglePlus,
              private twitter: TwitterConnect,
              private userResource: UserResourceProvider
              ) {
    }

    loginTwitter():Promise<any> {
      return this.twitter.login()
      .then((response: TwitterConnectResponse) => {
        let accessToken = response.token;
        return this.userResource
            .register(accessToken, 'twitter')
            .then(token => this.jwtClient.setToken(token));
      })
      .catch((error) => {
          console.log(error);
      });
    }

    logoutTwitter():Promise<any>{
      return this.twitter.logout().then(() => {
            console.log("logged out");
        });
    }

my code, not work

Wow! I didn't know that the Ionic team added this plugin to their project! That's pretty cool.
Unfortunately, I haven't really used this plugin since 2015 (it was maintenance-only mode after that point) and no longer work for Manifest Web Design. I am neither using this nor Ionic at my current employer (sad face here) so I'm not knowledgeable enough to help you.
It looks like you're doing everything correctly from the Ionic Native docs, but without more details (like what the error log says), I can't really help.
If you can post more error messages (like what exactly the error says, what exactly is not working), I may be able to help you troubleshoot. You can also try asking over on the Ionic forums to see if anyone can help.


Curl certificate problem

Hi Luca,
Thank's for your job.
I have a problem making the call from CURL
curl -X POST "https://localhost:44370/Validation/bool?input=QRSTRING" -H  "accept: text/plain" -d ""

where QRSTRING is a real encoded string GreenPass QR

I get this error:
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
why if I try it from the web interface it works and from a direct call curl doesn't?
can you give me some suggestions how to solve?
thanks a lot

wrong issue


Why this CSS ".entry-content blockquote + p"?

I'm just curious why this style exists:
.entry-content blockquote + p {
    color: #555;
    font-style: italic;
    font-weight: 200;
}

I don't quite understand why the text after a blockquote needs to be light-weight italics. On the sites I'm reading these are always just a normal part of the article and this styling looks a little peculiar.
I'm just wondering...

I cannot recall why I did this. Perhaps, it was for feeds that use a paragraph to cite the source of the blockquote. I believe that could be removed since it will apply a wrong style to the next paragraph most of the time.


refactor: Improve memory metric parsing

Can you clarify what is improved?

Can you clarify what is improved?

this version uses a for-loop instead of multiple conditional checks
and other minor tweaks

No. You made it slower. If MemAvailable is available, other properties should not be searched.

No. You made it slower. If MemAvailable is available, other properties should not be searched.

would you like me to fix that :upside_down_face:

No


Export to webpage does not work

Hi! Thank you for the great work! Export to webpage seem do not work now. This is also mentioned by other uses here. I am using Firefox 111.0 (64-bit), not sure whether this is related to browser~

could you share the error message in console? it's working on my firefox + macos

I have updated to the latest version and it works now. Thanks!


Add client credential auth method

This adds a new oidc authentication method to the client and refactors the authentication handling

Do we want to add same test for Google authentication?

Do we want to add same test for Google authentication

Google sadly doesn't support client credentials. I haven't tested user/pw, but I'll make sure that the next method is supported by google


App restart after getPicture() in Android

Bug Report
App restart after getPicture() in Android
Problem
App restart after getPicture() in Android
What is expected to happen?
Take a picture
What does actually happen?
App restart
Environment, Platform, Device
cordova (Cordova CLI) : 9.0
Cordova Platforms : android 8.0
cordova-plugin-camera 4.0.3

I am having the same issue.

Same problem here, however, very irregular and very difficult to reproduce.

I am having the same issue.

I'm not sure but I assume that the app is terminated by the operating system due to lack of memory while using the camera app. Currently I'm not sure how to fix this.

I have the same issue, but only in a device with memory smaller than 3gb.
There was not a workarround to this?

I'm not sure but I assume that the app is terminated by the operating system due to lack of memory while using the camera app. Currently I'm not sure how to fix this.
EDIT:
You can reproduce it by opening the camera, then filling the main memory with an app like FillRAM. After taking the picture, the Camera Activity will be closed and the app will restart.

I have the exact same feeling. Newer Android devices take pictures with a much higher resolution then the older ones.

Is this reproducible in a new, plain Cordova app? A minimal reproduction repository would really help to debug and later fix this issue. More information on how to create one: https://github.com/apache/cordova-contribute/blob/master/create-reproduction.md

you can easily reproduce this by going into the develop settings and enable "Don't keep activities"

This is not a bug, but part of the Android lifecycle. The Android OS may kill activities that are in the background to preserve memory, particularly if the foreground activity requires a lot of memory. When you use the Camera App, it puts your app into the background.
This is documented here: https://github.com/apache/cordova-plugin-camera#android-quirks with an explanation of how to deal with these cases.


style(redux): change global action names

WIP: check naming, only global actions names changed

Hi @cpooley, thank you for working on this. Even if the pull request is still a work in progress, I see value in giving you feedback early on so we are on the same page from the start with naming conventions. We'll share our thoughts soon.


Scam Account Submission

Duplicate Submissions

[X] Yes, I checked that the account name is not currently in the list
[X] I read the wiki explaining each different categories and examples before submitting

(Required) Spam Comment Direct Link
https://www.youtube.com/watch?v=aB2wvo7PEq4&lc=Ugxemeyc1A5oE6DcmkZ4AaABAg.9tJz72HjwR19tLnPQiKWXf
https://www.youtube.com/watch?v=aB2wvo7PEq4&lc=UgydpgZjovdlafGMGxx4AaABAg.9tJjP9A8H759tJl1M7l1re
https://www.youtube.com/watch?v=aB2wvo7PEq4&lc=UgzcYCEzjzMNgi7_iWV4AaABAg.9tKaK_ptY359tKdPi-bk6b
(Optional) Screenshot of comments referencing the scam account

(Required) List of the scam account names
AdalineAlice
DontReadMyProfilePicture.94
AAAAVR

While they are a bot we don't currently have a category to add it to sorry.


DOC: split docstring into multiple lines in excel.py

[x] closes #13967
[x] tests added / passed
[x] passes git diff upstream/master | flake8 --diff
[ ] whatsnew entry

A follow-up on #14030.
Not sure whether this is the good way to do it - this seems too verbose.
I will add it to parsers.py or move it to common.py once it's done.
I also thought about moving the function to Appender to fix the length problem for good if necessary.

this is also an issue on read_csv doc string as well

Current coverage is 85.27% (diff: 100%)

Merging #14073 into master will increase coverage by <.01%

@@             master     #14073   diff @@
==========================================
  Files           139        139
  Lines         50455      50465    +10
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          43026      43036    +10
  Misses         7429       7429
  Partials          0          0

Powered by Codecov. Last update 6645b2b...5e61c71

@jreback  do u want me to move the func to common.py?

yes move to common.py

@jreback @jorisvandenbossche I assume this is what you're talking about? It seems okay to me.
I have limited access to Internet in these few days so I might not responding in time.

@OXPHOS Just a question, what did you precisely change regarding to the previous version (I just don't remember exactly anymore, sorry). Sometimes adding a commit instead of amending the previous can make this more clearer.

@jorisvandenbossche oh sorry my bad. I realized this problem but made the wrong fix.
So I was doing this only for the last commit.
And now I used this

@OXPHOS coming back to this, is the spit_doc function still needed now that you added a call to textwrap.fill (which already splits the long string created by "', '".join(sorted(_NA_VALUES)) ? Seems like you can remove this now?

@jorisvandenbossche I updated the wrap char number and now both parses.py and excel.py uses textwrap.fill

@OXPHOS Thanks a lot, looking good!


Unable to load chats. Details: Error: 401: Unauthorized

After deploying to Azure, log in to AAD and enter Loading Chats with an error message: Unable to load chats Details: Error: 401: Unauthorized

Hello!
There are multiple authorization options for the web service: https://github.com/microsoft/semantic-kernel/blob/main/samples/apps/copilot-chat-app/webapi/appsettings.json#L68.
Depending on how you configure it, you will have to set up your Web App differently: https://github.com/microsoft/semantic-kernel/tree/main/samples/apps/copilot-chat-app#start-the-webapp-frontend-application. Please refer to section 1 part 2.

@XunLi-Nick were you able to get unblocked?

Closing now as it appears this issue has been resolved. Please reopen as needed.


Combine DragListener and KeyboardDragListener into a single class

While working on https://github.com/phetsims/scenery-phet/issues/849, we found that RichDragListener and RichKeyboardListener are identical, but need to be duplicated because they DragListener and KeyboardDragListener are separate classes. I wonder if we could create a third class that combines them into a single drag listener, and have RichDragListener extend from that. @jessegreenberg @pixelzoom, I couldn't find another issue for this, but please close as a duplicate if I missed it. I know we have discussed this before.

I also thought there was a similar issue, but can't locate it.  It's unfortunate that we need to add both a DragListener and a KeyboardDragListener, but I'll be surprised if we find a way around that.

This is probably a subset of https://github.com/phetsims/scenery/issues/1238.

I wonder if we could create a third class that combines them into a single drag listener,

Great idea!

I also was teasing with the idea of doing it in a different way, where we make KeyboardDragListener a subtype of DragListener. Perhaps calling it FullDragListener. And it may not be too challenging to handle an "off switch" for each type of input. No matter, this isn't the kind of work we could just sprinkle into an iteration.

Over in https://github.com/phetsims/scenery-phet/issues/849, we need KeyboardDragListener to have an interrupted flag like PressListener. I'll add it here.

This was also nice, as it aligned the API for the end callbacks.

I am trying out an idea for this in branch richDragListener_scenery_1614. It simply creates both a DragListener and a KeyboardDragListener and forwards the input events to each. Options are set up so that many are shared by the two listeners but you can still provide options to each listener as needed.

A combined RichDragListener was added to scenery-phet using the approach from https://github.com/phetsims/scenery/issues/1614#issuecomment-2121484904. It is in scenery-phet because it combines the "rich" drag listeners that also include tambo sounds. Ill prune the scenery branch now that we are done with it and transfer this issue to scenery-phet to wrap up.

Code review will occur in https://github.com/phetsims/scenery-phet/issues/858, closing.


Example with dynamic meta tag would be helpful

Issue:
http://stackoverflow.com/questions/41061233/issue-with-loading-dynamic-meta-tag-value-in-react-app-using-server-side-renderi?noredirect=1#comment69495327_41061233

This is not an issue with react-helmet, but with fetching data before calling React.renderToString() on the server. http://stackoverflow.com/questions/30974007/fetching-data-before-rendering-server-side


[dv] Common exclusions don't work for Xcelium

@rasmus-madsen
We have these 2 exclusions for toggle, but they don't work. Can you take a look?
https://github.com/lowRISC/opentitan/blob/92173aa54ac2fba4c68b2362eb0bf7b563b09cfb/hw/dv/tools/xcelium/common_cov_excl.tcl#L9-L10
EDN still shows them uncovered.
https://reports.opentitan.org/hw/ip/edn/dv/latest/cov_report/index.html
FYI @sriyerg @senelson7

@weicaiyang sure - I will do this first thing Monday morning as everyone in WD will need these

@weicaiyang the issue is the [6] is not escaped - but for some reason I cannot get it to escape it correctly
which causes the following exclusions to be ignored.
I tried really fast to exclude it, but then I get a signal cannot be found issue.
I will look close monday.

@weicaiyang the issue is the [6] is not escaped - but for some reason I cannot get it to escape it correctly which causes the following exclusions to be ignored.
I tried really fast to exclude it, but then I get a signal cannot be found issue. I will look close monday.

Thanks for looking into this.
rsp_intg[6] is truly unreachable. If we can't exclude it in a common file, we can rely on the exclusion from UNR.
It will be nice if we can exclude *alert_rx_*.ping_* in common exclusion, otherwise, we have to manually add it in each IP.

@weicaiyang  I have reached out to cadence for the rsp_intg[6].
the others work fine if we remove the failing ones.
I will create a PR to update once I hear back from Cadence

@weicaiyang update
I know have Cadence trying to reproduce this, as their solutions does not work:
I expect to hear more by tomorrow

@weicaiyang update I know have Cadence trying to reproduce this, as their solutions does not work: I expect to hear more by tomorrow

sounds good. Thanks for the update.

@weicai so I figured it out .
for some weird reason the [6] needs to go outside the the ''


ItemList text threshold for truncating with ellispis (...) may need changing

Tested versions
4.3
System information
Windows 10
Issue description
In an ItemList, names are truncated if they are too wide for the list. Usually this is done with an ellipsis ..., but when the width is small enough, no ellipsis is used, so more of the original name is preserved. This is good behavior, otherwise a label like new_script.gd, truncated to 5 characters, would appear as ne... rather than new_s.
There is some threshold for when truncation stops using ellipses. Possibly this threshold should be changed, so that ellipsis truncation is used for more narrow controls than it currently is.
The exact logic may also need tweaking. In this example, the list item named wwwwwwwwwwwwww is truncated without an ellipsis, even though visually it has room for an ellipsis.
Observed behavior in the MRP:
https://github.com/user-attachments/assets/74bc973d-7544-4236-97bb-af7895c3864b
Context:
I first noticed this behavior when testing https://github.com/godotengine/godot/pull/96909. That PR changed the minimum width of the script list to 100, and now the width is small enough that many script names are truncated with no ellipsis.
Observed behavior in the https://github.com/godotengine/godot/pull/96909 artifact. Not how new_script.cs file is truncated without ellipsis.
https://github.com/user-attachments/assets/de277fb5-d98e-4320-a506-41a2ff36f1ad
Steps to reproduce
Open the MRP.
Adjust the HSplitContainer left and right. You can test with and without 16x16 icons.
Observe that at a certain width, some labels are truncated using an ellipsis and some are not.
Minimal reproduction project (MRP)
mrp-truncation.zip

It seems that this behavior isn't unique to ItemList, but in general any TextParagraph with text_overrun_behavior = OVERRUN_TRIM_ELLIPSIS
Here's demonstration with Label:

Note how there's a brief moment when "new_s" is shown, there would be space enough for either one letter or ellipses.


Window Control Overlay: Question from Citrix about inflexible content

Citrix recently posed a question regarding the Window Control Overlay proposal.
The scenario they're considering is when a remote native application window is rendered locally in a PWA window. There's an obvious benefit to maximizing the content area, to avoid showing a local standalone window titlebar with the remote native application titlebar below, so the Window Control Overlay proposal is compelling in that regard.
A question arises about how to support cases where elements of the underlying inflexible native content are covered by the overlay. For example, if a Microsoft Word window shows UI elements immediately to the left of the minimize button, these would be covered by the three-dot menu button and the draggable area of the overlay (plus the origin at times).
Has there been any thought around supporting this case? My naive thoughts:

Could the overlay be user-draggable, or perhaps temporarily hidden by the user?
Could the user or application toggle back into a standalone mode temporarily?
How could runtime changes to the presence/placement/size of the overlay be relayed to the site?

Thank you (also on behalf of Citrix) for any consideration here.

Thanks for sharing the feedback from Citrix
According to the current proposal, that scenario wouldn't be well supported, but there are a couple of options:

The web app can query for the size of the overlay using JS or CSS environment variables, so it could implement a control that would toggle between filling the entire client area with the "remote native application window" and shifting the web content below the overlay temporarily, allowing the user to reach all points on the remote window. This would be similar to using the -safe-area-inset-top CSS environment variable to shift the web content below a phone notch.
Another alternative would be to just use a normal standalone display mode, and encouraging users to use F11 to fullscreen the app. Unfortunately, this wouldn't work with snapping windows to left/right if that was a desired scenario.

With respect to your suggestions:

Could the overlay be user-draggable, or perhaps temporarily hidden by the user?

I would expect this to be even more of a security concern than the existing proposal already poses, so I don't think this one would work out.

Could the user or application toggle back into a standalone mode temporarily?

We posed this as an option in the Privacy and Security review doc. Since we already have to support falling back to the standalone title bar when navigating out of scope, this would be fairly straightforward to implement.

How could runtime changes to the presence/placement/size of the overlay be relayed to the site?

These will be exposed via a new JS API: navigator.windowControlsOverlay.getBoundingClientRect() and CSS environment variables

Okay, the site (temporarily) shifting content down itself and possibly supporting a toggle back to standalone mode makes sense. I also like the comparison to handling a phone notch.
I'll make sure we share this feedback.