Update some sheets to 0.7.9

This PR

Simplifies Application, FormApplication, and BaseEntitySheet a bit and fixes a couple of small errors
Updates ItemSheet to 0.7.9
Update ActorSheet to 0.7.9

Fixes #53
Fixes #60

@kmoschcau are you OK with going ahead and merging this?

I will need a bit to look through this. But I will take a look today.


Error after installing as a library: #error DECNUMDIGITS must be defined to be >= DECQUAD_Pmax

I installed ion-c as a library from the latest commit, using the following steps (on Arch Linux):
git clone https://github.com/amzn/ion-c.git
cd ion-c
./build-release.sh
cd build/release
make
sudo make install

These steps all completed without any issues. However, when I went to use the ion-c library in a project, I got the following error during compilation:
[1/2] building build/obj/main.o...
FAILED: build/obj/main.o
gcc -c  -I./IonTest/app IonTest/app/main.c -o build/obj/main.o
In file included from /usr/local/include/ionc/ion.h:27,
                 from IonTest/app/main.c:26:
/usr/local/include/ionc/ion_decimal.h:45:6: error: #error DECNUMDIGITS must be defined to be >= DECQUAD_Pmax
   45 |     #error DECNUMDIGITS must be defined to be >= DECQUAD_Pmax
      |      ^~~~~
ninja: build stopped: subcommand failed.

Here is my main.c. As you can see, not really doing anything yet. Seems to be an issue with just the include:
/* ========================================================================== */
/* PRIVATE INCLUDES                                                           */
/* ========================================================================== */

/* system */
#include <stdio.h>
#include <stdlib.h>
#include <ionc/ion.h>

/* project */
#include "main.h"

/* ========================================================================== */
/* PRIVATE MACROS, DEFINES                                                    */
/* ========================================================================== */

#define ION_OK(x) if (x) { printf("Error: %s\n", ion_error_to_str(x)); return x; }

/* ========================================================================== */
/* GLOBAL VARIABLES                                                           */
/* ========================================================================== */

/* ========================================================================== */
/* PRIVATE TYPEDEFS, ENUMS, etc.                                              */
/* ========================================================================== */

/* ========================================================================== */
/* PRIVATE VARIABLES                                                          */
/* ========================================================================== */

char fbuf[10000];
const char * fpath = "support/data.ion";

/* ========================================================================== */
/* PRIVATE FUNCTION PROTOTYPES                                                */
/* ========================================================================== */

int rd_file_to_buf ( const char * path, char * output_buffer, unsigned long max_len );

/* ========================================================================== */
/* EXTERNAL (API) FUNCTION DEFINITIONS                                        */
/* ========================================================================== */

/**
 * @brief  The application entry point.
 * @retval int
 */
int main ( void )
{
    hREADER reader;
    ION_READER_OPTIONS options;

}

I don't see anything about needing to manually define this anywhere in the examples or install scripts, so I assume it's just an issue with the latest build. Thanks in advance for any fixes or pointers

Manually defining DECNUMDIGITS to be 34 ended up working, but I didn't actually see this item in the root CMakeLists.txt until a few days ago:
# NOTE: DECNUMDIGITS must be set across all compilation units to at least DECQUAD_Pmax (34), so that the value is
# guaranteed to be consistent between ionc and decNumber. This is required for conversions between decQuad and
# decNumber. This is NOT the limit on decimal precision; ION_DECIMAL can handle arbitrarily large precision.
add_definitions(-DDECNUMDIGITS=34)
message(STATUS "Setting DECNUMBER max digits to 34")

I had been using the built static library in combination with the installed library headers, hence the error when I tried to further compile.


refactor Refactor pipeline execution

Proposed changes
Unify prepare and open in Operator.

run buildall

run buildall

run buildall


SyntaxError: 'return' outside of function

Describe the bug
After regenerating package-lock started getting this error
> graphql-codegen --config codegen.yml

  ✔ Parse configuration
  ❯ Generate outputs
    ❯ Generate ./src/types/generated/graphql.ts
      ✔ Load GraphQL schemas
      ✖ Load GraphQL documents
        → 'return' outside of function (13:4)
        Generate

 Found 1 error

  ✖ ./src/types/generated/graphql.ts
    SyntaxError: 'return' outside of function (13:4)
        at Object._raise (/Users/path-to-project/node_modules/@babel/parser/lib/index.js:742:17)
        at Object.raiseWithData (/Users/path-to-project/node_modules/@babel/parser/lib/index.js:735:17)

To Reproduce
Steps to reproduce the behavior:
I'm using graphql-code-generator with Gatsby
overwrite: true
schema: "http://localhost:8000/___graphql"
documents:
  - ./src/**/*.{ts,tsx}
  - ./node_modules/gatsby-*/**/*.js
generates:
  ./src/types/generated/graphql.ts:
    hooks:
      afterOneFileWrite:
        - prettier --write
    plugins:
      - typescript
      - typescript-operations
config:
  namingConvention:
    enumValues: keep
  avoidOptionals: true
  immutableTypes: true
  maybeValue: T

Environment:
System:
OS: macOS Mojave 10.14
CPU: (4) x64 Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz
Shell: 5.3 - /bin/zsh
Binaries:
Node: 12.14.1 - /usr/local/bin/node
Yarn: 1.21.1 - /usr/local/bin/yarn
npm: 6.13.4 - /usr/local/bin/npm
Languages:
Python: 2.7.10 - /usr/bin/python
Browsers:
Chrome: 81.0.4044.113
Firefox: 72.0.2
Safari: 12.0
npmPackages:
gatsby: 2.20.23
@graphql-codegen/cli: 1.13.2
@graphql-codegen/introspection: 1.13.2
@graphql-codegen/typescript: 1.13.2
@graphql-codegen/typescript-operations: 1.13.2

Could you share a reproduction repo or CodeSandbox?

I'd love to, but not quite sure how to do it

l can try to run clean Gatsby project with latest gatsby and graphql-code-generator. Let's see if it results in error.

Reproduction https://github.com/smashercosmo/graphql-code-generator-issue

run npm run develop
then in another terminal npm run graphql2ts

@smashercosmo  ./src/**/*.{ts,tsx} is too wide so every single file is getting parsed to find a valid GraphQL operation, so I recommend you to narrow it down a little bit.

I removed almost all the tsx files. But I think the error is caused by gatsby files.
If I remove this line https://github.com/smashercosmo/graphql-code-generator-issue/blob/master/codegen.yml#L5 error goes away

Ok, actually replacing this line with officially recommended
- ./node_modules/gatsby*/!(node_modules)/**/*.js fixes the issue.

So we can close the issue, right?

Yes, thx


is there a trick to running the specs?

i've created a fork to try to resolve the dependency on out-of-date Faraday. however, immediately after bundle install, running the tests gives me a mess of errors.
Finished in 0.00004 seconds (files took 0.35452 seconds to load)
0 examples, 0 failures, 32 errors occurred outside of examples

i have little faith that there are humans actively monitoring/managing this software right now (as most threads, specifically those around Faraday are completely unaddressed/replied to) but thought i'd ask this question.

I am able to run tests using either rake spec (which is what's used in CI, see ref in the readme) or rspec spec/core.
There is a separate task that will run tests against a live instance of Zendesk (rake spec:live. though that requires some setup for credentials that doesn't appear to be documented here)
https://github.com/zendesk/zendesk_api_client_rb/blob/86534b5bc5a9aac974a5759a53d73f7c33bb56c7/Rakefile#L12-L21
What is the error output if you try to run tests for a single file?

so so many issues... the biggest/reddest is
An error occurred while loading ./spec/live/webhook_spec.rb.
Failure/Error: dependency 'json'

NoMethodError:
  undefined method `dependency' for ZendeskAPI::Middleware::Request::EncodeJson:Class

          dependency 'json'

try removing yr previously working Gemfile.lock [which isn't in version control] and generating from scratch

you can see what i end up with here: https://gist.github.com/rsl/6ab47ca0b8f20335a40d0009baea077f

Ah, first guess is a Ruby version issue - it looks like you're using 2.3 (which is the minimum for this project, and should likely be updated given it's pretty out-of-date) - but is incompatible with a number of gems in the lockfile you linked<EMAIL_ADDRESS>being one).
The minimum Ruby version used in CI is 2.6
https://github.com/zendesk/zendesk_api_client_rb/blob/86534b5bc5a9aac974a5759a53d73f7c33bb56c7/.github/workflows/main.yml#L16-L22
📝 I had run my earlier checks using 3.0 (on an M1 mac)

looks like it's using the system ruby not chruby for some reason. good catch. when i ran with bundle exec rspec it gets different errors but doesn't freak the heck out at least. explains some of it, right?  gotten used to not having to bundle exec everything manually in most of my projects.
glad to see there's humans around as well. any chance some of them/y'all are looking at upgrading to a modern Faraday? there's been several threads about it but zero replies. i get how OSS works and how not every request merits attention and all.

isn't the bundled with line tho a reference to the version of bundler, not Ruby?
i get
BUNDLED WITH
   2.3.20

when i bundle exec bundle install as well because
zendesk_api_client_rb on  master [$?] via 💎 ruby-3.1.2
➜ bundle --version
Bundler version 2.3.20

zendesk_api_client_rb on  master [$?] via 💎 ruby-3.1.2
➜ ruby --version
ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-darwin21]

sure thing


Running Spark on Azure

There are actually more than 2 ways of running Spark on Azure including running Spark Jobs on AKS - https://docs.microsoft.com/en-us/azure/aks/spark-job

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

ID: 71093e2a-bbff-3a79-5f16-289a3a5f6cd7
Version Independent ID: e4e9873d-0ae7-25a4-16d1-5ecac6e84b91
Content: Capture streaming events - Azure Event Hubs
Content Source: articles/event-hubs/event-hubs-capture-overview.md
Service: event-hubs
GitHub Login: @ShubhaVijayasarathy
Microsoft Alias: shvija

@kjayantmenon Thanks for the feedback and bringing this to our notice. At this time we are reviewing the feedback and will update the document as appropriate.

@kjayantmenon  Thanks for the feedback! I have assigned the issue to the content author to review further and update the document as appropriate.

I see a link to the article: https://docs.microsoft.com/en-us/azure/aks/spark-job in the Use Spark section of the article. I guess it has already been updated.
#please-close

I see a link to the article: https://docs.microsoft.com/en-us/azure/aks/spark-job in the Use Spark section of the article. I guess it has already been updated.
#please-close


Install :)

I welcome, I am a beginner in programming.
You couldn't prompt as to install application or whether there is a demo? I am engaged in internet marketing and permanently I track development, I will be able perhaps to help something.

@gwynnbleiidd
Thanks for checking out the project.  This project is the start of a tool that isn't fully developed yet.
I will be updating this project to use the latest version of MEAN.js.  Currently, this project uses MEAN.js 0.4.0, but I will be updating it to 0.4.2 and adding additional functionality.
I will add Install and Usage Instructions in the README.md when it is ready to use.


Slider Syncing not working properly

What I Did
I created three sliders below each other. On this website when you scroll down you will se a gallery of which i am talking about.
There are 3 Sliders:
1.) The dots above the gallery
2.) The gallery itself.
3.) The text-captionoverlapping the gallery
Each slider should sync with the other sliders so i used this code: (Dont mind the bottom slider not being in sync when scrolling, i will deactivate the scrolling function on this one so it doesnt matter). This will only trigger if one of the slider above are being scrolled.
    var galleryTop = new Swiper('.gallery-top', {
        spaceBetween: 0,
        slidesPerView: 3,
        // Responsive breakpoints
        breakpoints: {
            // when window width is >= 320px
            320: {
                slidesPerView: 1
            },
            // when window width is >= 480px
            480: {
                slidesPerView: 1
            },
            // when window width is >= 640px
            640: {
                slidesPerView: 2
            },
            // when window width is >= 768px
            992: {
                slidesPerView: 3
            }
        }
    });
    var galleryThumbs = new Swiper('.gallery-thumbs', {
        spaceBetween: 50,
        slidesPerView: 3,
        // Responsive breakpoints
        breakpoints: {
            // when window width is >= 320px
            320: {
                slidesPerView: 1,
                spaceBetween: 20
            },
            // when window width is >= 480px
            480: {
                slidesPerView: 1,
                spaceBetween: 30
            },
            // when window width is >= 640px
            640: {
                slidesPerView: 2,
                spaceBetween: 40
            },
            // when window width is >= 768px
            992: {
                slidesPerView: 3,
                spaceBetween: 50
            }
        }
    });
    var galleryBottom = new Swiper('.gallery-bottom', {
        spaceBetween: 50,
        slidesPerView: 3,
        // Responsive breakpoints
        breakpoints: {
            // when window width is >= 320px
            320: {
                slidesPerView: 1,
                spaceBetween: 20
            },
            // when window width is >= 480px
            480: {
                slidesPerView: 1,
                spaceBetween: 30
            },
            // when window width is >= 640px
            640: {
                slidesPerView: 2,
                spaceBetween: 40
            },
            // when window width is >= 768px
            992: {
                slidesPerView: 3,
                spaceBetween: 50
            }
        }
    });

    galleryThumbs.controller.control = [galleryBottom, galleryTop];
    galleryTop.controller.control = [galleryBottom, galleryThumbs];

Now the problem is, that when i scroll through the dots (first slider) everything looks synced. But if i scroll through the actual gallery, the Dots above and the Text-Caption below lose their alignement with the syncing and everything moves to the left until the last Element is reached.
Expected Behavior
When using .controller.control on multiple sliders they should be in sync and not misalign.
Actual Behavior
If you slide through the gallery the top and bottom slider lose their alignement.

Set controller.by = 'container' parameter (https://swiperjs.com/swiper-api#controller) on every Swiper and it should work correctly. Also not sure why you need controller here at all, as basically what you have achievable by single Swiper


stdenv/linux: remove perl enableThreading=false override from stage1

Note: this PR includes two commits; the first commit is #161925 which needs to merge with or before this one in order to not break CI.  Only the second commit is specific to this PR.
Description of changes
The comment for the line removed by this patch states that "A threaded perl build needs glibc/libpthread_nonshared.a, which is not included in bootstrapTools".  This is no longer true; libpthread_nonshared.a is now part of the bootstrap-files.
Moreover, it appears that lack of static libraries was never the reason why this hack was needed.  It was in fact needed because nuke-refs erases the rpath from libpthread.so, and unpack-bootstrap-tools.sh neglects to undo this using patchelf.  This oversight has been fixed in #161925, which makes enableThreading=false unnecessary.
The enableThreading=false attribute not only removes the -Dusethreads from the invocation of perl's Configure script, it also patches the script like this:
# We need to do this because the bootstrap doesn't have a static libpthread
sed -i 's,\(libswanted.*\)pthread,\1,g' Configure

Although this prevents the perl interpreter from linking against libpthread.so, it does not prevent the libraries bundled with the  interpreter from doing so.  Time/HiRes/HiRes.so will still try to link against libpthread.so, and is only prevented from doing so by the fact that unpack-bootstrap-tools.sh neglects to patchelf out all of the nuke-refs'd rpaths.  When all of the nuke-refs'd paths are patchelf'ed out, HiRes.so links against libpthread.so in the bootstrap tools, and the stdenv bootstrap fails:
Can't load '/nix/store/7ny8kmppjzx6kx4xr5kphjz8fqqrlsll-perl-5.34.1/lib/perl5/5.34.1/x86_64-linux/auto/Time/HiRes/HiRes.so' for module Time::HiRes: libpthread.so.0: cannot open shared object file: No such file or directory at /nix/store/7ny8kmppjzx6kx4xr5kphjz8fqqrlsll-perl-5.34.1/lib/perl5/5.34.1/XSLoader.pm line 93.
at /nix/store/7ny8kmppjzx6kx4xr5kphjz8fqqrlsll-perl-5.34.1/lib/perl5/5.34.1/x86_64-linux/Time/HiRes.pm line 94.
Compilation failed in require at lib/Autom4te/FileUtils.pm line 42.
BEGIN failed--compilation aborted at lib/Autom4te/FileUtils.pm line 42.
Compilation failed in require at bin/autom4te line 46.
BEGIN failed--compilation aborted at bin/autom4te line 46.
make[1]: *** [Makefile:2259: tests/wrapper.in] Error 2
make[1]: *** Waiting for unfinished jobs....

To reproduce the error message above, apply the last commit (only) of #161925 (64d30ac321aa7c20a3802328635f1e133a3d85f3) and build stdenv-linux.  Perl implements its own custom library loading routines for its modules, which likely do not fully implement rpath searching.  This problem was revealed during the course of writing PR #161925, which depends on this PR in order to pass CI.
Since this workaround is no longer required, let's stop patching perl's Configure script like this, and simplify the stdenv bootstrap by not customizing the perl that is built in stage1 with an enableThreading=false override.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux (in progress)
[X] mips64el-linux
[X] powerpc64le-linux

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

In general we want less files in bootstrap rather than more, but since it's there already anyway, why not use it. Is it in all bootstrap packages?

Ofborg failed CI on this PR, but passed (completely) on #161925 which includes this PR.  It might be that this PR and #161925 both need each other, rather than the dependency being unidirectional.  I will merge the two PRs into a single PR if that turns out to be the case.

In general we want less files in bootstrap rather than more,

I think you mean "packages" not "files".
Deleting some parts of a package from the bootstrap but including other parts really does not seem like a maintainability win.  Especially when it forces weird hacks like what we're currently doing to perl5's Configure script.

but since it's there already anyway, why not use it. Is it in all bootstrap packages?

It's present on all but: powerpc64, arm, and riscv.  I have personally verified that the bootstrap (including both this PR and #161925) build and work on powerpc64le and arm.  So apparently libpthread(_nonshared).a is not even needed on most platforms.
nix@moore:/tmp/bootstrap$ for A in $(grep bootstrap-tools.tar.xz /nix/nixpkgs/pkgs/stdenv/linux/bootstrap-files/*.nix | sed 's_";.*__' | sed 's_.*"__'); do echo; echo $A; curl -s $A | tar -xvJf - | grep libpthread; done

https://wdtz.org/files/wjzsj9cmdkc70f78yh072483x8656nci-stdenv-bootstrap-tools-aarch64-unknown-linux-musl/on-server/bootstrap-tools.tar.xz
./lib/libpthread.a

http://tarballs.nixos.org/stdenv-linux/aarch64/c7c997a0662bf88264db52cbc41e67884eb7a1ff/bootstrap-tools.tar.xz
./lib/libpthread-2.33.so
./lib/libpthread.so
./lib/libpthread.so.0

http://tarballs.nixos.org/stdenv-linux/armv5tel/0eb0ddc4dbe3cd5415c6b6e657538eb809fc3778/bootstrap-tools.tar.xz
./lib/libpthread-2.30.so
./lib/libpthread.so
./lib/libpthread.so.0

https://wdtz.org/files/xmz441m69qrlfdw47l2k10zf87fsya6r-stdenv-bootstrap-tools-armv6l-unknown-linux-musleabihf/on-server/bootstrap-tools.tar.xz
./lib/libpthread.a

http://tarballs.nixos.org/stdenv-linux/armv6l/0eb0ddc4dbe3cd5415c6b6e657538eb809fc3778/bootstrap-tools.tar.xz
./lib/libpthread-2.30.so
./lib/libpthread.so
./lib/libpthread.so.0

http://tarballs.nixos.org/stdenv-linux/armv7l/0eb0ddc4dbe3cd5415c6b6e657538eb809fc3778/bootstrap-tools.tar.xz
./lib/libpthread-2.30.so
./lib/libpthread.so
./lib/libpthread.so.0

http://tarballs.nixos.org/stdenv-linux/i686/c5aabb0d603e2c1ea05f5a93b3be82437f5ebf31/bootstrap-tools.tar.xz
./lib/libpthread-2.27.so
./lib/libpthread.so
./lib/libpthread.so.0
./lib/libpthread_nonshared.a

http://tarballs.nixos.org/stdenv-linux/powerpc64le/49a83445c28c4ffb8a1a90a1f68e6150ea48893b/bootstrap-tools.tar.xz
./lib/libpthread-2.33.so
./lib/libpthread.so
./lib/libpthread.so.0

http://tarballs.nixos.org/stdenv-linux/riscv64/9bd3cf0063b80428bd85a286205adab4b6ffcbd6/bootstrap-tools.tar.xz
./lib/libpthread-2.33.so
./lib/libpthread.so
./lib/libpthread.so.0

https://wdtz.org/files/gywxhjgl70sxippa0pxs0vj5qcgz1wi8-stdenv-bootstrap-tools/on-server/bootstrap-tools.tar.xz
./lib/libpthread.a

http://tarballs.nixos.org/stdenv-linux/x86_64/c5aabb0d603e2c1ea05f5a93b3be82437f5ebf31/bootstrap-tools.tar.xz
./lib/libpthread-2.27.so
./lib/libpthread.so
./lib/libpthread.so.0
./lib/libpthread_nonshared.a

Aha, yes, both #161925 and this PR require each other.  Please see the boldfaced paragraph (which I have just added) in the topmost comment.  I have also bundled #161925's commit with this PR in order to keep CI happy.

The latest push breaks the dependency cycle between this PR and #161925, so they can be evaluated independently.


[Feature] Add open latest console from output panel.

Is your feature request related to a problem? Please describe.
I'm always frustrated when I have to manually look for a Tinker console previously open.
Describe the solution you'd like
A simple button bar with three options: Open Last, Open Console (pick one), and New Console.
Describe alternatives you've considered
None
Additional context
Some quick clicks over the output box it would be cool.

Nope. I usually hook the output panel on the right or left, so having a button there saves me pressing more buttons when I’m already have one hand on the mouse.
Italo Baeza C.

El 12-10-2021, a la(s) 18:28, Roboroads @.***> escribió:

So, adding an extra button to the tinker output - should be managable.
Are you really not satisfied by the already provided options? E.g.:
Use the Tools -> Laravel Tinker -> Reopen last console
Use the Smart Action which will open thje last window if not already opened (ctrl/cmd+shift+T default).
Use the Scratches and Consoles -> Laravel Tinker Consoles under your project structure
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

👌
Italo Baeza C.

El 18-10-2021, a la(s) 21:08, Roboroads @.***> escribió:

Will be in the next release!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Clean cannot drop schema with H2 1.4.197 and newer

Gradle plugin: 5.0.7
H2: 1.4.197
gradle flywayClean will execute the statement DROP SCHEMA "<name>" and this works with H2  1.4.196. However, in the latest version it fails with Cannot drop "<name>" because "..." depends on it.
The grammar of H2 DROP SCHEMA states:

Drops a schema. The command will fail if objects in this schema exist and the RESTRICT clause is used (the default). All objects in this schema are dropped as well if the CASCADE clause is used. This command commits an open transaction in this connection.

This indicates that the correct SQL statement would be DROP SCHEMA "<name>" CASCADE.

Thanks for reporting. This was nastier than expected as H2 actually introduced a breaking change in a patch release. The DROP SCHEMA ... CASCADE syntax is the only one that works for this from 1.4.197 onward, yet it isn't supported at all in 1.4.196 and earlier. I have now added detection code to handle both versions transparently.


Free wasd key for camere movement

We are using wasd to move the camera around. We need to disable the wasd keycode binding. What do you guys think?

Fine with me. WASD are pretty commonly needed for non-camera stuff. Thanks!


Docker image creation

hi,
i'm trying to build an image.
evrything is going fine but me and my friend also facing the same issue that in vi dockerfile i'm unable to run the command apt -get or sudo apt-get.
/
could u please check where i have gone wrong.

hi pavankumar,
please remove double quotes for apt-get update in Dockerfile and in dockerfile sudo command does not work.

remove sudo


Bug: Some errors are logged without timestamp and plugin name

Describe The Bug
Some errors are logged without timestamp and plugin name
To Reproduce
Turn off RainBird controller for a while so plugin cannot connect to it
Expected behavior
Error log messages should be prefixed with timestamp and plugin name
Relevant log output
Since version 2.0 of plugin error are logged like this:
RainBird controller request failed. [Error: connect EHOSTUNREACH <IP_ADDRESS>:80]
Failed Request: [18] [ControllerDateGetRequest]
Will retry in 60 seconds
RainBird controller request failed. [Error: connect EHOSTUNREACH <IP_ADDRESS>:80]
Failed Request: [18] [ControllerDateGetRequest]
Will retry in 60 seconds
RainBird controller request failed. [Error: connect EHOSTUNREACH <IP_ADDRESS>:80]
Failed Request: [18] [ControllerDateGetRequest]
Will retry in 60 seconds
RainBird controller request failed. [Error: connect EHOSTUNREACH <IP_ADDRESS>:80]
Failed Request: [18] [ControllerDateGetRequest]
Will retry in 60 seconds
RainBird controller request failed. [Error: connect EHOSTUNREACH <IP_ADDRESS>:80]
Failed Request: [18] [ControllerDateGetRequest]
Will retry in 60 seconds

Note that timestamp and plugin name are missing

Config for homebridge-rainbird
N/A

Screenshots
No response
Device & Model
TM2
Node.js Version
v18.18.2
NPM Version
v9.8.1
Homebridge Version
v1.7.0
Homebridge Rainbird Plugin Version
v2.0.0
Homebridge Config UI X Plugin Version
v4.55.1
Operating System
Docker

@mantorok1 just released 2.0.3, which you implemented the event loggings, right? So we should be able to close this?

I believe so. Does it work ok? I haven't had a chance to test it yet


Update devops-command-center.rst

Update for: https://github.com/mattermost/mattermost-plugin-incident-collaboration/pull/495

@agarciamontoro, for the DB changes, would that be in the telemetry doc only or somewhere else?

@agarciamontoro, for the DB changes, would that be in the telemetry doc only or somewhere else?

@justinegeffen, no need to document the DB changes. I wrote that only to make the dev review easier, it's an internal change.


Feature/delete orgs

This PR adds the ability to delete orgs.  The delete-orgs command makes use of the recursive flag on the CloudController API for deleting everything under that org as well.  Currently this feature is not implemented for generated concourse pipelines.  I may add that later, although given the destructive nature of delete-orgs, perhaps it shouldn't be inserted automatically unless someone is really looking to add that job to their pipeline.
A user has the option to look at which orgs would be deleted without actually deleting them using the --peek flag.
Orgs which should not be deleted can be configured in orgs.yml under the protected_orgs key in list form.
I have added an integration test, I could use some help adding unit testing.
Note. This is my first stab at working in Go, if things look odd or questionable please feel free to point that out. :)

Thanks @Anthonyhawkins for the PR.  Added some unit tests and fixed build issue as needed to re-generate the mocks when adding additional method(s) to interface.


Revert "Update index.yaml" Helm Chart Release AKO 2.5.0

This reverts commit 28c94794e468e154b58d545ce4e00dd17d79e5f4.
All Submissions:

[X] Have you signed our CLA?
[X] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

CLOUDP-265089


Dev

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

GitHub release
v1.2.0
v1.2.0

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-alpha.1 :tada:
The release is available on:

GitHub release
v2.0.0-alpha.1
v2.0.0-alpha.1

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-alpha.2 :tada:
The release is available on:

GitHub release
v2.0.0-alpha.2
v2.0.0-alpha.2

Your semantic-release bot :package::rocket:


Plugin initialization failed, there was a failure with event subscription

I have 3 thermostats on my account.
I have followed the instructions, and I still get this error showing. (I have hidden my project code in the message below)
[homebridge-google-nest-sdm] Plugin initialization failed, there was a failure with event subscription. Did you read the readme: https://github.com/potmat/homebridge-google-nest-sdm#where-do-the-config-values-come-from StatusError: Requested project not found or user does not have access to it (project=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). Make sure to specify the unique project identifier and not the Google Cloud Console display name.
at MessageStream._onEnd (/homebridge/node_modules/homebridge-google-nest-sdm/node_modules/@google-cloud/pubsub/src/message-stream.ts:301:20)
at MessageStream._onStatus (/homebridge/node_modules/homebridge-google-nest-sdm/node_modules/@google-cloud/pubsub/src/message-stream.ts:342:12)
at ClientDuplexStreamImpl. (/homebridge/node_modules/homebridge-google-nest-sdm/node_modules/@google-cloud/pubsub/src/message-stream.ts:198:38)
at Object.onceWrapper (node:events:510:26)
at ClientDuplexStreamImpl.emit (node:events:390:28)
at Object.onReceiveStatus (/homebridge/node_modules/homebridge-google-nest-sdm/node_modules/@grpc/grpc-js/src/client.ts:675:16)
at Object.onReceiveStatus (/homebridge/node_modules/homebridge-google-nest-sdm/node_modules/@grpc/grpc-js/src/client-interceptors.ts:424:48)
at /homebridge/node_modules/homebridge-google-nest-sdm/node_modules/@grpc/grpc-js/src/call-stream.ts:323:24
at processTicksAndRejections (node:internal/process/task_queues:78:11) {
code: 5,
details: 'Requested project not found or user does not have access to it (project=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). Make sure to specify the unique project identifier and not the Google Cloud Console display name.',
metadata: Metadata { internalRepr: Map(0) {}, options: {} }

Did you try using the gcpProjectId config value?

I had this error too.
In my case it was the wrong PubSub Subscription ID.
It must look like: "projects/your-gcp-project-id/subscriptions/your-subscriptionid"
It is confusing, because there is "Pub/Sub topic id" on Device Access Console, where you create project. This is not the one you need. The one you get is from those CMD calls from the installation manual.
I also added gcpProjectId - trying to add this one is also a good idea.

That worked perfectly thank you


[Header] Drop-downs support in header

Many applications and web-sites doesn't fit in Clarity 3-level navigation model. And there are a lot of cases, when you need multi-level menu inside Header component (alone, or even when used together with subnav or side menu). For example, when you want to let users see which 2nd-level nav items can be found inside, without forcing him to navigate just to see what's inside.
Technically, I can put drop-down menu and add nav-link class to it, but it won't be properly styled.

Dropdowns work only in header actions section, which is not enough.
Stackblitz
Workaround: fix css manually.
@mixin header-nav-dropdown {
  .header-nav {
    & > .dropdown {
      $clr-header-action-caret-icon-right-position: 0.5rem;

      & > .dropdown-toggle {
        height: $clr-header-height;
        line-height: $clr-header-height;
        @include header-nav-appearance();
      }

      $dropdown-nav-text-dist: 1.5rem;
      .dropdown-toggle.nav-text {
        padding: 0 $dropdown-nav-text-dist 0
          $clr-header-nav-text-horizontal-padding;

        clr-icon[shape^='caret'] {
          right: $clr-header-nav-text-horizontal-padding;
        }
      }

      .dropdown-toggle.nav-icon {
        padding-right: 0;
        width: $clr-header-height;
      }

      // Pull the dropdown menus of all dropdowns up to compensate for the height of the header.
      .dropdown-menu {
        left: auto;
        margin-top: -0.166667rem;
        right: 0;
      }
    }
  }
}

header,
.header {
  @include header-nav-dropdown();
}

I need to dig into the history of why we don't have dropdowns, but the vertical nav is where we intend to have nested links. Adding to considerations.

The feature request here has been captured into our list and we’re going to take it into consideration as we develop Clarity Core capabilities. In an effort to clean up our backlog and focus our attention, I’m going to close this as captured in our feature requests. Please follow our development and releases to see when we release relevant components to make this possible. Future feature requests can be made in our GitHub Discussions.


Syntax coloring works locally, not on RTD

RTD; works locally:

Possible causes?
And thanks for the extension, a must-have for some uses.

https://nbsphinx.readthedocs.io/en/0.7.1/installation.html#Pygments-Lexer-for-Syntax-Highlighting

@mgeier Thanks.
For clarity: ensure IPython is included in RTD's build (via e.g. requirements.txt in .readthedocs.yml).


cudpp_testrig tridiagonal tests fail if they are non-power-of-2 equation sizes.

What steps will reproduce the problem?
run cudpp_testrig -tridiagonal

What is the expected output? What do you see instead?

Press any key to continue . . .

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 28 Jul 2011 at 4:49

Fixed, closing.  Will open a new issue for the size=128 fp64 failure...

Original comment by<EMAIL_ADDRESS>on 1 Aug 2011 at 3:02

Changed state: Verified

Yes, non-power-of-two is currently not supported. I forget to add this
to the limitation description. Can I just change all test sizes to be
power of two, and clarify this in the solver description?

Yao

Original comment by<EMAIL_ADDRESS>on 31 Jul 2011 at 6:08


hlsl: Support custom root constant layout

Temporary patch for SPIRV-Cross. I'm aiming to merge it into the master in near future but would like to test it a bit first.

Thanks! I added this commit to a patched branch so we don't have to keep resetting master directly, is that fine? We can still point spirv_cross at the branch until your changes are eventually merged upstream.
It is a bit weird that the crate could link to a invalid submodule commit (i.e. whenever we remove temporary patches and delete old branches) but I don't see any good way around that 😕

Fixing this upstream instead


[virt-controller]: consider the ParallelOutboundMigrationsPerNode when evicting VMs

Signed-off-by: Igor Bezukh<EMAIL_ADDRESS>What this PR does / why we need it:
If not considering the maximum per-source-node active migrations we can have a scenario where we reach the maximum capacity of concurrent migrations in a cluster, where most of the migrations are pending because all the migrations are from the same source node.
This can be problematic in a case where multiple drains occur at the same time, therefore evictions from different source nodes can start simultaneously, but it won't happen because the migraiton queue was occupied with VMs from the same source node.
The solution is to observe migration queue with active migrations from same source node and limit the creation of new migrations up to the ParallelOutboundMigrationsPerNode.
Which issue(s) this PR fixes
https://bugzilla.redhat.com/show_bug.cgi?id=2069098
Special notes for your reviewer:
In this PR I'm not aiming to re-factor or improve the current eviction flow, but only concentrate on the fix.
Following are the cases that need to be tested:

Release note:
Consider the ParallelOutboundMigrationsPerNode when evicting VMs

/cc @acardace @iholder-redhat Hi, can you please take a look?

Just FYI,  I tested a temporary walkaround for this issue by setting
MaxParallelMigrationsPerCluster == MaxParallelMigrationsPerOutboundNode
I hoped that when this happens we would drain all the VMs from one node at a time and then we can hit max VMs migration in parallel, unfortunately, it didn't work.
so I'm really looking forward to testing this fix.

Just FYI, I tested a temporary walkaround for this issue by setting MaxParallelMigrationsPerCluster == MaxParallelMigrationsPerOutboundNode I hoped that when this happens we would drain all the VMs from one node at a time and then we can hit max VMs migration in parallel, unfortunately, it didn't work. so I'm really looking forward to testing this fix.

Hey!
This makes sense. With the current behavior the first node that would try to evacuate would create MaxParallelMigrationsPerCluster vmim objects, therefore it would be the only one migrating (at least at the beginning). I believe @enp0s3's changes address that problem :crossed_fingers:

Thanks a lot @enp0s3! Great job!
/lgtm
@xpivarc PTAL

@xpivarc Hey. I think I addressed everything, can you PTAL?

/hold
looking at unit tests

/unhold
Addressed unit test issues

/retest-required

/retest-required

/cherry-pick release-0.58

Results are here, and they are showing 533% faster migration

Awesome job @enp0s3 and @bbenshab!


FRONTEND WITH FRAMEWORK: REACT 2.5 => React Props vs State

Contributors are required to include information about the -

What is Props?
What is State?
Where and how we use React Props and State?
React Props vs State.
and also add anything related to that React props and State.

Also make sure -

Avoid copy/paste, We will be checking.
Changes should be made inside the Frontend_Web_Development_React_Angular_Vue/ dir inside Frontend_Web_Development_React_Angular_Vue branch.
Task will be assigned on first come first serve.
Files need to be added into the Week2 folder only.
Check out Contribution Guidelines and Code Of Conduct.

/assign

/assign

@CSAURABH great work done so here I am closing this issue here


Fix gonsfx/gulp-jscs-stylish#14

This fixes #14
I went through the commit logs to reconstruct the history of the problem, before trying to fix it. Here's what I came up with:

At first only the name of a file was reported using error.filename.

This proved ambiguous with files like a/index.js and b/index.js which led to fix #1: prepending file.base to error.filename.

However the value of error.filename was changed to an absolute path in this gulp-jscs commit. Suddenly there were duplicate parts in file paths, see #11. So it was back to error.filename.

Which brings us to issue #14.

The fix I'm proposing shouldn't reintroduce any of the previous issues and is a direct analogue of the way gulp-jshint constructs CWD relative file paths.
Since this plugin is predicated on delegating the actual reporting to jshint-stylish, producing the exact same paths that gulp-jshint produces and that are expected by jshint-stylish seems to be the best approach.
Here's the output created by my fix using the example repo I set up:

I have rarely seen a pull request, which was documented this good. Thanks a lot!
Will probably bump npm version tomorrow, not on a development computer right now.

Released as 1.4.0

Awesome! Thanks for the nice compliment and thanks for the quick merge!


BUG: Wrong Answer with scipy.optimize.linprog

Describe your issue.
I am trying to solve the following dual problem:

The variables of the problem are defined as:

 Variables

# Define parameters
N = 2
M = 4
ql = 1   # an arbitrary value for ql
qu = 10  # an arbitrary value for qu
Phi = np.array([[ql-0,ql-1,ql-4,ql-5],[qu-0,qu-1,qu-4,qu-5]])
u = np.reshape(np.array([0**0.5,1**0.5,4**0.5,5**0.5]),(4,1))
w = 1.5
p = np.reshape(np.array([1/2,1/2]),(2,1))

# Vectorlize matrix Phi
Phi_vec = Phi.reshape(N*M,1,order = 'F')

# Construct matrix A by Kronecker product
A1 = np.kron(u.T,np.ones((1,N)))
A2 = np.kron(np.ones((1,M)),np.identity(N))
A3 = np.kron(np.ones((1,M)),np.ones((1,N)))
A = np.vstack([A1,A2,A3])

# Construct vector b
b = np.vstack([w,p,1])

bounds = [(0,None)] * N*M

X = list(range(N))
Y = list(range(M))

Solution using scipy.optimize.linprog

 Solution 1

# Solve the dual problem
res_d = linprog(b, A_ub = -A.transpose(), b_ub = -Phi_vec)

print("success:",res_d.success)
print("fun:",round(res_d.fun,2))
print("nu_1:",round(res_d.x[0],2))
print("mu:",np.round([res_d.x[i] for i in [1,2]],2))
print("nu_2:",round(res_d.x[3],2))

Output:
success: True
fun: 5.5
nu_1: 0.0
mu: [0.51 9.51]
nu_2: 0.49

Here, Scipy gives the wrong solution. Theoretically, dual problems' object function values are no greater than primal problems'. To guarantee our conclusion, we use CVXPY to implement

 Solution 2

# Define variable _lambda
_lambda = cp.Variable((4,1))

# Define objective function
obj_expr_d = b.transpose() @ _lambda
obj_d = cp.Minimize(obj_expr_d)

# Define constraints
constraints_d = [A.transpose() @ _lambda >= Phi_vec]

# Create the model
cvxpy_dual = cp.Problem(obj_d,constraints_d)

# Solve the dual problem
cvxpy_dual.solve()

# print the result
print("status:", cvxpy_dual.status)
print("fun:", np.round(obj_expr_d.value,2))
print("nu_1:", np.round(_lambda.value[0],2))
print("mu:", np.round([_lambda.value[1]],2), np.round([_lambda.value[2]],2))
print("nu_2:", np.round(_lambda.value[3],2))

Output:
status: optimal
fun: [[3.]]
nu_1: [-3.]
mu: [[-2.]] [[7.]]
nu_2: [5.]

Reproducing Code Example
Same as the above code snippets.

Error message
NA

SciPy/NumPy/Python version information
1.7.1 1.20.3 sys.version_info(major=3, minor=9, micro=7, releaselevel='final', serial=0)

Please check your bounds. All decision variables are non-negative by default. I see the CVXPY solution has some negative values.

Please check your bounds. All decision variables are non-negative by default. I see the CVXPY solution has some negative values.

Oh, thanks for pointing that. It fixed the problem!


Manually set hover and active backgrounds and borders for dark and light buttons

This isn't elegant at all, and is actually rather annoying for others, but it fixes a problem, so here it goes.
This PR aims to improve the color contrast on hover and active state for light and dark buttons. There's no other way I can find to do this without it being a complete rewrite of the component at this point. Placing two custom conditions in here though—based on the extremes of our color palette—seems okay though.
I'd rather go this route than #35293 because this keeps the customization in the usage of the mixin as opposed to the logic of the mixin. Ideally we could setup custom color functions like #34013, but I can only see us doing that with a rewrite of the mixin as well (which could include an optional parameter or something for specifying tint or shade.
Lastly, I don't see this needing to affect outline buttons. Those have separate issues, yes, but for the moment they have a clear enough hover state at least (though not a clear enough active one).
Definitely need some more thoughts though from @twbs/css-review :).
Closes #35293.
Fixes #34123.

@julien-deramond This was the best solution I could come up with for these button contrast issues. Not sure if you have any other ideas for what we could try :).

@julien-deramond This was the best solution I could come up with for these button contrast issues. Not sure if you have any other ideas for what we could try :).

We've got a similar approach in Boosted where we call button-variant with different parameters following the cases in order to apply the right contrasted colors.
For example in this file:
.btn-light,
.btn-secondary {
  @include button-variant($white, $black, $disabled-background: $white, $disabled-border: $gray-500, $disabled-color: $gray-500);
  &.btn-inverse {
    @include button-variant($black, $white, $white, $white, $white, $black, $primary, $primary, $black, transparent, $gray-700, $gray-700, $black);
  }
}

Our palette is reduced, strict and limited in terms of colors so we don't need shade-color nor tint-color but that's specific to Boosted. This system was introduced by @ffoodd (and has just slightly changed in order to handle buttons with dark backgrounds defined by .btn-inverse and some params) so maybe he will have more details to share on what's been experimented at the time (2 years ago apparently so maybe it'll be complicated to remember :smile: )
I do believe there's room from improvement but that seems to work pretty well at the moment.

In fact in Boosted, it didn't relate to contrasts but to how inconsistent are Orange's buttons styles 😅
I recall modifying default argument values in button-variant() to reduce the need for explicit code, but couldn't do anything else than using specific mixin call for each button style.
The way Mark handles this looks better since it duplicates less code (and might allow some simplifications in Boosted, at some point).

Note added to #34123 with an observation on a change to rounded corners when picking up on this change and applying the update to take an advantage of it.

@mdo - saw your note saying the design update was intentional and was blogged about.  See mention of the button styles changing but not the card styles to match (or decision not to match).  I did see the border colour appears to have adjusted.  Should I raise as a bug to get the right eyes on this and allow conversation (even if I'm only to be shut down... might be somewhere for others to see that it's been discussed and confirmed as intentional).  Perhaps this is all just an optical illusion for me!  😂

@fitcwill You're commenting on unrelated PRs, please try to open a new issue or find the relevant PR, which is #35979 :). The global border-radius values were updated, which both the cards and buttons use for the current and old values. I don't see the need to change anything further given this.

Ah, thanks for the tips, cheers. I see the commit you're referring to now and it's helped highlight the problem.  Will add a comment to the other PR hoping that's a better place.  Might not be worth taking further forward than that though.

Just noting that similar changes impacting the active / hover states the default values for info and warning.

theme color
v4 bg
v5 bg
v4 bg hover
v5 bg hover

warning
#ffc107
#ffc107
#e0a800
#ffcd39

info
#17a2b8
#17a2b8
#138496
#3dd5f3

As can be seen, if the button colour is light enough, then tint is used, compared with the previous approach which darkened the colour.


DNSCrypt client proxy service terminated unexpectedly. (event 7034)

This doesn't happen very often, but it happened three times in past 7 days.
SimpleDnsCrypt log doesn't show anything other than it failed to check for update, I only find things in Event Viewer, I don't see anything else logged in event viewer when DNSCrypt client proxy service terminated.
I saved events as attachment, I hope it is useful.
SimpleDnsCryptCrashed.zip

+1

+1, win7

The DNSCrypt client proxy service terminated unexpectedly.  It has done this 2 time(s).
had to manually turn on the service again for it to work or the browser cannot browse site

is there a problem with the pre-release version? eg: https://simplednscrypt.blob.core.windows.net/deploy/SimpleDnsCrypt/bin/x64/SimpleDNSCrypt_x64.zip

Seems it was dnscrypt issue https://github.com/jedisct1/dnscrypt-proxy/issues/447
trying the pre-release will let you know if i encounter it again with the pre-release thanks

FYI: Until you correct the problem, the workaround I have found is as follows...

Well it's been 3 days since i use the pre release and haven't had any "DNSCrypt client proxy service terminated unexpectedly" error yet.
will report if any issue occur thx

@TehBotolSosro 0.5.5 is equal with the current preview.
I will cose this for now.

I'm on Windows Server 2016, and this have happened two times.
I hope @TA2DF's solution works.

dnscrypt-proxy 2.0.16 is released, so you'll no longer encountering this trouble.


msal-browser popup position for dual screen

Core Library
MSAL.js v2 (@azure/msal-browser)
Wrapper Library
Not Applicable
Description
Hello,
For dual screen setup, Popup cannot be positioned with negative values which occures depending of which screen is defined as the main one.
Setup example:

In both of those case the top or left variable will need negative values to position popup at the center of the screen, but negative values are ignored by openSizedPopup function in lib/msal-browser/src/utils/PopupUtils.ts, here is the snippet involved:
if (!top || top < 0 || top > winHeight) {
    logger.verbose("Default popup window top position used. Window top not configured or invalid.");
    top = Math.max(0, ((winHeight / 2) - (BrowserConstants.POPUP_HEIGHT / 2)) + winTop);
}

if (!left || left < 0 || left > winWidth) {
    logger.verbose("Default popup window left position used. Window left not configured or invalid.");
    left = Math.max(0, ((winWidth / 2) - (BrowserConstants.POPUP_WIDTH / 2)) + winLeft);
}

I makes it impossible for the application to position the popup at will using the popupWindowAttributes.popupPosition attribute, resulting the popup to be automatically positioned to the 0 axis depending of the screen setup.
Are there reasons I am unaware of to restrict negative values for popup positioning?
Thank you
Source
External (Customer)

@waxisien could you provide a screenshot showing where you want the popup to appear so we can better understand the request? Thanks.

Case 1: when the bottom screen is the main display, the popup is not centered but aligned with the bottom border:

Case 2: when the top screen is the main display, the popup is centered like it should be:

The same behavior can be observed when screen are displayed horizontally.
Please note that in those examples the popup is automatically positioned by msal, but the first case doesn't work either when I set manually the popup position using the popupWindowAttributes param.
Thanks

@jo-arroyo can you check if this is addressed already?

Hi!
Im also experience this issue. Are there any known workarounds or any plan to fix the issue?


[SPARK-34229][SQL] Avro should read decimal values with the file schema

What changes were proposed in this pull request?
This PR aims to fix Avro data source to use the decimal precision and scale of file schema.
Why are the changes needed?
The decimal value should be interpreted with its original precision and scale. Otherwise, it returns incorrect result like the following.
scala> sql("SELECT 3.14 a").write.format("avro").save("/tmp/avro")
scala> spark.read.schema("a DECIMAL(4, 3)").format("avro").load("/tmp/avro").show
+-----+
|    a|
+-----+
|0.314|
+-----+

Does this PR introduce any user-facing change?
Yes, this will return correct result.
How was this patch tested?
Pass the CI with the newly added test case.

cc @gengliangwang , @cloud-fan , @HyukjinKwon

cc @gengliangwang , @cloud-fan , @HyukjinKwon

Thank you, @imback82 . I updated the PR according to your advice. Thanks!

Thank you, @imback82 . I updated the PR according to your advice. Thanks!

Test build #134460 has started for PR 31329 at commit 21019cb.

Test build #134460 has started for PR 31329 at commit 21019cb.

Test build #134460 has finished for PR 31329 at commit 21019cb.

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

Test build #134460 has finished for PR 31329 at commit 21019cb.

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

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

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

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

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

Test build #134464 has started for PR 31329 at commit d474f35.

Test build #134464 has started for PR 31329 at commit d474f35.

Test build #134464 has finished for PR 31329 at commit d474f35.

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

Test build #134464 has finished for PR 31329 at commit d474f35.

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

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

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

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

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

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

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

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

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

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

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

Merged to master, branch-3.1, branch-3.0, and branch-2.4.

Merged to master, branch-3.1, branch-3.0, and branch-2.4.

Thank you so much, @HyukjinKwon !

Thank you so much, @HyukjinKwon !


[BUG] Update Access mode should be disabled if volume is already bound to a PV/PVC

Describe the bug
Update Access mode should be disabled if volume is already bound to a PV/PVC.
To Reproduce
Steps to reproduce the behavior:

Deploy longhorn in a K8s cluster.
Create a volume with ReadWriteOnce using longhorn UI.
Create a PV and PVC for the volume.
Update the access mode to ReadWriteMany.

Expected behavior
The Update access mode should be disabled if the volume is attached to a PV and PVC.

Environment:

Longhorn version: Longhorn-master 12/13/2020
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: RKE

Verified with Longhorn v1.1.0-rc2
Validation - Pass
The Access mode is disabled when the volume is bound to PV or PV/PVC both.
Validated with volume created, restored volume and DR volume.


Add script to dump and remove attachments?

Feature description
Currently, dumper fails on images with large attachments, likely because the contents are parsed into the DOM via minidom which creates very large documents that can become larger than the available memory, despite the file sizes being quite small.
Feature motivation
I have a series of notes from college that are gigabytes in size, which is almost entirely in attachments. However, I also have a few files of ~80MB which are mostly attachments also failing. I could export smaller notes, however, having a Python script (to handle files larger than a certain size) or similar to process each of the attachments would be very useful, and export the modified ENEX files (as well as adding support for other formats) and the attachments would be very helpful, and would solve many of the issues of large files.
If there's any interest, I'd be more than happy to provide it, under any license desired (including public domain, so you can do whatever you wish). Currently I only have access to Evernote ENEX files, but I could also use the test cases above to add support for other note file types.
I've got a simple version of the script here, and it reduces a 7MB file to ~150KB, while keeping everything but the resources present, and can then be processed by dumper.
Current issues with the script:

Assumes base64 encoding of attachments.
Only handles filename and contents.
XML output currently doesn't preserve CDATA sections, which should be trivial to implement using text processing rather than dumping the tree.
Only supports Evernote ENEX files.

I'm working on fixing the 1). and 3). currently, and would be more than willing to implement 4). if desired.

Update: I've since processed ENEX files up to ~3.4GB in size, and it's worked without hitch, and then used dumper to then export the notes from the resulting files. This includes large attachments, including over 100MB in size.


Adding support to null-safety

I need this to run tests on my project, but I haven't done anything according to the project standard, you can close it if you think it's necessary, but it could be useful for anyone who has the same problem.

Hi @acacioveit, thanks for your contribution! Unfortunately, the --no-sound-null-safety flag has been removed with Dart 3 release (more info here https://github.com/dart-lang/sdk/issues/50348). Thus, we can't support it in patrol_cli.
I'll close this PR for the sake of housekeeping, people can still find closed PRs using Github search.

Yes, in my current project I can't update to the latest versions of Flutter/Dart, that's why I needed to make this adjustment, then I decided to share it here, not a big deal, don't worry


IE fixes for IE8 and 7

I don't see the correlation with failed specs - good to merge
going to check specs after that


fix: respect GitHub rate limiting

Previously, the client would repeatedly attempt requests until getting actually rate limited by GitHub.
We saw a failure in the quality gate run for another PR that changed the GitHub provider: https://github.com/anchore/vunnel/actions/runs/6693756704/job/18185629045?pr=376#step:4:1530
GitHub's docs mention that failing to abide by these limits can result in escalated responses: https://docs.github.com/en/rest/guides/best-practices-for-using-the-rest-api?ref=retool-blog.ghost.io&apiVersion=2022-11-28#dealing-with-rate-limits

Sorry for the label spam - I was experimenting with the changelog generator.


Can connect via psql but not via knex

I have a database test that I've created locally. I can connect to this database via the psql command-line utility without problems:
$ createdb test
$ psql test
psql (9.4.6)
Type "help" for help.

test=> \q

However, I'm not able to connect to this same database via knex:
$ node
> require('knex')({client:'pg', debug: true, pool: {max: 1, min: 1},  connection: {host: 'localhost', database: 'test'}})
Knex:Error Pool2 - error: Ident authentication failed for user "<my username>"

Searching around for errors similar to this has yielded no results. I don't have any postgres-specific environment variables set that might be overriding the password. In addition, explicitly passing in password: '', user: '' to the connection object has no effect. No matter what I do, I'm getting authentication errors. What could be happening here?

@adnelson With psql you are using unix socket to connect DB and with knex you are trying to use TCP connection...
You should encounter the same problem if you try to connect the same way to your DB with psql -U <myusername> -d test -h localhost
Searching with error message http://lmgtfy.com/?q=Ident+authentication+failed+for+user
And click the first stackoverflow link: http://stackoverflow.com/questions/2942485/psql-fatal-ident-authentication-failed-for-user-postgres
This might also be helpful to get your postgres setup to allow remote connections http://www.cyberciti.biz/tips/postgres-allow-remote-access-tcp-connection.html
Let me know if there are more problems with this.


Fix experimental model command in mesheryctl

Notes for Reviewers
This PR fixes #9470
Signed commits

[x] Yes, I signed my commits.

Hey @LakshyaSatpal, just a heads up that there are some lint check failures on this PR. If you have a moment, could you please take a look and see if you can address them?


Integrate secure pairing with example app and device controller

Problem
Missing secure pairing integration
Summary of Changes
Integrated secure pairing with accessory and device controller.
fixes #611
fixes #612

Do I understand correctly that this commit takes away the ability to test examples other than the echo-server as they don't implement rendezvous over BLE yet and the manual key exchange has been dropped?
I wonder if it would be possible to keep the manual key exchange path in the controller, possibly guarded by a compile-time switch, to support testing examples which are not ready yet. Perhaps even if all examples switch to a proper rendezvous method the possibility to test a connection with fixed encryption keys could be useful (?).

Do I understand correctly that this commit takes away the ability to test examples other than the echo-server as they don't implement rendezvous over BLE yet and the manual key exchange has been dropped?
I wonder if it would be possible to keep the manual key exchange path in the controller, possibly guarded by a compile-time switch, to support testing examples which are not ready yet. Perhaps even if all examples switch to a proper rendezvous method the possibility to test a connection with fixed encryption keys could be useful (?).

@Damian-Nordic we can add provisions to have a test secret in the devices that do not yet have Rendezvous integrated. Here's how I am doing it in a test in the current PR (https://github.com/project-chip/connectedhomeip/pull/2230/files?file-filters[]=#diff-6827ec482c0a42a089c6e57eb3e087acR109). I prefer this over ManualKeyExchange, as the latter is not an actual API that we want to support in CHIP. The longer we keep ManualKeyExchange in the tree, more stuff will get built on top of it.
Do we have any test controller applications that are checked in CHIP repo that can interact with test device examples besides echo-server? I can help migrate the test and example application over to deriving security keys from test secret.

LGTM seems to also complain about non virtual destructors.

LGTM seems to also complain about non virtual destructors.

That should be fixed in the current set of commits. It complained about it earlier yesterday.

@Damian-Nordic we can add provisions to have a test secret in the devices that do not yet have Rendezvous integrated. Here's how I am doing it in a test in the current PR (https://github.com/project-chip/connectedhomeip/pull/2230/files?file-filters[]=#diff-6827ec482c0a42a089c6e57eb3e087acR109). I prefer this over ManualKeyExchange, as the latter is not an actual API that we want to support in CHIP. The longer we keep ManualKeyExchange in the tree, more stuff will get built on top of it.
Do we have any test controller applications that are checked in CHIP repo that can interact with test device examples besides echo-server? I can help migrate the test and example application over to deriving security keys from test secret.

@pan-apple we were using specifically on/off commands of chip-tool to control the door-lock example for nrfconnect platform and I realized that after merging this PR ChipDeviceController::ConnectDevice method used by commands other than echo-ble will always fail due to uninitialized secure session. I actually tested that.
I'm fine with the shared secret approach and I can implement it in our example, but I wonder if we can have the possibility to bypass rendezvous in chip-tool or we should write another test controller.

@Damian-Nordic we can add provisions to have a test secret in the devices that do not yet have Rendezvous integrated. Here's how I am doing it in a test in the current PR (https://github.com/project-chip/connectedhomeip/pull/2230/files?file-filters[]=#diff-6827ec482c0a42a089c6e57eb3e087acR109). I prefer this over ManualKeyExchange, as the latter is not an actual API that we want to support in CHIP. The longer we keep ManualKeyExchange in the tree, more stuff will get built on top of it.
Do we have any test controller applications that are checked in CHIP repo that can interact with test device examples besides echo-server? I can help migrate the test and example application over to deriving security keys from test secret.

@pan-apple we were using specifically on/off commands of chip-tool to control the door-lock example for nrfconnect platform and I realized that after merging this PR ChipDeviceController::ConnectDevice method used by commands other than echo-ble will always fail due to uninitialized secure session. I actually tested that.
I'm fine with the shared secret approach and I can implement it in our example, but I wonder if we can have the possibility to bypass rendezvous in chip-tool or we should write another test controller.

@Damian-Nordic , yes, as an immediate fix, the rendezvous would be bypassed in the chip-tool. We can add a temporary API to CHIPDeviceController that can initialize the security session from a test secret. Once we have support for Rendezvous in chip-tool, this API can be removed.

Not sure if I should press the big green button here or not. I believe https://github.com/project-chip/connectedhomeip/commit/32f990344a7b47cb0e5c21b2a78dced1b94ec787 uses the deleted function, but we do not have a CI test for it.
Are we ok to have a temporary breakage?

Not sure if I should press the big green button here or not. I believe 32f9903 uses the deleted function, but we do not have a CI test for it.
Are we ok to have a temporary breakage?

I am adding support for using test secret for key derivation here (https://github.com/pan-apple/connectedhomeip/pull/1). I can amend that PR to take care of the EFR32 scenario as well. The other PR is in my fork as of right now. I'll submit it for review here once this merges.


How to enable BackTest and Optimization through the Strategy Analyzer?

Greetings,
I noticed logic built into AlgoSystemsBase.cs to handle Backtest execution.
When attached directly as a strategy to a chart the included sample generates an expected large number of historical trades.
Strategy Analyzer executes Backtest and Optimization processes on the sample but produces no trades.
Any tips on how to get this sample working well with the Strategy Analyzer?
Thanks!

hi
thanks for the info - i would have to test this to replicate as far as i was aware it would work the same if it cold work on a chart etc

so if i'm right this was due to error corrected in your modification OnStateChange, So we can close this one?

Hi Tom, Thanks for the reply.
No I still have not been able to get any results to appear via the Strategy Analyzer via BackTest or Optimization modes.
On the upside I am testing out a few possible suggested changes to reduce rejected change orders on fast moving tick charts

ok perfect i am going to deal with this one now

"On the upside I am testing out a few possible suggested changes to reduce rejected change orders on fast moving tick charts"
Sounds interesting.
I did add an Unsafe mode -- to cut out all the workflow - but it lacks a post trade - context check to make sure the entry's and exits are in balance etc

ok latest version fixed an erroneous property IsReplay OnBarUpdate - which tested for replay account
also optimised code execution for backtest and also for Realtime in release notes etc


[ENHANCEMENT] Missing ServiceAccount for TaskList

Describe the use case:
Configuring ServiceAccounts for TLS based configuration between all pods using AppMesh
Describe the enhancement/feature:
All deployments, except Tasklist, support defining ServiceAccounts. We like to have a consistent way to configure the ServiceAccount for Tasklist as well.
(see here https://github.com/camunda/camunda-platform-helm/tree/main/charts/camunda-platform/charts/tasklist/templates)
Desired outcome and acceptance tests:
ServiceAccount of Tasklist can be configured in the same way like all other components (eg. Operate).

The fix is merged, and it will be part of the next release.

The fix is merged, and it will be part of the next release.

thanks a lot! :)


[BUG] Unable to initialize .opendistro_security index with remote-store feature enabled.

Describe the bug
I am trying to set-up a secure multi-node cluster with remote-store enabled but it is failing to bring up the OS process while trying to create the .opendistro_security index. I am getting following error:
[2023-06-19T18:42:05,625][INFO ][o.o.p.PluginsService     ] [ip-10-0-5-117.ec2.internal] PluginService:onIndexModule index:[.opendistro_security/X10sm8tySnq5AndLv_ICiA]
[2023-06-19T18:42:05,635][WARN ][o.o.i.c.IndicesClusterStateService] [ip-10-0-5-117.ec2.internal] [.opendistro_security][0] marking and sending shard failed due to [failed to create shard]
java.lang.IllegalArgumentException: Repository should be created before creating index with remote_store enabled setting
        at org.opensearch.index.store.RemoteSegmentStoreDirectoryFactory.newDirectory(RemoteSegmentStoreDirectoryFactory.java:62) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.index.IndexService.createShard(IndexService.java:475) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.indices.IndicesService.createShard(IndicesService.java:951) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.indices.IndicesService.createShard(IndicesService.java:210) ~[opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.indices.cluster.IndicesClusterStateService.createShard(IndicesClusterStateService.java:662) [opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.indices.cluster.IndicesClusterStateService.createOrUpdateShards(IndicesClusterStateService.java:639) [opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.indices.cluster.IndicesClusterStateService.applyClusterState(IndicesClusterStateService.java:296) [opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.cluster.service.ClusterApplierService.callClusterStateAppliers(ClusterApplierService.java:606) [opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.cluster.service.ClusterApplierService.callClusterStateAppliers(ClusterApplierService.java:593) [opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.cluster.service.ClusterApplierService.applyChanges(ClusterApplierService.java:561) [opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.cluster.service.ClusterApplierService.runTask(ClusterApplierService.java:484) [opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.cluster.service.ClusterApplierService$UpdateTask.run(ClusterApplierService.java:186) [opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:747) [opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.common.util.concurrent.PrioritizedOpenSearchThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedOpenSearchThreadPoolExecutor.java:282) [opensearch-2.9.0.jar:2.9.0]
        at org.opensearch.common.util.concurrent.PrioritizedOpenSearchThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedOpenSearchThreadPoolExecutor.java:245) [opensearch-2.9.0.jar:2.9.0]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
        at java.lang.Thread.run(Thread.java:833) [?:?]
Caused by: org.opensearch.repositories.RepositoryMissingException: [opensearch-infra-stack-test-us-east-1-secure-repo] missing

As per my understanding all the system indices are supposed to have DOCUMENT type replication setting so not sure why the security index is being registered as remote-store index.
Below is my opensearch.yml setting:
cluster.initial_cluster_manager_nodes:
  - seed
discovery.seed_providers: ec2
network.host: <IP_ADDRESS>
discovery.ec2.tag.Name: >-
  opensearch-infra-stack-test-us-east-1-secure/seedNodeAsg,opensearch-infra-stack-test-us-east-1-secure/managerNodeAsg

node.roles:
  - data
  - ingest

cluster.remote_store.repository: opensearch-infra-stack-test-us-east-1-secure-repo
opensearch.experimental.feature.remote_store.enabled: 'true'
cluster.remote_store.enabled: 'true'
opensearch.experimental.feature.segment_replication_experimental.enabled: 'true'
cluster.indices.replication.strategy: SEGMENT

######## Start OpenSearch Security Demo Configuration ########
# WARNING: revise all the lines below before you go into production
plugins.security.ssl.transport.pemcert_filepath: esnode.pem
plugins.security.ssl.transport.pemkey_filepath: esnode-key.pem
plugins.security.ssl.transport.pemtrustedcas_filepath: root-ca.pem
plugins.security.ssl.transport.enforce_hostname_verification: false
plugins.security.ssl.http.enabled: true
plugins.security.ssl.http.pemcert_filepath: esnode.pem
plugins.security.ssl.http.pemkey_filepath: esnode-key.pem
plugins.security.ssl.http.pemtrustedcas_filepath: root-ca.pem
plugins.security.allow_unsafe_democertificates: true
plugins.security.allow_default_init_securityindex: true
plugins.security.authcz.admin_dn:
  - CN=kirk,OU=client,O=client,L=test, C=de

plugins.security.audit.type: internal_opensearch
plugins.security.enable_snapshot_restore_privilege: true
plugins.security.check_snapshot_restore_write_privileges: true
plugins.security.restapi.roles_enabled: ["all_access", "security_rest_api_access"]
plugins.security.system_indices.enabled: true
plugins.security.system_indices.indices: [".plugins-ml-model-group", ".plugins-ml-model", ".plugins-ml-task", ".opendistro-alerting-config", ".opendistro-alerting-alert*", ".opendistro-anomaly-results*", ".opendistro-anomaly-detector*", ".opendistro-anomaly-checkpoints", ".opendistro-anomaly-detection-state", ".opendistro-reports-*", ".opensearch-notifications-*", ".opensearch-notebooks", ".opensearch-observability", ".ql-datasources", ".opendistro-asynchronous-search-response*", ".replication-metadata-store", ".opensearch-knn-models"]
node.max_local_storage_nodes: 3

To Reproduce
Steps to reproduce the behavior:

Create a remote-store enabled multi-node cluster with security.

Expected behavior
The cluster should come up and the system indices should be created without any issue.
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

The remote-store is working as expected with security disabled.

If we create a cluster by disabling remote store settings, what is the replication type of .opendistro_security index? DOCUMENT or SEGMENT?

In that case the security plugin is not initialized and the index is not created. @sachinpkale

I created a 2.9 cluster with only segment replication enabled and the .opendistro_security index replication type is DOCUMENT.
sngri@3c06304c0d45 opensearch-cluster-cdk % curl -X GET "https://opens-clust-1KXORCC7F0TCF-10d58231468f105e.elb.us-east-1.amazonaws.com/.opendistro_security/_settings?include_defaults&pretty" -ku admin:admin
{
  ".opendistro_security" : {
    "settings" : {
      "index" : {
        "replication" : {
          "type" : "DOCUMENT"
        },

@sachinpkale

There are three things going on here.

The remote store paths are implicitly overwriting the replication strategy, leading to unexpected behavior - https://github.com/opensearch-project/OpenSearch/issues/8162.
If a system index is configured to use remote storage, it breaks because the index is wired up before a remote store repository (stacktrace above).
Today system indices are not supported with segment replication.  Given remote store can only be enabled with segrep, they would also not be supported for remote storage.

I think we need to fix all three of these bugs for GA of remote storage.  I would expect system indices to also be backed up.

@sachinpkale We would like to remove the restriction on system indices for segrep.  I spent some time trying to solve 2 above and wire up the repository before the index.  The registration for a repo is only done via API and not through yml settings.  Given we want to use the default remote store repo, we can't require plugins to register their own repositories before attempting index creation.  We either need to provide the ability to set config for a repository through yml and do it before plugins are registered or default to node-node until the repo is registered, but that itself is also not currently supported.

Created an opensearch cluster using cdk and it is able to create system index with remote enabled settings -
➜  opensearch-cluster-cdk git:(main) curl https://<LB-URL>/\*/_settings\?pretty
{
  ".opensearch-observability" : {
    "settings" : {
      "index" : {
        "replication" : {
          "type" : "SEGMENT"
        },
        "number_of_shards" : "1",
        "remote_store" : {
          "translog" : {
            "repository" : "opensearch-infra-stack-remote-store-secure-repo"
          },
          "enabled" : "true",
          "segment" : {
            "repository" : "opensearch-infra-stack-remote-store-secure-repo"
          }
        },
        "auto_expand_replicas" : "0-2",
        "provided_name" : ".opensearch-observability",
        "creation_date" : "1694071416491",
        "number_of_replicas" : "2",
        "uuid" : "Q3HHJu0iSaunjsFFSf0HyA",
        "version" : {
          "created" : "136317827"
        }
      }
    }
  },
  ".plugins-ml-config" : {
    "settings" : {
      "index" : {
        "replication" : {
          "type" : "SEGMENT"
        },
        "number_of_shards" : "1",
        "remote_store" : {
          "translog" : {
            "repository" : "opensearch-infra-stack-remote-store-secure-repo"
          },
          "enabled" : "true",
          "segment" : {
            "repository" : "opensearch-infra-stack-remote-store-secure-repo"
          }
        },
        "provided_name" : ".plugins-ml-config",
        "creation_date" : "1694071425987",
        "number_of_replicas" : "1",
        "uuid" : "zUpf0dqHS3yvnJHOLRjlXA",
        "version" : {
          "created" : "136317827"
        }
      }
    }
  },
  "security-auditlog-2023.09.07" : {
    "settings" : {
      "index" : {
        "replication" : {
          "type" : "SEGMENT"
        },
        "number_of_shards" : "1",
        "remote_store" : {
          "translog" : {
            "repository" : "opensearch-infra-stack-remote-store-secure-repo"
          },
          "enabled" : "true",
          "segment" : {
            "repository" : "opensearch-infra-stack-remote-store-secure-repo"
          }
        },
        "provided_name" : "security-auditlog-2023.09.07",
        "creation_date" : "1694071930597",
        "number_of_replicas" : "1",
        "uuid" : "0sRUbxmjTi-_tKaG3y9-YQ",
        "version" : {
          "created" : "136317827"
        }
      }
    }
  },
  ".opendistro_security" : {
    "settings" : {
      "index" : {
        "replication" : {
          "type" : "SEGMENT"
        },
        "number_of_shards" : "1",
        "remote_store" : {
          "translog" : {
            "repository" : "opensearch-infra-stack-remote-store-secure-repo"
          },
          "enabled" : "true",
          "segment" : {
            "repository" : "opensearch-infra-stack-remote-store-secure-repo"
          }
        },
        "auto_expand_replicas" : "0-all",
        "provided_name" : ".opendistro_security",
        "creation_date" : "1694071416075",
        "number_of_replicas" : "2",
        "uuid" : "KLz_n9vqTJuq_HYPbDeyWg",
        "version" : {
          "created" : "136317827"
        }
      }
    }
  }
}


Hookify logic

We want as much logic in hooks as possible to avoid complex logic in ui components.

already hookified most logic


Why does the expression (20/50) evaluate to 0?

Why is the expression (20/50) evaluated to 0? Can you set globally how much to return when evaluating the expression?

I think that depends on the type of variables. If you are using integers the result is also an integer. If you are using doubles or floats or decimals the results will have more precision. This is the standard C# behavior, and in DynamicExpresso we try to mimic it. But we have a settings to force all numbers to be something else. See https://github.com/dynamicexpresso/DynamicExpresso?tab=readme-ov-file#default-number-type

I think that depends on the type of variables. If you are using integers the result is also an integer. If you are using doubles or floats or decimals the results will have more precision. This is the standard C# behavior, and in DynamicExpresso we try to mimic it. But we have a settings to force all numbers to be something else. See https://github.com/dynamicexpresso/DynamicExpresso?tab=readme-ov-file#default-number-type

Thanks! The SetDefaultNumberType method solved my problem, just set SetDefaultNumberType (DefaultNumberType.Decimal) and it's ok!


Retraining on floydhub.com is not available

Can you provide corpus? We cannot retraining this model on floydhub.com in readme. Thanks a lot.

@cnlinxi sorry for your inconvenience. I thought using floydhub would be sustainable but it seems very costly in a long run. So, I've decided to cancel my subscription, hence losing the datasets there.
I'll get back to you regarding the corpus. Would you mind sharing a bit on what you plan to do with the code?

Sorry for the delay. I hope to use this model to segment Thai words, and hope to improve it. I hope to provide a good Thai text regularization method.

@heytitle Sorry for reply too late. I hope to use this model to segment Thai words, and hope to improve it. I hope to provide a good Thai text regularization method.

@cnlinxi sorry again for my response. You can find the data at https://codeforthailand.s3-ap-southeast-1.amazonaws.com/attacut-related/data.zip
Please unzip and make sure the root directory is at ./data. The content of the archive contains

Only the first two are relevant for training; sampling-0 means all the dateset, while sampling-10 means only 10 files are used. You can use sampling-10 for quick training.
Before running the training command below, make sure that you have the ./artifacts directory.
python ./scripts/train.py --model-name seq_sy_ch_conv_concat \
 --model-params "embc:8|embs:8|conv:8|l1:6|do:0.1" \
 --data-dir ./data/best-syllable-crf-and-character-seq-feature-sampling-0  \
 --output-dir ./artifacts/model-xx  \
 --epoch 2 \
 --batch-size 1024 \
 --lr 0.001 \
 --lr-schedule "step:5|gamma:0.5"

@heytitle thank you very much. I have trained this model on BEST 2010. Great work:)

https://codeforthailand.s3-ap-southeast-1.amazonaws.com/attacut-related/data.zip

Is word split by "~" in "best-syllable-tokenized" dataset?

https://codeforthailand.s3-ap-southeast-1.amazonaws.com/attacut-related/data.zip

Is word split by "~" in "best-syllable-tokenized" dataset?


Distribution Gallery: Beta Alternative Parametrization [WIP]

Description
See discussion in #493

The logs are complaining about unknown directive jupyter-execute. Is it installed and "activated" in conf.py?

Library that provides the directive: https://jupyter-sphinx.readthedocs.io/en/latest/

The logs are complaining about unknown directive jupyter-execute. Is it installed and "activated" in conf.py?

This was the problem. Now it works. Thank you very much!

The PDF tabs and the CDFs tabs should be synced, so changing one, changes the other. Or we should have a single plot with two subplots on top if each other. One for the PDF and another for the CDF. If we have the two subplots the titles should indicate if the plot is the PDF or CDF.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 82.24%. Comparing base (8f36b1e) to head (88eebea).
Report is 38 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #529      +/-   ##
==========================================
- Coverage   82.36%   82.24%   -0.13%
==========================================
  Files          96      101       +5
  Lines        7895     8016     +121
==========================================
+ Hits         6503     6593      +90
- Misses       1392     1423      +31

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


reporting / disputing claim REP

Fix existing reporting and disputing claiming fees.
background:

flash is a utility used to push time on our fake time geth node
to run it yarn docker:geth:pop this will bring up a geth node that we can move time. We need to move time in reporting so we don't have to wait weeks.
yarn flash run push-timestamp -c 10w pushes time 10 weeks

When a user disputes a market outcome and wins, they win the other reporters REP. They can claim that REP after the market's dispute period is over.
There needs to be a notification in Account Summary that tells the user they can claim. There is an existing claim-reporting-fees
augur/packages/augur-ui/src/modules/reporting/actions/claim-reporting-fees.ts
in V2 the user only wins REP, we'll need to remove all verbiage of fees.
NOTIFICATION_TYPES.reportOnMarkets this is the notification type in notification-state we want to get working.
working with disputing
a market's reporting starts time has to have passed in order for the market to be reportable. endTime is the property on the market info object that is in state state.marketInfos

initial report (look on the reporting page)
disputing (look on the disputing page)

you can dispute the initial reporter then push time 2 weeks then the user can claim report winnings. They get 40% ROI (return on investment) of the REP they won (not full 50%, this is new in V2) so if the initial report staked 0.3497 and you dispute with 0.6994. You'll end up getting back your original 0.6994 + 0.27976 = 0.97916. if my math is correct.
other stuff
users reporting history is on loginAccount state as “reporting” property.
there is a new selector that processes the user's reporting data. Look for usages of loginAccount.reporting.
REP value in notification is the sum of all totalAmount for disputing, participationTokens and reporting
these values are attoREP and need to be converted to display value. Use BigNumber math to sum and formatAttoRep method in format-number.
design: https://www.figma.com/file/bZh7tOiLm6Ls9Hl4RL6qMC5X/Augur-Redesign?node-id=7110%3A283094
V1 design (fees are in DAI in V2)

Some conventions
we use Formatted to indicated the number/string has been formatted
we use BigNumber properties to identify properties that have been converted to BigNumber.
use timestampInMilliseconds if the timestamp has been converted to milliseconds, our timestamps are from blockchain node and in seconds.
we are trying to be come consistent with variable naming, just FYI.

this has been fixed. Gas estimates will be handled in another ticket once we figure out gnosis wallet fees and be able to toggle user to/from rep/dai for paying transactions fees


Revert "feat: 🎸 ignore result of job runner if job has been canceled …

…(#1188)"
This reverts commit a85b08697399a06dc2a98539dd4b9679cf6da8be.
For some reason the queue stopped picking jobs after the deploy that included this change in queue.py

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Update vanity url management

As a developer, I want to be able to easily manipulate the url of an app I am working on so that I can make it more user friendly and map to business architecture.
This ticket is to use the lambda@edge functionality to improve url management for the DR, A&R, DUP (should we break this into separate tickets?)
Acceptance Criteria:
Notes:

@marklise when you get a chance can you add some additional content to this ticket around how we can use lambda edge to improve vanity urls?

@danieltruong will break this up into additional cards for DR (API url improvement), A&R, DUP


Identifiers validation failed for dataset Biodiversidad fitoplanctónica de cenotes: Patrones espaciales y temporales

Identifier validation failed for the dataset Biodiversidad fitoplanctónica de cenotes: Patrones espaciales y temporales:

Crawler attempt: 307
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 1009
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 1009 total records; 1009 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3740330/step

New IDs sample:

Old IDs sample:

007d8ff94c003fb75d7f32059f27e9e3
009a719be02927832ffa54fb3bea5bce
00d6bd1c1ac1b399ee65de8192635511
015701ae1cb5e4df58f1238bef817eff
019349d0380a0ae09dd839e25cd2f1e7
01d22dfed9987fda053197c9fe1f5f54
023f7dcb6b5e86055715c13cfbcf917a
02cbba8a04f5e16804b52b1f01da98e9
03882a519a11c9380ab7e5a8ac4c9060
0421592d23f5e66cd82a371618cb2294

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Biodiversidad fitoplanctónica de cenotes: Patrones espaciales y temporales : https://doi.org/10.15468/mxjojj.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Biodiversidad fitoplanctónica de cenotes: Patrones espaciales y temporales:

Crawler attempt: 310
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 1009
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 1009 total records; 1009 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741812/step

New IDs sample:

Old IDs sample:

007d8ff94c003fb75d7f32059f27e9e3
009a719be02927832ffa54fb3bea5bce
00d6bd1c1ac1b399ee65de8192635511
015701ae1cb5e4df58f1238bef817eff
019349d0380a0ae09dd839e25cd2f1e7
01d22dfed9987fda053197c9fe1f5f54
023f7dcb6b5e86055715c13cfbcf917a
02cbba8a04f5e16804b52b1f01da98e9
03882a519a11c9380ab7e5a8ac4c9060
0421592d23f5e66cd82a371618cb2294

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Biodiversidad fitoplanctónica de cenotes: Patrones espaciales y temporales : https://doi.org/10.15468/mxjojj.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


Timeseries example does NOT address the core of prediction

URL(s) with the issue:
https://www.tensorflow.org/tutorials/structured_data/time_series
Please provide a link to the documentation entry, for example:
https://www.tensorflow.org/tutorials/structured_data/time_series
Description of issue (what needs changing):
I get the sequential data and the methods to get to next step or multi steps. But with the Time being converted to frequency, why do we have to have again equidistant events record. That beats the purpose of ANY timed series problem. In the example given, converting the time to frequency does not affect the model much because the series is Timed, not any value for the period. The period between records is equal. I still don't see this as a clear example of Time series. You can call this example as Series prediction, not Timed series prediction.

There seems to be some errors too,  In the below function, why do we have Shuffle to TRUE ? I thought timeseries is sequential ?

def make_dataset(self, data):
  data = np.array(data, dtype=np.float32)
  ds = tf.keras.preprocessing.timeseries_dataset_from_array(
      data=data,
      targets=None,
      sequence_length=self.total_window_size,
      sequence_stride=1,
      shuffle=True,
      batch_size=32,)
  ds = ds.map(self.split_window)
  return ds

2 ) And also, how is the Validation done ? Do we have to window slide the validation data too ?
3)  Do we really need window slide for LSTM ? Seems to be over fitting for a lots of examples.
4)  If some input fields have categorical data (not the output), there is no way this will perform better especially if we use embedding
5) With this function timeseries_dataset_from_array, it is hard to do any embedding layer.
6) Timeseries involves large datasets, unfortunately using BatchNormalization is very confusing, blame it on the documentation.
7) How do we do feature engineered layer (such as mixed with embedding layer) in the first input with 3D tensor.

And also i don't understand this one in the code in make dataset function
   ```data = np.array(data, dtype=np.float32)```
    ds = tf.keras.preprocessing.timeseries_dataset_from_array(
        data=data,
        targets=None,
        sequence_length=self.total_window_size,
        sequence_stride=sequence_stride,
        shuffle=shuffle,
        batch_size=batch_size, )

If we have to preserve the dtype from dataframe until we feed this to feature engineered layer, how do we do it ?

There seems to be some errors too,  In the below function, why do we have Shuffle to TRUE ? I thought timeseries is sequential ?

def make_dataset(self, data):
  data = np.array(data, dtype=np.float32)
  ds = tf.keras.preprocessing.timeseries_dataset_from_array(
      data=data,
      targets=None,
      sequence_length=self.total_window_size,
      sequence_stride=1,
      shuffle=True,
      batch_size=32,)
  ds = ds.map(self.split_window)
  return ds

2 ) And also, how do the Validation done ? Do we have to window slide the validation data too ?
3)  Do we really need window slide for LSTM ? Seems to be over fitting for a lots of examples.
4)  If some input fields have categorical data (not the output), there is no way this will perform better especially if we use embedding
5) Timeseries involves large datasets, unfortunately using BatchNormalization is very confusing, blame it on the documentation.

There seems to be some errors too,  In the below function, why do we have Shuffle to TRUE ? I thought timeseries is sequential ?

def make_dataset(self, data):
  data = np.array(data, dtype=np.float32)
  ds = tf.keras.preprocessing.timeseries_dataset_from_array(
      data=data,
      targets=None,
      sequence_length=self.total_window_size,
      sequence_stride=1,
      shuffle=True,
      batch_size=32,)
  ds = ds.map(self.split_window)
  return ds

2 ) And also, how do the Validation done ? Do we have to window slide the validation data too ?
3)  Do we really need window slide for LSTM ? Seems to be over fitting for a lots of examples.
4)  If some input fields have categorical data (not the output), there is no way this will perform better especially if we use embedding
5) Timeseries involves large datasets, unfortunately using BatchNormalization is very confusing, blame it on the documentation.

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.