add info about verifying provenance attestations

Updates the documentation for provenance attestations to include information about verifying attestations. Includes a note about using the latest npm version to ensure that users have the latest verification logic.

Looks good. We probably either want to re-state this here or link to this page from there.


StackOverflowError on plots of large sequences

Hi,
I went a bit more in-depth with Koma and depart from the examples. Trying to import some of our sequences that we use on daily basis seems to cause errors in the plots on my system.
pulseq files were generated with pypulseq and the sequences are small scaled-down examples of what we use (2D Cartesian with 64 phase encode steps and 18 repetitions per step).
Sequence was read with
julia> using KomaMRI

julia> seq = read_seq("/path/to/seqfile")
Sequence[ τ = 39276.8 ms | blocks: 6912 | ADC: 1152 | GR: 5724 | RF: 1088 | DEF: 9 ]
julia> plot_seq(seq)
ERROR: StackOverflowError:

I used v0.7.5 with julia 1.9.1 on macOS and Ubuntu (same behavior).
I opened #220 that addresses this, but it's probably better to have an issue for it as well to give more context.

Thanks @gabuzi :) Running the CI on the pull

https://github.com/cncastillo/KomaMRI.jl/pull/220

If it passes all the tests, it could be an instant merge!


Debug reporting that state not loading correctly from server store

Forum post link - https://discourse.nodered.org/t/dashboard-2-beta-development/83550/127
The following debug msg's are reporting state as undefined.
(I have added the node type as a suffix)
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:87f1e1fa47a4d50a undefined - ui-text
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:24b58fe1f550fd18 undefined - ui-text
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:e4c76dbd1c4d844a undefined - ui-text
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:ee60257a3951b4eb undefined - ui-text
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:d050b3f87d0e7c2c undefined - ui-text
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:8c0b4930d485f3e4 undefined - ui-text
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:9009cf7f724cf7e3 undefined - ui-text
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:3a5ba08ef8bc953f undefined - ui-text
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:195bc4d0420ab07a undefined - ui-chart
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:11675ce3e247ee27 undefined - ui-button
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:1a391f1b47f9ac5a undefined - ui-button
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:12c7093609532b00 undefined - ui-button
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:e2712a1bde4a33e5 undefined - ui-button
conn:fIHGK11AwN-UJ0DDAAAB on:widget-load:aa418cf38de5a548 undefined - ui-button

And if you refresh your screen, are you then not seeing data that was there before?

Unfortunately I won't get a chance to fix this now until 30th at least as going away

And if you refresh your screen, are you then not seeing data that was there before?

Yes, the chart redraws as expected, and the text nodes are retrieving their last state.
So DB working as expected, but reported as 'undefined' in debug.
I guess this is more about a problem with the debug, and not an issue with the dashboard?

I won't get a chance to fix this now until 30th at least as going away

Not a problem, have a nice break, and we'll speak next year.

So DB working as expected, but reported as 'undefined' in debug.

That's a relief - in that case, just an issue with the debug statement

Can confirm this is no longer a problem - closing the issue


Added argument value preprocessing using :map option

You can alter an argument's value before it is being resolved. To do this, pass a method
name (as a symbol or a string), or a Proc (or lambda expression) to the :map option
of resolve. The method or Proc you specify is then passed the original argument value
and expected to return the value that shall be used for resolution.
This comes in handy in various cases, for instance when you need to make sure that an
argument value is well-defined:
resolve :offset, map: -> (value) { [value, 0].max }
resolve :limit, map: -> (value) { [value, 100].min }

The above example guarantees that the offset is never negative and that the limit is
capped at a reasonable value (for security reasons).

Very creative! I like it 👍


Problem with python namespace print error

Describe the bug
Powershell shows the error is related to cprint when running python3 wa_kdbe.py --allow-reboot Please see screenshot
To Reproduce
Steps to reproduce the behavior:

run python3 wa_kdbe.py --allow-reboot
See error in powershell with windows 10

Expected behavior
To work properly without error
Screenshots

Terminal output or log file
[wa_kdbe.log](https://github.com/YuvrajRaghuvanshiS/WhatsApp-Key-Database-Extractor/files/14817614/wa_kdbe.log)

Any ideas about this please ?


How to highlight line in

I have this code, Lines are drawn. But I want to highlight a line when hovered or clicked.
        {Object.keys(this.props.pavements).length > 0 && (
          <GeoJSONLayer
            data={this.props.pavements}
            linePaint={{
              'line-color': ['get', 'color'],
              'line-width': 10,
            }}
            lineLayout={{
              'line-cap': 'round',
            }}
            lineOnClick={e => this.populateInfobox(e)}
            lineOnMouseEnter={e => this.populateInfobox(e)}
          />
        )}

What can I do in lineOnClick to change the color of the clicked line?

+1

I did it by saving the color property of GeoJson in redux and changing the color of the selected feature

I assume this can then be considered closed.

The "Mapbox" way of doing this would be to use setFeatureState but that's not possible at the moment, see https://github.com/alex3165/react-mapbox-gl/issues/652


Pressing enter quickly proceeds through all of the next steps

At the Add Username stage, pressing enter after typing in the user name, proceeds to the next step (this is fine). But if the user accidentally double or tripple taps the enter key, it proceeds through the second or third step in rapid succession. This is not ideal.

https://user-images.githubusercontent.com/3348223/119517434-75f2f700-bd2c-11eb-9adf-68c3579fe3f4.mov


upgrade to etcd/client/v3

in this PR, we migrate from etcd/client/v2 to etcd/client/v3.
Some high level changes:

rework a bit the Init method -> we first try to check that a key exist it does not we create it
use KV instead of KeyAPI from V2
did not use the client/v3/concurrency. in order to not break the current locksmithctl semaphore logic
rework a bit the tests - first step in order to provide a decent coverage

Testing done

[x] update the unit tests

run kola tests with locksmith:

[x] coreos.locksmith.reboot
[x] coreos.locksmith.tls
[x] cl.locksmith.cluster

How to use
easy way:
make
scp -P 2222 ./bin/locksmithctl core@<IP_ADDRESS>:/home/core

or using the SDK:
diff --git a/app-admin/locksmith/locksmith-9999.ebuild b/app-admin/locksmith/locksmith-9999.ebuild
index 1fab0c6e4..2fca232f3 100644
--- a/app-admin/locksmith/locksmith-9999.ebuild
+++ b/app-admin/locksmith/locksmith-9999.ebuild
@@ -11,7 +11,7 @@ inherit cros-workon systemd coreos-go
 if [[ "${PV}" == 9999 ]]; then
        KEYWORDS="~amd64 ~arm64"
 else
-       CROS_WORKON_COMMIT="085ff774311dba979a53d049f6a776e156224437" # flatcar-master
+       CROS_WORKON_COMMIT="cc4db15e48c1afc979ac1c73c3ac680cb2369c43" # tormath1/upgrade-etcd
        KEYWORDS="amd64 arm64"
 fi

then
emerge-amd64-usr -av app-admin/locksmith && ./build_image

SSH into the VM - then play a bit with the ./locksmithctl and assert it consumes correctly ETCDCTL_API=3
$ sudo systemctl start etcd-member.service
$ ./locksmithctl status
Available: 1
Max: 1
$ ./locksmithctl set-max 123
Old-Max: 1
Max: 123
$ ETCDCTL_API=3 etcdctl get "coreos.com/updateengine/rebootlock/semaphore"
coreos.com/updateengine/rebootlock/semaphore
{"semaphore":123,"max":123,"holders":[]}
$ ./locksmithctl lock
$ ETCDCTL_API=3 etcdctl get "coreos.com/updateengine/rebootlock/semaphore"
coreos.com/updateengine/rebootlock/semaphore
{"semaphore":122,"max":123,"holders":["0f80dd16217b482eb89ffea2e1412115"]}

Note for reviewers
This one https://github.com/kinvolk/locksmith/pull/12/commits/fde90bdacaea509c0a2823437b391878b729a3cc was a hard one to solve and I think it results from an implementation mistake - no matter which LOCKSMITHD_ENDPOINT we set as environment variable it will still be added to the default ones - with V2 it seems it was not an issue but with V3, in the test, we set a TLS etcd node on ::2379 since the connection is considered as a success with the default http://localhost:2379 this endpoint will be used as the correct one .. but each call will fail because we send http to a https service.

I'm on the fence with what you did with the tests. I kinda like the former table-based testing. :) Any reason to move away from that?

table tests were ok until now because we were only using {err, response} struct but we now have {err, getResponse, setResponse, Txn} which can be quite big to define into a table https://github.com/kinvolk/locksmith/pull/12/commits/a1a5db461f5f0bc9e788e40296c08f0d523b5a57#diff-509fec5f7f91a11e078c85b72f3645555168d99ae5a8a036f2d0c807b0eb673fR138-R146 :confused:
Also it gives a better reading of the running tests + can eventually be run in parallel.

I think we should leverage airlock as etcd3 client through the fleetlock protocol. Then we don't need to implement this again in locksmith.


Add support for any valid switch status to the GARGOYLE_SWITCH_DEFAULTS

I have added the system check and a few notes to the documentation and history.

@adamchainz Thanks for the responses. I am out of bandwidth for this PR. I'll add to a list and maybe someday get back to it.

I might finish it off then


Support placeholder in CurriedFunction interfaces

add placeholder type (PH)
remove CurriedFunction(7~8)
remove curry(7~8)

related #173
NOTE that there may be some breaking changes in tests due to the overloads' ordering in CurriedFunctions.

Thanks! We may still wanna test this to verify compilation performance hasn't been affected; otherwise looks good.


No connection to editing api

Description
I'm trying to load my project and it takes a long while. Firefox seems to have issues connecting with the editing api (see screenshot). I tested it in Edge too, no problems yet.

Reproduction URL
https://typst.app/project/p8xNdwRe-OsNXgdW9M6WGP
Browsers
Firefox
OS
Windows

Same problem with Firefox on windows throughout yesterday 😢

We're working on it. The problem arises because one backend service (the collaboration server) overloads the main backend API sometimes. We've started tracking more metrics and are trying to find out what exactly is happening.

We have made significant improvements to both back- and frontend. In particular, the error in the original screenshot can't happen anymore because we do not use hocuspocus anymore.


Add support for transitive dependencies (needs).

Problem
When using selectors in helmfile one can use the --include-needs parameter to also install the dependencies of the selected release(s). However, this doesn't work for transitive needs, only the direct needs of the specified releases will be included. The problem is described in more detail with an example here:
https://github.com/roboll/helmfile/issues/1915
Solution
After conferring with @mumoshu we decided to introduce a new parameter called --include-transitive-needs, which will also include transitive needs. We deliberately decided to not change the behavior of --include-needs (even if including transitives might be the expected behavior for most users) to ensure backwards compatibility.
Notes
--include-transitive-needs will override any potential exclusions done by selectors or conditions. So even if you explicitly exclude a release via a selector it will still be part of the deployment in case it is a direct or transitive need of any of the specified releases.
Fixes roboll/helmfile#1915
Closes roboll/helmfile#1915

Hi @pjotre86 and @mumoshu,
As far as I know, needs has been broken for a few months now, see https://github.com/roboll/helmfile/issues/1881.
Does this PR fix this bug?

Hey @Hey @dudicoco !
Not sure, the I never ran into the problem with needs described in #1881.

Hi @pjotre86,
Did you try to recreate the issue per the instructions in https://github.com/roboll/helmfile/issues/1881?


Fix library broken for Python 2

Python 2 doesn't implement encoding argument for str.
Fixes #84

Thank you!

This should be released. 1.16.11?


super-slicer-latest: fix build

Fixes https://github.com/NixOS/nixpkgs/issues/349359. Submitted upstream PR with the fix
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 4 packages built:

super-slicer-beta
super-slicer-beta.debug
super-slicer-latest
super-slicer-latest.debug

Upstream PR: https://github.com/supermerill/SuperSlicer/pull/4441

Thank you!
Builds, and that doesn't look like a potentially breaking change.


Added Travis CI

I added the travis.yml file and the build passes! #5

currently it just tests npm test and npm run build and does not include a deploy section since this repo hasn't yet been deployed.

@klymenkoo  removing the package-lock.json makes the build fail in Travis:

I believe we should have included the package-lock from this originally PR but for now we can still include it in this PR.


[prog] set version of GLSL in shader files

Hello.
According to GLSL recommendations setting version of shader language it a good practice.
From practice side it allow to run desktop samples on Ubuntu 16.04 without install vendor specific video driver as based (out of box) driver include support for version of GLSL 100 (a.k.a. GLSL ES version 1.00) that used in OpenGL ES 2.0.
Thank you.

Hello!
I think we need to support a version on .prog-level, and generating corresponding shader-preface during shader loading. Our challenge for the future is processing shader data at highest level.
For example
<?xml version="1.0" encoding="UTF-8"?>
<program name="something">
    <shaders version="100_es | 300_es">
       ...
    </shaders>
</program>

100_es - "#version 100"
300_es - "#version 300 es"
If the version is not specified use the default - 100_es.
(for example, the precision should be processed the same way).
Thank you.

Hello.
Looks good.
I prepare new commit: also if version unknown expect that is 100, so there is no need to check is this version 100, only check if it 300 or 310.
How precision may defined in xml file?
By taking 4.5.3 Default Precision Qualifiers from GLES ES specification what can be
<program name="something">
    <shaders>
        <vertex "precision_float"="highp" "precision_int"="highp" "precision_sampler2D"="lowp" "precision_samplerCube"="lowp">
            ...
        </vertex>
        <fragment "precision_int"="mediump" "precision_sampler2D"="lowp" "precision_samplerCube"="lowp">
            ...
        <fragment>
    </shaders>
</program>

Thank you.

Hello.
The standard practice is supported the full namespace.
<shader> - ok, use default
<shader version="100_es"> - ok, use 100 es
<shader version="300_es"> - ok, use 300 es
<shader version="310_es"> - ok, use 310 es
<shader version="asdasda"> - error, can't load a shader

In addition, I think the 'program_data' class must encapsulates this functionality
// v_shader() - returns a source with a version
shader v_shader(data.value().v_shader(), shader_type::VERTEX);

Thank you.

Hello.
OK, new commit prepared.
Please note that reference for 1.0 version required that at version located only number without 'es', so definition '100_es' only for xml file.
Thank you.

Hello.
Could you please see review?
About C++. For example
static std::unordered_map<const char *, const char *> versions_map =
{
    {"100_es", "#version 100"},
    {"300_es", "#version 300 es"},
    {"310_es", "#version 310 es"}
};

...

auto version_attribute = root_node.child("shaders").attribute("version");
if(!version_attribute.empty())
{
    auto it = versions_map.find(version_attribute.as_string());
    if(it == versions_map.end())
        return false;

    v_shader_ += it->second;
    f_shader_ += it->second;
}
v_shader_ += vertex_node.text().get();
f_shader_ += fragment_node.text().get();

It is easier and 'strlen', 'strcmp', 'insert' are not needed. What do you think?
Thank you.

Hello.
Well your variant is more compact. I agree with you, so new commit added to 'prog' branch.
Thank you.

You are right, i missed "\n", it is needed.
Could you please add it?
And is it working? I didn't test.
And I think we need include <unordered_map> to unit.
Thank you.

On Windows work all discussed algorithm.
On Ubuntu work all except this propose

 - ok, use default

So on desktop logical changed: if no version set to 100 in macros approach. No benefits on Ubuntu for out of box video driver with use default version.
On Android... Actually I have a problem to success run all apk's even from master branch on emulators that use host GPU and one real device.
So it is better to test by own that propose change on own devices to make sure that nothing broken.
Thank you.

Why did you put map in separate header?
Ok... .We don't understand each other (perhaps because of my poor English).
I mean add
#include <unordered_map>

because we use unordered_map.
In my comment above, this is just an example, that as I see it.
You do not need to copy it.

On Ubuntu work all except this propose

Then why is this commit needed if it is not work?

I see.
Actually direct include do not need because we already include asset_storage that have #include < unordered_map >.
It may another do not understand.
In initial discuss I propose to add version to shader files. You set better do it in xml way. Than we discuss logic of version. I propose shader without version threat as version 100. Than I view your propose:
<shaders> - ok, use default <shaders version="100_es"> - ok, use 100 es <shaders version="300_es"> - ok, use 300 es <shaders version="310_es"> - ok, use 310 es <shaders version="asdasda"> - error, can't load a shader
And think that you do not support that idea for Android platform. That all I conclusion that use default version have some benefits for Android, but I do not view that for Ubuntu that's why there are two variants.

Actually direct include do not need because we already include asset_storage that have #include < unordered_map >.

Need. If include was removed from asset_storage (for different reasons for example refactoring), the loader will not be compiled. The best practice is include all dependencies directly into cpp unit. Implicit inclusion is bad.
The task is to parse config. What are the keys does not matter. Platform is not matter.
<shaders> - ok, use default version - "#version 100"
<shaders version="100_es"> - ok, use 100 es - "#version 100"
<shaders version="300_es"> - ok, use 300 es - "#version 300 es"
<shaders version="310_es"> - ok, use 310 es - "#version 310 es"
<shaders version="asdasda"> - error, can't load a shader

// we can't use const char * as a key,
// hash function will be using specialization for pointer-type in this case
const std::unordered_map<std::string, std::string> versions_map =
{
    {"100_es", "#version 100\n"},
    {"300_es", "#version 300 es\n"},
    {"310_es", "#version 310 es\n"}
};
const char * default_version_key = "100_es";

...

const char * key = shader_node.attribute("version").as_string(default_version_key);
auto it = versions_map.find(key);
if(it == versions_map.end())
    return false;

v_shader_ += it->second;
v_shader_ += vertex_node.text().get();

f_shader_ += it->second;
f_shader_ += fragment_node.text().get();

OK. New commit prepare.
It is very important to me to know such information.

The best practice is include all dependencies directly into cpp unit. Implicit inclusion is bad.

Here is my story - why actually I prefer to use implicit inclusion.
There is a some job - write firmware for some embedded device with ARM CPU inside. Vendor of device present the proprietary C compiler with very interesting anti theft system - at every compiled file will check license status on a server.
My team lead decide to speed-up the compile of whole project. So created task to write tool that remove includes (official term for this includes - superfluous ) that actually do not need by current file. Actually some example work of that tool you can view at includes branch.
After your story I agree with your argument, so removing of superfluous includes may not be always good practice.
Thank you.

Thank you.

Hello again.
What do you think about test for this algorithm?
My view is next.
It assumed that all required library installed by package manager:
apt-get install mesa-common-dev
apt-get install libglu1-mesa-dev
apt-get install libpugixml-dev

Thank you.

Hello.
The first I think we need to separate program_data to program_data.h/cpp. This will allow us to be tested without depending on the mesa (testing the data generation with OpenGL depending is very strange, isn't it?). And expected results result.vs/result.fs need to make in the files. The second, we could build pugixml from third-party.
Generally, I assume to integrate gtest. What do you think?
Thank you.

Hello.
Yes it it strange, so separate program_data is a good idea. How result.vs/result.fs can be view?
First and third discuss message implemented in new commit.
Using gtest will be a nice.
Thank you.

Hello.
I mean
{"default_version.prog", std::make_pair("default_version.vs", "default_version.fs")},
// or instead of the map to use the list of names
// Test1 - default_version
// input - default_version.prog
// result - default_version.vs, default_version.fs
// where *.vs/*.fs are expected vertex/fragment shaders.

Thank you.

Hello.
New commit [ready](https://github.com/TheVice/elements/commit
/124f7144ef394ee3cd1c019fa164df6a8db2d9aa), map as store save in it.
In theory, if rewrite to list storage, what type should be in member of that list, tuple?
std::list<std::tuple<std::string, std::string, std::string>>
First is a prog file, second and third is a expected vertex/fragment shaders.
Thank you.

Hello.
About 'read_from_stream' function, offer so
#include <streambuf>
...
std::string read_from_stream(std::ifstream & stream)
{
    return {std::istreambuf_iterator<char>{stream}, {}};
}

In our case the string class's automatic reallocation is enough. Or if we want to save resources, we must use the stream comparison. Read the one symbol from the stream and compare with a symbol of generated data, then get the next one and so on. But I think to use string is enough.
And template parameters of std::make_pair from tests_map can be omitted
std::make_pair<std::string, std::string>("", "") ->
std::make_pair("", "")

Thank you.

Hello.
Done.
Thank you.

Hello.
It is not building
fatal error: pugixml.hpp: No such file or directory

Missed include pugixml in makefile
-I../../third-party/pugixml/src

You ok, because you have installed libpugixml.
Thank you.

Yes, that is.
Added.

Great.
Pushed
Thank you.


Support tear-out and drop in of tabs

A user should be able to drag a tab out of window and drop it on the desktop to create a new window with the tab.
A user should be able to drag a tab from one window and drop it into the tab set of another window.  When dropping into the tab set, the user should be able to drop it at a specific point in the tab set.

After some initial work on this.  Going to try the following approach as an adjustment to the original plans:

a 'tear out' icon will be added to the tab, this will spawn the tab in a new window
tabs cannot be dragged out into their own windows
the tab bar and tabs in any window will be a drop area for tabs and a tab can be dragged from another window into a different window this way
on a successful drop of a tab into another tab set, the tab will removed from the origin window and added into the target window.  If the tabset of the origin is now empty, the window will automatically close.

PR #50 addresses full pass of this.


⚠ Bofrost.at has degraded performance

In 0f26f41, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1278 ms

Resolved: Bofrost.at performance has improved in 2a34787 after 6 minutes.


Missing Code for Generating Pickle Files

Can you provide a description of the data present in the Pickle files for Multi Domain Amazon Dataset?
Or code for generating these pickle files

We took the preprocessed version of the Amazon dataset from the mSDA paper (https://www.cse.wustl.edu/~mchen/code/mSDA.tar) that comes in a Matlab format (.mat).
I guess I further converted that into a pickle file and did some reorganization of the data, such as splitting the data into "labeled" and "unlabeled" sets, etc.
Sorry I can no longer locate the script I used for this conversion, but I can briefly describe the structure of the pkl file. The relevant for consuming the pkl file can be found in data_prep/msda_preprocessed_amazon_dataset.py
It contains a single dictionary with two keys "labeled" and "unlabeled". For either of the two items, it contains a tuple (x, y), where x is a 2d numpy array containing the input while y is a 1d numpy array with the labels.
You can also modify the script to use with other data formats.

Hey,
I looked at the pickle files. The matrix was of the shape (Number of data
points, 30000). I wanted to test your implementation on different Amazon
dataset. I believe that 30000 feature vector was constructed using the
unigrams and bigram features. Can you explain the process of generating the
feature vector of size 30000.
On Wed, Jul 11, 2018 at 2:47 AM, Xilun Chen<EMAIL_ADDRESS>wrote:

We took the preprocessed version of the Amazon dataset from the mSDA paper
(https://www.cse.wustl.edu/~mchen/code/mSDA.tar) that comes in a Matlab
format (.mat).
I guess I further converted that into a pickle file and did some
reorganization of the data, such as splitting the data into "labeled" and
"unlabeled" sets, etc.
Sorry I can no longer locate the script I used for this conversion, but I
can briefly describe the structure of the pkl file. The relevant for
consuming the pkl file can be found in data_prep/msda_preprocessed_
amazon_dataset.py
It contains a single dictionary with two keys "labeled" and "unlabeled".
For either of the two items, it contains a tuple (x, y), where x is a 2d
numpy array containing the input while y is a 1d numpy array with the
labels.
You can also modify the script to use with other data formats.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ccsasuke/man/issues/1#issuecomment-403909197, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ATsP8V9LuDXD_MtiAqF0rKnoFkjHfXyAks5uFOjAgaJpZM4VJP3T
.

Hi,
As I mentioned, the 30k dimensional matrix is taken from the mSDA paper by Chen et al. (2012), so I cannot speak for them about how exactly they processed the dataset. However, I believe they simply took the most frequent 30000 features (and we only use the top 5k to be consistent to some earlier work we compared as baselines).


Update Documentation

Documentation of Graylog v4 contains examples with v3
https://docs.graylog.org/en/4.0/pages/installation/docker.html
Expected Behavior
Show examples containing graylog docker containers of version 4 (e.g. 4.0.1-1)
Current
https://docs.graylog.org/en/4.0/pages/installation/docker.html
Examples provide graylog version 3.3
Possible Solution 1
https://docs.graylog.org/en/4.0/pages/installation/docker.html
Update Documentation with a working examples and correct dependencies for Version 4.
Possible Solution 2
Insert a link to description of version dependencies.

It's a tangent, but as part of the 4.0.0 to 4.0.1 Graylog upgrade I opted to upgrade the MongoDB container used with Graylog from 3.6 as the documentation suggested to 4.2.
I made the mistake of assuming that the Docker container would take care of handling any 3.6 to 4.2 upgrade concerns, but after checking the error logs I saw that I had to go from 3.6 to 4.0 first, then I could upgrade from 4.0 to 4.2, but only after manual intervention (AFAICT) to make the upgrade as safe.
https://docs.mongodb.com/manual/release-notes/4.2-upgrade-standalone/
I don't know enough about MongoDB to feel comfortable upgrading 4.0. to 4.2, so any tips for that in the official docs (or just a warning not to attempt a direct 3.6 to 4.2 upgrade) would be helpful to future readers.

@atc0005 Thanks for the heads up. I'll see if I can get a note on that added to the docs (https://github.com/Graylog2/documentation/pull/1020).
@phaabe Thanks for letting me know about this. I missed it! It should be fixed now.


image cannot be parsed

Hi,
this image failed to be parsed, prompt_data = parser_manager.parse(filename) returns None
I got the image from civitai.com, PNG info from automatic1111 can parse it.
Thanks.

seems to be an issue in the split_meta method of the automatic1111.py module
I don't understand why it treats the last line as key:value separated by commas, since last line also contains the negative prompt (format change from automatic11111 maybe?)

This issue should now be fixed in the dev0.3 branch, commit 432a437.
If you're feeling adventurous, feel free to pip install --upgrade<EMAIL_ADDRESS>to test it out.
Be aware, that 0.3 will be breaking existing code - check the examples for what's changed.

I don't think stable-diffusion-webui was used to generate the image, I don't know what he use, you can see other here : https://civitai.com/images/4033343
PNG ingo from stable-diffusion-webui also has troubles parsing the file, when you clic send it txt2img.
Thanks I will try the dev branch


swarm config witness amount as 1 but two nodes verify the bp msg.

then, broadcast the block msg. (different node i)

Also, there is a problem that one node send same msg twice. (same node i)

@weihaopeng both witness and collector are selected randomly based on the NHashDistance function, which is not accurate  but on average, that means this situation is proper and expected :)


Support different ABI on Windows

ffi.cc does currently use FFI_DEFAULT_ABI (and FFI_DEFAULT_ABI only) when it calls ffi_prep_cif(…).
That ABI, however, sometimes cannot be used for calling Windows system functions. I guess the following (very simple) code is an example of that:
var user32 = new require('node-ffi').Library('user32', {
   'MessageBoxW': [ 'int32', [ 'int32', 'string', 'string', 'int32' ]]
});

user32.MessageBoxW(0, 'Hello world!', 'Title of the window', 0);

When run, that example creates some dialog window, but the text (such as «Hello world!») is not readable:

Here node-ffi could follow Mozilla's js-ctypes route and support a set of ABI constants for an additional optional parameter of require('node-ffi').Library(…). Probably in the same optional object (one object per function name) where {async: 'true'} may already be given.
The complete list of available ABI is defined in https://github.com/atgreen/libffi/blob/master/src/x86/ffitarget.h and similar platform-dependent files, but support for all of them would be complex and unnecessary. I beileve that node-ffi (like js-ctypes) does actually need only some two additional ABI necessary to call Windows system functions.

Ignore this issue! I totally forgot that MessageBoxW needs UTF-16 instead if UTF-8.

Somehow MessageBoxW() from user23.dll works without any special ABI. I cannot explain it, I mean, it just works. I haven't tried anything else yet.
I have a fixed version of the above example, and with Russian comments and strings; I posted it on Habrahabr.Ru today. Here's an exact copy and a screenshot:
// функция преобразования строки JavaScript (UTF-8) в UTF-16
function TEXT(text){
   return new Buffer(text, 'ucs2').toString('binary');
}

var FFI = require('node-ffi');

// подключаемся к user32.dll
var user32 = new FFI.Library('user32', {
   'MessageBoxW': [
      'int32', [ 'int32', 'string', 'string', 'int32' ]
   ]
});

// диалоговое окно
var OK_or_Cancel = user32.MessageBoxW(
   0, TEXT('Привет, Хабрахабр!'), TEXT('Заголовок окна'), 1
);

The TEXT() converter is analogous to the macro of the same name, described at MSDN.
If using Node.js on Windows API becomes popular, then Node's devs should un-deprecate 'binary' encoding of Buffer.

Thanks for the snippet! I don't think un-deprecating binary is gonna happen though. I recommend a "safer" TEXT() function like this one that doesn't depend on deprecated APIs:
function TEXT (text) {
  // malloc() the buffer for the String
  var p = new ffi.Pointer(Buffer.byteLength(text, 'ucs2') + 1);
  var b = p.toBuffer();
  b.write(text, 'ucs2');
  b[b.length - 1] = 0;
  return p;
}

Note that this will now return a Pointer instance instead, so you should change your function signatures to 'pointer' instead of 'string'. Let me know if that works for you!

It works, thanks.

Ok cool. Well I guess we'll punt on the ABI thing for now, if you find you need it with some other Windows functions then please re-open this ticket, it should be a relatively easy feature to add (though I'd need to recompile the binaries afterwards, GAH!!!)

Further in Wikipedia, I've finally found a page where the difference of cdecl (FFI_DEFAULT_ABI) and stdcall (FFI_STDCALL) is explained.
It seems that the only difference is dealing with stack. With cdecl, the called function ends with ret and the caller cleans the stack, so the call looks like the following example:
; x = function_name(a, b, c)
push c             ; arg 3
push b             ; arg 2
push a             ; arg 1
call function_name ; jump to function_name's code
add esp, 12        ; pop function args (a, b, c) off the stack
mov x, eax         ; fetch function return value

With stdcall, the called function cleans the stack by itself (it ends with ret 12 for the above example, instead of simple ret) so there is no need to clean it (add esp, 12) every time after the call.
So, when stdcall function (such as MessageBoxW) is called with FFI_DEFAULT_ABI, the stack is most likely forced to pop twice the amount of data pushed into it. Looks somewhat dangerous (unless there is some compensator in libffi that I am not aware about).
Reopening the issue after all.

Ok will do. We need to add an `abi

Ok, so we need to add an abi option to the Library function (same options object that receives async). That will pass through to ForeignFunction, which I suppose we could add on as a 5th argument. I usually don't like having functions with arguments lengths that long, so we could also change ForeignFunction's 4th argument to an options object, if we maintain backwards compatibility.
@Mithgol I'll be busy the next couple weeks probably, but if you feel like whipping up a patch then I'll accept that, otherwise it'll be a little while.

A couple of weeks are fine, I don't mind waiting.

@Mithgol

the TEXT function does not need .toString('binary') it will break if you try to use Hebrew chanracters אבגד for example, shown as its ASCII parts characters (where each character < 128).
new Buffer is obsolete, you should use return Buffer.from(text, "ucs2")
to prevent memory read-leak you should add "\0" at the end of the strings (otherwise the title will also be shown in the body of the message, the best way is to simply add it to the TEXT function too.

Here is a modified version that also includes icons, default buttons, all of the types and RTL support,
taken from: https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-messageboxw
change  require("./ffi/node_modules/ffi/") to where you load your FFI from.
/**
 ************************************************
 * MessageBoxW  -  Unicode supported MessageBox *
 ***************************************************************
 * https://github.com/eladkarako/nodejs_ffi_winapi_messageboxw *
 ***************************************************************
 *
 * Notes:
 *
 * - API from https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-messageboxw
 * - Currently MessageBoxEx and MessageBox work the same way.
 * - user32.dll must be registerd on the system, FFI will not accept different path for the lib (for example
 *    if you'll copy the file to your program's folder),
 *    so the program tries to get the 'windir' system-environment variable (or fallback to 'C:\Windows\').
 * - only the 32bit (x86) version will work with FFI, the x64 version will fail with an error.
 *
**/

"use strict";

const FFI               = require("./ffi/node_modules/ffi/")
   //,REF               = require("./ffi/node_modules/ref/")
     ,_TEXT             = function(text){ return Buffer.from(text + "\0", "ucs2"); }   //string-conversion UTF-8 to UTF-16

     ,USER32_PATH       = ((process.env.windir || "C:\Windows") + "/System32/user32.dll").replace(/[\\\/]+/g, "/")
     ,USER32_FUNCTIONS  = {
                           "MessageBoxA":   ["int32", [ "int32", "string", "string", "int32" ]]
                          ,"MessageBoxW":   ["int32", [ "int32", "string", "string", "int32" ]]
                          ,"MessageBoxExW": ["int32", [ "int32", "string", "string", "int32" ]]
                          }

     ,TYPES             = {
                           "MB_OK"                 : 0x00000000   //The message box contains one push button: OK. This is the default.
                          ,"MB_OKCANCEL"           : 0x00000001   //The message box contains two push buttons: OK and Cancel.
                          ,"MB_ABORTRETRYIGNORE"   : 0x00000002   //The message box contains three push buttons: Abort, Retry, and Ignore.
                          ,"MB_YESNOCANCEL"        : 0x00000003   //The message box contains three push buttons: Yes, No, and Cancel.
                          ,"MB_YESNO"              : 0x00000004   //The message box contains two push buttons: Yes and No.
                          ,"MB_RETRYCANCEL"        : 0x00000005   //The message box contains two push buttons: Retry and Cancel.
                          ,"MB_CANCELTRYCONTINUE"  : 0x00000006   //The message box contains three push buttons: Cancel, Try Again, Continue. Use this message box type instead of MB_ABORTRETRYIGNORE.
                          }
     ,ICONS             = {
                           "MB_ICONEXCLAMATION"    : 0x00000030   //An exclamation-point icon appears in the message box.
                          ,"MB_ICONWARNING"        : 0x00000040   //An icon consisting of a lowercase letter i in a circle appears in the message box.
                          ,"MB_ICONASTERISK"       : 0x00000040   //An icon consisting of a lowercase letter i in a circle appears in the message box.
                          ,"MB_ICONQUESTION"       : 0x00000020   //A question-mark icon appears in the message box. The question-mark message icon is no longer recommended because it does not clearly represent a specific type of message and because the phrasing of a message as a question could apply to any message type. In addition, users can confuse the message symbol question mark with Help information. Therefore, do not use this question mark message symbol in your message boxes. The system continues to support its inclusion only for backward compatibility.
                          ,"MB_ICONSTOP"           : 0x00000010   //A stop-sign icon appears in the message box.
                          ,"MB_ICONERROR"          : 0x00000010   //A stop-sign icon appears in the message box.
                          ,"MB_ICONHAND"           : 0x00000010   //A stop-sign icon appears in the message box.
                          }
     ,DEFAULT_BUTTON    = {
                           "MB_DEFBUTTON1"         : 0x00000000   //The first button is the default button. MB_DEFBUTTON1 is the default unless MB_DEFBUTTON2, MB_DEFBUTTON3, or MB_DEFBUTTON4 is specified.
                          ,"MB_DEFBUTTON2"         : 0x00000100   //The second button is the default button.
                          ,"MB_DEFBUTTON3"         : 0x00000200   //The third button is the default button.
                          ,"MB_DEFBUTTON4"         : 0x00000300   //The fourth button is the default button.
                          }
     ,OPTIONS           = {
                           "MB_RIGHT"              : 0x00080000   //The text is right-justified.
                          ,"MB_RTLREADING"         : 0x00100000   //Displays message and caption text using right-to-left reading order on Hebrew and Arabic systems.
                          ,"MB_SETFOREGROUND"      : 0x00010000   //The message box becomes the foreground window. Internally, the system calls the SetForegroundWindow function for the message box.
                          ,"MB_TOPMOST"            : 0x00040000   //The message box is created with the WS_EX_TOPMOST window style.
                          }
     ,RETURNS           = {
                           "IDOK"                  : 0x00000001   //1  The OK button was selected.
                          ,"IDCANCEL"              : 0x00000002   //2  The Cancel button was selected (or [ESCAPE] pressed).
                          ,"IDABORT"               : 0x00000003   //3  The Abort button was selected.
                          ,"IDRETRY"               : 0x00000004   //4  The Retry button was selected.
                          ,"IDIGNORE"              : 0x00000005   //5  The Ignore button was selected.
                          ,"IDYES"                 : 0x00000005   //6  The Yes button was selected.
                          ,"IDNO"                  : 0x00000007   //7  The No button was selected.
                          ,"IDTRYAGAIN"            : 0x0000000A   //10 The Try Again button was selected.
                          ,"IDCONTINUE"            : 0x0000000B   //11 The Continue button was selected.
                          }

     ,USER32            = new FFI.Library(USER32_PATH, USER32_FUNCTIONS)
     ;

var returned_value;

returned_value = USER32.MessageBoxExW(0
,_TEXT("Resource not available\nDo you want to try again?")
,_TEXT("Account Details")
,ICONS.MB_ICONWARNING | TYPES.MB_CANCELTRYCONTINUE | DEFAULT_BUTTON.MB_DEFBUTTON2
)

//see the verbosed output for better readibility
returned_value = Object.values(RETURNS).indexOf(returned_value);  //get index in 'RETURNS'.
returned_value = Object.keys(RETURNS)[returned_value];            //get key name (helps verbosity).

console.log('user selected \"' + returned_value + '\"');

//-------------------------------------------------------------------------

//Right to left example where the text is RTL (readibility) and the dialog UI-direction is RTL (upside-down)
returned_value = USER32.MessageBoxExW(0
,_TEXT("משאב לא זמין" + "\n" + "האם לנסות שוב?")
,_TEXT("פרטי חשבון")
,ICONS.MB_ICONWARNING | TYPES.MB_CANCELTRYCONTINUE | DEFAULT_BUTTON.MB_DEFBUTTON2 | OPTIONS.MB_RIGHT | OPTIONS.MB_RTLREADING
)

//see the verbosed output for better readibility
returned_value = Object.values(RETURNS).indexOf(returned_value);  //get index in 'RETURNS'.
returned_value = Object.keys(RETURNS)[returned_value];            //get key name (helps verbosity).

console.log('user selected \"' + returned_value + '\"');

taken from: https://github.com/eladkarako/nodejs_ffi_winapi_messageboxw


can not compile tag v<IP_ADDRESS>

My Environment

ArangoDB Version: v<IP_ADDRESS>
Configuration:               cmake ..
Operating System: Linux arango 5.9.0-2-amd64 #1 SMP Debian 5.9.6-1 (2020-11-08) x86_64 GNU/Linux

Steps to reproduce
git clone https://github.com/arangodb/arangodb
cd arangodb
git checkout v<IP_ADDRESS>
mkdir build
cd build
cmake ..
V=1 make -j 4

Problem:
user@arango:~/arangodb-3.7/build$ V=1 make -j 4
[  0%] Built target jemalloc_build
[  0%] Built target libunwind_build
[  1%] Built target zlibstatic
[  2%] Built target nghttp2
[  2%] Built target boost_filesystem
[  3%] Built target v8_build
[  9%] Built target s2
[  9%] Built target boost_system
[  9%] Built target boost_program_options
[  9%] Built target arango_v8_no_deadline
[  9%] Built target snappy-static
[  9%] Built target arango_v8_deadline
[ 10%] Built target man
[ 10%] Built target arango-validation
[ 10%] Built target boost_thread
[ 10%] Built target llhttp
[ 10%] Built target lz4_static
[ 10%] Built target modules
[ 10%] Built target arango_v8
[ 11%] Built target snowball
[ 12%] Built target simdcomp-static
[ 12%] Built target iresearch-scorer-bm25-static
[ 12%] Built target iresearch-scorer-tfidf-static
[ 12%] Built target iresearch-build_identifier
[ 13%] Built target iresearch-ofst
[ 13%] Built target iresearch-build_version
[ 13%] Built target iresearch-murmurhash
[ 13%] Built target build_version
[ 13%] Built target arango_storage_engine_common
[ 14%] Built target arango_utils
[ 14%] Built target gtest
[ 14%] Built target stemmer_deps
[ 17%] Built target boost_locale
[ 25%] Built target arango
[ 29%] Built target stemmer-static
[ 30%] Built target arango_geo
[ 44%] Built target rocksdb
[ 45%] Built target arango_shell
[ 45%] Built target iresearch-analyzer-mask-static
[ 46%] Built target fuerte
[ 46%] Built target arango_metrics
[ 47%] Built target arango_cache
[ 47%] Built target arangobench
[ 47%] Built target arangodump
[ 47%] Built target arangoimport
[ 47%] Built target arangorestore
[ 48%] Built target arangovpack
[ 48%] Built target arangoexport
[ 48%] Built target arango_indexes
[ 48%] Built target arangosh
[ 50%] Built target iresearch-format-1_0-static
[ 50%] Built target iresearch-analyzer-norm-static
[ 50%] Built target iresearch-analyzer-ngram-static
[ 50%] Built target iresearch-analyzer-stem-static
[ 50%] Built target arango_network
[ 50%] Built target iresearch-analyzer-delimiter-static
[ 51%] Built target arango_cluster_engine
[ 51%] Built target iresearch-analyzer-text-static
[ 51%] Built target arango_cluster_methods
[ 56%] Built target iresearch-static
[ 59%] Built target arango_iresearch
[ 59%] Built target arango_common_rest_handler
[ 61%] Built target arango_agency
[ 63%] Built target arango_rocksdb
[ 63%] Built target arango_storage_engine
[ 63%] Built target arango_replication
[ 65%] Built target arango_pregel
[ 68%] Built target arango_vocbase
[ 69%] Built target arango_v8server
[ 69%] Building CXX object arangod/CMakeFiles/arango_aql.dir/Aql/ModificationExecutor.cpp.o
[ 69%] Building CXX object arangod/CMakeFiles/arango_aql.dir/Aql/LimitExecutor.cpp.o
[ 69%] Building CXX object arangod/CMakeFiles/arango_aql.dir/Aql/LimitStats.cpp.o
[ 69%] Building CXX object arangod/CMakeFiles/arango_aql.dir/Aql/MaterializeExecutor.cpp.o
[ 69%] Building CXX object arangod/CMakeFiles/arango_aql.dir/Aql/ModificationExecutorHelpers.cpp.o
/home/user/arangodb-3.7/arangod/Aql/LimitExecutor.cpp: In member function ‘arangodb::aql::AqlCall arangodb::aql::LimitExecutor::calculateUpstreamCall(const arangodb::aql::AqlCall&) const’:
/home/user/arangodb-3.7/arangod/Aql/LimitExecutor.cpp:88:30: error: no match for ‘operator=’ (operand types are ‘arangodb::aql::AqlCall::Limit’ {aka ‘std::variant<long unsigned int, arangodb::aql::AqlCall::Infinity>’} and ‘int’)
   88 |     upstreamCall.hardLimit = 0;
      |                              ^
In file included from /home/user/arangodb-3.7/arangod/Aql/AqlCall.h:35,
                 from /home/user/arangodb-3.7/arangod/Aql/ExecutionBlockImpl.h:29,
                 from /home/user/arangodb-3.7/arangod/Aql/LimitExecutor.h:30,
                 from /home/user/arangodb-3.7/arangod/Aql/LimitExecutor.cpp:26:
/usr/include/c++/10/variant:1358:16: note: candidate: ‘constexpr std::variant<_Types>& std::variant<_Types>::operator=(const std::variant<_Types>&) [with _Types = {long unsigned int, arangodb::aql::AqlCall::Infinity}]’
 1358 |       variant& operator=(const variant&) = default;
      |                ^~~~~~~~
/usr/include/c++/10/variant:1358:26: note:   no known conversion for argument 1 from ‘int’ to ‘const std::variant<long unsigned int, arangodb::aql::AqlCall::Infinity>&’
 1358 |       variant& operator=(const variant&) = default;
      |                          ^~~~~~~~~~~~~~
/usr/include/c++/10/variant:1359:16: note: candidate: ‘constexpr std::variant<_Types>& std::variant<_Types>::operator=(std::variant<_Types>&&) [with _Types = {long unsigned int, arangodb::aql::AqlCall::Infinity}]’
 1359 |       variant& operator=(variant&&) = default;
      |                ^~~~~~~~
/usr/include/c++/10/variant:1359:26: note:   no known conversion for argument 1 from ‘int’ to ‘std::variant<long unsigned int, arangodb::aql::AqlCall::Infinity>&&’
 1359 |       variant& operator=(variant&&) = default;
      |                          ^~~~~~~~~
/usr/include/c++/10/variant:1421:2: note: candidate: ‘template<class _Tp> std::enable_if_t<((__exactly_once<std::variant<_Types>::__accepted_type<_Tp&&, typename std::enable_if<__not_self<_Tp&&>, void>::type> > && is_constructible_v<std::variant<_Types>::__accepted_type<_Tp&&, typename std::enable_if<__not_self<_Tp&&>, void>::type>, _Tp>) && is_assignable_v<std::variant<_Types>::__accepted_type<_Tp&&, typename std::enable_if<__not_self<_Tp&&>, void>::type>&, _Tp>), std::variant<_Types>&> std::variant<_Types>::operator=(_Tp&&) [with _Tp = _Tp; _Types = {long unsigned int, arangodb::aql::AqlCall::Infinity}]’
 1421 |  operator=(_Tp&& __rhs)
      |  ^~~~~~~~
/usr/include/c++/10/variant:1421:2: note:   template argument deduction/substitution failed:
/usr/include/c++/10/variant: In substitution of ‘template<class ... _Types> template<class _Tp, class> using __accepted_type = std::variant<_Types>::__to_type<__accepted_index<_Tp> > [with _Tp = int&&; <template-parameter-2-2> = void; _Types = {long unsigned int, arangodb::aql::AqlCall::Infinity}]’:
/usr/include/c++/10/variant:1417:14:   required by substitution of ‘template<class _Tp> std::enable_if_t<((__exactly_once<std::variant<long unsigned int, arangodb::aql::AqlCall::Infinity>::__accepted_type<_Tp&&, typename std::enable_if<__not_self<_Tp&&>, void>::type> > && is_constructible_v<std::variant<long unsigned int, arangodb::aql::AqlCall::Infinity>::__accepted_type<_Tp&&, typename std::enable_if<__not_self<_Tp&&>, void>::type>, _Tp>) && is_assignable_v<std::variant<long unsigned int, arangodb::aql::AqlCall::Infinity>::__accepted_type<_Tp&&, typename std::enable_if<__not_self<_Tp&&>, void>::type>&, _Tp>), std::variant<long unsigned int, arangodb::aql::AqlCall::Infinity>&> std::variant<long unsigned int, arangodb::aql::AqlCall::Infinity>::operator=<_Tp>(_Tp&&) [with _Tp = int]’
/home/user/arangodb-3.7/arangod/Aql/LimitExecutor.cpp:88:30:   required from here
/usr/include/c++/10/variant:1335:8: error: no type named ‘type’ in ‘struct std::enable_if<false, void>’
 1335 |  using __accepted_type = __to_type<__accepted_index<_Tp>>;
      |        ^~~~~~~~~~~~~~~
make[2]: *** [arangod/CMakeFiles/arango_aql.dir/build.make:1213: arangod/CMakeFiles/arango_aql.dir/Aql/LimitExecutor.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:3935: arangod/CMakeFiles/arango_aql.dir/all] Error 2
make: *** [Makefile:171: all] Error 2
user@arango:~/arangodb-3.7/build$ git branch
* (HEAD detached at v<IP_ADDRESS>)
  devel
user@arango:~/arangodb-3.7/build$ uname -a
Linux arango 5.9.0-2-amd64 #1 SMP Debian 5.9.6-1 (2020-11-08) x86_64 GNU/Linux
user@arango:~/arangodb-3.7/build$ g++ --version
g++ (Debian 10.2.0-17) 10.2.0
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Expected result:
compiles without an error. devel@7469380cc4bd6172134a825c9ed049845be2cd54 compiles.

Hi @baslr,
I haven't tried <IP_ADDRESS> with g++10.2 yet (will do tomorrow), but I can see there is the following difference between <IP_ADDRESS> and devel for this particular file:
diff --git a/arangod/Aql/LimitExecutor.cpp b/arangod/Aql/LimitExecutor.cpp
index ffbb8f6194..f5f6adc56e 100644
--- a/arangod/Aql/LimitExecutor.cpp
+++ b/arangod/Aql/LimitExecutor.cpp
@@ -86,7 +86,7 @@ auto LimitExecutor::calculateUpstreamCall(AqlCall const& clientCall) const -> Aq
     TRI_ASSERT(clientCall.hasHardLimit());

     upstreamCall.offset = upstreamCall.offset + remainingLimit();
-    upstreamCall.hardLimit = size_t{0};
+    upstreamCall.hardLimit = std::size_t(0);
     // We need to send fullCount upstream iff this is fullCount-enabled LIMIT
     // block.
     upstreamCall.fullCount = infos().isFullCountEnabled();

If you want to try this out, please go ahead. If not, I will have a look at it tomorrow.
I also can't say for sure if there will be further compile errors for <IP_ADDRESS> with g++10.2.
devel should be fine with that compiler version, but we build and CI 3.7 using g++-9.2.

The 3.7 branch compiles fine for me with g++-10.2.
However, tag v<IP_ADDRESS> does not. It produces the compile error you posted, both with g++10.2 and recent clang++ versions.
@kvahed has fixed this issue upstream already:
commit 9fc2cd4157641ac0d68fed052dc8d6b6a947e7b8
Author: Kaveh Vahedipour<EMAIL_ADDRESS>Date:   Wed Oct 14 17:51:20 2020 +0200

    clang compilation issue

diff --git a/arangod/Aql/LimitExecutor.cpp b/arangod/Aql/LimitExecutor.cpp
index 5c07563f0b..61249883de 100644
--- a/arangod/Aql/LimitExecutor.cpp
+++ b/arangod/Aql/LimitExecutor.cpp
@@ -85,7 +85,7 @@ auto LimitExecutor::calculateUpstreamCall(AqlCall const& clientCall) const -> Aq
     TRI_ASSERT(clientCall.hasHardLimit());

     upstreamCall.offset = upstreamCall.offset + remainingLimit();
-    upstreamCall.hardLimit = 0;
+    upstreamCall.hardLimit = size_t{0};
     // We need to send fullCount upstream iff this is fullCount-enabled LIMIT
     // block.
     upstreamCall.fullCount = infos().isFullCountEnabled();

But that fix is not in the v<IP_ADDRESS> tag, and will not get into it. We are compiling the 3.7 releases g++-9.2, so it just went through for us, and obviously we don't want to move the tag forward for an already created release.
You could try applying the above patch to the source, or move to a newer tag (v3.7.5) or the 3.7 branch.

Hi @jsteemann,
thank you for investigating. I use v3.7.5 then, but there is no v3.7.5 tag in this repository anymore 🤔

I have another anragodb repo clone where v3.7.5 is https://github.com/arangodb/arangodb/commit/a3af96701fac7b3ec7cd398be150a580f4649bf5 and v3.7.4 is https://github.com/arangodb/arangodb/commit/51f167605c6f29169c3dc6a2df37c37910e2da86.

@baslr : ah ok, I wasn't aware of that this tag was removed.
Unfortunately, tags may change for versions that haven't yet been released. 3.7.5 is one such example.
The easiest is probably to switch to the 3.7 branch (in contrast to using a tag), because that will be relatively up-to-date and should include most recent fixes.

@jsteemann I will use the 3.7 branch then :-)


Incorrect database identification in step 5 of the first strategy

In the first strategy, if I understand correctly, the text describing the 5th step incorrectly indicates that the PRIMARY database should be put in RW mode and upgraded. Should this not be the SECONDARY database? In any case it doesn't match the diagram.
"3. Turn the primary database to read-write mode and run the upgrade script in the stage slot (5)."

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

ID: baa6b22d-e969-1a7b-5598-a34e0f6314a6
Version Independent ID: 2d741fa1-3fea-7f78-5074-0627b1bfa129
Content: Rolling application upgrades - Azure SQL Database
Content Source: articles/sql-database/sql-database-manage-application-rolling-upgrade.md
Service: sql-database
GitHub Login: @anosov1960
Microsoft Alias: sashan

@MashaMSFT please provide an update on progress on this issue

Hi @CarlRabeler , we're still working on this :) Thanks!

Hi @agentHoover , thanks again for your feedback! The steps identified in the article have been corrected. Can you please verify your issue has been addressed? Thanks!

Looks good.  Thanks.


Rename lengthscale to lengthscales

Addressed your comments - thanks. I'll merge once the tests pass.


We need a FAQ that explains roles better

Could we please have a description of roles that are assignable to users on discord with an explanation of when they are assigned?

Can I start adding ?

Thanks @mikeysan .
Yes @UnevenCoder , please start adding, we dont need everything at once. Even 1 or 2 roles with description add value to the community 👍

@mikeysan this is indeed necessary, thank you for raising the issue 👍. Do you think this FAQ can simply be in this repository, or could it also be on EddieBot?

I think we need a home for general community FAQs, where EddieBot can read it from there. Also each repo might have its own FAQs.

I think eddie bot will be better

We can always move it later, it would be best to document it where it is the most convenient for now. It will add value once it is available which more important than finding the "perfect" location, which wont always be perfect as our project/community evolve  🤓
In short @UnevenCoder I think support would be best and you think EddieBot - I think both are right, so whoever does this can decide for now 😄

cool why not both ?

@UnevenCoder If the info is duplicated in both places, when we change on one place, we need to remember to change on the other place as well 😅. For that reason, I think we should have it on the support repo which is more "abstract" or higher level, then on EddieBot we add a link to the support FAQ. So we can make a change to both places, but with the role explanation on only one.

I agree with @BOLT04 - we want it in a single place and support is best, then we can always easily link to it, rather than having docs mixed in with functionality.

Stalebot we still need this 🤓

I think we still need this stalebot

Maybe this could be added to the #README channel, this is the supporting doc https://github.com/EddieHubCommunity/support/blob/main/discord-readme.md

Still needed


('MMDataParallel only supports single GPU training, if you need to' AssertionError: MMDataParallel only supports single GPU training, if you need to train with multiple GPUs, please use MMDistributedDataParallelinstead.

 ('MMDataParallel only supports single GPU training, if you need to'
AssertionError: MMDataParallel only supports single GPU training, if you need to train with multiple GPUs, please use MMDistributedDataParallelinstead.

OK, seems need specific launcher default is none. However using pytorch as default got:
    raise KeyError(key) from None
KeyError: 'RANK'

We gave up the support for multi-GPU training with DataParallel any more since there is no advantage over DistributedDataParallel.

@hellock  But it can not work out of box now when using multi-gpu on one machine.
It claims need several envriment variables which seems hard to set

@hellock DataParallel was working alright just a couple of weeks ago. Is this change due to some new issue? If not, would you consider making that a warning instead of an assert?
As the above thread said, DataParallel is easier to use. It also shuts down more gracefully. With DistributedDataParallel, when I press Ctrl^C, but sometimes the underlying process doesn't get shutdown and I have to kill it explicitly.

I commented out the assert in MMDataParallel and ran the training, it works! (I have switched off evaluation during training).

Hi, Another observation is that training DistributedDataParallel uses more CPU and GPU memory compared to training with DataParallel. Found couple of threads talking about by searching (For example: https://discuss.pytorch.org/t/is-it-expected-for-distributeddataparallel-to-use-more-memory-on-1-gpu-in-a-1gpu-1process-setup/77748/2) - that says it is a limitation - not sure.

@hellock But it can not work out of box now when using multi-gpu on one machine.
It claims need several envriment variables which seems hard to set

For multiple GPUs on a single machine, it just works as simple as DataParallel and no additional environment variable is needed. ./dist_train.sh is enough.

@hellock DataParallel was working alright just a couple of weeks ago. Is this change due to some new issue? If not, would you consider making that a warning instead of an assert?
As the above thread said, DataParallel is easier to use. It also shuts down more gracefully. With DistributedDataParallel, when I press Ctrl^C, sometimes the underlying process doesn't get shutdown and I have to kill it explicitly.

To support the multi-GPU mode of DataParallel, we need to overwrite a few more methods to add two apis train_step() and val_step(). There is a trend to discard DataParallel since it is twice slower than DistributedDataParallel and some new projects/repos only support DistributedDataParallel.

I removed the assert in MMDataParallel and ran the training, it works!


balenaOS in container worker?

@klutchell is it worth us making a balenaOS in a container worker:  https://github.com/balena-os/balenaos-in-container
It feels like this may be useful? (Spin up virtual device, run tests like the cloud test suite on it). I know there is overlap with the qemu worker though so not sure if this would be worth doing or not

I think this is definitely worth it, and less friction than a qemu worker. Both should exist IMO, and IIRC Alex M specifically mentioned testing basic interfaces against this.

@klutchell I'll get onto it, quite keen to get this up and running - do you know if the jenkins yocto jobs create a draft base image that can be used with this? In the repo I linked, they are pulling from here: https://hub.docker.com/r/resin/resinos/tags, which only contains released versions as far as I can tell

do you know if the jenkins yocto jobs create a draft base image that can be used with this?

Yeah, the Jenkins jobs attach a .docker extension in addition to the images.
\https://jenkins.product-os.io/view/Yocto/job/yocto-raspberrypi3/1065/
It's in the format of a docker save, so just need to download it and docker load balena-image.docker.

I completely agree. One of the benefits of running containerized is that you don't need to dedicate memory to it, it shares memory with the host system. There's also less time spent with things like booting.


[SPARK-46654][DOCS][FOLLOW-UP] Remove obsolete TODO item

What changes were proposed in this pull request?
Remove obsolete TODO item
Why are the changes needed?
the Example 2 test had been already enabled
Does this PR introduce any user-facing change?
No
How was this patch tested?
CI
Was this patch authored or co-authored using generative AI tooling?
No

Merged to master.


Function for flexible access to the content of a saver / checkpoint file

As far as I am aware, the only ways to interact with a saver file through API are (from https://www.tensorflow.org/versions/r0.7/how_tos/variables/index.html , I also looked at the API documentation online):

to restore a full model into exactly the same computational graph
to restore variables 'one at a time' through an op.
Am I right or did I miss something?

Would it be possible to release additional API functions giving more flexible access to a saver file? Like making it possible to:

list all tensors saved and their size, name etc contained in a saver file
access a tensor saved in a saver file by just reading its content and outputting it as a series of numpy arrays (for easy post processing), instead of needing to add an op, run it etc.

2966fcd adds support for most of what you want. Assigning to @sherrym for further updates.

286c5a4 added support to print the content of a tensor.

c85b942 added a python-based tool for inspecting checkpoint.
To print shape information:
inspect_checkpoint --file_name=model.ckpt-4971
To print contents of a particular tensor:
inspect_checkpoint --file_name=model.ckpt-4971
--tensor_name=mixed_17x17x768e/branch7x7dbl/Conv_2/weights/ExponentialMovingAverage
NOTE: If you see this message, it's likely that your checkpoint file
has been compressed with SNAPPY:
"Data loss: Unable to open table file /tmp/model.ckpt-4971: Data
loss: corrupted compressed block contents: perhaps your file is in a
different file format and you need to use a different restore operator?
It's likely that your checkpoint file has been compressed with SNAPPY."
To work around this issue without regenerating the
checkpoint files for now, you can rebuild by defining SNAPPY in
tensorflow/core/platform/posix/port.cc and link "lib_internal" with snappy
(-lsnappy) in tensorflow/core/BUILD.

I got the same error with the "Data loss, etc.", but could not readily figure out how this could be fixed @sherrym ?
I mean fine-tuning from inception_resnet_v2_2016_08_30.ckpt works using TF-Slim. The evaluation of the fine-tuned model works too, but when I try to do inference using the newly created checkpoint I got the same error (same with inspect_checkpoint)
The demo inference from there works fine as well: https://github.com/tensorflow/models/blob/master/slim/slim_walkthough.ipynb


Update js-packages.csv

mark azure-arm-apimanagement is deprecated in the "support" "EOL Date" and "Replace" columns.

Hi @josefree,
Looks like the CI is failing because it requires when a library is marked as deprecated it needs to have a link to a migration guide added. The migration guide link should be in the following format aka.ms/azsdk/<language>/migrate/<library>.
Here are the libraries that are failing CI:

azure-arm-batchai
azure-arm-analysisservices
azure-arm-apimanagement
azure-arm-machinelearningcompute

@ronniegeraghty which column should have the link to the migration guide? Is it "ReplaceGuide"? I see quite a few "NA" in this column of those old deprecated packages.  So I updated my updated rows with "NA".


FR: Add support for read-only tags when allowClear is true

Hi,
Thanks for the plugin.
I'm wondering if it would be possible to add support for both removable and not-removable tags, e.g. via support for readonly or disabled tag on "option" tag.
I created some POC: https://github.com/Istalacar/bootstrap5-tags/commit/bcd802b1cf1fed321368c2ed6037ef9e55e38d44
Also, "readonly" attr is not part of HTML standard. It might be better to us e.g. tag-readonly or something simillar.
Best regards
JN

@Istalacar that sounds really cool and it seems simple enough
feel free to make a PR and update the demo.html so i can give this a try :)

@Istalacar i added on master a feature to show disabled option, maybe that should do it ?

How would I go about displaying the tags as disabled, using what you two made above?
I tried data-show-disabled="true" and also just adding the disabled attribute to the select.
I also created my own ugly solution with an overlayed div and a function that copied the tags into the div :-) but it was ugly and it seems that there's a simpler way.
I'm using the latest version 1.5.12 and I'm also using Modular Behaviour.

@perikorese  you can see an example here
https://github.com/lekoala/bootstrap5-tags/blob/e6fcb5bdc5dbf98b524cc7fd5ec47eb7bc35a809/demo.html#L418-L431

I was looking there earlier, but now I get it. Thanks.

@perikorese
something like this work fine
https://github.com/lekoala/bootstrap5-tags/blob/3f48b7e928939849fb9c4e2832a48fc9dc9d008b/demo.html#L185-L198

@lekoala Thanks again.
Can data-server="" get disabled attribute from json like it can get selected attribute?

@perikorese
seems to work fine!

https://github.com/lekoala/bootstrap5-tags/commit/b5a967740dcd64864004edb045d1671ac8eb1f1d
you will not be able to update it dynamically, you need to reload the data with the attributes updated in the json response
i added the loadData function in the public api on master if you need to reload static json
otherwise with liveServer, it should update just fine on its own

Hmm, okay, I do have "disabled": true on the ones I want in the json, I'm pulling in from a database, but the tags are not disabled.
I use these bootstrap5-tags related settings on the <select> element along with Modular Behaviour:
data-server="/path/to/json/"
data-server-params='{"id":"0"}'
data-allow-new="true"
data-allow-clear="true"
data-clear-end="true"
data-show-disabled="true"

@perikorese not sure what's not working for you
if you check demo.html you have Tags (onload server side + preselected values) it seems fine
do you have a jsfiddle or codepen where i can see this?

I found another way to do what I wanted, which is basically displaying the tags-area as inactive before an edit button is clicked. I used CSS.
For now I will not take more of your time with this, but I'll get back if I investigate it again.


[SUPPORT] command line HiveSyncTool: parsing with JCommander broken

Describe the problem you faced
Upgraded to hudi 0.12 here (from 0.10) and it seems some things changed to the HiveSyncTool, more specifically to HiveSyncConfig.java
Where before there were defaults for some Boolean parameters, this is now no longer the case. As an example:
    @Parameter(names = {"--spark-datasource"}, description = "Whether sync this table as spark data source table.")
    public Boolean syncAsSparkDataSourceTable;

used to be
  @Parameter(names = {"--spark-datasource"}, description = "Whether sync this table as spark data source table.")
  public Boolean syncAsSparkDataSourceTable = true;

When I try to run the synctool commandline, I now get NPE's as soon as I include one of these Boolean parameters.
I found https://github.com/cbeust/jcommander/issues/447
This does not appear to be fixed in later JCommander releases at first sight (did a quick test overriding the dependencies).
Haven't tested yet whether switching to boolean as suggested in that issue fixes it. Reverting to default values as before also has the issue https://github.com/cbeust/jcommander/issues/378 (so it then just flips the set default which is weird). Specifying an arity 1 so the value has to be set is maybe another option (https://jcommander.org/).
To Reproduce
Steps to reproduce the behavior:

Run HiveSyncTool main and specify one of the boolean parameters; e.g. --spark-datasource, --ignore-exceptions...
a NullPointerException will be thrown

Expected behavior
Should run fine
Environment Description

Hudi version : 0.12

Stacktrace
java.lang.NullPointerException:
[info]   at org.apache.hudi.com.beust.jcommander.JCommander.parseValues(JCommander.java:718)
[info]   at org.apache.hudi.com.beust.jcommander.JCommander.parse(JCommander.java:340)
[info]   at org.apache.hudi.com.beust.jcommander.JCommander.parse(JCommander.java:319)
[info]   at org.apache.hudi.hive.HiveSyncTool.main(HiveSyncTool.java:353)

@matthiasdg thanks for reporting the issue.  We'll try to reproduce it.

Hi, I can fix this bug.

#7068 @yihua @xushiyan Have a review, if you are available.

Thanks for taking this up @xicm


Improve Clarity of Pipeline Version Logs During Execution

Open Source Contributors Welcomed!
Please comment below if you would like to work on this issue!
Contact Details [Optional]
<EMAIL_ADDRESS>What happened?
Currently, when running a pipeline in ZenML, the log messages regarding different versions (such as pipeline version, model version, etc.) are not clearly distinguishable. This lack of clarity can lead to confusion in understanding which version of what component is being referenced. An example of the current logging format is as follows:
Initiating a new run for the pipeline: ingest.
Registered new version: (version 3).
New model version 6 was created.

Task Description
Enhance the log messages related to versioning in ZenML to be more explicit and distinguishable. This involves clearly specifying what each version number pertains to (e.g., pipeline version, model version) in the log messages.
Expected Outcome

Log messages should clearly indicate the type of version being referenced (e.g., "Pipeline version 3 registered", "Model version 6 created").
This enhancement will improve the user experience by providing clearer and more informative logs during pipeline execution.
Steps to Implement
Review the current logging implementation for pipeline execution in ZenML.
Modify the log messages to include explicit references to the type of version (pipeline, model, etc.).
Ensure consistency in logging style across different parts of the application.
Test the new logging implementation to ensure clarity and accuracy.
Update any relevant documentation to reflect the changes in the logging format.

Additional Context
This improvement is part of ongoing efforts to make ZenML more user-friendly and intuitive, especially in understanding the lifecycle and versioning of pipelines and their components.
Code of Conduct

[ ] I agree to follow this project's Code of Conduct

Already completed and released.


OSX - Catalina: Key repeat broken after Revery upgrade

#1137 upgrades Revery from commit d2fd73b to 99441c7 - it seems, somewhere in between, the 'key repeat' functionality on OSX 10.15 breaks.
This doesn't reproduce on OSX 10.14.

For now, I'll back out the change to upgrade revery - but we'll need to fix this in Revery before we can pick up the latest.


[Event Request] - OnBeforeGetLocation_CheckWarehouse table 5902 "Service Line"

Dear ALAppExtensions Team:
Please consider adding a new event publisher in table 5902 "Service Line"
NEW PUBLISHER:
[IntegrationEvent(false, false)]
local procedure OnBeforeGetLocation_CheckWarehouse(var ServiceLine: Record "Service Line"; var IsHandled: Boolean)
begin
end;
The code in procedure "CheckWarehouse" in table 5902 "Service Line" would be modified as follows:
OLD CODE:
local procedure CheckWarehouse()
var
Location2: Record Location;
WhseSetup: Record "Warehouse Setup";
ShowDialog: Option " ",Message,Error;
DialogText: Text[100];
begin
GetLocation("Location Code");
if "Location Code" = '' then begin
.
.
.
NEW CODE:
local procedure CheckWarehouse()
var
Location2: Record Location;
WhseSetup: Record "Warehouse Setup";
ShowDialog: Option " ",Message,Error;
DialogText: Text[100];
IsHandled: Boolean
begin
   IsHandled := false;
   OnBeforeGetLocation_CheckWarehouse(Rec, IsHandled);

   if IsHandled then
     exit;

    GetLocation("Location Code");
    if "Location Code" = '' then begin
      .
      .
      .

Thanks in advance!

Availability update: We will publish a fix for this issue in the next update for release 22.
Build ID to track: 56846.


Issues in A-Frame 4.0

Using https://github.com/aframevr/aframe/blob/master/dist/aframe-master.js build
in A-Frame Extras this line is now deprecated
isMobile = AFRAME.utils.isMobile();

Should be
isMobile = AFRAME.utils.device.isMobile();

In addition something else broke but I wasn't able to trace the callstack to somewhere useful in Extras.

The second issue with the bad stack trace seems to be an A-Frame 4.0 issue where "shadow" was not in an element's initialComponents during
            initialComponents[attr.name] = utils.extendDeep(
              initialComponents[attr.name], Component.parse(attr.value || {}));

Perhaps A-Frame can have this fixed before release.
Although fixing this in A-Frame still shows no shadows.

The first issue (device check) can be resolved via #109

@mflux do you have a demo with shadows working correctly? There have always been some issues, but definitely something weird happening in v0.4.0.
<a-entity shadow-light="intensity: 0.4" position="3 10 -10" distance="50"></a-entity>

^With this syntax, el.object3D comes out undefined, so that part feels like an A-Frame bug. Guessing that's the stack trace you mention?

Original issue is now resolved; tracking shadows in PR to aframe core: https://github.com/aframevr/aframe/pull/2350


Start this abandoned project again?

I mean, if such an undertaking wanted to be done I don't see a bad reason why not.
But a new roadmap would have to be created and such.

If can get an IDE that consistently provided good component development features such as a good live-preview option (react-component-preview or atom-react-preview) and had good i18n/accessibility/testability features (i.e. storybook with addons type equiv), and could hook/integrate/import (with same preview/testability) external components (like callme's material-ui), those three items alone would be awesome to help get junior and senior react developers greatly speed up iterations/productivity.

Dev is taking place at https://github.com/reactide-community/reactide/tree/dev.
Contributions are welcome and we need programmers.

@simonhochrein good to know :)

I created a project that aims to be a great react IDE. Give it a look there!
https://github.com/eveningkid/reacto

Love the support and integrity of the community. Glad to say that we are officially launching (finally) on Tuesday 8/13


'module' object has no attribute 'relu' in keras and tensorflow

my keras is not built upon theano but tensorflow, for the testing , I am running a mnist_mlp.py, it outputs the error :
File "/usr/local/lib/python2.7/dist-packages/keras/activations.py", line 20, in relu
return T.nnet.relu(x)
AttributeError: 'module' object has no attribute 'relu
how to solve this issue?

Update Theano to the Github / master branch.

@fchollet I am now switching the tensorflow for keras, why should I update theano ??


Support Shared S3 Bucket for K8up Backups

Context
AWS has hard limit on the number of S3 buckets one can create within an account (1000). Lagoon sets the backup bucket name on a project level (baas-${project}) and offloads the credentials and bucket creation to K8up on the Kubernetes cluster. With this approach a cluster can not contain over 1000 projects without configuring custom backup locations on a project level.
Idea
K8up uses Restic under the hood which supports multiple Restic repositories within the same S3 bucket using different paths. This can be leveraged by introducing an (opt-in) option to configure a shared S3 bucket on a Lagoon Remote (~K8s cluster) level.
Rough Example
Old:
# S3 bucket name supplied to K8up
baas-project-a
baas-project-c

New:
# Config for Lagoon Remote
baasSharedBucketName: cluter-x-shared-bucket

# S3 bucket name supplied to K8up
cluter-x-shared-bucket/baas-project-a
cluter-x-shared-bucket/baas-project-c

---
apiVersion: backup.appuio.ch/v1alpha1
kind: Schedule
spec:
  backend:
    s3:
      bucket: cluter-x-shared-bucket/baas-project-a
[...]

Additional Information
AFAIK Lagoon Core needs to the know the full bucket name to start a restore. Otherwise it might be possible to implement this only within Lagoon Remote (https://github.com/uselagoon/build-deploy-tool)

https://github.com/uselagoon/build-deploy-tool/pull/219 and https://github.com/uselagoon/lagoon/pull/3481 for initial support of this.
Details will be in #3481


Offline: Remove downloaded area and view details

Description
This PR adds 2 features

Remove downloaded files for a preplanned map area

By swiping the list row to the left, a delete button is revealed. Once tapped, the directory of the preplanned map area is removed from local disk
If an area is currently open but is removed, the selectedMap binding will be set to nil so the online web map is used instead

View the metadata of a preplanned map area

Tapping on the list row will reveal the metadata view, similar to App Store listing
Currently it get all the metadata from the downloaded files. In the next on-demand workflow, some metadata will be serialized when the area is downloaded

Forgot to add test, will mark as ready for review once it is added.

Ready for review.

Thanks for approving! I was hoping #867 can get reviewed first and merged into this branch. Then I'll merge this PR.


Validate and document all params that could be passed to ::consul

The documentation on what params we could pass is kinda lacking. I think we should document all of the params (most are missing right now) and perhaps update the readme as well.
Also, while doing this we need to ensure these params are properly validated, that is also lacking, only a few are being validated.
I can work on this but if someone else wants to feel free and let me know if I can help :+1:

This was solved by @tdevelioglu in #278


Need more documentation Google Play

Need add to README steps of configuration of google play like

add com.google.android.play:core
Enffort REAL DEVICE with SAME ACCOUNT EMAIL
Have one app on google play with same name of yours and same account
Enable Internal app sharing on the google play
add Testers email in internal testing
call function installUpdate on status 11 of progress

Those are mostly generic instructions about setting up in-app-updates using play core services, and there are plenty of tutorials and instructions on the web.
The purpose of this library is only to expose that functionality to react-native apps (and not teach developers how to use the play core framework).
That being said, those extra instructions on our Readme would be more than welcome and would probably help developers further down the line, so feel free to open a PR if you feel like contributing.
Even better, we even could provide external documentation urls - probably from google docs or stack overflow- (so that we don't re-invent the wheel with yet another tutorial of ours - and that way it won't get outdated as play core docs change).
Both of the above would be perfectly fine.

Hi, I am interested in adding this functionality to my app but am having several difficulties. Could someone help me to correctly configure the library and use it in different cases, especially android. Thanks

I've followed the steps and finally while debugging using the link from internal app sharing, its redirected to playstore with my app opened but Install button is missing in it! My app is supported only in US. I'm trying from a different country. Could that be the reason? Kindly clarify, Thanks.

@divyasri93 I'm afraid I don't have an answer to that.
Your question is a generic android in-app-updates question and would be better answered in stackoverflow.


Summoner needs to not call db every time it checks.

Fixed waiting next commit.

https://github.com/Civcraft/PrisonPearl/pull/174

Fixed


Octant loading forever if not accessed from localhost (OCTANT_LISTENER_ADDR)

I wanted to run octant on my Kubernetes cluster and access the web ui from my dev laptop.
I set export OCTANT_LISTENER_ADDR="<IP_ADDRESS>:8000", run octant (output looks fine) and open my browser at http://$my_cluster_ip:8000.
Octant starts loading html and css, but does not show any data. It appears to be due to the URL /api/v1/content/overview/namespace/default/ returning a 403 Forbiden.
Note that it works fine if accessed from localhost: from my dev laptop http://<IP_ADDRESS>:8000 with ssh forward ssh -L 8000:<IP_ADDRESS>:8000 $my_cluster_ip.

+1

I am still hitting this with v0.6.0 :(

I am still hitting this with v0.6.0 :(

Same here.

Have you tried setting OCTANT_ACCEPTED_HOSTS to what ever the request host IP address is? This environment variable was added in 0.6

Ah. That works now. My bad. Sorry. Great work !

I opened a new issue related to this, if you start Octant listening on <IP_ADDRESS> is should allow all hosts. See #199

OCTANT_ACCEPTED_HOSTS

Thanks!

Same issue when running on headless linux.
OCTANT_ACCEPTED_HOSTS
Where is the env located please?


find_each with a custom select needs the primary key

Fixes: Primary key not included in the custom select clause
Add basic test of #getAssociators and #getAssociatedVmdbObjs
https://bugzilla.redhat.com/show_bug.cgi?id=1281890

@roliveri @h-kataria Please review.  The test is really simplistic but recreates the error reported in the bug @h-kataria opened.  Please let me know if this fixes it.
@roliveri You can clean up this test to make it more correct in terms of cim values after merge, I didn't want to lose the opportunity to fix this bug and add a missing test.
Thanks @matthewd for pointing out the obvious solution

@jrafanie tested in UI, tissue i was encountering while accessing Host summary screen is fixed with this PR. This can be merged if @roliveri is good with changes.


Unable to build projects after updating to 1.46.0 when our repo is using sparse-checkouts

Problem
Since updating to 1.46.0, for some reason we can't build our application if a git clone is using sparse checkouts.
Steps
c:\projects>cargo init foo

c:\projects>cd foo\

c:\projects\foo>git init                                                                                Initialized empty Git repository in C:/projects/foo/.git/

c:\projects\foo>mkdir bar

c:\projects\foo>touch bar/test.txt

c:\projects\foo>echo fn main() { () } > build.rs

c:\projects\foo>vim build.rs

c:\projects\foo>ls
bar  build.rs  Cargo.toml  src

c:\projects\foo>cargo run
   Compiling foo v0.1.0 (C:\projects\foo)
    Finished dev [unoptimized + debuginfo] target(s) in 1.31s
     Running `target\x86_64-pc-windows-msvc\debug\foo.exe`
Hello, world!

c:\projects\foo>git sparse-checkout init --cone

c:\projects\foo>git sparse-checkout add src

c:\projects\foo>cargo run
error: failed to determine package fingerprint for build script for foo v0.1.0 (C:\projects\foo)

Caused by:
  failed to determine the most recently modified file in c:\projects\foo

Caused by:
  failed to determine list of files in c:\projects\foo

Caused by:
  did not expect repo at c:/projects/foo/.git/ to be bare

c:\projects\foo>

Possible Solution(s)
I have no idea. Sorry!
Notes
Output of cargo version: cargo 1.46.0 (149022b1d 2020-07-17)
As far as I can tell this really breaks things in a solid way. Just disabling sparse-checkout after this isn't enough to recover.

Ah, if you edit .git\config and remove:
[extensions]                                                                                worktreeConfig = true

Then you'll be able to build again.

Posted https://github.com/libgit2/libgit2/pull/5656 to start the ball rolling to fix this.

Could we also change cargo so that it doesn't fail if it cannot understand the git repo?  It doesn't matter if the repo is completely borked; as long as there is a valid Cargo.toml, cargo should be able to run the build.


Need help in establishing VNC with SIkuliX or SikuliX2?

Hi RaiMan,
Thanks for your blog. It's really nice.
I need to connect to linux machine through Real VNC and run my sikuli scripts with Java API. Please help me to get APi location. Checked this SikuliX Java API docs http://nightly.sikuli.de/docs/index.html . But i dont see any classes related to VNC. If SikuliX still needs implimentation then help atleast in Sikuli old version. Thanks in advance.
Thanks

only available in version 1.1.1 (version 2 not yet useable)
look
http://sikulix-2014.readthedocs.io/en/latest/screen.html#connecting-to-a-vnc-server-vncscreen

Thank you for quick reply...


testing pr-preview with surge

Hey @yubathom,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: e76cddb0-d0cf-11e9-97e2-99a13ad28605


[NOID] Does some CI maintenance

Fixes spotless check
Fixes deprecated node actions
Makes archived test list name depend on the JDK (otherwise test results get overridden depending on whether it's JDK 17 or 21 that finishes first)
Reformats some files

Closing as this is old and was never merged and the CI now looks quite different :)


Ability to confirm storage of metadata via staging card component

Feature extending #12 and related to #54. Currently, the workflow confirmation happens through giving written permission in a chat message. Another path for providing confirmation is through the staging card component.

Completed via 59fcf770ccf53a5e2f9edfea90695c66cff9537d


Internal References Test

This is still WIP. Just sharing to further discuss.

curious as to what the Pcp.PrimIndex.DumpToDotGraph output looks like for the shader prims here... I'll try to scratch out some time to try it

curious as to what the Pcp.PrimIndex.DumpToDotGraph output looks like for the shader prims here... I'll try to scratch out some time to try it

@chrizzFTD , @noWookies --  might be cool to inspect this dataset in Grill? 👍🏼 https://github.com/thegrill/grill

curious as to what the Pcp.PrimIndex.DumpToDotGraph output looks like for the shader prims here... I'll try to scratch out some time to try it

@chrizzFTD , @noWookies -- might be cool to inspect this dataset in Grill? 👍🏼 https://github.com/thegrill/grill

here's the output from Grill--

it confirms that the Prefab hierarchy on this side of the external reference is not in the composition graph for Bolt_01, because it's the Prefab on the other side of the external reference that is in the composition graph for Bolt_01.

@mati-nvidia What's the current state of this one?

I haven't had a chance to pick this back up yet, but I think all that's left to do is add some explanation based on Aaron's debugging.
I was going to add an example using specializes or inherits, but maybe that's out of scope for this asset and just a short explanation will suffice. It could link to another specializes/inherits asset in the future.


PostCSS "autoprefixer", incorrect statement

https://github.com/readium/readium-desktop/blob/3e79dccb5757fc70f86931cd6b7bd7a8436c8343/src/renderer/assets/styles/publication.css#L179-L181
=>
        WARNING in ./src/renderer/assets/styles/publication.css
(./node_modules/css-loader/dist/cjs.js??ref--8-1!
./node_modules/postcss-loader/src!
./src/renderer/assets/styles/publication.css)
        Module Warning (from ./node_modules/postcss-loader/src/index.js):
        Warning

        (181:9) Second Autoprefixer control comment was ignored.
Autoprefixer applies control comment to whole block, not to next rules.

Instead, should be:
/* autoprefixer: ignore next */
See: https://github.com/postcss/autoprefixer/issues/776
Documentation: https://github.com/postcss/autoprefixer#control-comments

Hotfix (no PR) via https://github.com/readium/readium-desktop/commit/dc23718ed6e9e7ccbe69f7790e63b7b21669f63c


Refactor bma status update

When syncset or clustersync are not found, set started to false

/assign  @TheRealHaoLiu
/hold still need e2e test for this


fix: apollo context headers in http requests

Headers such has x-hasura-role were not making it into the apollo requests.

Hello @jovermier,
Thanks for your PR!
As far as I understand your problem, it has been likely solved by #387 and #388.
Plus the Apollo link were set already in this line.
I'm therefore closing this PR for now. If the latest release does not solve your problem, please open an issue with some insights on how to reproduce it.
Thanks!


Revert "Added Breakout, Tic-tac-toe, Pokemon generator and Candy crush projects"

Reverts ZeroOctave/ZeroOctave-Javascript-Projects#204

Reason for revert
@Adit0507 You didn't have to make a new index.html file for the website
Just you need to add your code snippet in the existing file of website

Oh so the PR won't get merged then ?
I will take care of this from the next time


Script Analyzer Warning

We should include the warning rule-set from the Script Analyzer. I've been sloppy with some of my work. Adding the warning rule-set should keep our standards up.
Git:> Invoke-ScriptAnalyzer -Path .\PSGitLab\ -Recurse | group Rulename | Select-Object Name, count | ft *
Name                                           Count
----                                           -----
PSUseDeclaredVarsMoreThanAssignments               5
PSUseShouldProcessForStateChangingFunctions       10
PSAvoidUsingConvertToSecureStringWithPlainText     1
PSPossibleIncorrectComparisonWithNull              2
PSUseSingularNouns                                 1
PSAvoidDefaultValueForMandatoryParameter           1
PSAvoidUsingUserNameAndPassWordParams              2
PSAvoidUsingPlainTextForPassword                   2

Some of these should be easy to fix. Others might be design choices that we should suppress.

I like that!

Current snapshot.
Invoke-ScriptAnalyzer -Path .\PSGitLab\ -Recurse | group Rulename | Select-Object Name, count
| ft *

Name                                           Count
----                                           -----
PSAvoidUsingCmdletAliases                          1
PSUseDeclaredVarsMoreThanAssignments               7
PSAvoidUsingConvertToSecureStringWithPlainText     2
PSUseShouldProcessForStateChangingFunctions       22
PSPossibleIncorrectComparisonWithNull              3
PSUseOutputTypeCorrectly                           4
PSAvoidUsingWriteHost                              2
PSAvoidDefaultValueForMandatoryParameter           1
PSAvoidUsingPlainTextForPassword                   2
PSAvoidUsingUserNameAndPassWordParams              2

This is so outdated.


Respect CC/CXX/CFLAGS/CXXFLAGS values

Hi,
please consider most of the changes in https://github.com/gentoo/sci/blob/master/sci-biology/stringtie/files/Makefile.patch . Except the first 3 lines which should be more general:
BAM_INC = -I/usr/include/bam
BAM_LIB =  # or -L/some/path
BAM_LIBS = -lbam

To explain, Gentoo Linux installs old samtools-0.x series headers in a separate location (and the library under a different name), to allow simultaneous installation with never samtools-1.x. Otherwise I believe the patch can be accepted. Other software packagers will appreciate you do not ignore their environment settings.

No -- I respectfully disagree. The samtools-0.x code included here actually differs from any "official" samtools-0.x distribution, as I fixed and/or back-ported some patches from the newer 1.x releases of the library. It's really a private, customized copy of samtools 0.x code and should not be installed globally (system-wide). Also, it's meant to be just statically linked during the build process into the stringtie binary so there is really no reason for a system-wide installation anyway.
Also, as opposed to my other projects (e.g. gffread, gffcompare etc.) , stringtie has its own copy of the gclib "code library" (again, not a "proper" object library) and as such it is totally self-contained and built in place as is. These private instances of gclib or samtools-0.x should not be "installed" system wide.
Back to samtools: I do plan to switch to the official htslib (samtools-1.x) distribution in the near future, which would indeed then allow setting BAM_* to the system-wide installation.  But until then, sorry..

Still, please try to repect user's environemnt settings in you Makefile. Please reopen until that happens. Gentoo/Debian/Bioconda/etc., all are wasting time on fixing your Makefiles. Thank you.

Although I disagree with this attitude (as I believe that this kind of software development does not have to be tied to some particular packaging requirements), I am very willing to cooperate, within reasonable limits. The instructions for building this software, as provided here and on the official site, work just fine for anyone trying to build this software from source -- never had any complaints about it, with the source package being self-contained as it is. So I could argue that "fixing" the Makefile is not really an issue here, and I certainly did not intend for anyone to "waste time on fixing" the Makefile -- just because it does not conform to some particular third-party packaging requirements..
However I do agree with adjusting the Makefile as to make it easier for such packaging methods, as long as such adjustments do not alter the current, simple and straight forward build instructions for this software.

Thank you for your efforts. I admit I evidently forgot to check for current version but nevertheless I hope the patches I made are clear in intent. I think you can find similar in Debian repositories too.

Regarding the Makefile adjustments, it seems that statements like CXX ?= g++ fail when CXX is set to an empty string -- though I agree that is very unlikely for that to ever be the case.. but it might get slightly less unlikely for stuff like CXXFLAGS and LDFLAGS in some wacky environments (?).
So is it OK with you (in terms of potential portability issues) if I change that kind of assignment to a conditional instead? Like this:
CXX   := $(if $(CXX),$(CXX),g++)

Works fine for me for the main stringtie directory, thank you.
Something similar needs to be done for ./samtools-0.1.18 too. Currently Gentoo uses https://packages.gentoo.org/packages/sci-biology/samtools/files/samtools-0.1.20-buildsystem.patch for the 0.1.20 sources.


Publish to Maven Central

I discovered your project when searching for an alternative to MaryTTS and found that it mostly works as described. Perhaps others working on the JVM would find it useful as well. Do you have any plans to publish on Maven Central somewhere in the near future?

Thank you @breandan. Yes, actually I have those plans, but I must admit that I haven't got round to it yet. I put it on my agenda for 2023 ;-) I keep this request open until it is done.

the voice of microsoft zira is good but we cant download it in wav fie, if anyone can solve then please do message


Fix: Removed unwanted files + updated .gitignore

Fixes #54
Describe the changes you have made in this PR - Removed unwanted files and folders from the repository and updated gitignore file to include more needless files from uploading.

already fixed by author

Yes, you fixed it after I made this PR so the changes were not seen by me. You may keep the changed .gitignore file in this commit though @Erarshad. It will prevent any future occurrences of such errors :)


match used in assembly is a reserved keyword.

Ref: https://github.com/Vectorized/solady/blob/54ea1543a229b88b44ccb6ec5ea570135811a7d9/src/utils/LibZip.sol#L49
While using LibZip in a Hardhat project and testing coverage using npx hardhat coverage the compilation errors out.

Turns out match is a reserved keyword https://docs.soliditylang.org/en/latest/units-and-global-variables.html#reserved-keywords.
Changing match to anything else makes it work.
solidity-coverage: v0.8.6
solidity: 0.8.23

@anudit Pushed a new version of Solady 0.0.167.

Thanks @Vectorized @atarpara ! At 23% savings on compressed calldata.

@anudit you can also try cdCompress() function might be you get more gas saving on decompression.

I heard cdCompress + flzCompress can synergize on some kinds of data.

@Vectorized @atarpara  Some quick numbers on compressing Groth16 Proofs with some extra calldata for omnid.io.

Method
Calldata Savings (Single - Multiple proofs)
Gas Overhead

cdCompress & cdDecompress
7-23%
39k - 77k

flzCompress & flzDecompress
0-22%
10.5k - 21k

flzCompress(cdCompress()) & cdDecompress(flzDecompress())
0-25%
41k - 81k

cdCompress(flzCompress()) & flzDecompress(cdDecompress())
0-22%
50k - 97k

flzCompress & flzDecompress seems to work the best for this usecase.