e2e: Check that we are testing the correct version

Make use of crc version output to cross check that we are indeed testing the expected CRC version. Because version is so unique, it is enough to check for containment. If we start releasing *-ec and similar variations, this might need to be changed to matching instead of containing.
In the case of this CI, this PR has no effect -- if VERSION_TO_TEST is set to --crc-version="" (default), then version is not checked. I manually checked the first Scenario in basic.feature which is affected if version is passed:
Log successfully started, logging into: /home/jsliacan/Github/crc/test/e2e/out/test-results/e2e_2023-3-8_15-21-12.log
Running e2e test in: /home/jsliacan/Github/crc/test/e2e/out/test-run
Working directory set to: /home/jsliacan/Github/crc/test/e2e/out/test-run
Using existing bundle: /home/jsliacan/Downloads/crc_libvirt_4.12.5_amd64.crcbundle
Feature: Basic test
  User explores some of the top-level CRC commands while going
  through the lifecycle of CRC.

  Scenario: CRC version                        # features/test.feature:8
    When executing crc version command         # testsuite.go:868 -> github.com/crc-org/crc/test/e2e/testsuite.ExecuteCRCCommand
    Then stdout should contain correct version # testsuite.go:600 -> github.com/crc-org/crc/test/e2e/testsuite.CommandREturnShouldContainCorrectVersion
Deleted CRC instance (if one existed).

1 scenarios (1 passed)
2 steps (2 passed)
58.890846ms
ok  	github.com/crc-org/crc/test/e2e	0.085s

Make use of crc version output to cross check that we are indeed testing the expected CRC version. Because version is so unique, it is enough to check for containment. If we start releasing *-ec and similar variations, this might need to be changed to matching instead of containing.

@jsliacan I don't see how it will used to check for containment . Current crc version output bunch of things like openshift/podman version. and if we want to check a released binary vs nightly bits then you first need to know the version of nightly bit and figure out. I think what we should do as part of makefile v$(CRC_VERSION)-$(COMMIT_SHA) as default version like we are doing for CRC_E2E_IMG_VERSION ?

I retested it, because even though the last commit is a5e3f27, I was seeing this failure:
Then stdout should contain correct version # testsuite.go:600 -> github.com/crc-org/crc/test/e2e/testsuite.CommandREturnShouldContainCorrectVersion
output did not match. Expected: '2.15.0+8729c83b', Actual: 'CRC version: 2.15.0+8729c83
OpenShift version: 4.12.5
Podman version: 4.3.1'

Not only do I see a5e3f27 as the last commit, but I can't even find 8729c83b among commits. And I most definitely don't know why there's b at the end of it compared to the output of crc version: 8729c83.
When I run it locally, it passes fine...

@praveenkumar yes, the error complains that expected: 26fb4fed and actual: 26fb4fe don't match. However, the last commit on my branch is: 2381736. So I have to investigate a bit further.

/hold

/unhold


Geolocation issues

Geolocation issues
Open-webui suddenly began to ask for geolocation before sending anything to the models (local ollama models and API models alike), and fail
Expected Behavior:

should not require geolocation
should work whether geolocation allowed or not

Actual Behavior:

fail in both case (except on brave, where it works when geolocation is allowed)

steps to reproduce

when i deny the geolocation, i just get an error : Unknown error acquiring position and user denied geolocation, and then i can't use open-webui

In Firefox, when allowing the access to my geolocation, the UI get unresponsive and i can't interact with it anymore

In chromium, when allowing the access to my geolocation, i get Failed to query location from network service. Check the DevTools console for more information.. In the console i get the following errors :

Network location provider at 'https://www.googleapis.com/' : Returned error code 429.

index.ts:386 Error getting user location:
GeolocationPositionError {code: 2, message: 'Failed to query location from network service. Check the DevTools console for more information.'}
code
:
2
message
:
"Failed to query location from network service. Check the DevTools console for more information."
[[Prototype]]
:
GeolocationPositionError
(anonymous)	@	index.ts:386
Promise.catch
re	@	index.ts:385
V	@	index.ts:259
bt	@	Chat.svelte:1518
await in bt
(anonymous)	@	Chat.svelte:1020
await in (anonymous)
pt	@	Chat.svelte:962
await in pt
me	@	Chat.svelte:896
await in me
hl	@	Chat.svelte:2320
await in hl
(anonymous)	@	lifecycle.js:105
(anonymous)	@	lifecycle.js:104
X	@	Placeholder.svelte:212
(anonymous)	@	lifecycle.js:105
(anonymous)	@	lifecycle.js:104
Nt	@	MessageInput.svelte:545
(anonymous)	@	lifecycle.js:105
(anonymous)	@	lifecycle.js:104
Enter	@	RichTextInput.svelte:321
(anonymous)	@	index.js:99
(anonymous)	@	index.js:3132
someProp	@	index.js:5490
ce.keydown	@	index.js:3132
t.dom.addEventListener.t.input.eventHandlers.<computed>	@	index.js:3052

It weirdly seem to work fine (with geolocation on) in Brave (when disabling any "brave shield")

Installation Method
i run open-webui in docker, with docker-compose :
services:
  open-webui:
    image: ghcr.io/open-webui/open-webui:main
    container_name: open-webui
    ports:
      - 3000:8080
    extra_hosts:
      - host.docker.internal:host-gateway
    volumes:
      - ./open-webui:/app/backend/data
    environment:
      - OPENAI_API_BASE_URLS=${OPENAI_API_BASE_URLS}
      - OPENAI_API_KEYS=${OPENAI_API_KEYS}
    restart: unless-stopped

Environment

Open WebUI Version: v0.3.35

Operating System: ubuntu 22.04.5

Browser (if applicable): Firefox 131.0.3, Chromium 130.0.6723.69, Brave v1.71.118

Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I am on the latest version of both Open WebUI and Ollama.
[x] I have included the browser console logs.
[ ] I have included the Docker container logs (nothing relevant there)
[x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Addendum : only happens if i use a system prompt (any content)


ci: basic integration test framework

A modified (imho slighty improved) take on the integration framework proposed in #6218.
Example run: https://github.com/meltano/meltano/actions/runs/2578001545
And inline below:

Dir/file layout:

docs/example-library/<test-name> holds the markdown guide/test and the meltano YAML files. I opted to include both the starting and ending YAML files here. Including the "ending" or resulting YAML config was something that I saw https://buf.dev did in their guides that was subtle but appreciated (since it lets impatient users like me jump ahead). Since we need this file to diff against anyway I went a head included there.

Open Question: Do we want to make these actual pages on the docs site ? If so I'll probably need to adjust the paths some and include the Jekyll preamble in the index.md's.

integration/ holds the integration framework.

integration/validate.sh the main entry point for all integration tests. It takes care of producing the script from the markdown, injecting a logging YAML, diffing the meltano yaml's, and calling the additional per-test validations when required.
integration/<test-name>/validate.sh - optional additional tests to run for a test. Often, this won't even be needed, but the ability is available if you want to run extended checks (i.e. grepping logs, running sql, etc)

Status: still a WIP (hence being a draft still) so don't need an exhaustive review, but looking for early feedback (cc @aaronsteers @afolson ) to make sure I'm on the right path.

Updated to now also include:

shell linter check based on shellcheck for integration scripts
jsonschema validation check of sample meltano.yml's. closes #6181

One request on my side to perhaps beef up contributor docs - either in the examples readme or in the contributors guide.

Absolutely, just wanted to make sure i was on the right path before going through and documenting all the things.

Theres still a larger open question of exactly when these should run and what all tests we want to add out of the gate, but i think as a "get some scaffolding up and running" this is ready to review/merge.

Given the (elapsed) runtime is just 2.5 minutes, I think it's totally fine to run on each build.
Based on: https://github.com/meltano/meltano/actions/runs/2584765141

Given the (elapsed) runtime is just about 2.5 minutes, I think it's totally fine to run on each build.

Yea was actually more concerned about the total volume of CI minutes used if we have a ton of tests , but I just realized this isn't a private repo so the smaller billing limits don't apply 🥳


How to fine-tune it

It seems that a pre-trained language model. Could i run train on a lot of unconditional text to get a checkpoint  then fine-tuning the model on Seq2seq tasks?

Sure! (Continue) pre-training and finetuning with the diffusion objective are both supported.


CrateDB 5.8.4 no longer accepts ARRAYs with varying inner types in OBJECT(IGNORED) columns

CrateDB version
5.8.4
CrateDB setup information
Standard Docker.
docker run -it --rm --publish 4200:4200 --env CRATE_HEAP_SIZE=2g crate/crate:5.8.4 crate -Cdiscovery.type=single-node

Problem description
While it still works in 5.8.3, when using CrateDB 5.8.4, it no longer accepts storing ARRAYs like [42.42, "foo"]. We are using that capability of CrateDB when importing data from DynamoDB, where we are deferring data into a OBJECT(IGNORED) column, that can not be stored into a OBJECT(DYNAMIC) column.
Steps to Reproduce
DROP TABLE IF EXISTS t01;
CREATE TABLE IF NOT EXISTS t01 (data OBJECT(IGNORED));
INSERT INTO t01 (data) VALUES ('{"items": [42.42, "foo"]}'::json);
REFRESH TABLE t01;
SELECT * FROM t01;

Actual Result
SQLParseException[Mixed dataTypes inside a list are not supported. Found double precision and text]

Expected Result
INSERT OK, 1 row affected (0.008 sec)

# SELECT * FROM t01;

+---------------------------+
| data                      |
+---------------------------+
| {"items": [42.42, "foo"]} |
+---------------------------+

Hi @amotl, thanks for catching! It was a regression introduced in 5.8.4 fix will be available in the next 5.8.5 hotfix release.

Thank you for providing a quick fix!


Add whileloop to avoid incomplete URL

Add While loop to rerun function till it gets right URL.
reason
sometimes module gives
https://streamtape.com/get_video  as output. To solve this I added while loop.

This project is no longer maintained i think.


How to install MAJA 4 in Ubuntu 20.04 and Docker

This is not a typical issue, but a step by step example of how to install MAJA 4 in Ubuntu 20.04 and Docker.
Assumption: Docker is already installed.
Get Ubuntu 20.04 Docker container and go into the container
docker run -d -it --restart=always -v /srv/data:/data --name Maja4-Ub20 ubuntu:20.04 /bin/bash
docker exec -it Maja4-Ub20 /bin/bash

/srv/data is a data folder, which is linked into the container (to /data)
Install dependencies
apt -y update
apt -y install libffi-dev
apt -y install mono-complete
apt -y install bison flex
apt -y install libpcre++-dev
apt -y install wget
apt -y install lsof

Download and install binaries from CNES
https://logiciels.cnes.fr/en/node/58?type=tel
Optionally build MAJA from source
# install build dependency
apt -y install build-essential cmake pkg-config
apt -y install cmake-curses-gui
apt -y install git
apt -y install tmux

# build maja
mkdir /root/software
cd /root/software
git clone https://github.com/CNES/MAJA.git
cd MAJA
mkdir build
mkdir install
cd build
cmake ../SuperBuild -DDOWNLOAD_DIR=../SuperBuild-archives/ -DENABLE_TU=OFF -DENABLE_TV=OFF -DENABLE_TVA=OFF -DCMAKE_INSTALL_PREFIX=`pwd`/../install
make -j4

Start maja
Configure folders.txt according to https://github.com/CNES/MAJA
In case CAMS should be activated (--cams) follow https://github.com/CNES/MAJA#download-cams-data and download the cams data before
L1C data structure example (without specifying a site)
/data/sentinel_products_L1C-test/33UWP/S2A_MSIL1C_20200909T095031_N0209_R079_T33UWP_20200909T110415.SAFE
Start maja in case it is installed from the binary package in the default folder
/opt/maja/MAJA-4.2.1/bin/startmaja -f folders.txt -t 33UWP -d 2020-01-01 -e 2020-07-01 -v --type_dem srtm

...or start maja if it is built from source
/root/software/MAJA/install/maja/4.2.1/bin/startmaja -f folders.txt -t 33UWP -d 2020-01-01 -e 2020-07-01 -v --type_dem srtm

@c00kiemon5ter would be nice if you could test the steps.
@olivierhagolle, I had a discussion with Ivan on how to install Maja in Ubuntu. I thought it might be also interesting for other people and started a new thread. I hope that's o.k.?
@olivierhagolle and @petket-5 I hacked a line into startmaja to configure the Muscate format. Is there a proper method to configure it? It might be nice to have a command-line option.

Hi @jprankl
sorry, we are a bit too busy these days to reply quickly, but it's more OK, thanks a lot for this contribution !

Thanks a lot @jprankl for this information.
I've created a repo with a proper Dockerfile in case anyone is interested in the future.
https://github.com/rohitshetty/maja-docker
This compiles the Maja from the develop branch from gitlab.
But for some weird reason make binpkg fails, so cannot yet create a standalone binary, but rest of it works.

Thanks a lot @jprankl for this information.
I've created a repo with a proper Dockerfile in case anyone is interested in the future.
https://github.com/rohitshetty/maja-docker
This compiles the Maja from the develop branch from gitlab.
But for some weird reason make binpkg fails, so cannot yet create a standalone binary, but rest of it works.


Remove python version from language info metadata.

Fix #49.

Modify clean_notebook to remove python version from language info metadata.
Make check_notebook return False if the notebook contains python version in language info metadata.
Add test cases

$ poetry run pytest
================================== test session starts ===================================
[...]
tests/test_check_notebook.py .......                                               [ 20%]
tests/test_clean_notebook.py ....                                                  [ 31%]
tests/test_cli.py ..............                                                   [ 71%]
tests/test_git_integration.py ..........                                           [100%]

=================================== 35 passed in 0.23s ===================================

Thanks @jbfiot! I merged this locally so I could rebase it, and have pushed it up to main.

I've just released v2.1.0 to PyPI, which contains this functionality.


bpftools: fix cross

https://github.com/NixOS/nixpkgs/issues/366859

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Applying the<EMAIL_ADDRESS>fix native and cross builds for riscv64, tested using this diff:
diff --git a/pkgs/by-name/bp/bpftools/package.nix b/pkgs/by-name/bp/bpftools/package.nix
index 88ec301bc356..9fec63c2ff9e 100644
--- a/pkgs/by-name/bp/bpftools/package.nix
+++ b/pkgs/by-name/bp/bpftools/package.nix
@@ -1,6 +1,7 @@
 {
   lib,
   stdenv,
+  fetchpatch,
   linuxHeaders,
   buildPackages,
   libopcodes,
@@ -25,6 +26,13 @@ stdenv.mkDerivation rec {
   patches = [
     # fix unknown type name '__vector128' on ppc64le
     ./include-asm-types-for-ppc64le.patch
+    # fix build for riscv64
+    (fetchpatch {
+      # tools: add forwarding header for arch/riscv/include/asm/fence.h
+      #<EMAIL_ADDRESS>+      url =<EMAIL_ADDRESS>+      hash = "sha256-xFLwWuuymim5m8UjZDOeH9KSOqbL6Nv7frasuCaMpnM=";
+    })
   ];

   depsBuildBuild = [ buildPackages.stdenv.cc ];

Patches mentioned here aren't fixing the cross builds...


The demo site still uses Lychee-3.2.8

Go to https://lycheeorg.github.io/demo/
Try to login. You get "Lychee 3.2.8 - Update available"

Yeah. I need to regenerate it.

Ping, you should demonstrate v4 now

Yeah. I need to regenerate it.

oupsie.

Yeah. I need to regenerate it.

oupsie.

done.

done.


Harbor fails to show vulnerability severity "critical" (actually Harbor seems to treat "critical" as "unknown") whereas vulnerability db contains "critical" severity

First, Clair vulnerability database used by vmware/clair-photon:v2.0.1-v1.4.0 contains vulnerability severity "critical/high/medium/low":

Also, according to Clair project clair/ext/vulnmdsrc/nvd/nvd.go, it says that Clair complies with CVSS3.0 spec which contains "critical/high/medium/low" vulnerability severity:

SeverityFromCVSS converts the CVSS Score (0.0 - 10.0) into a database.Severity following the qualitative rating scale available in the CVSS v3.0 specification (https://www.first.org/cvss/specification-document)

func SeverityFromCVSS(score float64) database.Severity {
	switch {
	case score < 1.0:
		return database.NegligibleSeverity
	case score < 3.9:
		return database.LowSeverity
	case score < 6.9:
		return database.MediumSeverity
	case score < 8.9:
		return database.HighSeverity
	case score <= 10:
		return database.CriticalSeverity
	}
	return database.UnknownSeverity
}

However, in harbor/src/common/utils/clair/utils.go, it looks like Harbor parse only "high/medium/low" vulnerability severity, and set others to default "unknown".
This causes a severe problem: Harbor not only makes "critical" vulnerability disappear on UI but misclassify "critical" vulnerability as "unknown":
harbor/src/common/utils/clair/utils.go:
func ParseClairSev(clairSev string) models.Severity {
	sev := strings.ToLower(clairSev)
	switch sev {
	case models.SeverityNone:
		return models.SevNone
	case models.SeverityLow:
		return models.SevLow
	case models.SeverityMedium:
		return models.SevMedium
	case models.SeverityHigh:
		return models.SevHigh
	default:
		return models.SevUnknown
	}
}

Since that "critical" severity is quite different from "unknown" severity, I think it should be necessary to show "critical/high/medium/low" vulnerability severity accordingly to avoid misleading!

docker 17.03.2-ce, docker-compose 1.16.1, Harbor v1.4.0 release

@jeffweilee May I know did you see this issue in any image from docker hub?  I'm thinking we should add a testcase in E2E test.


Programmatically generate open graph metadata for articles

http://ogp.me/

closing b/c scope of CMS has changed to backend-only


Automatically reload/load live stream without refreshing page

Is there a way to get clappr to keep checking for an hls stream without the client refreshing the page?
Maybe a retry mechanism? (Not even really sure what that is)
Sorry, I'm very very new to code...trying to work through this.
Error Code: Cannot load https://parkland.phxcdn.com:8443/live/parklandhs/index.m3u8HTTP response code:404 Not Found
37.031 | A network error occured
`

`

Take a look at Player Error handling documentation.

Still a bit confused by this. Is there an easy fix where I can just enter a line of code to have this work? Again, very very very new to all of this...

Try this code on Clappr demo page : it retry the stream each 10 seconds on error :
var playerElement = document.getElementById("player-wrapper");

var player = new Clappr.Player({
  source: 'https://parkland.phxcdn.com:8443/live/parklandhs/index.m3u8HTTP',
  disableErrorScreen: true, // Disable the internal error screen plugin
  height: 360,
  width: 640,
  events: {
    onError: function(e) {
      setTimeout(function() { player.configure(player.options); }, 10000);
    }
  }
});

player.attachTo(playerElement);

Would this replace my entire video player code or would I add this to my existing code?

The only "parts" you may have interest are disableErrorScreen and events player configuration options.


Popup: key ordering

Make mock show an example of key ordering in the popup.
An example in mock-extension.buildInfoWinTemplate:
var displayedAttributes={
"Percent": attributes.percent, //brings it to the top, renaming the field (the original key name with also be put in below)
"color": attributes.color //Will be overwritten below, but keeps it's place at the top
};
foreach(attributes, function(key, val){
displayedAttributes[key] = val;
});
NOTE: This will cause a conflict with #304 if done before #304 is merged.

No pull request, doesn't need to be done


Allow Launcher to self-configure Kubernetes

Now that Launcher supports self-configuring Kubernetes, we no longer have to dynamically generate the launcher.kubernetes.conf file.
In addition, these changes also support multiple [cluster] sections in the launcher.conf file.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@colearendt This is now ready for review.

This also addresses #180

@colearendt Have you had a chance to play with these changes yet?
If they look good, I will go ahead and update the chart in this PR.

Resolved merge conflicts and fixed a little bug in the default values that made templating fail (when .serviceAccountCreate is empty (the default)). I think this should be good to go! Just need to sanity check that all the version numbers match - will try to do that later tonight


Refacto examples

Description
Import and call systematically regression_mean_width_score and classification_mean_width_score in examples.
Fixes #139
Type of change
Please remove options that are irrelevant.

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
By compiling the doc locally and checking consistency with online website readthedocs.
Checklist

[x] I have read the contributing guidelines
[x] I have updated the HISTORY.rst and AUTHORS.rst files
[x] Linting passes successfully : make lint
[x] Typing passes successfully : make type-check
[x] Unit tests pass successfully : make tests
[x] Coverage is 100% : make coverage
[x] Documentation builds successfully : make doc

Looks good to me !

Looks good to me !


Hipchat has more detailed logs then Slack?

Is it possible to have more detailed logs on Slack?
On Hipchat, I get where request was sent and then completely detailed critical error/exception.
On Slack, I get just where exception has happened, without any details about request.

I guess this is due to the fact Slack doesn't include context info and includes extra only optionally. You could try to enable the $includeExtra param in the constructor, and then possibly we should fix the handler to include context also when includeExtra is on.

Thanks for the answer. Hopefully I will have time to check it and maybe even contribute.

I think this has been resolved by #507


Invalid Resource 400 - Interests

Hi,
Trying to understand the following issue. When interests is an empty array I receive the following error:
        $this->mailchimp->put("lists/$list/members/" . md5($email), [
            'email_address' => $email,
            'status' => 'subscribed',
            'merge_fields' => [
                'COUNTRY' => 'foo'
            ],
            'interests' => [],
        ]);

array:6 [▼
  "type" => "http://developer.mailchimp.com/documentation/mailchimp/guides/error-glossary/"
  "title" => "Invalid Resource"
  "status" => 400
  "detail" => "The resource submitted could not be validated. For field-specific details, see the 'errors' array."
  "instance" => ""
  "errors" => array:1 [▼
    0 => array:2 [▼
      "field" => "interests"
      "message" => "Schema describes object, array found instead"
    ]
  ]
]

Is that normal? Why I can't give an empty array?
Thank you (your package is awesome!)

That is the expected response as Mailchimp expects an empty here. You can use new stdClass eg.
$a = [
    'array' => [],
    'object' => new stdClass,
];
json_encode($a);
// {"array":[],"object":{}}

still get this error, despite the commit.


No way to cancel invalid bulk change request

on trying to replace admin contacts on multiple domains with another one i received an error message:
Admin contacts must be identical
That is expected as old and new contact do not share identical ident data. THat being said the error message could be more specific saying "New and old contacts' ident data must be identical"
There is no way to cancel the bulk change request. meaning even if i leave the view, refresh the portal, when i press again in the bulk change link i am brought back to the previous unsuccessful bulk change request with no way to change nor cancel it. Being stuck with this:

OK


chore(build): drop webpack and use Hugo Pipes

This PR drops webpack and uses Hugo Pipes's SASS/SCSS processor.
Refs: https://gohugo.io/hugo-pipes/scss-sass/

Any updates?

Thank you for your effort!


add segment download implementation to controller

JIRA link (if applicable)

https://tools.hmcts.net/jira/browse/EM-3175

Change description

implement recording segment download feature

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

merged ahead of test coverage being completed


Invalid Discord link

Invite Invalid error

Thanks for letting me know.
I've created a new link: https://discord.gg/cJeVygB
I'll update the readme later when I get home, leaving issue open till I do that.

Thanks 👍


bumped capability ID of the push_batch_votes rpc

We added an extra field to the Batch message, without considering the fact that an extra field won't be recognized by old binaries and they will fail to verify signatures on Batch messages. They will consider sending such invalid signatures malicious and will disconnect from the peer. To avoid this we create a new RPC instead (by just bumping the capability id on push_batch_votes RPC) which will not be interpreted by the old binaries at all.

we have a test for this, but you can always forget to add the ID to the test


[boost-di]

Existing port boost-di is missing.
Last week i won't face this problem. Today I try to install today boost-di dependency but i face the below error messages:
Error: while loading boost-di:
The port directory (C:\Users\User\Libs\vcpkg\ports\boost-di) does not exist
Error: failed to load port from C:\Users\User\Libs\vcpkg\ports\boost-di
Note: Updating vcpkg by rerunning bootstrap-vcpkg may resolve this failure.
I follow the below steps many times still the problem exists
Note: Updating vcpkg by rerunning bootstrap-vcpkg may resolve this failure.

After i find the solution from this link https://github.com/microsoft/vcpkg/pull/16302


Add Gymnasium Nepomucenum Coesfeld (Germany)

@Lutz-Pfannenschmidt First stage of verification passed, official domain is nepomucenum.de as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://www.nepomucenum.de/aktuelles/digitalisierung-aktivierung-des-iserv-systems-in-der-schule/

@Lutz-Pfannenschmidt Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Sweep: Remove code of the challenge-response-auth feature

Sweep: Remove all code of the challenge-response-auth feature from the following files:

authenticator.rs
command.rs
state.rs

Checklist

[X] src/command.rs

Remove all instances of the #[cfg(feature = "challenge-response-auth")] attribute and the associated code blocks.
• Check for any dependencies on the challenge-response-auth feature within the remaining code and address them as necessary.

[ ] src/state.rs

Remove all instances of the #[cfg(feature = "challenge-response-auth")] attribute and the associated code blocks.
• Check for any dependencies on the challenge-response-auth feature within the remaining code and address them as necessary.

sweep: Add an empty commit to https://github.com/szszszsz/trussed-secrets-app/pull/4 to trigger the CI build.

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!


Adding an Amazon site

Adding code for amazon to the sites file would be a cool idea. Anybody know or willing to try and do that?

Fairgame is supposed to be able to do Amazon.

Fairgame is supposed to be able to do Amazon.

Test
On Tue, Jan 19, 2021 at 7:52 PM Joatnm<EMAIL_ADDRESS>wrote:

Fairgame is supposed to be able to do Amazon.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/natewong1313/bird-bot/issues/78#issuecomment-763248288,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJQ7L4ED6BSOXXYVYRRDF2LS2YSODANCNFSM4UZKHBOQ
.

Test
On Tue, Jan 19, 2021 at 7:52 PM Joatnm<EMAIL_ADDRESS>wrote:

Fairgame is supposed to be able to do Amazon.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/natewong1313/bird-bot/issues/78#issuecomment-763248288,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJQ7L4ED6BSOXXYVYRRDF2LS2YSODANCNFSM4UZKHBOQ
.


Use getSentinlClient from Kibi access control, renamed getSentinelcli…

…ent to getElasticsearchClient

I believe this is no longer needed after the merge. please reopen if I'm wrong ;)


Comparison to node.js

Could you add performance numbers for node.js to compare to your benchmarks?

You can see benchmark results of Haywire versus different web servers here.
https://www.techempower.com/benchmarks/#section=data-r10&hw=peak&test=plaintext


Tunnel.Consumer is empty when using @stencil/router >0.2.6

I finally figured out what was causing my problems in #5
it looks like stencil router is pulling in the consumer as well, but your docs are using ion-router which appears to work.
Should we be using ion router instead?

@joelalejandro it looks like youre using an old version of router in https://github.com/counterfactual/monorepo/blob/master/packages/dapp-high-roller/package.json (0.2.6)
Youre also not pulling in state-tunnel as a dependency, and therefore using the state-tunnel through the one that router is getting.
So looking at your yarn.lock:
https://github.com/counterfactual/monorepo/blob/master/yarn.lock#L755-L784
Maybe one of your other apps is pulling in the other version of state-tunnel - but you get 0.0.91 from the router, and when i use yarn add @stencil/state-tunnel it gives me 0.0.8 - and if I have both state-tunnel and router as dependencies, typescript blows up saying that the consumer component has already been defined.
I'm really at a loss atm, I can't get state-tunnel consumer working at all.  I can if I rebuild an app from scratch, but whats really throwing me off right now is that the dependency versions all over the place, like maybe I have to get my versions all exact for it to work.  I did not have any issues at all until I updated stencil's core.  Are they even doing integration testing between their components? I swear something is going on

Oh right, I do remember we are forced to use<EMAIL_ADDRESS>We got it working with the following versions:
@stencil/core: 0.15.2 (or 0.16.0)
@stencil/router: 0.2.6
@stencil/state-tunnel: 0.0.8
And yeah, I know what you mean. Stencil works great with Web Components, but it looks like beyond that, the developer experience is a bit clunky yet.

Your suggestion fixed my issue.  We probably want to leave this open as stencil should-state-tunnel should probably work with the latest version of router and core. I'm going to rename this topic.

Glad to hear @MattMcFarland! Yeah I agree, let's keep the issue open :)

If by empty you mean that it renders an empty <tunnel-consumer></tunnel-consumer>, then we have the same problem here, but only on Windows. My work mate was just telling me about some components not rendering, and I couldn't reproduce on Mac, so I got her to share her screen and saw that empty tunnel consumer. Tried a couple things, like upgrading to 0.0.9-5 but didn't help. Wondering whether all those Stencil fixes related to paths on Windows are going to help... will try to migrate our code base next week.


Add option to delete multiple messages at once

No content

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @CSab6482 in #requests.

Completed in full rewrite


handling date with ajv

Hello, I have a question with the type "format", in my properties I add dateOfBirth and this has to be dates higher than '2002-01-01 "and I do it with the example that is in the documentation:
" format ":" date "
"formatMaximum": "2016-02-06",
"formatExclusiveMaximum": true
but when I send a date higher than '2002-01-01 ", the error is not triggered, thanks for reading, I would appreciate an answer please
my code:
allOf: [
{
properties: {
email: {
type: 'string',
format: 'email',
},
password: { type: 'string', minLength: 6 },
dateOfBirth: {
type: 'string',
format: 'date',
formatMaximum: "2002-01-01",
formatExclusiveMaximum: true
    },

}
}
]

It is not possible to say what is wrong without the full code sample reproducing the issue, but possibly you are not adding custom formatMaximum etc. from ajv-keywords. If you do still have the issue with them please resubmit the full code sample to that repo.


1.0.2 - devicePixelRatio causes responsive:true to result in the wrong size (growing chart)

When the browser has a devicePixelRatio, a CSS height and width are defined on the canvas. The physical height of the element (clientHeight) is determined by this height. When the resize method runs, it updates the canvas.height property to resize the element. If the device's devicePixelRatio is greater than 1, what that means is that the height is set to a value greater than it should be set.
The net result is that resizing the element causes it to grow on each resize event.

:+1: I am being plagued by the same problem.

Hello, today I am closing all issues that are only affecting version 1 of Chart.js as WONTFIX.
If this issue does affect version 2 as well, I apologize for the error. Please create a test case against Chart.js 2 using on of the below websites and we will be happy to reopen the issue and update its classification:

http://jsbin.com/
http://jsfiddle.net/
http://codepen.io/pen/
Premade template: http://codepen.io/pen?template=JXVYzq

I experience this issue in version 2.5.0

still exists in 2.7.3

I'm having a similar issue where my chart grows out of control on page load.
It seems to be related to the generateLegend() function.
https://jsfiddle.net/up9beo1v/58/

I have the same issue@asrz chart growing

Same issue, triggered by floating component sibling to the div wrapping the canvas.

FWIW: In my case it I could set "maintainAspectRatio":true to stop the height growing.

For me wrapping with a div classed "relative" helped.

For me wrapping with a div classed "relative" helped.

chartJs has any class with the relative that is used? I just want to understand why this works.

@TheoOliveira It's part of their documentation: https://www.chartjs.org/docs/latest/general/responsive.html#important-note

Sorry to comment on a closed issue but I am also facing this for a chart that needs to be responsive. None of the solutions here work for me and the chart continues to grow on the width beyond the parent and the page.
My use case is that the chart is inside a flex container which uses 100% of the available width. I do not know what the vw (or vh) will be - because its responsive. Therefore I have use width: 100%.
This container is relatively positioned and dedicated to the chart canvas only, as advised in the docs. However I need this container to fill 100% of the width of the parent - so have width 100% which seems to cause the problem. Having no height or width, or a fixed height and width, does not cause the chart to increase in width, but obviously this is not responsive.
Setting maintainAspectRatio: false as advised, just causes my graph to grow indefinitely until the browser uses so much memory it crashes.
It seems to be that I cant use ChartJS responsively at all. The only way is if I know exactly what vh/vw it needs, which seems to completely defeat the purpose of responsive?

I got the exact same problem. In Firefox on mobile, my charts keep growing horizontally until after a few seconds the browser crashes. Unfortunately, the solution proposed by @alex-r89 did not work and neither did wrapping the canvas element inside a relative positioned div. Any other ideas?

Please create a new issue, unless you are still using version 1.0.2 this issue is valid for.


Docs: Write Setup Docs

Need to write docs on how to set up Gnerate.
generate --init will provide a base config file, but still need to describe what templates are, and the templates directory.

The high level of the docs is done.


pip doesn't seem to pick up the luckydonald-utils dependency

I know i could just install it but i'd expect it to just work™
$ sudo pip install pytg
[sudo] password for dx:
Collecting pytg
  Downloading pytg-0.4.2.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 20, in <module>
      File "/tmp/pip-build-73hkqbzs/pytg/setup.py", line 8, in <module>
        from pytg import VERSION
      File "/tmp/pip-build-73hkqbzs/pytg/pytg/__init__.py", line 9, in <module>
        from luckydonaldUtils.encoding import to_unicode as u
    ImportError: No module named 'luckydonaldUtils'

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-73hkqbzs/pytg

$ pip --version
pip 7.1.2 from /usr/lib/python3.5/site-packages (python 3.5)
$ pip list | grep setuptools
setuptools (18.5)

Quick solution, until I got the dependencies in correct order:
pip install luckydonald-utils

should be fixed in v0.4.3 now.

Successfully installed DictObject-0.1.2 luckydonald-utils-0.33 pytg-0.4.4

Looks good now. Thanks!

Awesome.


VSCode gives hints after space when writing comments

Bicep version
Bicep CLI version 0.2.46 (fa6e2c5d92)
Describe the bug
VSCode opens hint window after every word (after hitting space) when writing comment line. It's quite annoying.

To Reproduce
Steps to reproduce the behavior:

begin comment line
start writing a comment, press space

Hint window should not appear when writing a comment.

FYI, I started working on fix for this :)

Dup of https://github.com/Azure/bicep/issues/576

@miqm This was a duplicate of an issue that was already assigned to me. Luckily, I haven't started yet and your implementation is similar to what I was planning to do, so I approved and merged your PR.
However, you have exposed a bug in our contribution guide 😊. Issues that get newly created first need to go through triage before PRs get created, which helps us avoid duplication of effort. It worked out ok this time, but we will update the contribution guide to avoid similar situations in the future.

@majastrz i didn't notice the original one and that hints in comments were so annoying I had to do something :)
For next thing I'll pick up one of those labeled nice first task.

We really appreciate all the contributions. ❤ We just want to avoid having to block PRs if we disagree with the design or if work is getting duplicated. This way everyone gets the best experience.

Totally agree on it being annoying btw.


Need more graceful errors if ENVSETUP_ENVIRON isn't set.

What happened?
It looks like envsetup::read_path() will fail if you don't set ENVSETUP_ENVIRON:
Let's say I have the config file:
default:
  paths:
    data: './DEV/username/project1/data'
    output: './demo/DEV/username/project1/output'
    programs: './demo/DEV/username/project1/programs'

Following the basics to setup the Rprofile, this is the error returned:
envsetup::read_path("data", "test.sas7bdat")
Error in which(names(lib) == envsetup_environ):length(lib) :
  argument of length 0

My impression is this comes from here:
https://github.com/pharmaverse/envsetup/blob/539514d89cbff4f61635052ba865d05a1d3fb181/R/paths.R#L28
Which is clear by the error, but in this config, we didn't name the vectors for the libraries, so we get back a 0 length vector:
my_path <- file.path('a', 'b' ,'c')
print(my_path)
#> [1] "a/b/c"

print(which(names(my_path) == ""))
#> integer(0)

which(names(my_path) == ""):1
#> Error in which(names(my_path) == ""):1: argument of length 0

Created on 2022-10-26 with reprex v2.0.2
So there needs to be a condition around assigning restircted_paths that checks that:

The library you're calling is actually named
Additionally, we might want a default assumption if envsetup_environ is not enabled.

@nicholas-masel curious of your thoughts around this.
Session Information
R version 4.1.1 (2021-08-10)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 10 x64 (build 22000)
Matrix products: default
locale:
[1] LC_COLLATE=English_United States.1252  LC_CTYPE=English_United States.1252    LC_MONETARY=English_United States.1252
[4] LC_NUMERIC=C                           LC_TIME=English_United States.1252
attached base packages:
[1] stats     graphics  grDevices datasets  utils     methods   base
loaded via a namespace (and not attached):
[1] compiler_4.1.1   magrittr_2.0.3   assertthat_0.2.1 cli_3.4.1        envsetup_0.0.1   tools_4.1.1      rstudioapi_0.14
[8] yaml_2.3.6       config_0.3.1     rlang_1.0.6      renv_0.15.2      purrr_0.3.5
Reproducible Example
config_path <- "C://Users//16105//OneDrive - ATorus//Documents//Projects//envsetup_test/_envsetup.yml"

envsetup_config <- config::get(file = config_path)

envsetup::rprofile(envsetup_config)

objects("envsetup:paths")
#> [1] "data"     "output"   "programs"

Sys.getenv("ENVSETUP_ENVIRON")
#> [1] "DEFAULT"

print(output)
#> [1] "."

envsetup::read_path(output, "my_file.txt")
#> Error in which(names(lib) == envsetup_environ):length(lib): argument of length 0

Created on 2022-10-26 with reprex v2.0.2

@mstackhouse  Thanks for the nice example.
I see set_autos() already handles this better than read_path().
  if (envsetup_environ %in% names(autos_paths)) {
    autos_paths <-
      autos_paths[which(names(autos_paths) == envsetup_environ):length(autos_paths)]
  }

I think we can add this condition around the read_path() list subsetting.  So if users don't name the list and control the execution environment, it will check all paths, all the time.
This is fine for read_path(), but we need just one path for write_path().  We can add the check to write_path() to throw a nice error if lib contains more than one path and envsetup_environ is not being used to name the execution evironment, i.e. telling this where to write.
Another thought would be a new helper function to run on config files to sus this out during config creation.
What do you think?  And any thoughts on documentation updates to make this more clear?

I think we can add this condition around the read_path() list subsetting. So if users don't name the list and control the execution environment, it will check all paths, all the time.

I think that sounds good, particularly if people are just using unnamed defaults. But I think this actually looks like an issue for the autos paths too:
envsetup_environ <- getOption("ENVSETUP_ENVIRON")
paths <- file.path("unnamed", "path")

if (envsetup_environ %in% names(paths)) {
  print("Blah")
}
#> Error in if (envsetup_environ %in% names(paths)) {: argument is of length zero

Created on 2022-10-27 with reprex v2.0.2
So what we can do here is:
envsetup_environ <- getOption("ENVSETUP_ENVIRON")
paths <- file.path("unnamed", "path")

if (!is.null(envsetup_environ) && envsetup_environ %in% names(paths)) {
  print("Blah")
}

Created on 2022-10-27 with reprex v2.0.2

Another thought would be a new helper function to run on config files to sus this out during config creation.

So like a config validator - I think we're homing in on a few rules here that would be valid checks so that would be really useful

And any thoughts on documentation updates to make this more clear?

I'll need to do a review here, but since there's only one vignette, I think we probably want to split vignettes out to outline different potential configurations. For example:

Using envsetup for single path environments
Using envsetup for hierarchical path environments
A vignette around reading and writing data
A vignette around using functions stored in autos paths

Another thing I think could be more clear is when is the right time to call library(envsetup). I think I created an infinite loop in an Rprofile I was working with yesterday, because it crashed my R session every time I restarted. I didn't have time to pinpoint the issue though - and this was with calling envsetup in the .RProfile itself.

@nicholas-masel  another question - do we have a configuration option to have separate levels but not look up the hierarchy? In your language, what if QA should just look at QA and PROD should just look at PROD?

@nicholas-masel another question - do we have a configuration option to have separate levels but not look up the hierarchy? In your language, what if QA should just look at QA and PROD should just look at PROD?

@mstackhouse  Yes, this is doable if we are ok with updating write_path() just write to the first path in the hierarchy.
Then we would create the config file with default left blank but add hardcoded configurations for DEV, QA and PROD where QA doesn't have DEV paths, and PROD only has PROD paths.  Now you just select the correct configuration when calling config::get() using the config parameter.
For example:
config::get(file = config_path, config = "PDEV")
config::get(file = config_path, config = "QA")
config::get(file = config_path, config = "PROD")

@nicholas-masel ah ok gotcha - I probably didn't read the vignette thoroughly enough but that makes much more sense now.

Closed by #52


Model weights

Hey,
I couldn't find any links to the weights of the models, as it's written in readme.
Would you mind sharing the weights?

Hi, I can't provide the weights files because I don't have them anymore... it would require me to train YOLO and the Attention-OCR all over again...

Weights and other configuration files are now available.


Reports - Master inventory list

I am not sure if this has a ticket or not.

Ticket already exsistes #359


jacocoTestCoverageVerification failing in circleci after JDK17, Gradle 7.6.1 upgrade

Error log:
!/bin/bash -eo pipefail
./gradlew jacocoTestCoverageVerification
Picked up _JAVA_OPTIONS: -Xmx3g

Welcome to Gradle 7.6.1!

Here are the highlights of this release:
 - Added support for Java 19.
 - Introduced `--rerun` flag for individual task rerun.
 - Improved dependency block for test suites to be strongly typed.
 - Added a pluggable system for Java toolchains provisioning.

For more details see https://docs.gradle.org/7.6.1/release-notes.html

> Task :compileJava UP-TO-DATE
> Task :processResources UP-TO-DATE
> Task :classes UP-TO-DATE
> Task :jacocoTestReport FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':jacocoTestReport'.
> Could not create service of type IsolatedAntBuilder using BuildScopeServices.createIsolatedAntBuilder().
   > Could not inspect the Groovy system for ClassLoader VisitableURLClassLoader(ant-and-gradle-loader)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.6.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 6s
3 actionable tasks: 1 executed, 2 up-to-date

Exited with code exit status 1
CircleCI received exit code 1

Bumped JDK17 to JDK21 and Jacoco to 0.8.9 and Gradle to 8.4.


pyconfig.h not found from custom python 3.7.2 installation

When compiling boost against a custom python 3.7.2 installation the following error occurrs:
In file included from ./boost/python/detail/prefix.hpp:13:0,
                 from ./boost/python/list.hpp:8,
                 from libs/python/src/list.cpp:5:
./boost/python/detail/wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory
 # include <pyconfig.h>

This is due to the fact that the include files are located within a directory called python3.7m in the installation include directory:
$ ls -l /usr/local/Python-3.7.2/include
drwxr-xr-x. 3 ralph users 4096 Jan 10 11:05 python3.7m

Creating a softlink from python3.7m to python3.7 solves the problem.
This problem happened on a Centos7 installation. Python was compiled and installed with pretty much standard compile options:
$ ./configure CFLAGS=-fPIC --prefix=/usr/local/Python-3.7.2 --enable-optimizations

This issue still exists with python-3.7.4 and boost-1_71_0.  Thanks for posting the workaround.


Directly passing texture objects to fabric material shaders

For my master thesis, I required direct access to the fragment shader in order to do Volume Raycasting. In Cesium, this can be done using the Fabric approach. However, there was no way to directly pass a texture containing my volume data. A slight alteration to the Material code, allowing me to directly pass a Texture object to the shader was enough to access the sampler in the fragment shader. Example, starting with creating the texture:
var pointcloud = new Uint8Array(length * width * height);

/* fill the pointcloud here */

var source:any = new Object();
source.arrayBufferView = pointcloud;

var texture = new Cesium.Texture({
    context : this.scene.context,
    width : width,
    height : length * height,
    pixelFormat : Cesium.PixelFormat.LUMINANCE,
    pixelDatatype : Cesium.PixelDatatype.UNSIGNED_BYTE,
    source: source,
    sampler: new Cesium.Sampler({
        wrapS : Cesium.TextureWrap.CLAMP_TO_EDGE,
        wrapT : Cesium.TextureWrap.CLAMP_TO_EDGE,
        minificationFilter : Cesium.TextureMinificationFilter.LINEAR,
        magnificationFilter : Cesium.TextureMagnificationFilter.LINEAR
    })
});

Creating Shader Source:
var shader_source = `
    czm_material czm_getMaterial(czm_materialInput materialInput)
    {
        czm_material m = czm_getDefaultMaterial(materialInput);
        float x = sampler2D(pointcloud, materialInput.st) / 256.0;
        m.diffuse = (x, x, x);
        return m;
    }
`;

And then passing it to the primitive:
var instance = new Cesium.Primitive({
    asynchronous: false,
    geometryInstances: new Cesium.GeometryInstance({
        geometry: polygonGeometry
    }),
    appearance : new Cesium.MaterialAppearance({
        material : new Cesium.Material({
            fabric : {
                uniforms : {
                    pointcloud: texture,
                },
                source : shader_source
            }
        })
    })
});

My code example is in Typescript, please excuse me if this does not directly convert to JavaScript.

Cool, thanks @LukasdeBoer!  Can you please add a unit test to https://github.com/AnalyticalGraphicsInc/cesium/blob/master/Specs/Scene/MaterialSpec.js?
Also, just a heads up that Cesium.Texture is not part of the public API so its interface may change from release to release, e.g., when we upgrade to WebGL 2.

Off topic: Are you using typescript with Cesium? Can I get some details, please (type definitions, etc)? Thank you.

@thinkpadder1 Unfortunately, nothing special. I use Cesium from our visualization framework CommonSense. There are some definition files circling around the internet, but I don't use them at the moment.

Closing given that Texture isn't yet part of the public Cesium API.  We can revisit when we make Renderer changes, which are imminent-ish given WebGL 2 progress.  Thanks for supporting Cesium, @LukasdeBoer!


Pytorch Geometric support (deprecates KGCN)

What is the goal of this PR?
Migrate the ethos of TypeDB-ML to be a library to support machine learning using existing graph learning frameworks, starting with support for PyTorch Geometric and NetworkX to support in-memory graphs and general-purpose graph algorithms.
What are the changes implemented in this PR?

Encoding of a TypeDB graph (already exported into NetworkX) into a PyTorch Geometric HeteroData object
Updating the Diagnosis example to demonstrate how to create a GNN using TypeDB, KGLIB and PyTorch Geometric

Solves #44

Approved for the build only. The API contains a lot of changes and most of them fundamental. They will be reviewed later in a longer discussion (most probably in person).


Problem with building by Gulp

I have bought theme so if I need to use variables from theme (in this case I need to add:
@import '~saturn-datepicker/theming'; @include sat-datepicker-theme($theme); to my main style.scss) and when I hit:
gulp --prod --angular
I get an error:
Message:
..\src\sass\framework\vendors\material-angular_custom.scss
Error: File to import not found or unreadable: ~saturn-datepicker/theming.
on line 32 of ../src/sass/framework/vendors/material-angular/_custom.scss
from line 9 of ../src/sass/framework/vendors/material-angular/mat.scss
from line 21 of ../src/sass/demo/default/style.bundle.css

@import '~saturn-datepicker/theming';
^

internal/streams/legacy.js:59
throw er; // Unhandled stream error in pipe.
^
Error: ..\src\sass\framework\vendors\material-angular_custom.scss
Error: File to import not found or unreadable: ~saturn-datepicker/theming.
on line 32 of ../src/sass/framework/vendors/material-angular/_custom.scss
from line 9 of ../src/sass/framework/vendors/material-angular/mat.scss
from line 21 of ../src/sass/demo/default/style.bundle.css

@import '~saturn-datepicker/theming';
^

Saturn-datepicker version: 6.1.1
Angular 6

Sorry, I'm not familiar with Gulp. You could try @import '~saturn-datepicker/_theming';

For those looking for an answer (like I just was).
You have to import in your styles.scss inside src folder,  not in your component.
This did the trick for me.
@import '~saturn-datepicker/bundle.css';


Allow page brake within a section.

Allow a page break within a section.
For example, if work experience is crossing a page brake allows breaking the section between pages.

Hello, I have started working on a similar feature - we want to have work experience distributed on multiple pages.
I have opened a PR #1060 feel free to comment on it and contribute.
The basic idea is that we can define some sections that can be multiplied - thus having work, work-1, work-2 and so on. Then on the template layout level you can put them wherever you like including multiple pages


[Feature Request] Be able to set a starting build number

It would be great to be able to set the starting build number.
Use case:
When you migrate from another build system or even upgrade drone sometimes you want to set the build number to the last of the other system.
Seems like in the settings or enable location we could add a starting build number.
@bradrydzewski If you have any ideas around what's the best way to handle this, I'm down to take a stab at it.

You can do update repos set repo_counter = ? where repo_id = ?.  You could use a sql script to set the counter in batch for all repositories. Example script:
cat <<EOF > setup.sql

update repos set repo_counter = ? where repo_full_name = ?;
update repos set repo_counter = ? where repo_full_name = ?;
update repos set repo_counter = ? where repo_full_name = ?;
update repos set repo_counter = ? where repo_full_name = ?;

EOF

Example command to load the script (sqlite):
> sqlite3 /path/to/drone.sql
> sqlite> .read setup.sql

ah yeah totally works. I was more meaning getting a UI component for folks to use and be able to set the next build counter :)

I would suggest we add this to the drone repo update CLI command. These sort of features get incubated in the CLI (see drone repo repair and drone repo chown) before we consider adding them to the user interface.
Setting the next build number definitely has some risks, so I think we should probably provide a warning message that we force the user to acknowledge:
$ drone repo update foo/bar --build-counter=25
Setting the build counter is an unsafe operation that could put your
repository in an inconsistent state. Please use --unsafe to proceed

$ drone repo update foo/bar --build-counter=25 --unsafe

We may also want to consider, at least initially, restricting the ability to set this field to system administrators (similar to what we do for timeout and trusted). We can always loosen up the restrictions in the future, but perhaps a conservative approach here makes sense to start?

I think the UI component could only increment after a build has started right? Because the next build has to increment the build counter. If you change it to anything less, what implication does that have on the build that just ran?

@tonglil right now the only way to do it is once the PR are merged and via the command line. The idea is that the admin should make sure manually to only update to a higher number since there's no verification in the code. Hence why you need the unsafe flag that Brad mentioned should be there :)  This honestly solves most problems I've seen but we could open a new feature request once it's all merged in if it makes sense to be in the UI

It's now been merged for the CLI/Drone/Drone-go repos


Fixed typo in teal/index.md

Fixed minor typo from "Langauge" to "Language".

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


how to specify database connection when using multiple databases

I'm using two databases, and currently it is defaulting to the wrong database, ie not the one that contains the laravel-love tables
usually I get around this by simply specifying the connection inside the model. But since there is no configuration file where you can specify which model to use, I can create a model of my own and then extend your model
so is there another way of specifying which connection the two models (love_likes and love_likes_counters) are using?

nevermind.. got it to work by following your extending docs and binding to my own models in my service provider
would be nice if next version has a configuration file where you can specify the connection however


PrediKit

PrediKit - An NSPredicate DSL for iOS & OS X inspired by SnapKit and written in Swift :large_orange_diamond:

@KrakenDev, do you know where we could add PrediKit?

@dkhamsing @naeemshaikh90 /CoreData?


chore: helm lock

Description
Update of dependency Helm lock.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Bug fix

How Has This Been Tested?
N/A
Checklist

[x] My commit message is conventional
[x] I have run pre-commit on all files before creating the PR
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have checked my code and corrected any misspellings

:tada: This PR is included in version 1.8.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Not working - 918+, DSM 7.2-64570

see picture.

Did storage manager see the NVMe drives before you ran the scripts?

Did storage manager see the NVMe drives before you ran the scripts?

no.but syno_hdd_db.sh scripts can see.

Some people have had issues with 7.2 update 2 or 7.2 update 3 not seeing their NVMe drives.
Do you want to roll back to 7.2 update 1 and see if storage manager then shows your NVMe drives? You won't lose any settings or data.

Run https://github.com/007revad/Synology_DSM_reinstall
Do a manual DSM install of DSM 7.2 (with Update 1)

Some people have had issues with 7.2 update 2 or 7.2 update 3 not seeing their NVMe drives.
Do you want to roll back to 7.2 update 1 and see if storage manager then shows your NVMe drives? You won't lose any settings or data.

Run https://github.com/007revad/Synology_DSM_reinstall
Do a manual DSM install of DSM 7.2 (with Update 1)

Followed the steps but the downgrade failed, including the script to upgrade to version 1.08.
1、run re-install scripts.

2、upload dsm os.(DS918+

3、wait restart

4、After restarting, control panel information.

5、Run hdd.sh

6、run enable.sh

7、storage manager not NVMe drives

What does the following command return:
sudo -i nvme list
Can you downgrade to DSM 7.2 (with Update 1) again but this time disable DSM Auto Updates and don't run the scripts.

Disable any schedules you have that run the scripts.
Disable DSM Auto Update via "Control Panel > Update & Restore > Update Settings > Notify me... > OK".
Run https://github.com/007revad/Synology_DSM_reinstall
Do a manual DSM install of DSM 7.2 (with Update 1)
After the DS918+ has rebooted check if storage manager shows the NVMe drives.

If step 5 shows the NVMe drives, then run syno_hdd_db script.

Also, what does the following command return:
ls /run/synostorage/disks
And these:
ls /run/synostorage/disks/nvme0n1
ls /run/synostorage/disks/nvme1n1

以下命令返回什么： sudo -i nvme list
您能否再次降级到 DSM 7.2（更新 1），但这次禁用 DSM 自动更新并且不运行脚本。

禁用运行脚本的任何计划。
通过“控制面板”禁用 DSM 自动更新 > 更新和恢复>更新设置>通知我...> 好的”。
运行 https://github.com/007revad/Synology_DSM_reinstall
手动安装 DSM 7.2（更新 1）
DS918+ 重新启动后，请检查存储管理器是否显示 NVMe 驱动器。

如果步骤 5 显示 NVMe 驱动器，则运行syno_hdd_db脚本。

Affected the use, test next time. But my downgrade steps are the same as you described, 1. disable automatic updates, 2. run the reinstall script, 3. manually install 7.2-64570-1-NanoPacked. However, the system information does not change to update 1.

I just tested downgrading from 7.2 Update 2 to 7.2 (with Update 1) and after it rebooted it had 7.2 Update 3 installed (even though I have DSM set to notify me instead of auto updating. It looks like Synology consider update 3 is a critical update and is forcing it on people when they update to DSM 7.2.
I might try it again but this time with my Internet disconnected so it can't update to Update 3.
Do you have a real DS918+ or is DSM running in expenology?
What do each of the following commands return:
sudo -i nvme list
ls /run/synostorage/disks
ls /run/synostorage/disks/nvme0n1
ls /run/synostorage/disks/nvme1n1
get_key_value /etc.defaults/synoinfo.conf support_m2_pool
get_key_value /etc/synoinfo.conf support_m2_pool
get_key_value /etc.defaults/synoinfo.conf supportnvme
get_key_value /etc/synoinfo.conf supportnvme

i'm running expenology.
There is currently no 918 operating environment, so the command you gave cannot be tested.

There's a post on the xpenology forum here that says Peter Suh's M SHELL for TCRP FRIEND includes NVMe cache automatic recognition.

I had the same problem and it didn't work properly after using the “Synology_enable_M2_volume”. At present, I am in the DSM 7.2-64570 Update 3 version. The information obtained by executing these commands is for your reference.

The 0 @ drive model is a problem. I've seen something similar in syno_hdd_db before.
I'll create a debug version of the script so we can see where it's getting that 0 @ drive model from.

驱动器模型有问题。我以前在syno_hdd_db看到过类似的东西。0 @
我将创建脚本的调试版本，以便我们可以看到它从何处获取该驱动器模型。0 @

0 @ 'should be the reason why the firmware of my hard disk has been flashed, which causes the HDD model to be recognized as 0 @'.
However, this hard disk can be recognized and used normally, and DSM can also recognize and use it.

In addition, I would like to add some information:
I also tried to use " Synology_M2_volume", and the script ran normally, but after restarting, it was the same as before, and M was not recognized.

Did the NVMe drive show in storage manager before you updated to DSM 7.2 Update 3?
Do the following commands list your NVMe drive?
ls /run/synostorage/disks
ls /sys/block | grep nvme

在您更新到 DSM 7.2 更新 3 之前，NVMe 驱动器是否显示在存储管理器中？
以下命令是否列出您的 NVMe 驱动器？
ls /run/synostorage/disks
ls /sys/block | grep nvme

None in synostorage, only HDD hard disk

在您更新到 DSM 7.2 更新 3 之前，NVMe 驱动器是否显示在存储管理器中？
以下命令是否列出您的 NVMe 驱动器？
ls /run/synostorage/disks
ls /sys/block | grep nvme

None in synostorage, only HDD hard disk

Can you try running syno_hdd_db with the -n option
./volume/OS/Script/syno_hdd_db.sh -n
Then reboot.

Can you try running syno_hdd_db with the -n option
./volume/OS/Script/syno_hdd_db.sh -n
Then reboot.

NVME is also not working properly.
PS: I added a SATA SSD "S100Pro 1TB" and it works.

Can you run this script and see if that makes the NVMe drive show in storage manager.
https://github.com/AuxXxilium/arc-extensions/blob/main/nvmecache/all/usr/sbin/nvmecache.sh

It's working！It appears that “libsynonvme.so.1” must be modified.

Excellent


Document Controlled vs Uncontrolled Component Design pattern

pursuant to this discussion https://twitter.com/dan_abramov/status/1001943857096003584
all react components can be:

controlled (no internal state)
uncontrolled (internal state)
mixed (uncontrolled by default, unless some props are passed to make it controlled)

the current docs on controlled vs uncontrolled: https://reactjs.org/docs/uncontrolled-components.html focus entirely on forms, but this design pattern applies to -all- components. we should document this.
questions

What else should we say in the docs?
do we want to tell people that they can do "mixed control" or do we leave that for people to discover for themselves?
is this the same page as https://reactjs.org/docs/uncontrolled-components.html or is it a separate page?

Draft copy:

I would very much like to see a "canonical" approach for the mixed mode in the docs. This is the most cumbersome to re-implement in React 16.4.
An example of component needing mixed controls — i.e. a state-from-props approach — from my own codebase is a text input in which the value is committed only when pressing the Enter key.
The blog post on React 16.4 mentions an approach:

static getDerivedStateFromProps(props, state) {
  const prevProps = state.prevProps;
  // Compare the incoming prop to previous prop
  const controlledValue =
    prevProps.value !== props.value
      ? props.value
      : state.controlledValue;
  return {
    // Store the previous props in state
    prevProps: props,
    controlledValue,
  };
}

I wonder if there's another way to think about this sort of scenario.

@sw-yx in regards to your Draft:

Should the uncontrolled pattern include a way for the component to broadcast the change to its parent? e.g. using the componentDidUpdate lifecycle method:

//...
componentDidUpdate(previous_props, previous_state) {
  if (this.state.isOn !== previous_state.isOn && typeof this.props.onChange === 'function') {
    this.props.onChange(this.state.isOn);
  }
}
//...

It's also apparent that I've been using mixed control to mean something slightly different: taking the value from the prop, forking it in the state, and reacting to changes in the prop — it's now clear that the approach is bug-prone, but in the example from my previous comment, I believe there needs to exist a flow to address these kinds of things...

@danburzo these are good questions. i think we can err on the side of having more examples rather than having one that demonstrates all the bells and whistles. so something like:

simple uncontrolled example
simple controlled example
simple mixed example
broadcast controlled example
deduped broadcast controlled example

something like that?
with this much content, and with the importance of the topic, this probably warrants a new page. is there anyone we should ask to sign off on this? since there would be a "Uncontrolled Components" page and a "Controlled vs Uncontrolled Components" page. how does that big picture thing look?

btw feel free to get started on a PR if anyone watching wants, i dont lay claim to this :)

The upcoming blog post also has some useful info in that regard: https://github.com/reactjs/reactjs.org/pull/931

Sounds good to me.
I do think we should have some cross-linking and that maybe some of the post should make its way into the docs as well, but so far I've been focusing mostly on the blog post itself and getting it right.

The blog post is out, I should probably spend some time this weekend firming up the docs. Does anyone have to sign off/decide on adding a new page vs renaming the "Uncontrolled Components" page?

Does anyone have to sign off/decide on adding a new page vs renaming the "Uncontrolled Components" page

Someone like Dan or myself should review the PR, yeah 😄Especially if you're proposing any sort of structural changes. Just to be safe!

well. we could just stick it inside the Uncontrolled Components page. I don't know. I can write a lot, or very little, or not at all. I am very uncertain about the scope of this issue, and its going to vary a lot from person to person.

@sw-yx that sounds really great. I'd very much like to see the officially recommended way of writing that kind of mixed components.

simple uncontrolled example
simple controlled example
simple mixed example
broadcast controlled example
deduped broadcast controlled example

I'm wondering, isn't the "broadcast controlled" example unnecessary? Correct me if I'm wrong but I thought if you want to control the state most likely you also want to be notified of the changes. And could you also explain what you meant by "deduped broadcast"?
Btw. can we find a better name? "Mixed components" to me sounds a bit too generic. Maybe something like "controllable components"? "Mixed-control components"?

sure thing. if anyone wants to take over this issue please do, I don't have a strong vision for it. I would also say we can try to limit the scope for now, so maybe just do the first 3 to get the initial message across. we're not writing a book here.

Hi!
I wonder what is an appropriate way of getting uncontrolled component's data, eg: email example from blogpost


Fix nodeSelector and its associated documentation.

Previously, the templates and README.md referenced a general.nodeSelector field that didn't exist in
helm-charts/k8s-mediaserver/values.yaml or k8s-mediaserver.yml files. Conversely, those yaml/yml files allow for per-pod node selection, which allows for more flexibility. We've gotta resolve this inconsistency one way or the other, so let's go with the more flexible approach.

Actually -- this is a breaking change. Lemme fix that


refactor(CreateAIReply): use azure openai instead

Since we will be using Whisper APIs (Open AI only -- Azure's STT is as expensive as Google's), I decided that we should not complicate the settings and keep using OpenAI's endpoint for now.


Pressing Enter or Tab doesn't fire change event

I've got a <textarea> with TabOverride activated on it. I attached an event listener on the <textarea> for the change event like this:
$textArea.on("change", function () {
    var newValue = $(this).val();
    $("#AnotherTextArea").val(newValue);
});

The problem is that if you press the Enter or Tab keys in the <textarea>, the change event is never fired because TO intercepts the keypress event and runs event.preventDefault(), which evidently keeps the browser from ever firing the change event afterward.
Is there an easy way to fix this without messing up core plugin functionality?

You should be able to do something similar to what I suggested in #10:
$textArea
    .on('change', function () {
        $('#AnotherTextArea').val(this.value);
    })
    .on('keydown', tabOverride.handlers.keydown)
    .on('keypress', function (e) {
        tabOverride.handlers.keypress.call(this, e);
        $(this).change();
    });


Analyze possible ways to decouple current Coordinator code

Right now our Coordinator is quite coupled and as per Software Architect request we should split it into more decoupled components, utilizing MediatR.
This story will investigate how this could be done


DEV-812 Make naming of exceptions more standard

SonarQube analysis reported 5 issues

 2 major
 3 minor

Watch the comments in this conversation to review them.


[T3A3][T09-A3] Tang Di Feng

@e0011840 some comments added, please check.
please close the PR once you have noted the suggestions.

Noted With thanks!!


Upgrade to ADBC 0.4.0

Checklist

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

ah, the bot picked it up so I'll merge this on top of the other branch


Revert "Avoid pushing fybrik-template chart to public registry."

We need this almost empty helm chart in a public repository for integration testing.

/retest

@roytman I assume you are refering to name: ghcr.io/fybrik/fybrik-template:0.1.0 from https://github.com/fybrik/fybrik/blob/master/manager/testdata/blueprint.yaml#L56 . I indeed missed that sorry. Can we change it to name: localhost:5000/fybrik-system/fybrik-template:0.1.0 similar to https://github.com/fybrik/fybrik/blob/master/manager/testdata/unittests/module-read-csv.yaml#L14 so we could avoid pushing this chart to public repo? Thanks

@roytman I assume you are refering to name: ghcr.io/fybrik/fybrik-template:0.1.0 from https://github.com/fybrik/fybrik/blob/master/manager/testdata/blueprint.yaml#L56 . I indeed missed that sorry. Can we change it to name: localhost:5000/fybrik-system/fybrik-template:0.1.0 similar to https://github.com/fybrik/fybrik/blob/master/manager/testdata/unittests/module-read-csv.yaml#L14 so we could avoid pushing this chart to public repo? Thanks

@revit13 Yes, it can be renamed to localhost:5000/fybrik-system/fybrik-template:0.1.0

@roytman @shlomitk1 ok Thanks I will create a pr for that.

@revit13 , @shlomitk1 I understood from @roee88, that this chart is used for the integration tests, and better to check helm chart deployment from a public repository.
Did I miss something ?

@roytman OK I see. @shlomitk1 can we use arrow-flight-module-chart in the integration tests instead of fybrik-template? not sure what version though - maybe latest

@roytman OK I see. @shlomitk1 can we use arrow-flight-module-chart in the integration tests instead of fybrik-template? not sure what version though - maybe latest

Not latest. Any change in arrow-flight repo will break testing. The last official version that is compatible with Fybrik release, perhaps.

@roytman OK I see. @shlomitk1 can we use arrow-flight-module-chart in the integration tests instead of fybrik-template? not sure what version though - maybe latest

Not latest. Any change in arrow-flight repo will break testing. The last official version that is compatible with Fybrik release, perhaps.

OK Thanks. I guess  fybrik-template chart was created to avoid such compatibility issues...

@roytman OK I see. @shlomitk1 can we use arrow-flight-module-chart in the integration tests instead of fybrik-template? not sure what version though - maybe latest

Not latest. Any change in arrow-flight repo will break testing. The last official version that is compatible with Fybrik release, perhaps.

OK Thanks. I guess fybrik-template chart was created to avoid such compatibility issues... on the other hand, this is the purpose of integration tests to reveal such problems. no?

Not in this repo. There are no integration tests with external modules in this repo. The ideas discussed so far were to eventually setup a way for external repos to run their own integration tests against fybrik. If this decision needs to be revisited then we can open a separate discussion.

@roytman OK I see. @shlomitk1 can we use arrow-flight-module-chart in the integration tests instead of fybrik-template? not sure what version though - maybe latest

Not latest. Any change in arrow-flight repo will break testing. The last official version that is compatible with Fybrik release, perhaps.

OK Thanks. I guess fybrik-template chart was created to avoid such compatibility issues... on the other hand, this is the purpose of integration tests to reveal such problems. no?

Not in this repo. There are no integration tests with external modules in this repo. The ideas discussed so far were to eventually setup a way for external repos to run their own integration tests against fybrik. If this decision needs to be revisited then we can open a separate discussion.

@roee88 OK, I guess https://github.com/fybrik/fybrik/blob/master/manager/testdata/blueprint.yaml#L18 should be changed after the implicit copy modules are moved to their own repo right? I can create an issue for that.

Also, these are used in unit tests not in integration tests. @shlomitk1 after getting back to the previous state (i.e. after this PR is merged) would one be forced to push anything to the local registry before running those unit tests from within an IDE?

Unit tests are not supposed to use helm, so the images do not matter.

If the value is ignored, i.e., we have no test that actually helm installs the dummy, then this PR is not needed. I was under the probably wrong impression that we do have some test in the blueprint controller that works with the non-fake helm implementation. Apologies for the confusion.

If the value is ignored, i.e., we have no test that actually helm installs the dummy, then this PR is not needed. I was under the probably wrong impression that we do have some test in the blueprint controller that works with the non-fake helm implementation. Apologies for the confusion.

So we don't have any integration test with a module installation from a real public repository ?

a minor comment: fybrik-template is pushed to public repo with tag latest, master or release version tag. I guess that in the tests that use the public chart one of them should be used instead of 0.1.0 tag to avoid making the public push redundant.

If the value is ignored, i.e., we have no test that actually helm installs the dummy, then this PR is not needed. I was under the probably wrong impression that we do have some test in the blueprint controller that works with the non-fake helm implementation. Apologies for the confusion.

So we don't have any integration tests with a module installation from a real public repository ?

We have unit tests that run in the fake environment and integration tests that run in the real environment. Tests in xxx_controller_test.go run as both unit tests and integration tests. Blueprint.yaml is not applied in the integration test, blueprint_read.yaml is applied in the integration test as well, and it includes a public image for a module: ghcr.io/fybrik/fybrik-template:0.1.0
On the other hand, e2e test in fybrikapplication_controller-test.go applies the same module image from localhost:5000...


Polish letters URL based image manipulation

I'm using {route-name}/{template-name}/{file-name}. Everything works as expected but when the name of the file have Polish characters like "ł", "ó" "ż" shows the error 404 Not Found.

Solved:
https://github.com/Intervention/image/commit/7ff8e3947db5848494e182d3adc83f9d35d91aed


pkg/hooks/exec: Add a new package for local hook execution

This wraps os/exec to:

Clear the environment when the hook doesn't set env.  The runtime spec has:

env (array of strings, OPTIONAL) with the same semantics as IEEE Std 1003.1-2008's environ.

And running execle or similar with NULL env results in an empty environment:
$ cat test.c
#include <unistd.h>

int main()
{
  return execle("/usr/bin/env", "env", NULL, NULL);
}
$ cc -o test test.c
$ ./test
...no output...

Go's Cmd.Env, on the other hand, has:

If Env is nil, the new process uses the current process's environment.

This commit works around that by setting []string{} in those cases to avoid leaking the runtime environment into the hooks.

Roll the timeout value (if set) into the passed context.  There's no need for two separate ways to cancel hook execution.

This, like #855, is more groundwork for calling the poststop hooks ourselves instead of delegating to the OCI runtime.

Tests are happy, except for cloud Podman, whic has:
Running Suite: Libpod Suite
===========================
Random Seed:<PHONE_NUMBER>
Will run 286 of 286 specs
Caching alpine...
Caching busybox...
Caching registry.fedoraproject.org/fedora-minimal:latest...
Caching docker.io/library/nginx:latest...
"Error reading config blob sha256:ae513a47849c895a155ddfb868d6ba247f60240ec8495482eca74c4a2c13a881: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/ae/ae513a47849c895a155ddfb868d6ba247f60240ec8495482eca74c4a2c13a881/data?verify=1527728759-P4yE%2BFI7dYTukwbke06OsUr81Uc%3D: read tcp <IP_ADDRESS>:41116-><IP_ADDRESS>:443: read: connection reset by peer"

as well as the Python issues discussed in #856.

I've pushed 5c0a892f -> 854a6663 to get go test -cover ./pkg/hooks/exec to 100%.

I've pushed 854a6663 -> a492f1d1, rebasing onto master and adding a configurable post-kill timeout for waiting on the killed hook process.  There's also a constant with @mhean's recommended 10s timeout.  One benefit of keeping the timeout configurable is that I can set it to 0s for a test and keep 100% coverage ;).

bot, retest this please

LGTM
@mheon @umohnani8 @baude PTAL

LGTM
@rh-atomic-bot r+


Handwriting support

Currently Mozc seems to only support handwriting input to recognize a kanji and copy to the clipboard.
With the amount of computers including tactile screens, it would be great to have handwriting input support similar to Android.

Hi, thank you for the feature request.
I'm sorry, but we have stopped supporting the handwriting feature following the upstream project's change to focus on the core typing features.
Mozc's source code for handwriting is available at:
https://github.com/google/mozc/tree/2018-02-26
Thank you,


Disable coloring output

print called within Duktape puts the output colored in blue. Sometimes color codes aren't rendered properly (in my example -- in Sublime Text build output). What I see is:
You are 29 years old.

I wonder if this coloring a part of this very binding or Duktape itself or even javascript (:laughing:)? BTW, console.log outputs in white but still with color codes:
You are 29 years old.

And if it's the part of this binding, I guess it should be at least allowed to configured, or even removed.
P.S: Thanks for the shard, it otherwise works smoothly! :heart:

duktape.cr definitlely makes use of Crystal's colorize method when rendering output - it's not coming directly from the engine (see: https://github.com/jessedoyle/duktape.cr/search?q=colorize&unscoped_q=colorize).
I think adding a flag to disable colored and styled terminal output would be great!
Would a flag in an environment variable work for your use-case? (i.e. DUKTAPE_COLORED_OUTPUT=false)?
It may take me a few weeks to look into implementing such a flag - I'd absolutely be open to any pull requests with an implementation!
I do think that keeping the default colored output is ideal (i.e. one must opt-out of colored output, but it is enabled by default).

Thinking a bit more on the subject, there may be a flag present already upstream in Crystal that disables the colorize functionality for non-TTY based apps.
See: https://github.com/crystal-lang/crystal/blob/5282fdf913cdf8a1bdf84afc148b238e91a4889e/src/colorize.cr#L128-L130.
I'm curious, does the following configuration disable colored output in your app?
require "colorize"
Colorize.on_tty_only!

Great, disabling Colorize works as expected.
I'm wondering why

I do think that keeping the default colored output is ideal

Just interested. It's your project etc. etc. but for me, I always try to follow SOLID principles and coloring output of an embedded language falls out of its responsibility IMO.

@vladfaust

Just interested. It's your project etc. etc. but for me, I always try to follow SOLID principles and coloring output of an embedded language falls out of its responsibility IMO.

That's a fair observation. In my opinion it's all for developer experience.
I believe that the majority of Crystal users are interacting with their programs via an ANSI-color enabled terminal. The fact that Crystal includes the colorize method in its standard library and that it is widely used in many popular CLI-based tools supports this notion.
I believe that colorizing output enhances the developer experience and makes software tools easier to work with. Could you imagine how unwelcoming the Rails development server would be if it didn't colorize its output by default?
Finally, Duktape.cr uses color to draw the developer's attention to a few things:

The differences between alert and print messages. Alert messages are printed to standard error in yellow, print messages are printed to standard out in light cyan.
Various log levels in the Duktape.cr logger are colorized to assist the the developer when debugging.

As long as there's always a way to disable colorized output, I think we're in a good spot.

As we've established a good mechanism to disable colorized output here, I'm going to close this issue.
I would accept a PR to add documentation about disabling colorized output if anyone is interested.


spdx to cycloneDX report type

sudo su
sudo dnf update -y
sudo dnf install curl -y

next
curl -sSfL https://raw.githubusercontent.com/anchore/grype/main/install.sh | sudo sh -s -- -b /usr/local/bin

this is console output
[info]\033[0m checking github for the current release tag \033[0m
[info]\033[0m fetching release script for tag='v0.79.3' \033[0m
[info]\033[0m checking github for the current release tag \033[0m
[info]\033[0m using release tag='v0.79.3' version='0.79.3' os='linux' arch='amd64' \033[0m
[info]\033[0m installed /usr/local/bin/grype \033[0m

next
ls -l /usr/local/bin/grype

console output
-rwxr-xr-x. 1 root root 54993048 Jul 24 07:27 /usr/local/bin/grype

next
echo $PATH

consle output
/root/.local/bin:/root/bin:/sbin:/bin:/usr/sbin:/usr/bin

next
export PATH=$PATH:/usr/local/bin

netxt
grype version

console output:
Application:         grype
Version:             0.79.3
BuildDate:           2024-07-15T12:57:46Z
GitCommit:           45b7236e948ef973a8a6ffbac52dff28be0fd70e
GitDescription:      v0.79.3
Platform:            linux/amd64
GoVersion:           go1.22.5
Compiler:            gc
Syft Version:        v1.9.0
Supported DB Schema: 5

i try to do this:
grype sbom:./TNC_PrimeRead-build-f2c3b683f67343329c446f2c3847e447.spdx.json -o cyclonedx > report.xml

console output
 ✔ Vulnerability DB                [updated]
 ✔ Scanned for vulnerabilities     [0 vulnerability matches]
   ├── by severity: 0 critical, 0 high, 0 medium, 0 low, 0 negligible
   └── by status:   0 fixed, 0 not-fixed, 0 ignored
[0012]  WARN attempted CPE search on System.Web.WebPages.dll, which has no CPEs.
[0012]  WARN attempted CPE search on System.Xml.ReaderWriter.dll, which has no C
[0012]  WARN attempted CPE search on Unity.Abstractions.dll, which has no CPEs.
[0012]  WARN attempted CPE search on Unity.Configuration.dll, which has no CPEs.
[0012]  WARN attempted CPE search on Unity.Container.dll, which has no CPEs. Con
[0012]  WARN attempted CPE search on Unity.Interception.Configuration.dll, which
[0012]  WARN attempted CPE search on Unity.Interception.dll, which has no CPEs.
[0012]  WARN attempted CPE search on Unity.RegistrationByConvention.dll, which h
[0012]  WARN attempted CPE search on Unity.ServiceLocation.dll, which has no CPE
[0012]  WARN attempted CPE search on Unme.Common.dll, which has no CPEs. Conside
[0012]  WARN attempted CPE search on WebActivatorEx.dll, which has no CPEs. Cons
[0012]  WARN attempted CPE search on WebActivatorEx.dll, which has no CPEs. Cons
[0012]  WARN attempted CPE search on WebMatrix.Data.dll, which has no CPEs. Cons
[0012]  WARN attempted CPE search on WebMatrix.Data.dll, which has no CPEs. Cons
[0012]  WARN attempted CPE search on WebMatrix.WebData.dll, which has no CPEs. C
[0012]  WARN attempted CPE search on WebMatrix.WebData.dll, which has no CPEs. C
[0012]  WARN attempted CPE search on log4net.dll, which has no CPEs. Consider re
[0012]  WARN attempted CPE search on protobuf-net.dll, which has no CPEs. Consid
[0012]  WARN attempted CPE search on sonatype:iq_application_PrimeRead - TNC, wh

but is not working
and show 0 imports in DD

To me this issue gives no sense. Your report shows:
✔ Scanned for vulnerabilities     [0 vulnerability matches]
├── by severity: 0 critical, 0 high, 0 medium, 0 low, 0 negligible
└── by status:   0 fixed, 0 not-fixed, 0 ignored
Can we close this @mtesauro ?

@johnfelipe Look at https://github.com/CycloneDX/cyclonedx-cli  - I've only had good results using that tool.
I'd also not that a SBOM is a listing of software modules/libraries used but that's not necessarily also a listing of findings/vulnerabilities with those modules/libraries.
If you're only looking for software to inventory modules/libraries then perhaps you want OWASP Dependency Track which also has a DefectDojo integration.
If you have outstanding items, feel free to reopen this issue.


React.Exceptions.ReactScriptLoadException shuts down debugging and IIS Express

Nowadays whenever I have a ReactScriptLoadException my debugging session shuts down.
I feed a webpack bundle to reactjs.net and whenever it changes (there is a separate webpack -w console that recompiles it) reactjs.net tries to reexecute it, throws an exception and that shuts down my iis express.
So basically everytime I hit ctrl+s on a jsx halfway through writing a function (where some variables are not declared yet for example) the debugging session shuts down. Since the project is large and needs around 30 seconds to start up, this is very annoying.
I'm asking for help on why this is happening and how to turn it off.

Wow, that's terrible :/
Try calling .SetReuseJavaScriptEngines(false) in your ReactConfig.cs and see if that helps.  It will make page loads a bit slower, but it should be more reliable in this case.

Yes it actually helps, thanks.
Also to try to nail down the exact issue:
Debugging only shuts down if the exception happens outside of a request (if it happens during (or more precisely as a result of) a request the error page is properly shown).
It is happening for both syntax errors and execution errors.

I have a feeling this is happening because the exception is happening on a background thread. ReactJS.NET watches all files you load, and recycles the JavaScript engines if any of those files change. If any errors are encountered while loading the JS file, an exception is thrown. This approach is fine for initial load (as it's fine to throw exceptions on the request thread), but not for background stuff. I'll look into a better approach here.

this should only be an issue with how scripts are loaded when you use AddScriptWithoutTransform. If you instead use AddScript, the error is handled correctly (as those scripts are loaded as part of the request, if they haven't already been loaded).

Yes, I'm using AddScriptWithoutTransform because I already transform my scripts with webpack.

@SoonDead  - Can you please try out the latest dev build and see if it's any better? You can add https://ci.appveyor.com/nuget/reactjs.net as a NuGet package source to get the dev packages. Use version `2.0.2-dev-20151116-0644

@SoonDead  - Can you please try out the latest dev build and see if it's any better? You can add https://ci.appveyor.com/nuget/reactjs.net as a NuGet package source to get the dev packages. Use version 2.0.2-dev-20151116-0644 or higher.

I'll try it when I get to work (in about 1-2 hours).

It seems to be working OK (it's not throwing exceptions when on a background thread).
I have no idea if the javascript engine is properly reused or not, but the react component properly renders upon subsequent requests when the error is fixed.

Thanks for the confirmation!


Correcting false positive of HLint passing GitHub workflow

Our GitHub action for running HLint on the code was previously emitting an alarming warning:
  Running hlint -j --json -- src/ test/
  Warning: Can't find file "MachDeps.h" in directories
  	src/Database/LSMTree/Internal
  	.
    Asked for by: src/Database/LSMTree/Internal/RawBytes.hs  at line 8 col 1
  hlint completed with status code 0

The haskell.yml workflow file's entry for the HLint action had previously specified only fail-on: suggestion whereas this PR increases the failure condition to fail-on: warning. This change causes our CI pipeline to have caught and require correcting the previously ignored warning.
Additionally, the PR corrects the warning by conditionally importing the offending file.

While reviewing the subject of HLint, is there a reason we only include the src and test directories as part of the HLint coverage action and exclude the following directories from HLint coverage?

bench
blockio-api
blockio-sim
bloomfilter
prototypes
src-extras
src-fcntl-nocache
src-kmerge
src-mcg
src-monkey
src-rocksdb
xxhash

The 9.10 job didn't run because it didn't exist before, but it's required now. Maybe just rebase and push again to trigger CI and the auto-merge?

I rebaseed, so the ghc-9.10 checks should run now.
I added all the src-* directories to the HLint checks.
I not not add the bench directory to the HLint checks because there are many suggestions and warnings raised by HLint which would change the evaluation semantics of the benchmarks in undesirable ways. Essentially, within the bench directory, HLint gives too many "false positives."

Instead of adding {-# HLINT ignore ... #-}, ignore the warnings in the hlint.yaml file

I removed the {-# HLINT ignore ... #-} pragmas from all the modules and I added the corresponding ignore statements from the src-* directories to the hlint.yaml file. I did not add the {-# HLINT ignore ... #-} pragmas from the bench directory to the hlint.yaml file since those were related to evaluation semantics false positives.
I think the PR is ready to be merged.


Create flutter specific leak troubleshooting guidance.

There is no tests, because this PR updates testing code and documentation only.

There is no tests, because this PR updates testing code and documentation only.

Isn't this changing user-facing behavior of a user-facing package that is intended for use in tests, rather than code that is just part of one of our own tests? If it's the former, that's not considered a test for exemption purposes.

There is no tests, because this PR updates testing code and documentation only.

Isn't this changing user-facing behavior of a user-facing package that is intended for use in tests, rather than code that is just part of one of our own tests? If it's the former, that's not considered a test for exemption purposes.

The modified code is under 'test'.
It changes information that developers of Flutter Framework will see when they run unit tests of Flutter Framework.
All other people will not get any change.
All other code of flutter_test_config.dart is not test covered.
Does it help?

test-exempt: is a test
(Sorry about that, my brain got confused by the flutter_test in the filename, and read the path as packages/flutter_test/... rather than packages/flutter/test/.... Which I should have realized was wrong since it didn't have a /lib/.)


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_74zlvvqigl/clone/recipe/meta.yaml:15: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_74zlvvqigl/clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_74zlvvqigl/clone/recipe/meta.yaml:22: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_74zlvvqigl/clone/recipe/meta.yaml:24: missing_wheel: For pypi packages, wheel should be present in the host section
WARNING: /tmp/abs_74zlvvqigl/clone/recipe/meta.yaml:54: missing_description: The recipe is missing a description
ERROR: /tmp/abs_74zlvvqigl/clone/recipe/meta.yaml:54: missing_license_family: The recipe is missing the about/license_family key.
ERROR: /tmp/abs_74zlvvqigl/clone/recipe/meta.yaml:54: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_74zlvvqigl/clone/recipe/meta.yaml:54: missing_documentation: The recipe is missing a doc_url or doc_source_url
Errors were found