iptables script does not intercept users whose group ID equals the number specified with -u option

iptables script from Istio does not intercept users whose group ID equals the number specified with -u option.
https://github.com/istio/istio/blob/master/tools/deb/istio-iptables.sh#L265
For example, say there are two users: user-a and user-b:
username  |  user-id  |  group-id
user-a        |  5001     |  8001
user-b        |  8001     |  8001
If I evoke the script with: "sudo ./iptables.sh -u 8001", then both user-a and user-b will not be intercepted.

@andraxylia Should we just replace L264-265 with:
iptables -t nat -A ISTIO_OUTPUT -m owner --uid-owner ${uid} --gid-owner ${uid} -j RETURN

And it's the exact duplicate of #6557


build gradle updated to 80pc

Before creating a pull request make sure that:

[x ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[x ] Yes
[ ] No

Old PRS removing to clean up in git.


ImGui Context Crash on Startup - Multiple Titles

Describe the bug

In recent versions of Remix, I have found a number of titles that are now crashing immediately.  Some of these titles appear to have regressed and worked correctly in previous tests (i.e. Condemned: Criminal Origins, F.E.A.R.).
The error points directly to ImGui's codebase and at first glance appears to be a race condition as the ImGui function GetIO() is called before a context has actually been created and/or set.
This crash will silently occur on Release builds. If using Debug-Optimized, an assert will fail before crashing.

User specifications

Remix Version 0.3.0 Debug-Optimized
GPU: Nvidia Geforce RTX 3080
Driver: Nvidia Studio 536.67
Sea Dogs (GOG)

Attach files!
Sea Dogs ImGui Crash.zip

This contains all logs for startup.  The logs are for a debug-optimized assert failure; the crash dump was taken immediately after by allowing the program to proceed anyway.

Setup Instructions (Sea Dogs):

Download and install Sea Dogs from GOG:
Install ElishaCloud's DxWrapper v1.1.6900.22 to the game directory, including dxwrapper.dll and stub/ddraw.dll in the base directory
Extract the included INI files to the game directory:
SeaDogsImGuiCrashConf.zip

To Reproduce
Steps to reproduce the behavior:

Complete the setup instructions above
Open ENGINE.exe
Game will fail assert
If continuing, the game will hit a ddraw error

Other titles with similar issues:

Condemned: Criminal Origins (Steam) (regression)
F.E.A.R. (GOG) (regression)
Risen 2: Dark Waters (GOG)
MDK (Direct3D - ElishaCloud DxWrapper d3d7to9) (GOG) (Regression)

Expected behavior

ImGui is supposed to begin performing basic functions such as setting the mouse cursor to the appropriate type at this point.
A context should already exist by the time ImGui functions are called on in the program.

Screenshots

REMIX-2283 for tracking.

Today I had this issue with Slave Zero (GOG) after using a community provided D3D patch.  The game launched successfully the first few times then eventually began to suffer from this same ImGuiContext issue.  In the original issue filing I was uncertain as to whether this behavior was a race condition or ImGui's initialization silently failing, but my current testing experience seems to further indicate a race condition.

Today I reproduced the issue with a game that was already running successfully.  While testing Unreal Tournament 2003 I started the game, began a match without issue, and changed resolutions from fullscreen 800x600 to fullscreen 1680x1050, and the result was a GImGuiContext crash.  Unfortunately this game will be difficult to test with as it is not available digitally.

Hello. Do you happen to have a crash dump and logs for the UT crash? Updated bug with latest info.

Hi,
I'm sorry, I'm not sure I follow.  What is UT referring to?

Unfortunately after attempting to reproduce the UT2003 bug to provide a crash, I instead found several unrelated bugs and crashes that occurred while changing settings.  I'll collect more info on those and file them as separate issues as soon as I can.

Hi could you try the latest REMIX and Bridge? We tested it on the some games you listed, the Sea Dogs and F.E.A.R (GOG version), both works without seeing the crash in ImGUI.

Hi could you try the latest REMIX and Bridge? We tested it on the some games you listed, the Sea Dogs and F.E.A.R (GOG version), both works without seeing the crash in ImGUI.

It looks like it's fixed now.  I'll go ahead and close this thread. Thank you!


Nesting scrollViews and touchables not working

This issue is actually a duplicate of: https://github.com/facebook/react-native/issues/10822
But I think that the original issue didn't have to be closed as this seems to be an annoying bug, that has a workaround, but at the end it is still a bug.
I have a repository of the issue:
https://github.com/compojoom/rnScrollBug
The code to reproduce this is is very simple:
<ScrollView style={styles.container}>
        <TouchableOpacity
          style={{backgroundColor: 'yellow', padding: 20}}
          onPress={() => this.setState({count: this.state.count+1})}>
          <Text>Count {this.state.count}</Text>
        </TouchableOpacity>

        <Text>selected +{this.state.selected.callCode}</Text>
        <FlatList
          style={{height: 300}}
          initialNumToRender={5}
          renderItem={this.renderItem}
          data={this.state.data}
        />
</ScrollView>

Basically when the nested Flatlist is scrolling touchables don't receive the touch. (And I'm not talking about touchable elements in the Flatlist, but outside of the flatlist)
That is actually unexpected since the parent ScrollView is not moving.
Is this a bug report?
yes
Have you read the Contributing Guidelines?
yes
Environment

(Write your steps here:)

Launch https://github.com/compojoom/rnScrollBug
scroll the list of countries
try to press the count button

Expected Behavior
When pressing the count button - the coun't should update & one shouldn't wait for the flatlist to stop scrolling
Actual Behavior
Pressing the count button has no effect until the list stops scrolling.
Reproducible Demo
https://github.com/compojoom/rnScrollBug

android only? i have the same problem in android, but not on ios, I ended up using on android this library https://github.com/cesardeazevedo/react-native-nested-scroll-view

@compojoom we are also having this issue. what we did is we added a scrollEnabled prop on flatlist which is set for the parent by overriding the touch listener callbacks.

Hi @vivek-walecha-657, how did you do that? Thanks

+1
Very annoying problem. If you have a scroll view that is auto scrolling, any touchable just stops working until the scroll view stops scrolling.

Can you try with #18299 ?

I am also facing same problem, please help with solution

Hi,
I am using android emulator nexus s API and here nested scrollview is not working.


Ct 1827/064 column comments tests conversion

resolves #6623
Description
Straightforward test conversion. Turned a private method into a fixture and requested it as is the pytest way.
We interested in porting any of these to adapters? I don't see an immediate reason to.
Checklist

[X] I have read the contributing guide and understand what's expected of me
[X] I have signed the CLA
[X] I have run this code in development and it appears to resolve the stated issue
[X] This PR includes tests, or tests are not required/relevant for this PR
[X] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR

We interested in porting any of these to adapters? I don't see an immediate reason to.

The legacy version of this test was copy-pasted over to dbt-redshift + dbt-snowflake back in 2021:

https://github.com/dbt-labs/dbt-redshift/blob/main/tests/integration/column_comments_tests
https://github.com/dbt-labs/dbt-snowflake/tree/main/tests/integration/column_comments_tests

We should either:

Replace them with the new converted test (inherited, modified if needed)
Delete them because this isn't adapter-specific behavior

It looks like this test was added as a new test back in https://github.com/dbt-labs/dbt-core/pull/2733 (one of Gerda's very first contributions!) — but it's really an extension of tests for persist_docs, which you just converted (!) in https://github.com/dbt-labs/dbt-core/pull/6409.
That one is running everywhere:

https://github.com/dbt-labs/dbt-redshift/tree/main/tests/integration/persist_docs_tests
https://github.com/dbt-labs/dbt-snowflake/tree/main/tests/integration/persist_docs_tests
https://github.com/dbt-labs/dbt-bigquery/tree/main/tests/integration/persist_docs_tests
https://github.com/dbt-labs/dbt-spark/tree/main/tests/integration/persist_docs

My vote would be:

Move this column_comments test into the persist_docs tests
Set up the new persist_docs tests to run in adapter plugins (replacing the current copy-pasted versions). This behavior varies a lot across different data platforms, and it requires some real implementation feats to provide end users with a consistent experience. E.g. on Snowflake we have to take a roundabout (and therefore riskier) approach for views, which don't support adding column-level comments after the view has been created.

I'll opt for 2, but to ensure I'm on the right path:

merge what I've written here into the persist_docs test
move that persist_docs test into the adapter zone
kick up PRs in each adapter to swap through the adapter zone tests for the copy-paste versions already present that you linked to

That seem right?

@VersusFacit Those steps look exactly right to me!

I th

Good insight, @jtcohen6 . I'll opt for 2 since it seems the better option for the long term. But, I'm a bit shakey on the steps. Can you verify my plan looks right:

merge what I've written here into the persist_docs test
move that persist_docs test into the adapter zone
kick up PRs in each adapter to swap through the adapter zone tests for the copy-paste versions already present that you linked to

Generally don't we kick up PRs per adapter and point them at this branch of core before merging?

Generally don't we kick up PRs per adapter and point them at this branch of core before merging?

@colin-rogers-dbt That's true! Here's how I understood the steps that @VersusFacit outlined:

Update this PR so that it's adding the "column comments" tests into the larger set of persist_docs tests, since they're all very closely related, and should never really have been created/stored separately. Then, merge this PR.
Open a new dbt-core PR that moves all persist_docs tests into the "adapter zone" (dbt-tests-adapter).
Kick up adapter PRs that inherit/run all persist_docs tests from the "adapter zone" (replacing the old unconverted ones that have been copy-pasted into each repo). Those adapter PRs should repoint to the core branch for step 2.

Steps 2 + 3 may require some "rinse + repeat" iteration, as you find that there are adapter-specific behaviors that warrant modifications to the "core" test definition.


ENG-8199 builds off master cpp client and uses sha256 encoding

Is the new exceptions.h file included in the patch? I don't see it.
And also make sure that all the exception error codes are exported so that PHP code can access them.


Query sum value record

This adds a new method to transaction_record and unit tests it.

closed because the merge-base was changed too much. reopening


Support editable install for namespace package

I have a monorepo project with a base package and multiple namespace packages.
The namespace packages cannot be imported when doing an editable install with pdm-backend. However, it can be imported using setuptools as the build backend.
The project structure is as follows:
.
├── packages
│   ├── pkg_a
│   │   ├── pyproject.toml
│   │   └── somepkg
│   │       └── pkg_a
│   │           └── __init__.py
│   └── pkg_b
│       ├── pyproject.toml
│       └── somepkg
│           └── pkg_b
│               └── __init__.py
├── pdm.lock
├── pyproject.toml
└── src
    └── somepkg
        └── __init__.py

The somepkg is the base package and pkg_a, pkg_b are two namespace packages.
The pyproject.toml of base package is:
[project]
name = "somepkg"
version = "0.1.0"
dependencies = []
requires-python = ">=3.12"

[build-system]
requires = ["pdm-backend"]
build-backend = "pdm.backend"

[tool.pdm.dev-dependencies]
dev = [
    "-e pkg_a @ file:///${PROJECT_ROOT}/packages/pkg_a",
    "-e pkg_b @ file:///${PROJECT_ROOT}/packages/pkg_b",
]

[tool.pdm]
distribution = true

The pyproject.toml of namespace packages is:
[project]
name = "pkg_a"
version = "0.0.1"
dependencies = ["somepkg"]

[tool.pdm.build]
includes = ["somepkg/"]

[build-system]
requires = ["pdm-backend"]
build-backend = "pdm.backend"

When use setuptools build backend:
[project]
name = "somepkg"
version = "0.1.0"
dependencies = []
requires-python = ">=3.12"

[build-system]
requires = ["setuptools>=61", "wheel"]
build-backend = "setuptools.build_meta"

[tool.pdm.dev-dependencies]
dev = [
    "-e pkg_a @ file:///the_path_of_project/packages/pkg_a",
    "-e pkg_b @ file:///the_path_of_project/packages/pkg_b",
]

[tool.pdm]
distribution = true

[project]
name = "pkg_a"
version = "0.0.1"
dependencies = ["somepkg"]

[build-system]
requires = ["setuptools>=61", "wheel"]
build-backend = "setuptools.build_meta"

I found that this is because the two handle editable installations of namespace packages differently.
The site-packages directory generated by setuptools is as follows:
.venv/lib/python3.12/site-packages/
├── __editable__.pkg_a-0.0.1.pth
├── __editable__.pkg_b-0.0.1.pth
├── __editable__.somepkg-0.1.0.pth
├── __editable___pkg_a_0_0_1_finder.py
├── __editable___pkg_b_0_0_1_finder.py
├── _virtualenv.pth
├── _virtualenv.py
├── pkg_a-0.0.1.dist-info
│   └── ...
├── pkg_b-0.0.1.dist-info
│   └── ...
└── somepkg-0.1.0.dist-info
    └── ...

And the site-packages directory generated by pdm-backend is as follows:
.venv/lib/python3.12/site-packages/
├── pkg_a.pth
├── pkg_b.pth
├── somepkg.pth
├── _virtualenv.pth
├── _virtualenv.py
├── pkg_a-0.0.1.dist-info
│   └── ...
├── pkg_b-0.0.1.dist-info
│   └── ...
└── somepkg-0.1.0.dist-info
    └── ...

I'm not sure why this works with setuptools, but IMO it shouldn't work, because somepkg is not a native namespace package, since it provides an __init__.py module, and packages a and b do not provide an __init__.py module, so they are native namespace package. Even if somepkg is a pkgutil or pkgresource-style namespace package (or whatever the names are, can't recall), such old-style namespace packages cannot be mixed with native namespace packages.
To correct the setup you should remove the init module from the main somepkg package.

@pawamoy Yes, you are right, the somepkg is not a namespace package. I don't know what to call this package, maybe it's called base package or something. It corresponds to the mynamespace package in the official documentation. So, I think it's a typical usage of namespace package and should work fine. It's work when using non-editable install.

For example, if you have the following package structure:

[mynamespace has an init module]

Then you can break these sub-packages into two separate distributions:

[`mynamespace does not have an init module]

A native namespace package is by definition a package without an init module. You can't have one part with an init module and the other parts without: Python will stop at the first and ignore the rest.

setuptools has special handling for namespace package editable packages as you see in the site-packages folder.
I don't know why because it is not the case as described in the packaging official docs

@pawamoy @frostming Thanks for the clarification, I misunderstood the documentation.
The directory structure above is indeed not a namespace package, but it works without editable installs. Because without editable installation, it will directly generate the directory structure below:
.venv/lib/python3.12/site-packages/
├── _virtualenv.pth
├── _virtualenv.py
├── pkg_a-0.0.1.dist-info
│   └── ...
├── pkg_b-0.0.1.dist-info
│   └── ...
├── somepkg
│   ├── __init__.py
│   ├── pkg_a
│   │   └── __init__.py
│   └── pkg_b
│       └── __init__.py
└── somepkg-0.1.0.dist-info
    └── ...

In this case, somepkg is just a normal package.
So I think this is not a kind of namespace package, but a special case of splitting a package into multiple parts.
Additionally, the PDM Backend does not seem to be able to handle true namespace packages.
I used the following directory structure for testing:
.
├── packages
│   ├── pkg_a
│   │   ├── pyproject.toml
│   │   └── somepkg
│   │       └── foo
│   │           └── pkg_a
│   │               └── __init__.py
│   └── pkg_b
│       ├── pyproject.toml
│       └── somepkg
│           └── foo
│               └── pkg_b
│                   └── __init__.py
├── pdm.lock
├── pyproject.toml
└── src
    └── somepkg
        └── __init__.py

The foo is a namespace package, but also not available in editable installations.
Perhaps we should use the same method how setuptools handle editable installations to support both cases.

Additionally, the PDM Backend does not seem to be able to handle true namespace packages.

For nested namespace packages, every level of the directory must be a namespace package, here somepkg is a namespace package and it must not contain __init__.py in every distribution.

@frostming Oh, I see. But I found that this actually works fine with a non-editable installation. Here somepkg is not a namespace package, and somepkg.foo is a namespace package.
>>> somepkg
<module 'somepkg' from '/xxx/.venv/lib/python3.12/site-packages/somepkg/__init__.py'>
>>> import somepkg.foo
>>> somepkg.foo
<module 'somepkg.foo' (namespace) from ['/xxx/.venv/lib/python3.12/site-packages/somepkg/foo']>

Is this some kind of undefined behavior? I don't seem to find any documentation on this.
I also found some well-known packages using this structure, such as Airflow.
https://github.com/apache/airflow/tree/main/airflow/providers

Is this some kind of undefined behavior? I don't seem to find any documentation on this.

Yes, the way installer installs packages allow this, because why not, it is easy to do, shouldn't be that restrict otherwise.

I also found some well-known packages using this structure, such as Airflow.
https://github.com/apache/airflow/tree/main/airflow/providers

airflow/provider is a namespace package without a __init__.py, that is correct, what do you want to prove?

airflow/provider is a namespace package without a __init__.py, that is correct, what do you want to prove?airflow/provider是一个没有__init__.py的命名空间包，这是正确的，你想证明什么？

Maybe I didn't express clearly enough.
What I mean is that the provider package of Airflow is a namespace package, and its subpackages are actually packaged separately when released.
Like apache-airflow-providers-sqlite, apache-airflow-providers-postgres, etc.
So I think it's actually something like the project structure below.
.
├── packages
│   ├── apache-airflow-providers-sqlite
│   │   ├── pyproject.toml
│   │   └── airflow
│   │       └── providers
│   │           └── sqlite
│   │               └── __init__.py
│   └── apache-airflow-providers-postgres
│       ├── pyproject.toml
│       └── airflow
│           └── providers
│               └── postgres
│                   └── __init__.py
├── pdm.lock
├── pyproject.toml
└── src
    └── airflow
        └── __init__.py

What I want to express is that there are different behaviors when using editable installation and non-editable installation, similar to the project structure above and the project structure at the beginning. When using non-editable installation, these project structures are all feasible, but they are not suitable for editable installation.
Using special handling like setuptools, both cases can be supported with editable installation.

Airflow is apparently a pkg-util namespace package, see this line in their __init__.py module:
__path__ = __import__("pkgutil").extend_path(__path__, __name__)

So apparently I was wrong thinking that old-style and native namespace packages cannot be mixed together, since the Airflow providers (native) seem to work with the main package (pkgutil-style).

Thanks for your suggestion, I will try it.

So apparently I was wrong thinking that old-style and native namespace packages cannot be mixed together, since the Airflow providers (native) seem to work with the main package (pkgutil-style). That's interesting.

Yes, there is a compatibility note in the guide:

While native namespace packages and pkgutil-style namespace packages are largely compatible, pkg_resources-style namespace packages are not compatible with the other methods. It’s inadvisable to use different methods in different distributions that provide packages to the same namespace.


Support Multiple Result Sets

add in support for cursor.nextset()
Fixes issue with Earthly not finding the correct mssql driver

Fixes:
https://github.com/blue-yonder/turbodbc/issues/368
https://github.com/blue-yonder/turbodbc/issues/367
https://github.com/blue-yonder/turbodbc/issues/323
https://github.com/blue-yonder/turbodbc/issues/145
https://github.com/blue-yonder/turbodbc/issues/192

Codecov Report
Base: 98.32% // Head: 98.39% // Increases project coverage by +0.06% :tada:

Coverage data is based on head (e2ed2af) compared to base (ca36325).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #369      +/-   ##
==========================================
+ Coverage   98.32%   98.39%   +0.06%
==========================================
  Files          93       93
  Lines        2978     2983       +5
==========================================
+ Hits         2928     2935       +7
+ Misses         50       48       -2

Impacted Files
Coverage Δ

cpp/turbodbc/Library/src/command.cpp
100.00% <100.00%> (ø)

cpp/turbodbc/Library/src/cursor.cpp
100.00% <100.00%> (ø)

...odbc_python/Library/src/python_bindings/cursor.cpp
100.00% <100.00%> (ø)

python/turbodbc/cursor.py
99.00% <100.00%> (+<0.01%)
:arrow_up:

...bc_python/Library/src/determine_parameter_type.cpp
98.24% <0.00%> (-0.04%)
:arrow_down:

...p/cpp_odbc/Library/src/level1/unixodbc_backend.cpp
82.14% <0.00%> (+3.57%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

Fixes:
https://github.com/blue-yonder/turbodbc/issues/366

Fixes: #366

How does this affect pyarrow 10 support? As long as
https://github.com/blue-yonder/turbodbc/blob/ca36325a61cda7e1af628b7a947de8a3a00149be/setup.py#L233
is there, support is explicitly disabled

I have all the commits ready to be push to this feature branch to support pyarrow10. There is one issue calling new test around pyarrow10 to fail. Once this arrow issue is closed out, I'll commit my changes

Test pass for pyarrow <10, but fail for pyarrow10. Seems like the STATIC_LIB files could be the issue, ie. libarrow.a and libarrow_python.a.

Seems to me there are two include paths post pyarrow10, one is the old /opt/conda/envs/turbodbc-dev/include and one is the new /opt/conda/envs/turbodbc-dev/lib/python*.*/site-packages/pyarrow/include (PYARROW_INCLUDE_DIR) where things like api.h and pyarrow.h now live. additionally libarrow.a is required, here is the relevant doc below
Find ARROW (arrow/api.h, libarrow.a, libarrow.so)
This module defines
ARROW_INCLUDE_DIR, directory containing headers
ARROW_LIBS, directory containing arrow libraries
ARROW_STATIC_LIB, path to libarrow.a
ARROW_SHARED_LIB, path to libarrow's shared library
ARROW_FOUND, whether arrow has been found

Seems to me there are two include paths post pyarrow10

Yes, that is correct and expected

additionally libarrow.a is required

Do you need the static libraries? For example, when installing pyarrow as a wheel, only .so libs are included for libarrow(_*). And certainly now libarrow_python is always included in the pyarrow package (also for conda), I think this will always only available as dynamic library.

We could altogether remove the static section from FindArrow, this is not needed for turbodbc.

Seems to me there are two include paths post pyarrow10

Yes, that is correct and expected

additionally libarrow.a is required

Do you need the static libraries? For example, when installing pyarrow as a wheel, only .so libs are included for libarrow(_*). And certainly now libarrow_python is always included in the pyarrow package (also for conda), I think this will always only available as dynamic library.

I've adjusted the FindArrow logic to not include static libraries based on @xhochy comment. The two include path issue still persist for pyarrow10 test. Currently, the FindArrow logic defines the following ARROW_INCLUDE_DIR, directory containing headers. I'm going to define PYARROW_INCLUDE_DIR and add an include_directories call in cpp/turbodbc_arrow/CMakeLists.txt

Currently this feature branch works for all test cases including pyarrow10. The next steps is to add in the changes to the change log. The largest adjustments are the introduction of .nextset() capabilities, and the ability to use pyarrow10+. The largest overarching changing that users should be aware of is that pyarrow10 requires the use of c++17, I bumped the default arguments but that's a pretty large change we will have to make with pyarrow


Ivy rebuild

:tada: This PR is included in version 5.0.0-rc.11 :tada:
The release is available on:

npm package (@rc dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Conditional devtools

This environment variable, if set to 1, will allow running app in development without devtools.

Coverage remained the same at 68.229% when pulling 3481fa883578f9387bca2f90d0be4cd3c9de14bb on conditionalDevtools into 246c3b015dbe1bb4d65b90cd6f58488fba8f0620 on master.


BatchNorm behavior during inference

This is bit more detailed but I wanted to check if the batch norm layer of the computation graph (1st picture below) matches the one you find when importing the model.
When zeroing in on the model graph loaded under inference mode, it seems that the batch norm doesn't use the running_mean and running_var during forward pass (see 1st graph below; I also checked by computing expected output and it didn't match).
But when I construct a simpler net, batch norm uses the running_mean and running_var during forward pass (see 2nd graph; I also checked by computing expected output).
I'm wondering if this is could be an error related to FusedBatchNorm vs FusedBatchNormV3; upon importing the model, it uses FusedBN yet when constructing a new model, it used FusedBNV3.  I'm not sure what causes this difference in the type of class used to construct the BN layer.
Thanks.

Hi @slala2121, thanks for your question! Sorry for my extremely late reply.
Can you first please let me know what Python and Tensorflow version you're running this with? And give me some instructions on how to get this graph please?


videos +markdown

Overview

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: [ABC-123]
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change
[ ] This PR includes testing instructions tests for the code change
[ ] The alpha package of this PR is passing end-to-end tests in all relevant Codecademy repositories

Testing Instructions

Don't make me tap the sign.
PR Links and Envs

Repository
PR Link
PR Env

Monolith
Monolith PR
Monolith Env

Portal
Portal Link
Portal Env

Another Repo
Another Link
Another Env

📬Published Alpha Packages:@codecademy/gamut@57.2.3-alpha.1f6671.0@codecademy/gamut-kit@0.6.444-alpha.1f6671.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut@57.3.1-alpha.ef28c2.0@codecademy/gamut-kit@0.6.445-alpha.ef28c2.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://66fd9b28f914aa727f72ec84--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut@57.3.1-alpha.f51cd9.0@codecademy/gamut-kit@0.6.445-alpha.f51cd9.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://66fdbb35d9202c94f6db05eb--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut@57.3.1-alpha.014413.0@codecademy/gamut-kit@0.6.445-alpha.014413.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://66fff8466d7c813ff945a53e--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut@57.3.1-alpha.e82ce9.0@codecademy/gamut-kit@0.6.445-alpha.e82ce9.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://670001dd93a3915362a2c019--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut@57.3.2-alpha.7847e3.0@codecademy/gamut-kit@0.6.446-alpha.7847e3.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://67004f6c4c7e411bd02c9d3c--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut@57.3.2-alpha.2cac30.0@codecademy/gamut-kit@0.6.446-alpha.2cac30.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://670059acb153101f913f5ccd--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut@57.3.3-alpha.685447.0@codecademy/gamut-kit@0.6.447-alpha.685447.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut@57.3.3-alpha.b4412b.0@codecademy/gamut-kit@0.6.447-alpha.b4412b.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6704254ffe121a0930962681--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut@57.3.3-alpha.dd5af3.0@codecademy/gamut-kit@0.6.447-alpha.dd5af3.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://67044872db196b3a704dc43e--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut@57.3.3-alpha.1532c0.0@codecademy/gamut-kit@0.6.447-alpha.1532c0.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://67044e62af98783763589e54--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut@57.3.4-alpha.6a179d.0@codecademy/gamut-kit@0.6.448-alpha.6a179d.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6706a7de22cb4b870a86e5ba--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut@57.3.4-alpha.6a179d.0@codecademy/gamut-kit@0.6.448-alpha.6a179d.0<EMAIL_ADDRESS>
📬Published Alpha Packages:@codecademy/gamut@57.3.4-alpha.01e813.0@codecademy/gamut-kit@0.6.448-alpha.01e813.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://670d238ac1ee79f243a3ce15--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut@57.3.4-alpha.76db61.0@codecademy/gamut-kit@0.6.448-alpha.76db61.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://670d3c72c4b31d0b2277af4f--gamut-preview.netlify.appDeploy Logs


✨ Added option to disable member subscriptions

refs https://github.com/TryGhost/Team/issues/579

new Members Access settings screen that moves subscription access and default post visibility from the Members Payments settings screen
expanded "Free signup" toggle into three signup access options

"anyone" - full signup and login functionality is enabled. To restrict signups to paid members only, remove the free plan from the available plans in Portal settings
"invite only" -  signup is disabled but login is enabled. Members must be added manually by site admins or via Ghost's Admin API
"nobody" - completely disables member signup and login. Removes injected portal and stripe scripts on the front-end and hides member related sections on the admin dashboard

(this commit moves the above changes out from behind the developer experiments flag and cleans up now-unused code)

@kevinansfield how do we check for this in theme handlebars ?

@ramrami I haven't seen a way to do this yet but I'm looking for the same thing. I created a forum post

@rajivshah3 Kevin answered here
"For the time being the @labs.members property still works although it’s deprecated and may be removed in the next major release. A non-deprecated replacement is being worked on."

Oh, great! Thanks @ramrami


VSCode Terminal launches with "export" text printed on it

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.78.2
OS Version: macOS Monterey 12.6.3

Steps to Reproduce:

Open the terminal.

Screenshot

Description
The above text "export" cannot be deleted. It appears in all the folders and workspaces and started happening yesterday after an update. I am using the Zsh terminal. This issue doesn't appear on bash.

It was a problem with zsh actually. For some reason, the export path statement was on the same line as prompt in .zshrc. This led to "export" becoming a part of the prompt. Fixed it by adding a line break


Steps component

Feature description
Steps component inspired by starlight
Affected component/components/documentation
Steps
Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues and PRs

Issues like these are now migrated from Github to Linear for internal use.


Error during parsing: unsupported root directive: crypto

Describe the issue
I'm configuring for the first time the jwt plugin but I cannot start caddy service as it throws an error every time.
This is the error log:
Apr 23 20:43:17 palmiottos-server caddy[45986]: {"level":"info","ts":1619203397.5166593,"msg":"using provided configuration","config_file":"/etc/caddy/Caddyfile","config_adapter":""}
Apr 23 20:43:17 palmiottos-server caddy[45986]: reload: adapting config using caddyfile: parsing caddyfile tokens for 'route': /etc/caddy/Caddyfile:20 - Error during parsing: parsing caddyfile tokens for 'jwt': /etc/caddy/Caddyfile:14 - Error during parsing: unsupported root directive: crypto
Apr 23 20:43:17 palmiottos-server systemd[1]: caddy.service: Control process exited, code=exited, status=1/FAILURE
Apr 23 20:43:17 palmiottos-server systemd[1]: Reload failed for Caddy.

Configuration
Paste full Caddyfile below:
test.palmiotto.duckdns.org {
tls {
        issuer acme {
                disable_http_challenge
        }
        issuer zerossl {
                disable_http_challenge
        }
}

route {
        jwt {
                primary yes
                crypto key token name 4cc3ssT0k3n
                crypto key verify xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
                set token sources header query cookie
                set auth url https://auth.palmiotto.duckdns.org/token
        }
        reverse_proxy localhost:3000
}

#reverse_proxy /jellyfin/* <IP_ADDRESS>:8096

#handle_path /auth/* {
#     reverse_proxy <IP_ADDRESS>:5000
#}

#route /planes/* {
#     uri strip_prefix /planes
#     reverse_proxy <IP_ADDRESS>:8754
#}

#handle_errors {
#       rewrite * /{http.error.status_code}
#       reverse_proxy https://http.cat {
#               header_up Host http.cat
#       }
#}
}

auth.palmiotto.duckdns.org {
tls {
        issuer acme {
                disable_http_challenge
        }
        issuer zerossl {
                disable_http_challenge
        }
}
reverse_proxy <IP_ADDRESS>:5000
}

Version Information
Provide output of caddy list-modules -versions | grep auth below:
http.authentication.hashes.bcrypt v2.4.0-beta.1
http.authentication.hashes.scrypt v2.4.0-beta.1
http.authentication.providers.http_basic v2.4.0-beta.1
http.handlers.authentication v2.4.0-beta.1
http.authentication.providers.jwt v1.2.7

Expected behavior
The server should start.
What is causing the problem? What can I do to fix it? Thanks in advance

@offgabriele , I am in the process of rewriting the plugin. Please use the instructions from here: https://github.com/greenpau/caddy-auth-jwt/tree/v1.2.7
The crypto key instructions coming out soon.

@offgabriele , I finished the plugin rewrite. However, did not mark it for release yet. Feel free to try it out. You would need to reread the docs. Your jwt directive may be missing “allow” directive, e.g. “allow roles viewer editor reader”. The ACL systems is much more advanced, but I did not get a chance to document it yet.

@offgabriele , were you able to test it?

No I am sorry I did not had the chance, I went with the version you linked me. Thank you for the effort you put in managing this plugin.


Be able to configure Mapnik's logger severity level through options

Mapnik uses stdout for logging and we might want to decide what to do with them.
$ node
> const mapnik = require('@carto/mapnik');
undefined
> mapnik.Logger
{ [Function: Logger]
  getSeverity: [Function: getSeverity],
  setSeverity: [Function: setSeverity],
  NONE: 3,
  ERROR: 2,
  DEBUG: 0,
  WARN: 1 }
> mapnik.Logger.getSeverity()
2
> mapnik.Logger.setSeverity(mapnik.Logger.NONE)
undefined
> mapnik.Logger.getSeverity()
3

@Algunenano, do you know what severity level we are setting for the logger while compiling @carto/mapnik?

We redirect stdout to a file and it's polluted with messages as follows:
WARNING:  ST_Line_Interpolate_Point signature was deprecated in 2.1.0. Please use ST_LineInterpolatePoint
WARNING:  ST_Line_Interpolate_Point signature was deprecated in 2.1.0. Please use ST_LineInterpolatePoint
WARNING:  ST_Line_Interpolate_Point signature was deprecated in 2.1.0. Please use ST_LineInterpolatePoint
WARNING:  ST_Line_Interpolate_Point signature was deprecated in 2.1.0. Please use ST_LineInterpolatePoint
WARNING:  ST_Line_Interpolate_Point signature was deprecated in 2.1.0. Please use ST_LineInterpolatePoint
WARNING:  ST_Line_Interpolate_Point signature was deprecated in 2.1.0. Please use ST_LineInterpolatePoint
WARNING:  ST_Line_Interpolate_Point signature was deprecated in 2.1.0. Please use ST_LineInterpolatePoint
WARNING:  ST_Line_Interpolate_Point signature was deprecated in 2.1.0. Please use ST_LineInterpolatePoint
Mapnik LOG> 2020-05-01 12:20:17: SVG PARSING ERROR:"SVG support error: <font-size> attribute is not supported"
Mapnik LOG> 2020-05-01 12:20:17: SVG PARSING ERROR:"SVG support error: <font-style> attribute is not supported"
Mapnik LOG> 2020-05-01 12:20:17: SVG PARSING ERROR:"SVG support error: <font-variant> attribute is not supported"
Mapnik LOG> 2020-05-01 12:20:17: SVG PARSING ERROR:"SVG support error: <font-weight> attribute is not supported
NOTICE:  identifier "right_temps_perdu_moyen_par_jour_supplementaire_en_heure_de_pointe" will be truncated to "right_temps_perdu_moyen_par_jour_supplementaire_en_heure_de_poi"
NOTICE:  identifier "right_temps_perdu_moyen_par_jour_supplementaire_en_heure_de_pointe" will be truncated to "right_temps_perdu_moyen_par_jour_supplementaire_en_heure_de_poi"
NOTICE:  identifier "right_do_any_hospitals_have_access_to_a_tax_refund_offset_program_in" will be truncated to "right_do_any_hospitals_have_access_to_a_tax_refund_offset_progr"
NOTICE:  identifier "right_do_any_hospitals_have_access_to_a_tax_refund_offset_program_in" will be truncated to "right_do_any_hospitals_have_access_to_a_tax_refund_offset_progr"
WARNING:  ST_Shift_Longitude signature was deprecated in 2.2.0. Please use ST_ShiftLongitude
WARNING:  ST_Shift_Longitude signature was deprecated in 2.2.0. Please use ST_ShiftLongitude

We've never done anything with them, wondering how useful are they and what approach we should give to them.

Also wondering why some of them have the prefix Mapnik LOG> {TIMESTAMP} and if they can be omitted by setting a higher security level.

@Algunenano, do you know what severity level we are setting for the logger while compiling @carto/mapnik?

We don't change it https://github.com/CartoDB/mason/blob/master/scripts/mapnik/3.0.15-carto/script.sh so whatever is default.
The log level is defined at compile time, and when it's not defined it's automatically set to 2 (https://github.com/CartoDB/mapnik/blob/1021a5e3059e939ffc78b84792e605ae6fd8344c/src/debug.cpp#L41) which enables logger::error.
The SVG PARSING ERROR messages are reported by the svg_parser.
The logs starting from WARNING or NOTICE come from the database and don't have the mapnik log format (they should start with Mapnik LOG>), so they are either printed without the logs (I couldn't find them) or they are printed directly by libpq for some reason. I would need to investigate further to find where they are being emited.


Added jdk httpclient to live tests

The jdk httpclient needs to setup on Java 11+.
Issue link: https://github.com/Azure/azure-sdk-for-java/issues/10465
Jdk httpclient has some blacklist headers (like Date) which affect the results of live tests, so it cannot be tested over Java 11.
Think about to add another Java version (like 13, MTS) to test Jdk httpclient.
Refer this build:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=368178&view=logs&j=d4b67cd2-6572-561e-035e-54acb01c3f6e
This PR is still in discussion. Welcome to review, but this is not ready to merge yet.   If this is still desirable to add, please work with @JimSuplizio and @mitchdenny to get this into a state where it can be merged.  Sima is no longer working on Java related work (though she certainly can help explain anything in the PR that doesn't make sense) and has moved on to other tasks.

Should this now be closed?

In fact, I am pre-emptively closing it ... if anyone needs to pick it up they can re-open.


[20.09] discord: 0.0.14 -> 0.0.15

Backport of #124336 for 20.09
Discord prevents you from using the application if a new version is out, so it's practically broken for everyone right now

Result of nixpkgs-review pr 124369 at b5e483a7 run on x86_64-linux 1

3 packages built successfully:

discord
discord-canary
discord-ptb


Bug in default executor code

Summary
This link looks wrong, "" should not be docker anymore:
https://github.com/argoproj/argo-workflows/blob/ca87f2906995b8fecb796d94299f54f6dfbd6a41/workflow/controller/workflowpod.go#L538

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

I took an initial attempt at a fix of it, but couldn't complete it yet. Feel free to take it over :+1:

Thanks, @mweibel. I will raise a PR


utf8toUnicode buffer misallocation

The utf8toUnicode transformation function reads utf8 sequences and formats out codepoints as hex sequences.
We are considering the C implementation here:
https://github.com/SpiderLabs/ModSecurity/blob/046b5537368c2a5c3ef9c25b64f0041d3932b373/apache2/re_tfns.c#L348
however I think the following also applies to the C++ implementation here:
https://github.com/SpiderLabs/ModSecurity/blob/libmodsecurity/src/actions/transformations/utf8_to_unicode.cc
The maximum unicode codepoint is U+10FFFF. This is stored in four UTF-8 bytes max:
https://stijndewitt.com/2014/08/09/max-bytes-in-a-utf-8-char/
Regardless of however many UTF-8 bytes are used, output is formatted as a literal %, literal u, followed by sprintf of "%x" for the hex value of the codepoint. So that outputs %u10ffff for the maximum codepoint. This is 8 characters long including the prefix; the hex digits are in storage allocated by apr_psprintf():
unsigned char *unicode = NULL;
unicode = apr_psprintf(mp, "%x", d);

The literal % u prefix is written to data. The eight characters are then copied out to data:
*data++ = '%';
*data++ = 'u';
length = strlen(unicode);
for(j=0; j<length; j++) {
    *data++ = unicode[j];
}

But data was allocated to have a maximum space for 7 characters per byte of UTF-8 input:
len = input_len * 7 + 1;
data = rval = apr_palloc(mp, len);

Single-byte sequences are not output as hex sequences. So the smallest number of bytes
per codepoint is 2, and the maximum 4.
How many bytes are written out, given each byte consumed:

utf8 in

bytes out
factor

1
→
1
1/1 = 1

2
→
8
8/2 = 4

3
→
8
8/3 = 2.66

4
→
8
8/4 = 2

So without considering whether any particular byte is a UTF-8 sequence or not, the worse case given input_len alone is a factor of 4. Hence:
len = input_len * 4 + 1;

Hi @katef,
Better if you can submit it in a format of a patch, so you can keep the authorship of the change, what do you think?

This makes sense for me. I've submitted a commit for testing here: https://github.com/SpiderLabs/ModSecurity/commit/6926f404d1c662302fa92e7b4a9d902fde5b562a
And v3 branch here: https://github.com/SpiderLabs/ModSecurity/commit/318d45236fb872f984e5308fc8c0a117a68d9c7e
If all goes well, I believe we can merge for 2.9.3.
Thanks :)

Fixed in v2: https://github.com/SpiderLabs/ModSecurity/commit/b600669d02d2344089c8b024f75c806619cb3135
And v3: https://github.com/SpiderLabs/ModSecurity/commit/ecad8c6c7e0aca3225c432f0ea5b11e160c6c5ce
Thanks for your contribution @katef :)

Wonderful, thank you :)


Updates based on upstream review

Changes based on discussion on the upstream pull request, https://github.com/cwRichardKim/RKNotificationHub/pull/12.  @vokal/ios-developers Code review please?

LGTM

@chillpop merge-ready?


add normalize

Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure to update the docs?
[x] Did you write any new necessary tests?

What does this PR do?
Fixes #334 .
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
⚡

Awesome start, @k223kim!

I think the failing checks are (mostly) real.

@t-vi Yes, sorry. I think there is an issue with my implementation. Let me take a closer look and update you on this!

Hi @t-vi Tom! Just updated my code with the requested test cases. I will add another PR to handle different dims! (cc. @mruberry )

One last thing: I think we want to increase the allowed difference to rtol=1e-5 or test with a larger eps. Normalization can be expected to be numerically touchy.
FAILED thunder/tests/test_grad.py::test_vjp_correctness_normalize_nvfuser_cuda_float64 - AssertionError: Scalars are not close!

Expected 13.858696783947043 but got 13.858595215142994.
Absolute difference: 0.00010156880404821322 (up to 1e-05 allowed)
Relative difference: 7.328885654375779e-06 (up to 1.3e-06 allowed)

The test failure is related, the vjp tests just need their tolerance tightened:
FAILED thunder/tests/test_grad.py::test_vjp_correctness_normalize_nvfuser_cuda_float64 - AssertionError: Scalars are not close!

Expected 13.261265786378505 but got 13.261199947853306.
Absolute difference: 6.583852519881361e-05 (up to 1e-05 allowed)
Relative difference: 4.964724051186771e-06 (up to 1.3e-06 allowed)

Maybe 1e-03 for both values would be OK for now?

The test failure is related, the vjp tests just need their tolerance tightened:

This needs an update on the vjp test itself to use the tolerance (which is something we tried earlier and didn't work out of the box, so we tried with larger eps)

Hey all! The current CI testing is failing with the following error:
FAILED thunder/tests/test_grad.py::test_vjp_correctness_normalize_torch_cpu_float64 - AssertionError: Scalars are not close!

Expected 13.56249856229506 but got 13.562559772296954.
Absolute difference: 6.121000189374115e-05 (up to 1e-05 allowed)
Relative difference: 4.513180341556706e-06 (up to 1.3e-06 allowed)

And I believe this can be resolved by #598! Other than that, I think this PR is good to go! Please let me know if I could improve more :)


Agent feature - ability to start at step

Fixes https://github.com/Microsoft/azuredatastudio/issues/1507
Screenshots of New Job and Edit Job scenarios -
New Job

Edit Job

Accomapanying tools service PR - https://github.com/Microsoft/sqltoolsservice/pull/758

@abist I'll merge to include in tonight's insider build.


The target scope "resourceGroup" does not match the deployment scope "subscription".

I have followed this MS article: https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/deploy-to-resource-group?tabs=azure-cli#create-resource-group
I have copied the code exactly and named my modules files the same. The only edited part is the subscription ID.
When running the below from Visual Studio (1.79.1)
az deployment sub create --location uksouth --template-file main.bicep
The error returns
The target scope "resourceGroup" does not match the deployment scope "subscription".

Any help would be appreciated please. Thank you!
Main bicep file
@maxLength(11)
param storagePrefix string

param firstStorageLocation string = resourceGroup().location

param secondResourceGroup string
param secondSubscriptionID string = '****removed for security****'
param secondLocation string

var firstStorageName = '${storagePrefix}${uniqueString(resourceGroup().id)}'

// resource deployed to target resource group
module firstStorageAcct 'storage2.bicep' = {
  name: 'storageModule1'
  params: {
    storageLocation: firstStorageLocation
    storageName: firstStorageName
  }
}

// module deployed to subscription
module newRG 'resourceGroup.bicep' = {
  name: 'newResourceGroup'
  scope: subscription(secondSubscriptionID)
  params: {
    resourceGroupName: secondResourceGroup
    resourceGroupLocation: secondLocation
  }
}

module file resourcegroup.bicep
targetScope='subscription'

param resourceGroupName string
param resourceGroupLocation string

resource newRG 'Microsoft.Resources/resourceGroups@2022-09-01' = {
  name: resourceGroupName
  location: resourceGroupLocation
}

Storage2.bicep module file
param storageLocation string
param storageName string

resource storageAcct 'Microsoft.Storage/storageAccounts@2022-09-01' = {
  name: storageName
  location: storageLocation
  sku: {
    name: 'Standard_LRS'
  }
  kind: 'Storage'
  properties: {}
}

Structure in VS

Version: 1.79.1 (user setup)
Commit: 4cb974a7aed77a74c7813bdccd99ee0d04901215
Date: 2023-06-12T16:14:05.102Z
Electron: 22.5.7
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22000
Bicep extension =  v0.18.4
Azure cli tools extension  = v0.18.4

main.bicep is scoped for a resource group deployment. You would need to use the az deployment group create command in the az CLI rather than the az deployment sub create command.

main.bicep is scoped for a resource group deployment. You would need to use the az deployment group create command in the az CLI rather than the az deployment sub create command.

Hi @jeskew
Thank you for your help.
I do not fully understand though as I am wanting the module resourcegroup.bicep to create the resource group including the name.
To run the command az deployment group I have to run it with --resource-group which ends in a error as the resource group does not exist which is correct.
What would I need to run as an Azure command for to build the resource group?

Got it; I thought the template was supposed to create a second resource group. You can create a resource group and deploy resources into it in a single deployment, but you would need to start at subscription scope. That means your main.bicep file will need a targetScope = 'subscription' statement. (Note that the storage2.bicep module needs to be at resource group scope, since storage accounts have to be deployed within a resource group.)
There's a tutorial/walkthrough on how to deploy at multiple scopes that might be helpful if you want more detail on what scope transitions are supported.


Improve PSKKeyExchangeModes support

Don't send PSKKeyExchangeModes when there's no PSK
Add tests for correct behavior by offered mode

Don't send PSKKeyExchangeModes when there's no PSK

What do you mean by this? On the client it's the correct behavior to request a Ticket.


Use performance.now() as timestamp per spec

Emscripten SDL2 only updates gamepad data if the timestamp changes. Before, it would only change once per second. Now it will change every time getGamepads is called. Ideally it would only change if values are updated, but this is fine for now. performance.now ("current high resolution time") is what the gamepad spec requires: https://www.w3.org/TR/gamepad/#dom-gamepad-timestamp

Thank you for correcting that spec difference! Documentation and examples work just as well with performance.now(). I'll rerun some other tests to make sure & make a new release soon, but overall thanks!
I may make a release after that with (hopefully minimal) breaking changes. If I can ask, what parts of the current api did you find hardest to use? I know the current api surface has a lot of boilerplate config.

So far I'm only using GamepadEmulator to emulate a single left analog stick, and I found it pretty nice. I haven't tried using GamepadDisplay. I wasn't sure if I could have it automatically display a single left stick.


Add count to work visa outcomes

Adds a count of the number of visas available on the outcomes for the work visa smart answer.
In order to do this, we have needed to move the visa types into their own partials and the possible combinations into a YAML file.  This is now used to dynamically generate the outcome, rather than hardcoding into multiple views.
This has been branched from https://github.com/alphagov/smart-answers/pull/5523 and will need to be rebased against main after #5523 has been merged.
Example:

Trello card
⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠

(Rebased to fix conflicts. No changes required).


[SPARK-37317][MLLIB][TESTS] Reduce weights in GaussianMixtureSuite

What changes were proposed in this pull request?
This PR aims to reduce the test weight 100 to 90 to improve the robustness of test case GMM support instance weighting.
test("GMM support instance weighting") {
  val gm1 = new GaussianMixture().setK(k).setMaxIter(20).setSeed(seed)
  val gm2 = new GaussianMixture().setK(k).setMaxIter(20).setSeed(seed).setWeightCol("weight")
- Seq(1.0, 10.0, 100.0).foreach { w =>
+ Seq(1.0, 10.0, 90.0).foreach { w =>

Why are the changes needed?
As mentioned in https://github.com/apache/spark/pull/26735#discussion_r352551174, the weights of model changes when the weights grow. And, the final weight 100 seems to be high enough to cause failures on some JVMs. This is observed in Java 17 M1 native mode.
$ java -version
openjdk version "17" 2021-09-14 LTS
OpenJDK Runtime Environment Zulu17.28+13-CA (build 17+35-LTS)
OpenJDK 64-Bit Server VM Zulu17.28+13-CA (build 17+35-LTS, mixed mode, sharing)

BEFORE
$ build/sbt "mllib/test"
...
[info] - GMM support instance weighting *** FAILED *** (1 second, 722 milliseconds)
[info]   Expected 0.10476714410584752 and 1.209081654091291E-14 to be within 0.001 using absolute tolerance. (TestingUtils.scala:88)
...
[info] *** 1 TEST FAILED ***
[error] Failed: Total 1760, Failed 1, Errors 0, Passed 1759, Ignored 7
[error] Failed tests:
[error] 	org.apache.spark.ml.clustering.GaussianMixtureSuite
[error] (mllib / Test / test) sbt.TestsFailedException: Tests unsuccessful
[error] Total time: 625 s (10:25), completed Nov 13, 2021, 6:21:13 PM

AFTER
[info] Total number of tests run: 1638
[info] Suites: completed 205, aborted 0
[info] Tests: succeeded 1638, failed 0, canceled 0, ignored 7, pending 0
[info] All tests passed.
[info] Passed: Total 1760, Failed 0, Errors 0, Passed 1760, Ignored 7
[success] Total time: 568 s (09:28), completed Nov 13, 2021, 6:09:16 PM

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.

Hi, @zhengruifeng . Could you review this?

Test build #145198 has started for PR 34584 at commit e559455.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49667/

Test build #145198 has finished for PR 34584 at commit e559455.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/49667/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/49667/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/145198/

cc @HyukjinKwon and @LuciferYang , too

Thank you, @HyukjinKwon ! Merged to master.

late LGTM

Thank you, @zhengruifeng .

Is this another issue that I haven't found out? Let me try it too

No, @LuciferYang . It happens on Java 17 native Apple Silicon version.
Your verification on Java 17 on Linux is fine as we see in our Daily GitHub Action job.

I reset master branch to 41f9df92061ab96ce7729f0e2a107a3569046c58 (before this pr). This issue can be reproduced using sbt, but maven is passed. And  both maven and sbt passed with this  PR. thanks @dongjoon-hyun


feat: add ShouldHaveOnlyOnePublicMethod rule

Useful for ensuring that Application Services, Controllers… have only one public method in order to enforce SRP. 🙂
I've tried to follow all the code practices in the repo, feel free to make any changes.
PHPMD offers this feature as well, but imho, it has more sense as an architectural layer.

Thanks!
Psalm is complaining because it doesn't understand the tricks BetterReflection does to be compatible with PHP 7 and 8, but it works well in reality. I will merge, fix the CI config problems, and release a new version during this week :D
Thanks for the contribution, and happy to hear that PHPat is going to be part of one of your amazing courses  🙌

Awesome!! 🙌

Graaaaandeeee!!! 🔝
In two weeks we'll publish the YT video! Already recorded. 🙂


Fix horizontal scrollbar appearing on Hyper window

The overflow: hidden; property on the Hyperline wrapper element isn't taking margin
into account for the x-axis, so a horizontal scrollbar is shown.
Here's what this looks like:

By using padding instead of margin on the x-axis , any x-axis overflow is correctly hidden.
Here's how it looks with the changes in this PR:

Thanks Bill!


og fixes

Fix of og problems after merging studio with rest of www

Can we use this OG image for Studio instead?

@mohab-sameh added 👍


fix(tooltip): add border radius

What I did

Added border radius
Use logical properties for positioning
Removed deprecated custom CSS properties

Closes #1840
Testing Instructions

Notes to Reviewers

If possible it's better to defer removing the deprecated props until the next major


SSO for Microsoft Outlook using auth0

I am using auth0 to perform SSO for Microsoft Outlook.   When I click on button it gives error like
https://login.live.com/err.srf?lc=1033#error=invalid_request&error_description=The+provided+value+for+the+input+parameter+'redirect_uri'+is+not+valid.+The+expected+value+is+'https://login.live.com/oauth20_desktop.srf'+or+a+URL+which+matches+the+redirect+URI+registered+for+this+client+application.&state=g6Fo2SBhSmMtbWFoY0FpT3ZGcjVrcFZzX3hHNkxvNTVKNlJ4baN0aWTZMmdhRm8yU0JtZDJkdVZIWk1kV1kzZERoTWFtRkNVbXg2WDJWdFFqTjRUV2xETXpseFNno2NpZNkgZW9GMENjNFlyMEp5bm9UYXB6aEVwUUJsaVVXeUVDTkc.
I have setup callback url https://localhost:3000/signin-microsoft.
Please help to solve this problem.

We're going to need more information like:

The names and versions of nuget packages you're using.
How you configured this in code.
Steps to reproduce this error.

@Tratcher
So what I have done is client side SSO. I have used auth0. We have to create an app in Auth0. There we have to select type of application. In my case it is Single page application.  Once you create app over there they will provide you sample code. Download that code and they will tell you to perform some command to install and run that sample code. So when you run npm start command, sample code will start running and open app on localhost:3000. Once you get here, you will see login button. When you click on that button, it will redirect you to Auth0 screen where you will see option to login with microsoft account. Now click on that button and you will get this error.

If this is all about Auth0 then why are you reporting it here?

Oh sorry. I was looking for solution and found out that many people have posted same issue and I tried the solution but did not work out for me. So I thought this would be place where I can post. It is not about auth0. Gmail login is working perfectly, but when I try with microsoft it gives me error.

We can only help you here if you're using the Microsoft.AspNetCore.Authentication.MicrosoftAccount nuget package (.NET web applications).

Oh Ok. Sorry for that.


Not playing MIDI local files

How can I play midi files located in assets folder? Tried doing so but failed.

I get this error: DEMUXER_ERROR_COULD_NOT_OPEN: FFmpegDemuxer: open context failed


Working add/change list for tokens v3.x.x

Tracking potential token additions or changes for v3.x.x of the design tokens package.
Change

(Figma only) revert layout.borderRadius.default to layout.borderRadius.medium — see #386
add descriptions (in Figma and exported) for all tokens — see #350

Add (for discussion/investigation)

layout.padding.hair as a parallel to layout.margin.hair: we have cases in the codebase where we're using margin tokens to define padding because this token is missing
component-specific height/size variables for form fields and text inputs: as above, currently using other tokens in this case, but it feels like a broad/generic enough need that we should consider tokenising

@Philip-Cheung @ty2k please chime in with any additions or revisions you're thinking about for next release of the tokens package.

@bcgov/design-tokens v3.1.0<EMAIL_ADDRESS>


seedrng: remove environment variables

Now that we have the command line arguments, there's no need for the environment variables.

CC @williamh


Wallet Connect Issue: safe wallet - creating new wallet

Overview
creating new account gives an error after signing with the kk, wont allow the account to be created.
References and additional details

Acceptance Criteria
Should be able to create new wallet
Need By Date
No response
Screenshots/Mockups
No response
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Estimated effort
No response
Sponsor / Stakeholder
No response
Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

Attempting to create new safe account with trust wallet and still getting an error. this time says its to do with gas estimates.

Will try with native

closed with #5372


Add some locks so multiple writers are not failing all the time.

@damianh and the solution was so close

Might be good to test different kind of writes simultaneously, not just *VersionAny.

:boom: that's awesome!

Going to run some more load tests, thanks for the contrib.

Might be good to test different kinds of writes simultaneously, not just *VersionAny.

Yes I'll beef up the suite a lot.


Error Missing resultID or measurementID

I have noticed in clicking around pages in development mode that I often am triggering:
    if (!query.resultID || !query.measurementID) {
      // XXX maybe we should redirect to the listing in this case and show a toast
      throw Error('Missing resultID or measurementID')
    }

It's unclear to me why this is happening, but it happens very often.
@sarathms have you noticed this too?
If not I can share with you my ooni_home folder so you can see if you can reproduce it with that.

I haven't seen this since and I suspect it was actually only affecting my development environment.
I am closing this, but will reopen if I notice it again.


How to access a bucket using S3:// uri?

From the PR:
https://github.com/datafuselabs/databend/pull/4170/files#diff-dc7428e39de9915b0830549374e55e143995149f2a90303d38e4017d014d2fc2R79-R84
The file_location is s3://databend-external/t_ontime/t_ontime.csv, opendal stat will return Unexpected("s3://databend-external/t_ontime/t_ontime.csv").

Looks we should do a convert:
# s3://example-bucket/path/to/object
http(s)://example-bucket.s3.amazonaws.com/path/to/object
http(s)://s3.amazonaws.com/example-bucket/path/to/object


Update README.md: Add Issue link

Hi, this is a first-timers-only issue. This means we've worked to make it more legible to folks who either haven't contributed to our codebase before or even folks who haven't contributed to open source before.
If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!
We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝
If you have contributed before, consider leaving this one for someone new, and looking through our general help wanted issues. Thanks!
🤔 What you will need to know.
Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.
📋 Step by Step
🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!
📝 Update the file README.md in the image-builder-rpi repository (press the little pen Icon) and edit the line as shown below.
the line to be changed:-
-Check planning issue # 5 for other plans.
Replace # 5 with :-
Issue_number- [5]
Link- https://github.com/publiclab/image-builder-rpi/issues/5
Adding [tag] bracket followed by (link) without any space in between is used for adding links in Docs.
Refer https://help.github.com/articles/basic-writing-and-formatting-syntax/#links
💾 Commit your changes
🔀 Start a Pull Request. There are two ways how you can start a pull request:
If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
You can also edit files directly in your browser and open a pull request from there.
🏁 Done Ask in comments for a review :)
🤔❓ Questions?
Leave a comment below!
Is someone else already working on this?
We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

Hi, great!!! Thank you!

Hey! I can do this one :)

Alright I just went ahead and submitted the PR https://github.com/publiclab/image-builder-rpi/pull/25 😊
I hope that's ok. Thank you for the thorough guide ❤

please go ahead! thank you!
On Wed, Oct 3, 2018 at 11:33 AM Anabella<EMAIL_ADDRESS>wrote:

Hey! I can do this one :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/image-builder-rpi/issues/24#issuecomment-426682266,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABfJxTYcbBFOM-2cBwjK59LFeRjdCIeks5uhNiwgaJpZM4XFiIm
.

Hey, is it possible to do this please?

Hi, I believe this was solved in #25 -- but we'd love your help with another issue at https://code.publiclab.org!


Todo List App

Thank You!
What's the Play about?
It is a ReactJs based Todo List Web app
What ReactJS concept will be used to create this play?
useState and useEffect hooks will be used.

@nirban256 Are you doing this one?

yes


Alternative themes

Hi,
since galleria seems to be not continued anymore (http://support.galleria.io/discussions/problems/13502-galleria-site-not-working#comment_35916181) and colorbox misses some features, are there any other themes which could be recommended ?
Thanks, Thomas

This post is about the "Galleria Display service", not the Galleria script itself. Even if there is no recent activity on their github, maybe they will continue to maintain it.
I'm not aware of other sigal themes, but there are a lot of javascript gallery script which could be used, for example http://photoswipe.com/ seems cool.

ok, thanks


Verify @batch(1) - Virtual Network Gateway

Description
Test if @batch(1) is required for the PIP deployment.
If not - remove it
If it is required - keep it and add an inline documentation why it is needed
Applicable resource type:

Microsoft.Network/virtualNetworkGateways

1.) duplicate task for all modules that are affected
2.) if @batch(1) is needed, add a inline comment why that is the case

This is already done


Validate 'ml.update_job'

Ran into the MlCustomSettings issue I've seen before, not sure how to handle arbitrary fields plus a few known fields.
Hit a validation error where a value wasn't fitting into the MlAppliesTo enum but that value wasn't printed and when I checked out the workbench directory it was consistently empty, not sure what to do here?

Receiving an error that I don't know how to resolve since it looks correct to me?
  workbench/xpack-Test_update_job_2_request.json.test-d.ts:9:2
  ✖  9:2  Type { "groups": string[]; "description": string; "detectors": ({ "detector_index": number; "custom_rules": { "conditions": { "applies_to": string; "operator": string; "value": number; }[]; }[]; } | { "detector_index": number; "description": string; })[]; ... 5 more ...; "custom_settings": { ...; }; } is not assignable to type { allow_lazy_open?: boolean | undefined; analysis_limits?: MlAnalysisMemoryLimit | undefined; background_persist_interval?: string | number | undefined; ... 11 more ...; system_annotations_retention_days?: number | undefined; }.
  Types of property detectors are incompatible.
    Type ({ "detector_index": number; "custom_rules": { "conditions": { "applies_to": string; "operator": string; "value": number; }[]; }[]; } | { "detector_index": number; "description": string; })[] is not assignable to type MlDetector[].
      Type { "detector_index": number; "custom_rules": { "conditions": { "applies_to": string; "operator": string; "value": number; }[]; }[]; } | { "detector_index": number; "description": string; } is not assignable to type MlDetector.
        Type { "detector_index": number; "custom_rules": { "conditions": { "applies_to": string; "operator": string; "value": number; }[]; }[]; } is not assignable to type MlDetector.
          Types of property custom_rules are incompatible.
            Type { "conditions": { "applies_to": string; "operator": string; "value": number; }[]; }[] is not assignable to type MlDetectionRule[].
              Type { "conditions": { "applies_to": string; "operator": string; "value": number; }[]; } is not assignable to type MlDetectionRule.
                Types of property conditions are incompatible.
                  Type { "applies_to": string; "operator": string; "value": number; }[] is not assignable to type MlRuleCondition[].
                    Type { "applies_to": string; "operator": string; "value": number; } is not assignable to type MlRuleCondition.
                      Types of property applies_to are incompatible.
                        Type string is not assignable to type MlAppliesTo.

The test in the workbench:
expectAssignable<T.MlUpdateJobRequest>({
  "job_id": "jobs-crud-update-job",
  "body": {
    "groups": [
      "group-1",
      "group-2"
    ],
    "description": "Post update description",
    "detectors": [
      {
        "detector_index": 0,
        "custom_rules": [
          {
            "conditions": [
              {
                "applies_to": "actual",
                "operator": "gt",
                "value": 10
              }
            ]
          }
        ]
      },
      {
        "detector_index": 1,
        "description": "updated description"
      }
    ],
    "model_plot_config": {
      "enabled": false,
      "terms": "foobar"
    },
    "renormalization_window_days": 10,
    "background_persist_interval": "3h",
    "model_snapshot_retention_days": 30,
    "results_retention_days": 40,
    "custom_settings": {
      "setting3": "custom3"
    }
  }
})

actual is an entry in the AppliesTo enum, not sure what to do here?


Adds Google Drive support on Android

Closes #11

Thanks for the PR. Would you mind rebasing this on the current master and then create a PR against the master. This one is against the old PR. Thanks

Thanks for the PR. Would you mind rebasing this on the current master and then create a PR against the master. This one is against the old PR. Thanks

Ahhh my bad! New PR here - https://github.com/photon-sdk/photon-lib/pull/22

Ahhh my bad! New PR here - https://github.com/photon-sdk/photon-lib/pull/22


Update AUTHORS

@Elblinator in the future, please do not open branches in the repos directly, but instead use your own forks, as described in https://github.com/OpenSlides/OpenSlides/wiki/Development-organization#start-developing

I will delete the branch since the CI failed for some reason - please follow the guide to open a new PR from your fork.


Solving for initial value conditions and final value conditions

Hey @patrick-kidger , I recently started exploring diffrax (just realised how powerful diffrax is!, and kudos for the amazing work!). I was thinking if there was a way to solve the initial value problem and a final value problem, viz, a system of stiff ODE's solving for ${ y(0) = k1, y(T) = k2}$, (A boundary value problem instead of an initial value problem) any kind of reference would be much appreciated.

A standard approach for something like this would be a shooting method.

Hi @patrick-kidger, I am interested in implementing a collocation-based BVP solver, since for my particular application shooting methods do not work well. Is there current work along this direction for Diffrax?
Good references might be the MIRK4 solver in Julia or scipy's solve_bvp. Are you aware of any additional resources that might be useful? Would porting any of these methods to Diffrax be a herculian task?

So there's no current work in this direction, but I suspect it shouldn't be that hard! (I don't have any additional resources beyond the ones you link / the ones that are referenced in the scipy documentation.)
Right now, diffeqsolve specifically handles initial value problems. (E.g. it only accepts a y0.) So to solve a 2-point BVP we would want a new interface (biffeqsolve? :D ) that accepts a y1 as well. One could then imagine calling biffeqsolve(..., y0=y0, y1=y1, solver=MIRK4()), biffeqsolve(..., y0=y0, y1=y1, solver=Shooting(Tsit5())). Where appropriate this could internally lower to diffeqsolve + a nonlinear solver.
If you manage to stand up a prototype then I'd be interested to see the result. I'd be happy to see this either as a third-party library, or as a new interface in Diffrax.
(Regarding the nonlinear solver portion: for a prototype it'd probably be simplest to just use diffrax.NewtonNonlinearSolver, although that isn't necessarily well-adapted for this kind of nonlinear problem. At some point Soon™ I will have some more sophisticated handling for nonlinear solvers coming out, and we can then use that.)

Hi @patrick-kidger, I have partially adapted scipy.integrate.solve_bvp (without support for unknown parameters p), which you can see here. The collocation system is solved by a damped Newton method which alternates between full Newton iterations and fixed-Jacobian iterations. Right now it is standalone of Diffrax but it would be interesting to integrate as a new interface in Diffrax. Three comments/questions:

I have tried to use diffrax.NewtonNonlinearSolver to solve the collocation system (as a drop-in replacement in line 582) but it does not seem to work well for this particular problem. I suspect that the Newton method being damped is important. Thoughts?
The collocation system being solved is very sparse and scipy makes uses of this fact by using scipy.sparse.linalg.splu however using sparse solvers in Jax (jax.scipy.sparse.linalg.cg, jax.scipy.sparse.linalg.gmres) is slower than jax.scipy.linalg.lu_factor for moderately large matrices.
Scipy's implementation iteratively increases the mesh nodes based on the residuals. I suppose that this behavior is not easily batchable unless the mesh is always expanded by the same number of nodes at each iteration. Thus it might be more performant to use a fixed but relatively large mesh rather than starting with a small mesh and iteratively expanding it. Thoughts?

I am not very well-versed in Jax so I am happy to take feedback :)

I've just had a look over. I think it looks really good!
(Also you say you're new to JAX, but many of your points -- e.g. batching the mesh -- are pretty advanced things to spot.)
To answer your questions:

Damped Newton: I agree, this is probably important. The current Newton implementation is a simple Newton method or Chord method, as that is all that's needed for implicit RK solvers. There will soon be a much more sophisticated system in place here; it would then be easy to expand the available nonlinear solvers to include Newton with damping, backtracking etc.

Sparse: when you tried using the sparse solvers, did you specify the matrix as function describing the matrix-vector product, or as a materialised matrix? The former should probably be much more efficient for this problem (at least on the forward pass, at least in terms of runtime-without-compiletime). If it was a materialised matrix, was it as a sparse or as a dense matrix?
For what it's worth, JAX's support for sparse arrays is still pretty limited. (I suspect this is still at least a couple of years away from being anything comprehensive.) Both JAX and Diffrax place much greater focus on dense arrays.
I do note that the system being solved should exhibit quite a lot of structure (just staring at the code I think it's block tridiagonal+dense?) One possible path forward is to use a custom linear solver that exploits this property. (This is also something that should be a lot easier with the soon-ish improvements to the linear and nonlinear solvers.)

Mesh nodes: the usual way to handle batching for this kind of variable-size computation is to use a computational structure that does as much work as the "most demanding" batch element.
To give an example: vmap(lax.while_loop) works by iterating until every batch element has completed its computation; all of the other batch elements will still have their body_fun evaluated, but the result of the computation will simply be thrown away.
Here, then: probably what you want to do is to something like nodes_added = unvmap_max(nodes_added). Here unvmap_max is a function which is just the identity when run without vmap, but takes the maximum over all vmap'd dimensions when run with vmap. It's available at equinox.internal.unvmap_max. The "most demanding" batch element will get as many nodes as it requires, and the other batch elements will just be evaluated on a few more nodes than they really need. (Actually, I can see a bit more work is required here, as insert_1 and insert_2 are dynamically-sized arrays at the moment, and you'll need to find a way to express the computation using statically-sized arrays, but hopefully you get the idea.)

Other comments:

Right now solve_bvp isn't really jit'able, as it still has a Python while loop at the top level.
This has a couple of issues: (a) it introduces a lot of overhead relative to doing the whole thing in JAX and then jit'ing solve_bvp; (b) it breaks composability with the rest of JAX i.e. a downstream user can't use solve_bvp in an arbitrary spot in their code. (Admittedly, if you're the only downstream user right now: maybe you don't mind!)
Anyway, I'd recommend switching out this Python while loop with e.g. lax.while_loop, and making the other appropriate adjustments, e.g. no print statements. (It's for these kinds of reasons that diffeqsolve has a totally different API to solve_ivp: JAX's programming model is actually pretty different to NumPy, despite the similarity at the jax.numpy level.)
You might rightly complain that lax.while_loop isn't reverse-mode autodifferentiable. (a) I have a reverse-mode autodifferentiable version of while_loop coming out in the next few days, as a drop-in replacement; (b) it's not clear to me that you actually want to directly differentiate the iterations anyway: I'm guessing there's probably e.g. an implicit representation of the adjoint (c.f. diffrax.ImplicitAdjoint) that would be a more efficient representation of the tangent/cotangent operations anyway.

I note that you call fun several times. Do be aware that each separate time you call fun, JAX will need to trace and compile it afresh (it can't know that it's already seen fun from earlier), and this can start to increase compile times.
Up to a certain point this is inevitable (I think diffeqsolve traces through the vector field ~5 times or so), but if you do see ways to minimise the number of times that fun is called then this can be useful.

WDYT?

Hi @patrick-kidger, thank you so much for the detailed feedback! I am stuck trying to make solve_bvp jittable by swapping out the Python while loop at the top level for a lax.while_loop. As far as I understand, lax.while_loop requires val to have fixed shape, however we would like to expand the mesh at every iteration (i.e., x and y to have increasing size). I thought that one solution would be to let x and y have static size max_number_nodes, where only the first n_mesh_nodes are passed to the Newton solver (i.e., newton_solver.solve(y[:n_mesh_nodes, x[:n_mesh_nodes])), and n_mesh_nodes is increased at every iteration. However, it is not possible to index by a dynamic n_mesh_nodes (even slize_sizes of lax.dynamic_slic must be static). Do you have any suggestions?

Right; JAX unfortunately has poor support for dynamic shapes.
I think I can see a way to make this work, but it's pretty tricky.
To start, let's consider doing a vector-vector dot product with dynamic shapes. This can be done by representing the vectors using statically-sized buffers that we only partially fill, and then using a lax.while_loop to perform the actual computation:
def dot(a: Float[Array, "n"], b: Float[Array, "n"], size: Int[Array, ""]):
    # Only a[:size] and b[:size] should be filled; the rest is padding.
    def cond_fun(carry):
        step, _ = carry
        return step < size

    def body_fun(carry):
        step, val = carry
        val = val + a[step] * b[step]
        step = step + 1
        return step, val
    _, out = lax.while_loop(cond_fun, body_fun, (0, 0))
    return out

We can now upgrade that to a matrix-vector product like so:
def matvec(A: Float[Array, "n n"], b: Float[Array, "n"], size: Int[Array, ""]):
    # Only A[:size, :size] and b[:size] should be filled; the rest is padding.
    def cond_fun(carry):
        step, _ = carry
        return step < size
    def body_fun(carry):
        step, val = carry
        val = val.at[step].set(dot(A[step], b, size))
        step = step + 1
        return step, val
    out = jnp.zeros_like(b)
    _, out = lax.while_loop(cond_fun, body_fun, (0, out))
    return out

and with this we can move up to getting linear solvers, some of which only need matrix-vector products (without e.g. doing a LU decomposition of the entire matrix, which may be potentially large due to all the padding)
def linear_solve(A: Float[Array, "n n"], b: Float[Array, "n"], size: Int[Array, ""]):
    # Only A[:size, :size] and b[:size] should be filled; the rest is padding.
    out, _ = jax.scipy.sparse.gmres(ft.partial(matvec, A, size=size), b)
    return out

and with that we can then build a nonlinear solver callable asnewton_solver.solve(y, x, n_mesh_nodes), which uses the above linear solver. (Exercise for the reader.)
Obviously threading all of that through is less-than-ideal. Ultimately this is case in which we're bumping up against the limitations of JAX's model of computation. At some point there is a plan that we'll get dynamic shapes in JAX, but I don't think that's going to happen any time soon. I'm sorry I don't have something more positive to say!

This is incredibly cool to see. I had a quick look over and your implementation looks good to me!

It's great that you managed to get JIT and vmap working.
Likewise, I'm glad to see the succes of the BABD solver. Once the aforementioned linear/nonlinear package comes out then this would be a great match with that. (I've looked at your implementation and it should be compatible!)

In terms of reducing the number of times the ODE function is called.

In this function, then vmap(fun) is called twice in quick succession. You might be able to package that up into a length-2 scan, so that it is only traced once. (This admittedly reduces readability.)
backtrack_cost (which calls fun) is traced twice here, once at initialisation and once again in the step. It might be possible to combine this into just one call, with some appropriate dummy initialisation of the variables. For something a little similar see the Newton implementation in Diffrax itself -- this uses a step counter to ensure that we make the minimum number of required steps for our diffsize and diffsize_prev variables to actually be meaningful, and just initialises them to dummy zeros outside the loop.

Regarding backpropagation through all of this: I can now make good on my earlier promise. Equinox now has a reverse-mode autodifferentiable while loop available as equinox.internal.while_loop(..., kind="checkpointed"). (The only real footgun is to make sure to use its buffers argument with anything that you update in-place (.at[].set()), but I don't think you're using that so you should be safe.) No idea if this is really the correct thing to do of course, as I said before there might be more elegant ways to differentiate a BVP solve.
If you manage to dynamically refine the mesh as per my previous message then I'd be very impressed; that looks pretty hellish to get working all the way through!
Integration into Diffrax: yup, I think waiting on the new linear/nonlinear solvers makes most sense. Once that happens I'd definitely be interested in considering that.

(Regarding the nonlinear solver portion: for a prototype it'd probably be simplest to just use diffrax.NewtonNonlinearSolver, although that isn't necessarily well-adapted for this kind of nonlinear problem. At some point Soon™ I will have some more sophisticated handling for nonlinear solvers coming out, and we can then use that.)

Coming back to this -- we (finally!) released Optimistix, as an Equinox-based library for nonlinear optimisation.
As that's such an important part of BVP solvers, perhaps it will be of interest to those here.


Check if user has a correct cluster-cidr and service-cidr config

Signed-off-by: Manuel Buil<EMAIL_ADDRESS>

Proposed Changes

This PR has two changes:
1 - It removes the nature of the node's IP to decide if we should enable IPv6. It does not matter if the node is ipv6, ipv4 or dual-stack to enable ipv6 parameters
2 - Check if cluster-cidr and services-cidr share the same IP version. Otherwise, there are strange errors
Types of Changes

"New feature" ==>  avoids user shooting himself/herself in the foot
Verification

Linked Issues

https://github.com/k3s-io/k3s/issues/5491
User-Facing Change

Further Comments

Waiting for code freeze to end....


Update Nvidia-ROS2-Projects.rst

Updated documents for humble isaac ros development

This looks OK to me now, thanks for iterating.
Should we port this to any of the other branches? That is, are these projects only supported on Humble, or do they also support Galactic, Foxy, and Rolling?

Isaac ROS is only tested on Humble.


feat: generate ContentExerpt from entry with more comment tag

As-is
To-be

Thank you for your contribution, but I'm sorry I can't merge it since this feature doesn't suit the current UI design very well.


Linting: Force splitting variable declaration for initialized vars

Eslint will now warn if declaring multiple variables in the same statement, except if all of them are uninitialized. For example, this is still valid:
var testContainer, para0, para1, para2;
(There are a lot of these in the test specs and splitting them up isn't necessarily better imo)

I'm not so sure about this, but since very little of Bliss had to be changed to follow it, eh, merging.
Thanks!

I probably misinterpreted the conversation: https://github.com/LeaVerou/bliss/pull/209#issuecomment-343310691. Anyway, don't be afraid to reject my PR's in cases like this.

To clarify that comment, I meant that things like this should be valid:
var a = 5, b = 8, c;

but things like this should not be:
var a = 5,
    b = 8,
    c;

I see! The one-var rule doesn't allow this distinction I'm afraid.


[FLINK-20096][docs] Clean up PyFlink docs

What is the purpose of the change
This cleans up the PyFlink documentation. Mostly fixing English grammar and adding additional cross-links. I've also added an overview page to the section.

cc @morsapaes

@morsapaes @dianfu thank you both for the review. I've tried to address all the comments, please take another look.

Updated overview for reference

Looks good from my side, thanks Seth!

Grazi, Merging


Nmap caps

This is an attempt to deal with #123

This is going to be open for a little while as I don't have time to test it out tonight and I will be travelling the next several days. From a glance, it looks good. Thanks for investigating this.

This is going to be open for a little while as I don't have time to test it out tonight and I will be travelling the next several days. From a glance, it looks good. Thanks for investigating this.

No problem! Safe travels.


I cant't install brackets from packge deb in ubuntu 16.04

https://github.com/adobe/brackets/wiki/Brackets-Linux-Guide

It is not bug, Its feature. I understand.

Hi, if you took a time to quickly search issues for libgcrypt you'd see that this is an issue that has been reported on 2014 (https://github.com/adobe/brackets/issues/10255) and so far, no-one that'd be able to fix this has been found. You're free to open a PR of course. Thanks


Memory leak when constructed from numpy array

This code piece can cause a memory leak in my computer:
while True:
    glm.vec3(np.zeros(3))

In addition, glm.vec3(*np.zeros(3)) is OK, but glm.vec3(*np.zeros(3, dtype=np.float32)) also causes the memory leak.
I tested with PyGLM 2.5.3 and NumPy 1.20.2 on Windows 10.

Hey there (:
Thank you very much ^^
You've actually found two different memory leaks.
glm.vec3(np.zeros(3)) creates a memory leak, because the buffer given by numpy is never released.
glm.vec3(*np.zeros(3, dtype=np.float32)) leaks, because the number objects (numpy.float32 objects) aren't properely dereferenced.
Then again, glm.vec3(*np.zeros(3)) doesn't leak, because it passes Python floats to the vec3 function, instead of numpy floats. And those are handled differently.
Both leaks should be fixed now.
Cheers
--Zuzu_Typ--


feat(material/form-field): Ability to support custom error message components inside a form field

Adds an ability to use custom error components tagged with [matError] attributes inside a form field. This is useful when a reusable custom error message template is needed for form fields.
Example:
<mat-form-field>
  <mat-label>Label</mat-label>
  <input matInput>
  <custom-error matError>Error message</custom-error>
</mat-form-field>

(It was possible, as mat-error is a directive. You just had to create a component with an attribute selector)


pull request for e2e test at 12/04/2016 22:56:03

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


eunit context cleanup times out while cleaning up os daemons

Expected and Current Behaviour
Sometimes, the eunit test harness fails to complete context cleanup. In this case, it fails finishing off the couchdb_os_daemons_tests test should_spawn_multiple_daemons.
https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/15/pipeline/49
Makefile output:
module 'couchdb_os_daemons_tests'
  OS Daemons tests
    couchdb_os_daemons_tests:107: should_check_daemon...ok
    couchdb_os_daemons_tests:113: should_check_daemon_table_form...ok
    couchdb_os_daemons_tests:120: should_clean_tables_on_daemon_remove...[0.548 s] ok
    couchdb_os_daemons_tests:127: should_spawn_multiple_daemons...[0.607 s] ok
    undefined
    *** context cleanup failed ***
**in function test_util:stop_sync_throw/4 (src/test_util.erl, line 161)
in call from couchdb_os_daemons_tests:teardown/2 (test/couchdb_os_daemons_tests.erl, line 58)
**throw:{timeout,os_daemon_stop}

Application config was left running!
Application couch_epi was left running!
Application ioq was left running!
  undefined
  Application config was left running!
*** context setup failed ***
**in function meck_proc:start/2 (src/meck_proc.erl, line 96)
  called as start(couch_stats,[passthrough])
in call from test_util:mock/1 (src/test_util.erl, line 245)
in call from test_util:'-mock/1-lc$^0/1-0-'/1 (src/test_util.erl, line 238)
in call from test_util:start/3 (src/test_util.erl, line 226)
in call from couchdb_os_daemons_tests:setup/1 (test/couchdb_os_daemons_tests.erl, line 47)
**error:{already_started,<0.10686.1>}

[done in 7.158 s]

Possible Solution
Increase the timeout for couchdb_os_daemons_tests:teardown/2.

+1 for increasing the timeout it is 1s only

https://github.com/apache/couchdb/compare/fix/571/increase-test-timeout?expand=1

The patch here didn't work - see #583.

Took a look at this. Part of shutdown code is in terminate callback in couch_os_daemons module. In terminate each port is sequentially stopped. When stopping, it spawns an os process to run "kill -9 " then port is also closed with "port_close". Forking another process and the sequential part could take a while I suppose. In this particular case we can probably wrap the test teardown code iin a try/except and then if cleanup fails issue an exit(OsDPid, kill) signal.
However speaking of timing, ran this on my laptop (5 year old Thinkpad, 1.9Ghz, Ubuntu 17.04) and the should_spawn_multiple_daemons. test finishes in [0.006 s] seconds. From the log above I see it finished in [0.607 s] on our test runner. That's over a 100x slowdown. It's not scientific, of course, but even so seems like a significant difference. Wonder if there is any way to guarantee a minimum performance profile in the test runners, or least abandon a test run if we see it's running at the speed of a pocket calculator.

Look at the rest of the test run logfile - most of the tests complete pretty speedily, certainly not 100x slower. We just have occasional slowdowns, I guess, possibly related to process execution. The environment is largely out of our control, unless Cloudant is prepared to donate hosts for full control by the ASF on which we can run our Dockerized tests.
If the entire test run takes > 45 minutes, we abort the test run. Our tests should complete in 20 minutes. I think that's enough safeguarding.

Yap, obviously it's not a sustained 100x slowdown but there are either random spikes or like you said related to specific operations (forking, reading from disk, socket stuff maybe...).
Besides getting dedicated hosts with predictable performance profile wonder if Travis has anything to mitigate this. Say if test fails retry one more time. Or take the best of 5 runs.

Travis doesn't do "best of 5" unless you explicitly enable it. And to my mind that's just sweeping the problem under the rug.....

Haven't seen this again in a bit. Closing for now...


replased debugger nuget packages by source code

Implementation of https://github.com/Microsoft/vscode-mono-debug/issues/36

It fails because nobody init and updates git submodules.
@weinand, is make file nice place to execute: "git submodule init" and "git submodule update" ?

Build is failed becase of issue fixed in PR https://github.com/Microsoft/vscode-mono-debug/pull/40


Genre separator

Hi there,
I recently updated my library with new genre-tags and the tool I used, uses ";" instead of "," as a separator between multiple genres. I only realized afterwards, that swingmusic is not able to split the genre with ";" and instead merges them.
Example:
Hip Hop; Rap

is parsed and shown as
"Hip Hoprap"
where as
Hip Hop, Rap

Is correctly separated.
In the settings you can customize artist separators, I would like to suggest to introduce the same customization for the genre-tag.
Thank you so much for your work, swingmusic is a great piece of work.

Hi @platypusgit
The genres are split using the following characters:
/ , & ;

Somehow ; does not work on your case and I don't know why. But I agree we should have allow users to customize genre separators like we do for artists.
We'll work on this in the future.
Thank you.

Hi @cwilvx,
thank you so much.
I dug through other issues here on github and it might also be connected to:
https://github.com/swingmx/swingmusic/issues/184

Hi @platypusgit
Just in case it's a problem with the underlying tag reading library we use, I've updated to the latest released version (Tinytag v1.10.1).