unknown directive "OpenIDCProvider" in nginx Docker container

Attempting to install the new version 3.2.1 ngx_openidc_module and the version 1.4.3 liboauth2 module in an official nginx Docker container (1.20.1) based on Debian buster. Installation of ngx_openidc gives a warning
/var/lib/dpkg/info/libnginx-mod-openidc.postinst: 22: cd: can't cd to /etc/nginx/modules-enabled
but successfully installs (there is no modules-enabled directory in the Docker version of nginx). However after updating the default.conf file similar to the example on the README and running nginx -t gives the following error:
2021/07/15 21:17:06 [emerg] 496#496: unknown directive "OpenIDCProvider" in /etc/nginx/conf.d/default.conf:13 nginx: [emerg] unknown directive "OpenIDCProvider" in /etc/nginx/conf.d/default.conf:13 nginx: configuration file /etc/nginx/nginx.conf test failed

that's most probably because the module does not load since it was built for the stock version of NGINX on Buster which is 1.14.2

The nginx for Docker maintainers are basing their image on "buster-slim", which as you point out defaults to 1.14. However, they are constantly updating their version of nginx, still using buster by re-compiling the newer code, installing the new version and then publishing a new image.
So, I tried the following:
Pull nginx:1.20.0 docker image, start and enter container
Install various build tools
Download and build from source prerequisites for building nginx (pcre, zlib, ssl)
Download and build from source nginx version 1.20.0
Install prerequisites for liboauth2 (libcjose0 libhiredis0.14 libjansson4 libmemcached11 libmemcachedutil2 libcurl4)
Build from source liboauth2, using --with-nginx flag pointing to source of nginx 1.20.0 build. I see it creates artifacts liboauth2.so.0.0.0 and liboauth2_nginx.so.0.0.0.
Build from source ngx_openidc_module with --with-nginx flag point to source of nginx 1.20.0. I see it creates artifacts ngx_openidc_module.so.
Package all artifacts up and copy into a fresh nginx:1.20.0 container with ngx_openidc_module in /etc/nginx/modules and liboauth2 modules in /usr/lib/x86_64-linux-gnu/.
Test nginx with nginx -t.
I get the same output unknown "OpenIDCProvider" directive. Am I missing something in building from source on a newer version of nginx? I sorted out all the missing dependencies and nginx header files so I don't see anything wrong from that standpoint.
BTW, I tried to test installing your released libraries on an nginx 1.14.2 Docker image, but the version of libhiredis in that version is 0.13 and the dependency is libhiredis0.14. So, at this point, there doesn't seem a way to use official nginx images. However, the 'Ubuntu Focal' packages work, although nginx in Focal is 1.18.

there's only so much platforms I can maintain a build for so that's it; when compiling yourself you'll also need to make sure that you use the same compilation flags, as recorded in nginx -V

I tried re-compiling nginx with the options from the default Docker image and added the missing load_module directive in ngninx.conf since, for whatever reason there is no modules-enabled directory on this image. Unfortunately that didn't work either, so using the official nginx Docker image is a non-starter and I'll have to create one from scratch using the appropriate distro packages.
Thanks for taking a look.


Webhooks for events

Webhooks for certain events:

[ ] before pool starts - sync and async option (sync should block starting pool until webhook responds)
[ ] after pool stopped

Closing in favor of #91


bootjdk download from API intermittently failing

23:30:55  + ./build-farm/make-adopt-build-farm.sh
23:30:55  BUILD TYPE:
23:30:55  VERSION: jdk15u
23:30:55  ARCHITECTURE s390x
23:30:55  VARIANT: hotspot
23:30:55  OS: linux
23:30:55  SCM_REF:
23:30:55  Detecting boot jdk for: jdk15u
23:30:55  Found build version: 15
23:30:55  Required boot JDK version: 14
23:30:55  Downloading GA release of boot JDK version 14...
23:30:55
23:30:55  gzip: stdin: unexpected end of file
23:30:55  tar: Child returned status 1
23:30:55  tar: Error is not recoverable: exiting now
23:30:55  Downloading GA release of boot JDK version 14 failed.
23:30:55  Attempting to download EA release of boot JDK version 14 ...
23:30:56
23:30:56  gzip: stdin: unexpected end of file
23:30:56  tar: Child returned status 1
23:30:56  tar: Error is not recoverable: exiting now

https://ci.adoptopenjdk.net/view/Failing Builds/job/build-scripts/job/jobs/job/jdk15u/job/jdk15u-linux-s390x-hotspot/156/console

These all failed at the start of jdk15 build pipeline, at exactly 23:30, could it be too many requests all at the same time?

These all failed at the start of jdk15 build pipeline, at exactly 23:30, could it be too many requests all at the same time?

Can you give the list of machines (or at least the jobs) that this is happening on?

Can you give the list of machines (or at least the jobs) that this is happening on?

https://ci.adoptopenjdk.net/view/Failing Builds/job/build-scripts/job/jobs/job/jdk15u/job/jdk15u-aix-ppc64-hotspot/165/console
https://ci.adoptopenjdk.net/view/Failing Builds/job/build-scripts/job/jobs/job/jdk15u/job/jdk15u-linux-s390x-hotspot/156/console
https://ci.adoptopenjdk.net/view/Failing Builds/job/build-scripts/job/jobs/job/jdk15u/job/jdk15u-mac-x64-openj9-macosXL/163/console

https://ci.adoptopenjdk.net/view/Failing Builds/job/build-scripts/job/jobs/job/jdk15u/job/jdk15u-aix-ppc64-hotspot/165/console
https://ci.adoptopenjdk.net/view/Failing Builds/job/build-scripts/job/jobs/job/jdk15u/job/jdk15u-linux-s390x-hotspot/156/console
https://ci.adoptopenjdk.net/view/Failing Builds/job/build-scripts/job/jobs/job/jdk15u/job/jdk15u-mac-x64-openj9-macosXL/163/console

Wondering if this is related? https://github.com/AdoptOpenJDK/openjdk-build/issues/1450#issuecomment-756835783
As API forards to the github API binaries URL

Wondering if this is related? https://github.com/AdoptOpenJDK/openjdk-build/issues/1450#issuecomment-756835783
As API forards to the github API binaries URL

CC @johnoliver JIC this triggers any thinking with your investigation

CC @johnoliver JIC this triggers any thinking with your investigation

NOTE: I've added the additional boot JDKs onto the zLinux build machines so those should no longer try to download. I suggest we make sure that is done universally. We can progress in https://github.com/AdoptOpenJDK/openjdk-api-v3/issues/341

NOTE: I've added the additional boot JDKs onto the zLinux build machines so those should no longer try to download. I suggest we make sure that is done universally. We can progress in https://github.com/AdoptOpenJDK/openjdk-api-v3/issues/341

We've not seen this for a while now, any further api work can continue in https://github.com/AdoptOpenJDK/openjdk-api-v3/issues/341

We've not seen this for a while now, any further api work can continue in https://github.com/AdoptOpenJDK/openjdk-api-v3/issues/341


*: move from tokio-core to tokio

Resolves #93
Resolves #218
Issue #218 was caused by our tokio reactor somehow running on a single thread, so when the RuntimeHost was processing events it would block all other tasks.
Now things are more async, which required making a bunch of things Send and Sync. This was done mostly by just adding the bounds, but the subgraph resolver needed a deeper refactoring, which was good because we're now using failure for it's errors.
The tricky part is the WasmiModule because it's not Send, so we spawn a dedicated OS thread to handle each RuntimeHost and then may call wait() inside host exported functions without causing a system-wide slowdown.

@fordN Thanks for the careful review! If a tokio worker thread panics it will only log the panic and drop the task, so I've changed the store tests to always panic on the main thread so that the test fails properly.

Looks good! 👍  Graph-store-postgres tests are now behaving as expected.


Public test demo neopixel no longer lighting up, needs replacement and better unit tests

Would be good to have a unit test that can auto-check for something like this. Just a rough check that turning on the light produces a reasonable set of spectra values after background submission. Also, a good future reference that I need to transport it more carefully (i.e., in a case).
In the meantime, I'll just need to swap it out with another Maker Pi Pico base

The Pico W microcontroller pin connection seems to have broken. What I get for being too rough with it for a very long time (storing in backpack without a case, traveling internationally, etc.)


Update landing page to better showcase Raito's work 🌟✍

Current Situation 👀
The website (https://www.raito.wtf/) could better explain what Raito does and look more modern. Right now it's missing the wow factor that would make users want to explore more!
What Could Be Better 💭

First Impression

Add a hero section with a cool animation
Modern, clean design that shows we're a tech company

Missing Information

Social proof/testimonials missing
more engaging ui component to draw in the user
lack on a white mode to give user more control
about section
contact us section

Suggested Improvements 🎨

Add sections for:

Quick overview ("Raito helps you do X")
Main features with icons
How it works steps
Team/About section
Contact info
Links to socials/community

Why This Matters 🎯

Makes better first impression
Helps users understand the product faster
Looks more professional

References
https://www.raito.wtf/
and the picture i attached to the issue

Would love to bring this to life. can i work on this?

Hi @akintola4 can I implement this?
I’m a frontend and smart contract developer.
I’d review the code base and implement all features as expected.
ETA: 48hrs

Would love to work on this. @akintola4

Would love to work on this. @akintola4

great would love to build the frontend and i have a great friend who is the best in ui/ux

@akintola4  I'd love to work on this

Hi, I'd love to work on this


fixes #37. #38 had bad merge resolution.

Really fixes #37. I messed up the merge resolution and it dropped a conditional. Tested against the source from the issue and got a byte slice in return, no panics.

Coverage increased (+1.3%) to 90.805% when pulling 48c51766113358d4f0b280e76c0b7c68803b636d on fix37 into 1b869955198b7b6b63428eff0edff4526fed4d43 on master.


Show error if default value for Rancher server-url is a local host IP

Detailed Description
Provide insight to the user in case of communication issues with DO instance.

Add validation to the server URL property both on the setup screen and the global settings page that lets you change it - when set to <IP_ADDRESS> or localhost, we show a warning banner.
Text for banner should be: If the Server URL is internal to the Rancher server (e.g. localhost) the downstream clusters may not be able to communicate with Rancher

Context
While interacting with a cloud service, if the server-url is not set, requests will hang unfulfilled without a clear message, especially for beginner users.
Displaying a notice if Rancher has not a remote IP, we should inform the user of possible issue, e.g. creation of Clusters.
Configuration path: /c/local/settings/management.cattle.io.setting
Area: Global Settings -> Settings -> server-url

I think this is a great idea and will help many people who are trying Rancher for the first time.
Here is what should change. When you set up Rancher for the first time, you will see this screen:

Here Rancher uses whatever is in your web browser as the default value for the Rancher server URL. So if you are running Rancher on localhost, the default value can end up as https://<IP_ADDRESS>:8005. This does not immediately cause an error, but it should. Because if the Rancher server URL is localhost, then if you try to create a downstream cluster, the cluster will get stuck pending.
In the above screen, if the default value contains <IP_ADDRESS>, we should show an error that says "If the Rancher server URL is local host, Rancher will not be able to communicate with downstream Kubernetes clusters"

We would need a similar mechanism for the server-url setting in global settings.
That has the description below (note the incorrect product name of Explorer).
Default Explorer install url. Must be HTTPS. All nodes in your cluster must be able to reach this.

So would suggest flipping the test from If the Rancher server URL is local host, Rancher will not be able to communicate with downstream Kubernetes clusters to If the Rancher server URL is internal to the host the downstream clusters will not be able to communicate with Rancher

The problem with changing the text is that people don't read. This is documented in several places as well, but a lot of times, text just doesn't register.

I'm not saying that changing the text is a bad idea, because in fact your version is more technically correct. Just that some people won't read either way

I'm only advocating a tweak to the text you suggested (to fix the direction), and that whatever we do on the setup page should also be done in the global settings page.

In summary:

Add validation to the server URL property both on the setup screen and the global settings page that lets you change it - when set to <IP_ADDRESS> or localhost, we show a warning banner.
Text for banner should be: "If the Server URL is internal to the Rancher server (e.g. localhost) the downstream clusters may not be able to communicate with Rancher"

As this will touch global settings, I'll proceed after https://github.com/rancher/dashboard/issues/6633 is merged, so I can simply add the setting for this.
I'll create a new validation to check if something is local, with the possibility to define true/false.

As discussed with @nwmac we should not block the submission if the server url is a localhost url, we should only show a warning message. But for the below cases we'll block the submission and show an error message when the server url:

is not a url(we reuse the imported library is-url to validate this)
is not provided at all
is not https
has a trailing forward slash

This one should go through QA right @momesgin? Our bot should have re-opened it

@richard-cox that's right, thanks! I moved it to "To Test" state as I discussed it with @gaktive

Added as possible automation-candidate. Login part could probably be tested with a unit test... Settings page we have several e2e that we could piggy-back on.

The E2E implementation using fixtures was a really good call. Coverage looks good


MT field of DR and TSDR registers of RTC may need a numeric type with variant definition.

It is a corner case, single bit MT field of DR and TSDR registers of RTC is marked as bool type, which is a little wired.
Since MT stands for Month Tens, it may have numeric type, with variant MT_A::Zero and MT_A::One.
I think this affects all chips with RTC embedded.

thanks for guiding me.


Community contributed examples

Keeping track examples put together by the community. This list will be moved to and featured on the SST Examples page. Submissions welcome!

Author
Title
Link
Slack Conversation

Mischa
SST + Prisma ORM Template with DB migrations
https://github.com/jetbridge/sst-prisma
Slack

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble


gccgo : -fgo-dump-ast segfault Ast_dump_traverse_blocks_and_functions::block is passed null

The int Ast_dump_traverse_blocks_and_functions::block(Block * block) method gets passed a null block on empty switch statements which unchecked creates a segfault.
I have a simple test case here :
https://github.com/h4ck3rm1k3/nogo/blob/master/expression/switch/empty_switch.go
switch f {
case 1:
// empty
case 2:
   ....
}

Here is a snippet of the new ast which illustrates the problem,
look for :/* ERROR NULL BLOCK */ to see what was skipped.
.main.main() : (/*Function_type*/func )
{
  var .main.f (/*Named_type*/ int ) = 1
  {
    switch .main.f {
    case 1:/* ERROR NULL BLOCK */
    case 2:    {
      var .main.foo (/*Named_type*/ int ) = 1
      .main.foo = (.main.foo + 1)
    }
}
  }
}

@ianlancetaylor I have a minimal test case and a patch for you.


implemetation of AtomCommandline to preserve args

Inital work for #1248 . @zcbenz If its desirable to have our own commandline class , then i can implement other methods from base::commandline for our needs and eliminate its usage. If this is too heavy for a trivial stuff, feel free to close it. would love to hear any better approaches :)
EDIT: sorry didnt mean eliminate base::commandLine but just atomCommandLine will wrap around it, so all commandLine calls to base will happen through this new class.

Thanks for working on this.

We don't need to replicate base::CommandLine's interface, our purpose is to keep a copy of argv and then pass it to node::CreateEnvironment, so a simple singleton class that keeps a references to argv should be enough in our case.

@zcbenz made the changes and added tests, havnt tested on windows though. Would be nice if someone did :)

It works on Windows, thanks!


Feature Request: Ability to add to adventure log from chat log if you forget /log when displaying a chat message

A context right mouse click or message button to add a chat message to the journal.
If a message is displayed to players and they think it worthy of adding to the journal, it would be nice to simply click on the message and have it logged to the adventure log.

I will look into this when I do a larger update to the Chat Archive. I plan to add some more QoL to the feature.


Fix LuckPerms Integration

Description
Currently, LuckPerms permissions will only work consistently if a player has or inherits a single queue permission node, the loop breaks as soon as a single permission node is found. This requires inherited nodes to be negated so only one queue permission node is resolved per group/player.
How it will work
Check the entire stream of permission nodes and sort the available queues by their priority, then add the player to the queue with the highest priority they have the permission node for.

Additional Bug
LuckPerms will load after MatsuQueue. In some server configurations, this will break MatsuQueue. Currently this branch https://github.com/nitricspace/MatsuQueue/tree/bugs/luckperms-depedancy?files=1 has a fix, although it will mean the plugin will not load at all if LuckPerms isn't used.
Need to find a more elegant solution, alongside the previous issue.

Dependency issue is fixed, as is the original problem.
Still need to implement a way to filter negated permission nodes. Steam the permission node set and filter out any nodes which have been negated.

Resolved with https://github.com/nitricspace/MatsuQueue/commit/a8eeed7fa450e68ef156b14a78077e62f9b90e72


Version 1.2.1

Changelog:

Fix duplicate() and clone() regression
Use only obj ownProperties in mergeObjects()

Landed in https://github.com/metarhia/common/commit/09070b7916f09663d1f418aa99746edbdd70762b.


link and meta tags are not self-closing

Something else that I found: https://github.com/ribice/kiss/blob/master/layouts/partials/header.html#L5
link and meta are void elements and not self-closing.
See https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta#Examples and https://developer.mozilla.org/en-US/docs/Web/HTML/Element/link#Examples
I will try to provide a PR in a few days when I find the time.

Any update on this @DanielRuf ?

Any update on this @DanielRuf ?

Unfortunately I had not much time so far and currently work related projects are need my whole time.
I will try to find some time this or next weekend.

Unfortunately I had not much time so far and currently work related projects are need my whole time.
I will try to find some time this or next weekend.

Thanks for the reminder.
Unfortunately I had not much time so far and currently work related projects are need my whole time.
I will try to find some time this or next weekend.

Thanks for the reminder.
Unfortunately I had not much time so far and currently work related projects are need my whole time.
I will try to find some time this or next weekend.


Rebasing breaks the internet connection

Hey, very new to Fedora and rebasing, but want to give SecureBlue a try for my upcoming laptop.
Now, I am installing this in a VM, so this could be a non issue when installing on my laptop, but I wanted to check out the system first. I had some issues getting it installed on Hyper-V, but when I used VM Generation 2 and disabled secure boot, everything went well.
So after installing SilverBlue using the ISO, I run this command:
rpm-ostree rebase ostree-unverified-registry:ghcr.io/secureblue/silverblue-main-hardened:latest

After this I reboot. Upon system start up, the internet connection is gone and no amount of tweaking brings it back. I am hoping this is some VM issue, but I am not entirely sure. Does anyone know what could be happening?
Hope someone can help me out.

hello :-)
Im guessing this might be a HyperV problem. Maybe the required virtualization drivers are nor part of ublue.
could you maybe check the NetworkManager logs for any obvious errors?

@aunefyren What @34N0 is correct. This is expected. I should probably remove the note to test on a VM first, that's from upstream but not an appropriate recommendation for secureblue because of the changes we make.

https://github.com/secureblue/secureblue/commit/4fb96f6f6fdfa16d2e6999a11fbdf5615ff1096b

Thank you so much for the replies. I'll give it a go on a laptop. Cheers


id = 1 [(validate.rules).string.optional_uuid = true]

This is more of a feature request. Would be nice to have in addition to the already existing
id = 1 [(validate.rules).string.uuid = true]

something like
id = 1 [(validate.rules).string.optional_uuid = true]

which doesn't fail validation if the param is missing respectively an empty string.

Maybe this is more of a use case for StringValue?

Maybe this is more of a use case for StringValue?

So you mean something like this?
id = 1 [(validate.rules).optional_string.uuid = true]

Agree. That would cover more use cases 🤔

So you mean something like this?
id = 1 [(validate.rules).optional_string.uuid = true]

Agree. That would cover more use cases 🤔

You can do something like this:
google.protobuf.StringValue id = 1 [(validate.rules).string.uuid = true];

Just run into this. It would be nice that google.protobuf.StringValue is not needed to wrap a string in order to make the validation optional. Perhaps we can supportsomething like this:
google.protobuf.StringValue id = 1 [(validate.rules).string.optional.uuid = true];

@owenthereal Did you mean rather this?
string id = 1 [(validate.rules).string.optional.uuid = true];

I guess with the new proto v3.15 release this can be achieved via:
optional string id = 1 [(validate.rules).string.uuid = true];


yarn version incompatibility issue blocks Dashboards plugins CI, docker-image, windows build

:exclamation:This issue may block release 2.6
issue description
Multiple Dashboards plugins CI failure reported during plugin bootstrap step, after this commit to Dashboards core merged recently<EMAIL_ADDRESS>The engine "yarn" is incompatible with this module. Expected version "^1.22.10". Got "1.21.1"

dashboards-observability plugin CI
dsahboards-maps plugin CI

yarn run v1.21.1
$ node ../../scripts/osd bootstrap
 info [opensearch-dashboards] running yarn

$ node ./preinstall_check
[1/5] Validating package.json...
[2/5] Resolving packages...
warning Resolution field<EMAIL_ADDRESS>is incompatible with requested version<EMAIL_ADDRESS>
[3/5] Fetching packages...
warning<EMAIL_ADDRESS>Invalid bin entry for "sha.js" (in "sha.js").
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
error<EMAIL_ADDRESS>The engine "yarn" is incompatible with this module. Expected version "^1.22.10". Got "1.21.1"
error Found incompatible module.
ERROR [bootstrap] failed:
ERROR Error: Command failed with exit code 1: /opt/hostedtoolcache/node/14.[20](https://github.com/opensearch-project/dashboards-maps/actions/runs/4206519945/jobs/7300112650#step:13:21).1/x64/lib/node_modules/yarn/bin/yarn.js install --non-interactive
          at makeError (/home/runner/work/dashboards-maps/dashboards-maps/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:25150:11)
          at handlePromise (/home/runner/work/dashboards-maps/dashboards-maps/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:24085:26)
          at processTicksAndRejections (internal/process/task_queues.js:95:5)
          at async installInDir (/home/runner/work/dashboards-maps/dashboards-maps/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:238[21](https://github.com/opensearch-project/dashboards-maps/actions/runs/4206519945/jobs/7300112650#step:13:22):3)
          at async Project.installDependencies (/home/runner/work/dashboards-maps/dashboards-maps/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:14780:5)
          at async Object.run (/home/runner/work/dashboards-maps/dashboards-maps/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:9003:11)
          at async runCommand (/home/runner/work/dashboards-maps/dashboards-maps/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:57870:5)
          at async Module.run (/home/runner/work/dashboards-maps/dashboards-maps/OpenSearch-Dashboards/packages/osd-pm/dist/index.js:[26](https://github.com/opensearch-project/dashboards-maps/actions/runs/4206519945/jobs/7300112650#step:13:27)3:3)
error Command failed with exit code 1.

Root cause
The recent commit in OpenSearch Dashboards updates dependency @opensearch-project/opensearch from ^1.1.0to ^2.1.0, where openearch-js2.1.0 specifies yarn: ^1.22.1, in this commit.
Plugin CI workflow fetches yarn version from Openesarch-Dashbaords/package.json file, to set up yarn, and still found 1.21.1. This is causing the yarn version incompatibility, and bootstrap will fail.
Dashboards docker image, windows build scripts are using hardcoded yarn version, which will potentially be impacted, according to @peterzhuamazon
Impact

All Opensearhc Dashboards Plugin CI & build
Dashboards docker image build, windows build process, etc

Proposed solution

step 1: To unblock dashboards plugins CI, Opensearch-Dashboards core repo needs to update yarn version in package.json to ^1.22.1 https://github.com/opensearch-project/OpenSearch-Dashboards/pull/3443
step 2: After step 1 is completed,  to unblock docker image build, windows build, we could fetch the yarn version on demand from Openesarch-Dashbaords/package.json , instead of hardcode.

This issue is brought up late as plugins are not always following the core defined yarn version.
After glance around 5 docker images and 1 ami get impacted.

./release.centos.clients.x64.arm64.dockerfile:    for node_version in $NODE_VERSION_LIST; do nvm install $node_version; npm install -g<EMAIL_ADDRESS>done
./build.centos7.opensearch-dashboards.x64.arm64.dockerfile:    for node_version in $NODE_VERSION_LIST; do nvm install $node_version; npm install -g<EMAIL_ADDRESS>done
./test.rockylinux8.systemd-base.x64.arm64.dockerfile:RUN npm install -g<EMAIL_ADDRESS>./test.rockylinux8.opensearch-dashboards.x64.arm64.dockerfile:RUN npm install -g<EMAIL_ADDRESS>./test.centos7.performance-test.x64.dockerfile:    for node_version in $NODE_VERSION_LIST; do nvm install $node_version; npm install -g<EMAIL_ADDRESS>done

./scripts/windows/scoop-install-commons.ps1:volta install<EMAIL_ADDRESS>
Among these 6 there are 2 docker images related to bundle build + integTest, and 1 ami related to bundle build, means they need to be updated now to avoid failures on 2.6.0 builds.
The rest of them can be updated at a later time.
The updates of these images/ami should retrieve the value of yarn dynamically from core osd repo, instead of hardcoding again in the template.
Thanks.

Since this issue would impact on 2.6.0 release, cc @CEHENKLE @bbarani into the discussion on this.
Thanks.

Would it be easier to mitigate by downgrading the yarn version in openearch-js to be compatible with opensearch-dashboard?

PRs:

https://github.com/opensearch-project/opensearch-build/pull/3191
https://github.com/opensearch-project/opensearch-build/pull/3212

Why don't we just revert https://github.com/opensearch-project/OpenSearch-Dashboards/commit/de89c527dee3a997bfffc2079dbf97e4f813e54e in 2.x?
In general, OpenSearch Dashboards considers bumping direct dependencies (such as @opensearch-project/opensearch) to be a breaking change when the dependency bump contains a breaking change (which it clearly does in this case).

Revert PR: https://github.com/opensearch-project/OpenSearch-Dashboards/pull/3464

+1 @joshuarrrr. I think the call if we want the sigv4 into OpenSearch Dashboards core, without a deep dive, I don't see why not cut a minor release OpenSearch JS client for 1.x to have this feature. And then have OpenSearch Dashboards take the minor version bump from the client.

Adding @zhongnansu @derek-ho on to the change on this.
Do we need to make the changes to make the revert.
Thanks.

@joshuarrrr
I am against reverting https://github.com/opensearch-project/OpenSearch-Dashboards/commit/de89c527dee3a997bfffc2079dbf97e4f813e54e only because it includes opensearch-js version bump

openearch-js client 2.0 was released June, 2022. But in OSD core, we are still using 1.xclients now. According to the compatibility matrix of opensearch-js client. Client version 1.x doesn't support OpenSearch version 2.x, which means OSD was supposed to bump opensearch-js client lib.

As for dashboards plugins, in any 2.x.x.x, they know they are talking to OpenSearch 2.x. But  opensearch-js client1.x is being used, as it's decided from upstream OSD core. But till now, there's no known issue complaining that plugin failed to talk to OpenSearch 2.x using opensearch-js client 1.x, which means plugins are not using any deprecated APIs. So there shouldn't be a problem with plugin consuming opensearch-js 2.x now

Plus, this commit is a feature commit that was put on the roadmap, and targeted to release in 2.6.0. Also, no backwards compatibility CI has ever failed in any PR during feature implementation stage.

cc: @zengyan-amazon @peterzhu1992 @bbarani

Client version 1.x doesn't support OpenSearch version 2.x, which means OSD was supposed to bump opensearch-js client lib.

Might be a confusing matrix but on our site we state:

All clients are compatible with any version of OpenSearch.

[SOURCE]

Plus, this commit is a feature commit that was put on the roadmap, and targeted to release in 2.6.0. Also, no backwards compatibility CI has ever failed in any PR during feature implementation stage.

For build wise we usually rely on the build CI to verify and have reverted commits in the past.

For build wise we usually rely on the build CI to verify and have reverted commits in the past.

@kavilla @joshuarrrr
That's why I tried to backport the fix to OSD 2.x, so that plugin CI on 2.x could be triggered to verify. https://github.com/opensearch-project/OpenSearch-Dashboards/pull/3465.
The original plugin CI failure reported in this issue has been addressed in main. https://github.com/opensearch-project/dashboards-maps/actions/runs/4227411858/jobs/7341865358

Could we at least test the yarn version bump fix the build?

For build wise we usually rely on the build CI to verify and have reverted commits in the past.

@kavilla @joshuarrrr That's why I tried to backport the fix to OSD 2.x, so that plugin CI on 2.x could be triggered to verify. opensearch-project/OpenSearch-Dashboards#3465. The original plugin CI failure reported in this issue has been addressed in main. https://github.com/opensearch-project/dashboards-maps/actions/runs/4227411858/jobs/7341865358

Awaiting: https://github.com/opensearch-project/OpenSearch-Dashboards/pull/3477

@peterzhuamazon
Plugin CI on main is unblocked. But the fix needs to be backported to OSD 2.x, otherwise the same issue will happen.
I have a backport PR opened here: https://github.com/opensearch-project/OpenSearch-Dashboards/pull/3465

Awaiting:

[Manual backport 2.x][MD] Support SigV4 as a new auth type of datasource (#3058) OpenSearch-Dashboards#3477

This PR is merged, I noticed that Plugin CI starts to fail on 2.x, because of same yarn incompatibility. https://github.com/opensearch-project/dashboards-observability/actions/runs/4236740246/jobs/7361893066 , and the PR to fix it from OSD side is blocked. https://github.com/opensearch-project/OpenSearch-Dashboards/pull/3465
Adding @AMoo-Miki, since I saw you opened a related issue in plugin repo about the yarn config in CI workflow. I do want to mention that the same way to configure yarn is used across almost all dashboards plugins.  https://github.com/opensearch-project/dashboards-observability/issues/290

Tagging @gaiksaya as she is the release manager for 2.6.0 release.

Hi @zhongnansu @peterzhuamazon What are the next steps here? As the today is the code cutoff date for 2.6.0 trying to see if we need to extend that from dashboards prespective.
Thanks!

All images updated now in docker hub (3131 3126 3125 3123 docker-build Jenkins).
Windows image requires a redeployment later.
Thanks.

@peterzhuamazon I do not see any PRs for adding yarn version https://github.com/opensearch-project/opensearch-build/tree/main/docker/ci/dockerfiles/current am I missing anything?

Hi @zhongnansu @peterzhuamazon What are the next steps here? As the today is the code cutoff date for 2.6.0 trying to see if we need to extend that from dashboards prespective. Thanks!

The next step is approve and merge in this PR: https://github.com/opensearch-project/OpenSearch-Dashboards/pull/3465, to fix yarn issue and unblock plugin CI

All the effected plugins were using a flawed logic to install Node.js and Yarn runtimes based on the information they were reading from OSD's manifest. They all took the ranges OSD provided, manipulated it incorrectly and attempted to install Node and Yarn. I have gone through all the repos and raised PRs with the correct procedure on all of them.
There is also a possibility of some repos using strict versions for their own engines.* which is a bad and wrong practice. While I did not see this in any repo, i caught one PR that attempted to do so and commented on it.
There is also a repo that uses a file named .node-version that we are investigating to remove in the future; I will reach out to them if we decide to remove the file so that they can use .nvmrc instead.

Hi @zhongnansu @peterzhuamazon What are the next steps here? As the today is the code cutoff date for 2.6.0 trying to see if we need to extend that from dashboards prespective. Thanks!

The next step is approve and merge in this PR: opensearch-project/OpenSearch-Dashboards#3465, to fix yarn issue and unblock plugin CI @gaiksaya

That PR is not an acceptable solution; OSD cannot make arbitrary changes to accommodate mistakes in CI scripts of plugins.

Should we also add the .npmrc to enforce the restriction the node version in OSD core?

Kristen, my goal is relaxing all of these restrictions. If nvmrc would allow me, I would have used a range there as well.

All new images for Jenkins have been deployed with yarn 1.22.19.


Upgrade Guava and drop Java 7 support

Upgrading Guava requires :

to drop Java 7
to upgrade Wiremock
to fix new spotbugs issues

:x: Build jmxtrans 462 failed (commit https://github.com/jmxtrans/jmxtrans/commit/c34d8c4f21 by @gquintana)

:x: Build jmxtrans 462 failed (commit https://github.com/jmxtrans/jmxtrans/commit/c34d8c4f21 by @gquintana)

:x: Build jmxtrans 471 failed (commit https://github.com/jmxtrans/jmxtrans/commit/7271f220d9 by @gquintana)

:x: Build jmxtrans 471 failed (commit https://github.com/jmxtrans/jmxtrans/commit/7271f220d9 by @gquintana)

@gehel @kevinconaway where can I find the Dockerfiles used to build jmxtrans/testing images ?

@gehel @kevinconaway where can I find the Dockerfiles used to build jmxtrans/testing images ?


Updated description with new email

Hi,
I will likely be working on this again for use with the NWM. I updated the description with my new email.

🎊 Glad to hear it!

Build failures are on me. I'll pull down your changes and fix the build in another PR.

Broken build was on you @jmills-ncar -- extra line in the DESCRIPTION is bad. I fixed it over in #153.


[nrf fromlist][nrfconnect] Improve CHIP_MEMORY_PROFILING config

Enabled the full SHELL option when memory profiling is enabled.

Also, can you please describe why SHELL_MINIMAL is undesired? It doesn't seem related to the profiling feature.

Also, can you please describe why SHELL_MINIMAL is undesired? It doesn't seem related to the profiling feature.

It was requested by QA to have it because it helps with using all SHELL components like KERNEL_SHELL, CHIP_SHELL, and NET_SHELL.


Update Localization.txt

Partial update Portugues Language.

Thanks for the work.
I found this by poking around because of your message.  You have got the right idea, but this pull request is from your Sanscouer-patch-1 branch to your master branch.  It needs to be merging into NPBruce:master, then I will get it for approval (as this is your repo I can't approve this anyway, only comment).
I will create a new pull request.

https://github.com/NPBruce/valkyrie/pull/496
I have also targeted development rather that master, usually a good idea to fork and target this.


Update jackson-databind to 2.9.8

Updates com.fasterxml.jackson.core:jackson-databind from <IP_ADDRESS> to 2.9.8.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a nice day!

I need to configure this to be ignored…


Grafana Login Invalid Username and password

Unable to login to Grafana invalid username and password when updated to latest version

Updates have no effect on your username and password.
You can try and reset your Grafana volume which will mean you lose any dashboard modifications you have made and you'll get the initial setup again with the default username and password.


Context aware - foundation

Note: this PR is made against a feature branch, not main

This is the initial work required to get the new context aware implementation ready.
Once merged, this allows policies to fetch any kind of Kubernetes resource from a cluster.
No security check is done yet, meaning a policy could fetch basically everything. This will be fixed with a future PR made against this feature branch.
These are the commits done inside of this PR, each one aims to be self explanatory:

refactor: split and DRY code
Update policy metadata
feat: introduce new context aware callbacks
chore(deps): use latest version of the SDK

@viccuad can you take another look please?


Add Drupal as a setup config option in containers demo startup app

Describe the issue
Currently https://github.com/bcgov/startup-sample-project-aws-containers installs hello world and https://github.com/bcgov/startup-sample-project-aws-drupal-containers installs Drupal.  Due to the similarities in the codebases, for maintenance effectiveness we want to collapse these into one code stream with config options to choose from like "hello app", "Drupal" and more.
Additional context
Add any other context, attachments or screenshots
Definition of done

Add a local and remote deployment option for Drupal to https://github.com/bcgov/startup-sample-project-aws-containers
Add the Drupal functionality to https://github.com/bcgov/startup-sample-project-aws-containers from https://github.com/bcgov/startup-sample-project-aws-drupal-containers
Get rid of https://github.com/bcgov/startup-sample-project-aws-drupal-containers

not relevant


replace gittip by liberapay

Gittip, later Gratipay has shut down.
https://gratipay.news/the-end-cbfba8f50981
There is a fork, Liberapay. Gratipay has hand their asset's over to them.
I also use Liberapay sucessfully, so i can reccommend that!

Thanks for the suggestion! To be honest I've never received any donation through gitpay and I forgot we have that link on the website. I'm going to remove it in a moment.
It seems to me that Liberapay is something similar to Patreon. With my current level of involvement into this project I feel it's more appropriate to ask for one time donations using ko-fi. I'll create an account for that when I'm less busy


pin setuptools in the testpypi configure script

This works around a incompatibility between setuptools>=60 and setuptools_scm.

[x] Closes #6659

that didn't help, either. I'll investigate tomorrow unless someone else beats me to it.


Best way to add tooltip

Hi Daniel,
Really enjoying your React library! I was just wondering, do you have a recommended way of adding a tooltip (using one of the available tooltip libraries) to a graph generated with your approach? Would be very helpful if you could point me to an example.
Thanks!
Simon

@danielcaldas What about for tooltips like in this graph? https://bl.ocks.org/d3noob/257c360b3650b9f0a52dd8257d7a2d73
I want to display several pieces of text inside this tooltip like in the graph above when you hover over the nodes and I wonder if i can keep a tooltip fixed as well?

Hello @owlstack as mentioned before

With custom nodes you can now add complex JSX structures customized for nodes see the sandbox example.

Please use custom nodes where you can define yourself a tooltip.

@danielcaldas What would be the best way to handle hover/click scenario then? If hover/click, then display icon div otherwise, don't?
Also, is this a thing or is not implemented currently:
node: {
showToolTip: true,
tooltipProp: 'id',
tooltipBackgroundColor: ' black',
tooltipTextColor: 'white'
}
Where I can set a tooltip id, have a show/hide bool, etc... ? Thanks!

Hi @danielcaldas I'm trying to enable tooltip for node on MousrOver. I'm unable to access the below URL.

If possible, can you enable it?
Even after including the node configuration, the tooltip is not visible.
node: {       showToolTip: true,       tooltipProp: 'id',       tooltipBackgroundColor: ' black',       tooltipTextColor: 'white' }
Can you suggest me, how to attach tooltip onMouseOverNode?
Thanks


Add team devs as default dependabot reviewers

What
Add team devs as default dependabot reviewers
Ticket
n/a
Why
Any team dev can review and approve dependabot
PR.s this automates the assignment of devs.
Note: we should move to version 2 of the
dependabot githubnative config. see
cccd for example.

I was thinking, instead of the individuals, whom we would have to remove from code when there is a change to the team structure, why not add the github team 'laa-get-paid'?

I was thinking, instead of the individuals, whom we would have to remove from code when there is a change to the team structure, why not add the github team 'laa-get-paid'?

I was thinking, instead of the individuals, whom we would have to remove from code when there is a change to the team structure, why not add the github team 'laa-get-paid'?

I don't think that allows you to easily just add your individual review - but have not tried it. The idea is to a) ping the individuals to notify them they can review (if they have notifications enabled) and b) remove the need to assign yourself to the PR and then approve. We already have this on CCCD incidentally
I its pretty easy to amend to remove a dev if they leave so i don't see that as a big issue

I was thinking, instead of the individuals, whom we would have to remove from code when there is a change to the team structure, why not add the github team 'laa-get-paid'?

I don't think that allows you to easily just add your individual review - but have not tried it. The idea is to a) ping the individuals to notify them they can review (if they have notifications enabled) and b) remove the need to assign yourself to the PR and then approve. We already have this on CCCD incidentally
I its pretty easy to amend to remove a dev if they leave so i don't see that as a big issue


Remove version: Jackett.Jackett version 0.20.3011

404 - release deleted
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Jackett/Jackett/releases/download/v0.20.3011/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)


Issues signing in on stage after changing password on live

There's something slightly strange going on with signing into the stage Auth0 tenant as a library member.
Here's what I saw:

Account on stage, able to log in fine
Changed password on live, couldn't log in on stage with new password
Deleted Auth0 account on stage, still couldn't log in with new password

So now I'm unable to log in on stage, even when there is no account in Auth0 for my patron record. I get told the user/password is wrong and a new Auth0 user is not created.
I'm likely doing something unexpected or wrong here, but I think it's worth a bit of investigation in case there is something slightly awry that might hit users who change their password after we go live.
I think @cbowskill saw this recently too.

I'm going to close this, as I reckon it was probably caused by our old approach to Auth0/Sierra account sync. We can open a new ticket if we see the issue again.


Organism Taxons now missing kingdom labels

From back in October of last year: https://github.com/RTXteam/RTX/issues/1100 , @finnagin added a script to decorate Organism Taxon nodes with their kingdom (to quickly pull out microbes): https://github.com/RTXteam/RTX/blob/e41d3eeba3f08f8e6ae53fd7db8f91c87e55dba6/code/kg2/misc-tools/decorate_organism_taxon_nodes.py
Looking at KG2.7.0, that label (organism_type) appears to be missing. Can we get it back?

The organism_type label has been added to KG2.7.0.
A couple things to document about using that script now:

It looks for the RTX directory. I had to change this to RTX-KG2. (I will commit that change, but it is helpful for documentation purposes).
To run it on the Neo4j instance, I had to manually install ontobio. (It's not included on the Neo4j requirements document).
Also, before you can run it, you have to set the database to not read only (sudo sed -i '/dbms.read_only/c\dbms.read_only=false' /etc/neo4j/neo4j.conf)
After you run the script, make sure to set it back to read only (sudo sed -i '/dbms.read_only/c\dbms.read_only=true' /etc/neo4j/neo4j.conf)
You have to manually curl the RTXConfiguration.py script, since the RTX-KG2 repo is now separate from the RTX repo. Further, you have to curl it into the same directory as the decorate_organism_taxon_nodes.py file (misc-tools).

Perhaps we should consider running this in tsv-to-neo4j.sh to make sure it happens? @saramsey Thoughts on adding it in?

Thanks @ericawood ! It does have the ability to use a config file (which I think is what you do elsewhere in tsv-to-neo4j.sh correct?) with the --config argument here. If specified it won't use RTXConfig so we could move the import lines inside of an if statement so they are only imported if --config is not used.

This is resolved in the issue89 branch, so I'm going to mark this for verification.


[SAM] SAM 6.0 Data

updated Data for SAM actions and statuses.
Removal of code for lost mechanics

Potencies are a holdover I've never used nor did I have plans to use them.... though now that you mention monk using them I could do something similar for kaiten to show lost "free" potency from Higanbana and Midare instead of the current "X skills missed" from 5.0
I'll get a change log for fixing the status buffs once I get home from the holidays.

though now that you mention monk using them

FWIW we only have potency on True and Twin to show the loss when calculating bad uses. I removed it from Boot because it's 2 separate Bootshine potencies that are relevant so the field wasn't of clear value. I've stripped potencies from the rest tho.


Tree multiselect 'get_next_selected()' not collects all selected items

Godot version:
Godot Engine v3.2.3.stable.mono.official - https://godotengine.org
OpenGL ES 3.0 Renderer: GeForce GTX 980/PCIe/SSE2
OS/device including version:
Windows 10 x64
Issue description:
The multi selection on Tree is broken when select multiple items from bottom to top in the tree.
Steps to reproduce:
To reproduce you have to select the items from bottom to top. (press CRTL + mouse )

select folder 'folder_8'
select folder 'folder_4'
press right mouse button to show current selection
only folder_8 is found as selected

If you select from top to bottom it works as expected

select folder 'folder_4'
select folder 'folder_8'
press right mouse button to show current selection
folder_4 and folder_8 is found as selected

Suggested Feature
Add a new function to get all selected items on SELECT_MULTI mode
Array get_multi_selected() const
Returns all selected items if SelectMode set to SELECT_MULTI otherwise null.
For SelectMode=SELECT_SINGLE use 'get_selected' instead
Minimal reproduction project:
selectionBug.zip

I believe the behavior is intentional, i.e. get_next_selected only traverses the tree from the top-down, so it is not able to get any selected nodes that come before the node that is supplied as the argument.
To get all the selected nodes, you can first pass null to get_next_selected to get the very first selected node:
	var selected_item:= get_next_selected(null)
	while selected_item:
		print(selected_item.get_text(0))
		selected_item = get_next_selected(selected_item)

I believe the behavior is intentional, i.e. get_next_selected only traverses the tree from the top-down, so it is not able to get any selected nodes that come before the node that is supplied as the argument.
To get all the selected nodes, you can first pass null to get_next_selected to get the very first selected node:
	var selected_item:= get_next_selected(null)
	while selected_item:
		print(selected_item.get_text(0))
		selected_item = get_next_selected(selected_item)

@mrushyendra take you a look in the attached example project?
I use var selected_item:= get_selected() and not get_next_selected as first call

@mrushyendra take you a look in the attached example project?
I use var selected_item:= get_selected() and not get_next_selected as first call

Yeah, I was just suggesting a workaround if you want to get all the selected nodes.
From the documentation for get_next_selected():
If 'from' is null, this returns the first selected item.
On the other hand, get_selected() may not return the first selected node. Instead it will return the node that is clicked first.

Yeah, I was just suggesting a workaround if you want to get all the selected nodes.
From the documentation for get_next_selected():
If 'from' is null, this returns the first selected item.
On the other hand, get_selected() may not return the first selected node. Instead it will return the node that is clicked first.

Thanks for your suggestion, i will change my code and use get_next_selected(null) to get first selected node ;)

Thanks for your suggestion, i will change my code and use get_next_selected(null) to get first selected node ;)

The workaround doesn't work.
My issue is slightly different:

when single selecting from bottom to top, the get_next_selected() will still report the bottom one as selected.

Using 4.2.1 stable.

Update:
I was able to fix the issue by "queueing" getting the selection for the next frame.
I noticed that the multiselection signal gets emitted multiple times and thought it may be the cause of the problem.
I don't know if there was a problem in my system with updating multiple times per frame, or the Tree needs a frame to update its selection stuff properly.


Identify file format based on filename

Hi there,
I was very excited to try Rotor this morning, using rotor version 0.16.0 and ran into a small documentaion/UX issue:
While following the instructions in the README to start with Flat Files Service Discovery, the README doesn’t mention that to use a YAML file – in the format described – one needs to specify the --format=yaml flag to Rotor.
Otherwise Rotor tries to parse the YAML as JSON, which is the default value in the github.com/turbinelabs/codec library and spits out file: invalid character ' ' in numeric literal errors with no obvious clue as to what is causing this.
I looked into trying to guess the file format from the filename, but it looks it would require quite a few changes to the way flags are parsed.

Hi @pims,
We'll update the README to be more precise, but will continue to require that the format be explicitly specified.


Local Debugging does not Work

Local debugging in VS Code does not work as explained here.
After following the instructions, I receive the following error:

error: Error while running local experiment Run: (number).

There is no explanation and the Run in AzureML has no output.

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

ID: 23b35e09-7c87-ee02-ce21-7582679b752d
Version Independent ID: 6c77b990-7932-426f-548f-144ec9abd495
Content: Tutorial: Set up the Visual Studio Code extension (preview) - Azure Machine Learning
Content Source: articles/machine-learning/tutorial-setup-vscode-extension.md
Service: machine-learning
Sub-service: core
GitHub Login: @luisquintanilla
Microsoft Alias: luquinta

Pada tanggal Sel, 2 Feb 2021 06.09, Sepehr Farhand<EMAIL_ADDRESS>menulis:

Local debugging in VS Code does not work as explained here.
After following the instructions, I receive the following error:
error: Error while running local experiment Run: (number).
There is no explanation and the Run in AzureML has no output.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com
http://docs.microsoft.com ➟ GitHub issue linking.

ID: 23b35e09-7c87-ee02-ce21-7582679b752d
Version Independent ID: 6c77b990-7932-426f-548f-144ec9abd495
Content: Tutorial: Set up the Visual Studio Code extension (preview)
Azure Machine Learning
https://docs.microsoft.com/en-us/azure/machine-learning/tutorial-setup-vscode-extension
Content Source:
articles/machine-learning/tutorial-setup-vscode-extension.md
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/machine-learning/tutorial-setup-vscode-extension.md
Service: machine-learning
Sub-service: core
GitHub Login: @luisquintanilla https://github.com/luisquintanilla
Microsoft Alias: luquinta

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/69838, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARHWXR2EITXERD2EBDBNSOTS44RB5ANCNFSM4W5RSKIA
.

@sfarhand Thanks for the feedback! We will review and update accordingly.

@sfarhand Here’s a repo showing how to do remote debugging via VSCode on Azure ML: https://github.com/danielsc/azureml-debug-training.

#assign:@luisquintanilla

Hi @sfarhand
Thanks for filing this issue. Is there a specific step in the tutorial where you're getting this error?

@sfarhand Could you please add more details about the specific step.

@ram-msft The "Setting up VSCode Remote on an AzureML Notebook VM" link from the page you shared is broken.
I followed the instructions from Interactive debugging with Visual Studio Code.  This might take some time. You can track the progress via the 60_control_log being streamed. Run: 1". After that, it appears that nothing is happening; that is, there is no 60_control_log in the experiment page and there is no message in the  Azure ML Output.
If I am patient enough, I get the following message:
error: Error while running local experiment Run: (number).

Thanks for those details @sfarhand. Looking into it.

Hi @sfarhand,
I was unable to reproduce the error and was able to successfully debug experiments using the instructions in the doc.  For reference, here's my setup:

OS: Windows 10
VS Code Version: 1.53.2
Azure ML Extension Version: 0.6.20
Docker Desktop

Version:  3.1.0
Running: Yes
Set up to run Linux containers: Yes

Hi @sfarhand, since it's been some time since we've heard back from you. I'll proceed to #please-close this issue. If you feel that your doc issue hasn't been resolved, feel free to open a new issue with the additional information requested. Thank you!


Expose validate()

Currently, only is_valid() is exposed, which just returns a bool.
It would be great to expose validate(), too, to get actual validation errors thrown (with information about why the validation is failing...).

@wolfgangwalther @olirice
I would like to contribute to the project, and take this issue.
Can you take a look at PR #32 ?

I wonder if this would make it possible to return meaningful validation errors for CHECK constraints. For now, all we get for an invalid insert is:
ERROR:  new row for relation "node" violates check constraint "node_column_check"


Minor: Fix incorrect s.apache.org links

Some of the s.apache.org links that we include in documentation and error message were incorrect. This PR updates them. To make sure I got them all I used grep to find all unique links and verified them:
❯ egrep -iIro 'https:\/\/s.apache.org\/[a-z\-]*' sdks/python/apache_beam/dataframe --no-filename | sort | uniq
https://s.apache.org/dataframe-event-time-semantics
https://s.apache.org/dataframe-non-deferred-columns
https://s.apache.org/dataframe-non-deferred-result
https://s.apache.org/dataframe-non-parallel-operations
https://s.apache.org/dataframe-order-sensitive-operations
https://s.apache.org/dataframe-plotting-tools

ValidatesRunner compliance status (on master branch)

Lang
ULR
Dataflow
Flink
Samza
Spark
Twister2

Go
---

---

---

Java

Python
---

---

---

XLang

---

---

Examples testing status on various runners

Lang
ULR
Dataflow
Flink
Samza
Spark
Twister2

Go
---
---
---
---
---
---
---

Java
---

---
---
---
---
---

Python
---
---
---
---
---
---
---

XLang
---
---
---
---
---
---
---

Post-Commit SDK/Transform Integration Tests Status (on master branch)

Go
Java
Python

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website
Whitespace
Typescript

Non-portable

Portable
---

---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @tvalentyn

Run Python PreCommit

LGTM, thank you


DocumentStore cache

I've got a number of types that are almost never changed, like a Country type. To prevent unnecessary loading I want to cache the items globally (at documentstore per tenant).
Loading
The DocumentSession.Load<..>() can load the item from the local Session Cache, if not found, load from the documentstore, if not found load from database and store in the documentstore cache.
When an object is  loaded and converted from json it could also check if the type is cache-able and if yes, add to the global cache.
Saving
After a Session.SaveChanges store the modified item from the session in the documentstore if the type is cached.
Configuration
enable cache for a specific type
specify a cache period (or infinity)

You're asking for 2nd level caching support in Marten? I think I'd rather you just handle that in your app with something sitting right above Marten to be honest. I really don't want to have to support that feature because it sounds like the kind of thing that users would shoot themselves in the foot with.

Correct! 2nd level caching.

it sounds like the kind of thing that users would shoot themselves in the foot with.

Why? it should not be enabled by default and the implementation should be safe when you use a single documentstore (single appdomain) / single point of entry to the database (direct edits via SQL are not visible). My definition of safe is: the 2nd level cache is also updated when an entry is changed via an attached document session

Where's this document coming from? Why isn't it reflecting the latest changes? Why is Marten blowing up my memory usage?

Why isn't it reflecting the latest changes?

It should because a SaveChanges should update the entry in the 2nd level cache.

Why is Marten blowing up my memory usage?

MemoryCache can be configured with a memory limit and it's not enabled by default.
But I understand you're concern, more features is more complex and more questions.
To add this function to your own application, it would be useful if the Load functions in the QuerySession are declared as virtual... Or extend the StoreEventListener with a BeforeLoad / AfterLoad / AddedToSessionCache... ( i don't know if there's a single point where the loading/transforming from json of documents is handled)

You'd want to integrate the 2nd level cache into the IdentityMap mechanics to make this work

Thanks! Can we make this method protected and virtual, so we can override it in a subclass?
private IIdentityMap createMap(DocumentTracking tracking, CharArrayTextWriter.IPool sessionPool, IEnumerable<IDocumentSessionListener> localListeners)

@mdissel I'd really rather we don't do that with inheritance. I'd rather just switch off and use different IIdentityMap types in that case.
If you're going to do this, are you also okay signing up to help field user questions later too?

@mdissel did you make any progress with this?

No, sorry didn't had time..

Closing this. No recent activity.


added tracing capability to ext-authz http client

Description:
This PR adds tracing support to the HTTP client in the external authorization filter. So far, only gRPC client was able to trace requests from the filter to an authorization service.
Risk Level: Low
Testing: yes
Docs Changes: N/A
Release Notes: Added
Fixes #6520
Signed-off-by: Gabriel Linden Sagula<EMAIL_ADDRESS>

@dio Sorry for the delay on that. I think I addressed all your comments from https://github.com/envoyproxy/envoy/pull/7267. Thanks!

Thanks. will take a look.

/retest

/retest

/azp run envoy-linux

@zuercher @dio Thank you for reviewing it.

/retest

/retest

Needs master merge.

Done.

@zuercher I think this just needs a re-approve but I haven't been tracking carefully.


Control + Tab Never Selects "Overview"

I think it would be nice if we could control+tab to the "overview" tab; at this point the only way to reach it is clicking its tab (as far as I know).

The overview isn't a tab anymore in the new frontend.


feat(TextLink): Add TextLink component

📋 Changes

🤔 Context

✅ Checklist

[x] I have reviewed the submitted code.
[x] I have tested on a phone device/emulator.
[x] If it includes design changes, please ask for a review spark-design GitHub team.

📸 Screenshots

🗒 Other info

@spark-ui-bot paparazzi golden images

@spark-ui-bot paparazzi golden images

@spark-ui-bot Paparazzi golden images


Properly format and reference MIT License

I notice that the content of the LICENSE is in relation to the MIT License, but the normally expected first line is missing

good catch. updated!


Chore/sonarqube lint

Fix some issues reported by sonarqube

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

Comparison is base (cafcd45) 99.73% compared to head (e6943a7) 99.86%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #19      +/-   ##
==========================================
+ Coverage   99.73%   99.86%   +0.13%
==========================================
  Files          13       13
  Lines         754      754
  Branches       20       20
==========================================
+ Hits          752      753       +1
+ Misses          1        0       -1
  Partials        1        1

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


[Feature]: Entity Filter Card

Is your feature request related to a problem?
I would love having an entity filter card configurable!
Describe the solution you'd like
This could show entities only when they are in specific states
Describe alternatives you've considered
No response
Additional context
No response

It's already possible to mix mushroom cards with auto-entities. 🙂


Targets with BeforeTargets="Build" never get executed.

A simple example is:
<Target Name="_ErrWhenExecuted" BeforeTargets="Build">

Add this to any of the Islandwood vcxproj files, and compile it. The target never gets executed.
But BeforeTargets="_ClangCompile" works.

I added the following target to a vcxproj in tools.sln, build.sln, and WOCCatalog-WinStore10.sln. The error text definitely was produced in each build. However, when the error tag was not present, sometimes the msbuild output did not say it was running the target (probably because the target did nothing).
  <Target Name="_ErrWhenExecuted" BeforeTargets="Build">
    <Error Text="Target: _ErrWhenExecuted" />
  </Target>

Also, to execute before Build, I believe it's recommended to override the BeforeBuild target instead.
https://msdn.microsoft.com/en-us/library/ms366724.aspx
I can't find a fault in execution because of this issue. Closing.


Pyzeebe will never time out a connection to a gateway with problems

Describe the bug
If the gateway fails in a certain way, while a connection has been opened to it, Pyzeebe will not time out.
The issue applies both to the client, and the worker.
For the worker, the issue is noticed by it hanging, if it experience loss of connectivity to gateway.
To Reproduce
Start the gateway and brokes (use https://github.com/camunda-community-hub/zeebe-docker-compose/blob/0.26.0/standalone-gateway/docker-compose.yml) – don't run any workers against this cluster.
docker-compose up -d

In a second terminal, run the following code:
import logging
from pyzeebe import ZeebeClient
logging.basicConfig(level=logging.DEBUG, format="%(asctime)s %(levelname)s [%(thread)d|%(threadName)s] %(filename)s:%(lineno)d: %(message)s")

zeebe_client = ZeebeClient(hostname="localhost", port=26500)
zeebe_client.deploy_workflow("tests/integration/test.bpmn")
workflow_instance_key, workflow_result = zeebe_client.run_workflow_with_result(
    bpmn_process_id="test",
    timeout=10000
)
logging.info("Result: %s", workflow_result)

After a few seconds, pause the broker, using
docker-compose pause gateway

What you'll see is that the client waits forever (actually 2 hours) since the broker has gone down:
2021-06-25 14:11:20,716 DEBUG [123145476907008|Thread-2] zeebe_adapter_base.py:51: Grpc channel connectivity changed to: ChannelConnectivity.IDLE
2021-06-25 14:11:20,716 DEBUG [123145476907008|Thread-2] zeebe_adapter_base.py:55: Connected to localhost:26500
2021-06-25 14:11:20,716 DEBUG [123145476907008|Thread-3] zeebe_adapter_base.py:51: Grpc channel connectivity changed to: ChannelConnectivity.CONNECTING
2021-06-25 14:11:20,716 DEBUG [123145476907008|Thread-3] zeebe_adapter_base.py:61: Connecting to localhost:26500.
2021-06-25 14:11:20,718 DEBUG [123145476907008|Thread-4] zeebe_adapter_base.py:51: Grpc channel connectivity changed to: ChannelConnectivity.READY
2021-06-25 14:11:20,718 DEBUG [123145476907008|Thread-4] zeebe_adapter_base.py:55: Connected to localhost:26500

The reason being that the timeout argument is for the server side, and not the client-side.
Expected behavior
If connection to the gateway is lost, Pyzeebe should detect this and throw an error (or retry connection).
Version

Pyzeebe: 0.26.4

Zeebe: 0.26.0

Additional context

https://github.com/grpc/grpc/blob/0e20a5fce8e53510255fa1a5199544a86ebfcd8e/src/core/ext/transport/chttp2/transport/chttp2_transport.cc#L65-L70

By default, the gRPC client will wait for 2 hours (DEFAULT_SERVER_KEEPALIVE_TIME_MS) before trying to check if the server is still up

This has been solved in the official clients:

https://github.com/camunda-cloud/zeebe/issues/3368
https://github.com/camunda-cloud/zeebe/pull/3487

node.js:

https://github.com/camunda-community-hub/zeebe-client-node-js/blob/2b1312dfed027d942a04c8ec6b0eaac3591aee57/src/lib/GrpcClient.ts#L227-L291

C#:

https://github.com/camunda-community-hub/zeebe-client-csharp/blob/af5ed6bfb20c353c5e27a362e8778302c7b22e4c/Client/ZeebeClient.cs#L75-L92

After some experimenting it seems that this:
    def _create_channel(connection_uri: str, credentials: BaseCredentials = None,
                        secure_connection: bool = False) -> grpc.Channel:
        options = (
                ("grpc.keepalive_time_ms", 45000),
                ("grpc.keepalive_timeout_ms", 120000),
                ("grpc.http2.min_time_between_pings_ms", 60000)
        )
        if credentials:
            return grpc.secure_channel(connection_uri, credentials.grpc_credentials, options=options)
        elif secure_connection:
            return grpc.secure_channel(connection_uri, grpc.ssl_channel_credentials(), options=options)
        else:
            return grpc.insecure_channel(connection_uri, options=options)

would fix it.
Do we want these to be changed? Both the java and go clients allow this, but the node client does not.

What about allowing to monkeypatch it if the user wants to change it?
We could define GRPC_CHANNEL_OPTIONS as a dict (that we convert to tuples before using), so the user can do
from pyzeebe.grpc import GRPC_CHANNEL_OPTIONS
GRPC_CHANNEL_OPTIONS.update("grpc.keepalive_time_ms": 5000)

With regards to grpc.keepalive_timeout_ms, grpc.http2.min_time_between_pings_ms – I think we should avoid specifying them, and following the convention in go/java to let the underlying C implementation set the defaults.

I can add this in a PR, though not sure how to test this (except testing that default values, monkeypatching works).

@JonatanMartens See PR. Let me know if you would like this ported to 3.0 branch as well - I see that I can do it quite similarly.
grpc_channel_utils.py
def create_channel(
    connection_uri: str,
    credentials: Optional[BaseCredentials] = None,
    secure_connection: bool = False
) -> grpc.aio.Channel:
    options = get_channel_options()
    if credentials:
        return grpc.aio.secure_channel(connection_uri, credentials.grpc_credentials, options=options)
    if secure_connection:
        return grpc.aio.secure_channel(connection_uri, grpc.ssl_channel_credentials(), options=options)
    return grpc.aio.insecure_channel(connection_uri, options=options)

get_channel_options could perhaps be extended to accept a dict, that allows the user to override variables (using dict merge).

@JonatanMartens See PR. Let me know if you would like this ported to 3.0 branch as well - I see that I can do it quite similarly.

That would be appreciated.

get_channel_options could perhaps be extended to accept a dict, that allows the user to override variables (using dict merge).

Good idea!

I'll keep this issue open until we also fix the 3.0.0 branch.


Add example program

Add an executable under example/ showing how to get up and running with SLEIGH's API. Ideally we'd have something that takes a binary and has an option to print either Ghidra P-Code or the disassembled instructions.

@pgoodman
In order to disassemble or translate to P-Code, you need to give SLEIGH an address range (start address and end address). With LoadImageBDF, this is easy because BDF gives you the ability to jump to the text section and get the correct offsets.
The sleighexample.cc example that SLEIGH provides doesn't use the BDF component but it's a contrived example because the program is an array in memory and the correct offsets are hardcoded in the program. So if we're going to rip out BDF, we'll have to figure out another way of parsing executables and getting this information. Remill must be doing something similar (or is that XEDD's responsibility) so perhaps I can lean on this functionality and feed the offsets into SLEIGH.

Yep, it's definitely easy to give SLEIGH a buffer and offset and just let it do its thing. I was just pointing out that if we want to integrate this elsewhere (like Circuitous) without BDF, we'll need some way of figuring out what start address to feed to SLEIGH.


Add dockerfile for Tegola with config generation

This PR introduces a dockerfile for tegola to ease build process.
It connects to remote postgis and expired imposm3 directory to wipe expired tiles from cache
The docker build operation includes the config.toml file generation with Python help.

@russss would you like to consider again merging this PR at least please?
It shouldn't alter the current running, only providing docker capability for ones who use it.
The only change I notice is to define an env variable DB_URI to allow to Tegola to connect (used in tegola.yml)

Ah, well, the problem is that I've also Dockerised Tegola now but I've done it a different way (see tegola/Dockerfile and tegola/Dockerfile.expiry). Sorry about that, I really should have mentioned in this PR!
I run these containers on top of Kubernetes so the scheduling aspect of the seeding is handled by kubernetes and spawns a new instance of the same Tegola container image (this part is in my kubernetes config which is not public). However even if I wasn't using Kubernetes I'd probably still just use docker run in the host machine crontab in preference to putting cron into the dockerfile (which does complicate things as you've seen).

Oh that's fine. I didn't noticed those new Dockerfiles.
So I close this PR.
Can I propose a slight change to allow selecting the config used at docker build?
It will keep the default to local tegola.yml and layers.yml

Yes, happy to accept a PR for that if it preserves the current behaviour by default.

Wait for it


Update Migration.md - Migration Tool link

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Support unstructured archives [FEATURE REQUEST]

Description

I am working on an algorithm which relies on an unstructured archive. This means the archive doesn't have a grid structure which is known ahead of time. Instead, the archive can grow unbounded and uses a "nearest neighbor" approach to add solutions. Unfortunately, the paper which describes this archive doesn't give a reference to where this type of archive originated so I can't provide a source. The paper I am referencing is here: https://dl.acm.org/doi/abs/10.1145/3583131.3590524
The archive uses a distance parameter $\lambda$ to determine if there is an entry in the "$\lambda$-ball" in measure space and adds the solution in the usual way. This is probably most similar to a CVT archive where the number and locations of the centroids are updated every time a solution is added... For a CVT archive recalculating the centroids can be resource intensive. The unstructured archive differs from CVT and Grid Archives in that the bounds and partitioning of metric space don't need to be known in advance, the number of cells is non-deterministic, and there is no need to calculate centroids for every update.
The specific unstructured archive mentioned here uses a Euclidean distance to determine the cells and whether or not objectives should be compared but this could be made more general to use other methods, such as a density-based approach (if the density of solutions in region of measure space is below a threshold then add the solution unconditionally, otherwise replace the lowest objective solution in the region), energy-based approach, etc.

Hi @gresavage; thanks for reaching out! The archive you mentioned sounds like the one from Novelty Search http://eplex.cs.ucf.edu/papers/lehman_ecj11.pdf Indeed, pyribs does not currently support it, but we have wanted to for a
very long time.
I'll put this on my TODO list, but it may be a while (months) before I can get to it. If you have time to spare, I'd also be willing to guide you through a PR!

@btjanaka Thanks for finding the source!
I am happy to initiate a PR. I have implemented a solution so it should be pretty quick and easy to contribute it to the project... assuming it works as intended :grimacing: . The biggest hurdle I had to solve was filtering the batch-adding of solutions when more than one solution in the incoming batch occupied the same "cell".
I also had the idea of a "lazy" archive where the solution_dim and measure_dim are inferred from the first call to add. I can open a separate issue for the "lazy" archive if you're open to that idea.

Ah nice! Feel free to open a PR. I had some thoughts on such an archive that I can share there.
For the lazy archive idea, I think inferring the dimensions would complicate initialization. For instance, the whole call to ArchiveBase.init would have to be done in a separate method. At the same time, I can see scenarios where you would need to do that. Is there a specific use case you had in mind? Feel free to open an issue and we can talk more there.

@btjanaka Will do! FWIW, you'll see the UnstructuredArchive I implemented is still somewhat structured in the sense that all solutions must have the same solution_dim and measure_dim... since the Novelty Search paper uses NEAT, the topology changes and therefore so too does the solution_dim
I haven't thought yet about how to efficiently implement this degree of "free structure" while keeping with the np.ndarray-based data structure. My first thought is to use a masked array if we are strictly married to an np.ndarray for its compactness and speed.

One idea for variable solution sizes is to make the archive store solutions as objects. Currently, we assume the solutions, objectives, and measures will all be float, but it's certainly possible to have other data types. It's actually a pretty simple implementation given the ArrayStore data structure we use inside the archive, but I haven't had time to figure out the best way to make an API for this on the archive itself. For this implementation, I think it's best to just assume fixed-size continuous solutions for now, and when the different dtypes come along, the archive will easily inherit those changes.
By the way, does your implementation use ArrayStore? One of the reasons that I refactored the archives with ArrayStore was that I envisioned we could use an ArrayStore as the backbone of a novelty search archive. In particular, it would allow easily resizing the archive as the archive expanded (similar to how a C++ vector is implemented) since novelty search's archive is unbounded in size.

Interesting, I had thought briefly of using object dtype, but I haven't ever used NumPy with anything other than the typical int/float/bool/str dtypes so I wasn't sure how well that was supported.
I didn't use the ArrayStore structure - I based my implementation on the v0.6.4 because that was the version I was using in my project and I assumed there wouldn't be significant "breaking" changes prior to a major version release.
I will investigate the ArrayStore structure.

Yup, numpy supports object arrays too. Basically each object is a differently sized array in this scenario.
Regarding changes to the API, yes that's a correct assumption. We tried to minimize the API changes to changing parameter names that people don't really touch anyways, but the archive implementation has major changes to be more flexible, in particular with ArrayStore. Definitely take a look; with some luck it should make your life easier!

@btjanaka I initiated PR #472
Sorry it took so long. Please take a look - I welcome your feedback. I am sure there are probably fancier ways of doing things.

No worries! Thank you so much for working on this. I will take a look shortly.

@btjanaka I may have found an issue with _unstructured_archive.py, line 198
As I was using this in my own code, I found that it was possible for thenp.logical_or to return an empty array. Meaning that none of the top-k neighbors are either in the archive nor will be added.
I am trying to think whether this is a flaw in my implementation or if it is actually possible and expected outcome. The simple solution would be to change this section to instead check the entire archive + batch using the previous results from argsort like so:
        ...
        # find the nearest [k+1]-neighbors to determine the sparsity
        # use k+1 since self is included in the first k-neighbors
        sorted_dist_indices = np.argsort(distances, axis=1)
        top_k = sorted_dist_indices[:, : min(self._k_neighbors + 1, distances.shape[1])]

        # determine which entries can be newly inserted and resize
        # the store to accommodate them
        where_mask = np.zeros(distances.shape, dtype=np.bool_)
        where_mask[np.repeat(np.arange(batch_size, dtype=np.int32)[:, None], top_k.shape[1], axis=1), top_k] = True
        new_entries = np.sqrt(distances[where_mask]).reshape(batch_size, -1).sum(axis=1) / self._k_neighbors > self._sparsity_threshold
        new_entry_indicies = np.argwhere(new_entries) + curr_occ

        # use the nearest index already in the archive or the closest one which
        # will be added
        indices = np.array(
            [
                tk[
                    np.logical_or(
                        tk < curr_occ,
                        np.isin(tk, new_entry_indices, assume_unique=True),
                    )
                ][0]
                for tk in sorted_dist_indices
            ],
            dtype=np.int32,
        )
        ...

Also, I discovered the existence of np.isin which I believe is faster than what I had.


Process terminated due to OutOfMemoryException

Prerequisites

[X] I have written a descriptive issue title
[X] I have verified that I am running the latest version of Nancy
[ ] I have verified if the problem exist in both DEBUG and RELEASE mode (deployed release build and not sure how to reproduce)
[X] I have searched open and closed issues to ensure it has not already been reported

Description
I have an application running as Windows Service. Deployed an update with all the latest NuGet packages less than 24 hours ago, and found out it crashed due to OutOfMemoryException.
I'm not sure if this issue got anything to do with Nancy, but posted here because the stack trace contains reference to Nancy:
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
   at System.Diagnostics.StackTrace.CaptureStackTrace(Int32, Boolean, System.Threading.Thread, System.Exception)
   at System.Diagnostics.StackTrace..ctor(System.Exception, Boolean)
   at System.Environment.GetStackTrace(System.Exception, Boolean)
   at System.Exception.GetStackTrace(Boolean)
   at System.Exception.ToString(Boolean, Boolean)
   at System.Exception.ToString()
   at System.Text.StringBuilder.AppendFormatHelper(System.IFormatProvider, System.String, System.ParamsArray)
   at System.String.FormatHelper(System.IFormatProvider, System.String, System.ParamsArray)
   at Nancy.Hosting.Self.HostConfiguration.<.ctor>b__0(System.Exception)
   at Nancy.Hosting.Self.NancyHost.GotCallback(System.IAsyncResult)
   at System.Net.LazyAsyncResult.Complete(IntPtr)
   at System.Net.LazyAsyncResult.ProtectedInvokeCallback(System.Object, IntPtr)
   at System.Net.ListenerAsyncResult.IOCompleted(System.Net.ListenerAsyncResult, UInt32, UInt32)
   at System.Net.ListenerAsyncResult.WaitCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

Steps to Reproduce
Not sure how to reproduce.
System Configuration

Installed RAM: 32 GB

64-bit OS

Normal RAM usage: < 10 / 32 GB

Nancy version: 1.4.4

Nancy host

Nancy.Hosting.Self (1.4.1)

Other Nancy packages and versions:

Nancy.Bootstrappers.Autofac (1.4.1)
Nancy.Serialization.JsonNet (1.4.1)

Environment (Operating system, version and so on): Windows Server 2012 R2 Standard

.NET Framework version: 4.7.2

Sorry, application crashed again due to OutOfMemoryException, but this time different stack trace. My mistake, closing this as non-issue.


[graphviz] Please enable graphviz customization interface or options tweaking resulting graph

I've used the tool to generate a cartesian product of 3 finite automata, but the resulting graph is huge and when I try to view the picture, it becomes problematic to understand what is happening because the font is very small and the graph nodes themselves are too huge. It would be great if we had the option to select those graph parameters, or even better, introduce some python graphviz interface to be able to configure the graph plot settings to our preferences.

I'll also attach the graph

Hey @sin-diesel thank you for using automathon, I'm gonna be working on it!

Already created new version 0.0.13 you can update and test it @sin-diesel !


Support for stringified booleans

Adds back support for stringified booleans
Ensure this was working in charles proxy and ensured  no negative side effect on integers being passed as 0/1

The following was  tested with this test event using contextValues from this Source
[[SEGAnalytics sharedAnalytics] track:@"Video Playback Started"
                            properties:@{
                                @"channel": @"SegTest",
                                @"video_player": @"Segment",
                                @"title": @"Test Show",
                                @"content_asset_id": @"132421",
                                @"total_length": @"300",
                                @"livestream": @false,
                            }
                             options:@{
                                 @"context":@{ @"video_genre": @NO, @"primary_business_unit": @1 }}

True Test:

False Test:

The s.contextData variable does not directly take a value. Instead, set properties of this variable to a string.
Adobe docs:  https://docs.adobe.com/content/help/en/analytics/implementation/vars/page-vars/contextdata.html


port CM IDs

When completed,

Resolves https://github.com/CM-14/CM-14/issues/270
Resolves #268
Resolves #269
Resolves #265
Resolves #268
Resolves #52

IDs inherit their access from the job they spawn with so this shouldn't require any access code yet

just have to port the civilian(survivor) lanyard ID, and that will be the end of this pr for the basics


Add support for Arbitrarystd::byte

std::byte is not a character or arithmetic type, and so needs its own template specialization. This is implemented by simply wrapping an inner Arbitrary.

Thanks for review! And let me know if I'm screwing up the workflow... I'm far more accustomed to gerrit these days...

This is actually the first time we're doing a code review for a FuzzTest pull request, so I'm also not completely sure about the workflow. :)


New Patch System and Incrementally Updated Js Object for automerge-js

This PR has a few parts

In order to implement the incrementally updated js object I needed object paths instead of just obj ids.  Without this I would need to maintain a elemid <-> index lookup table in memory per list and as we saw in automerge 0.14 this is about as computationally expensive as the whole of automerge.
For the paths to be correct they need to be computed at the moment of op insert - not at commit time.  This is because an op after the one inserting could insert or delete to a parent list changing the list index.
To make this work I had to move the op observer from the commit call to the transaction itself.  I'm mostly but not tally happy with the current implementation especially because there is some confusion between OpObserver being implemented by () and Option<&mut OpObserver>.
The current WASM api (materialize(), registerDatatype(), popPatches(), enablePatches()) is a work in progress and not the final API but are sufficient to meet automerge-jss needs.
AutomergeJS now incrementally updates an in memory representation of the automerge document.  The ability to observer patches is back.  All of this work is done by rust in the automerge-wasm applyPatches() function.

I rebased this and merged it manualley


Q: Authentication with AccessToken, before Router.run

Sorry for posting a question but this thing is making me crazy :).
How my app works: I use react-router 1.0.0-beta3 in my isomorphic react app. The application uses a token to authenticate a user. If a cookie named accessToken is set it means that a user is authenticated. I have to load that token into a store to be able to check for cookie existence isomorphicly (e.g. CurrentUserStore.isAuthenticated()). Each <Router ...> uses onEnter={requireAuthentication} which transition.to('/login') when token is not found.
Q1: Stores must be initialized after calling Router.run so you know what stores should be initialized. But in my case I have to do it before that call otherwise onEnter callbacks will not have the right data and will always redirect to /login. Router.run seams synchronous so it should be fine. Is it?
Q2: Anyway, in my case I have to bootstrap my stores twice - before run to set the token and after run to bootstrap my stores. Is there a better way to do that? My solution is not clean enough.
Q3: Should I ignore isomorphic logic in routes that require authentication?
// SERVER
export default (req, res, next) => {
  let location = new Location(req.path, req.query);

  Alt.bootstrap(JSON.stringify({CurrentUserStore: {user: {accessToken: req.cookies.accessToken}})); // authenticate by setting the token

  // I would do that as
  // let {error, state, transition} = Router.run(routes, req);
  Router.run(routes, location, (error, state, transition) => {
    if (error) return next(error);
    if (transition.isCancelled) return res.redirect(transition.redirectInfo.pathname); // redirect to login, should I ignore that?

    LoadStoresFromState(state).then(snapshot => {
       Alt.bootstrap(snapshot);

       let markup = React.renderToString(<Router {...state}/>);
       let html = Iso.render(markup, Alt.flush());
       res.render('index', {html});
    })
  });
};

I solved it like this:
export default (req, res, next) => {
  cookie.setRawCookie(req.headers.cookie);

  let location = new Location(req.path, req.query);
  Router.run(routes, location, (error, state, transition) => {
    if (error) return next(error);
    if (transition.isCancelled) return res.redirect(transition.redirectInfo.pathname);

    bootstrap(state, req).then(snapshot => {
      Alt.bootstrap(snapshot);

      let markup = ReactDomServer.renderToString(<Router {...state}/>);
      let html = Iso.render(markup, Alt.flush());
      res.render('index', {html});
    }).catch(next);
  });
};


Update README.md

Codecov Report

Merging #156 (e3b4061) into master (3e6035e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #156   +/-   ##
=======================================
  Coverage   56.50%   56.50%
=======================================
  Files          20       20
  Lines        3235     3235
  Branches      479      479
=======================================
  Hits         1828     1828
  Misses       1288     1288
  Partials      119      119

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3e6035e...e3b4061. Read the comment docs.


Is the :arguments option actually used in the plugin?

I was currently testing the arguments option of the rabbitmq output plugin.
Specifically, i tried the 'x-max-length' option like this:
rabbitmq {
...
arguments => { "x-max-length" => 10000 }
...
}

But after checking in the rabbitmq management interface the option doesn't seem to be honored. A quick check at the source code (https://github.com/logstash-plugins/logstash-output-rabbitmq/blob/master/lib/logstash/outputs/rabbitmq.rb and https://github.com/logstash-plugins/logstash-mixin-rabbitmq_connection/blob/master/lib/logstash/plugin_mixins/rabbitmq_connection.rb) suggests, that the :argument option is not used in the code, or did I miss anything?

i was also curious about it. arguments and passive options are queue-specific, though no queue name could be provided and no queue-specific logic exists not in output nor in plugin. from the history, it seems that both options was created on initial commit of the mixin (https://github.com/logstash-plugins/logstash-mixin-rabbitmq_connection/pull/1/files#diff-5a4e6da9864c64f906837378a6f551e6R56) which was "Pulled from the rabbitmq output sources. Modified to be a mixin." by @andrewvc , though no such logic nor option itself was not present in the original output... (relevant commit: https://github.com/logstash-plugins/logstash-output-rabbitmq/commit/bea6ebfae9e7322c47c99a6e7111e6b70a8b42f0)

Apologies here, this seems to have just been an artifact of that being legacy code. I'll try and take a look at it this week.

Is there a fix in progress for this issue?


Fix the anchor regression

It seems https://github.com/tcort/markdown-link-check/commit/65221868bb1101bf211f9791037f304eacf908a2 caused a regression with inline  links.
Trying to see if this is intentional, currently I've only included a unit test to discuss whether the behavior is intentional or not (without including the actual "fix").

markdown-link-check doesn't parse HTML, so it can't find #tomato in your test, but it is something I'm planning on adding.

@tcort do you have an issue tracking <a id=… (or <a name=…) parsing?

@tcort do you have an issue tracking <a id=… (or <a name=…) parsing?

I've created one at #195.


Remove frequency from cloudflare_logpush_job

This removes frequency from cloudflare_logpush_job, as it has been deprecated.

👋 if this is now deprecated, we can instead add the Deprecated attribute to the schema and then in the next major release we can rip it out completely.

👋 if this is now deprecated, we can instead add the Deprecated attribute to the schema and then in the next major release we can rip it out completely.

Ah, cool. Closing this PR in favor of https://github.com/cloudflare/terraform-provider-cloudflare/pull/3745


update path to articles per npm 3

npm no longer nests modules
the path to articles does not need to specify node_modules

Ah this PR already existed!

Apologies, merging the original now!


net: fix TestUDPZeroBytePayload for windows

"It would be nice, if you send change to fix TestUDPZeroBytePayload first - it is OK to break the test on Windows - just skip test on Windows."

alexbrainman - https://github.com/golang/go/issues/26668#issuecomment-408657503

Issue is resolved over in this PR:
https://github.com/golang/go/pull/27446
Updates #26668

Closing as requested here:
https://github.com/golang/go/issues/26668#issuecomment-417995643


COBOL (first) - Allow use of "exotic" EXEC / END-EXEC block in source programs

Description of the enhancement requested
Hi,
We use a product (IBM origin) that requires the use of EXEC / END-EXEC instructions blocks, other than SQL, SQLIMS or CICS, in the source code of programs (COBOL).
These EXEC / END-EXEC are translated to COBOL with a specific preprocessor.
When these programs are edited with IBM Z Open Editor, the (COBOL) Language Server triggers errors, which then invalidates many of ZOE features... 😢
We would like the (COBOL) Language Server to accept others EXEC / END-EXEC blocks than those currently provided (SQL, SQLIMS, CICS), and not trigger errors.
At the textmate grammar level, we should provide a specific scope name for these EXEC / END-EXEC blocks that we could overload with a proprietary "left" textmate grammar in a "language" extension developed by ourself.
Another solution would be to implement a before/after markup system in the form of standardized comments to tell the (COBOL) Language Server to ignore lines of source code that Language Server does'nt support:

*>BEGIN-LS-IGNORE
*>END-LS-IGNORE

Thanks.

Our specific use case, but enhancement should be generic:

Do you think this could be solved by our new preprocessor capability? You could use the Java or REXX samples we provide and adjust them to do this substitution?
https://ibm.github.io/zopeneditor-about/Docs/advanced_preprocessor.html

Hi @phaumer,
In our use case, the preprocessor is a remote processing on mvs.
I don't think that using the preprocessor function meets our needs.
We want to be able to work on the COBOL source code before translating by the preprocessor, and not after this translating.
By the way, how does editing work in ZOE of a source code containing lines of code to be translated by a preprocessor?
The same problem must arise since the lines before processing by the preprocessor are not COBOL lines?
The samples provided make me think more of a "macro" system for quickly writing a program than of a system for extending / enriching the basic language, (like Report Writer, and Exec / End-Exec):

in the case of a "macro" system, we can forget the initial version carrying the macros, then use the output of the preprocessor to continue working on the code after translation,
in a system for extending the basic language, the goal is to work only on the source code before translation.


Enable multi-coord grouping from xarray

I'm working through some around non-trivial groupby from colleagues. In particular, grouping by multiple coordinates seems much harder in xarray than pandas. Flox actually does this really nicely, as per the comment from @dcherian:

As an aside, the API isn't great but this works in flox (I think)

import flox.xarray

flox.xarray.xarray_reduce(da, "labels1", "labels2", func="mean")

Originally posted by @dcherian in https://github.com/pydata/xarray/issues/9278#issuecomment-2250993016
Would be great if da.groupby(["labels1", "labels2"]).mean() worked too — is that just a simple translation to flox from the xarray code? (I can probably do it if so). Or is there something more complex going on?

from https://github.com/pydata/xarray/issues/6610#issuecomment-1523666774 the idea is to eventually support
data.groupby({"labels1": xr.UniqueGrouper(), "labels2": xr.UniqueGrouper()}).mean()

As far as I remember, multi-dimensional groupby is planned but not supported yet. What we'd need to do is remove the condition here: https://github.com/pydata/xarray/blob/ce5130f39d780cdce87366ee657665f4a5d3051d/xarray/core/dataset.py#L10388-L10393 and make sure the loop still works (@dcherian will have more details).

from #6610 (comment) the idea is to eventually support
data.groupby({"labels1": xr.UniqueGrouper(), "labels2": xr.UniqueGrouper()}).mean()

Great!
I would have also supported data.groupby(["labels1", "labels2"]) as syntactic sugar (which pandas supports) but I would need to read more to have a confident view...

Yes I have struggled to fully generalize it.
That said, we could just begin with simply supporting _flox_reduce. This should be a straightforward extrapolation of what's already there.


Doc improvement: Link to Written Guide for Key/ID

The video linked for key/id retrieval seems complete, but a written version could be faster and more accessible for some users.  This writeup worked for me.

Thanks, been doing a docs rewrite, and will link them to this.


Run SQL in-memory with yarrow

Convert full rewritten SQL AST to yarrow analysis graph to run whole query in-memory

Will not implement; pandas and PySpark are sufficient