RHBPMS-4220: Added RoleRegistry and registered principals that come from Keycloak remote logins as roles.

Depends on https://github.com/uberfire/uberfire/pull/509

Hi @dgutierr , added tests here as well! Thanks!

+1 Well done!

@romartin @dgutierr This PR is failing to compile with JDK1.6 (required for 0.9.x). Please see https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/uberfire-extensions-0.9.x/26/console

@manstis @romartin after looking into this, it doesn't look like a JDK version issue at all. It looks like when jenkins build uf-ext 0.9.x it didn't pick up the right snapshots/sources from uf 0.9.x. I can't reproduce the problem locally.

@manstis @romartin in fact, uf-ext is green on jenkins too now: https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/uberfire-extensions-0.9.x/

@dgutierr @manstis @csadilek yes guys, I ran the build locally using the full profile ( which checks jdk6 verifications ) and just tried againnow, it builds fine as well. Thanks and sorry if any inconveniences!!


About batch_size

❓ Questions & Help

Hi, I want to know how to use batch, if the shape of x in def forward(self, x, edge_index) is [batch_size, node_num, input_feature]. the shape of x is [node_num, input_feature] in cora.py? How to use batch_size?
Thank you!

We support mini-batches by concatenating node features in the node dimension and stacking adjacency matrices diagonally (see here). So you can either use the PyG provided DataLoader or manually convert your data to this kind of format. In case you want to use the same edge_index for all your batched node features, this issue might be of interest to you.

Those are useful information, but I am doing the graph generation problem. So the edge_index and x vary in each epoch. I can't use DataLoader to pre-define the mini-batches. Thanks to your MetaLayer, I implemented a batch-based MetaLayer which does the edges' and nodes' information exchanging in every batch-dim with some trick.
class MetaLayer(nn.Module):
    def __init__(self, n_in, n_out, e_h, n_h):
        super(MetaLayer, self).__init__()
        self.edge_mlp = Sequential(Linear(2 * n_in, e_h), ReLU())
        self.node_mlp_1 = Sequential(Linear(e_h + n_in, n_h), ReLU())
        self.node_mlp_2 = Sequential(Linear(n_h, n_out), ReLU())

    def _n2e_e2e(self, src, dest):
        out = torch.cat([src, dest], -1)
        out = self.edge_mlp(out)
        return out

    def _e2n_n2n(self, x, edge_index, edge_attr, edge_value):
        src, dest = edge_index
        out = torch.cat([x[:,dest], edge_attr], dim=-1)
        out = self.node_mlp_1(out)
        input = out * edge_value[None,:,None]
        out = scatter_add(input, dest, dim=1, dim_size=x.size(1))
        out = self.node_mlp_2(out)
        return out

    def forward(self, x, edge_index, edge_value):
        edge_src, edge_dest = edge_index
        edge_attr = self._n2e_e2e(x[:,edge_src], x[:,edge_dest])
        x = self._e2n_n2n(x, edge_index, edge_attr, edge_value)
        return x

the shape of x is [batch_size, node_num, input_feature]. From the experimental results, It works well. But I want to make it compatible with your MassagePassing framework, then I can using the model in PyG, like GAT, GraphSAGE, etc.
I considering several solutions, such as converting the x [batch_size, node_num, input_feature] to [node_num, input_feature], the batch_size is analogy to sub-graph which will be used to construct a big graph (mini-batch) along the diagonal, just as the method mentioned here. But I don't know whether it's derivable? And how do people use PyG to do graph generation problem? Thank you!

I would go with your proposed solution, something like:
edge_index = edge_index.view(2, 1, -1).repeat(1, x.size(0), 1) + torch.arange(x.size(0)).view(1, -1, 1) * x.size(1)
edge_index = edge_index.view(2, -1)
x = x.view(-1, num_features)
x = ... # use any PyG operator now
x = x.view(batch_size, num_nodes, num_features)

Concerning graph generation: Graph generation is a difficult problem and is mostly tackled by using dense adjacency matrices where edge weights denote the probability of an edge. You can do this for sparse adjacency matrices too, where gradients only pass through edge_value, not edge_index.

Cool! I will try it! Thank you!

I would go with your proposed solution, something like:
edge_index = edge_index.view(2, 1, -1).repeat(1, x.size(0), 1) + torch.arange(x.size(0)).view(1, -1, 1) * x.size(1)
edge_index = edge_index.view(2, -1)
x = x.view(-1, num_features)
x = ... # use any PyG operator now
x = x.view(batch_size, num_nodes, num_features)

Concerning graph generation: Graph generation is a difficult problem and is mostly tackled by using dense adjacency matrices where edge weights denote the probability of an edge. You can do this for sparse adjacency matrices too, where gradients only pass through edge_value, not edge_index.

What do you think about how to use edge_value in PyG operator now.

Can you elaborate?

As you know, edge_value[1,E] has the same length like edge_index[2, E], E is the edge number, edge_value holds the connection probability. the generated adjacency like:
array([[0.6710922 , 0.88077555, 0.76953579, 0.74592817, 0.38684827],
       [0.67407643, 0.05540686, 0.07848255, 0.79545276, 0.58294445],
       [0.60898092, 0.55322303, 0.93865896, 0.0118191 , 0.55793872],
       [0.15374984, 0.92119851, 0.93366929, 0.2216791 , 0.03274837],
       [0.15263654, 0.15071275, 0.6112376 , 0.59826883, 0.80632444]])

So, the element in edge_value is its corresponding connection probability in adjacency.
Then I want to do this operation. let the node feature multiply the connection probability.
input = x * edge_value[None,:,None]
x = scatter_add(input, dest, dim=1, dim_size=x.size(1))

Another question, as you mentioned above, this operation can make the indices does not mix up. but according to my experiments, the edge_value is actually the gradients' source, not edge_index? from what I understand, the most examples the PyG provided do not care about whether the edge_index can be derivable or not, because in node classification and link prediction, edge_index is the data source, not a intermediate step.
edge_index = edge_index.view(2, 1, -1).repeat(1, x.size(0), 1) + torch.arange(x.size(0)).view(1, -1, 1) * x.size(1)

https://arxiv.org/abs/1812.11482v2 is our previous work, and I am working on enlarge the graph. I want to replace the dynamics learner with the GNN based on MessagePassing. the gradient should be able to pass through the network converter (dense [batch_size, node_num, input_feature] to sparse [batch_size * node_num, input_feature] )

Yes, gradients will we propagated through edge_value, not edge_index. So to convert your batch-wise scenario to PyG, you need to repeat edge_value batch_size times:
edge_value = edge_value.view(-1, 1).repeat(batch_size, 1).view(-1)

Can it be simply merged into x by x * edge_value after repeat before feed in GCN forward?

No, those tensors have different shape.

Yes, I see. But how do x coalesce edge value?

In the message function of the PyG operators. For GCNConv, simply pass in the edge_value to the forward call: conv(x, edge_index, edge_value)

Wow, I will check it closely. Do GAT and GrapSAGE have the same operation?

Sadly no, these operators are only defined for unweighted graphs. I suggest copy pasting those operators and integrating the edge_weight by yourself (in analogy to GCNConv).

I get it. I will try. Thank you sincerely!


As an admin, I would like Midas to automatically sign up all people creating new accounts to GovDelivery and Salesforce

We send all our marketing info out through GovDelivery.  Since I don't want people to have to signup 2 places it would help me save a very manual step of adding new account inforation to GovDelivery and Salesforce.

closing, since we're now tracking in midas repository


add a factory method for AnyType

instead of new AnyType<MyType>(){} everywhere, just use Any.type()

Wow - I'm surprised that works. I thought that the only way to get the semi-reified type was the way I did it. I'll need to test this in some edge cases.

This does not work. Try this:
Any<List<String>> anyList1 = Any.type();
Any<List<String>> anyList2 = new Any<List<String>>(){};
System.out.println(anyList1.getRawType());
System.out.println(anyList2.getRawType());

There's no workaround that I know of.

Oops, poor Java type system. Let me see if there I can find a workaround.

It's erasure. A 1000 deaths for those who decided erasure was OK.

no workaround, :(

There's a special place in Hell for erasure :(


Pagination and grid cleanup

[x] pagination
[ ] grid fixup for listings & pagination
[ ] #172

Spin off issue for the unchecked items #177


Install firebase_database fails

I can't install firebase_database.
Current pubspec.yml:
...

dependencies:
  flutter:
    sdk: flutter

  # The following adds the Cupertino Icons font to your application.
  # Use with the CupertinoIcons class for iOS style icons.
  cupertino_icons: ^0.1.0

  # firebase
  firebase_core: "^0.1.0"
  firebase_database: "0.4.0"
  firebase_auth: "^0.5.1"

dev_dependencies:
  flutter_test:
    sdk: flutter

...

When I install the packages I get:
>flutter packages get -v
[  +64 ms] [C:\Users\Fabo\Documents\Entwicklung\flutter\] git rev-parse --abbrev-ref --symbolic @{u}
[ +175 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/beta
[        ] [C:\Users\Fabo\Documents\Entwicklung\flutter\] git rev-parse --abbrev-ref HEAD
[ +132 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] beta
[        ] [C:\Users\Fabo\Documents\Entwicklung\flutter\] git ls-remote --get-url origin
[ +111 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[        ] [C:\Users\Fabo\Documents\Entwicklung\flutter\] git log -n 1 --pretty=format:%H
[ +138 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[        ] 3ea4d06340a97a1e9d7cae97567c64e0569dcaa2
[        ] [C:\Users\Fabo\Documents\Entwicklung\flutter\] git log -n 1 --pretty=format:%ar
[ +121 ms] Exit code 0 from: git log -n 1 --pretty=format:%ar
[        ] 4 weeks ago
[        ] [C:\Users\Fabo\Documents\Entwicklung\flutter\] git describe --match v*.*.* --first-parent --long --tags
[  +96 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v0.1.5-0-g3ea4d0634
[ +192 ms] Running "flutter packages get" in mira...
[   +6 ms] [C:\Users\Fabo\Documents\Entwicklung\mira\] C:\Users\Fabo\Documents\Entwicklung\flutter\bin\cache\dart-sdk\bin\pub.bat --verbosity=warning get --no-precompile
[+1624 ms] Package firebase_database has no versions that match 0.4.0 derived from:
[   +1 ms] - mira depends on version 0.4.0
[  +82 ms] "flutter get" took 1.756ms.
pub get failed (1)

#0      throwToolExit (package:flutter_tools/src/base/common.dart:28)
#1      pub (package:flutter_tools/src/dart/pub.dart:164)
<asynchronous suspension>
#2      pubGet (package:flutter_tools/src/dart/pub.dart:100)
<asynchronous suspension>
#3      PackagesGetCommand.runCommand (package:flutter_tools/src/commands/packages.dart:74)
<asynchronous suspension>
#4      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:290)
<asynchronous suspension>
#5      FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:228)
<asynchronous suspension>
#6      CommandRunner.runCommand (package:args/command_runner.dart:194)
<asynchronous suspension>
#7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:286)
<asynchronous suspension>
#8      CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:109)
#9      new Future.sync (dart:async/future.dart:222)
#10     CommandRunner.run (package:args/command_runner.dart:109)
#11     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:166)
#12     run.<anonymous closure> (package:flutter_tools/runner.dart:90)
<asynchronous suspension>
#13     AppContext._run (package:flutter_tools/src/base/context.dart:76)
<asynchronous suspension>
#14     AppContext.runInZone.<anonymous closure> (package:flutter_tools/src/base/context.dart:66)
#15     _rootRun (dart:async/zone.dart:1126)
#16     _CustomZone.run (dart:async/zone.dart:1023)
#17     runZoned (dart:async/zone.dart:1501)
#18     AppContext.runInZone (package:flutter_tools/src/base/context.dart:65)
#19     run (package:flutter_tools/runner.dart:61)
<asynchronous suspension>
#20     main (package:flutter_tools/executable.dart:48)
<asynchronous suspension>
#21     main (file:///C:/Users/Fabo/Documents/Entwicklung/flutter/packages/flutter_tools/bin/flutter_tools.dart:16)
#22     _startIsolate.<anonymous closure> (dart:isolate-patch/dart:isolate/isolate_patch.dart:277)
#23     _RawReceivePortImpl._handleMessage (dart:isolate-patch/dart:isolate/isolate_patch.dart:165)

[  +58 ms] ensureAnalyticsSent: 48ms
[   +3 ms] exiting with code 1

Flutter doctor gives me:
>flutter doctor -v
[√] Flutter (Channel beta, v0.1.5, on Microsoft Windows [Version 10.0.16299.309], locale de-DE)
    • Flutter version 0.1.5 at C:\Users\Fabo\Documents\Entwicklung\flutter
    • Framework revision 3ea4d06340 (4 weeks ago), 2018-02-22 11:12:39 -0800
    • Engine revision ead227f118
    • Dart version 2.0.0-dev.28.0.flutter-0b4f01f759

[√] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at C:\Users\Fabo\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-P, build-tools 27.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)

[√] Android Studio (version 3.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)

[√] VS Code
    • VS Code at C:\Program Files (x86)\Microsoft VS Code
    • Dart Code extension version 2.10.0

[√] VS Code (version 1.21.0)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Dart Code extension version 2.10.0

[√] Connected devices (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 8.1.0 (API 27) (emulator)

• No issues found!

try switching to dev channel or try an older version of the firebase_database dependency

It's probably because the firebase packages have been updated to require more recent Flutters (with Dart 2). As @zoechi says, if you loosen the version constraint, or update to a more recent flutter, it should work fine.

Thank you for the help.
I tested which versions pub would resolve by setting:
firebase_auth: any
firebase_core: any
firebase_database: "0.4.1" // latest
The configuration that was resolved and works:
firebase_auth: "0.5.1"
firebase_core: "0.0.7"
firebase_database: "0.4.1"
I hope this helps people in the future.


Refactor the togglebutton from float layout to flex

In the setting page, there are buttons that have svg in them, and these buttons use float to position the svg.

Although it looks fine in normal layout, it is broken in RTL layout. The position is reverted

Here is the CSS file https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/src/components/helpers/toggle-button.css
And here is the HTML file, if you needed https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/src/components/helpers/toggle-button.tsx
Refactoring it to flex should fix the weird positioning in the RTL layout.

Additional Context

Why not Grid?

Browsers has different way of rendering the SVG size with Grid, although I think the height and weight will render the SVG with the desired look, it may change based on how browser decided how to render SVG in the future.
If you want to create a grid that works in safarri, firefox and chrome, go for it.

Do I need to be mindful of how it looks in the RTL layout?

No, refactoring it to flex is good enough, if there is weird behavior accruing in the RTL layout, I will fix it in another PR.

If you would like to fix this issue, please make sure you read our guidelines for contributing, we prioritize contributors following the instructions in our guides. Join us in our chat room or the forum if you need help contributing, our prolific contributors will guide you through this.

Hey could you please assign this issue to me i would like to make the necessary changes from float to flex

We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute, and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum

Hi, I am looking to work on this issue,
I am not able to replicate the issue. Can anyone tell me how can I switch to Arabic/RTL language here?

HEY, I want to work on this issue , please assign me

hello sir , can you assign me this issue to me?


Reference assemblies fail to include nullability attributes

Describe the Bug
Reference assembly source code does not include nullability attributes which are required parts of the signatures. For example, these methods failed to include the [NotNullWhen(true)] attribute on the parameters:
https://github.com/dotnet/source-build-reference-packages/blob/4163a212b06740e791c3dfe7ea1258565229af07/src/referencePackages/src/microsoft.codeanalysis.workspaces.common/3.7.0/lib/netstandard2.0/Microsoft.CodeAnalysis.Workspaces.cs#L231-L235

https://github.com/dotnet/roslyn-analyzers/pull/6705 disables CS8603 in source build scenarios due to this omission.

FYI @ViktorHofer, @ericstj

I did regenerate this package to validate it was up to date with respect to the latest generator changes.  The code (*.cs) is up-to-date.  There are a few csproj/nuspec updates that are irrelevant to this issue.


Travis CI hit by attrs breakage

https://travis-ci.org/dbader/pytest-mypy/jobs/602328209#L1267
1252Traceback (most recent call last):
1253  File "/home/travis/build/dbader/pytest-mypy/.tox/py35-pytest4.0-mypy0.570/bin/py.test", line 11, in <module>
1254    sys.exit(main())
1255  File "/home/travis/build/dbader/pytest-mypy/.tox/py35-pytest4.0-mypy0.570/lib/python3.5/site-packages/_pytest/config/__init__.py", line 58, in main
1256    config = _prepareconfig(args, plugins)
1257  File "/home/travis/build/dbader/pytest-mypy/.tox/py35-pytest4.0-mypy0.570/lib/python3.5/site-packages/_pytest/config/__init__.py", line 182, in _prepareconfig
1258    config = get_config()
1259  File "/home/travis/build/dbader/pytest-mypy/.tox/py35-pytest4.0-mypy0.570/lib/python3.5/site-packages/_pytest/config/__init__.py", line 153, in get_config
1260    pluginmanager.import_plugin(spec)
1261  File "/home/travis/build/dbader/pytest-mypy/.tox/py35-pytest4.0-mypy0.570/lib/python3.5/site-packages/_pytest/config/__init__.py", line 522, in import_plugin
1262    __import__(importspec)
1263  File "/home/travis/build/dbader/pytest-mypy/.tox/py35-pytest4.0-mypy0.570/lib/python3.5/site-packages/_pytest/tmpdir.py", line 25, in <module>
1264    class TempPathFactory(object):
1265  File "/home/travis/build/dbader/pytest-mypy/.tox/py35-pytest4.0-mypy0.570/lib/python3.5/site-packages/_pytest/tmpdir.py", line 35, in TempPathFactory
1266    lambda p: Path(os.path.abspath(six.text_type(p)))
1267TypeError: attrib() got an unexpected keyword argument 'convert'

https://github.com/pytest-dev/pytest/issues/5900

This appears to affect pytest3.4 also:
py38-pytest3.4 create: /Users/davidmtucker/Projects/pytest-mypy/.tox/py38-pytest3.4
py38-pytest3.4 installdeps: pytest ~= 3.4.0, pytest-cov ~= 2.5.1, pytest-randomly ~= 2.1.1
py38-pytest3.4 inst: /Users/davidmtucker/Projects/pytest-mypy/.tox/.tmp/package/22/pytest-mypy-0.4.1.tar.gz
py38-pytest3.4 installed: attrs==19.3.0,coverage==4.5.4,mypy==0.740,mypy-extensions==0.4.3,pluggy==0.6.0,py==1.8.0,pytest==3.4.2,pytest-cov==2.5.1,pytest-mypy==0.4.1,pytest-randomly==2.1.1,six==1.12.0,typed-ast==1.4.0,typing-extensions==<IP_ADDRESS>
py38-pytest3.4 run-test-pre: PYTHONHASHSEED='4080983515'
py38-pytest3.4 run-test: commands[0] | py.test --cov pytest_mypy --cov-fail-under 100 --cov-report term-missing
Traceback (most recent call last):
  File "/Users/davidmtucker/Projects/pytest-mypy/.tox/py38-pytest3.4/bin/py.test", line 6, in <module>
    from pytest import main
  File "/Users/davidmtucker/Projects/pytest-mypy/.tox/py38-pytest3.4/lib/python3.8/site-packages/pytest.py", line 13, in <module>
    from _pytest.fixtures import fixture, yield_fixture
  File "/Users/davidmtucker/Projects/pytest-mypy/.tox/py38-pytest3.4/lib/python3.8/site-packages/_pytest/fixtures.py", line 845, in <module>
    class FixtureFunctionMarker(object):
  File "/Users/davidmtucker/Projects/pytest-mypy/.tox/py38-pytest3.4/lib/python3.8/site-packages/_pytest/fixtures.py", line 847, in FixtureFunctionMarker
    params = attr.ib(convert=attr.converters.optional(tuple))
TypeError: attrib() got an unexpected keyword argument 'convert'
ERROR: InvocationError for command /Users/davidmtucker/Projects/pytest-mypy/.tox/py38-pytest3.4/bin/py.test --cov pytest_mypy --cov-fail-under 100 --cov-report term-missing (exited with code 1)
_________________________________________________________________ summary _________________________________________________________________
ERROR:   py34-pytest3.4: commands failed
ERROR:   py35-pytest3.4: commands failed
ERROR:   py36-pytest3.4: commands failed
ERROR:   py37-pytest3.4: commands failed
ERROR:   py38-pytest3.4: commands failed

Not sure why this wasn't hit before 🤔

Not sure why this wasn't hit before

Pytest 3.4 is neither 3.0 nor 3.x, so it wasn't checked.

This affects 3.3 too: https://github.com/pytest-dev/pytest/commit/07b2b18a01a3ba12757a4eb1c0e082922f5299e5
py38-pytest3.3 create: /Users/davidmtucker/Projects/pytest-mypy/.tox/py38-pytest3.3
py38-pytest3.3 installdeps: pytest ~= 3.3.0, pytest-cov ~= 2.5.1, pytest-randomly ~= 2.1.1
py38-pytest3.3 inst: /Users/davidmtucker/Projects/pytest-mypy/.tox/.tmp/package/22/pytest-mypy-0.4.1.tar.gz
py38-pytest3.3 installed: attrs==19.3.0,coverage==4.5.4,mypy==0.740,mypy-extensions==0.4.3,pluggy==0.6.0,py==1.8.0,pytest==3.3.2,pytest-cov==2.5.1,pytest-mypy==0.4.1,pytest-randomly==2.1.1,six==1.12.0,typed-ast==1.4.0,typing-extensions==<IP_ADDRESS>
py38-pytest3.3 run-test-pre: PYTHONHASHSEED='3906030418'
py38-pytest3.3 run-test: commands[0] | py.test --cov pytest_mypy --cov-fail-under 100 --cov-report term-missing
Traceback (most recent call last):
  File "/Users/davidmtucker/Projects/pytest-mypy/.tox/py38-pytest3.3/bin/py.test", line 6, in <module>
    from pytest import main
  File "/Users/davidmtucker/Projects/pytest-mypy/.tox/py38-pytest3.3/lib/python3.8/site-packages/pytest.py", line 13, in <module>
    from _pytest.fixtures import fixture, yield_fixture
  File "/Users/davidmtucker/Projects/pytest-mypy/.tox/py38-pytest3.3/lib/python3.8/site-packages/_pytest/fixtures.py", line 842, in <module>
    class FixtureFunctionMarker(object):
  File "/Users/davidmtucker/Projects/pytest-mypy/.tox/py38-pytest3.3/lib/python3.8/site-packages/_pytest/fixtures.py", line 844, in FixtureFunctionMarker
    params = attr.ib(convert=attr.converters.optional(tuple))
TypeError: attrib() got an unexpected keyword argument 'convert'
ERROR: InvocationError for command /Users/davidmtucker/Projects/pytest-mypy/.tox/py38-pytest3.3/bin/py.test --cov pytest_mypy --cov-fail-under 100 --cov-report term-missing (exited with code 1)

The issue was fixed in 3.5: https://github.com/pytest-dev/pytest/commit/82cdc487cefbbbd1848705427fed6276461835e6
However, it was reintroduced in 4.0.1: https://github.com/pytest-dev/pytest/commit/fc61bdd9073d86819eb54c8603384a10c626a9d4

This is why the 3.4 traceback is different from the original.

Then it was finally fixed in 4.3.0: https://github.com/pytest-dev/pytest/commit/40cec637d7b9faf7f3794cd6c71517f98704c817


⚠ Visit Santa Rosa - Search has degraded performance

In 6ade98c, Visit Santa Rosa - Search (https://www.visitsantarosa.com/results?search=) experienced degraded performance:

HTTP code: 200
Response time: 691 ms

Resolved: Visit Santa Rosa - Search performance has improved in 1e78acc.


Add support for Docz

Fixes #2055
Changes proposed:

[x] Add
[ ] Delete
[ ] Fix
[ ] Prepare

Not sure how the icon will look 'n' feel on light themes.


sam_freespace

hello, thanks for your contribution, i really appreciate your work.
I think it possible to use grounded_sam model to develop freespace or namely, drivable area.
Does anybody have an idea on using demos to do so


Add buble extension

Here's project link
https://gitlab.com/Rich-Harris/buble

@TrySound thanks for sending this but that project is still insanely immature, I'm going to hold off for now to see if it gains traction.

@phated I agree it's very immature, but I don't think it is our place to decide if something is popular enough to be included. As long as there isn't a conflict with an existing extension, I'm inclined to support anything people submit that is actually a project.

Thanks, guys. Yeah, buble is very young. But as it's focused on small part and have an experience of another js-processing projects it's mostly complete. I use it in big production code and it works well. Also implementing buble as gulpfile processor can involve more people to let this project be improved.

Thanks, Tyler. WIll you publish?

I just did, like, a few seconds ago!

Cool!

Hope this is the right place to post this, but I'm trying to use ES2015 in my Gulpfile with buble, but I get the error Failed to load external module buble/register
package.json
"devDependencies": {
    ...
    "buble": "^0.13.2",
    "gulp": "^3.9.1",
    ...
}

@WolfieZero would you mind opening a new issue?


Support for simple labels

Is your feature request related to a problem? Please describe.
currently(at least not without using the custom module), it's not possible to create a module that has two running script. (see e.g.)
scripts/wifi_icon scripts/wifi_essid
Describe the solution you'd like
We can either expand the current script module(by adding an option maybe called format)
or create a new module that supports the short-hand for scripts({{script}})
Describe alternatives you've considered
Using the custom module, which works but... it's not elegant
Additional context
While using the custom module workaround. I've found one tiny issue with the label set to this{{100:scripts/wifi_icon scripts/wifi_essid}}
it sometimes would output this instead. but sometimes it works.

i'm guessing it's somewhat of an racing condition? or does ironbar simply output the script which got executed first

Agreed it could be more elegant for simple scenarios like this. I'm not sure how I want to tackle it yet, but will do some planning when I look at the other changes for 0.12. This will be fairly low priority, since there is a working solution for this already via custom.
Regarding the additional context, the system to embed scripts within text is shared across the bar, so I am almost certain that is the same issue as #69. I'm hoping to look at that in the next few days.

I've opted to add a new module called label which takes a single label option. The eventual plan is to migrate custom to use the modules, so that it relies on this new module to remove the duplication.


[New Mock]: BasketBall Teams

Is your feature request related to a problem? Please describe.
Feature to add an endpoint that returns a list of Basketball NBA teams similar to /sports/football/leagues/premier/teams
Describe the solution you'd like
A clear and concise description of what you want to happen.
Sample response would look like this
  [{
    "abbr": "CHI",
    "conference": "Eastern",
    "division": "Central",
    "city": "Chicago",
    "name": "Bulls",
    "color": "CE1141",
    "colors": [
      "CE1141",
      "061922"
    ]
  }]

I'd like to be assigned to this issue.

This would be awesome :) @ade1705

@ageddesi Please review


Ability to search PDX models that meet multiple genomic criteria

Description
As a PDX Finder user, I want to search for PDX models with tumor samples that meet multiple genomic criteria. Molecular profiles can combine mutation, expression, and/or copy number aberration criteria. Multiple profiles can be searched at one time.
Possibility to implement PDX Like Me functionality in the PDX Finder.

this is in the ticket #400. This Epic is not needed. closing


Can we use this in ionic?

Can we use this in ionic? If yes, then can you provide the example code ?

Sorry for the super late response. I haven't noticed this was up in my notifications.
Not sure if you can use ionic since I never tried this, but I'm sure as long as it's pure JavaScript environment you can use it out of box.


Add blog on downtime post-mortem

We had some downtime of the website on October 18th, as a result of an issue that is by now fixed.
It is good to write up a post-mortem to share the details of how this happened and how we fixed it, plus how we know this will not happen again.
Total downtime was circa 10hours at most.

Fixed in #225


Reload gpg key files after creating them, fixes #64

Released in v1.3.2 https://github.com/olafurpg/sbt-ci-release/releases/tag/v1.3.2

Cool, how do you release so quickly?!?

It works, I tested it with a temporary tag at scala-async (https://travis-ci.org/scala/scala-async/builds/585968808)

Nice!


[ADP-3327] Revise PKCS7 padding implementation and tests.

Issue
ADP-3327
Summary
This PR revises the PKCS#7 padding implementation and property tests.
In particular, we:

Move functions pad and unpad into their own dedicated PKCS7 module.
Use the PKCS7 qualifier when importing functions from PKCS7.
Move tests for pad and unpad into their own dedicated PKCS7Spec module.
Revise the documentation for pad and unpad.
Revise the pad function to accept zero-length byte strings.
Add coverage checks to property tests.

Merging manually, since:

This PR only affects:

the test suite for crypto-primitives.
the implementation of module AES256CBC, which is not yet used anywhere outside of crypto-primitives.

The above test suite has been demonstrated to pass both locally and on Buildkite (https://buildkite.com/cardano-foundation/cardano-wallet/builds/4321#018ec2c6-2568-4883-9a32-dc783c36bf9b)


Parse variable inside nested translations

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior
This is my translations file, where I use another translation key in a translation value as documented:
{
  "greetPerson": "Hi {{name}}",
  "welcome": "{{ greetPerson }}, welcome to my site!"
}

Template code :
<p>{{ 'welcome' | transloco: { name: 'Bob' } }}</p>

This outputs "Hi {{ name }}, welcome to my site!"
Expected behavior
"Hi Bob, welcome to my site!"
Minimal reproduction of the problem with instructions
Use the code above (I tried the stackblitz but couldn't make recompilation work)
Environment

Angular version: 9.0.7

Browser:
- [x] Chrome (desktop) version 80

Below were not tested:

- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX

@foucdeg We don't support nested interpolation, only the first level can except parameters.
If you have any questions please feel free to ask in gitter channel

As @shaharkazaz we don't support nested interpolation, therefor I'm closing this issue, for further questions feel free to ask us on our gitter channel

@itayod @shaharkazaz so this is a feature request, is this the right place?

@foucdeg available in v2.15.0, Also updated the docs

Awesome! Thanks.


Request for additions

To begin with I want to thank you for your dedication to keeping GPIOs active in RPI which are, for me, the reason that I remain loyal to Home assistant.
My question is: do you think it is also possible to have integration for DHT and I2C?
If you can give me a perspective to orient myself to the changes that I inevitably see myself forced to make.
Thanks again.

I tried i2c before with the MCP23017 custom_component and found the i2c operation very unstable, at least on a pi4.
(switched to external arduino that interfaces to mcp;s and sends a mqtt message to HA, no issues ever since.


Flaky test in Gateway API conformance: GatewayObservedGenerationBump

Problem statement
GatewayObservedGenerationBump was observed to fail where it shouldnt'.
 I personally haven't observed this anymore and buildpulse confirms that (as you've already linked to it). 👍 to close it.
One thought though: I'd retain the area/tests label for this as it's a testing matter after all.

Closing as discussed above.


2.2.0-RC2 missing latest commits from master

Pull request https://github.com/fakemongo/fongo/pull/334 was merged on Apr 23.
Release version 2.2.0-RC2 was release May 9.
However, 2.2.0-RC2 is based on https://github.com/fakemongo/fongo/commit/090330b65c9c33d333b39b49af280abf7fe1867b, from the driver36 branch, whereas PR #334 went into master and those commits never got merged into the driver36 branch.
Can you push a release to maven-central with the changes from #334? I've been waiting on that fix to go public.

can you check against the driver37 branch ?

How do I convince maven to look at the driver37 branch?

git clone ...
mvn clean install -DskipTests

com.github.fakemongo
fongo
2.2.0-RC3-SNAPSHOT
test

It still fails with 2.2.0-RC3-SNAPSHOT. I still get an InsertManyWriteConcernException (ie. what I fixed in https://github.com/fakemongo/fongo/pull/334)
com.mongodb.InsertManyWriteConcernException
	at com.mongodb.FongoBulkWriteCombiner.throwOnError(FongoBulkWriteCombiner.java:98)
	at com.mongodb.FongoDBCollection.executeBulkWriteOperation(FongoDBCollection.java:1218)
	at com.mongodb.DBCollection.executeBulkWriteOperation(DBCollection.java:2352)
	at com.mongodb.BulkWriteOperation.execute(BulkWriteOperation.java:121)

Also, my project is currently using mongo-java-driver 3.6.3 and morphia 0.108. I had to bump my mongo-java-driver version to 3.7.0 just to get the test case to start, but that will not be sustainable for the rest of my project; I need to fix in the version for the 3.6 driver.

@twillouer any updates on this?

@MustafaHaddara I think the branch driver36 was rebased in June 6th to include your changes and remain on mongo 3.6 (branch driver36 is currently on 75f7204), but it wasn't retagged nor deployed in maven central.
I was also trying to use #334, ideally if current master (fa0d307) was deployed as 2.1.2 or similar. I tried 2.1.2-SNAPSHOT compiled locally and it worked as expected.
@twillouer , any chance these deployments can be done?


Add weekly/monthly test to CI for large model

We currently don't do any automatic testing on large models. Would be good to process a large model on TeamCity to see if performance recent changes didn't cause any major performance loss and to reassure that iMOD Python can still deal with large, complex datasets.
The LHM-fresh salt could be used for this. When we have the iMOD5 backwards compatibility, we could also test on LHM fresh.
This also serves as a user acceptance test.

UPDATE
I added a user_acceptance pytest mark to the imod5_convert_feature_branch, which can be used to run the user acceptance tests. This uses an environmental variable: LHM_PRJ, which is the path to the LHM projectfile, that has to be imported, defined in a .env file.
We can use this to run the tests on TeamCity


Add support for start/end dates for policies

Adds support for active/inactive policies via date:
policies:
  - name: start-policy-on-03-30
    resource: ec2
    start: 2018-03-30

This policy will be skipped (if executed after 2018/03/29):
policies:
  - name: expire-on-03-29
    resource: ec2
    end: 2018-03-29

This policy will be skipped (if executed before 2020/03/30):
policies:
  - name: start-on-2030-03-30
    resource: ec2
    start: 2020-03-30

These two policies will be skipped on/after 2018/03/31:
policies:
  - name: expire-policy-on-03-30
    resource: ec2
    end: 2018-03-30

policies:
  - name: run-for-a-month
    resource: ec2
    start: 2018-03-01
    end: 2018-03-30

it would be better to have an issue on this first to discuss the use cases

also definitely needs some docs, policy attributes aren't discoverable via schema tool.

@kapilt what errors are you getting? I was able to execute off of my branch
$ cat test.yml
policies:
  - name: start-policy-on-03-30
    resource: ec2
    start: 2018-03-30
$ custodian run -s out --dryrun -c test.yml -v --region us-east-1
2018-03-30 14:06:30,276: custodian.commands:DEBUG Loaded file test.yml. Contains 1 policies
2018-03-30 14:06:30,932: custodian.output:DEBUG Storing output with <DirectoryOutput to dir:out/start-policy-on-03-30>
2018-03-30 14:06:30,932: custodian.policy:DEBUG Running policy start-policy-on-03-30 resource: ec2 region:us-east-1 c7n:<IP_ADDRESS>
2018-03-30 14:06:30,933: custodian.cache:DEBUG Using cache file /Users/thisisshi/.cache/cloud-custodian.cache
2018-03-30 14:06:30,933: custodian.resources.ec2:DEBUG Using cached c7n.resources.ec2.EC2: 0
2018-03-30 14:06:30,933: custodian.resources.ec2:DEBUG Filtered from 0 to 0 ec2
2018-03-30 14:06:30,933: custodian.policy:INFO policy: start-policy-on-03-30 resource:ec2 region:us-east-1 count:0 time:0.00
2018-03-30 14:06:30,933: custodian.output:DEBUG metric:ResourceCount Count:0 policy:start-policy-on-03-30 restype:ec2 scope:policy

$ cat test.yml
policies:
  - name: expire-policy-on-03-30
    resource: ec2
    end: 2018-03-30
$ custodian run -s out --dryrun -c test.yml -v --region us-east-1
2018-03-30 14:08:39,715: custodian.commands:DEBUG Loaded file test.yml. Contains 1 policies
2018-03-30 14:08:40,294: custodian.output:DEBUG Storing output with <DirectoryOutput to dir:out/expire-policy-on-03-30>
2018-03-30 14:08:40,294: custodian.policy:DEBUG Running policy expire-policy-on-03-30 resource: ec2 region:us-east-1 c7n:<IP_ADDRESS>
2018-03-30 14:08:40,294: custodian.cache:DEBUG Using cache file /Users/thisisshi/.cache/cloud-custodian.cache
2018-03-30 14:08:40,295: custodian.resources.ec2:DEBUG Using cached c7n.resources.ec2.EC2: 0
2018-03-30 14:08:40,295: custodian.resources.ec2:DEBUG Filtered from 0 to 0 ec2
2018-03-30 14:08:40,295: custodian.policy:INFO policy: expire-policy-on-03-30 resource:ec2 region:us-east-1 count:0 time:0.00
2018-03-30 14:08:40,295: custodian.output:DEBUG metric:ResourceCount Count:0 policy:expire-policy-on-03-30 restype:ec2 scope:policy

$ cat test.yml
policies:
  - name: run-for-a-month
    resource: ec2
    start: 2018-03-01
    end: 2018-03-30
$ custodian run -s out --dryrun -c test.yml -v --region us-east-1
2018-03-30 14:10:17,738: custodian.commands:DEBUG Loaded file test.yml. Contains 1 policies
2018-03-30 14:10:18,323: custodian.output:DEBUG Storing output with <DirectoryOutput to dir:out/run-for-a-month>
2018-03-30 14:10:18,324: custodian.policy:DEBUG Running policy run-for-a-month resource: ec2 region:us-east-1 c7n:<IP_ADDRESS>
2018-03-30 14:10:18,326: custodian.cache:DEBUG Using cache file /Users/llq270/.cache/cloud-custodian.cache
2018-03-30 14:10:18,327: custodian.resources.ec2:DEBUG Using cached c7n.resources.ec2.EC2: 0
2018-03-30 14:10:18,327: custodian.resources.ec2:DEBUG Filtered from 0 to 0 ec2
2018-03-30 14:10:18,327: custodian.policy:INFO policy: run-for-a-month resource:ec2 region:us-east-1 count:0 time:0.00
2018-03-30 14:10:18,327: custodian.output:DEBUG metric:ResourceCount Count:0 policy:run-for-a-month restype:ec2 scope:policy

These policies should all run today, but the last two, run-for-a-month and expire-policy-on-03-30 should be skipped tomorrow. I'll edit the description to provide policies that expire like so:
$ cat test.yml
policies:
  - name: expire-03-29
    resource: ec2
    end: 2018-03-29
$ custodian run -s out --dryrun -c test.yml -v --region us-east-1
2018-03-30 14:12:59,303: custodian.commands:DEBUG Loaded file test.yml. Contains 1 policies
2018-03-30 14:12:59,906: custodian.policy:INFO Skipping policy expire-03-29 end-date: 2018-03-29 is before current date: 2018-03-30

Hmm it looked like the tests were passing date times objects and I didn’t see any date time parse for the use of strings from policies.

i was able to validate  my assumption that this wouldn't work. schema validators typically aren't supposed to be returning mutations of the things their validating. also whenever dealing with dates, tzs need to be considered.
$ cat fo.yml
policies:
  - name: vpc-check
    resource: vpc
    start: 2019-01-1
    filters:
      - type: dhcp-options
        domain-name: [c7n.internal]

$ custodian validate -c fo.yml
2018-03-31 06:29:16,543: custodian.commands:INFO Configuration valid: fo.yml

$ custodian run -c fo.yml  -s out
2018-03-31 06:29:31,246: custodian.commands:ERROR Error while executing policy vpc-check, continuing
Traceback (most recent call last):
  File "/Users/kapilt/projects/custodian/c7n/commands.py", line 229, in run
    policy()
  File "/Users/kapilt/projects/custodian/c7n/policy.py", line 732, in __call__
    resources = mode.run()
  File "/Users/kapilt/projects/custodian/c7n/policy.py", line 207, in run
    if not self.is_runnable():
  File "/Users/kapilt/projects/custodian/c7n/policy.py", line 301, in is_runnable
    if self.policy.start and self.policy.start > now:
TypeError: can't compare datetime.date to str

The policy is failing to execute because when parsing the string it's expecting a format of YYYY-MM-DD, changing the policy to the following will work:
policies:
  - name: vpc-check
    resource: vpc
    start: 2019-01-01
    filters:
      - type: dhcp-options
        domain-name: [c7n-internal]

That's definitely confusing though and not intuitive, I originally changed schema to explicitly check for date as to not put the burden of validation on the policy class, but to enable more flexibility I can see why you would want to do the parse explicitly:
>>> from dateutil.parser import parse
>>> parse('January 1 2019')
datetime.datetime(2019, 1, 1, 0, 0)
>>> parse('2019-1-1')
datetime.datetime(2019, 1, 1, 0, 0)
>>> parse('2019-01-1')
datetime.datetime(2019, 1, 1, 0, 0)

re: timezones-- definitely

ideally if someone gives an invalid string, it would be a validation error, instead of a traceback later on, there's some regex capabilities on string in json schema for that.

hmm.. instead of dealing with the missing imports and adding more dependencies it might easier for us to just implement the format checker ourselves using dateutil parser and pass it into the validator


NXP S32K1XX peripheral clock fixes

I have a few changes for NXP S32K1XX. I will split them into three PRs to make it easier for PX4 to backport specific changes if they want to. This is the first and includes these changes:

Only apply PCC clock divider when it is actually set. This makes it possible to leave the field empty in the peripheral clock config. Most peripherals don't have this divider field in their PCC register, so it allows for cleaner peripheral clock config files (but it does not break existing files).
Use uppercase "FLEXCAN_CLK" identifiers instead of mixed case "FlexCAN_CLK" for consistency.
Style fixes.

Hmmm... I see that you did run nxstyle.  But the current version of nxstyle used in the PR checks is reporting style errors as you see above.  We will have to resolve these before continuing.

@patacongo I see. It refuses to show me the full log output (it says "loading" for minutes), but I'll try to figure out what is causing the issue.

It refuses to show me the full log output

You should be able to press "Details" to the righit of PR Check CI / check (pull_request).  That should bring up a window that shows the step(s) that failed.  Expand the failed step and you see all of the nxstyle complaints claimed.

@jarivanewijk for the style check. You have 2 options:

rebase on current master to pick up the NOW version of the tool
runs style checks again
and force push

OR
do the following:
cd tools
wget https://raw.githubusercontent.com/apache/incubator-nuttx/master/tools/nxstyle.c
make -f Makefile.host
then run tools/checkpatch.sh on your commits.
do not commit the nxstyle.c

rebase -i   to clean up and force push

Thanks. @davids5 - I actually used the most recent nxstyle, but I must have made a mistake.
There was one error I missed, and a few long lines that I had ignored because I used nxstyle -m 8. I extended the "rulers" by 8 characters, because it just would not make the code any clearer if I started breaking up these lines. Now everything should be okay.


Testing for errors

Related: #132
I'm trying to test for a failure when two objects interact, a's method interact() throws an error. I'm not sure how to really do this, I can't get parent topics in the vow, so I can't trigger the error in the vow without writing a helper topic putting current and parent topic together in an object, which is clumsy.
Maybe my problem is that I dont know how I have to write failing tests in vows, or I don't get the vow/topic separation. I ran into enough problems with vows for now, I'll try another testing framework.
'A': {
    topic: new A,
    'and B': {
        topic: new B,
        'interact': {
            topic: function(b, a) {
                return a.interact(b) // throws an error
            },
            'should fail': function(topic) {
                assert.fail(topic)
            }
         },
         'interact fails': function(b, a) {
             console.dir(arguments) // [null (??!), B]
         }
         ....

Fixed in 6f84e3b535239e8b36adfc656510b99b37d78859. When topic throws, exception will be passed down as first argument to callback. See 239df6022e4ba6951fed5dce9fb3c3eb0a81ec67 for a test.


#107, open the output file in the write mode

With ReadWriteMode Haskell opens the file but doesn't truncate the contents. That means if we have a file there from before, we end up overwriting the start, and if the file was longer, we end up with corrupt JSON. Only visible if you run the test suite multiple times, and somewhat non-deterministic since it requires longer times (when printed in exponential format), followed by shorter times.

Thanks for catching this.  I fee silly for reproducing that bug because I think something similar may have been happening with the previous binary serialization.


Device assignment does not work in PyTorch

As of 12372f4c6562f296c510f6734e748ef54c375c33, device assignment in the PyTorch dataloader does not work correctly with multiple GPUs.
import os
import pandas as pd

from merlin.dataloader.torch import Loader
from merlin.io.dataset import Dataset

dataset = Dataset(pd.DataFrame({"a": list(range(10))}))
dataset = dataset.repartition(npartitions=2)

rank = int(os.environ["LOCAL_RANK"])

with Loader(
    dataset,
    batch_size=1,
    global_rank=rank,
    global_size=2,
    device=rank,
) as loader:
    for idx, batch in enumerate(loader):
        x, y = batch
        device = x["a"].device
        print(f"rank: {rank}, device: {device}")

When I run the above, I get:
root@ba87ba84045a:/dataloader# torchrun --nproc_per_node=2 test_torch_multi_gpu.py
WARNING:torch.distributed.run:
*****************************************
Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.
*****************************************
/usr/local/lib/python3.8/dist-packages/merlin/dtypes/mappings/tf.py:52: UserWarning: Tensorflow dtype mappings did not load successfully due to an error: No module named 'tensorflow'
  warn(f"Tensorflow dtype mappings did not load successfully due to an error: {exc.msg}")
/usr/local/lib/python3.8/dist-packages/merlin/dtypes/mappings/tf.py:52: UserWarning: Tensorflow dtype mappings did not load successfully due to an error: No module named 'tensorflow'
  warn(f"Tensorflow dtype mappings did not load successfully due to an error: {exc.msg}")
rank: 0, device: cuda:0
rank: 0, device: cuda:0
rank: 0, device: cuda:0
rank: 0, device: cuda:0
rank: 0, device: cuda:0
rank: 1, device: cuda:0
rank: 1, device: cuda:0
rank: 1, device: cuda:0
rank: 1, device: cuda:0
rank: 1, device: cuda:0

But for rank 1, tensors are expected to be be placed on cuda:1 not cuda:0.

Even with #132, the device assignment still doesn't work for list columns:
import os
import pandas as pd

from merlin.dataloader.torch import Loader
from merlin.io.dataset import Dataset

#dataset = Dataset(pd.DataFrame({"a": list(range(10))}))
dataset = Dataset(pd.DataFrame({"a": [[1], [2, 3]] * 5}))
dataset = dataset.repartition(npartitions=2)

rank = int(os.environ["LOCAL_RANK"])

with Loader(
    dataset,
    batch_size=1,
    global_rank=rank,
    global_size=2,
    device=rank,
) as loader:
    for idx, batch in enumerate(loader):
        x, y = batch
        values_device = x["a__values"].device
        offsets_device = x["a__offsets"].device
        print(f"rank: {rank}, values_device: {values_device}, offsets_device: {offsets_device}")

# torchrun --nproc_per_node=2 test_torch_multi_gpu.py
WARNING:torch.distributed.run:
*****************************************
Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.
*****************************************
/usr/local/lib/python3.8/dist-packages/merlin/dtypes/mappings/tf.py:52: UserWarning: Tensorflow dtype mappings did not load successfully due to an error: No module named 'tensorflow'
  warn(f"Tensorflow dtype mappings did not load successfully due to an error: {exc.msg}")
/usr/local/lib/python3.8/dist-packages/merlin/dtypes/mappings/tf.py:52: UserWarning: Tensorflow dtype mappings did not load successfully due to an error: No module named 'tensorflow'
  warn(f"Tensorflow dtype mappings did not load successfully due to an error: {exc.msg}")
rank: 0, values_device: cuda:0, offsets_device: cuda:0
rank: 0, values_device: cuda:0, offsets_device: cuda:0
rank: 0, values_device: cuda:0, offsets_device: cuda:0
rank: 0, values_device: cuda:0, offsets_device: cuda:0
rank: 0, values_device: cuda:0, offsets_device: cuda:0
terminate called after throwing an instance of 'thrust::system::system_error'
  what():  transform: failed to synchronize: cudaErrorIllegalAddress: an illegal memory access was encountered
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: -6) local_rank: 1 (pid: 1218) of binary: /usr/bin/python3
Traceback (most recent call last):
  File "/usr/local/bin/torchrun", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.8/dist-packages/torch/distributed/elastic/multiprocessing/errors/__init__.py", line 346, in wrapper
    return f(*args, **kwargs)
  File "/usr/local/lib/python3.8/dist-packages/torch/distributed/run.py", line 762, in main
    run(args)
  File "/usr/local/lib/python3.8/dist-packages/torch/distributed/run.py", line 753, in run
    elastic_launch(
  File "/usr/local/lib/python3.8/dist-packages/torch/distributed/launcher/api.py", line 132, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/usr/local/lib/python3.8/dist-packages/torch/distributed/launcher/api.py", line 246, in launch_agent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
=====================================================
test_torch_multi_gpu.py FAILED
-----------------------------------------------------
Failures:
  <NO_OTHER_FAILURES>
-----------------------------------------------------
Root Cause (first observed failure):
[0]:
  time      : 2023-04-13_21:57:34
  host      : 0810733-lcedt
  rank      : 1 (local_rank: 1)
  exitcode  : -6 (pid: 1218)
  error_file: <N/A>
  traceback : Signal 6 (SIGABRT) received by PID 1218
=====================================================

Wondering if this may be related to which GPU the cuDF dataframe or series is coming from. Selecting the device with cuDF requires dropping down to CuPy AFAIK, which I think requires running cupy.cuda.Device(1).use() before creating dataframes.


switch the default for dartanalyzer to strong mode

We've switched the default handing in the analysis server to strong-mode: true; we should update the default handling for the cli as well.

this is done


Error messages from loaders misreported when extra <> characters present

I am encountering a problem with Webpack with the Typescript ts-loader (I have also seen an identical bug with Webpack and awesome-typescript-loader). I first filed this bug with ts-loader. They told me it was a Webpack bug (citing its presence in multiple Webpack loaders) and closed my bug.
If this is not a Webpack bug, then I would like to request you help me figure out what to say to convince ts-loader that this is their bug that should be fixed at their end. I am an end user and do not know how Webpack loaders work.
Bug report
If the current behavior is a bug, please provide the steps to reproduce.
Check out this minimal example repo. Run npm install and npx webpack. The example uses version 4.41.6 of Webpack with ts-loader (and copy-webpack-plugin).
What is the current behavior?
Upon running npx webpack with this example, the following confusing and misleading error occurs:
[./src/index.tsx] 294 bytes {main} [built] [failed] [11 errors]

ERROR in ./src/index.tsx 18:1
Module parse failed: Unexpected token (18:1)
File was processed with these loaders:
 * ./node_modules/ts-loader/index.js
You may need an additional loader to handle the result of these loaders.
| console.log("9");
| console.log("10");
>  > , label;
| string;
| {

ERROR in /Users/mcc/work/g/temp/ts-hello-bug/src/index.tsx
./src/index.tsx
[tsl] ERROR in /Users/mcc/work/g/temp/ts-hello-bug/src/index.tsx(25,58)
      TS1005: ';' expected.

9 more errors follow after these.
What is the expected behavior?
The second error shown in the error spew is correct. However the first error is fallacious, marks a line which is completely correct, misformats the code sample (it claims the error was on line 18 but prints a > pointing at line 22; both lines 18 and 22 are correct) and is generally nonsensical. The expected behavior would be to show only the real error (line 25) and not the phantom error(s) on line 18 or 22.
Explanation: The example contains this line in "index.tsx" on line 25:
function UsersBox(props: {list: State<OrderedSet<string>>>, label:string}) {

This is an invalid line of TypeScript. TypeScript uses <angle brackets> to denote parameterized types in generics, for example, a Set<number> is a Set of numbers. The <brackets> in this example are unbalanced, there is one > too many.
You can tell that the phantom error is being inserted by either WebPack or ts-loader because normal TypeScript does not flag the line 18/22 bug. If you run tsc in the example repo the only errors you will see are
src/index.tsx(25,58): error TS1005: ';' expected.
src/index.tsx(25,59): error TS1109: Expression expected.
src/index.tsx(25,73): error TS1005: ',' expected.

The reason I consider the phantom error a significant problem is that usually in compiler errors, the first error in a group is the most significant. Coders effectively become trained to assume the first-reported error is "real" and further ones could be the result of a parser being lead off track by the first error. A user encountering this misreported-error bug (this happened to me) could lose a significant amount of time due to not realizing which error is the real one (the second out of eleven, but not the others). Furthermore the error is easy to encounter because <> is common in TypeScript.
Other relevant information:
Very many other simple typos involving stray <angle brackets> cause similar misreported errors to occur with Webpack+ts-loader. For example, if I remove index.tsx line 25 from the example repo and put this in instead:
return

Errors

{errorFragment}

(The
s here are unbalanced; the second to last
 should be a
). Similar to the >> bug, this code reports a nonsensical error about seven or eight lines before the place where the error actually occurred.

The error message shows the code generated by typescript. Typescript even generates some JS code when errors are found. That JS code is malformed, which causes the error.

@sokra , is there a way to see what JS code ts-loader generated in this case, which caused the error, so I can check whether that is true?
is there anything ts-loader could be doing differently (for example, providing a source map) so that the line number in the error would be reported correctly?
If I run tsc (showing what output Typescript would normally emit— tsc will print errors but still emit a file), I get:
let verbose = false;
class OrderedSet {
    constructor() { }
}
class State {
    constructor() { }
}
console.log("1");
console.log("2");
console.log("3");
console.log("4");
console.log("5");
console.log("6");
console.log("7");
console.log("8");
console.log("9");
console.log("10");
// HERE IS THE LINE WITH THE CURSE
function UsersBox(props =  > , label) {
}

It looks like there is an error in the emitted code here on line 18, where typescript passes through a raw >. Line 18 is where the "phantom error" was reported. So Webpack might be reporting right in that there is an error on line 18 of the output it's been given, but it's not correct insofar as it's not line 18 of index.tsc, and also it truncates the displayed line to >  > , label; instead of printing function UsersBox(props =  > , label) { which would have been slightly more helpful.

there is an error on line 18 of the output it's been given, but it's not correct insofar as it's not line 18 of index.tsc, and also it truncates the displayed line to > > , label; instead of printing function UsersBox(props = > , label) { which would have been slightly more helpful.

That seem to be true, but I don't know why this is broken.
You might debug that. Here are the code which generates the error message:
https://github.com/webpack/webpack/blob/a87d290dd84aeb9190a836b79e1a9d91d9e4a680/lib/ModuleParseError.js#L47-L56

is there anything ts-loader could be doing differently (for example, providing a source map) so that the line number in the error would be reported correctly?

Instead of reporting only soft errors with this.emitError(error) they could report a hard error with this.callback(error). Not sure how this fits in the typescript philosophy and you probably only want this for parsing errors not for type errors.


create mp4 file from playlist

Is it possible to create an mp4 file from a given playlist url?

Not with this gem alone, you would also need something like FFmpeg. You can use this library to parse each media playlist and get the URI of each MPEG-2 transport stream file that makes up each segment of the playlist. You'd then use FFmpeg to concatenate all the individual transport stream files from a single media playlist and remux it into a MP4 (assuming you want to preserve codecs).

Thanks, I was able to use FFmpeg to create an mp4 directly from a m3u8 playlist URL.


Add is_parenthesized flag to ExprTuple

Summary
This PR adds an is_parenthesized prop to ExprTuple that exposes if the tuple is parenthesized in the source.
The information is useful during linting and formatting, and dedecting if a tuple is parenthesized is somewhat involved.
Should this information be present in the AST: IMO, properties that are needed more than once are worth tracking in the AST, even if they don't have any semantical meaning.
It also simplifies implementing the new parser where it otherwise would need to be necessary to track the information separately.
Test Plan
I added new tests and reviewed the snapshot changes

If we track this for tuples, should we also track it for generators, where it's also optional?

I def support this. I think I tried to pitch it at one point but there wasn't enough interest :joy:

If we track this for tuples, should we also track it for generators, where it's also optional?

Adding it to generators increases the Expr size from 40 to 48 bytes...


Multiple Config File Support

Adds ability to drop config files into the 'configs' dir whilst developing and have them ignored by git

Does it support run bot with multiple configs as once?

The bot can currently use any .json file to run, all this PR will do is move all the configs to a 'configs' directory and have your commits ignore them, while still not ignoring the example configs.

we are going to make changes to config.json and release_config.json. once those are updated, please review this PR again and make the updates necessary for it to work.

Even with changes, this PR shouldn't affect anything but help developers test on different configs. I can make changes accordingly once we merge the config files if it does affect anything

Okay, example files have been re-included. Was just a missing * form the .gitignore :+1:

Added the warnings as suggested. Is this PR good to go?

waiting for a second review but it should be good to go !

+1

Thanks!

@ColeGreenlee can I ask for another PR with information about new folder for config files in README?

Yeah, I'd be more than happy to document this.

Please do document this. What are the arguments for running configs from this /configs/ folder


build: avoid semver and word-wrap vulnerabilities

PR summary
This PR uses the "overrides" field in package.json to override a couple of transitive dependencies to avoid vulnerabilities in word-wrap and semver.
PR Checklist
General checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] Dependencies have been updated as needed
[ ] .secrets.baseline updated as needed?

Checklist for adding a new validation rule:

[ ] Added new validation rule definition (packages/ruleset/src/rules/*.js, index.js)
[ ] If necessary, added new validation rule implementation (packages/ruleset/src/functions/*.js, updated index.js)
[ ] Added new rule to default configuration (packages/ruleset/src/ibm-oas.js)
[ ] Added tests for new rule (packages/ruleset/test/*.test.js)
[ ] Added docs for new rule (docs/ibm-cloud-rules.md)

:tada: This PR is included in version 1.2.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


missing babel-runtime?

When I upgrade from 0.8 to 0.9.3, I get this when I try to run esformatter:
:; esformatter
module.js:341
    throw err;
    ^

Error: Cannot find module 'babel-runtime/helpers/interop-export-wildcard'
    at Function.Module._resolveFilename (module.js:339:15)
    at Function.Module._load (module.js:290:25)
    at Module.require (module.js:367:17)
    at require (internal/module.js:16:19)
    at Object.<anonymous> (/Users/aredridel/Projects/npm/npm-website/node_modules/babel-types/lib/index.js:13:30)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Module.require (module.js:367:17)

that's weird, I was not able to reproduce this. can you try npm cache clean esformatter babel-runtime and install esformatter again?

can't repro and nobody else reported this, so I'm going to close it as invalid.
PS: I'm also going to change the way the parser is loaded soon, so it might actually help to solve this issue (#440)

Alright. might also have been an npm bug in one of the older 3.x series.


fixed comment section

This pull request is fixed the documentation about how to use getJSBundleFile. having file:// makes react on android crash. The path needs to be an absolute.

fixed comment section

Can you please add the fact this has to do with getJSBundleFile on Android to the PR title?

file:// makes react on android crash

Can you show how it crashes? What's the stack trace? I wonder why we haven't noticed this before.

@alinz I'm going through all pull requests and noticed this one hasn't been updated in a while and the last comment asks a question. I'll close this pull request so it doesn't stay open indefinitely but please send a new one if you want to continue working on this.

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain thumbmunkeys.com has exceeded the max emails per hour (67/60 (111%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from filter03.reliabledns.org ([<IP_ADDRESS>]:42616)
by en02-ams.stablehost.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1biJUi-003Ktk-88
for<EMAIL_ADDRESS>Fri, 09 Sep 2016 10:57:18 +0000
Received: from o5.sgmail.github.com ([<IP_ADDRESS>])
by filter03.reliabledns.org with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128)
(Exim 4.85)
(envelope-from<EMAIL_ADDRESS>id 1biJUg-0000Cq-Bi
for<EMAIL_ADDRESS>Fri, 09 Sep 2016 03:57:16 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=github.com;
h=from:reply-to:to:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=AyAYps5s5LqUAS0hmxcNvyowKaY=; b=n+tekFFPr3lZyCXc
moOpcIP6wKRw21HPBbQdLqJ7ApwNwyOmbrK2grv6Cv2ZLNENHFW2NYgUk/tydQOd
ggn2IblVJH90gK5rJOGhxhVFbQtoLvhd6W8AAd/Zk5Wqeqhao84iMrJlQxMlWKoY
B2pGzLLbLdURK6j2wwBdHHWzQ4A=
Received: by filter1000p1mdw1.sendgrid.net with SMTP id filter1000p1mdw1.5934.57D295606C
2016-09-09 10:56:32.832919927 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id cFDLWL9wQoyV9ukuwy5IHg
for<EMAIL_ADDRESS>Fri, 09 Sep 2016 10:56:32.811 +0000 (UTC)
Date: Fri, 09 Sep 2016 03:56:32 -0700
From: Martin Konicek<EMAIL_ADDRESS>Reply-To: facebook/react-native<EMAIL_ADDRESS>To: facebook/react-native<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [facebook/react-native] fixed comment section (#8031)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_57d29560a78b6_291b3fcfdf48d2a06263eb";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mkonicek
X-GitHub-Recipient: bunnyboy1
List-ID: facebook/react-native <react-native.facebook.github.com>
List-Archive: https://github.com/facebook/react-native
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/ARoNg8k1omiCzh7PnjScn34yfrkgD-MRks5qoTtggaJpZM4IyQ3R
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: wxILpmbMy+DMOe8s3uTnYJqhMhAtpIHhpRnO60rP0k+QUkmiayl7Ph78iw+tF/N+8+lWbZkN3oYYxi
Fy2qu2161fpmdB7MbCzyGNTlSp+FUseNEzXo74uPBKCs+dhdiGYPYfx2LvutSIMs7XwZHywNBiUOi/
QUM0qLfCyWLyoEvHxLGtVcERoao0ZlBt7sLL/bTndJa1FiLO6T2MMVe+hBRPU2xpJGGbKY+Okzd73O
0=
Received-SPF: pass (filter03.reliabledns.org: domain of sgmail.github.com designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS><EMAIL_ADDRESS>helo=o5.sgmail.github.com;
X-SPF-Result: filter03.reliabledns.org: domain of sgmail.github.com designates <IP_ADDRESS> as permitted sender
X-Sender-Warning: sgmail.github.com has no MX records
Authentication-Results: filter03.reliabledns.org; dmarc=pass header.from=github.com
X-Filter-ID: s0sct1PQhAABKnZB5plbIT1RbOwy06L9REYyr9AwRQTwqQ7CW4gxUeeyoz1oed5P/SEnTgrA37IX
TZjA4tFfC9o7/kuvJ3wuZWRdcwKwe1+/dW/xGlBq3/UmIKUCpDxGneIVwSf+lCa+FY3nagRj3wdr
IZ+D/FAg6XyPDmfkLA7rcxAODBZO2BOkcGk4nUtaK+NKmfKT1VzfmhD1tR7fxVarIGSMLt5vX9V9
rVXE/wBcR6vcRlDk/cSBa4A2VcTnkxlSZxHxTWgJwgGAdAfYx5W19KrPTiYX8ldb/scbU0w4f8VH
yZVYpz0RzxE1zGEMSmEIS4GON+6FOG36iMWh1MkJ+S1xR7tBHCAvxXNNyU893SsS4aMXJmiJ2G0e
b5ahm8p6HlShAEYnwZBavOYADGb0g2n0QCK0NUarjxzvKHXDqcigOvSxdRnthmhn8Zn6s8w/N/eB
P5qFKj1/fsvit0UWb7Au9+OsDspaYXORD9DExXy0aVT1HuhJQmP8nOV/gcSXPi64HW9TLHbE1xGc
sIqosGRVic0wJZbsnU20WkB8LSJSyBhtnWbngGtasJkXBf0jdZtXXwRMZ/pKak7GRV+Sy3brvYFg
uJ068d7ZjkeRv8Gjvtc3eeZ2pvOmIPvav2ToL5w5nDAUe12FhqWGsTEvuGslKTrRIXcXpFg5ivY=
X-Report-Abuse-To<EMAIL_ADDRESS>Authentication-Results: reliabledns.org; spf=pass<EMAIL_ADDRESS>Authentication-Results: reliabledns.org; dkim=pass header.i=github.com
X-SpamExperts-Class: ham
X-SpamExperts-Evidence: Combined (0.00)
X-Recommended-Action: accept
X-Spam-Status: No, score=1.1
X-Spam-Score: 11
X-Spam-Bar: +
X-Ham-Report: Spam detection software, running on the system "en02-ams.stablehost.com",
has NOT identified this incoming email as spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
root@localhost for details.
Content preview:  @alinz I'm going through all pull requests and noticed this
one hasn't been updated in a while and the last comment asks a question.
I'll close this pull request so it doesn't stay open indefinitely but please
send a new one if you want to continue working on this. [...]
Content analysis details:   (1.1 points, 5.0 required)
pts rule name              description

-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
trust
[<IP_ADDRESS> listed in list.dnswl.org]
1.5 SPF_SOFTFAIL           SPF: sender does not match SPF record (softfail)
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
1.6 HTML_IMAGE_ONLY_24     BODY: HTML: images with 2000-2400 bytes of words
0.0 HTML_MESSAGE           BODY: HTML included in message
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
domain
0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
X-Spam-Flag: NO
----==_mimepart_57d29560a78b6_291b3fcfdf48d2a06263eb
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
@alinz I'm going through all pull requests and noticed this one hasn't been updated in a while and the last comment asks a question. I'll close this pull request so it doesn't stay open indefinitely but please send a new one if you want to continue working on this.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/facebook/react-native/pull/8031#issuecomment-245882371
----==_mimepart_57d29560a78b6_291b3fcfdf48d2a06263eb
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
@alinz I=
'm going through all pull requests and noticed this one hasn't been updated=
 in a while and the last comment asks a question. I'll close this pull requ=
est so it doesn't stay open indefinitely but please send a new one if you w=
ant to continue working on this.
&mda=
sh;You are receiving this because you are subscribed to this thread.<=
br />Reply to this email directly, view it on GitHub, or mute the thread.

=
----==_mimepart_57d29560a78b6_291b3fcfdf48d2a06263eb--

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain thumbmunkeys.com has exceeded the max emails per hour (69/60 (114%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from filter03.reliabledns.org ([<IP_ADDRESS>]:42638)
by en02-ams.stablehost.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1biJVV-003LDS-0U
for<EMAIL_ADDRESS>Fri, 09 Sep 2016 10:58:06 +0000
Received: from o7.sgmail.github.com ([<IP_ADDRESS>])
by filter03.reliabledns.org with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128)
(Exim 4.85)
(envelope-from<EMAIL_ADDRESS>id 1biJVT-0000EU-5O
for<EMAIL_ADDRESS>Fri, 09 Sep 2016 03:58:04 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=github.com;
h=from:reply-to:to:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=Pke5GF4E2HEU+ssINItwWC5WYcE=; b=SgPx6dyXGem7B+BO
AHaFWZemSRSJW8Betdebbk3eaplhouEmwSZfVO5DLVVeEDLC31/2kpLUvoFdVrPb
xENJ7L4KmuXmak94wlQ580dVBNlPM5ze/k8YWhBj62JcFZMirc5tWyr1rzLdSbxd
mFbrW1dTy7uHhsBpKMCw1usiFJE=
Received: by filter0800p1mdw1.sendgrid.net with SMTP id filter0800p1mdw1.20958.57D2956A43
2016-09-09 10:56:42.445486084 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id OPtiiggJRhePi3oQSCkh5A
for<EMAIL_ADDRESS>Fri, 09 Sep 2016 10:56:42.280 +0000 (UTC)
Date: Fri, 09 Sep 2016 03:56:42 -0700
From: Martin Konicek<EMAIL_ADDRESS>Reply-To: facebook/react-native<EMAIL_ADDRESS>To: facebook/react-native<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [facebook/react-native] fixed comment section (#8031)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_57d2956a19c6f_7bbd3fcfdf48d2a07819d4";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mkonicek
X-GitHub-Recipient: bunnyboy1
List-ID: facebook/react-native <react-native.facebook.github.com>
List-Archive: https://github.com/facebook/react-native
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/ARoNgzjJI2vqcWCrilyuRmTvgf5VtiWPks5qoTtqgaJpZM4IyQ3R
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: wxILpmbMy+DMOe8s3uTnYJqhMhAtpIHhpRnO60rP0k9QyPBTXe/WsCLkpbRHMinLguKKcGjifb/qo4
2eZMMpvj7G25Rclsn5vruDGBL2pQEapF5UUuEgo5ZgIbkbYl3I6BRpFe2i1+Pq2J/I1oL1j+8lo4df
Q158KYCcPCk3rr4H4RytNv0N46YRajyrdYKmNl1bXlbCPNhoejHfsdPlZOhnQwBIucXLwgK4N0GUkV
Y=
Received-SPF: pass (filter03.reliabledns.org: domain of sgmail.github.com designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS><EMAIL_ADDRESS>helo=o7.sgmail.github.com;
X-SPF-Result: filter03.reliabledns.org: domain of sgmail.github.com designates <IP_ADDRESS> as permitted sender
X-Sender-Warning: sgmail.github.com has no MX records
Authentication-Results: filter03.reliabledns.org; dmarc=pass header.from=github.com
X-Filter-ID: s0sct1PQhAABKnZB5plbIT1RbOwy06L9REYyr9AwRQTwqQ7CW4gxUeeyoz1oed5P/SEnTgrA37IX
TZjA4tFfC9o7/kuvJ3wuZWRdcwKwe1+/dW/xGlBq3/UmIKUCpDxGneIVwSf+lCa+FY3nagRj3wdr
IZ+D/FAg6XyPDmfkLA7rcxAODBZO2BOkcGk4nUtaxOiX9YDSnHorhGapNwu/olarIGSMLt5vX9V9
rVXE/wBcR6vcRlDk/cSBa4A2VcTnkxlSZxHxTWgJwgGAdAfYxx8xmCnWn68g8jnD06bAHEXijFtv
rjshZ/GrG1bvi5TjSmEIS4GON+6FOG36iMWh1C1uVXAOmyVl/Wyr3s1GEt093SsS4aMXJmiJ2G0e
b5ahm8p6HlShAEYnwZBavOYADGb0g2n0QCK0NUarjxzvKHXDqcigOvSxdRnthmhn8Zn6IqkbEmc1
9yngYmzZWx8QSkUWb7Au9+OsDspaYXORD9DExXy0aVT1HuhJQmP8nOV/gcSXPi64HW9TLHbE1xGc
sIqosGRVic0wJZbsnU20WkB8LSJSyBhtnWbngGtasJkXBf0jdZtXXwRMZ/pKak7GRV+Sy3brvYFg
uJ068d7ZjkeRv8Gjvtc3eeZ2pvOmIPvav2ToL5w5nDAUe12FhqWGsTEvuGslKTrRIXcXpFg5ivY=
X-Report-Abuse-To<EMAIL_ADDRESS>Authentication-Results: reliabledns.org; spf=pass<EMAIL_ADDRESS>Authentication-Results: reliabledns.org; dkim=pass header.i=github.com
X-SpamExperts-Class: ham
X-SpamExperts-Evidence: Combined (0.04)
X-Recommended-Action: accept
X-Spam-Status: No, score=1.1
X-Spam-Score: 11
X-Spam-Bar: +
X-Ham-Report: Spam detection software, running on the system "en02-ams.stablehost.com",
has NOT identified this incoming email as spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
root@localhost for details.
Content preview:  Closed #8031. -- You are receiving this because you are subscribed
to this thread. Reply to this email directly or view it on GitHub: https://github.com/facebook/react-native/pull/8031#event-783762475
[...]
Content analysis details:   (1.1 points, 5.0 required)
pts rule name              description

-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
trust
[<IP_ADDRESS> listed in list.dnswl.org]
1.5 SPF_SOFTFAIL           SPF: sender does not match SPF record (softfail)
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
1.6 HTML_IMAGE_ONLY_24     BODY: HTML: images with 2000-2400 bytes of words
0.0 HTML_MESSAGE           BODY: HTML included in message
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
domain
0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
X-Spam-Flag: NO
----==_mimepart_57d2956a19c6f_7bbd3fcfdf48d2a07819d4
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #8031.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/facebook/react-native/pull/8031#event-783762475
----==_mimepart_57d2956a19c6f_7bbd3fcfdf48d2a07819d4
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #8031.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_57d2956a19c6f_7bbd3fcfdf48d2a07819d4--


Upgraded support to Canon SDK 3.4.0

Upgraded to Canon SDK 3.4.0+
Compatibility with previous versions discontinued

Thanks! Accepting this since I know you've tested it, hopefully if anyone runs into any other issues they can report them.


Sep 22 firedrill

Additional code and data files for running the firedrill of Sep 2022.
fd2209b-data.json is the adapted data packet, adding the action and burst id fields, followed by a report action.  Next time, it may be better if have input modules which can just take the packet as given and add these fields.
The json file is piped into snewpdag with the configuration file fd2209.csv.  This should result in a skymap showing the calculated localization.
test-fd2209.csv is meant to generate a SN, from the direction which was calculated above, to check the relative timings of the detectors.  It doesn't generate a skymap.  Instead, run it at least at loglevel INFO to get the neutrino burst times at each detector.

Added a JsonAlertInput plugin for reading a json file into the payload, along with the original packet, and configuration file fd2209-direct.csv.
We can use this pattern for reading from the SNEWS server as well, extracting Riccardo's code from app into a stand-alone input plugin.

I think this can be merged before Thursday firedrill and contribute to it! I actually prefer this alternative way where you pipe the file:
python -m snewpdag --log INFO --jsonlines snewpdag/data/fd2209.csv < snewpdag/data/fd2209b-data.json
So that the config needs no change for news firedrills, you just pipe a different input file from the snews coincidence server.

Concerning this:
Right now it seems it is not possible to pipe directly the original fd_sep_alert.json as input to the fd2209-direct.csv which converts to "the needed json format for snewpdag". And that would be ideally what we want for the firedrills, so that everything that needs to be done is:
snews_pt subscribe --no-firedrill -p "-m snewpdag --log INFO --jsonlines snewpdag/data/fdout-process-direct.csv <"
which actually does:
os.system(f"python -m snewpdag --log INFO --jsonlines snewpdag/data/fd2209.csv < {saved_json (firedrill output) }")
when an alert is published by snews_pt on the coincidence server

Thanks for pointing that out. I'll take a look at snews_pt.  This may just be a case of making a snewpdag plugin read stdin to the end of stream.

Thanks for pointing that out. I'll take a look at snews_pt. This may just be a case of making a snewpdag plugin read stdin to the end of stream.

This is the error when the direct firedrill output json is used as input to snewpdag with the *direct.csv:
(snewpy_env) marta@marta:~/snewpdag-firedrill$ python -m snewpdag --log INFO --jsonlines snewpdag/data/fd2209-direct.csv < snewpdag/data/fd_october_trial.json
Traceback (most recent call last):
File "/home/marta/miniconda3/envs/snewpy_env/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home/marta/miniconda3/envs/snewpy_env/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/marta/snewpdag-firedrill/snewpdag/main.py", line 5, in
app.run()
File "/home/marta/snewpdag-firedrill/snewpdag/dag/app.py", line 119, in run
data = ast.literal_eval(jsonline)
File "/home/marta/miniconda3/envs/snewpy_env/lib/python3.8/ast.py", line 59, in literal_eval
node_or_string = parse(node_or_string, mode='eval')
File "/home/marta/miniconda3/envs/snewpy_env/lib/python3.8/ast.py", line 47, in parse
return compile(source, filename, mode, flags,
File "", line 1
{
^
SyntaxError: unexpected EOF while parsing
which one does not get with the alternative command line when you pipe as input the modified json already and not the direct one

Turns out the command-line option --input is supposed to do something like this, but the packet still needs an action and a starting point.  The first part is easy (just add an action field).  For the second part we can use the first plugin defined, but I have to think about exactly how to do that, since a dictionary is in principle unordered.

Turns out the command-line option --input is supposed to do something like this, but the packet still needs an action and a starting point. The first part is easy (just add an action field). For the second part we can use the first plugin defined, but I have to think about exactly how to do that, since a dictionary is in principle unordered.

Yes, ideally:
Take original input json from firedrill with --input, and as starting point use JsonAlertInput plugin on that file.
(I guess action should just be "alert" right?)

snewpdag can now take a firedrill packet and add a default action and injection point from the command line:
python -m snewpdag --log INFO snewpdag/data/fd2209.csv --input snewpdag/data/fd_sep_alert.json
Perhaps one can use "-m snewpdag snewpdag/data/fd2209.csv --input" as an argument for snews_pt subscribe?

We tried that (which should have worked, as it worrks out of snews_pt, just snewpdag), but the output files (fits and png) are not created, maybe do to the warning. That's the output:
`INFO:root:Read detector database file snewpdag/data/detector_location_zerobias.csv
Control: received 1 alerts
/Users/amandadepoian/snews/supernova_communication/venv/lib/python3.8/site-packages/erfa/core.py:154: ErfaWarning: ERFA function "dtf2d" yielded 1 of "dubious year (Note 6)"
warnings.warn('ERFA function "{}" yielded {}'.format(func_name, wmsg),
Dts-out: received 1 alerts

Dts-out >>>> (1) alert
_id: 'SNEWS_Coincidence_ALERT 2022-10-19T18:18:30.118295'
detector_names: ['DS-20K', 'XENONnT']
false_alarm_probability: 0.00044
neutrino_times: ['2030-01-01T12:34:47.678999', '2030-01-01T12:34:45.678999']
p_values: [0.98, 0.98]
p_values average: 0.98
sent_time: '2022-10-19T18:18:30.118295'
server_tag: 'PURDUE SERVER'
sub list number: 0
action: 'alert'
name: 'Control'
history: ('Control', 'Dts')
dts:
('DS-20K', 'XENONnT'):
dt: 2.0
t1:<PHONE_NUMBER>.678999
t2:<PHONE_NUMBER>.678999
bias: 0.0
var: 1.8e-05
dsig1: 0.003
dsig2: -0.003
<<<< Dts-out <<<<
INFO:root:cache (DS-20K, XENONnT): {'dt': 2000.0, 't1':<PHONE_NUMBER>678.999, 't2':<PHONE_NUMBER>678.999, 'bias': 0.0, 'var': 18.000000000000004, 'dsig1': 3.0, 'dsig2': -3.0}`

Are there only two detectors? The min_dts argument for DiffPointing specifies the minimum number of time differences before it will try to calculate a sky map. Usually I've set it to 3, which requires at least 3 detectors.
Not sure what's going on with the warning message.

Regarding the warning message: the burst times are set in the year 2030, which is around the time the Unix epoch overflows 32 bits. Which may be why it's being flagged as possibly a dubious year. (This is one of the things I was trying to avoid with the weird 64-bit timestamps, and later with a "local" epoch, but I guess if one is converting a text string you're limited by the conversion function.)

Are there only two detectors? The min_dts argument for DiffPointing specifies the minimum number of time differences before it will try to calculate a sky map. Usually I've set it to 3, which requires at least 3 detectors.
Not sure what's going on with the warning message.

Oh right I completely forgot about the minimum of three detectors, that makes sense that the skymap was not generales in that case then

Is it all right to run the next firedrill from this branch? It may be better to leave things alone until then. I can merge this PR afterwards.

Is it all right to run the next firedrill from this branch? It may be better to leave things alone until then. I can merge this PR afterwards.

I can run a firedrill with this branch, yes, but still the skymap is not created...

Whoops - forgot how the time differences work.  We choose one detector, and then calculate the differences relative to that one, so 3 detectors give 2 time differences.  The third time difference doesn't add any information.  Sorry about that.
If you don't want to add another detector, you can change min_dts to 2.  It should produce a skymap.

Whoops - forgot how the time differences work. We choose one detector, and then calculate the differences relative to that one, so 3 detectors give 2 time differences. The third time difference doesn't add any information. Sorry about that.
If you don't want to add another detector, you can change min_dts to 2. It should produce a skymap.

mmm but three detectors should give three time differences:
dt1 = tDUNE - tDS-20
dt2 = tDUNE - tXENONnT
dt3 = tDS-20 - tXENONnT
(and all should give information?)
right?
But okey, I will anyway try with min_dts =2

Whoops - forgot how the time differences work. We choose one detector, and then calculate the differences relative to that one, so 3 detectors give 2 time differences. The third time difference doesn't add any information. Sorry about that.
If you don't want to add another detector, you can change min_dts to 2. It should produce a skymap.

mmm but three detectors should give three time differences:
dt1 = tDUNE - tDS-20 dt2 = tDUNE - tXENONnT dt3 = tDS-20 - tXENONnT
(and all should give information?) right?
But okey, I will anyway try with min_dts =2

I do get the skymap changing min_dts=2, but I get a very precise point with only two dts, which is not what I expect... I expected a band

I'll merge the PR tonight.
In the meantime, a couple of notes from today's firedrill:

null in p_values was causing ast.literal_eval() to throw a ValueError. Need to see if there's a way to ignore malformed data.
an unknown detector also shouldn't cause a problem, but should result in a non-fatal error message of some kind. DetectorDB returns None when it can't find a detector. DiffPointing (among others) need to handle that.


Update swift-argument-parser dependency

Overview

#178 added Swift 5.6 support, but f38ae33 limited the version flexibility of the swift-argument-parser dependency. The reasoning for this is explained in this comment.
This makes package resolution for other packages that have Mockolo as a dependency less flexible. So, to have the same flexibility as before f38ae33, but still account for the issue mentioned in the comment linked above, the version range of the  swift-argument-parser dependency is being made dependent on the Swift version.

@uhooi i'd love to see this un-pinned

Thanks @uhooi, do you know what could be done to release a 1.7.1 version that includes this?

I will now release.

@pablocornejo Released!
https://github.com/uber/mockolo/releases/tag/1.7.1


empty txt file after exporting dataset with yolov8 format

When I am try to export a Video dataset from label-studio using the yolov8 format I get an .zip file with the folders with one is named labels with an empty txt file in it. How can I solve this problem? I am updatet label-studio today but never made a video dataset earlier.

Hi @bauerhartmut - we don't actually offer yolov8 export; our yolo export is intended for image datasets rather than video. What I'd recommend doing instead is exporting in json format, then converting the result to your intended format (though unfortunately, we don't offer any tools for this conversion just yet)

Hi,
@jombooth  this actually happens also for images ( I tried Keypoint labelling)

Hi @bauerhartmut - we don't actually offer yolov8 export; our yolo export is intended for image datasets rather than video. What I'd recommend doing instead is exporting in json format, then converting the result to your intended format (though unfortunately, we don't offer any tools for this conversion just yet)

The UI offers the option of YOLOv8 OBB, but it also exports empty labels txt files.


Incorrect text displayed back to users

Issue moved from MicrosoftDocs/feedback#2853

Please respond to @mniem.

From @mniem on Thursday, June 11, 2020 9:09:40 PM
Issue is on this  page.
Gets or sets <code>true to enable client affinity; false to stop sending session affinity cookies, which route client requests in the same session to the same instance. Default is true.

Issue moved from MicrosoftDocs/feedback#2853

Please respond to @welcome[bot].

From @welcome[bot] on Thursday, June 11, 2020 9:09:42 PM
Thank you for creating the issue! One of our team members will get back to you shortly with additional information. If this is a product issue, please close this and contact the particular product's support instead (see https://support.microsoft.com/allproducts for the list of support websites).

@mnriem thanks for finding this!
This is coming from an auto-generated part of our library.
Adding @calvinsID as he seems to have last modified the file that generates this.

@mnriem thanks for finding this!
This is coming from an auto-generated part of our library.
Adding @calvinsID as he seems to have last modified the file that generates this.


UX Report Out - Call for Records

Title of ticket: UX Report Out - Call for Records
Description
Summarize findings with comparison of existing and new proposed user journey.
Document Pain points and action items for upcoming prototype development
Dependencies
Study sessions need to be complete first
DOD

[x] User journey map of existing system
[x] User journey map of new proposed system
[x] Visual to report out at Sprint Demo

Link to Miro Board - with Visual of Report Out: https://miro.com/app/board/o9J_l6d8LwM=/

Completed in Demo July 20th


[NEW ICON] Shadcn UI

Shadcn UI
Why?
A popular beautifully designed components that you can copy and paste into your apps. Made with Tailwind CSS. Open source.
Reference Image

I created a new project since this project is no longer updating & the author left it, shadcnui is available skills-icons
https://skills-icons.vercel.app/api/icons?i=shadcnui

Thanks your icons looks great


mapPackage() does not work with subpackes

Hi all,
I don't want to map every single Entity-class only to have the indexes created correctly (at the moment, if you don't map a class explicitly, the application works, but no index is created other then the index on "_id").
What I want to have is the folloing:
morphia.getMapper().getOptions().setMapSubPackages(true);
morphia.mapPackage("<basicPackageName>", true);

I think, that the method "ReflectionUtils.isSubPackage()" has a problem, because the comparison would work, but currently, there is added a period to the parentPackgeName, so the equals()-method will fail (without the period, everything would work fine)...
Or do I oversee something here?
Thanks in advance,
Ulrich

Are you saying the subpackages aren't getting mapped properly?  The tests are all green at the moment.

< The tests are all green at the moment>
:-) Yes, because the test does not check for a class in a subpackage. The resulting set only contains classes from the parent "org.junit".
For example: org/junit/rules  results in "false" in the method "isSubPackage()" with "org/junit" as parent, but you see, that it should result in "true".
private static boolean isSubPackage(final String fullPackageName, final String parentPackageName) {
        return fullPackageName.startsWith(parentPackageName + ".");
}

The period at the end breaks the "startWith()".

Got it.  I'll take another look at the test then.  Thanks.

I provided a pull-request for this issue. Perhaps, you can take a look at that.

Looks good.  Thanks for the patch.
fixed  https://github.com/mongodb/morphia/commit/04c9a0ca8227eb101e955755ba744d89c2f3206c