Including nb2workflow metadata

An annotation is created and added to the graph at the end of a renku run command, within the activity_annotations hook.

These are the annotations added to the graph :
...
<http://odahub.io/workflows#out_e3eb519e> a oda:workflow ;
    oda:expects <http://odahub.io/workflows/out_e3eb519e/parameter_bindings#DEC>,
        <http://odahub.io/workflows/out_e3eb519e/parameter_bindings#RA>,
        <http://odahub.io/workflows/out_e3eb519e/parameter_bindings#T1>,
        <http://odahub.io/workflows/out_e3eb519e/parameter_bindings#T2>,
        <http://odahub.io/workflows/out_e3eb519e/parameter_bindings#a>,
        <http://odahub.io/workflows/out_e3eb519e/parameter_bindings#dT>,
        <http://odahub.io/workflows/out_e3eb519e/parameter_bindings#src_name> ;
    oda:location "git@renkulab.io:astronomy/mmoda/fermi.git#ef8f8c5" .

...

<http://odahub.io/workflows/out_e3eb519e/parameter_bindings#DEC> a oda:PointOfInterestDEC .

<http://odahub.io/workflows/out_e3eb519e/parameter_bindings#RA> a oda:PointOfInterestRA .

<http://odahub.io/workflows/out_e3eb519e/parameter_bindings#T1> a oda:StartTime .

<http://odahub.io/workflows/out_e3eb519e/parameter_bindings#T2> a oda:EndTime .

<http://odahub.io/workflows/out_e3eb519e/parameter_bindings#a> a xsd:int .

<http://odahub.io/workflows/out_e3eb519e/parameter_bindings#dT> a xsd:int .

<http://odahub.io/workflows/out_e3eb519e/parameter_bindings#src_name> a oda:AstrophysicalObject .
...

Ok I can extract the metadata via nb2workflow, but I am a bit lost on how to best include those within the graph.
Perhaps we should discuss it together, looking directly at the graph...

by using the input notebook fermi_lc.ipynb for this example, I now get less annotation, as it seems that one parameter binding less is found by the nb2rdf.

These are the annotations added to the graph :
...
<http://odahub.io/workflows#fermi_lc_5bb8e0d5> a oda:workflow ;
    oda:expects <http://odahub.io/workflows/fermi_lc_5bb8e0d5/parameter_bindings#DEC>,
        <http://odahub.io/workflows/fermi_lc_5bb8e0d5/parameter_bindings#RA>,
        <http://odahub.io/workflows/fermi_lc_5bb8e0d5/parameter_bindings#T1>,
        <http://odahub.io/workflows/fermi_lc_5bb8e0d5/parameter_bindings#T2>,
        <http://odahub.io/workflows/fermi_lc_5bb8e0d5/parameter_bindings#dT>,
        <http://odahub.io/workflows/fermi_lc_5bb8e0d5/parameter_bindings#src_name> ;
    oda:location "git@renkulab.io:astronomy/mmoda/fermi.git#b08df21" .

...

<http://odahub.io/workflows/fermi_lc_5bb8e0d5/parameter_bindings#DEC> a oda:PointOfInterestDEC .

<http://odahub.io/workflows/fermi_lc_5bb8e0d5/parameter_bindings#RA> a oda:PointOfInterestRA .

<http://odahub.io/workflows/fermi_lc_5bb8e0d5/parameter_bindings#T1> a oda:StartTime .

<http://odahub.io/workflows/fermi_lc_5bb8e0d5/parameter_bindings#T2> a oda:EndTime .

<http://odahub.io/workflows/fermi_lc_5bb8e0d5/parameter_bindings#dT> a xsd:int .

<http://odahub.io/workflows/fermi_lc_5bb8e0d5/parameter_bindings#src_name> a oda:AstrophysicalObject .
...

I attached the workflow annotations to the activity so to be consistent with the approach used to build the graph, where we for each activity we extract the entities for the inputs and outputs. In this way, I extract the various parameter-bindings starting from the entityInput (fermi_lc.ipynb in the example).

Another, partial, result:

Looks interesting but since review is not requested I suppose it's not ready? Anyway we can discuss today.

As discussed, now the type assigned to each parameter_binding is is inserted in the graph

Color also updated


Readme fixes

There are a few errors in the README that prevent this from working.

This was fixed in #8

Promport wasn't fixed in #8 . Good catches.

Ah missed that!


add pullpreview config

Add ticket reference to Pull Request title: e.g. 'FS-123: Add content', if there is no ticket prefix with BAU
Change description
Testing pullpreview

[ ] Unit tests and other appropriate tests added or updated
[ ] README and other documentation has been updated / added (if needed)
[ ] Commit messages are meaningful and follow good commit message guidelines (e.g. "FS-XXXX: Add margin to nav items preventing overlapping of logo")

How to test
If manual testing is needed, give suggested testing steps
Screenshots of UI changes (if applicable)

Not using any more since closing the PR


Update dashboards-json-configmap.yaml

Fix grammatical errors

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] Title of the PR starts with chart name (e.g. [stable/mychartname])

@Nctllnty
Thanks for contribution.
Could you bump the chart to latest and sign DCO as on the bottom of this PR page? Click Details for detail.
/assign


2-way bound value parameter of all Input components

by spec, all of the Input components should have at least one "2-way bound" value parameter.
there are still some input components that are not compatible with this important rule.

This issue has been solved in multiple pull requests.


Semver can't be used on pecl

There is an issue with hyphen https://github.com/semver/semver/issues/145
We can't use semver 1.0 1.8.0-alpha1 or 2.0 1.8.0-alpha.1 on pecl:
PEAR_PackageFileManager2 Error: Package validation failed:
Error: Version type <release> is not a valid version (1.8.0-alpha1)

The version in the package.xml must also match with the source code:

Extension version mismatch between the package.xml (1.8.0alpha1) and the source code (1.8.0-alpha1)

What format we should follow?
Package versioning:
https://packagist.org/about#managing-package-versions
https://getcomposer.org/doc/articles/versions.md
https://en.opensuse.org/openSUSE:Package_versioning_guidelines#Pre-Release_packages
https://fedoraproject.org/wiki/Package_Versioning_Examples

Ice\Version::get() returns version in semver 2.0 spec: 1.8.0-alpha.1 and this will stay. In the ice section in phpinfo() we will have to put 1.8.0alpha1. We can't use semver 1.0 as we do currently:
https://github.com/ice/framework/blob/c36198b8dc757858930bfc863ce1b1a1d3fe8a9b/config.json#L6
The release tags will also be in 1.8.0alpha1 format.


Add Health Data sensors

This PR adds support for the new car health API.
TODO:

[ ] Test when merged with 1.9.0(rcX)
[ ] Add translations
[ ] Check if we can change the icon to show when there actually is a warning

Resolves #183

Perhaps we can merge process #227 first and then update this with dataclass models?

Yeah I agree, I'll go review that PR tomorrow!

You want #241 merged to fix some issues with the model I believe.

There are some additional work on the dataclasses and sensors #249 that will simplify this PR.


Generic control elements for parts & scenes

Background
The scene/part can have any number of attributes. At this moment, they have (1) name (string), (2) folded (boolean). Adding more attributes is easy, but the problem is the fluent nature of parts and scenes in the editor. You can create and delete them on-the-fly with backspaces, delete and typing, and I have no intention to change that.
Data fields
With new nested editor, the scene/part header has become a "data field", reflecting the name attribute tied to scene itself. When you write something to this data field, it is modifying the parent scene block attributes.
With the same principle, we could implement other data fields, that is, fields that control some parent info.
Filler: The most urgent feature would be a "filler" element, which sets the length of the scene (or part) to certain number. This would be used in the diagram section: there you would set the target length to scenes, so that you could examine your story structure early on.
Tags: In some more distant future, we might need scene tagging. In many other editors, you can set a viewpoint to a scene, which is intended to help organizing stories with many parallel plot lines and viewpoints. We can go further: the scene tag is just a tag, it can be a character, place, artifact and so on.
Implementation considerations: A "brute force" way could be to update all the controlled attributes when normalizing the block. It is possible that it is the only realiable way in the end.
But I am always bit worried when adding block scanning to functions which are executed on every single key press. They may drop the responsiveness of the editor component too low, especially if you are working with large text bunch. There is already a big block scan (withIDs() scanning through all elements to check that they have unique ID) and I wouldn't like to add more of them.
So, if there is clever and light-weigth solution to update the attributes from control fields realiably, I am more than happy.

At the moment, fillers and tags are already implemented. They are not scene/part control blocks, but regular, separate blocks within the text. I'm not sure, if this feature is ever needed, we might be just fine with the current implementation.


ava test runner

easier to read output and no need for t.end()
no big deal but saw the earlier conversation re tape, and using it is super easy to implement.

fixed the build - this, #20 , and #23 all fix #21 but as such will also merge conflict so whichever one goes first, i can resolve those conflicts afterward

Ready to go!

@osdiab same here :)

cool that should do it!

Awesome! Thanks for all the PRs 💪 👏 🎉


splink using spark is slower and complex then 2.1.14 version

What happens?
Hey I ran this new version of splink on a spark, And I found that the latest version of splink is much slower than the previous version 2.1.14, And also the parameters were too simple, but the newest version has complex parameters. May I know if my statement is correct or not?Is this version not made for spark?
To Reproduce
Supposed to be faster than the previous version 2.1.14 for spark.
OS:
ubuntu
Splink version:
3.4.2
Have you tried this on the latest master branch?

[X] I agree

Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

[X] I agree

For most jobs, Splink 3 is significantly faster than Splink 2 using Spark.  Do you have an reproducible example of a job that's slower with Splink 3?

Closing in favour of https://github.com/moj-analytical-services/splink/discussions/909


[C-Api/Service] add new API (ML-API ext)

Add new API set for ML service, these functions support constructing new handle from json configuration.

type for ml-service: single, pipeline

TODO: need discussion for ml-service remote

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #454. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @jaeyun-jung, Oooops. The commit has an invalid executable file. The file is c/src/ml-api-service-extension.c. Please turn the executable bits off. Run chmod 644 file-name command.

:octocat: cibot: @jaeyun-jung, Oooops. The commit has an invalid executable file. The file is c/src/ml-api-service-extension.c. Please turn the executable bits off. Run chmod 644 file-name command.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/454-202402021451340.98993110656738-dfa65eeafcd1e1cd638118af8f7e3580c28fe429/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/454-202402051904550.42917990684509-6ef890d22bfc463726bd62464d9a10b248c90b1a/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/454-202402202030070.35509300231934-6b25c678de94562af7779327bcb72d4784e49534/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/454-202402202056540.9779679775238-f135b3d5e048c07d966090fa28d3f77f333687c0/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/454-202402211433570.98222208023071-3f8db57ec16c85facc6eb1f7ed2923dbe675adb9/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/454-202402231623300.58707189559937-54626f4e9759871caf8b90ce736573945f771523/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/454-202403042050510.46929311752319-d0c012253222af6d97d5ab11b8344eb08b5bc0b6/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/454-202403061213210.19146299362183-969aad1692ace99c269c2edb78f37f6b1af19ddc/.

:octocat: cibot: @jaeyun-jung, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nnstreamer-api/ci/repo-workers/pr-checker/454-202403071526400.11145496368408-587d9620cfa5abc7b13e08fc38aaf63ebf68f06e/.

Now ready to prepare new API for next Tizen release.


add command to switch implementation and interface

This PR is adding the new command switch-impl-intf which enables users to switch the implementation *.res to interface *.resi back and forth. Actually, we can find this same feature in the OCaml vscode extension too.
I hope this feature helps users to open the implementation file once after navigating to the interface file with the go to definition command.
I'm not sure whether the contribution is open to not members. If it is open, I'm going to add a button in the editor title menu.
https://user-images.githubusercontent.com/36963424/166794591-eb110a6f-1e2d-46d6-a625-886e236912c2.mov

Looks good, only had a small nitpick. Which icon will you use for the button?

Looks good, only had a small nitpick. Which icon will you use for the button?

@fhammerschmidt I don't have a particular skill to design an icon 🫣 I found the free svg repo in which we might pick one. https://www.svgrepo.com/svg/392618/arrow-large-update-direction-navigation I would be looking as below.

If the ReScript core team has a resource to create an icon for it, I love to use it.

I think the icon is fine, but I guess you would need to add an attribution to the README (CC license)?

I like this!
One thing I thought of though - maybe we should prompt the user before creating the interface file, if it doesn't already exist? Let them decide whether to create (and then open) the interface file. I think it might be confusing otherwise, as in "oh did I already have an interface file for this file?".

@zth Very good point! I’ll add the step to ask user for creating the interface.

@fhammerschmidt I've added the button in the editor title menu. https://github.com/rescript-lang/rescript-vscode/pull/404/commits/14bcf09aa8150384a4b6d16f7a8007993daf4769
@zth I've added the popup(window.showInformationMessage) to ask before creating the interface. https://github.com/rescript-lang/rescript-vscode/pull/404/commits/4fc40e372acb8340157ced35bb308afb8e808bf2

@zth Great! 😃


Add thirdparty library etcpak for faster imports.

Squish and etc modules have been modified.
Modifications for mingw.
Some times from TPS sample.
ook ook ook :banana:
Please help measure if this is faster or not.
ETCPAK encode took 74 ms
Encoding format: ETC2_RA_AS_RG
ETCPAK encode took 60 ms
Encoding format: DXT5 RGBA8
ETCPAK encode took 74 ms
Encoding format: ETC2_RGB8
ETCPAK encode took 130 ms
Encoding format: DXT1 RGB8
ETCPAK encode took 7 ms
Encoding format: ETC
ETCPAK encode took 30 ms
Encoding format: FORMAT_DXT5_RA_AS_RG
ETCPAK encode took 9 ms
Encoding format: ETC2_RA_AS_RG
ETCPAK encode took 135 ms
Encoding format: DXT5 RGBA8
ETCPAK encode took 8 ms
Encoding format: ETC2_RGB8

Test using.
// https://github.com/godotengine/godot/blob/master/editor/editor_file_system.cpp#L1974
for (int i = 0; i < files.size(); i++) {
  uint64_t t = OS::get_singleton()->get_ticks_msec();
  pr.step(files[i].path.get_file(), i);
  _reimport_file(files[i].path);
  uint16_t final = OS::get_singleton()->get_ticks_msec() - t;
  print_line(vformat("%s import took %f.001 seconds", files[i].path, rtos(final / 1000.0)));
}

From a 8k texture load test, 37 seconds is get_pixel and 13 seconds is texture compression (this pr),
https://github.com/fire/texture-import-godot-project/tree/main/peacock

Added some flags:
env.Prepend(CCFLAGS=["-msse4.1"])
env.Prepend(CCFLAGS=["-mavx"])
env.Prepend(CCFLAGS=["-mavx2"])
env.Prepend(CCFLAGS=["-march=skylake"])

I don't have the full numbers because there's another pr for better import time logging but here they are.
ETCPAK encode took 920 ms (dxt5)
ETCPAK encode took 3130 ms (etc2)

etc2 import with quicketc2 modified optimization which need to be up streamed.

Does this PR include the QuickETC2 patch? Because that's not documented and it says it's on https://github.com/wolfpld/etcpak/commits/403d38b3f1cb347c196d845d0a05e44a00d17169 which is upstream master without QuickETC2.

We're not using QuickEtc2.
Making other changes.

I added the copyright from jtbr's bswap and bswap64.

I'll try to get this error fixed upstream.
type 'int' to 'uint32_t' type narrowing.

https://github.com/wolfpld/etcpak/issues/11

I was able to build etcpak on mingw with only the following diff:
diff --git a/ProcessRGB.cpp b/ProcessRGB.cpp
index 220d5c5..b9e90a8 100644
--- a/ProcessRGB.cpp
+++ b/ProcessRGB.cpp
@@ -1,5 +1,6 @@
 #include <array>
 #include <string.h>
+#include <limits>

 #ifdef __ARM_NEON
 #  include <arm_neon.h>
diff --git a/System.cpp b/System.cpp
index 1383d0e..a09b289 100644
--- a/System.cpp
+++ b/System.cpp
@@ -35,7 +35,7 @@ unsigned int System::CPUCores()

 void System::SetThreadName( std::thread& thread, const char* name )
 {
-#ifdef _WIN32
+#ifdef _MSC_VER
     const DWORD MS_VC_EXCEPTION=0x406D1388;

 #  pragma pack( push, 8 )

This was a cross-build so I will try on native windows as well, but I don't think we need quite as many chances to etcpak to make it work for us.

@hpvb With your changes (and without https://github.com/godotengine/godot/pull/47370/commits/853b03548de68d66749809df355e56817b74d1d3) I still get an error trying to include byteswap.h here:
https://github.com/wolfpld/etcpak/blob/403d38b3f1cb347c196d845d0a05e44a00d17169/ProcessRGB.cpp#L24-L30
Removing this #else then works fine as what we want for MinGW/GCC is to use the __builtin_bswap32 and __builtin_bswap64 which are aliases right below. Might break other platforms, not so sure what's the exact intent of this code since upstream seems to use _WIN32 and _MSC_VER interchangeably.

I made a branch based on this PR, with the second commit removed, and replaced by the above patch (minus the addition of <limits> which didn't seem needed in the end?) + some other packaging cleanups. WDYT?

I'm not able to check the code by running it, but from a textual review, the code follows logically.

I made a version with both commits squashed together and the commit message edited to add some more details (please confirm that I understood and described the changes correctly):
https://github.com/akien-mga/godot/tree/etcpak-cleaned-up
I'll try to do some tests building on Windows with MSVC and MinGW to confirm that it works OK.

The commit message is correct.
Minor comments:

lz4/lz4.c What's the difference between lz4 and minil4?
I also removed an etc framing format -- pkm. I've not heard of people using it.

I made a branch based on this PR, with the second commit removed, and replaced by the above patch (minus the addition of <limits> which didn't seem needed in the end?) + some other packaging cleanups. WDYT?
https://github.com/akien-mga/godot/tree/etcpak-fixup

<limits> is really missing and it will break when we update to gcc 10 on mingw.

Added <limits> back. Updated my branch with further fixes to the SCsub: https://github.com/akien-mga/godot/tree/etcpak-cleaned-up
I clarified the dependency on libpng, and remove the two defines (NO_GZIP and PNG_INTEL_SSE) which would likely conflict with our zlib and libpng build depending on what the build order is (redefining defines which impact a header which has possibly already been parsed likely doesn't work reliably). We can re-evaluate them if they're relevant to enable for the whole engine, but not only for etcpak's sake.
Now I see the narrowing errors on the CI which are specific to LLVM, not to mingw:
https://github.com/akien-mga/godot/runs/2325019211?check_suite_focus=true
So I added back @fire's changes with a dedicated patch (separate from the mingw patch). I don't know if they're the proper way to fix the issue, it's just what LLVM recommends (so I assume it's just making explicit what happens otherwise - doesn't mean that it's not an actual bug that should be fixed upstream).

OK, building with native clang on Linux I need to do the following changes, which is closer to ifire's original work:
diff --git a/BlockData.cpp b/BlockData.cpp
index a2cd032..78f0f55 100644
--- a/BlockData.cpp
+++ b/BlockData.cpp
@@ -340,10 +340,10 @@ static etcpak_force_inline void DecodeT( uint64_t block, uint32_t* dst, uint32_t
     const auto c3b = clampu8( cb1 - table59T58H[codeword] );

     const uint32_t col_tab[4] = {
-        cr0 | ( cg0 << 8 ) | ( cb0 << 16 ) | 0xFF000000,
-        c2r | ( c2g << 8 ) | ( c2b << 16 ) | 0xFF000000,
-        cr1 | ( cg1 << 8 ) | ( cb1 << 16 ) | 0xFF000000,
-        c3r | ( c3g << 8 ) | ( c3b << 16 ) | 0xFF000000
+        uint32_t(cr0 | ( cg0 << 8 ) | ( cb0 << 16 ) | 0xFF000000),
+        uint32_t(c2r | ( c2g << 8 ) | ( c2b << 16 ) | 0xFF000000),
+        uint32_t(cr1 | ( cg1 << 8 ) | ( cb1 << 16 ) | 0xFF000000),
+        uint32_t(c3r | ( c3g << 8 ) | ( c3b << 16 ) | 0xFF000000)
     };

     const uint32_t indexes = ( block >> 32 ) & 0xFFFFFFFF;
@@ -395,10 +395,10 @@ static etcpak_force_inline void DecodeTAlpha( uint64_t block, uint64_t alpha, ui
     const auto c3b = clampu8( cb1 - table59T58H[codeword] );

     const uint32_t col_tab[4] = {
-        cr0 | ( cg0 << 8 ) | ( cb0 << 16 ),
-        c2r | ( c2g << 8 ) | ( c2b << 16 ),
-        cr1 | ( cg1 << 8 ) | ( cb1 << 16 ),
-        c3r | ( c3g << 8 ) | ( c3b << 16 )
+        uint32_t(cr0 | ( cg0 << 8 ) | ( cb0 << 16 )),
+        uint32_t(c2r | ( c2g << 8 ) | ( c2b << 16 )),
+        uint32_t(cr1 | ( cg1 << 8 ) | ( cb1 << 16 )),
+        uint32_t(c3r | ( c3g << 8 ) | ( c3b << 16 ))
     };

     const uint32_t indexes = ( block >> 32 ) & 0xFFFFFFFF;
@@ -442,10 +442,10 @@ static etcpak_force_inline void DecodeH( uint64_t block, uint32_t* dst, uint32_t
     const auto codeword = codeword_hi | codeword_lo;

     const uint32_t col_tab[] = {
-        clampu8( r0 + table59T58H[codeword] ) | ( clampu8( g0 + table59T58H[codeword] ) << 8 ) | ( clampu8( b0 + table59T58H[codeword] ) << 16 ),
-        clampu8( r0 - table59T58H[codeword] ) | ( clampu8( g0 - table59T58H[codeword] ) << 8 ) | ( clampu8( b0 - table59T58H[codeword] ) << 16 ),
-        clampu8( r1 + table59T58H[codeword] ) | ( clampu8( g1 + table59T58H[codeword] ) << 8 ) | ( clampu8( b1 + table59T58H[codeword] ) << 16 ),
-        clampu8( r1 - table59T58H[codeword] ) | ( clampu8( g1 - table59T58H[codeword] ) << 8 ) | ( clampu8( b1 - table59T58H[codeword] ) << 16 )
+        uint32_t(clampu8( r0 + table59T58H[codeword] ) | ( clampu8( g0 + table59T58H[codeword] ) << 8 ) | ( clampu8( b0 + table59T58H[codeword] ) << 16 )),
+        uint32_t(clampu8( r0 - table59T58H[codeword] ) | ( clampu8( g0 - table59T58H[codeword] ) << 8 ) | ( clampu8( b0 - table59T58H[codeword] ) << 16 )),
+        uint32_t(clampu8( r1 + table59T58H[codeword] ) | ( clampu8( g1 + table59T58H[codeword] ) << 8 ) | ( clampu8( b1 + table59T58H[codeword] ) << 16 )),
+        uint32_t(clampu8( r1 - table59T58H[codeword] ) | ( clampu8( g1 - table59T58H[codeword] ) << 8 ) | ( clampu8( b1 - table59T58H[codeword] ) << 16 ))
     };

     for( uint8_t j = 0; j < 4; j++ )
@@ -489,10 +489,10 @@ static etcpak_force_inline void DecodeHAlpha( uint64_t block, uint64_t alpha, ui
     const auto tbl = g_alpha[(alpha >> 48) & 0xF];

     const uint32_t col_tab[] = {
-        clampu8( r0 + table59T58H[codeword] ) | ( clampu8( g0 + table59T58H[codeword] ) << 8 ) | ( clampu8( b0 + table59T58H[codeword] ) << 16 ),
-        clampu8( r0 - table59T58H[codeword] ) | ( clampu8( g0 - table59T58H[codeword] ) << 8 ) | ( clampu8( b0 - table59T58H[codeword] ) << 16 ),
-        clampu8( r1 + table59T58H[codeword] ) | ( clampu8( g1 + table59T58H[codeword] ) << 8 ) | ( clampu8( b1 + table59T58H[codeword] ) << 16 ),
-        clampu8( r1 - table59T58H[codeword] ) | ( clampu8( g1 - table59T58H[codeword] ) << 8 ) | ( clampu8( b1 - table59T58H[codeword] ) << 16 )
+        uint32_t(clampu8( r0 + table59T58H[codeword] ) | ( clampu8( g0 + table59T58H[codeword] ) << 8 ) | ( clampu8( b0 + table59T58H[codeword] ) << 16 )),
+        uint32_t(clampu8( r0 - table59T58H[codeword] ) | ( clampu8( g0 - table59T58H[codeword] ) << 8 ) | ( clampu8( b0 - table59T58H[codeword] ) << 16 )),
+        uint32_t(clampu8( r1 + table59T58H[codeword] ) | ( clampu8( g1 + table59T58H[codeword] ) << 8 ) | ( clampu8( b1 + table59T58H[codeword] ) << 16 )),
+        uint32_t(clampu8( r1 - table59T58H[codeword] ) | ( clampu8( g1 - table59T58H[codeword] ) << 8 ) | ( clampu8( b1 - table59T58H[codeword] ) << 16 ))
     };

     for( uint8_t j = 0; j < 4; j++ )
diff --git a/ProcessRGB.cpp b/ProcessRGB.cpp
index 220d5c5..b9e90a8 100644
--- a/ProcessRGB.cpp
+++ b/ProcessRGB.cpp
@@ -1,5 +1,6 @@
 #include <array>
 #include <string.h>
+#include <limits>

 #ifdef __ARM_NEON
 #  include <arm_neon.h>
diff --git a/System.cpp b/System.cpp
index 1383d0e..a09b289 100644
--- a/System.cpp
+++ b/System.cpp
@@ -35,7 +35,7 @@ unsigned int System::CPUCores()

 void System::SetThreadName( std::thread& thread, const char* name )
 {
-#ifdef _WIN32
+#ifdef _MSC_VER
     const DWORD MS_VC_EXCEPTION=0x406D1388;

 #  pragma pack( push, 8 )

https://github.com/fire/godot/tree/importer-timings can be helpful

Quick test of importing all assets of the TPS demo (note: includes some DAEs and glTFs too):

Before this PR: 6m30s
After this PR: 1m13s

Example:

Before:

res://enemies/red_robot/textures/red_robot_albedo.png import took 2.871 seconds
res://enemies/red_robot/textures/red_robot_emission.png import took 1.115 seconds
res://enemies/red_robot/textures/red_robot_normal.png import took 3.756 seconds
res://enemies/red_robot/textures/red_robot_orm.png import took 3.275 seconds

After:

res://enemies/red_robot/textures/red_robot_normal.png import took 0.869 seconds
res://enemies/red_robot/textures/red_robot_emission.png import took 0.489 seconds
res://enemies/red_robot/textures/red_robot_albedo.png import took 0.659 seconds
res://enemies/red_robot/textures/red_robot_orm.png import took 0.797 seconds

So there's already a pretty significant gain on this very unscientific test. This can likely be improved further by ensuring that we properly use the available SSE4.1 / AVX2 code paths on compatible CPUs.

Thanks!

#elif !defined(__APPLE__) && !defined(__MINGW32__ )
    pthread_setname_np( thread.native_handle(), name );
#endif

LLVM + MINGW still requires the MINGW32  check.

#elif !defined(__APPLE__) && !defined(__MINGW32__ )
    pthread_setname_np( thread.native_handle(), name );
#endif

LLVM + MINGW still requires the __MINGW32__ check.

That doesn't seem like a correct fix. What's the error exactly?
This API is not compiler dependent, it's likely related to whether your MinGW distro is configured to use pthread or another thread API. Typically MinGW-GCC distros come with winpthreads, there might be a switch or a package you need for mingw-llvm.

If anyone is interested, I did some work to backport this change (and follow-ups) to the 3.x branch, which could help speed import times significantly:
https://github.com/akien-mga/godot/commits/3.x-etcpak
It's WIP and I don't plan to work further on it as it turns out etcpak doesn't support all formats needed for GLES2 support in the 3.x branch, so a hybrid solution would be needed (keeping the old importers for the formats that etcpak doesn't support).


YARN-10314. YarnClient throws NoClassDefFoundError for WebSocketException with only shaded client jars

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 30s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
1m  1s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
18m 44s
trunk passed

+1 :green_heart:
compile
0m 24s
trunk passed

+1 :green_heart:
mvnsite
0m 48s
trunk passed

+1 :green_heart:
shadedclient
35m  3s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 44s
trunk passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 26s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
6m 16s
the patch passed

+1 :green_heart:
compile
0m 15s
the patch passed

+1 :green_heart:
javac
0m 15s
the patch passed

+1 :green_heart:
mvnsite
0m 32s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
13m 34s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 36s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 18s
hadoop-client-runtime in the patch passed.

+1 :green_heart:
unit
0m 18s
hadoop-client-minicluster in the patch passed.

+1 :green_heart:
asflicense
0m 31s
The patch does not generate ASF License warnings.

61m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-2075/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2075

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml

uname
Linux 591f59e2a4f7 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 81d8a887b04

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-2075/1/testReport/

Max. process+thread count
460 (vs. ulimit of 5500)

modules
C: hadoop-client-modules/hadoop-client-runtime hadoop-client-modules/hadoop-client-minicluster U: hadoop-client-modules

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-2075/1/console

versions
git=2.17.1 maven=3.6.0

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

@aajisaka @steveloughran @jojochuang @ayushtkn
Please review, thanks

I ran following on hadoop dist built by mvn clean install -DskipTests -Pdist -Pnative. The patch fixed the ClassNotFoundException reported on the JIRA.
java -classpath etc/hadoop:share/hadoop/common/lib/*:share/hadoop/client/*:share/hadoop/mapreduce/hadoop-mapreduce-examples-3.4.0-SNAPSHOT.jar org.apache.hadoop.examples.QuasiMonteCarlo 1 100

I ran following on hadoop dist built by mvn clean install -DskipTests -Pdist -Pnative. The patch fixed the ClassNotFoundException reported on the JIRA.
java -classpath etc/hadoop:share/hadoop/common/lib/*:share/hadoop/client/*:share/hadoop/mapreduce/hadoop-mapreduce-examples-3.4.0-SNAPSHOT.jar org.apache.hadoop.examples.QuasiMonteCarlo 1 100

Thanks @iwasakims for verifying.

+1 pending Jenkins. Thanks.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
24m 20s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
1m  9s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
19m 44s
trunk passed

+1 :green_heart:
compile
0m 23s
trunk passed

+1 :green_heart:
mvnsite
0m 47s
trunk passed

+1 :green_heart:
shadedclient
35m 59s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 44s
trunk passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 25s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
6m 20s
the patch passed

+1 :green_heart:
compile
0m 15s
the patch passed

+1 :green_heart:
javac
0m 15s
the patch passed

+1 :green_heart:
mvnsite
0m 31s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  3s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
13m 46s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 36s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 18s
hadoop-client-runtime in the patch passed.

+1 :green_heart:
unit
0m 18s
hadoop-client-minicluster in the patch passed.

+1 :green_heart:
asflicense
0m 31s
The patch does not generate ASF License warnings.

86m 19s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-2075/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2075

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml

uname
Linux 631bed4802c3 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 81d8a887b04

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-2075/2/testReport/

Max. process+thread count
414 (vs. ulimit of 5500)

modules
C: hadoop-client-modules/hadoop-client-runtime hadoop-client-modules/hadoop-client-minicluster U: hadoop-client-modules

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-2075/2/console

versions
git=2.17.1 maven=3.6.0

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

Thanks @aajisaka @iwasakims and @ayushtkn  for reviews.
Merged


[5.8] Fail assertSee and assertSeeText if value is null

Fixes issue where a null value is sent to assertSee or assertSeeText results in the test passing. As a null value, will always pass as valid.
Consider the following test, which is often given in examples. To list some model information on a page and follow Test Driven Development.

    public function testListCurrentModels()
    {
          $models = factory(Model::class, 5)->create();

          $response = $this->get('models');

          $response->assertSuccessful();

          $models->each(function(Model $model) use ($response){
              $response->assertSee($model->name);
          });

    }

If a model has been recently added using php artisan make:model -m -f and these have not been altered and the route 'models' exists. So that $response->assertSuccessful(); passes.
As in this example $model->name does not exist on the model (not defined yet in migration or factory) this returns a null value.
When checked using assertSee or assertSeeText on the response this passes.
This occurs because the underlying check casts the null value to a string.
PHPUnit::assertStringContainsString((string) $value, strip_tags($this->getContent()));

This results in seeing "" which assertStringContainsString passes. Which is why I'm submitting this pull request as otherwise any tests which are checking a null value are erroneous (in my opinion) and not adding any meaningful to the test results.

Requested changes have been made 👍

This is actually a breaking change. If people are using null conditionally to skip a test.

If people are wanting to conditionally skip tests wouldn't they be written as:
if ( $condition ) {
    $response->assertSee($condition)
}

Regarding the concerned for breaking changes, I could do a PR to add an optional parameter to complete strict, wich is defaulted to the current behaviour i.e.
$response->assertSee($condition, $strict = false)


Revise anything with a file interaction to accept an encoding, with default to locale-default

Otherwise there could be users who have to jump through hoops to make things work.
Ideally, the default would be UTF-8; but, in order to retain backward compatibility, the default for a v2 will need to match the encoding=None, which is locale.getpreferredencoding().
A switch to UTF-8 as default, while likely breaking very little code, would be a breaking change and need a major version bump.

Per comment(s) #103, this may only actually be needed for interactions with decompressed inventories, and with JSON-formatted content, as compressed inventories always use the Python UTF-8 default encoding.


Script/ruby nanderson83

Added basic script for provisioning ruby 2.3. There are other ruby versions that can be added from the same ppa, but for now I wanted to get the ball rolling with this.

Hey! It looks good, but do you think you can change the target branch for this merge to script/ruby?

Closing this request after pulling in the correct request to the correct branch.


Extension that will pre-Gzip JS and CSS files

Gzipped assets can be served directly by Apache or Nginx with the proper configuration, and pre-zipping means that we can use a more aggressive compression level at no CPU cost per request.
See section 4.1.1 of the Rails Asset Pipeline guide for more info: http://guides.rubyonrails.org/asset_pipeline.html#in-production

One thing to consider is that, since this is a static website, HTML files could also be pre-gzipped. I'd probably just make that an option for this extension, though. Thoughts?

Killer, 3 things though.

Usually, it's traditional to include both gzipped and regular files along-side each other. So this should supplement the existing output.

I'd love to see the build actually output a message, something like:
[gzip] javascripts/site.js.gz (12kb)

Some versions of Safari hate the .gz extension and require hacks like .jsz or .cssz. So the output extension should be either an option or a callback.

Whoops... maybe just make the list of extensions we gzip a config array so people could add .html?

 My intention is not to serve ".gz" files to clients though. Instead, I use something like this in my .htaccess:
AddEncoding gzip .gz

RewriteEngine on
RewriteCond %{HTTP:Accept-encoding} gzip
RewriteCond %{HTTP_USER_AGENT} !Konqueror
RewriteCond %{REQUEST_FILENAME}.gz -f
RewriteRule ^(.*)\.css$ $1.css.gz [QSA,L]
RewriteRule ^(.*)\.js$ $1.js.gz [QSA,L]

So clients still request "foo.css" but Apache serves the Gzip directly.
I think suggestion #2 would be pretty cool, but I'm not sure how to do it - I originally tried to do this as an after_build hook, but couldn't figure out how to get ahold of the Thor actions and ended up feeling that the reroute method was cleaner anyway.
#4 is totally something I should just throw in there... I just read the new option support in activate... give me a minute.

Oh, and I had an idea to add a CLI command that'd create a .htacess file or insert this stuff into it...

There's module mod_gzip_static for nginx which will handle *.gz etc, but it require timestamps of original file and gzipped version to match (for caching)
And yep, actually all text files are to be comressed, including feeds

Okay, so can we build both css and css.gz and have a :gzip_only option on activate for disable plain css?
Then we'll merge, and I'll open a new ticket for seeing if we can include the space savings in the build messages. And you can investigate CLI stuff.

OK, I'll probably have to rewrite the extension to do it that way though - instead of being a reroute it'll have to be a proxy or after_build thing.

Can you rebase this?

Would you just like it rebased into one commit?

OK, I've rewritten this extension to go with your suggestions. It ended up being a lot simpler in the end.

.gz versions are now produced side-by-side with uncompressed versions
.html is included by default
The builder output now says "gzip" and includes the number of bytes saved. I couldn't use number_to_human_size to format that better because of another bug which I'll send a pull request about in a bit.

An example output (the example files are so small that gzip actually makes them bigger...):
      create  build/javascripts/test.js
      create  build/stylesheets/test.css
      create  build/index.html
        gzip  build/index.html.gz (-20 bytes smaller)
        gzip  build/javascripts/test.js.gz (-14 bytes smaller)
        gzip  build/stylesheets/test.css.gz (-20 bytes smaller)

If you'd rather pull just one commit, I've squashed it all here:
https://github.com/bhollis/middleman/tree/gzip_squashed


WIP: GitLab

Mentally preparing myself for danger/danger-js#396
For now I've been mostly browsing through https://github.com/danger/danger-js/pull/516 and annotating the source code with TODOs. I'll have to come up with a clear plan to follow, but this looks doable!

Forked the repo to GitLab.com (for reasons): https://gitlab.com/stigi/danger-js


DM-30997: Pin galsim minor version.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Why is this needed? Version 2.3 has the .so files for linking.

Because binaries have been built against 2.2, and we would like them to continue to function.

I suspect the two versions are ABI compatible. Did you find they are not?

The library version is baked into libmeas_extensions_shapeHSM.  ldd gives:
	libgalsim.so.2.3 => not found

when using a version built against the new galsim with the old rubin-env build.

ouch. thanks for for answering my questions!


Existing Rich Text corrupts .xlsx on write

My current program reads in an existing .xlsx that contains a few cells with values that look like this (this was made in excel and I haven't created the structure with JavaScript in any way):
{ richText:
   [ { font:
        { bold: true,
          size: 10,
          color: { theme: 1 },
          name: 'Arial',
          family: 2 },
       text: '(j) ' },
     { font: { size: 10, color: { theme: 1 }, name: 'Arial', family: 2 },
       text: 'blah blah blah ' },
     { font:
        { bold: true,
          underline: true,
          size: 10,
          color: { theme: 1 },
          name: 'Arial',
          family: 2 },
       text: 'blah blah' },
     { font: { size: 10, color: { theme: 1 }, name: 'Arial', family: 2 },
       text: ' more blah blah blah \r\n' },
     { font:
        { bold: true,
          size: 10,
          color: { theme: 4 },
          name: 'Arial',
          family: 2 },
       text: '\r\nReference: numbers, blah blah blah' } ] }

The problem is when I write the .xlsx back into a file using workbook.xlsx.writeFile and open in Excel the file is prompted to be repaired, clearing only the cells with rich text, and I get an error (in Excel) of:
Repaired Records: String properties from /xl/sharedStrings.xml part (Strings)
Removed Records: Named range from /xl/workbook.xml part (Workbook)
A temporary solution I found was to just take the cell.value and set it equal to the cell.text which nukes the formatting while keeping the text, and everything works fine, but I was wondering if there was something wrong with the way rich text is being written back into a new file?
Thanks for any help or insight.

I am running into a similar issue. I am not seeing a corrupted file, but Rich Text values are lost on write. I have { useSharedStrings: true }, but any cell that had existing Rich Text comes out with no value.

Before writing a file, you need to go through the existing cells with rich text and pass cell.model.value to cell.value:
worksheet.getRow(3).eachCell(cell => {
  if (cell.model.value!.hasOwnProperty("richText")) {
    cell.value = cell.model.value as CellRichTextValue;
  }
});


Add external notification - containrrr/shoutrrr

Add containrrr/shoutrrr for sending notification to external apps such as slack, teams, etc.
This will be useful for backup completion, failure and storage warning.

shoutrrr can be easily added to the image by copying the shoutrrr binaries from its docker image (shoutrrr is written in golang which is self-contained).


Can't do anything after now logout

After logged out from cli, both login and logout don't work (now v17.0.3)
$ now logout
Now CLI 17.0.3
Error! The content of "~/.now/auth.json" is invalid. No `token` property found inside. Run `now login` to authorize.
$ now login
Now CLI 17.0.3
Error! An unexpected error occurred!
  Error: The specified token is not valid

I even can't see the help message
$ now --help
Now CLI 17.0.3
Error! An unexpected error occurred!
  Error: The specified token is not valid

I downgraded now to v16.x and I was able to login. After that I upgraded to v17 again and now I can use the cli v17 with logged-in state. Maybe this is a workaround, but it seems very inconvenient.

Same issue here. I roll back to 16.7.3 and it's work.

Thanks for reporting this issue! It will be fixed in PR #3907.

You can try this out on the canary channel npm i -g now@canary.


Privacy component update to read and delete cookies

Closed by https://github.com/ethyca/fides/pull/3569

moving to done


Update Pages “home”

Automatically generated by Netlify CMS

👷 Deploy Preview for shimmering-marigold-4f5b4a processing.

Name
Link

🔨 Latest commit
fe01c7facbc3eb64a79af0feaf44d35197a10a94

🔍 Latest deploy log
https://app.netlify.com/sites/shimmering-marigold-4f5b4a/deploys/6500e45499d6ab000827339a


fixes npm run build

Typescript needs this file in order to recognize modules in ".vue" files.
Without this, I was not able to run "npm run build".
More on this here: https://stackoverflow.com/questions/54622621/what-does-the-shims-tsx-d-ts-file-do-in-a-vue-typescript-project/59788563#59788563

@ocarneiro i am running on Mac OS and with node version v18.17.1 and i do not need it so can you tell me which OS and which Node version you are working with.

I'm using Windows 11 and node 18.17.1 as well.

@ocarneiro ok i will check on Windows


demonstrate programmatically cache KJAR into KieRepository

...given anyway is a single KJAR
without kjar-inheritance

superseeded by
https://github.com/tarilabs/demo20230606-orchestrator/blob/aca6c845ab97e82a819f122b8ab095f91e814867/demo20230606-kiecontainerorchestrator/src/main/java/org/drools/demo/demo20230606_kiecontainerorchestrator/AppPreloadThenMultiJar.java#L31-L35


Remove successful event deliveries from db

I want to merge this change because we want successful event deliveries to be automatically removed from db. Additionally this pr fixes minor bug with wrong attempt status set.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-5078 Remove deliveries after successful logging to external apps


[FEATURE] : Dark mode functionality

Description
want to work on the functionality of dark mode and light mode  under Gssoc'24 . Please assign it to me
Use Case
Will improve the user interface
Proposed Solution
No response
Additional Information
No response
Attachments
No response

i would like to fix this issue

I also want to work on this issue under gssoc24

Hey @Sooraj002 I am  a GSSOC contributor can you please label this issue as GSSOC  and assign this issue to me I would love to work on it!

Hey @Sooraj002 I am a GSSOC contributor can you please label this issue as GSSOC and assign this issue to me I would love to work on it!

Well, I am Also a Contributor . I think you should ask the admin @krishnaacharyaa

@Sooraj002 It is already there dear, the functionality :)

@Sooraj002 @KavyaBS123 @mohit-bhandari45 @tusharyadav11  Kindly find the code-of-conduct of the project Code-of-conduct.
And if you feel this issue is not following the code-of-conduct. Kindly close the issue.
Looking forward to have you as a contributor in the project :) We have a long way to go
p.s: Feel free to join our discord server: https://discord.gg/FEKasAdCrG and assign roles for yourself in the group, The likely-hood of contributing in the project will be really high :)

Closing as it already exists


Enable JWT playback on studio dashboard

Currently, when a user enables access control on a stream, the stream will not load on the studio dashboard. This is not expected behavior for users.

Duplicate of #1356


In nextjs 13, While pulling existing amplify backend, graphql folder is not added in src folder.

Amplify CLI Version
12.6.0
Question
In nextjs 13, While pulling existing amplify backend, graphql folder is not added in src folder. How to resolve this.

Hey @RZ-Jyothsna, thank you for reaching out. We can generate the graphql folder by running amplify configure codegen and run the through the flow. If the project already has the .graphqlconfig.yml present, we can run amplify codegen to generate the folder.

closing the issue due to inactivity. please feel free in reaching out to us, we would be happy in diving deeper.


Fixed deprecation warnings and index increment

The if inside the generate methods would test index and then increment it, allowing it to go out of bounds.

Hey @vfn thank you for the PR
Oh, I see, the index thing was definitely wrong, wonder why it didn't pop out before.
I'll check why Travis is complaining before merging.

@andreacremaschi I forgot to update the travis file to use xcode7.3. The PR has been updated, build and tests are fine, but Travis is now crashing https://travis-ci.org/andreacremaschi/GEOSwift/builds/120500155
It looks like a xctool issue https://github.com/facebook/xctool/issues/666

https://github.com/facebook/xctool/issues/684

thanks! :beers:

👍


GEOWAVE-667: added visibility stats and duplicate stats and used as q…

…uery hints
It is used on query now.  TBD is how we may want to use it for GeoWaveInputFormat (it'd probably be beneficial).  The stats would just need to be pulled into InputFormatAccumuloRangeQuery and passed along to AccumuloConstraintsQuery.  Also, the implementation just continued to primarily use patterns that had been established by IndexMetaDataSet, but it may be considered technical debt to try to clean up a little now that there's many stats being passed to AccumuloConstraintsQuery and now that there;s an ongoing set of stats that continue to be added to DataStoreStatisticsProvider (and ignored by GeoWaveBasicIT).  In general we probably need better hooks for users/developers to provide there own stats, and to subset or include more default stats.
...So I think that this likely should become a new issue and I just (mostly) followed the pattern and added the appropriate stats given #667.

actually, I'm going to run benchmarks on this v. master so don't quite merge this in...yet.


npm ERR! Code EINTEGRITY

I was trying to install the npm after the creation of the angular application by using the command
npm install -g @angular/cli
then I was getting the following error:
** PS D:\Project\rr> npm install -g @angular/cli@latest
npm ERR! code EINTEGRITY
npm ERR! sha512-z8H8/diyk76B7q5wg+Ud0+CqzcAF3mBBI/bA5ne5zrRUUIvNkJY//D3BqyH571KuAC4Nr7Rw7CjWX4r0y9DvNg== integrity checksum failed
when using sha512: wanted sha512-z8H8/diyk76B7q5wg+Ud0+CqzcAF3mBBI/bA5ne5zrRUUIvNkJY//D3BqyH571KuAC4Nr7Rw7CjWX4r0y9DvNg== but got
sha512-SniK8bztT8Gdnh4naDvDF80ePEd5am8p6Gr0jxDjAQbrt0CDXrGE9QcUYWsSTIlKlbsplwFeunOq1gd5QRdrVQ==. (1597 bytes) **
And I need to know the PATH to be added in the Variables section.

Please open issue for angular-cli.

I got the solution, by giving proper proxy settings


Executing playbook from cwd results in: Error: duplicate mount destination

Summary
Using 1.0.0b1, executing ansible-navigator run <playbook.yml> from cwd results in cwd being passed as a volume mount 2x to the podman command.
Eg:
% cd /home/user/ansible-project
% ansible-navigator run playbook.yml
Error: /home/user/ansible-project/: duplicate mount destination
Whereas this works:
% cd /home/user/ansible-project
% ansible-navigator run playbooks/playbook.yml
Issue Type
Bug Report
Ansible-navigator Version
$ ansible-navigator --version
ansible-navigator 1.0.0b1

Ansible-runner Version
$ ansible-runner --version
<IP_ADDRESS>a5

Settings
$ cat ansible-navigator.yaml
---
ansible-navigator:
  execution-environment:
    pull-policy: missing
    environment-variables:
      pass:
        - VMWARE_HOST
        - VMWARE_USERNAME
        - VMWARE_PASSWORD
        - TOWER_HOST
        - TOWER_OAUTH_TOKEN
        - TOWER_USERNAME

  logging:
    append: false
    level: debug
    file: /tmp/ansible-navigator.log
  playbook-artifact:
    enable: False
  mode: stdout

Command
$ ansible-navigator run site.yaml
Error: <project_dir>: duplicate mount destination

Ansible Version
$ ansible --version

Ansible navigator logs
$ cat ./ansible-navigator.log
210613225030.346 INFO 'ansible_navigator.setup_logger' New ansible-navigator instance, logging initialized
210613225030.346 INFO 'ansible_navigator.setup_logger' New ansible-runner instance, logging initialized
210613225030.346 DEBUG 'ansible_navigator.main' Share directory '/home/user/.virtualenvs/ansible-2.9-py39/lib/python3.9/site-packages/share/ansible_navigator' not found (development path)
210613225030.346 DEBUG 'ansible_navigator.main' Share directory '/home/user/.local/share/ansible_navigator' not found (userbase)
210613225030.346 DEBUG 'ansible_navigator.main' Share directory '/home/user/.virtualenvs/ansible-2.9-py39/share/ansible_navigator' found (sys.prefix)
210613225030.346 DEBUG 'ansible_navigator.main' Default collection_doc_cache_path set to: /home/user/.cache/ansible-navigator/collection_doc_cache.db
210613225030.346 DEBUG 'ansible_navigator.main' EDITOR environment variable set as '{editor}'
210613225030.346 DEBUG 'ansible_navigator.main' Default editor_command set to: /usr/bin/nano {filename}
210613225030.346 DEBUG 'ansible_navigator.main' No config file set by ANSIBLE_NAVIGATOR_CONFIG
210613225030.346 DEBUG 'ansible_navigator.main' Looking in /home/user
210613225030.346 DEBUG 'ansible_navigator.main' Looking for '/home/user/.ansible-navigator.yml', '/home/user/.ansible-navigator.yaml' and '/home/user/.ansible-navigator.json'
210613225030.346 DEBUG 'ansible_navigator.main' Found 1: '/home/user/.ansible-navigator.yaml'
210613225030.346 DEBUG 'ansible_navigator.main' Looking in /home/user/project/playbooks
210613225030.346 DEBUG 'ansible_navigator.main' Looking for '/home/user/project/playbooks/ansible-navigator.yml', '/home/user/project/playbooks/ansible-navigator.yaml' and '/home/user/project/playbooks/ansible-navigator.json'
210613225030.346 DEBUG 'ansible_navigator.main' Found 0:
210613225030.346 DEBUG 'ansible_navigator.main' All found 1: '/home/user/.ansible-navigator.yaml'
210613225030.346 DEBUG 'ansible_navigator.main' Using: /home/user/.ansible-navigator.yaml
210613225030.347 DEBUG 'ansible_navigator.main' Using settings file at /home/user/.ansible-navigator.yaml in search path
210613225030.347 DEBUG 'ansible_navigator.main' Command provided: '--eei vmware_ee run deploy_esxi.yml'
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.app not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.ansible.cmdline not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.collection-doc-cache-path not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.ansible.config not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.execution-environment.container-engine not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.color.enable not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.editor.command not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.editor.console not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.execution-environment.enabled not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.execution-environment.image not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.execution-environment.volume-mounts not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.help-config not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.help-doc not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.help-inventory not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.help-playbook not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.ansible.inventories not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.inventory-columns not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.color.osc4 not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.ansible.playbook not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.playbook-artifact.replay not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.playbook-artifact.save-as not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.documentation.plugin.name not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.documentation.plugin.type not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' ansible-navigator.execution-environment.environment-variables.set not found in settings file
210613225030.347 DEBUG 'ansible_navigator.main' Completed post processing for cmdline. (changed=False)
210613225030.347 DEBUG 'ansible_navigator.main' Completed post processing for collection_doc_cache_path. (changed=False)
210613225030.347 DEBUG 'ansible_navigator.main' Completed post processing for container_engine. (changed=True)
210613225030.347 DEBUG 'ansible_navigator.main'  before: 'auto'
210613225030.347 DEBUG 'ansible_navigator.main'  after: 'podman'
210613225030.347 DEBUG 'ansible_navigator.main' Completed post processing for display_color. (changed=False)
210613225030.347 DEBUG 'ansible_navigator.main' Completed post processing for editor_console. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for execution_environment. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for execution_environment_image. (changed=True)
210613225030.348 DEBUG 'ansible_navigator.main'  before: 'vmware_ee'
210613225030.348 DEBUG 'ansible_navigator.main'  after: 'vmware_ee:latest'
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for execution_environment_volume_mounts. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for help_config. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for help_doc. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for help_inventory. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for help_playbook. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for inventory. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for inventory_column. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for log_append. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for log_file. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for mode. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for osc4. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for pass_environment_variable. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for playbook. (changed=True)
210613225030.348 DEBUG 'ansible_navigator.main'  before: 'deploy_esxi.yml'
210613225030.348 DEBUG 'ansible_navigator.main'  after: '/home/user/project/playbooks/deploy_esxi.yml'
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for playbook_artifact_enable. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for playbook_artifact_replay. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for plugin_name. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Completed post processing for set_environment_variable. (changed=False)
210613225030.348 DEBUG 'ansible_navigator.main' Collection doc cache not mounted
210613225030.348 DEBUG 'ansible_navigator.main' Collection doc cache: 'path' is '/home/user/.cache/ansible-navigator/collection_doc_cache.db'
210613225030.348 DEBUG 'ansible_navigator.main' Collection doc cache: 'current version' is '1.0'
210613225030.348 DEBUG 'ansible_navigator.main' Collection doc cache not attached to args.internals
210613225030.348 DEBUG 'ansible_navigator.main' Running with app as 'run' (str/cli parameters)
210613225030.348 DEBUG 'ansible_navigator.main' Running with cmdline as 'Constants.NOT_SET' (Constants/value has not been set)
210613225030.348 DEBUG 'ansible_navigator.main' Running with collection_doc_cache_path as '/home/user/.cache/ansible-navigator/collection_doc_cache.db' (str/default configuration value)
210613225030.348 DEBUG 'ansible_navigator.main' Running with config as 'Constants.NOT_SET' (Constants/value has not been set)
210613225030.348 DEBUG 'ansible_navigator.main' Running with container_engine as 'podman' (str/default configuration value)
210613225030.348 DEBUG 'ansible_navigator.main' Running with display_color as 'True' (bool/default configuration value)
210613225030.348 DEBUG 'ansible_navigator.main' Running with editor_command as '/usr/bin/nano {filename}' (str/default configuration value)
210613225030.349 DEBUG 'ansible_navigator.main' Running with editor_console as 'True' (bool/default configuration value)
210613225030.349 DEBUG 'ansible_navigator.main' Running with execution_environment as 'True' (bool/default configuration value)
210613225030.349 DEBUG 'ansible_navigator.main' Running with execution_environment_image as 'vmware_ee:latest' (str/cli parameters)
210613225030.349 DEBUG 'ansible_navigator.main' Running with execution_environment_volume_mounts as 'Constants.NOT_SET' (Constants/value has not been set)
210613225030.349 DEBUG 'ansible_navigator.main' Running with help_config as 'False' (bool/default configuration value)
210613225030.349 DEBUG 'ansible_navigator.main' Running with help_doc as 'False' (bool/default configuration value)
210613225030.349 DEBUG 'ansible_navigator.main' Running with help_inventory as 'False' (bool/default configuration value)
210613225030.349 DEBUG 'ansible_navigator.main' Running with help_playbook as 'False' (bool/default configuration value)
210613225030.349 DEBUG 'ansible_navigator.main' Running with inventory as 'Constants.NOT_SET' (Constants/value has not been set)
210613225030.349 DEBUG 'ansible_navigator.main' Running with inventory_column as 'Constants.NOT_SET' (Constants/value has not been set)
210613225030.349 DEBUG 'ansible_navigator.main' Running with log_append as 'False' (bool/user provided configuration file)
210613225030.349 DEBUG 'ansible_navigator.main' Running with log_file as '/tmp/ansible-navigator.log' (str/user provided configuration file)
210613225030.349 DEBUG 'ansible_navigator.main' Running with log_level as 'debug' (str/user provided configuration file)
210613225030.349 DEBUG 'ansible_navigator.main' Running with mode as 'stdout' (str/user provided configuration file)
210613225030.349 DEBUG 'ansible_navigator.main' Running with osc4 as 'True' (bool/default configuration value)
210613225030.349 DEBUG 'ansible_navigator.main' Running with playbook as '/home/user/project/playbooks/deploy_esxi.yml' (str/cli parameters)
210613225030.349 DEBUG 'ansible_navigator.main' Running with playbook_artifact_enable as 'False' (bool/user provided configuration file)
210613225030.349 DEBUG 'ansible_navigator.main' Running with playbook_artifact_replay as 'Constants.NOT_SET' (Constants/value has not been set)
210613225030.349 DEBUG 'ansible_navigator.main' Running with playbook_artifact_save_as as '{playbook_dir}/{playbook_name}-artifact-{ts_utc}.json' (str/default configuration value)
210613225030.349 DEBUG 'ansible_navigator.main' Running with plugin_name as 'Constants.NOT_SET' (Constants/value has not been set)
210613225030.349 DEBUG 'ansible_navigator.main' Running with plugin_type as 'module' (str/default configuration value)
210613225030.349 DEBUG 'ansible_navigator.main' Running with pull_policy as 'missing' (str/user provided configuration file)
210613225030.349 DEBUG 'ansible_navigator.main' Running with set_environment_variable as 'Constants.NOT_SET' (Constants/value has not been set)
210613225030.349 INFO 'ansible_navigator.image_manager.puller._log_message' Image tag is: latest
210613225030.483 DEBUG 'ansible_navigator.actions.run.run_stdout' playbook requested in interactive mode
210613225030.483 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: container_image:vmware_ee:latest
210613225030.483 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: process_isolation_executable:podman
210613225030.483 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: process_isolation:True
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: container_volume_mounts:None
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: container_options:None
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: container_workdir:None
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: private_data_dir:/tmp/ansible-navigator
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: json_mode:True
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: quiet:True
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: cancel_callback:<bound method BaseRunner.runner_cancelled_callback of <ansible_navigator.runner.api.CommandRunnerAsync object at 0x7fb239451310>>
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: finished_callback:<bound method BaseRunner.runner_finished_callback of <ansible_navigator.runner.api.CommandRunnerAsync object at 0x7fb239451310>>
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: artifacts_handler:<bound method BaseRunner.runner_artifacts_handler of <ansible_navigator.runner.api.CommandRunnerAsync object at 0x7fb239451310>>
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: host_cwd:/home/user/project/playbooks
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: input_fd:<_io.TextIOWrapper name='<stdin>' mode='r' encoding='utf-8'>
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: output_fd:<_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: error_fd:<_io.TextIOWrapper name='<stderr>' mode='w' encoding='utf-8'>
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: executable_cmd:ansible-playbook
210613225030.484 DEBUG 'ansible_navigator.runner.api.generate_run_command_args' Runner arg: cmdline_args:['/home/user/project/playbooks/deploy_esxi.yml']
210613225030.485 DEBUG 'ansible-runner._handle_command_wrap' containerization enabled
210613225030.485 DEBUG 'ansible-runner.wrap_args_for_containerization' container engine invocation: podman run --rm --tty --interactive -v /home/user/project/playbooks/:/home/user/project/playbooks --workdir /home/user/project/playbooks -v /home/user/project/playbooks:/home/user/project/playbooks -v /run/user/1000/keyring:/run/user/1000/keyring -e SSH_AUTH_SOCK=/run/user/1000/keyring/ssh -v /home/user/.ssh/:/home/runner/.ssh/ --group-add=root --userns=keep-id --ipc=host -v /tmp/ansible-navigator/artifacts/:/runner/artifacts:Z -v /tmp/ansible-navigator/:/runner:Z --env-file /tmp/ansible-navigator/artifacts/48da7350-0dc0-4624-abbb-8a4759b1653f/env.list --quiet --name ansible_runner_48da7350-0dc0-4624-abbb-8a4759b1653f vmware_ee:latest ansible-playbook /home/user/project/playbooks/deploy_esxi.yml
210613225030.485 DEBUG 'ansible-runner._handle_command_wrap' command: podman run --rm --tty --interactive -v /home/user/project/playbooks/:/home/user/project/playbooks --workdir /home/user/project/playbooks -v /home/user/project/playbooks:/home/user/project/playbooks -v /run/user/1000/keyring:/run/user/1000/keyring -e SSH_AUTH_SOCK=/run/user/1000/keyring/ssh -v /home/user/.ssh/:/home/runner/.ssh/ --group-add=root --userns=keep-id --ipc=host -v /tmp/ansible-navigator/artifacts/:/runner/artifacts:Z -v /tmp/ansible-navigator/:/runner:Z --env-file /tmp/ansible-navigator/artifacts/48da7350-0dc0-4624-abbb-8a4759b1653f/env.list --quiet --name ansible_runner_48da7350-0dc0-4624-abbb-8a4759b1653f vmware_ee:latest ansible-playbook /home/user/project/playbooks/deploy_esxi.yml
210613225030.485 DEBUG 'ansible_navigator.actions.run_playbook._run_runner' runner requested to start
210613225030.699 DEBUG 'ansible-runner.run' podman run --rm --tty --interactive -v /home/user/project/playbooks/:/home/user/project/playbooks --workdir /home/user/project/playbooks -v /home/user/project/playbooks:/home/user/project/playbooks -v /run/user/1000/keyring:/run/user/1000/keyring -e SSH_AUTH_SOCK=/run/user/1000/keyring/ssh -v /home/user/.ssh/:/home/runner/.ssh/ --group-add=root --userns=keep-id --ipc=host -v /tmp/ansible-navigator/artifacts/:/runner/artifacts:Z -v /tmp/ansible-navigator/:/runner:Z --env-file /tmp/ansible-navigator/artifacts/48da7350-0dc0-4624-abbb-8a4759b1653f/env.list --quiet --name ansible_runner_48da7350-0dc0-4624-abbb-8a4759b1653f vmware_ee:latest ansible-playbook /home/user/project/playbooks/deploy_esxi.yml execution failed, returncode: 125, output: None, stdout: None, stderr: None
210613225030.834 INFO 'ansible-runner.kill_container' Error from podman kill ansible_runner_48da7350-0dc0-4624-abbb-8a4759b1653f command:
b'Error: no container with name or ID "ansible_runner_48da7350-0dc0-4624-abbb-8a4759b1653f" found: no such container\n'
210613225030.891 DEBUG 'ansible_navigator.runner.api.runner_artifacts_handler' ansible-runner artifact_dir set to: '/tmp/ansible-navigator/artifacts/48da7350-0dc0-4624-abbb-8a4759b1653f'
210613225030.896 DEBUG 'ansible_navigator.actions.run_playbook.run_stdout' runner finished
210613225030.903 DEBUG 'ansible_navigator.runner.api.__del__' delete ansible-runner artifact directory at path /tmp/ansible-navigator/artifacts/48da7350-0dc0-4624-abbb-8a4759b1653f

Execution environment details
$ ansible-navigator images quay.io/ansible/ansible-runner:devel

Container enginer details
$ podman info

Ansible Configuration
$ ansible-navigator config dump --only-changed -m stdout
CACHE_PLUGIN(env: ANSIBLE_CACHE_PLUGIN) = jsonfile
CACHE_PLUGIN_CONNECTION(env: ANSIBLE_CACHE_PLUGIN_CONNECTION) = /runner/artifacts/d344f034-927a-4cc1-9e4a-938d92254414/fact_cache
DEFAULT_CALLBACK_PLUGIN_PATH(env: ANSIBLE_CALLBACK_PLUGINS) = ['/usr/local/lib/python3.8/site-packages/ansible_runner/callbacks']
DEFAULT_STDOUT_CALLBACK(env: ANSIBLE_STDOUT_CALLBACK) = awx_display
HOST_KEY_CHECKING(env: ANSIBLE_HOST_KEY_CHECKING) = False
RETRY_FILES_ENABLED(env: ANSIBLE_RETRY_FILES_ENABLED) = Fals

OS / Environment
Fedora 33
Steps to Reproduce
Run a playbook from cwd, eg:
% cd /home/user/ansible-project
% ansible-navigator run playbook.yml

Expected Results
Playbook should execute properly.
Actual Results
Error: /home/user/ansible-project: duplicate mount destination

Code of Conduct

[X] I agree to follow the Ansible Code of Conduct

https://github.com/ansible/ansible-runner/issues/727


Globally change defaults

Is there a way to change defaults for all servers in one place? For example, to get this working with ncm2 you need to add on_init = ncm2.register_lsp_source;. Given that I'll want this option added every time, is there a place to override the global defaults and include it? It should still be possible to override it again later for one particular server if a need arises, it would just be nice to reduce duplicate code.

Would do you try this PR?
lua << EOF
	local nvim_lsp = require"nvim_lsp"
	nvim_lsp.util.default_config = vim.tbl_extend(
		"force",
		nvim_lsp.util.default_config,
		{on_init = ncm2.register_lsp_source})
	nvim_lsp.some_ls.setup{}
<< EOF

resolved #149


Enhancements to PerfViewJS

I'm using OSX for daily .net core development and i don't have access to a windows terminal @ work.
Added in startup.cs to support .nettrace files
private readonly HashSet<string> perfviewJSSupportedFileExtensions = new HashSet<string> { "*.etl", "*.btl", "*.netperf", "*.nettrace" };
More or less refreshed spa, but i'm midway, but it's going to take quite a bit of effort, want to know if this PR will ever be accepted before i commit more of my time. Here's where i'm at

Thanks @murugaratham for submitting this!  The screenshots look great.  The original maintainer of PerfViewJS has left the company, but I am working to get eyes on this.

Thanks @murugaratham for submitting this! The screenshots look great. The original maintainer of PerfViewJS has left the company, but I am working to get eyes on this.

Ah, I see, I’ll work at a comfortable pace, it’s still not quite ready, but hearing from maintainers gives me some motivation.

Adding in Azure themes

AzureThemeDark
AzureThemeLight
AzureThemeHighContrastDark
AzureThemeHighContrastLight

Revamp'ed Trace Info page (Responsive)
Large screen

Medium screen

Small screen

Loading indicator

@murugaratham I agree with @brianrob the UI looks great. I won't promise that I'll be able to give timely PR comments, but I will say that your changes for correctness overall look good and the direction of electron.js also looks good.
Here is what was on my TODO list for PerfViewJS
(1) Add an electron shell -- which you're doing here, but I would recommend you don't break PerfViewJS rendering outside of Electron (for example, Home.tsx seems quite coupled with Electron now, but may be that is fine for that one view)
(2) Fix annoying user experiences issues like the loading screen, and reporting errors when loading fails. For example, if loading times out or an exception is thrown the user is not notified of any error. It'll be good to catch exceptions and report them if possible.
(3) Symbol resolution is clunky. To resolve symbols, you must go to the Modules View, click on the module which causes the symbols to be cached. This is the only way I was able to present symbol downloading, but really we should allow users to load symbols much like traditional PerfView in which you can right click and say resolve symbols.
(4) The event viewer doesn't fetch data in chunks, it buffers all the data and then displays it. This is probably not a huge deal for medium to small files, but if you have a big file and want to show all the events, the server buffers it and then converts to json, and the viewer renders it all in one go. It would be better to do it like traditional PerfView does, 1000 or so events at a time.
After these 4 features, PerfViewJS is more or less functionally equivalent to the traditional PerfView.
Enjoy and thanks for doing this!

@murugaratham I agree with @brianrob the UI looks great. I won't promise that I'll be able to give timely PR comments, but I will say that your changes for correctness overall look good and the direction of electron.js also looks good.
Here is what was on my TODO list for PerfViewJS
(1) Add an electron shell -- which you're doing here, but I would recommend you don't break PerfViewJS rendering outside of Electron (for example, Home.tsx seems quite coupled with Electron now, but may be that is fine for that one view)
(2) Fix annoying user experiences issues like the loading screen, and reporting errors when loading fails. For example, if loading times out or an exception is thrown the user is not notified of any error. It'll be good to catch exceptions and report them if possible.
(3) Symbol resolution is clunky. To resolve symbols, you must go to the Modules View, click on the module which causes the symbols to be cached. This is the only way I was able to present symbol downloading, but really we should allow users to load symbols much like traditional PerfView in which you can right click and say resolve symbols.
(4) The event viewer doesn't fetch data in chunks, it buffers all the data and then displays it. This is probably not a huge deal for medium to small files, but if you have a big file and want to show all the events, the server buffers it and then converts to json, and the viewer renders it all in one go. It would be better to do it like traditional PerfView does, 1000 or so events at a time.
After these 4 features, PerfViewJS is more or less functionally equivalent to the traditional PerfView.
Enjoy and thanks for doing this!

First of all, thanks @mjsabby for spending time here, and I do understand that you are likely busy with other high priority work.
I do foresee there’s quite a lot of changes along the way to my own satisfaction. As Microsoft is embracing OSS and pushing for xplat dev capabilities, this was one of my main pain point of not being able to view traces on non windows environment. PerfView itself is advanced tool that I believe typical non expert level developers had hardly come across it, but the UI is very dated and I get overwhelmed when I first came across it.
Since perfviewjs itself is marked as experimental and I’ve had trouble using it. The thought of wrapping it with electron would truly gives non windows developers a good dev experience to troubleshoot. (I’m doing this whole thing on an m1 mac) dotnet core had enabled this although there are some .net framework proj that I can’t build. I don’t intend to touch the “backend” much until the client app is more feature complete.
On top of the points you’ve mentioned, I’ve also intend to do the following:

update all raw HTML to fluent ui components
.net 5 upgrade for backend, and publish single file & publish trimmed (package is HUGE right now)
Notarization for mac app store or dmg for distribution (might need some help from any msft dev that have publishing profile)

im an ex-microsoftee and is itching to contribute back to OSS

(1) Add an electron shell -- which you're doing here, but I would recommend you don't break PerfViewJS rendering outside of Electron (for example, Home.tsx seems quite coupled with Electron now, but may be that is fine for that one view)
(2) Fix annoying user experiences issues like the loading screen, and reporting errors when loading fails. For example, if loading times out or an exception is thrown the user is not notified of any error. It'll be good to catch exceptions and report them if possible.

Decoupled Electron shell from PerfViewJS & also showing a "toast" notification of exception & allowing retry

(3) Symbol resolution is clunky. To resolve symbols, you must go to the Modules View, click on the module which causes the symbols to be cached. This is the only way I was able to present symbol downloading, but really we should allow users to load symbols much like traditional PerfView in which you can right click and say resolve symbols.

(4) The event viewer doesn't fetch data in chunks, it buffers all the data and then displays it. This is probably not a huge deal for medium to small files, but if you have a big file and want to show all the events, the server buffers it and then converts to json, and the viewer renders it all in one go. It would be better to do it like traditional PerfView does, 1000 or so events at a time.

Event "autocomplete" filter, with all the filters done..

Filtered events

Viewing Stack

Lookup number of symbols

Drill in/exclusive

Gonna continue to refresh the react ui stuff as time goes, but let's keep this PR open and i can leverage on the pipeline, although i don't yet understand why sometimes it fails, even though there was no commits on c# proj

@mjsabby or @brianrob I need some input on the following
https://github.com/microsoft/perfview/blob/7da0b1c7b6ffa64349121ca7f98708661cac6fc3/src/PerfViewJS/CallTreeData.cs#L219
Doesn't seem to work on Mac, not sure if it's supposed to work at all, the current main branch doesn't load source and only returns null
https://github.com/microsoft/perfview/blob/7da0b1c7b6ffa64349121ca7f98708661cac6fc3/src/PerfViewJS/CallTreeData.cs#L279
As well as the above method, which returns
Created SymbolReader with SymbolPath
Resolving all symbols for modules with inclusive times > 50
Got a total of 1 samples
Done Resolving all symbols for modules with inclusive times > 50

But the main branch's "Lookup # of Symbols (min samples)" doesn't seem to be passing the right parameters and it's reloading the page, for now i'm printing the output on to screen
Last thing would be "Process List" page, links of "Number of address occurrences in all stacks" <- when user clicks on the numbers, what's PerfViewJS supposed to do? Current one doesn't seem to work..
I've also added Todo to readme.md

[ ] Make source viewer work
[ ] Breadcrumbs on all pages
[ ] Loading indicator & error handlers
[ ] Understand what to do on "Lookup # of Symbols (min samples)"
[ ] Understand what to do on "Process List" page, links of "Number of address occurrences in all stacks"
[ ] Flame graph?
[ ] Electron MAS notarization
[ ] (is this still a todo?) Wrap PerfViewJS as a dotnet global tool
[x] Electron splash screen
[x] Refresh UI from HTML to Fluent-UI components
[x] Use Chromium Embedded Framework to make a client-side application
[x] Sortable Table (on tables which usually contains > 50 items)

@murugaratham, apologies for the delayed response, this slipped through my inbox.  I am not surprised that SymbolReader isn't working - it's mostly coupled to Windows, and is responsible for lookup and opening of Windows and Portable PDBs.  It definitely has dependencies on Windows-only DLLs.  If you're just trying to load nettrace files, then you should not need SymbolReader to resolve symbols, as symbols are present in the nettrace itself.  Do try setting minCount to 1 and see if that resolves everything, or if it doesn't work.
I'm not sure about the behavior of the proecesses view - @mjsabby do you know?

@murugaratham, apologies for the delayed response, this slipped through my inbox. I am not surprised that SymbolReader isn't working - it's mostly coupled to Windows, and is responsible for lookup and opening of Windows and Portable PDBs. It definitely has dependencies on Windows-only DLLs. If you're just trying to load nettrace files, then you should not need SymbolReader to resolve symbols, as symbols are present in the nettrace itself. Do try setting minCount to 1 and see if that resolves everything, or if it doesn't work.
I'm not sure about the behavior of the proecesses view - @mjsabby do you know?

No worries @brianrob, just not sure of what to do next, else I’ll leave the pr for coordinators to decide

@murugaratham Can you show a screenshot of what you mean? I'm not sure I understand.

What to do when user clicks on Lookup # of Symbols (min samples)

All i see from api was "Created SymbolReader with SymbolPath \nResolving all symbols for modules with inclusive times \u003E 50\nGot a total of 1 samples\nDone Resolving all symbols for modules with inclusive times \u003E 50\n"
Attempting to get source code viewer

Probably like what @brianrob mentioned, it's tied to Windows, i'm on mac and i think that's the point of this PerfViewJS..

@murugaratham Did some serious digging on Google for perfviewjs and found this issue come up. Wow - these are awesome changes!
PerfViewJS's been extracted out of this repo recently* and into https://github.com/microsoft/perfviewjs. I have a couple of PRs over there that you seem to have covered (nettrace fix, readme updates, vscode build tasks & gitignore). Could you look at porting your PR to that repo? TraceEvent reference is now done via nuget. Also having trouble running spa on Ubuntu 20.04 w/ issues in "chokidar" versioning so will need some package.json fix ups. Is there a way to run it without Electron?
cc @brianrob @mjsabby
*Is there anything that is lost by not being up-to-date with PerfView primary repo?

@murugaratham Did some serious digging on Google for perfviewjs and found this issue come up. Wow - these are awesome changes!
PerfViewJS's been extracted out of this repo recently* and into https://github.com/microsoft/perfviewjs. I have a couple of PRs over there that you seem to have covered (nettrace fix, readme updates, vscode build tasks & gitignore). Could you look at porting your PR to that repo? TraceEvent reference is now done via nuget. Also having trouble running spa on Ubuntu 20.04 w/ issues in "chokidar" versioning so will need some package.json fix ups. Is there a way to run it without Electron?
cc @brianrob @mjsabby
*Is there anything that is lost by not being up-to-date with PerfView primary repo?

Hi @colonelchlorine, the code changes were made to run the spa on its own, https://github.com/microsoft/perfview/pull/1440#issuecomment-856916266
I’m not sure if I can get time to move the pr over, would you mind to go ahead and fork https://github.com/murugaratham/perfview
but this pr seems to be in limbo state unless until @brianrob or @mjsabby can chip in on whether perfviewjs is gonna get more eyeballs

I can’t comment on if it’ll get more eyeballs, you could argue it’s easier to develop and faster to iterate.
I doubt much is lost in terms of features that can be accessed, we tried to keep things using public APIs.
One of things I’d like eventually is making it a native app on the platform using native technologies but that’s probably not a priority. For example, Windows 11 has WebView2 and you could imagine building an app on top of it to get even better experience.
I would imagine some symbol lookup stuff is funky and might break in Linux but nothing fundamentally is broken to make it feature full on all platforms and I don’t think we’re terribly far either.
That’s the best I can offer or comment, @brianrob probably knows more about the fate of this if any.


SatelliteML: Change x and y to x_geostationary and y_geostationary, and include x_osgb and y_osgb

At the moment, the SatelliteML class has x and y fields, which store the x_geostationary and y_geostationary coords, respectively.
As noted in #113, field names x and y are a bit ambiguous. Are they OSGB? Are they pixel indicies? Are they geostationary coords?! :slightly_smiling_face:
So I'd propose a simple PR that:

Adds the following fields to SatelliteML:

x_geostationary
y_geostationary
x_osgb
y_osgb

I assume that, if we remove x and y then a tonne of stuff will break. So, for now, I'd propose we keep x and y (but correct the docstrings), but state that x and y are deprecated and will be removed in a future version.

Does that sound OK, @peterdudfield?
Related issues:

#113
https://github.com/openclimatefix/nowcasting_dataset/pull/701
https://github.com/openclimatefix/nowcasting_dataset/issues/697

Cool, I'll work on this now


Fix ZFS templates

ZFS montoring template is fixed. This is tested and working.

added missing agent conf file with user parameters
fixed templates with inappropriate use of $1 and $2 variables for 5.4 and 6.0

Not Done:
updated 5.0 profile. I don't have the patience for this, and don't use 5.0. Someone else can contribute.

Your commit log said
"fixed templates with inappropriate use of $1 and $2 variables for 5.4 and 6.0"
When are $1 and $2 inappropriate for Zabbix 6 templates? I still see plenty of them in the current ZFS templates, such as:
UserParameter=zfs.zpool.health[*],/usr/bin/sudo /sbin/zpool list -H -o health $1
I read that after Zabbix 4 these vars are supposed to be replaced by Macro names?


Keyboard and mouse interaction freezes after program enters breakpoint

The specific performance is:
After hooking the keyboard event, if the program hits a breakpoint, the mouse and keyboard operations will suddenly become extremely stuck. According to the naked eye, each mouse position update will take up to several seconds.

Hi! Thanks for posting this issue! This is a known problem and unfortunately, this is just the way global hooks work on Windows.
I'm going to close this issue a duplicate of issue #37 - let's continue the discussion there.

Hi! Thanks for posting this issue! This is a known problem and unfortunately, this is just the way global hooks work on Windows.
I'm going to close this issue a duplicate of issue #37 - let's continue the discussion there.

Thank you very much for your answer.
I'm very sorry, I did a cursory check in the issues list and didn't find #37, which caused you trouble.

No problem, don't worry :)


update Readme.md example code

update Readme.md example code

@adavidoaiei prefix this PR with CODE RUB: ...

I updated PR prefix with CODE RUB: @hassanhabib


Implement new photo picker for uploading images

iOS has one built-in. We should just use that.
This would technically fix the issue where things are paging strangely, as in this thread.

I fixed the paging issue. Issue with the iOS picker is no multi select so this is a wontfix


PNG export / unwanted rotation of y label

I think there is a bug in the PNG export option of bokeh
While the inline plot is showing the name of the axis nicely:
import numpy as np
import holoviews as hv
hv.extension('bokeh')

test_array = np.random.rand(100,100)
hv.Image(test_array).redim.label(y='AXIS')

the png export of the plot does very weird things to the label:
%%output filename="view_plot.png" fig="png"
hv.Image(test_array).redim.label(y='AXIS')

So far I didnt find any plot option to solve this.

I suspect this is a bug in bokeh so would likely have to be raised there. Could you create a pure bokeh example and file an issue with bokeh? I'm also happy to do it but won't get to it immediately.

Personally, I would guess that's a problem in font support on your system, not bokeh itself, because it works fine on my Mac OS X system:

Given that the fonts are also poor quality even for the bits that are working, I'd suspect that the system is falling back to some less-capable font renderer that can't rotate letters.   I'll ask Bokeh devs if they know which libraries might be involved.  What kind of machine is this (OS and version)?

Okay thats interesting! Its Debian GNU/Linux 8 (jessie)

Best guess from Bokeh devs is that the underlying PhantomJS headless-browser library that Bokeh uses to render its PNGs is failing to find the right fonts on your system.  I'm not sure how to debug that on your system, though.  The fonts Bokeh is expecting to use are specified in this file, so maybe there is some font package on Debian that can be installed to make them available to PhantomJS.

There are known issues with fonts in phantomjs, and the behavior is platform dependent. I can't reproduce this locally, but I recall seeing this on travis ci. The short term solution is to do a google search for "phantomjs fonts linux" (or "debian" or something similar) and follow one of tutorials that are supposed to help with this (I don't know if they actually do; use at your own risk). Alternatively you can modify bokeh(.min).css to use a different font from the default Helvetica, and if this doesn't work, provide a font on your own (using CSS' @font-face syntax). In the long term we will switch from phantomjs to chrome headless to resolve this and many more issues with have with phantomjs.

And if you do figure out something that works on your system, please post it here for others to follow if they encounter the same problem!

Thank you for the quick answers! I'll report if I fix it!

Since this is an upstream issue and there is nothing we can do about it at the holoviews level I'm going to close.


add global prescribed atmos and radiation

Purpose
Add types for global atmos and radiation. Write new methods to initialize and update them.
I'll implement this for atmos first and then duplicate for radiation.
closes #442
To Do

[x] PrescribedAtmosphere becomes PrescribedAtmosSite, PrescribedRadiation becomes PrescribedRadSite
[ ] add new types PrescribedAtmosGlobal and PrescribedRadGlobal

these will be somewhat analogous to BulkAlbedoFunction and BulkAlbedoTemporal, where one stores FT-valued parameters, and the other stored Field-valued parameters over the entire globe

[ ] extend PrescribedDataTemporal/FileInfo/hdwrite_regridfile_rll_to_cgll to work for files with multiple varnames
[ ] implement methods of initialize_drivers to initialize global atmos and radiation types
[ ] implement methods of make_update_drivers to update global atmos and radiation types

analogous to next_albedo (maybe rename to update_albedo for consistency)

uses read_data_fields!(::PrescribedDataTemporal, date, space)

Notes

PrescribedAtmosGlobal is largely following BulkAlbedoTemporal, but needs an array of varnames since the input file contains many variables we want to read in

extend PrescribedDataTemporal constructor to dispatch on varname type?
varname goes into FileInfo --> loop over weights in hdwrite_regridfile_rll_to_cgll (avoids having to recreate regridding objects)
can we assume all variables in same file will be on same grid, or do we need to create new weight matrix for each? --> assume same grid since output from same simulation

should probably regrid only the dates we want to use in our simulation, rather than everything in file (as we've been doing)

[x] I have read and checked the items on the review checklist.

I think that there's some overlap with #451.
I've changed PrescribedAtmosphere and PrescribedRadiation to use the new Interpolators. My assumption was that they would be used for global run as well.

will not be implemented - doing #451 instead


[Microsoft.Plugin.WindowWalker] Enable analyzer and fix warnings

Summary of the Pull Request
What is this about:
What is included in the PR:
How does someone test / validate:
Quality Checklist

[x] Linked issue: #16511
[x] Communication: I've discussed this with core contributors in the issue.
[x] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[ ] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

Let's hold this one until my WindowWalker PR is merged.
cc: @jaimecbernardo , @crutkas

has someone validated that the changes in my pr not trigger warnings?


IE: Column hiding menu shadow/border is too light

See screenshot; Chrome on left, IE11 on right.

Change the box-shadow blur value from 5px to 6px in the last value here:
https://github.com/vaadin/components/blob/master/vaadin-components-gwt/src/main/webapp/vaadin-grid/vaadin-grid.html#L566