Fix warning output in build_with_symlink_to_path_dependency_with_build_script_in_git

The test build_with_symlink_to_path_dependency_with_build_script_in_git was emitting a large warning block (in my case, about init.defaultBranch) because it was running git without filtering its output. It's not clear to me why this test was shelling out to git instead of using the built-in test support functions. From what I can tell, this should be exactly equivalent, and silences the warning output.

@bors try

:hourglass: Trying commit 2e9dcdbdf5a4a5880c30867fdbbfbef21eab56a4 with merge e41007f0bbe9bb30b22e0e7553e91a99f777af8d...

:sunny: Try build successful - checks-actions
Build commit: e41007f0bbe9bb30b22e0e7553e91a99f777af8d (e41007f0bbe9bb30b22e0e7553e91a99f777af8d)

@bors r+

:pushpin: Commit 2e9dcdbdf5a4a5880c30867fdbbfbef21eab56a4 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 2e9dcdbdf5a4a5880c30867fdbbfbef21eab56a4 with merge 0f685f6198ed17afbbf5b8ced4c360fdf840c3ac...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 0f685f6198ed17afbbf5b8ced4c360fdf840c3ac to master...


Add link to dotnet project

Hi Alir3z4,
I've created a dotnet implementation of your stop words list.
Maybe you want to link it here.

Excellent.
Thanks for adding.
I will merge right away.


Jumping scroll bar on 2 lists in one window using WindowScroller

Hi,
AMAZING work on this package.
One issue I am seeing while implementing multiple lists that are using WindowScroller is that the scroll bar jumps as the browser reaches the bottom of the first list.
Here is an example:
https://codesandbox.io/s/jnpwvq5623

Thank you, Zohar. 😄
Unless I'm misunderstanding the scrollbar thing you mention, that's just the way the browser works. When momentum scrolling is active and one scrollable thing reaches its end (eg your List), the event bubbles up to the next scrollable thing (eg the body).
I don't think I can/should change that behavior in react-virtualized. You can fix it in your example app though by adding the following style to the outer container:
overflow-y: hidden;


VHLK download links are missing from docs..

The download links for VHLK are missing here:
https://docs.microsoft.com/en-us/windows-hardware/test/hlk/
Where are the download links?

@LusKrew - Thanks for reporting this. We are investigating this broken link.

@LusKrew - The links have been updated and should once again work as expected. Thanks again for reporting this issue!


'Finder" doesn't work anymore.

Describe the bug
Nothing happens when using 'Finder'.
Steps to reproduce
active 'Finder' on some code.
Expected behavior
expect to see a window popup with references/implementations etc.
Neovim version (nvim -v)
latest
lspsaga commit
latest
Terminal name/version
kitty latest

I can't reproduce. provide more info.

could you provide a code snippet ? which language

After latest changes, I don't seem to experience any issues.
P.s. can you please stop closing issues when they are not fixed? Or no conclusions are made?

because i need reproduce step.

I'm also seeing this, @Delice0 did you ever figure this out? @glepnir what debug steps should I perform to help debug this?  E.g. when I open :Lspsaga finder, I see the loading dots, and then get this empty floating window:

I haven't found a solution for this issue therefor I've deleted the plugin and went with Aerial mainly because of the neat outline functionality.

Whoa good recommendation @Delice0 ! The outline and floating term, along with this finder window were the only parts of lspsaga that I was using. With the outline replaced, now I can finally replac the terminal with fterm.nvim, the outline with aerial.nvim, and the finder with telescope lsp references!

I also reproduced the bug where :Lspsaga finder does not display information in the following environment:

NVIM v0.10.0-dev-772+g0211f889b-Homebrew
Build type: Release
LuaJIT 2.1.0-beta3

Upon checking the operation with each commit, it was found that this commit (https://github.com/nvimdev/lspsaga.nvim/commit/dc5d7f7390569219a88a21cb46eff399e0ac0d90) is the cause. For now, I resolved the issue by specifying the commit right before it (db74412e0282505ea1e63a42060728fb74c1968e).
I don't have time to fix it right now, so I'm just sharing the information for now.


remove date question

Needs to be checked before merging, have not been able to run it locally yet.

Fixes #16 and #17


cross-env with git tag

cross-env version: ^5.2.0
node version: 10.15.0
npm (or yarn) version: 6.4.1

Relevant code or config
"make": "cross-env APP_ENV=production cross-env APP_VERSION=`git tag --points-at HEAD` cross-env APP_COMMIT=`git rev-parse HEAD` webpack --config webpack.config.js"

What you did:
When using above code in package.json and running it as npm run-script make
What happened:

Gives below error.

Reproduction repository:

Problem description:
Suggested solution:

The common patterns seems to be crossenv [declaration] [command] where your command would be another crossenv.
Have you tried an explicit end at the end of each command?
cross-env APP_ENV=production; cross-env APP_VERSION=`git tag --points-at HEAD`; cross-env APP_COMMIT=`git rev-parse HEAD` webpack --config webpack.config.js

Not sure if that will carry on the variables though.
I thought this may be the solution:
"make": "cross-env-shell \"APP_ENV=production cross-env APP_VERSION=`git tag --points-at HEAD` cross-env APP_COMMIT=`git rev-parse HEAD` webpack --config webpack.config.js\"",

What is the minimal command to reproduce this?
Does this work?
"make": "cross-env APP_VERSION=`git tag --points-at HEAD` echo $APP_VERSION`

@jaller94, I was able to fix this by you using something like
 "make": "cross-env APP_ENV=production cross-env APP_VERSION=\"git tag --points-at HEAD\" cross-env APP_COMMIT=\"git rev-parse HEAD\" webpack --config webpack.config.js"


Adds support for partials

Partials are SCSS files that are only compiled when imported using @import.
Compared to regular SCSS files partials start with _.
In the @import statement however the _ can be omitted.

@matthewdavidson Do you accept pull requests? ^^


Remove redundant list brackets

PR o'clock
Description
As per the Terraform 0.12 upgrade guide, list variables no longer need to be surrounded with list brackets. See here for more info: https://www.terraform.io/upgrade-guides/0-12.html#referring-to-list-variables.
I believe this breaks the API for anyone using Terraform 0.11, so I have incremented the version from 3.5.0 to 4.0.0.
Couldn't get tests working with TF 0.12. Running tight on time, but hopefully this might get the momentum going.
Checklist

[x] terraform fmt and terraform validate both work from the root and examples/alb_test_fixture directories (look in CI for an example)
[ ] Tests for the changes have been added and passing (for bug fixes/features)
[ ] Test results are pasted in this PR (in lieu of CI)
[x] Docs have been added/updated (for bug fixes/features)
[x] Any breaking changes are noted in the description above

This is fixed in v4.0.0.
Terraform 0.12 users can use v4.0.0 of this module which has been just released.


Read json from the bagit package.

We've got rid of the three CSV files and replaced it with a single bagit
json. This change reads from that file and writes it to Dynamo.
It's more or less a copy of the json in the bagit package into Dynamo.
We're calculating the parent path from the ID and adding in the
checksums from the bag metadata and the file extensions and adding them
to the dynamo json.
This is all done with json objects and string keys. It's a bit fiddly
but as there'll be fields that we won't know in advance, we can't use a
case class.

There is a test for "Cannot find asset with citeable reference" https://github.com/nationalarchives/dr2-ingest-mapper/blob/DR2-1209-read-flat-json-from-bagit/src/test/scala/uk/gov/nationalarchives/DiscoveryServiceTest.scala#L98
I've added in the html codes into the test data for DiscoveryServiceTest.
I've added some backslashes into the test data as well to cover that.


Move the chocolatey config directly into this repo

Describe the Enhancement:
Move the chocolatey config to this repo and handle promotions of those packages just like any other package.
Describe the Need:
We want to make sure as soon as we promote Chef Infra Client that we publish the new version to chocolatey.org without a person having to do it by hand. It's basically the only by hand action in the Chef release at this point other than the overall announcement and only a few people even have permission to do it.

Another option for automated choco publishing could be to wire up https://github.com/chef/chocolatey-packages with expeditor subscriptions to omnibus packages getting promoted to stable to trigger expeditor performing a scripted update to the files there and having that repo do the publish. I haven't thought deeply yet about the trade-offs between these two options, though.

🤔 🤔 🤔 🤔
Though, as you said, there's something to be said for chef/chef owning the destiny of all its artifacts.

Nope. Chocolatey packages are still produced and pushed manually for this repo.

@tas50 anything that we can do to help with this?

It's all kinda on our side. We were doing workstation first and that kept blowing up for a number of different reasons. I think now it's just the large package size, which it sounds like we just have to live with. Setting up the same automation on this repo is just a matter of priority.

The larger package size, and the need for manual exemption is something that we want to get fixed, just need to get to that. In the interim, you can pre-upload the binaries to virus total which would help with the package scanner process.

Replacing with https://chefio.atlassian.net/browse/IPACK-68


Change resources

Closes #266

This could possibly be expanded to include all configuration of the Vagrantfile. Do we want that or not? I'm asking because we do force a pattern by having the ansible_local provider, which is what we want. Giving everyone the "option" to do whatever they want in the Vagrantfile might cause all sorts of weird uses.

Don't forget squash rebase, due to commits' messages are non-descriptive

Yup


Could we contribute bitmap-function into hive project?

https://issues.apache.org/jira/browse/HIVE-28528
If Hive has built-in bitmap-functions, users of Spark/Hive can use bitmap-functions very conveniently.

Of course. I'm quite willing to

@lihuigang Good! I think it would be more appropriate for you to submit the code to the HIVE community. If you need any help from me, please let me know at any time.

@BsoBird OK, no problem.


Update the FAQ to talk about consuming a JSON query string value

See also: https://github.com/falconry/falcon/issues/1020

Hey @kgriffs, I'm a fan of the framework and would love to help out, thought I might be able to get my toes wet by doing some documentation -- would it be helpful if I sent you a PR for this?

Hi @santeyio, thanks for contributing! This looks like a great addition to the FAQ. 👍

Fixed by #1111


Avoid calling toString() on alluxio.grpc.WriteRequest

Alluxio Version:
2.2.1
Describe the bug
A write request object contains all the data (MB or more) of data that is intended to be sent to a worker. On errors, its common for the failure to be logged, but on failures this entire grpc object is logged. The object itself prints out the entire buffer it intended to write. Not only is seeing that data not helpful; it spams the logs with multiple MB of useless junk, makes it harder for logs to parse, and may cause a leak of secure information (especially if dealing with PII), and/or
To Reproduce

Create a worker with a small total storage volume (a few MB).

alluxio.worker.memory.size=16MB

Write files taking up more than that space

./bin/alluxio runClass alluxio.cli.RunOperation -op CreateFile -s 8000000 -n 10 -t 10

Expected behavior
Failures should be logged more concisely and be easily readable.
Urgency
medium

@gpang did your recent PR fix this?

switch to netty might solve this


Add nextJSTypescriptTemplate

Hi @microhobby ,
i just prefered to create a new pull request instead of continuing the @escherstair one.
I decide to create the template for NextJS starting from the 'old' pages structure and not the 'new' src directory. It can be easily changed in case.
I tested the created container and runs with no problem on my module. I didn't test the Dockerfile.debug but I take it from the previous PR from @escherstair, so, should be fine.
I could miss something more related to torizonCore since I focus on the NextJS part, feel free to test scripts etc.

hey, @dellorogiulio thanks for the contribution. I did a rebase taking as a reference the dev branch which should be the branch to include new templates.
Let me ask, are you guys not using a docker-compose.yml file?

Currently we are using no docker-compose, but I think that this should be fine
version: "3.9"
services:
  __container__-debug:
    build:
      context: .
      dockerfile: Dockerfile.debug
    image: ${LOCAL_REGISTRY}:5002/__container__-debug:${TAG}
    ports:
      - 2229:2229
      - 9229:9229
      - 9230:9230
      - 9231:9231

  __container__:
    build:
      context: .
      dockerfile: Dockerfile
    image: ${DOCKER_LOGIN}__container__:${TAG}
    ports:
      - 3000:3000

Hey @dellorogiulio I was testing here and trying to attach to the debugger but seems that something has been crashed on the Next JS side: https://github.com/vercel/next.js/issues/55862
So, I will wait until they fix this.

Hi @microhobby
they should have fixed with this PR (already merged)

Next.js team worked on this issue and now it seems that this PR fixed it.
It's in the canary branch and I think it will be included in the upcoming v14.0.5 release

Hi @microhobby
Next.js v14.1.0 has been released and it includes the fix.
Can you verify if now the Next.js Typescript Template works?

Hey @escherstair we are in the process to release in this weekend a new version. I'm putting this to be reviewed in the next dev cycle. Thanks to point!

Hi @microhobby
do you have news on the merge of this PR?
Thanks

Hi @microhobby thank you...
Sad to see that this feature is btoken again


WebView2 is blank if other applications like e.g. Inkscape are running

Describe the bug
When other applications are running that lock the ApplicationFolder any WebView2 will remain blank. The issue is most likely related to https://github.com/microsoft/microsoft-ui-xaml/issues/4725#issue-849401247. I guess a workaround would be redirecting the cache folder of the webview to the local folder of the application. This would require access to  CoreWebView2Environment. To my current knowledge, this functionality is not yet supported for WinUI 3.0.
See also https://stackoverflow.com/questions/62470733/set-cache-directory-for-webview2, https://github.com/microsoft/microsoft-ui-xaml/issues/4066#issue-797469733, and https://github.com/MicrosoftEdge/WebView2Feedback/issues/297.
Is there any other workaround to avoid the issue with WinUI Reunion 0.5?
As I cannot know what application a user is using there is a chance that the WebView2 parts of the WinUI application do not work correctly which results in bad UX.
onecoreuap\base\appmodel\statemanager\winrt\lib\windows.storage.applicationdata.server.cpp(935)\Windows.Storage.ApplicationData.dll!00007FFE57AEA159: (caller: 00007FFE57AFCDDD) ReturnHr(2) tid(1c5c) 80070057 The parameter is incorrect.
    Msg:[SHCreateItemFromParsingName C:\Users\XXXXXX\AppData\Local\Packages\Microsoft.XAMLControlsGallery.Desktop.WinUI3Prev_8wekyb3d8bbwe\LocalState]
onecoreuap\base\appmodel\statemanager\winrt\lib\windows.storage.applicationdata.server.cpp(948)\Windows.Storage.ApplicationData.dll!00007FFE57AFCE28: (caller: 00007FFE57AE9C0B) ReturnHr(3) tid(1c5c) 80070057 The parameter is incorrect.
    Msg:[Package Microsoft.XAMLControlsGallery.Desktop.WinUI3Prev_8wekyb3d8bbwe 1]
onecoreuap\base\appmodel\statemanager\winrt\lib\windows.storage.applicationdata.server.cpp(878)\Windows.Storage.ApplicationData.dll!00007FFE57AE9C85: (caller: 00007FFE57AE19EA) ReturnHr(4) tid(1c5c) 80070057 The parameter is incorrect.
    Msg:[InternalGetRootStorageFolderFullTrustCaller Microsoft.XAMLControlsGallery.Desktop.WinUI3Prev_8wekyb3d8bbwe]
Exception thrown at 0x00007FFE92C74B59 (KernelBase.dll) in XamlControlsGallery.DesktopWap.exe: WinRT originate error - 0x80070057 : 'Error trying to initialize application data storage folder'.
onecore\com\combase\winrt\error\restrictederror.cpp(1016)\combase.dll!00007FFE9413C073: (caller: 00007FFE94145D49) ReturnHr(2) tid(1c5c) 8007007E The specified module could not be found.
onecoreuap\base\appmodel\statemanager\winrt\lib\windows.storage.applicationdata.server.cpp(893)\Windows.Storage.ApplicationData.dll!00007FFE57AE1AEC: (caller: 00007FFDF6EEA34A) ReturnHr(5) tid(1c5c) 80070057 The parameter is incorrect.
    Msg:[Locality 0 1]
onecoreuap\base\appmodel\statemanager\winrt\lib\windows.storage.applicationdata.server.cpp(588)\Windows.Storage.ApplicationData.dll!00007FFE57AE1B11: (caller: 00007FFDF6EEA34A) ReturnHr(6) tid(1c5c) 80070057 The parameter is incorrect.
    Msg:[InternalGetRootStorageFolder LOCAL]
'XamlControlsGallery.DesktopWap.exe' (Win32): Unloaded 'C:\Program Files (x86)\Microsoft\EdgeWebView\Application\89.0.774.75\EBWebView\x64\EmbeddedBrowserWebView.dll'
Exception thrown at 0x00007FFE92C74B59 in XamlControlsGallery.DesktopWap.exe: Microsoft C++ exception: winrt::hresult_invalid_argument at memory location 0x000000CD33176A40.
Exception thrown at 0x00007FFE92C74B59 in XamlControlsGallery.DesktopWap.exe: Microsoft C++ exception: winrt::hresult_invalid_argument at memory location 0x000000CD331745F0.
Exception thrown at 0x00007FFE92C74B59 in XamlControlsGallery.DesktopWap.exe: Microsoft C++ exception: winrt::hresult_invalid_argument at memory location 0x000000CD33176A70.
Exception thrown at 0x00007FFE92C74B59 in XamlControlsGallery.DesktopWap.exe: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.
(null)!00007FFE45A05E22: ReturnHr(1) tid(1c5c) 80070057 The parameter is incorrect.
    Msg:[winrt::hresult_error: Error trying to initialize application data storage folder]
Exception thrown at 0x00007FFE92C74B59 in XamlControlsGallery.DesktopWap.exe: Microsoft C++ exception: winrt::hresult_invalid_argument at memory location 0x000000CD33176C20.
'XamlControlsGallery.DesktopWap.exe' (Win32): Loaded 'C:\_work\github\Xaml-Controls-Gallery\XamlControlsGallery\bin\XamlControlsGallery.DesktopWap.Package\XamlControlsGallery.DesktopWap.Package\AppX\XamlControlsGallery.DesktopWap\ColorCode.Core.dll'.

Steps to reproduce the bug

Use WinUI Xaml Controls Gallery with branch winui3preview -> Reunion 0.5 prerelease
Run x64 Debug version -> WebView2 content visible
Start Inkscape
Run x64 Debug version -> WebView content not visible anymore

Expected behavior

WebView2 can be used on WinUI 3.0 without side effects caused by other programs

Screenshots
Without Inkscape running:

With Inkscape running

Version Info
NuGet package version:
[WinUI 3 - Project Reunion 0.5 Preview: 0.5.0-prerelease]
Windows app type:

UWP
Win32

Yes

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

October 2020 Update (19042)
Yes

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Additional context

potentially related: https://github.com/microsoft/microsoft-ui-xaml/issues/4725

@codendone and @anawishnoff FYI

I know some time has passed and I can this issue is still open, but the exact same behaviour occurs with GIMP as well as Inkscape. I have replicated it with the Win UI 3 Controls Gallery app version <IP_ADDRESS>.

Just wondering if there has been any update with this? WebView2 just doesn't work at all when you have GIMP or Inkscape open (possible GTK clash?).

Same behavior when running new Microsoft Teams at the same time.


gitlet: add support of -v, --version

Read version from package.json and show it when get flag -v or --version.

Thanks a lot for submitting this.  I'm sorry, but I'm afraid I'm not going to merge.  The goal of Gitlet is to demonstrate how Git works, not implement all of its API.  Displaying the Gitlet version doesn't explain anything about the fundamental properties of Git.
Sorry again, and thanks a lot for taking the time to submit the PR.


Domain name for email of add  supplier command allows missing period to be added

add -s n/John Doe p/98765432 e/johnd@example com/companyA t/friends t/owesMoney pro/rice pro/bread is accepted
when johnd@example is likely an invalid email

Look at #150

Look at #150


Auto redirected to not found page

When i have built my website and i change my route in the url i get redirected to a not found page.
Example:
My domain is test.com and when i tap a button i get to test.com/newpage. But when i type this url directly into my browser i get to url not found.
Any help is appreciated :)

After futher investigation i found out that this happens when i set a url strategy. Please fix this :)

Hi @Jens05,
Did you try this?


ENH: stats.percentileofscore: 2D array input should be fixed or forbidden

Is your feature request related to a problem? Please describe.
percentileofscore is documented to operate on 1D arrays. If one uses a 2D array for the a parameter, bizarre behavior happens.
import scipy
import numpy as np

a = np.array([
    [1, 2, 3, 4, 5],
])
print(scipy.stats.percentileofscore(a, 5))
print(scipy.stats.percentileofscore(a.T, 5))

Output:
[500.]
[20. 20. 20. 20. 20.]

The first behavior does not make sense, because 500% is not a percentile. The second behavior does not make sense, because 5 ought to be at the 100% percentile, and I only provided one input, not five.
Describe the solution you'd like.
This function is documented to only accept 1D arrays. Ideally it would do something sensible, but if that's not possible, the next best thing would be to forbid 2D input to the a parameter to this function. (Would this need to be phased in with a deprecation?)
Describe alternatives you've considered.
It would be best if percentileofscore returned a sensible result in this situation. I am not sure what a sensible result is if the a parameter is 2D.
It may also be good to forbid 2D input to score, while we're here.
Additional context (e.g. screenshots, GIFs)
This originally occurred to a user on StackOverflow.

Also, documentation note:

score : array_like
Scores to compute percentiles for.

This is technically right?
We support calling this like stats.percentileofscore([1, 2, 3, 4], 3), and a float is an array_like in the sense that it can be converted into an array. I would like to see score : float or array_like to clarify that this function can be called with a scalar.

pcos : float
Percentile-position of score (0-100) relative to a.

The return value is either a float or an array, depending on whether score was a float or an array.

I think it should be possible to vectorize the function. Perhaps we can add axis to behave similarly to how it does in https://scipy.github.io/devdocs/reference/generated/scipy.stats.mode.html.
For integer axis, for a of rank n, score should be an array-like of length n . The result pcos is a float or ndarray of length n with the i-th element equal to the percentile rank of the i-th element of score relative to the i-th row of a along axis.
For axis=None, the input is ravelled and score must be an array-like of length 1.
Hopefully we could get away without a deprecation given that it currently returns nonsense for a of rank >1. I assume there is an error for score of length >1?

Hmm never mind, I just realised that one can already provide multiple scores to compute for the same list a. Perhaps axis can apply to both a and score simultaneously?

I would suggest just deprecating it for now unless someone is willing to do a deep dive into how these sorts of functions should be vectorized. This is another one of those like boxcox_llf where the core dimensionality of one argument is 1 and the core dimensionality of the other is 0. NumPy provides a precedent for this case, e.g. quantile, but it is not a good precedent because it is inflexible and doesn't follow standard broadcasting rules. I've discussed with @seberg about how these functions should behave, and I think we reached consensus, but there are no functions that currently do behave like this, so I can't just point to another one. I will follow up when I can find the issue in which this was discussed.

Disabling the bad behaviour for now sounds like a good idea.

FYI: NumPy gufuncs implement broadcasting of vectors and higher dimensional arrays in a standard way; see "Generalized universal function API".   This is what @mdhaber might have been referring to when he mentioned discussing this with @seberg.
The idea is that the function implements a core (or elementary) operation on arrays or scalars, and broadcasting is applied to the dimensions of the inputs that are not part of the core operation.
For percentileofscore (and considering just the first two parameters), the core operation takes a 1-d array a and a scalar score and returns a scalar (the percentile).  Shapewise, the signature for this core operation is describe with the notation (n),()->().  Broadcasting of the inputs would be applied to the shapes after removing the core dimensions from their shapes.   For example, given inputs a and score with shapes (5, 1000) and (10, 1), respectively, the first step is to remove the dimensions corresponding to the core operations, working from the right by default.  For a, the core dimension is n=1000, so the shape that takes part in broadcasting is (5,).  For score, the core shape is a scalar, so no dimension is removed from the input shape, and (10, 1) is used for broadcasting.  The broadcast shape of (5,) and (10, 1) is (10, 5), so that is the shape of the result.
One reason that gufuncs don't make it into public APIs very often is that--compared to the flexibility of the signature of a function defined with def--the gufunc signature is relatively primitive. Specifically, the core parameters are strictly positional only.  You can't pass them in with a keyword, and you can't provide a default value for any of them.  (One way to work around this is to provide a wrapper of the gufunc that provides a more flexible API.)
As a demonstration, I implemented percentileofscore as a gufunc in ufunclab.  I included the parameters a, score and kind, so the shape signature is (n),(),()->().  Because it is a gufunc, the API is not exactly the same as that of scipy.stats.percentileofscore.  In particular, I chose to implement kind as an integer parameter (effectively an enum) instead of a string, and I didn't include nan_policy (but it could be added).  You can see examples in the percentileofscore section of README.md at ufunclab.  The relevant part for this discussion is the demonstration of broadcasting; with a gufunc, all three parameters (including kind) take part in broadcasting in a standard way.  The simple case where both a and score are 1-d and kind is a scalar is an example of broadcasting:
In [27]: import numpy as np

In [28]: from ufunclab import percentileofscore, op

In [29]: percentileofscore([2, 3, 4, 5, 5, 5, 8, 10], [4.5, 5, 6], op.KIND_RANK)
Out[29]: array([37.5, 62.5, 75. ])

Here's an example of broadcasting all three parameters that I doubt anyone would ever need in practice:
In [32]: rng = np.random.default_rng(121263137472525314065)

In [33]: a = rng.integers(0, 20, size=(3, 100))

In [34]: score = np.array([[0], [1], [10], [12], [19]])

In [35]: kind = np.array([op.KIND_RANK, op.KIND_WEAK, op.KIND_STRICT, op.KIND_MEAN]).reshape((4, 1, 1))

a has shape (3, 100), score has shape (5, 1) and kind has shape (4, 1, 1).  percentileofscore has shape signature (n),(),()->(), so the broadcast result will have shape (4, 5, 3).
In [36]: result = percentileofscore(a, score, kind)

In [37]: result.shape
Out[37]: (4, 5, 3)

In [38]: result
Out[38]:
array([[[  4. ,   3.5,   1.5],
        [ 10.5,   9. ,   3.5],
        [ 54. ,  54. ,  49.5],
        [ 63. ,  63. ,  56.5],
        [ 99.5,  98.5,  96. ]],

       [[  7. ,   6. ,   2. ],
        [ 13. ,  11. ,   4. ],
        [ 56. ,  56. ,  51. ],
        [ 64. ,  64. ,  58. ],
        [100. , 100. , 100. ]],

       [[  0. ,   0. ,   0. ],
        [  7. ,   6. ,   2. ],
        [ 51. ,  51. ,  47. ],
        [ 61. ,  61. ,  54. ],
        [ 98. ,  96. ,  91. ]],

       [[  3.5,   3. ,   1. ],
        [ 10. ,   8.5,   3. ],
        [ 53.5,  53.5,  49. ],
        [ 62.5,  62.5,  56. ],
        [ 99. ,  98. ,  95.5]]])

Anyone interested in extending how SciPy functions handle broadcasting should become familiar with this convention, even if only to have common understandng  of "gufunc-style broadcasting", and not because everything should be converted to gufuncs!

@WarrenWeckesser Can you interpret the behavior of np.percentile according to those rules?

np.quantile and np.percentile don't actually broadcast their arguments.  After removing the axis dimension from the first argument, they perform the calculation on (effectively) the Cartesian product of the second and first arguments.  So if the inputs have shapes, say (p, q, r) and (m, n), and axis=1, the output shape is (m, n, p, r).  In your example, the inputs have shape (2, 10), and (2,). You want the output to have shape (2,), but that does not appear to be possible with a single function call.
With gufunc-style broadcasting, you get the desired behavior:
In [111]: from ufunclab import percentileofscore, op, vnorm

In [112]: a
Out[112]:
array([[ 8, 11,  5, 18,  0,  7, 18, 19, 14, 12],
       [11,  1, 10, 14, 14,  8, 14,  3,  4, 17]])

In [113]: percentileofscore(a, [18.5, 2], op.KIND_STRICT)
Out[113]: array([90., 10.])

In [114]: vnorm(a, [1, np.inf])
Out[114]: array([112.,  17.])

I included vnorm, a gufunc with shape signture (n),()->() that computes the vector norm, to show that it uses the same rules as percentileofscore.

np.quantile and np.percentile don't actually broadcast their arguments

Right, and that's the problem I was referring to with:

NumPy provides a precedent for this case, e.g. quantile/percentile and similar, but it is not an ideal precedent because it is inflexible and doesn't follow standard broadcasting rules.

Is this a different standard, or was this ad hoc?
 In that case, do you just make sure that the batch shapes are orthogonal? (That is, one batch shape is (2, 1) and the other is (1, 2).)
Thanks!

Is this a different standard, or was this ad hoc?

I suspect it is ad hoc.  I think these functions predate NEP 5, where gufuncs were first proposed.  @seberg or @mhvk might know more, but it is likely that the creation of the API for these predates their involvement in NumPy.

 In that case, do you just make sure that the batch shapes are orthogonal? (That is, one batch shape is (2, 1) and the other is (1, 2).)

Yes, exactly. In the following, the first argument of percentileofscore has shape (2, 10) and the second has shape (2, 1).  After removing the core dimension of the first shape, the remaining shape is (2,), and (2,) broadcast with (2, 1)  results in an output shape of (2, 2):
In [135]: a
Out[135]:
array([[ 8, 11,  5, 18,  0,  7, 18, 19, 14, 12],
       [11,  1, 10, 14, 14,  8, 14,  3,  4, 17]])

In [136]: percentileofscore(a, [[18.5], [2]], op.KIND_STRICT)
Out[136]:
array([[ 90., 100.],
       [ 10.,  10.]])

@WarrenWeckesser - Not really much to add to what you wrote, except perhaps to note that for things like kind, I'd tend to have a wrapper function that just calls different gufuncs rather than try to let the gufunc do all the work internally.
On this particular problem: it actually seems quite sensible to wrap the function in np.vectorize for multi-D - that way one gets more standard behaviour for relatively little effort (vectorize can deal with gufunc signatures).


Summer School Live Deployment Improvements

This PR targets pruning some parts of the pipeline to make open3d slam easier to use and more real-time applicable

checking

Now tested @nubertj , I think it can be used in the summer school. Let me know, if I should change anything

should we merge this to master? is tested in the summer school and seems to be working well.


Can this be deployed with multiple replicas?

The chart seems to suggest yes as it has a replicaCount setting, however the project also uses a levelDB which appears to be stored in a local file. Can that cause any issues, for example if a client obtains a token from instance A but then later uses that refresh token on instance B?
As this application will need to be up for any clients that have not yet logged in to pull or push anything deploying it twice seems necessary to prevent short outages.

I was thinking about the same but found this pull request still pending of being accepted:
https://github.com/cesanta/docker_auth/pull/374


issue with helmrelease upgrade

Hi! I have a problem with the helm release; I will try to update the release and get the next error:
Helm upgrade failed: error while running post render on files: accumulating resources:
accumulation err='accumulating resources from 'helm-output.yaml': may not add resource with an already registered
 id: RoleBinding.v1.rbac.authorization.k8s.io/strimzi-cluster-operator.kafka': must build at directory: '/helm-output.yaml':
  file is not directory

helm upgrade manually work fine:
helm upgrade -f ./kafka-operator.values kafka-kafka-operator  --version 0.27.1 --namespace kafka  strimzi/strimzi-kafka-operator
Release "kafka-kafka-operator" has been upgraded. Happy Helming!
NAME: kafka-kafka-operator
LAST DEPLOYED: Wed Dec 14 13:30:08 2022
NAMESPACE: kafka
STATUS: deployed
REVISION: 8
TEST SUITE: None
NOTES:
Thank you for installing strimzi-kafka-operator-0.27.1

To create a Kafka cluster refer to the following documentation.

https://strimzi.io/docs/operators/latest/using.html#deploying-cluster-operator-helm-chart-str

This typically means there is a duplicate resource in the rendered Helm template. Flux is more strict about this than Helm itself, as we use Kustomize to label resources originating from a chart using post rendering.
I would advise you to check the output of helm template [...] to see if there is a duplicate RoleBinding.


ps remote free optimization

Summary of this Pull Request (PR)
Remote free optimization.

replace locked linked list with lock-free stack
per NUMA node remote free list struct
each remote free list struct has one cache line containing multiple list headers. Thus, different NUMA node access different cache lines, while different cores in same NUMA node access different list headers.

Intent for your PR
Choose one (Mandatory):

[ ] This PR is for a code-review and is intended to get feedback, but not to be pulled yet.
[x] This PR is mature, and ready to be integrated into the repo.

Reviewers (Mandatory):
@phanikishoreg @gparmer
Code Quality
As part of this pull request, I've considered the following:
Style:

[x] Comments adhere to the Style Guide (SG)
[x] Spacing adhere's to the SG
[x] Naming adhere's to the SG
[x] All other aspects of the SG are adhered to, or exceptions are justified in this pull request
[ ] I have run the auto formatter on my code before submitting this PR (see doc/auto_formatter.md for instructions)

Code Craftsmanship:

[x] I've made an attempt to remove all redundant code
[x] I've considered ways in which my changes might impact existing code, and cleaned it up
[x] I've formatted the code in an effort to make it easier to read (proper error handling, function use, etc...)
[x] I've commented appropriately where code is tricky
[x] I agree that there is no "throw-away" code, and that code in this PR is of high quality

Testing
I've tested the code using the following test programs (provide list here):

list, ns, pgalloc, slab, smr

I will fix other issues as you suggested.

I updated this PR based on your useful comments. Please see the new added commits


Feat: Add Regex Support For Email Verifier

This PR adds regex matching for email body and headers.

This is a comment for future PR.
Although I don't a standard manner to defined proved programs for risc0, I think it is better to separate common functions as library functions that can be used in a third-party's proved programs, which is a similar design to templates of our circom circuits.

@SoraSuegami I understand your concern and yes I have thought of this.
The reason you don't see a library implementation of the core code is because the current ZkVM implementations have different crates supported for precompiles and hence it becomes difficult to manage the dependencies properly. Once the ZkVM implementations become a bit stable, I'm planning to do an abstraction where we just write the rust and different ZkVM implementations are built automatically.
Something like this - https://github.com/MatteoMer/any-zkvm


Phone number validation

Expected behavior
Just like Android setPhoneNumberValidityChangeListener, there should be a callback or delegate method
Actual behavior
There is no way to validate entered phone number
Steps to reproduce the problem.
Simple to enter any phone number but you will not notify on your ViewController
Specifications
I am using one which you suggested into Github

You can add a target on your UITexField and use .editingChanged as UIControlEvents:
textfield.addTarget(self, action: #selector(updateTextField), for: .editingChanged)
Like that changes will trigger updateTextField function.

Thanks for prompt response.
The challenge part is how i will know that entered phone number is valid or not, Did you get my concern? As we know that different countries supports different number of digits.
You are suggesting me to add a function on edit event of UITextField but that will not solve my issue.

For now, you can solve it with this workaround. And in the function target check phoneNumberTextField.getFormattedPhoneNumber(). If it returns the number so it's valid otherwise it returns nil.

Hi @mohdimran3pg I'm testing some improvements on improvement branch so you can try it and tell me if that resolves your issue.
Try to add CTKFlagPhoneNumberDelegate :)

A new pod version, 0.6.0, is available. It should resolve your issue.


DIN run_din.py执行失败

Please refer to the FAQ in doc and search for the related issues before you ask the question.
Describe the question(问题描述)
run DeepCTR-0.7.2/examples/run_din.py failed
Additional context
Traceback (most recent call last):
File "run_din.py", line 39, in
history = model.fit(x, y, verbose=1, epochs=10, validation_split=0.5)
File "/home/s/apps/CloudSearch/anaconda3/lib/python3.7/site-packages/tensorflow_core/python/keras/engine/training.py", line 819, in fit
use_multiprocessing=use_multiprocessing)
File "/home/s/apps/CloudSearch/anaconda3/lib/python3.7/site-packages/tensorflow_core/python/keras/engine/training_v2.py", line 235, in fit
use_multiprocessing=use_multiprocessing)
File "/home/s/apps/CloudSearch/anaconda3/lib/python3.7/site-packages/tensorflow_core/python/keras/engine/training_v2.py", line 533, in _process_training_inputs
adapter_cls = data_adapter.select_data_adapter(x, y)
File "/home/s/apps/CloudSearch/anaconda3/lib/python3.7/site-packages/tensorflow_core/python/keras/engine/data_adapter.py", line 998, in select_data_adapter
_type_name(x), _type_name(y)))
ValueError: Failed to find data adapter that can handle input: (<class 'dict'> containing {"<class 'str'>"} keys and {"<class 'numpy.ndarray'>"} values), (<class 'list'> containing values of types {"<class 'int'>"})
Operating environment(运行环境):

python version 3.7.4
tensorflow version 2.1.0
deepctr version 0.7.2

先用1.x版本试下，2.0可能有一些兼容性的问题

报错写得很清楚了，都要numpy.array格式，run_din.py里面，y = [1, 0, 1]改成y = np.array([1, 0, 1])


multiple minor fixes

This is a couple of minor fixes to handle the following:

Reformatting issues graph on Overview page #70
Search bar to dynamically take the first input #97
Listing orgs first in search bar outputs #105
changing start to home page #96

@JamesKunstle was this merged? I got an email but still see this open

@cdolfi It says that mypy failed- just check on your local branch that you pass everything and we'll see.

@JamesKunstle looks like its passed now, if it looks good to you, merge


monorepo-build.phar split does not work

ptomulik@barakus:$ vendor/bin/monorepo-builder.phar split

 [WARNING] Some of the tags on this repository don't have committer's date. This may lead to unwanted tag selection
           during split. You may want to use the "tag" parameter.

 ! [NOTE] Running: "" '--from-directory=packages/basiclib' '--to-repository=git@github.com:korowai/basiclib.git'
 !        '--branch=test-split' "" '--repository=/home/ptomulik/projects/korowai-framework/.git'

 ! [NOTE] Running: "" '--from-directory=packages/compatlib' '--to-repository=git@github.com:korowai/compatlib.git'
 !        '--branch=test-split' "" '--repository=/home/ptomulik/projects/korowai-framework/.git'

 ! [NOTE] Running: "" '--from-directory=packages/contextlib' '--to-repository=git@github.com:korowai/contextlib.git'
 !        '--branch=test-split' "" '--repository=/home/ptomulik/projects/korowai-framework/.git'

 ! [NOTE] Running: "" '--from-directory=packages/contracts' '--to-repository=git@github.com:korowai/contracts.git'
 !        '--branch=test-split' "" '--repository=/home/ptomulik/projects/korowai-framework/.git'

 ! [NOTE] Running: "" '--from-directory=packages/errorlib' '--to-repository=git@github.com:korowai/errorlib.git'
 !        '--branch=test-split' "" '--repository=/home/ptomulik/projects/korowai-framework/.git'

 ! [NOTE] Running: "" '--from-directory=packages/ldaplib' '--to-repository=git@github.com:korowai/ldaplib.git'
 !        '--branch=test-split' "" '--repository=/home/ptomulik/projects/korowai-framework/.git'

 ! [NOTE] Running: "" '--from-directory=packages/ldiflib' '--to-repository=git@github.com:korowai/ldiflib.git'
 !        '--branch=test-split' "" '--repository=/home/ptomulik/projects/korowai-framework/.git'

 ! [NOTE] Running: "" '--from-directory=packages/rfclib' '--to-repository=git@github.com:korowai/rfclib.git'
 !        '--branch=test-split' "" '--repository=/home/ptomulik/projects/korowai-framework/.git'

 ! [NOTE] Running: "" '--from-directory=packages/testing' '--to-repository=git@github.com:korowai/testing.git'
 !        '--branch=test-split' "" '--repository=/home/ptomulik/projects/korowai-framework/.git'

 [OK] Running 9 jobs in parallel

In PackageToRepositorySplitter.php line 104:

  Process failed with "127" code: "sh: linia 0: exec: : nie znaleziono
  "

split [--branch [BRANCH]] [--max-processes MAX-PROCESSES] [-t|--tag TAG]

The bug is probably related to this line. The PHP docs say clearly:

Note:

The function realpath() will not work for a file which is inside a Phar as such path would be a virtual path, not a real one.

This happens to monorepo-builder-prefixed 8.0.1.

Any idea how to fix it?

The problem seems even worse. If I hack the phar to not use realpath() and pass the path as is, then the Symfony\Process generates and tries to execute the following commandline:
exec 'phar:///home/ptomulik/projects/korowai-framework/bin/monorepo-builder.phar/packages/split/src/Process/../../bash/subsplit.sh' '--from-directory=packages/testing' '--to-repository=git@github.com:korowai/testing.git' '--branch=test-split' "" '--repository=/home/ptomulik/projects/korowai-framework/.git'

but the external exec command does not know the phar: protocol and simply fails with error
Process failed with "127" code: "sh: /tmp/monorepo_builder/_subsplit/packages-basiclib/phar:///home/ptomulik/projects/korowai-framework/bin/monorepo-builder.phar/packages/split/src/Process/../../bash/subsplit.sh: No such file or directory

The /tmp/monorepo_builder/_subsplit/packages-basiclib prefix is cwd.

One way is to detect that phar is running, then unpack the script to temporary directory and run in from there. Other way is to get rid of this bash script and implement the same as PHP module.

Which way do you suggest here?

Second. It's harder to implement, it's more portable (no phar detection needed, no script extraction, no need for bash).

Are you able to handle it in PR?

There is no other way to find an answer than trying :)

Haha... Do or do not. There is no try. Mr. Yoda
Great, I look forward to it :+1:

Yesterday I have spent some time looking at the current solution. It looks that it's based on git-subsplit, which is currently a git plugin (it adds "git subsplit" command, when installed appropriatelly). Wouldn't it be simpler to just require user to have the script installed for monorepo subsplit to work? We could then remove the bash/git-subsplit.sh and use git subsplit command instead.

We used this approach before, but it required install extra install of git sumbodule. That proved as very huge obstacle. Programmers are super lazy :laughing: And they should be, because that's makes the best software design.
Are you able to add this feature and make installation as sipmle as composer require ...?
If so, let's do this!

We used this approach before, but it required install extra install of git sumbodule. That proved as very huge UX obstacle. Programmers are super lazy laughing And they should be, because that's makes the best software design.

Expected this answer. ;)

Are you able to add this feature and make installation as sipmle as composer require ...?
If so, let's do this!

Not sure what this means. I don't think, adding git-sumbodule as a dependency for symplify project solves the problem. The issue is that we try to spawn a process which runs a script that is part of phar. Adding git subslit as a composer dependency for symplify will not make the script to magically appear outside of phar. Am I right?

Not sure what this means.

I mean that I'm open to adding new features, if the installation for the developers remains as simple as it is now: composer require symplify/monorepo-builder-prefixed.

The issue is that we try to spawn a process which runs a script that is part of phar. Adding git-subsplit as a composer dependency for symplify will not make the script to magically appear outside of phar. Am I right?

I have no idea, my knowledge is zero in this area. There were many frustrating bugs with git-subsplit so I moved away from it.

Closed with https://github.com/symplify/symplify/pull/2490
And https://github.com/TomasVotruba/github-action-monorepo-split


Setup

Initial setup of the new section in the dApp.
Finalising designs of deliverables. Signoff from the team.

json feels that the dashboard has some redundant metrics.
cut treasury balance, monthly income. Duplicated elsewhere.
Number of holders is good.
of open OIPs? Snapshot, taps, wallets active in governance. Forum uses https://flarum.org/
Equivalent of voter turnout.


Merge pull request #16 from aedelfrid/cardholder

Updated cardholder Page information.
Maybe this is why the cards don't appear as Neeraja coded them to be, missing this component?

It does look as if this has no new changes though, could someone double check before we merge?


Upgrade to java8

Set a minimum version of Java 8, use java.time instead of org.joda and javax.xml for parsing xsd:duration.

Why we should set a minimum version of java8? I know Java6 / Java7 are deprecated, but I think there are several environments using it, and since the toolkit is able to work on Java6 / Java7, why add that restriction?
That said, can you update on your PR the .travis.yml  file to use the Java8 environment?

Fair enough, for some reason I thought you were planning on going JDK8 after working out the PowerMock incompatibility issues. The advantages mostly boil down to simpler code due to:

being able to use the new SDK like java.time and
new language features  like lambdas and streams.

The downside is lowered compatibility with JDK versions past end of life (Java SE 7 End of Public Updates on April 2015).
Note that the toolkit is not currently usable on JDK6 because it outputs JDK7 bytecode. In general you can't safely cross-compile to a JDK version different to the one you build with (due to different standard libraries) so if you wish to target Java 6 you should also change the pom.xml and .travis.yml to require building with JDK6.

I'm not an expert on Java, that why I'm open to any suggestion and try to make the toolkit as most usable as possible.
My target is let the community to use the toolkit with Java6, java7 or Java8 meanwhile a reasonable amount of people keep using those version.  It seems that the usage of Java6 residual so our main target must be 7&8, but if we offer a backdoor to Java6 user, great!
P.S, it seems that 1 test failed:
Failed tests:   testParseDuration(com.onelogin.saml2.test.util.UtilsTest): expected:<1357243225> but was:<1357070425>

P.S, it seems that 1 test failed:

Thanks, I reintroduced the problem with parseDuration and DST when porting to java.time. It's fixed now.

Great, I will keep this PR open , and when we decide to stop supporting Java7 we can try merge it.


Incorrect Implementation

Weight matrices should be 2 ** depth - 1 not 2 * depth -1
ChatGPT clamping fix in CMM isn't unnecessary due to this correction
Einsum usage is very inefficient both in time and space for FFF

@ThomasPluck can you submit a pr pls


TimetableItemTag may partially disappear when the font size is large

Overview
As the title says, the tags disappear when the font size is large. Maybe using FlowRow is the way to go.

No problem
Problem

🙋


Feature request: hidden doc comments

Currently, cargo-snippet's output includes doc comments in all cases.
This is surely a good feature for some users, but there may be other users who want doc comments to be removed from output because of verboseness.
Therefore, it would be nice if we introduce a new syntax like this:
/// many
/// doc
/// comments
#[snippet(doc_hidden)]
fn foo() {
    // omitted
}

and when doc_hidden is applied, cargo-snippet doesn't output doc comments.
What do you think about this @hatoo? If there's no problem, I'll implement it this weekend.

Yeah, it's a good feature indeed.
Please implement it. 😄
Thank you!


can i send you the body of the email as well ?  I.e using node api you send what i request you to send but not the campaign in your system ?

As part of the sendinblue API version 2 deprecation plan this repository is no longer supported. Please refer to its updated version 3: https://github.com/sendinblue/APIv3-nodejs-library


ts: Convert user_groups module to TypeScript.

lgtm aside from the issue noted above.

I think you put those fixes that belong in the first commit in the second.

Yeah, sorry, that totally slipped through my mind. Fixed :(

I did the straightforward rebase and merged this, thanks @priyank-p!


Challenge Task list

Soon we're going to add programming challenges to the platform that automatically verify themselves.  A challenge will have a list of tasks for the user to follow. Example:
1. Fork repo {...}
2. Create a branch named {...}
3. etc

We're gonna need 2 components:

One for the individual task
One for the task list

The task component needs to have a couple of states:

DEFAULT
DONE_BY_USER -> the user marks it as done but we don't know yet if it passes the test.
VERIFYING -> the task is currently verified by our job. Will need to have a spiner
VERIFIED -> the task is correct. Let's have a green checkmark
ERROR -> the task is not correctly implemented. Need to show some info text regarding what's wrong

Partially done in https://github.com/FrontEnd-ro/frontend.ro/pull/145
Needs to be refined, but overall it's been implemented.


Remove MaxPermSize JVM option for the compatibility with Java 17

What does this PR do?
As a result of changes being made in https://github.com/DataDog/dd-sdk-android/pull/1406, Bitrise is now using Java 17, so need to remove unsupported JVM option.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1412 (c85f5e0) into feature/session-replay (d742612) will decrease coverage by 0.06%.
The diff coverage is n/a.

@@                    Coverage Diff                     @@
##           feature/session-replay    #1412      +/-   ##
==========================================================
- Coverage                   83.76%   83.70%   -0.06%
==========================================================
  Files                         399      399
  Lines                       13720    13720
  Branches                     2207     2207
==========================================================
- Hits                        11492    11484       -8
- Misses                       1565     1568       +3
- Partials                      663      668       +5

see 10 files with indirect coverage changes


For version <IP_ADDRESS>, the log grow very fast

As title. Any method to make the log level to ERROR?

Hi @chwong1,
/kafka-manager/conf folder contains various Kafka Manager configs. Log file config is amoung them. I suggest you to change log level to ERROR only for annoing packages.
Please, try to change log level on your own, and write about you progress here :)

@chwong1 Any progress you can share with rest of us? :)

Closing as inactive. Feel free to reopen, if you still need help :)


Availability

I'm lucky to have version <IP_ADDRESS> (installed in July 2021), is there any plan to reintroduce the extension to AMO?
https://addons.mozilla.org/addon/fact-layer/ is no longer available :-(

Hi Graham, yes I'm looking into getting it back up. It was removed by Mozilla due to "creating DOM nodes from HTML strings containing potentially unsanitized data, by assigning to innerHTML, jQuery.html, or through similar means." The data in question is coming from the fact layer json file so I don't really agree there's a security issue, but seems easier to just change the approach then to fight it :)

Just an update on this, I have an updated version of the plugin awaiting review at Mozilla. Hopefully they'll approve it.

Looks like they approved it!


fix(Dockerfile): Allow non-priviledged docker.

This fixes #289. One can configure
the http and the https ports via
operator settings. This config only
matters for the yaml generator. It
has no impact on the running
operator since this config is
given by kestrel.

Hey @tillig
What do you think about this w.r.t. #289 ?
Do we need the EXPOSE part in the docker file, or should it suffice as it is now?

As an example, this creates:
# Build the operator
FROM mcr.microsoft.com/dotnet/sdk:latest as build
WORKDIR /operator

COPY ./ ./
RUN dotnet publish -c Release -o out tests/KubeOps.TestOperator/KubeOps.TestOperator.csproj

# The runner for the application
FROM mcr.microsoft.com/dotnet/aspnet:latest as final

RUN addgroup k8s-operator && useradd -G k8s-operator operator-user

WORKDIR /operator
COPY --from=build /operator/out/ ./
RUN chown operator-user:k8s-operator -R .

USER operator-user

EXPOSE 5000
EXPOSE 5001
ENTRYPOINT [ "dotnet", "KubeOps.TestOperator.dll" ]

I think that looks pretty good. I don't think you need the EXPOSE - I think it just works without it. I don't have it in mine, either. Nice work!


paymentMethodNonceReceived callback doesn't get a new nonce after submitting and re-entering number

I'm using the following coffeescript setup code for the drop-in UI:
      braintree.setup client_token, 'dropin',
        container: 'braintree-dropin',
        paymentMethodNonceReceived: (event, nonce) ->
          console.log event, nonce

client_token is a valid Braintree client token that's not associated with a Braintree customer. In the sandbox, if I enter in valid credit card information and submit the form with the braintree-dropin, then enter a different credit card and submit the same form, the same nonce gets used both times, which would then be rejected when submitting it to the Braintree server the second time during a customer create/update.
Is there a way of making this work? We do duplicate card checking on our side, which means that a user then might need to enter in a different card on the same form after being rejected.

Hi @aripollak, since Drop-In was generally designed to be used once during the checkout / payment method update flow, I'm not sure if there's a way to use it twice. Would it be possible in your architecture to solve the problem by doing a full page reload?
Something hacky that might also work would be removing the #braintree-dropin element from your DOM, re-adding it, and calling braintree.setup again. I'd highly recommend the full page reload route, though.

We might end up needing to do a full page reload if this becomes a real problem, but currently we can't do that without more changes since reloading would lose the state of the current page.
I tried removing the dropin element and calling setup again, but the old event handlers still seem to be kept around, so submitting the form again ends up running the callback multiple times.

Ok :/ sorry for leading you down the wrong path. I've replicated this and I'll try to see if there is a way to run with it.

I'm experiencing the same problem, I would like to display success or error messages from payment process without reloading page, currently I receive "Cannot use a payment_method_nonce more than once." when trying to pay second time.
What we've end up doing is creating the form element and all children with JS and if payment was unsuccessful dumping it and recreating new one and start all over with braintree.setup. Maybe this helps you @aripollak.

We experienced the same problem and found that reloading the page was our only recourse.

Same problem.

definitely a problem... sigh

Thanks everyone for chiming in! We're currently working on allowing Drop-in to support being submitted more than once per initialization. We will update this thread when the fix is deployed.

+1

Same issue here.

Same issue. Is there a time frame for a fix?
Regarding the full page reload, is there a way to pre-populate the drop-in form with previously entered values?

Quite same issue.
I'm using the Drop-in UI.
If I use the<PHONE_NUMBER>111115 visa card for sandbox test problem, I am unable to get another nonce if I enter directly another valid credit card code (like<PHONE_NUMBER>111111) in a second time. The same nonce is always returned until I reload the page.
I'm working on a Single page application, so reloading it's not a solution for me.
I confirm that removing the dropin element does not remove the old event handler.
Do you know how can I manage a user credit card problem without reloading the page ?
Is there some kind of dropin reset process availlable somewhere ?

@baillyje, until Braintree offers this out of the box, you can try to reset the widget by following the steps described in this comment https://github.com/braintree/braintree-web/issues/29#issuecomment-103986438

@tnunes Thanks!

As of the recent 2.7.4 release you will receive a new nonce each time the user submits the form. This version has not been hotlinked yet but is available now via this repo, bower, and npm.

you will receive a new nonce each time the user submits the form

That's great. How does this interact with onPaymentMethodReceived callbacks? Will our submission of the form from the callback be affected?

@bkirkbri if you are subscribe to onPaymentMethodReceived the form will not be force-submitted by braintree.js after a nonce has been generated.

Will our submission of the form from the callback be affected?

Your submission should not be affected.

Yes, we add payload.nonce to a form field, confirm with the user and then call form.submit().

Ok, then yes, this will not affect that behavior. Let me know if you run into any issues.

Will this same thing work with hosted fields?

@talofo yes it will work the same way with Hosted Fields

I believe this problem has resurfaced or was not fixed in 3.3 ?
Using version 3.3 and the drop-in, a second submit on the form that holds the drop-in returns the previous nonce, even when payment details are different on second submit.
Shouldn't a new nonce be created automatically every time?

Same issue with the nonce used in 3D Secure:
        function threeDResponseReceived(error, response)
        {
            if (error) {
                alert(error.message);
            }
            else
            {
                insertNonceOnCheckoutForm(response.nonce);
            }
        }

        client.verify3DS(
              { amount: 100, creditCard: nonce },
              threeDResponseReceived
        );

Also says that nonce cannot be used twice

@RikdeBoer thanks. The "re-tokenization" of a card form seems valid in the scenario you describe. As with other advanced use cases, it is supported with Hosted Fields.
In the interest of maintaining API compatibility with current integrations, we do not intend to update Drop-in's behavior to support this card form re-tokenization use case.

Fair enough @burnto. Will take a closer look at Hosted Fields.


[Backport 2.x] Block a vector field to have invalid characters for a physical file n…

…ame.
Description
Issue : https://github.com/opensearch-project/k-NN/issues/1859.
Issue
While OpenSearch does allow for a field name to have an empty space within it and it disallows an empty space to be contained in a physical file name, KNNCodecUtil::buildEngineFileName uses the field name directly as a part of a vector file name. As a result, in case where the field name had one of disallowed character for a physical file name, it fails in validation of BlobStoreIndexShardSnapshot. For example, _0_2011_my vector.hnswc (where 'my vector' is the field name). As a result, BlobStoreIndexShardSnapshot throws an exception complaining file name is not valid.
Solution
Add a validation logic to throw an exception in case provided vector field name has any invalid characters.
private void validateFullFieldName(BuilderContext context) {
    final String fullFieldName = buildFullName(context);
    for (char ch : fullFieldName.toCharArray()) {
        if (Strings.INVALID_FILENAME_CHARS.contains(ch)) {
            throw new IllegalArgumentException(...);
        }
    }
}

public abstract class KNNVectorFieldMapper extends ParametrizedFieldMapper {
    ...
    public static class Builder extends ParametrizedFieldMapper.Builder {
        @Override
        public KNNVectorFieldMapper build(BuilderContext context) {
            validateFullFieldName(context);
            ...

Related Issues
Issue : https://github.com/opensearch-project/k-NN/issues/1859.
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] API changes companion pull request created.
[ ] Commits are signed per the DCO using --signoff.
[ ] Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Change log already had the bug fix #1936. I did not include it in this PR.

@0ctopus13prime I think we need to backport change log as well

@0ctopus13prime I think we need to backport change log as well

Hi @jmazanec15
Just wondering, does this have the line we need already..?? 🤔  - Link
Please let me know if I missed sth.


fix in galaxy scaling

I believe this will address the problem with galaxies looking different depending on the size of the ptile padding. It was the same issues with stars -- which I fixed earlier -- but I guess that fix didn't go through to galaxies.
For future reference, the "rule of thumb" to keep things scale-invariant to image size is to always pass in the a source (either a psf or a rendered galaxy) to ._render_one_source that is the same size as the padded tile (or whatever you're rendering the source on). If the original PSF or galaxy is too large, we should trim it; if it is too small, we pad it with zeros.
Before merging, maybe @ismael-mendoza can checkout this branch and see if it indeed fixes those example images that you showed before? And of course double check if the rendering of galaxies look reasonable to you.
Also, one of the galaxy sleep tests fail on this branch (I believe it is the assert on line 60 of test_sleep_galaxy). We get an accuracy on counts of 0.72, while the threshold is 0.75. Is this a major problem?

Hey @Runjing-Liu120 , thank you so much for this change, I produced some images in galaxies where you can clearly see your code is cropping and doing the right thing. Here are some examples:
(ptile_padding=3, tile_slen=4)

(ptile_padding=5, tile_slen=4)

As you can see galaxies appear the same size but appear more cropped in the first case.

For future reference, the "rule of thumb" to keep things scale-invariant to image size is to always pass in the a source (either a psf or a rendered galaxy) to ._render_one_source that is the same size as the padded tile (or whatever you're rendering the source on). If the original PSF or galaxy is too large, we should trim it; if it is too small, we pad it with zeros.

That makes sense, I'll keep this in mind going forward


review the patch for arm/power in MatriplexCommon.h

to follow up on the discussion in https://github.com/trackreco/cmssw/commit/7fc06ca5550ba6bad7e5fbbc0791f75c53e0ef8a

done in cms-sw/cmssw#37111


net: go 1.11 DNS client incompatible with SRV records from kube-dns

What version of Go are you using (go version)?
go1.11
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
linux amd64
What did you do?
Running the following application in Kubernetes exits with an error:
https://play.golang.org/p/EW5NVeHJMrV
What did you expect to see?
Expected to get SRV records back
What did you see instead?
When running in Kubernetes with kube-dns 1.14.10 the application exits with error: "cannot unmarshal DNS message" (underlying error is "Target: compressed name in SRV resource data")
https://play.golang.org/p/EW5NVeHJMrV
A pcap of the DNS request: https://github.com/jnewmano/kube-dns/blob/master/dns_111_2.pcap
When built with Go1.10, it behaves as expected.
Golang-nuts discussion https://groups.google.com/forum/#!searchin/golang-nuts/dns|sort:date/golang-nuts/vAbjprJNPV0/HSh9635hBQAJ

kube-dns 1.14.11 has now been tagged. This version works with go1.11
https://github.com/kubernetes/dns/releases/tag/1.14.11

I'm not sure if this is the same underlying issue, but SRV responses from systemd-resolved can't be parsed on ubuntu 18.04, and return the same error message (though I'm not sure how to get to the underlying error message, unfortunately). go test . within the net directory fails with the mentioned error. Disabling systemd-resolved and setting the DNS server to <IP_ADDRESS>, then running go test net passes, as expected.

This was an intentional change. See #10622.

For what it's worth, the reason I requested to file this issue is that I guess this could be a roadblock for operating DNS-SD in near future. Nowadays DNS-SD is becoming important not only for consumer plug-and-pray-or-play use but for label distribution over unicast DNS with k8s-like scheduler stuff. As described in RFC 8222, we still don't see the end of the label handling conflict between classical/conventional unicast DNS, and latest unicast and/or multicast DNS and DNS-SD, but need to find out a comprimise for both use cases.
One easy option would be just adding a control knob to net.Resolver and x/net/dnsmessge package without changing the current defaut, classical/conventional unicast DNS, behavior in the net package of standard library (see also #24870).

Doesn't the DNS client in the standard library only support unicast DNS? Multicast DNS is different in a number of ways. For example, I believe the way that it uses the truncated bit is incompatible with our DNS client.
SRV records in unicast DNS must not be compressed. DNS servers which compress SRV records are either broken or doing multicast DNS.

A line item in the go1.11 release notes and a control knob to continue permitting non compliant DNS SRV responses would have been sufficient for us to have a smooth upgrade to 1.11.

@jnewmano I agree that mentioning the DNS changes in the release notes would have been nice.

Doesn't the DNS client in the standard library only support unicast DNS?

Yup, basically we don't want to bring fancy and complicated features into the "built-in" DNS stub resolver in the net package, though, GODEBUG=netdns=cgo allows to use the external stub resolvers.

SRV records in unicast DNS must not be compressed.

For now, I agree with you, but won't ignore the https://tools.ietf.org/html/draft-ietf-dnssd-hybrid endeavor in near future.

I understand not wanting to bend to people's bad implementations and/or deviating from spec, but really, FFS, if it's an epidemic, which apparently it is, and especially because k8s is made in Go and it depends on srv records, you'd think the Go community would want to make things work.
It's not like our entire base of open source software isn't literally filled to the brim with hacks and workarounds.
 Make the resolver work again. It's been how long now that we've had no good solution?

It appears that this issue has been fixed on the kube-dns end. Does anyone know if this is still an issue?

@mikioh what do you think?

It's still an issue as long as the language != the ability of dig. That
should be the barometer. Everyone and their uncle is going to say "man, dig
works, but my software doesn't. WTF?"
On Sun, Aug 18, 2019, 3:46 PM Andrew Bonventre<EMAIL_ADDRESS>wrote:

@mikioh https://github.com/mikioh what do you think?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/27546?email_source=notifications&email_token=AACFHRHCDKKPCPSMM43MN23QFHGMJA5CNFSM4FTXNSL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4RKFZQ#issuecomment-522363622,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACFHRHYQZLG5WIZA4IIRYDQFHGMJANCNFSM4FTXNSLQ
.

I also think behavioral difference with dig should be taken into account


Dependency exclude rule on a both direct and transitive dependency is discarded

When a dependency of a project appears both as

direct dependency (written explicitly)
transitive dependency of another direct dependency

The only way to exclude any of the transitive dependencies of the directAndTransitive
dependency consists at putting a global exclude.
Expected Behavior
A local exclude in either the

directAndTransitiveDependency or
directDependency
filters the jar.

Current Behavior
The local exclude is discarded.
Context
This impacts our maven to gradle transition (maven has the expected behavior)
Steps to Reproduce (for bugs)
The following unit test reproduces the issue
https://github.com/gradle/gradle/compare/master...criteo-forks:discardedExcludeRule?expand=1

The problem is harder to fix than expected:

the exclude rules are applied while discovering dependencies.

https://github.com/gradle/gradle/blob/master/subprojects/dependency-management/src/main/java/org/gradle/api/internal/artifacts/ivyservice/resolveengine/graph/builder/DependencyGraphBuilder.java#L138
The exclude rule applied computed here
https://github.com/gradle/gradle/blob/master/subprojects/dependency-management/src/main/java/org/gradle/api/internal/artifacts/ivyservice/resolveengine/graph/builder/NodeState.java#L156
//direct -> directAndTransitive -> foo
dependencies {
    compile directAndTransitive
    compile(direct) {
       exclude foo
    }
}

To resolve the configuration compile, gradle browses:

directAndTransitive, without any exclude rule and thus adds foo to the configuration.
direct, adds directAndTransitive that is already added, and filters foo, without removing it from the configuration (he does not know it came from directAndTransitive)

I'm afraid the fix would require quite a risky refactoring,
i.e.

first create the dependency graph
2.a. add the jars to the configuration based on the filtering
2.b detect the duplicated/useless dependencies and aggregate exclude rules accordingly, and execute the existing algorithm.

What do you think @bmuschko @bigdaz @melix @jjohannes @oehme  (taking the names from git blame) ?

I'm pretty sure this is a duplicate of #1473, so I'm closing it in favour of that issue. Please see this comment to get an understanding of why this isn't going to be easy (or even possible) to fix.

It's indeed pretty close, however I think that the issue is a little bit different.
in
dependencies {
    compile directAndTransitive
    compile(direct) {
       exclude foo
    }
}

when visiting directAndTransitive, gradle does not have direct->directAndTransitive  in the
transitiveIncomingEdges
list
(it only has root->directAndTransitive)
https://github.com/gradle/gradle/blob/master/subprojects/dependency-management/src/main/java/org/gradle/api/internal/artifacts/ivyservice/resolveengine/graph/builder/NodeState.java#L142
Thus whether the union or intersection is applied does not affect the output (if I'm not mistaken this union/intersection is computed at
https://github.com/gradle/gradle/blob/master/subprojects/dependency-management/src/main/java/org/gradle/api/internal/artifacts/ivyservice/resolveengine/graph/builder/NodeState.java#L269
        ModuleExclusions moduleExclusions = resolveState.getModuleExclusions();
        ModuleExclusion nodeExclusions = moduleExclusions.excludeAny(metaData.getExcludes());
        if (incomingEdges.isEmpty()) {
            return nodeExclusions;
        }
        ModuleExclusion edgeExclusions = incomingEdges.get(0).getExclusions();
        for (int i = 1; i < incomingEdges.size(); i++) {
            EdgeState dependencyEdge = incomingEdges.get(i);
            edgeExclusions = moduleExclusions.union(edgeExclusions, dependencyEdge.getExclusions());
        }
        return moduleExclusions.intersect(edgeExclusions, nodeExclusions);
    }

In your example, there are 2 paths to foo:
root -> direct-and-transitive -> foo
root -> direct -> direct-and-transitive -> foo

Unless both of these paths exclude foo, then Gradle is going to include foo in the result. This is the same use case as described in #1473.
Note that this:
    runtime(directAndTransitive) {
        exclude foo
    }

does not mean "everywhere in the runtime graph that you see 'directAndTransitive', exclude 'foo'". It means "for this particular dependency on 'directAndTransitive', exclude 'foo'".
Using an exclude like this is telling Gradle that for this particular runtime usage of directAndTransitive,  foo is not required. But if there's another reason that directAndTransitive is required (because it's transitively required as part of the runtime classpath of direct), then Gradle will assume that foo is required.
If you want to globally exclude foo from your runtime classpath, then you don't add the exclude as an attribute of a particular dependency. Instead, you can define an exclude globally for the configuration, or you can use a "Component Metadata Rule" to modify the metadata of directAndTransitive so that foo is always excluded.

Thanks for your answers @bigdaz. In case there was a misunderstanding

Unless both of these paths exclude foo, then Gradle is going to include foo in the result. This is the same use case as described in #1473.

I was just trying to provide a second root cause on why in this particular case foo will be included:

root cause 1: the one you mentioned in #1473
root cause 2: the fact that directDependency is not in the transitiveIncoming list (I reproduce the bug by putting union instead of intersect too in getModuleResolutionFilter).

does not mean "everywhere in the runtime graph that you see 'directAndTransitive', exclude 'foo'". It means "for this particular dependency on 'directAndTransitive', exclude 'foo'". If you want to globally exclude foo from your runtime classpath, then you don't add the exclude as an attribute of a particular dependency. Instead, you can define an exclude globally for the configuration,

As suggested in the issue you linked, gradle and maven have different semantics regarding excludes. I opened the issue hoping that aligning the semantics would be reasonably easy, but I agree with you it is not :(
Our plan B (we're migrating a big maven project to a ~1000 multi project gradle build) consists at modifying our converter to put a global exclude in the configuration as you suggested.

or you can use a "Component Metadata Rule" to modify the metadata of directAndTransitive so that foo is always excluded.

Thanks for the tip!


[Topbar] Blocks Space and Enter key press events on the whole document

The TopbarMobileComponent blocks Space and Enter key press events on the whole document.
Issue Type
Bug Report

Component or Pattern Affected

TopbarMobileComponent
Expected Behavior

Space and Enter key presses should be recognized in other parts of the application.
Current Behavior

An example: spaces can't be introduced in any text input element.
Possible Solution

The HostListener handleKeydown is listening for keydown events on the whole document. I think the e.preventDefault() call is what is causing the issue.
Steps to Reproduce (for bugs)

Create a component with template as follows:

<md-top-bar-mobile></md-top-bar-mobile>
<input type="text">

Type some characters including spaces in the input box.

Context

Trying to include a responsive top bar in an application that contains forms.
Your Environment

Library: Angular
Version used: 9.2.8
Browser Name and version: Chrome 77, Firefox 69
Operating System and version: Windows 10, Ubuntu 19

Fixed by #414


Uncovered line for destructuring spread stmt with variable key

Issue :
Using jest --coverage on code that uses the destructuring spread statement with a variable key shows uncovered lines.
Example:
const myKey = 'a';
const myObj = { a: 1, b: 2, c: 3 };
const { [myKey]: value, ...rest } = myObj;

Output:
----------|----------|----------|----------|----------|-------------------|
File      |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line #s |
----------|----------|----------|----------|----------|-------------------|
All files |      100 |       50 |      100 |      100 |                   |
 index.ts |      100 |       50 |      100 |      100 |                 5 |
----------|----------|----------|----------|----------|-------------------|
Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        1.108s

If you replace [myKey] with a, it works without issues.
Expected behavior :
Should not show any uncovered lines.
Debug log:

log file content
# content of ts-jest.log :
{"context":{"logLevel":20,"namespace":"Importer","package":"ts-jest","version":"23.10.5"},"message":"creating Importer singleton","sequence":1,"time":"2019-02-15T10:45:57.304Z"}
{"context":{"allowJs":false,"logLevel":20,"namespace":"jest-preset","package":"ts-jest","version":"23.10.5"},"message":"creating jest presets not handling JavaScript files","sequence":2,"time":"2019-02-15T10:45:57.308Z"}
{"context":{"actualVersion":"23.6.0","expectedVersion":">=22 <24","logLevel":20,"namespace":"versions","package":"ts-jest","version":"23.10.5"},"message":"checking version of jest: OK","sequence":3,"time":"2019-02-15T10:45:57.311Z"}
{"context":{"baseOptions":{},"logLevel":20,"namespace":"jest-transformer","package":"ts-jest","transformerId":1,"version":"23.10.5"},"message":"created new transformer","sequence":4,"time":"2019-02-15T10:45:57.311Z"}
{"context":{"fileName":"/Users/cht/Code/ts-jest-spread-destucturing/src/index.test.ts","logLevel":20,"namespace":"jest-transformer","package":"ts-jest","transformOptions":{"instrument":false,"rootDir":"/Users/cht/Code/ts-jest-spread-destucturing"},"transformerId":1,"version":"23.10.5"},"message":"computing cache key for /Users/cht/Code/ts-jest-spread-destucturing/src/index.test.ts","sequence":5,"time":"2019-02-15T10:45:57.311Z"}
{"context":{"logLevel":30,"namespace":"jest-transformer","package":"ts-jest","transformerId":1,"version":"23.10.5"},"message":"no matching config-set found, creating a new one","sequence":6,"time":"2019-02-15T10:45:57.312Z"}
{"context":{"config":{"automock":false,"browser":false,"cache":true,"cacheDirectory":"/var/folders/f2/vfb1sb2d3gbchx8gh50r3jn40000gn/T/jest_dx","clearMocks":false,"coveragePathIgnorePatterns":["/node_modules/"],"cwd":"/Users/cht/Code/ts-jest-spread-destucturing","detectLeaks":false,"detectOpenHandles":false,"errorOnDeprecated":false,"filter":null,"forceCoverageMatch":[],"globals":{},"haste":{"providesModuleNodeModules":[]},"moduleDirectories":["node_modules"],"moduleFileExtensions":["ts","tsx","js","jsx","json","node"],"moduleNameMapper":{},"modulePathIgnorePatterns":[],"name":"6b503014a1c6361980aadc3e55a503e7","prettierPath":null,"resetMocks":false,"resetModules":false,"resolver":null,"restoreMocks":false,"rootDir":"/Users/cht/Code/ts-jest-spread-destucturing","roots":["/Users/cht/Code/ts-jest-spread-destucturing"],"runner":"jest-runner","setupFiles":[],"setupTestFrameworkScriptFile":null,"skipFilter":false,"snapshotSerializers":[],"testEnvironment":"jest-environment-jsdom","testEnvironmentOptions":{},"testLocationInResults":false,"testMatch":[],"testPathIgnorePatterns":["/node_modules/"],"testRegex":"(/__tests__/.*|(\\.|/)(test|spec))\\.(jsx?|tsx?)$","testRunner":"/Users/cht/Code/ts-jest-spread-destucturing/node_modules/jest-jasmine2/build/index.js","testURL":"http://localhost","timers":"real","transform":[["^.+\\.(j|t)sx?$","/Users/cht/Code/ts-jest-spread-destucturing/node_modules/ts-jest/dist/index.js"]],"transformIgnorePatterns":["/node_modules/"],"watchPathIgnorePatterns":[]},"logLevel":20,"namespace":"backports","package":"ts-jest","transformerId":1,"version":"23.10.5"},"message":"backporting config","sequence":7,"time":"2019-02-15T10:45:57.312Z"}
{"context":{"jestConfig":{"automock":false,"browser":false,"cache":true,"cacheDirectory":"/var/folders/f2/vfb1sb2d3gbchx8gh50r3jn40000gn/T/jest_dx","clearMocks":false,"coveragePathIgnorePatterns":["/node_modules/"],"cwd":"/Users/cht/Code/ts-jest-spread-destucturing","detectLeaks":false,"detectOpenHandles":false,"errorOnDeprecated":false,"filter":null,"forceCoverageMatch":[],"globals":{"ts-jest":{}},"haste":{"providesModuleNodeModules":[]},"moduleDirectories":["node_modules"],"moduleFileExtensions":["ts","tsx","js","jsx","json","node"],"moduleNameMapper":{},"modulePathIgnorePatterns":[],"name":"6b503014a1c6361980aadc3e55a503e7","prettierPath":null,"resetMocks":false,"resetModules":false,"resolver":null,"restoreMocks":false,"rootDir":"/Users/cht/Code/ts-jest-spread-destucturing","roots":["/Users/cht/Code/ts-jest-spread-destucturing"],"runner":"jest-runner","setupFiles":[],"setupTestFrameworkScriptFile":null,"skipFilter":false,"snapshotSerializers":[],"testEnvironment":"jest-environment-jsdom","testEnvironmentOptions":{},"testLocationInResults":false,"testMatch":[],"testPathIgnorePatterns":["/node_modules/"],"testRegex":"(/__tests__/.*|(\\.|/)(test|spec))\\.(jsx?|tsx?)$","testRunner":"/Users/cht/Code/ts-jest-spread-destucturing/node_modules/jest-jasmine2/build/index.js","testURL":"http://localhost","timers":"real","transform":[["^.+\\.(j|t)sx?$","/Users/cht/Code/ts-jest-spread-destucturing/node_modules/ts-jest/dist/index.js"]],"transformIgnorePatterns":["/node_modules/"],"watchPathIgnorePatterns":[]},"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"version":"23.10.5"},"message":"normalized jest config","sequence":8,"time":"2019-02-15T10:45:57.312Z"}
{"context":{"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"tsJestConfig":{"compiler":"typescript","diagnostics":{"ignoreCodes":[6059,18002,18003],"pretty":true,"throws":true},"isolatedModules":false,"transformers":[],"tsConfig":{"kind":"file"}},"version":"23.10.5"},"message":"normalized ts-jest config","sequence":9,"time":"2019-02-15T10:45:57.313Z"}
{"context":{"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"version":"23.10.5"},"message":"babel is disabled","sequence":10,"time":"2019-02-15T10:45:57.314Z"}
{"context":{"logLevel":20,"namespace":"Importer","package":"ts-jest","requireResult":{"exists":true,"given":"typescript","path":"/Users/cht/Code/ts-jest-spread-destucturing/node_modules/typescript/lib/typescript.js"},"version":"23.10.5"},"message":"loaded module typescript","sequence":11,"time":"2019-02-15T10:45:57.514Z"}
{"context":{"logLevel":20,"namespace":"Importer","package":"ts-jest","version":"23.10.5"},"message":"patching typescript","sequence":12,"time":"2019-02-15T10:45:57.514Z"}
{"context":{"actualVersion":"3.3.3","expectedVersion":">=2.7 <4","logLevel":20,"namespace":"versions","package":"ts-jest","version":"23.10.5"},"message":"checking version of typescript: OK","sequence":13,"time":"2019-02-15T10:45:57.515Z"}
{"context":{"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"tsConfigFileName":"/Users/cht/Code/ts-jest-spread-destucturing/tsconfig.json","version":"23.10.5"},"message":"readTsConfig(): reading /Users/cht/Code/ts-jest-spread-destucturing/tsconfig.json","sequence":14,"time":"2019-02-15T10:45:57.515Z"}
{"context":{"logLevel":20,"namespace":"config","package":"ts-jest","transformerId":1,"tsconfig":{"input":{"compilerOptions":{"declaration":true,"lib":["dom","es5","scripthost","es2015"],"module":"commonJS","outDir":"lib","sourceMap":true,"strict":true,"target":"es5"},"exclude":["node_modules","**/*.spec.ts"],"include":["src/**/*"]},"resolved":{"compileOnSave":false,"configFileSpecs":{"excludeSpecs":["node_modules","**/*.spec.ts"],"includeSpecs":["src/**/*"],"validatedExcludeSpecs":["node_modules","**/*.spec.ts"],"validatedIncludeSpecs":["src/**/*"],"wildcardDirectories":{"/users/cht/code/ts-jest-spread-destucturing/src":1}},"errors":[],"fileNames":["/Users/cht/Code/ts-jest-spread-destucturing/src/index.test.ts","/Users/cht/Code/ts-jest-spread-destucturing/src/index.ts"],"options":{"configFilePath":"/Users/cht/Code/ts-jest-spread-destucturing/tsconfig.json","declaration":false,"inlineSourceMap":false,"inlineSources":true,"lib":["lib.dom.d.ts","lib.es5.d.ts","lib.scripthost.d.ts","lib.es2015.d.ts"],"module":1,"noEmit":false,"outDir":"$$ts-jest$$","removeComments":false,"sourceMap":true,"strict":true,"target":1},"raw":{"compileOnSave":false,"compilerOptions":{"declaration":true,"lib":["dom","es5","scripthost","es2015"],"module":"commonJS","outDir":"lib","sourceMap":true,"strict":true,"target":"es5"},"exclude":["node_modules","**/*.spec.ts"],"include":["src/**/*"]},"typeAcquisition":{"enable":false,"exclude":[],"include":[]},"wildcardDirectories":{"/users/cht/code/ts-jest-spread-destucturing/src":1}}},"version":"23.10.5"},"message":"normalized typescript config","sequence":15,"time":"2019-02-15T10:45:57.527Z"}
{"context":{"fileName":"/Users/cht/Code/ts-jest-spread-destucturing/src/index.ts","logLevel":20,"namespace":"jest-transformer","package":"ts-jest","transformOptions":{"instrument":true,"rootDir":"/Users/cht/Code/ts-jest-spread-destucturing"},"transformerId":1,"version":"23.10.5"},"message":"computing cache key for /Users/cht/Code/ts-jest-spread-destucturing/src/index.ts","sequence":16,"time":"2019-02-15T10:45:57.529Z"}

Minimal repo :
https://github.com/chmielot/ts-jest-spread-destucturing

I'm curious if this issue occurs with javascript as well or only with typescript. To me it looks like istanbul coverage issue rather than this preset itself.

I will close this issue as it's not related to ts-jest but it's a problem with istanbul


view_count: Can this be a value of thousands and millions separated with ','? If not, how to round it up with a decimal suffix added, e.g. 10M?

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood

Are such convertions possible?
README mentions adding suffixes under 'More Conversions'. Examples would help.

Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

Can this be a value of thousands and millions separated with ','?

I don't think so, but maybe pukkandan or Grub4K will correct me on that

how to round it up with a decimal suffix added, e.g. 10M?

More Conversions:
..., D = add Decimal suffixes (e.g. 10M) (flag # to use 1024 as factor) ...

--print "%(view_count)D"

%(view_count&{:,d})s?

%(view_count)D returns whole numbers such as 1M, 2k. Are decimals possible, like 1.4M, 2.5k?

@MMasutin %(view_count).1D


Fix behavior of containers with child controls set as top-level.

When setting a control as top-level, containers would not sort their children, leaving a gap where the control was until a sort was queued afterwards.
This has been fixed by adding a NOTIFICATION_TOP_LEVEL_CHANGED in canvas items that emits a top_level_changed signal which is tracked by containers. This signal and notification have also been added to Node3D nodes for consistency.
Additionally, the editor continued to treat top-level controls within containers as being managed by them, preventing changes to their anchors and offsets. The reason for this was that the editor simply checked for a parent of type Container, entirely disregarding the control's top_level property.
This has been fixed by replacing these checks with a is_managed_by_containers() method that also takes into account the top_level property of the control. The editor also now correctly informs the user that top-level controls can be freely positioned using anchors and the rectangle.
Fixes #91227. Closes godotengine/godot-proposals#3081.

Looks good!
Seems to work for all Containers except TabContainer and an issue in ScrollContainer.
In ScrollContainer, the Scrollbar isn't updated immediately, it looks like it uses outdated data.
TabContainer doesn't use sort children, so more work will need to be done on it.
That should be done in a different PR though.
When changing top_level to true, moving the Control, setting it to false, then undoing it, the position is reset. I don't think anything can be done about this with the current undo/redo system though.


Adding missing Google Analytics

The new design was missing GA tracker.

the docs say to put it just before the </head>. I think that's where we had it before. not sure it really matters...

Ok @mroch. Moved to before