C23 feature support checklist

Based on https://en.cppreference.com/w/c/23

[x] _Static_asert with no message
[x] [[nodiscard]]
[x] [[maybe_unused]]
[x] [[deprecated]]
[x] Attributes
[ ] IEEE 754 decimal floating-point types
[x] [[fallthrough]]
[ ] u8 character constants
[ ] Removal of function definitions without prototype
[x] [[nodiscard]] with message
[x] Unnamed parameters in function definitions
[ ] Labels before declarations and end of blocks
[x] Binary integer constants
[ ] __has_c_attribute in preprocessor conditionals
[x] Allow duplicate attributes
[ ] IEEE 754 interchange and extended types
[x] Digit separators
[ ] #elifdef and #elifndef
[ ] Type change of u8 string literals
[ ] [[maybe_unused]] for labels
[x] #warning
[x] Bit-precise integer types (_BitInt)
[x] [[noreturn]]
[ ] Suffixes for bit-precise integer constants
[x] __has_include in preprocessor conditionals
[ ] Removal of function declarations without prototype
[x] Empty initializers
[x] typeof ...
[ ] ... and typeof_unqual
[ ] New spelling of keywords
[ ] Predefined true and false
[ ] [[unsequenced]]
[ ] [[reproducible]]
[ ] Relax requirements for variadic parameter list
[ ] Type inference in object definitions (auto)
[ ] constexpr objects
[ ] nullptr

This list may also be helpful for test cases: https://htmlpreview.github.io/?https://icube-forge.unistra.fr/icps/c23-library/-/raw/main/README.html

@ehaas Do you want to handle the Unicode identifier change?

Sure. The list of acceptable start/continuation characters should be straightforward.  I've never done anything with unicode normalization so I don't know how much work that will be, but I think it will fit nicely with the string interner and there won't be too much incidental complexity around adding it.


FloatingArrow: "NaN is an invalid value for the left css style property" when running tests

Describe the bug
We are seeing the following error when running our test suite for components which include floating-ui and the FloatingArrow component.
console.error
      Warning: `NaN` is an invalid value for the `left` css style property.
          at svg
          at FloatingArrow (/Users/mjcampagna/Glue/glue-web/node_modules/@floating-ui/react/dist/floating-ui.react.umd.js:101:9)

Tests are run with Jest and React Testing Library.
I believe we used to see this error (and suppressed it!) in the test environment when floating-ui positioned its tooltips, resulting from the window now being defined, or client rectangle failures. That was using an older version; the latest version of floating-ui seems to have fixed this, but not for the FloatingArrow component.
For now, we're hiding arrows while running tests, e.g. process.env.NODE_ENV === "test".

Does it go away if you add:
if (!floating) return null;

After the DEV statement here:
https://github.com/floating-ui/floating-ui/blob/b8d1fd5854333b688ddc9ee2a171f6453fcdbcab/packages/react/src/components/FloatingArrow.tsx#L72-L81

Hey @atomiks
I am also experiencing the same issue. I hope it will be fixed soon :)
I have also found interesting observation. If I do
jest.mock('@floating-ui/react', () => ({
  ...jest.requireActual('@floating-ui/react'),
}));

and like this:
  beforeEach(() => {
    jest
      .mocked(useFloating)
      .mockImplementation(jest.requireActual('@floating-ui/react').useFloating);
    jest
      .mocked(useHover)
      .mockImplementation(jest.requireActual('@floating-ui/react').useHover);
    jest
      .mocked(useInteractions)
      .mockImplementation(
        jest.requireActual('@floating-ui/react').useInteractions,
      );
  });

The warning is gone. It is a bit weird and I cannot find the explanation. There is no need actually to require actual one because the component is using real module. However, it is a bit strange how it helps, maybe requireActual is not actually requiring, but maybe some kinda simulating it.  This is actually question to jest. Just out of curiosity, maybe do you have any idea how it could help?
However, ofc, it is not the solution. Therefore, looking forward to see fix for this one! Thanks a lot in advance!

I was able to replicate the issue in the non-testing environment 🙌🏻

It happens when the content of the floating element collapses before the floating element closes. This is relevant when the content presence is controlled from the external storage.

Please make an issue w/ a reproduction, otherwise it will get lost and not fixed

UPD: the issue I had is unrelated to the original submission.
The NaN exception was caused by the virtual reference, which was returning an empty DOMRectList from the getClientRects function.


Formatting dates won't work

When formatting a date to anything else than yyyy-mm-dd, the value gets written into the input correctly, but on re-opening the picker, it's empty.

I hate how when you open a new repo it does not auto add you to the watch list. I will look into this.

For me the picker re-opens in a wrong date when the format is different than yyyy-mm-dd.

I believe this is fixed now please check for your use case

I just installed and cannot do any formatting besides the default, v2.14.0.


Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]with Alpine PVC should be successfully started with NFS Disk PVC using ipv4 address of the NFS pod not owned by qemu

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
/triage build-watcher
What happened:
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/logs/periodic-kubevirt-e2e-k8s-prev/1356519903128981504
vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:43
Timed out after 180.000s.
expected phase is Running but got Pending
tests/storage_test.go:93

09:52:01: • [SLOW TEST:73.350 seconds]
09:52:01: Storage
09:52:01: tests/storage_test.go:66
09:52:01:   Starting a VirtualMachineInstance
09:52:01:   tests/storage_test.go:76
09:52:01:     [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]with Alpine PVC
09:52:01:     tests/storage_test.go:147
09:52:01:       should be successfully started and stopped multiple times
09:52:01:       vendor/github.com/onsi/ginkgo/extensions/table/table.go:92
09:52:01:         [test_id:3133]with CDRom PVC
09:52:01:         vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:43
09:52:01: ------------------------------
09:52:10: W0202 09:49:04.565515   48019 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
09:52:10: W0202 09:49:05.352537   48019 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
09:52:10: W0202 09:49:06.754048   48019 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
09:52:10:
09:52:10:
09:52:10: • Failure [186.036 seconds]
09:52:10: Storage
09:52:10: tests/storage_test.go:66
09:52:10:   Starting a VirtualMachineInstance
09:52:10:   tests/storage_test.go:76
09:52:10:     [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]with Alpine PVC
09:52:10:     tests/storage_test.go:147
09:52:10:       should be successfully
09:52:10:       tests/storage_test.go:149
09:52:10:         started
09:52:10:         vendor/github.com/onsi/ginkgo/extensions/table/table.go:92
09:52:10:           with NFS Disk PVC using ipv4 address of the NFS pod not owned by qemu [It]
09:52:10:           vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:43
09:52:10:
09:52:10:           Timed out after 180.000s.
09:52:10:           expected phase is Running but got Pending
09:52:10:
09:52:10:           tests/storage_test.go:93

What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

KubeVirt version (use virtctl version):
Kubernetes version (use kubectl version):
VM or VMI specifications:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

Also observed here: https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/logs/periodic-kubevirt-e2e-k8s-latest/1356724248772612098
23:09:49: • Failure [186.420 seconds]
23:09:49: Storage
23:09:49: tests/storage_test.go:66
23:09:49:   Starting a VirtualMachineInstance
23:09:49:   tests/storage_test.go:76
23:09:49:     [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]with Alpine PVC
23:09:49:     tests/storage_test.go:147
23:09:49:       should be successfully
23:09:49:       tests/storage_test.go:149
23:09:49:         started
23:09:49:         vendor/github.com/onsi/ginkgo/extensions/table/table.go:92
23:09:49:           with NFS Disk PVC using ipv4 address of the NFS pod not owned by qemu [It]
23:09:49:           vendor/github.com/onsi/ginkgo/extensions/table/table_entry.go:43
23:09:49:
23:09:49:           Timed out after 180.001s.
23:09:49:           expected phase is Running but got Pending
23:09:49:
23:09:49:           tests/storage_test.go:93

...

23:13:12:
23:13:12: Summarizing 1 Failure:
23:13:12:
23:13:12: [Fail] Storage Starting a VirtualMachineInstance [rfe_id:3106][crit:medium][vendor:cnv-qe@redhat.com][level:component]with Alpine PVC should be successfully started [It] with NFS Disk PVC using ipv4 address of the NFS pod not owned by qemu
23:13:12: tests/storage_test.go:93
23:13:12:
23:13:12: Ran 326 of 739 Specs in 3189.708 seconds
23:13:12: FAIL! -- 325 Passed | 1 Failed | 1 Pending | 412 Skipped
23:13:12:
23:13:12:
23:13:12: Ginkgo ran 1 suite in 53m11.950507359s
23:13:12: Test Suite Failed
make: *** [Makefile:74: functest] Error 1
+ make cluster-down
"Timestamp is enabled"
./cluster-up/down.sh
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.

Also being reported at the moment at https://storage.googleapis.com/kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flakefinder-2021-02-04-024h.html. Failed for:

pull-kubevirt-e2e-k8s-1.18

https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4953/pull-kubevirt-e2e-k8s-1.18/1357005226543943681

pull-kubevirt-e2e-k8s-1.20

https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4953/pull-kubevirt-e2e-k8s-1.20/1357111425310396416
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4953/pull-kubevirt-e2e-k8s-1.20/1357061094014717953
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4953/pull-kubevirt-e2e-k8s-1.20/1356962067667488768

We have it failing more than half of the time on kubevirt 1.20 lane, also often on kubevirt 1.19 since a while.
@mhenriks could you take a look why this is happening?
FYI @aglitke

container gets stuck in ContainerCreating
                "containerStatuses": [
                    {
                        "name": "nfsserver",
                        "state": {
                            "waiting": {
                                "reason": "ContainerCreating"
                            }
                        },
                        "lastState": {},
                        "ready": false,
                        "restartCount": 0,
                        "image": "registry:5000/kubevirt/nfs-server:devel",
                        "imageID": "",
                        "started": false
                    }
                ],

found event that says this
            "reason": "FailedMount",
            "message": "MountVolume.SetUp failed for volume \"nfsdata\" : hostPath type check failed: /tmp/hostImages/alpine1-nopriv is not a directory",
            "source": {
                "component": "kubelet",
                "host": "node01"
            },

the nfs server is trying to mount a hostPath that doesn't exist now I think... so the question is what happened to that host path.

Also observed again here:

https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4937/pull-kubevirt-e2e-k8s-1.19/1357310991280377856
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4937/pull-kubevirt-e2e-k8s-1.19/1357249585390555136
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4937/pull-kubevirt-e2e-k8s-1.19/1357188180461228032
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4937/pull-kubevirt-e2e-k8s-1.19/1357050020678864896
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4937/pull-kubevirt-e2e-k8s-1.19/1356988617083326464
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4937/pull-kubevirt-e2e-k8s-1.19/1356911861647282176
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4937/pull-kubevirt-e2e-k8s-1.19/1356850455501606912
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4937/pull-kubevirt-e2e-k8s-1.19/1356753064366706689
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4937/pull-kubevirt-e2e-k8s-1.20/1357372396872404992
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4937/pull-kubevirt-e2e-k8s-1.20/1357188180465422336
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4937/pull-kubevirt-e2e-k8s-1.20/1357126776190406656
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4937/pull-kubevirt-e2e-k8s-1.20/1357050020674670592

Again: (caused by single PR #4736 )
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4736/pull-kubevirt-e2e-k8s-1.20/1357571958752940032
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4736/pull-kubevirt-e2e-k8s-1.20/1357433800719601664
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4736/pull-kubevirt-e2e-k8s-1.19/1356957915285557248
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4736/pull-kubevirt-e2e-k8s-1.19/1356896509504786432
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4736/pull-kubevirt-e2e-k8s-1.19/1356834601527414785
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4736/pull-kubevirt-e2e-k8s-1.18/1356435974426464256
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4736/pull-kubevirt-e2e-k8s-1.19/1356957915285557248
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4736/pull-kubevirt-e2e-k8s-1.18/1356512731951271936

https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4552/pull-kubevirt-e2e-k8s-1.20/1357472429466718208
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4948/pull-kubevirt-e2e-k8s-1.20/1357328236014473216
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4552/pull-kubevirt-e2e-k8s-1.19/1357349497239244800
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4948/pull-kubevirt-e2e-k8s-1.19/1357325966740819968

Has in common to https://github.com/kubevirt/kubevirt/issues/4829
Both tests  are skipped with  a comment
					// Skipping the following 2 tests until https://github.com/kubevirt/kubevirt/issues/4829 is fixed
					table.PEntry("with NFS Disk PVC using ipv6 address of the NFS pod", tests.NewRandomVMIWithPVC, "nfs", k8sv1.IPv6Protocol, true),
					table.PEntry("with NFS Disk PVC using ipv4 address of the NFS pod not owned by qemu", tests.NewRandomVMIWithPVC, "nfs", k8sv1.IPv4Protocol, false),

for nfs ignoreWarnings is true, so even Error events will be ignored
Please consider this fix
https://github.com/kubevirt/kubevirt/pull/5012
so we see the exact Error event in the log and assert on it,
In case desired, also warnings can be enabled, and by using
https://github.com/kubevirt/kubevirt/pull/5002
We can ignore specific warnings that are problematic but accept the rest
I saw on https://github.com/kubevirt/kubevirt/issues/4829 a lot of context deadline exceed, from what i undersand
it comes from the 20 seconds gRPC tunnel between virt-handler and virt-launcher, should we increase the timeout there?

Opened a PR to re-enable the tests and see what happens: https://github.com/kubevirt/kubevirt/pull/5042
It they still fail, https://github.com/kubevirt/kubevirt/pull/5012 should help debug once merged, thanks!

Maybe worth running all this Context as [Serial] first for a while ?


Telemetry string output handling on QuRT

@mcharleb @jywilson It is pretty important to us to have a way to transport string messages from QuRT to our application layer on the Linux side. We could do this via muORB if we implement buffering.
Currently the call to the non-existent string device results in these errors:
oe-core/build/tmp-eglibc/work/cortexa8hf-vfp-neon-linux-gnueabi/adsprpc/1.0-r0/adsprpc-1.0/src/fastrpc_apps_user.c:224::error: -1: 0 == (nErr = remotectl_open(name, (int*)

Fixed this.


:mega: Refactored to middleware structure

Coverage remained the same at 100.0% when pulling c9e477a3df14e25cab16543ef119f71df58e7fe6 on feature/add-middleware into 24f5f65025495cfb0fdca09a6a3be9b947ffdfa0 on master.

The output from the route is going to change along with the way the rendering of it is done i.e. view vs messages as this progresses.
The tests are quite similar atm. I think over time the server level tests will be changed to accommodate the changing structure and output of the application. The location validator is going to change as functionality is added e.g. places of interest, towns, etc. but the tests for the postcode validation are likely to be required in a form closely related to how they currently are. Which is a long way of saying I know the tests might look like they are copied but I think that is OK atm!


Trunk compilation is broken with the Swift 5.7 compiler on linux

I reported this earlier on the offending pull, but filing an issue to make sure it is handled.
The error:
Sources/System/MachPort.swift:75:5: error: deinitializers may only be declared within a class or actor
    deinit {
    ^

Yes, I'm hitting this too with 5.7 releases.
$ git rev-parse HEAD
ccea4eed1aba98022a7af65875ffdf2d821450da
$ jw-docker-swift-5.7  swift build
Building for debugging...
/Users/johannes/devel/swift-system/Sources/System/MachPort.swift:75:5: error: deinitializers may only be declared within a class or actor
    deinit {
    ^
/Users/johannes/devel/swift-system/Sources/System/MachPort.swift:75:5: error: deinitializers may only be declared within a class or actor
    deinit {
    ^
/Users/johannes/devel/swift-system/Sources/System/MachPort.swift:75:5: error: deinitializers may only be declared within a class or actor
    deinit {
    ^
[25/25] Compiling SystemPackage Exports.swift


Added apache 2.0 license

Hi!  👋
I was hoping to add an Apache 2.0 license to this repo to clarify that the k8s config in this repo is able to be used under the same permissive licensing as the broader Keycloak project. I copied the license directly from https://github.com/keycloak/keycloak, but feel free to commit it separately from this PR if you'd rather have it added by a maintainer.
Thanks!

cc @vmuzikar @stianst


Dynamically setting cache key causes crash

I'm setting my cache on the fly, because depending on the page I want to have a different cache since my JS files are split per page.
So I do $this->reactRenderer->setCache($this->cacheItemPool, $myDynamicKey);
$this-cacheItemPool is the Symfony cache adapter and the dynamic key consists of the page and another id like string. When using this V8JS just seems to crash, but I can't find any more detailed information besides some invalid OPcode messages in the syslog or short message in the php-fpm logs.

This was not an issue with cache. This was an issue with using babel-polyfill on the server.
Hard to find, because I don't know where to check the logs for v8js, v8 or ReactRenderer, but I found the solution thanks to another issue on another repository.


Web Chat doesn't work

Message Bot source published. Preparing bot application to run the new source.
Deployment successful!, after that, I've deleted the bot secret and saved it. Still, when trying to use web chat, got a blank screen, and when said "hi" the message couldn't be sent. How do I confirm if the bot is ok? Or whatelse did I miss? It is working in the emulator. Thanks.

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

ID: 9d5bd35d-3178-42cd-2893-3b6a4b7a94ce
Version Independent ID: 1545fd44-d471-d947-f94d-4b5e8d6e853f
Content: Tutorial to create and deploy a basic bot - Bot Service
Content Source: articles/v4sdk/bot-builder-tutorial-basic-deploy.md
Service: bot-service
Sub-service: sdk
GitHub Login: @ivorb
Microsoft Alias: v-ivorb

Now it just show "Waiting for bot to be ready after deployment"

This typically happens when the deployment was not successful, even though you don't get any messages.
If your bot works locally in the Emulator, then refer to this document on deployment.
Note that we used to create a .bot file when you created a bot in Azure, but now we don't. You should use appsettings.json or .env file.


BI-9132: add Dockerfiles for Node 16

This could benefit from a little more description to add context. The main people to comment on this will be @sroberts2 and @Jata2k who have been most closely involved in the Node 16 work.


The mod doesnt work.

I was making a modpack and wanted to put Dynamic Surroundings into it. But I've been having some problems with that. When I put it in the Mods folder in Forge, and enter the game the mod just doesn't work, can anyone help me?

What version of Minecraft, Forge, and Dynamic Surroundings are you using?  Need specific version numbers.

I need this info too.  I tried to install java 15.0.2 SE Development Kit and set the path in environment variables and I have forge 36.0.10 installed.  I can boot the game to just before the terrain loads in...(I can see the hotbar) and then it crashes saying that the java version used in the mod uses a newer java version. (I removed all other mods by the way).

Make sure you use the latest version of Dynamic Surroundings, which as of this AM is <IP_ADDRESS>.

Thank you for patching this up!  It works and looks great!  Cheers!

What version of Minecraft, Forge, and Dynamic Surroundings are you using? Need specific version numbers.

minecraft: 1.16.5, Dynamic surroundings: also 1.16.5

This may be a weird question, but did you install Forge?  In the past couple weeks I have encountered several players that did not do that step.


GEOMETRY column in MYSQL not mapped.

GEOMETRY column in MYSQL not mapped in sink connector.

point :
CREATE TABLE `airport_geo` (
  `airport_id` smallint NOT NULL,
  `name` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NOT NULL,
  `city` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `country` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `latitude` decimal(11,8) NOT NULL,
  `longitude` decimal(11,8) NOT NULL,
  `geolocation` point NOT NULL,
  PRIMARY KEY (`airport_id`),
  SPATIAL KEY `geolocation_spt` (`geolocation`),
  CONSTRAINT `airport_geo_ibfk_1` FOREIGN KEY (`airport_id`) REFERENCES `airport` (`airport_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci COMMENT='Flughafen DB by Stefan Pröll, Eva Zangerle, Wolfgang Gassler is licensed under CC BY 4.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/4.0'

Debezium stores the Geometry value in WKB format and SRID.
The WKB needs to be parsed
    /**
     * Create a value for this schema using WKB and SRID
     * @param geomSchema a {@link Schema} instance which represents a geometry; may not be null
     * @param wkb OGC Well-Known Binary representation of the geometry; may not be null
     * @param srid the coordinate reference system identifier; may be null if unset/unknown
     * @return a {@link Struct} which represents a Connect value for this schema; never null
     */
    public static Struct createValue(Schema geomSchema, byte[] wkb, Integer srid) {
        Struct result = new Struct(geomSchema);
        result.put(WKB_FIELD, wkb);
        if (srid != null) {
            result.put(SRID_FIELD, srid);
        }
        return result;
    }
}

Added fix in 2.4.0 to support GEOMETRY datatype in MySQL.


Dispatch Scheduled Jobs from Apex

Custom Label

CallableApiMethodNotImplemented

Critical Changes
Changes

We added the ability to dispatch scheduled jobs from Apex with an update to the Callable_API class.
Thank you to @koenwesselman for this contribution!

Issues Closed
Community Ideas Delivered
New Metadata
Deleted Metadata

Track W-8712689

@force2b @andrewyu-salesforce Ready for review.  Would appreciate your feedback.
@sam-knox @mattwashington There is a new label here.  Would appreciate your review.
Thanks all!!!

@force2b Code review suggestions have been implemented.
Really like refactoring into delegation service to support the possibility of extension!
I debated making CallableApiApexDelegationService global to provide the same level of visibility, but since it is never directly called outside the managed package, decided that was a poor approach, so made it public.  Happy to change if you feel differently about this.

@force2b Change requests have made.   Would appreciate another pass from you.  Thanks!

@force2b Added logic to throw ParameterException in the edge cases of an empty job name or cron expression.  Both of those cases return unhelpful apex errors by default.  Also added unit tests to validate behavior in those scenarios.
Would appreciate another peek at this.  Thank you!!

@sam-knox Altered the label per your request.
@force2b @andrewyu-salesforce The label change introduced a test failure which I have corrected.
@rponti-sforg No changes to non-test code other than the label.

@npsp-reedestockton , this may not be the place to raise it - but the CallableApiApexDelegationService does not seem to be a global class, so its not currently publicly accessible in the sandbox beta release.

@npsp-reedestockton - Oops, ignore my previous comment! Its not the delegator that's global because we're still passing through the Callable_API.. My mistake!
Thanks so much for your changes and taking my minor contribution to the next level in incorporating it in NPSP! Much appreciated and will make a huge impact for our project in terms of overnight Scheduled Job performance! :-)

@koenwesselman Glad to hear things are okay.
The reaction to your contribution has been tremendously enthusiastic.  Thanks again for your major contribution!!


Fenrir - Hunger of the Wolf (human) got Frenzy instead of Lycan Form

I chose to deal myself damage at the start of Fenrir's turn as a human, and it played Frenzy instead of Lycan Form.

Fixed!

Fixed!


Mime type in metadata

add a new column, filetype
provide a default mapping of mime to this new file type
http://help.dottoro.com/lapuadlp.php
http://www.freeformatter.com/mime-types-list.html
http://fileinfo.com/browse/

@markkerzner  I added new column, pre-filled with content types from files in test-data, will add remaining content-types later.

@markkerzner can you merge this?

Tested, merged, and closed


[homebridge] move chart to ghcr repo

this just moves homebridge to @oznu's new ghcr repo

ugh i failed on this. will make another one later


Generate implementation of Parse trait, instead of parse method

Tracking issue for the following idea:
Instead of generating a parse method, it may be more interesting to generate an implementation of the parse trait.
Some thoughts:

instead of one implementation, this would generate two different methods (parse_be and parse_le), one for each endianness
this means the BigEndian / LittleEndian struct attributes may gain a new meaning (for ex, the struct is always parsed with this endianness, so generate only one implementation and make other methods use the same). The field attributes would not be changed.
Generating the trait is not possible when using the ExtraArgs attribute, since it changes the method signature. Not sure how to deal with this (keep generating only the parse method - not trait - in that case ?)

Note: not working with ExtraArgs also means enums will not implement this trait, because they have to specify a selector.


Add implementation and tests for the JobRunrProEventScheduler and JobRunrProDeadlineManager.

It needs the correct credentials and https://github.com/AxonFramework/AxonFramework/pull/2564 to be merged before it will build.

 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.


Explore logging options

https://newrelic.com/
https://developers.cloudflare.com/workers/learning/logging-workers
https://developers.cloudflare.com/logs/

Revisit after upgrading plan or more server-side logic.


Django 1.10 incompatibility: model instance has no _default_manager attribute

It appears that Django 1.10 removes the _default_manager attribute from model instances (per: https://code.djangoproject.com/ticket/26652).  django-celery currently uses this attribute in the ModelEntry class in schedulers.py (https://github.com/celery/django-celery/blob/bac46064cf19f6de026a3ed30b54569fb1aa325e/djcelery/schedulers.py#L98).  As a result, using django-celery with Django 1.10 results in errors like this:
[2016-06-25 20:14:42,098: ERROR/Beat] Process Beat
Traceback (most recent call last):
  File "/Users/mfenniak/.virtualenvs/iohint-background/lib/python3.5/site-packages/billiard/process.py", line 292, in _bootstrap
    self.run()
  File "/Users/mfenniak/.virtualenvs/iohint-background/lib/python3.5/site-packages/celery/beat.py", line 553, in run
    self.service.start(embedded_process=True)
  File "/Users/mfenniak/.virtualenvs/iohint-background/lib/python3.5/site-packages/celery/beat.py", line 486, in start
    self.scheduler._do_sync()
  File "/Users/mfenniak/.virtualenvs/iohint-background/lib/python3.5/site-packages/celery/beat.py", line 276, in _do_sync
    self.sync()
  File "/Users/mfenniak/.virtualenvs/iohint-background/lib/python3.5/site-packages/djcelery/schedulers.py", line 209, in sync
    self.schedule[name].save()
  File "/Users/mfenniak/.virtualenvs/iohint-background/lib/python3.5/site-packages/djcelery/schedulers.py", line 98, in save
    obj = self.model._default_manager.get(pk=self.model.pk)
AttributeError: 'PeriodicTask' object has no attribute '_default_manager'

This PR fixes the issue by accessing _default_manager on the model type, rather than the model instance.

thanks for the patch.


Block new disposable domain

Provider is https://skiff.com/quick-alias and it's actually subdomains, each user can generate their own subdomain. I tested it, very easy.
The page title of https://skiff.com/quick-alias is "Quick alias burner email address". In the HTML I see
<meta name="description" content="Secure and quick-to-create burner email addresses with Skiff!

There is a browser plugin https://github.com/irazasyed/email-masker to create one email per website, skiff.com's twitter account promoted it, the github repository is tagged as 'burner-email'
You should add:

maskmy.id because it is there main domain
anything.maskmy.id because it allows you to create disposable addresses with random subdomains

Also
mailbox.zip
sailmail.io

They just added new domains:

@groundcat


[Suggestion] Make loaders input always lane-balanced

Hello!
Just noticed weird behavior with loaders - if I use a loader-chest-unloader as a buffer and consumption down the line prefers one lane then the first loader loads only from left lane
Some small test in creative mode -

On the right you can turn on/off lane consumption by rotating loaders into trash chests, if only one of them is active then the whole system only consumes left lane from output chest on the left
Blueprint string:
0eNqllttywiAQht+Fa+wEyMHkVTodJ5rVMpNAhkOnjpN3LyStp0YFvTIJsh/7/wvsAa1bC73iwqDqgPhGCo2q9wPSfCfq1n8z+x5QhbiBDmEk6s6/bWttFq2sG1BowIiLBr5RRQYcNtOoWuheKrNYQ2vOItDhAyMQhhsO00LGl/1K2G7tWBU5BuJiy4UbWmw+QRsH6KV206TwaBdqQZZvGUZ790Td08iYZqw0GMPFTvt/KujkF6ysG2sNKGhWfr1uyCgLg0/oagV0VoS7+MLBG65gM42n+E8aaU1vff7/KOySovuWGzPPKY+c9JJDZ+Kmd424m0XmRJyJmF1GtM5ItVPS/QbETEdjHqqRh7ueJsfg7EnXMZq+TgX4C9a23Vqv/8al5jZLlmDUycYP1a4KoB5Xc9wIH3NSFYGlw8qLDM4tDRBrGWkxy68Ue1BCZWz8Ii4+SUJlyh7LxMUNlQgJpdBXzCCn40IbgPZm3TJ2pdK6Vr8n6nVIFmtAEmlAGigNLV8xIAul5C8ZkAcaQItgA4pIA/wxF2VA7BamLBIQu4cpjQPQJBYQWaOUxAJIJIA+f1OGAVj8xXnnJA1pKmj07X8C0n/AOUDonj4LTG7lcfPkoBHtwAnk+6Qnm0DXk45NbHXWLWP05TqEyd0lSYuSFsu8TFiSDsMPhOS0ug==
Just to be sure I tested that this happens specifically with 5dim transport mod -

Created new sandbox game with all mods disabled
Made same test blueprint with vanilla loaders, they did load from both lanes
Enabled 5dim core, transport, and bob inserters mods and loaded the sandbox
Vanilla loaders got replaced with modded ones, and they now consume left lane only

Some thoughts:
I don't actually know why but I can't reproduce the 'proper' behavior with vanilla loaders, which I thought were loading from both lanes always. I must be going senile :(
Anyway the problem is actually non-existent if you want to use loaders for single belt lane balancing (loader->chest->loader).
It doesn't work if you limit chest slots or use it to fill up to max, but it works as a lane balancer if you limit chest with circuit instead of limiting slots. Connect a circuit line from belt before to chest and make the belt work only if chest contains less than X items.
From my understanding of situation - imagine your buffer chest is full, only one lane is actively consumed after the buffer. One item at a time goes out through output loader, one item goes in since there's only enough space in chest for 1. So that means input loader would only load 1 item per cycle, consuming only single lane in the end.
With circuit stopping the belt before loading, it loads 'in bulk' all the items that are on that belt segment. So effectively it loads equally from both input lanes


Dataset Downloading Error

Hi All,
Thank you very much for this project!
I tried to run sh download_speaker.sh Dataset/chem but it seems there is a problem downloading the videos from youtube.
This is the error I'm getting:
Downloading Train set of chem
[youtube] rvPHWWNYC0I: Downloading webpage
[youtube] rvPHWWNYC0I: Downloading video info webpage
ERROR: rvPHWWNYC0I: YouTube said: This video is unavailable.

which stops the training set download process, the same happens for val/test sets. I tried to check if it is possible to see the video directly from Youtube's website and indeed it is possible (so the video exists).
Thank you in advance.

Please update your youtube-dl package and try again:
pip install --upgrade youtube-dl

I have done the following:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install youtube-dl

didn't work for me :/

Please update your youtube-dl package and try again:
pip install --upgrade youtube-dl

Please do this and re-open the issue if it does not solve the issue.

@prajwalkr @Rudrabha @AvivSham Can you tell how to run this command in windows CMD terminal ? as sh is for linux.


Scrolling in MutationList

The column headers and lineage search bar scroll with the mutation list content – these elements should be frozen to the top like the rest of the mutation list header elements

Closed by #388


Update google-cloud-pubsub to 1.123.6

About this PR
📦 Updates com.google.cloud:google-cloud-pubsub from 1.107.0 to 1.123.6
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.cloud", artifactId = "google-cloud-pubsub" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.google.cloud", artifactId = "google-cloud-pubsub" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #335.


424 Error when delegating an Operation

When delegating an Operation from the AAS Environment to an Operation in the SubmodelService, a 424 Failed Dependency (WebDAV) (RFC 4918) error occurs.
The qualifier is set correctly, because when delegating the Operation from the AAS Environment, it correctly connects to the SubmodelService.

Error Code 424 is signalling that the HTTP/REST endpoint being delegated to is returning an error code. Can you provide more details about your setup and test if the endpoint delegated to is working as expected?

Sure!
The setup contains an AAS-Environment which contains the following Operation that delegates the Operation to the SubmodelService:
and the corresponding SubmodelService that contains the square operation which gets actually executed.

The square operation is the same as the one from the examples and works when invoked directly:

I used host.docker.internal as the hostname because both components are launched locally via a docker-compose file. I tested the invocation via the AAS-WebUI and manually with Postman. In both cases i get the same error 424.
When looking further into the logs of the docker container, there are no other loggings that indicate an error.
The OperationDelegation feature is enabled and I use the most recent image of the AAS-Environment.
I also made sure that the AAS-Environment container can connect to the SubmodelService by directly sending the request inside the container:

Thank you very much for providing more details. This should work indeed - would it be possible to upload your complete setup (docker compose, AASX, project for the Submodel Service) to GitHub or share via other means with me?
Regardless of this issue, wouldn't it make more sense to move the complete Submodel contained in the Repository to a standalone SubmodelService or vice-versa, only implement the operation interface without the need for starting a complete SubmodelService?

Is this issue still relevant?

I think it is not relevant anymore. Thanks for your suggestions :)


Suggestion regarding the YouTube Notifications

Hi,
i really love your chrome extension. It works great for my purposes.
The only improvement i would really like to suggest is an extra button on the pop-up alongside  'Watch' and 'Dismiss' that would allow me to add the video to the 'watch later' queue on Youtube.
(Don't know if there are potential problems with rights management regarding the google account that would make this difficult?)
Thanks for your great work so far
Best regards
Heiko

I have the bare bones of your requested feature completed. I just have to make some minor adjustments. Thanks for your suggestion!

I have published the latest version to the Chrome web store and should be available within 24 hours.  If you have any more issues or suggestions regarding this, feel free to message me.

Just updated to <IP_ADDRESS>
New feature works perfectly. Thank you very much my friend :)


docs: Indicate that restore-keys uses prefix in README

I think we should state here that restore-keys supports prefixes as it is mentioned here.

I'm not sure if this is required. The line An ordered list of keys to use for restoring stale cache if no cache hit occurred for key already signifies what you are trying to add.

@vsvipul "list of keys" does not disclose that the keys can be prefixes to the keys.

Something like An ordered list of prefix-matched keys to use for restoring stale cache if no cache hit occurred for key

@vsvipul good idea.

Thank you for contributing 🎉


Clarify minimal supported rust version.

Another simple PR to clarify we are relying on Rust 1.18 or later.

Thanks! We'll need to be vigilant to keep this up to date, for example we're considering eprintln! which I think would bump this to 1.19.


feature request: exampes += --list-devices | --input-device | --output-device flags

feature request: exampes += --list-devices | --input-device | --output-device flags
When trying streaming example,  scripts seems to "detect speech" after each chunk of sound it voices out, and interrupting itself, even I try to run it with headphones. Therefore I consider that maybe it is using wrong input device or something else is going on. Also manual input seems very confused and not working correctly.
Platform: Linux, in fresh venv.

Same issue here, it seems there is no echo cancellation done (to cancel the output signal on the input one).
A threshold could be used in order to prevent sending input chunks with low-intensity voice (which would in most cases come from the output signal being heard by the microphone).
Did you try lowering the output intensity in your headset to make sure the microphone doesn't catch anything @gwpl?
I managed to chat with the model by muting my microphone whenever I'm not speaking, but that's not a viable solution.

In addition to using microphone, this change has also helped in fine tuning the audio response and avoid any interruptions. - https://github.com/run-llama/openai_realtime_client/pull/5.


How to write conf content in coding

I would like to use tinkerpop connection elasticsearch, I have written a json configuration file, how should I add this configuration file to conf? The code did not talk about how to write conf on json configuration.

You need to create a configuration like so
BaseConfiguration conf = new BaseConfiguration();
conf.addProperty('providers', '/path/to/mapping/folder');
UniGraph graph = UniGraph.open(conf);

@seanbarzilay
Thank you for your immediate reply. I write the above code on IDEA, as follows:
BaseConfiguration conf = new BaseConfiguration();
conf.addProperty("providers","/company/tinkerpop-server/json/");
UniGraph graph=UniGraph.open(conf);
GraphTraversalSource g=graph.traversal();
System.out.println(g.V().key());
and I copy your modern.json to my folder.but when I run the application,it told me this:
org.json.JSONException: A JSONObject text must begin with '{' at character 1
but I checked out the modern.json there is no character error,the modern.json is providered by this project,and I do not know how to do next?

@seanbarzilay
Thank you for your immediate reply. I wrote the above code on IDEA, as follows:
BaseConfiguration conf = new BaseConfiguration();
conf.addProperty("providers","/company/tinkerpop-server/json/");
UniGraph graph=UniGraph.open(conf);
GraphTraversalSource g=graph.traversal();
System.out.println(g.V().key());
and I copy the modern.json to my folder.but When I run my application,It show me this:
org.json.JSONException: A JSONObject text must begin with '{' at character 1
I checked out the modern.json file .There is no character error.and the modern.json is provided by this project.so I don't how to do next? Look forward for your reply.

Do you maybe have another file in that folder which is not a JSON file?

It works! Because my folder has a hidden file, so I delete the hidden file, you can successfully mapped.thank you for your help!

It works! Because my folder has a hidden file, so when I delete the hidden file,  can successfully mapped.thank you for your help!


How to add a new model with a .pth file ?

Hi.
I would like to use ollama with https://huggingface.co/manu/mistral-7B-v0.1.
The files available are :
tokenizer.model
consolidated.00.pth
params.json
RELEASE

Thanks.

mistral 7b is available in the library. However if you want to add it from original weights, you'll need to convert it to gguf and optionally quantize. more information can be found in llama.cpp


Support http/2.

This PR is rebased and added tests from https://github.com/expressjs/express/pull/3390
We need to disable some tests on http/2, as some node module have issue with http/2. PR pending on resolution of the following issues:

[ ] // cookies with http2 has an issue https://github.com/pillarjs/cookies/pull/99
[ ] // vhost with http2 has an issue https://github.com/expressjs/vhost/pull/29
[ ] // HEAD with http2 does not support response body

ping @dougwilson

I saw the PR come in, just haven't had time to look over it yet, I apologize.

Update: Node.js v10.10.0 was released an hour ago, and http2 module is no longer experimental
https://nodejs.org/en/blog/release/v10.10.0/

So I started taking a look into this, and it seems like this is good, but only a first pass.  Mainly, the test suite of Express doesn't extensively test all of it's dependencies, even just the high-level ones like express.static and express.json, etc. These seem to not work correctly under the HTTP/2 implementation in this PR. I think that definitely makes the PR a bit less than ideal here.
I'm going to write up a list of the issues I'm finding. Also, it seems like there is at least one more test disabled for HTTP/2 not mentioned in the OP. We may want to add a checkmark list (I did that already) and track what is the known-outstanding issues. One of the comments in the PR is HEAD with http2 does not support response body but I'm not sure what that means -- the test is not trying to send a response body to a HEAD, as HTTP/1 doesn't support a response body in a HEAD, either.

One of the comments in the PR is HEAD with http2 does not support response body but I'm not sure what that means -- the test is not trying to send a response body to a HEAD, as HTTP/1 doesn't support a response body in a HEAD, either.

It's my misunderstanding. I look into it and find issue about sendFile with http2 head method.
Failing sendFile with head method is caused by difference with http_outgoing_message and http2ServerResponse. http2ServerResponse.finished with head method is true from its made, but http_outgoing_message.finished with head method is false until calling http_outgoing_message.end().
res.sendFile with head method seems to depend on the order.

call onfile.
call onfinish.

However, http2ServerResponse.finished is always true so that onfinish is called first.
I will fix it tomorrow.

@sogaani superagent just dropped the HTTP/2 support https://github.com/visionmedia/superagent/commit/b08371c72fbdca40dda3ad39fe8bbbee4a2718d5 maybe you can help them, or maybe we just need to use something else for our http/2 tests.

@dougwilson Thank you telling me that. I made PR for superagent. https://github.com/visionmedia/superagent/pull/1414
I added same change here.

I think the tests are revealing some kind of Node.js bug:
     Uncaught TypeError: Cannot read property 'trailers' of undefined
      at Immediate.finishSendTrailers (internal/http2/core.js:1467:31)

It is interesting. I will look into it.

Regarding to TypeError, I found a nodejs bug and file the issue. https://github.com/nodejs/node/issues/22855

Since the person making this PR has also dropped off (judging by submission history, and the month or so since an update), what's the progress here? Is this the sort of thing we may see in a month? A year? I can't find any timeline for the next release of Express, so wondering whether this is coming soonish, or should I begin to look into other solution / switching frameworks?

Is there anything I could do to help here?

Both ate correct and on the latter point I am spending all my free time on this task currently.

Guys what is status? Maybe i can help?

/cc @dougwilson friendly ping. Can we release this without major bump? How i can help? Maybe you can to list issues/PRs/TODOs?

Any updates? I can't wait for Lighthouse to stop screaming at me once this gets implemented.

HTTP/2 is not gonna work in browsers unless you have TLS enabled (HTTPS), and you not gonna let Node/Express handle the SSL traffic because it's much of a burden on it, therefore, you would use Nginx as a reverse proxy in production for your node application. And Nginx will handle the SSL traffic and support HTTP/2.
So, for express or even node to support HTTP/2 is just a wild idea and not technically practical in real life (production environment).
See my tut: ( https://github.com/XOR-LIFE/node-production )

HTTP/2 is also very valuable in service-to-service communication between microservices, not just from frontend browsers.

I make a case for why server frameworks (and not just (reverse) proxies) needs to support HTTP/2 in https://github.com/aspnet/AspNetCore/issues/4249#issuecomment-460288563. There's more use-cases, but I think the one explained there is a pretty strong one.

/cc @dougwilson friendly ping again, what is blocker, where i can help?

https://github.com/expressjs/express/pull/3730#issuecomment-441338216

@dougwilson thanks, any roadmap/ideas/spec how we can solve this and how i can help? It seems to me that now nobody works on this and it is very awful, a lot of software is used express and need this feature so I offer my help, but without feedback from core developers i can't help.

Currently we are trying to focus on the 5.0 release so it does not continue to be years without release. We will come back to focus on items like http/2 once the 5.0 is out and work to figure out the points you have raised around 5.0.

@dougwilson how i can help with 5 version? Looks no commits from May 26

We are working on the docs in the expressjs.com repo currently.

@dougwilson thanks for feedback, any ETA for 5 version? We really need https support :disappointed:

Express 5 is coming out asap. That is why the TC decided to push all these other things to the side and get 5.0 out. None of us are paid for Express work, which consequently means that we have day job obligations that take priority, least we loose the roof over our heads. I bring this up because having an ETA with unpredictable hours is not very possible is all, besides saying that it is asap because it's the only focus at the moment.
Express already supports https even without http/2

@dougwilson oh, i was wrong about https, i mean http/2, thanks for feedback, if you need help with express@5 feel free to ping me, i can find time on help

@dougwilson if there are any specific things you'd like help with please let me know
It's now impossible to use webpack-dev-server with HTTP/2 anymore because spdy is broken past node 11.1

None of us are paid for Express work, which consequently means that we have day job obligations that take priority, least we loose the roof over our heads.

@dougwilson maybe you already have thought about this idea and also I'm not the person who should say this pardon :grimacing:
Something like opencollective may help to attract more people to spend their valuable time on valuable open-source projects like this one.

Hey @devsumanmdn, I am going to mark this as off topic, but I agree and if you would like to discuss more on this topic I have this issue open: https://github.com/expressjs/discussions/issues/69

To step forward this PR, I'd like to clarify the issues with http2 compatibility layer and make sure the criteria for landing this PR.
I thought rewriting http1 tests of nodejs to http2 is a reasonable way.
Here is the initial repo: https://github.com/sogaani/http2_compat_tests
Thanks to the efforts of making the compatibility layer, many tests of this repo are passed. However, this repo exposed 38 failer test cases(possibly increase). As @dougwilson said, this failer will cause a lot of breakages.
After notifying a lot of differences between http2 compatibility layer and http1, to make the new abstraction layer that @dougwilson is trying needs too large effort to maintain.
Since 38 failers include luck of API(e.g. res.writeProcessing, req.connection.bytesWritten ) and different behavior of API(e.g. res.setHeader cannot overload automatically adds), I think the http2 compatibility layer still has spaces to improve compatibility.
Because the repo did not expose the issue I found here, rewriting http1 tests of nodejs to http2 can not find all issues, but I think it still reasonable to be the criteria for landing this PR.

Express 4.0 + spdy + Node 10 work like a charm

2 years gone and still no http2 here. Any developers here? Any news? We can't work with NodeJS 10 anymore, but we need the http2 support at least on the localhost. Spdy module has stopped the support. :(

This gist can help somebody who needs to use spdy only for development http2 server with express js

@sogaani I read the related issues (and above), can you still clarify what the blocker in the current approach is? Any chance of helping (likely no luck ): )? Cheers

There is a core bug in HTTP/2 in Chromium/Chrome I found:
https://bugs.chromium.org/p/chromium/issues/detail?id=1045328#c50

@eljefedelrodeodeljefe
Referring to  https://github.com/expressjs/express/pull/3730#issuecomment-441338216
Current blocker is nodejs http2 compat layer does not compatible with http module and it cause breakages when we use http2 compat layer as it is.
Current approach is create new request and response object that wrap and hide differences between http2 and http module.
Maybe, @wesleytodd work on first step of that on https://github.com/expressjs/discussions/issues/82
I exposed the differences to fix them on https://github.com/nodejs/node/issues/29829

@sogaani Please update the community on the progress - thank you again of spending time on this.

Found this project, which may be just the right thing for non-production use: http-express-bridge  (You get what you pay for.)

@sogaani Please update the community on the progress - thank you again of spending time on this.
https://github.com/expressjs/express/pull/3730#issuecomment-780366418

Almost another year has passed -- HTTP/3 is around the corner ...

Any update on HTTP/2 support in Express?

Hey there, is express now supporting http/2 ?

Really?!?! My comment was marked as spam? How about something productive like a status update instead?

I have not been working on this PR for long time. Currently I don't have much time to progress.
I would be happy if someone could take over this PR.

Any update on HTTP/2 support in Express?

what the time line on this

any updates?


MongoDB

I currently have Oura setup to create .json files for me and my filter is, all metadata with label 721.
I then take the JSON files and dump them into mongoDB. Everything seems to be working fine, but not always when I search for a PolicyID mongoDB returns a result, however I do know it does exist.
I was wondering if anyone who is using mongoDB to create a search able index would be willing to share their configuration and maybe the search query as well since the policyID is a key not value.
Thank you,
Bakon

hi @bakon11 do you have an example of one of those policies? I have a similar setup using the Elasticsearch sink, I can see if for some reason we're missing the same data.

So actually I just realized that the query I am using in mongosh does not work the same way using in nodejs when searching an object by KEY.


SendKeys.SendWait() sends wrong characters for some particular characters

Using:
Windows 10
.NET Core 3.1
Library System.Windows.Forms
Function SendKeys.SendWait()
Reproduce steps:

create a new project with those 2 lines in Main:

Thread.Sleep(5000);
SendKeys.SendWait("ĚŠČŘŽÝÁÍÉÚŮĎŤ");

Switch to Czech QWERTZ keyboard on Windows (on standard English keyboard you get the expected result)
Run the project and (during the first 5 second since the start) open some notepad or something like this
observe ěščřžýáíéúůĎŤ being written

Expected result:
observe ĚŠČŘŽÝÁÍÉÚŮĎŤ being written
Note + possible cause of problem:
On Czech Keyboard, all of letters ĚŠČŘŽÝÁÍÉÚŮ could be written by pressing a single button on keyboard in case that CapsLock is turned on, but ĎŤ couln't (Ď has to be written by pressing ˇ (actually Shift + key on the left of Backspace) and then D (Shift + d)), so maybe SendWait() gets info about keyboard keys, and if the characters that could be written on this keyboard using 1 key (+Shift/CapsLock), then it presses according keys, but in other case, it just presses maybe Alt+KeyCode or something. And in the first case, it forgets about pressing CapsLock when writing letters that are keyboard language-dependent.

This issue was moved to dotnet/winforms#2660


New optional Mesa inline table behaviour using tooltips

Note this targets the ongoing orthogroup branch.
The default Mesa behaviour when options.inline is true, is for cell contents to be truncated so the rows are equal height. Clicking on the rows expands them to show the full contents.
This wasn't acceptable for ortho, where the tree and table alignment is messed up by expanding rows. (Also browser scroll-to behaviour is unpredictable and you can't easily find the row you expanded.)
With this PR there's a new configuration option: inlineUseTooltips which removes the click behaviour and adds tooltips to all table cells.
It would be nice to do this for
a) only cells with content
b) only cells that overflow
but neither are economical to implement at this time.

I'm using it here!
It was a useful way to get fixed-height rows. Until someone clicked on them of course...

I'm going to merge to orthogroup-tree-table. Going to be off grid for a few days and it would be nice to get this on the feature site.


[SPARK-31078][SQL] Respect aliases in output ordering

What changes were proposed in this pull request?

Currently, in the following scenario, an unnecessary Sort node is introduced:
withSQLConf(SQLConf.AUTO_BROADCASTJOIN_THRESHOLD.key -> "0") {
  val df = (0 until 20).toDF("i").as("df")
  df.repartition(8, df("i")).write.format("parquet")
    .bucketBy(8, "i").sortBy("i").saveAsTable("t")
  val t1 = spark.table("t")
  val t2 = t1.selectExpr("i as ii")
  t1.join(t2, t1("i") === t2("ii")).explain
}

== Physical Plan ==
*(3) SortMergeJoin [i#8], [ii#10], Inner
:- *(1) Project [i#8]
:  +- *(1) Filter isnotnull(i#8)
:     +- *(1) ColumnarToRow
:        +- FileScan parquet default.t[i#8] Batched: true, DataFilters: [isnotnull(i#8)], Format: Parquet, Location: InMemoryFileIndex[file:/..., PartitionFilters: [], PushedFilters: [IsNotNull(i)], ReadSchema: struct<i:int>, SelectedBucketsCount: 8 out of 8
+- *(2) Sort [ii#10 ASC NULLS FIRST], false, 0    <==== UNNECESSARY
   +- *(2) Project [i#8 AS ii#10]
      +- *(2) Filter isnotnull(i#8)
         +- *(2) ColumnarToRow
            +- FileScan parquet default.t[i#8] Batched: true, DataFilters: [isnotnull(i#8)], Format: Parquet, Location: InMemoryFileIndex[file:/..., PartitionFilters: [], PushedFilters: [IsNotNull(i)], ReadSchema: struct<i:int>, SelectedBucketsCount: 8 out of 8

Notice that Sort [ii#10 ASC NULLS FIRST], false, 0 is introduced even though the underlying data is already sorted. This is because outputOrdering doesn't handle aliases correctly. This PR proposes to fix this issue.
Why are the changes needed?

To better handle aliases in outputOrdering.
Does this PR introduce any user-facing change?

Yes, now with the fix, the explain prints out the following:
== Physical Plan ==
*(3) SortMergeJoin [i#8], [ii#10], Inner
:- *(1) Project [i#8]
:  +- *(1) Filter isnotnull(i#8)
:     +- *(1) ColumnarToRow
:        +- FileScan parquet default.t[i#8] Batched: true, DataFilters: [isnotnull(i#8)], Format: Parquet, Location: InMemoryFileIndex[file:/..., PartitionFilters: [], PushedFilters: [IsNotNull(i)], ReadSchema: struct<i:int>, SelectedBucketsCount: 8 out of 8
+- *(2) Project [i#8 AS ii#10]
   +- *(2) Filter isnotnull(i#8)
      +- *(2) ColumnarToRow
         +- FileScan parquet default.t[i#8] Batched: true, DataFilters: [isnotnull(i#8)], Format: Parquet, Location: InMemoryFileIndex[file:/..., PartitionFilters: [], PushedFilters: [IsNotNull(i)], ReadSchema: struct<i:int>, SelectedBucketsCount: 8 out of 8

How was this patch tested?

Tests added.

Test build #119498 has started for PR 27842 at commit 0dc6b08.

Merged build finished. Test PASSed.

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

Test build #119498 has finished for PR 27842 at commit 0dc6b08.

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

Merged build finished. Test PASSed.

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

Test build #119528 has started for PR 27842 at commit add187a.

Merged build finished. Test PASSed.

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

cc: @cloud-fan

Test build #119528 has finished for PR 27842 at commit add187a.

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

Merged build finished. Test PASSed.

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

Test build #119588 has started for PR 27842 at commit 346a6d3.

Merged build finished. Test PASSed.

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

Test build #119588 has finished for PR 27842 at commit 346a6d3.

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

Merged build finished. Test PASSed.

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

Test build #119598 has started for PR 27842 at commit fc6bc62.

Merged build finished. Test PASSed.

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

Test build #119598 has finished for PR 27842 at commit fc6bc62.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Merged build finished. Test PASSed.

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

Test build #119605 has started for PR 27842 at commit fc6bc62.

Test build #119605 has finished for PR 27842 at commit fc6bc62.

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

Merged build finished. Test PASSed.

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

thanks, merging to master!

late LGTM, thanks, guys.


Replace replacePage with redirectPage

Current @nanostores/router has no replacePage.

Thanks. I forgot to update docs 😅


error installing (solved)

I'm installing on a fresh Debian 8, livestreamer installed. Having trouble with python-librtmp.
EDIT: I should have read issue #10 , installed librtmp-dev and all is fine.

You should close this issue.


toLeopard: Avoid overwriting any browser globals, perhaps

From @PullJosh: https://github.com/leopard-js/sb-edit/pull/137#discussion_r1614635282

Question: Do we want to blacklist browser-provided identifiers like Array, Audio, Error, File, Map, Set, Temporal, etc., which are not used in generated Leopard code but could cause conflicts or confusion when the user starts adding their own hand-written JS code?
There are a lot of them. And keeping up-to-date might be challenging.

We're really interested in this point. It's true that with the new PR, we avoid overwriting globals which in-scope generated Leopard code depends on, fixing certain project runtime bugs when the fates align poorly (#133).
But that's not the only reason to avoid overwriting globals. Like PullJosh wrote, users who are learning JavaScript will start to use lots of browser-provided globals. (And likely pretty quickly! BTW, Object is missing from your list ✨) It would be nice if generated code never overshadowed at least the popular ones.
It would be pretty snazzy if the Leopard editor gracefully helped you rename sprites, but in the meanwhile (and certainly if you're working in your own text editor) it can be awkward to change a generates sprite named Array over to, well, some other name, when you want to start using array utilities... in the sprite... that is named Array. (You know, after you've introduced code in other sprites that already uses Array, so now the string "Array" means two totally different things in your overall project code.)

Some implementation thoughts:

Yes, maintaining the list ourselves would be awkward. Temporal is a nice new global (good point) and more are getting added all the time. There's obviously a limit to what Leopard should handle, and we wouldn't be totally amiss to just select the most popular ones, or the ones that are part of the ECMAScript standard itself (rather than DOM, etc), or so on. However...
Another alternative is to just use the globals package. This is an abundantly popular package (75M+ weekly downloads, recommended by eslint, etc) and literally automatically up-to-date.
We should probably choose a better name than just tacking on a 2. class Array2 extends Sprite is silly. How about class ArraySprite extends Sprite? Or something else?

Here are all the first-letter-capitalized names in globals.browser.
 (Please note that this is not a subset of globals.browser, i.e. we need to combine them if we want to use both.)
AggregateError Array ArrayBuffer Atomics BigInt BigInt64Array BigUint64Array Boolean DataView Date Error EvalError FinalizationRegistry Float32Array Float64Array Function Infinity Int16Array Int32Array Int8Array Intl JSON Map Math NaN Number Object Promise Proxy RangeError ReferenceError Reflect RegExp Set SharedArrayBuffer String Symbol SyntaxError TypeError Uint16Array Uint32Array Uint8Array Uint8ClampedArray URIError WeakMap WeakRef WeakSet

(Note that the list above includes recent additions like AggregateError.)
So we have a few practical options:

Just hard-code our own list, altogether, but more expansive than currently. Admit that it's not intended to be comprehensive. May be a subset of globals.builtin or a subset of the union [globals.builtin, globals.browser].
Hard-code our own subset of globals.builtin and combine that with globals.browser in its entirety.
Use globals.builtin in its entirety, don't bother with globals.browser.
Use the union of globals.builtin and globals.browser in its entirety.

I'm leaning towards the "don't hard-code anything" options, but could go either way on including globals.browser. There are a lot of names in that list, and most of them are extremely domain-specific. There's a decent chance that users themselves might code new Sprite subclasses with those names, and never run into a problem for it! But do feel free to convince us that globals.browser should totally be part of the reserved sprite name list, if you think that's right. Or share some totally different direction, we're always interested! 🥳

Should we block browser globals? My argument on this is that we'd like to help users write "good" JavaScript code. Of course, "good" is subjective, and there's no one right answer. But creating a class called Array that has nothing to do with JavaScript arrays seems bad. ArraySprite seems like a good compromise that a reasonable human might actually write and is easy to create an sb-edit rule for.
Which globals should we block? Looking at the lists of known globals, I think it would be overkill to block all of them. For example, if a human author were to write their own class called StorageBucket, I would have no objections to that. And I don't think sb-edit needs to either.
Can we generate (and update) the list automatically? I think it's a really, really good idea. My memory says that the most frequent kind of bug we've had to fix in sb-edit thus far is failing to update this list in response to changes in Leopard. To be honest, I think we could write a little script that pulls in Leopard's source code, parses it, and extracts all the method names.
If you accept my previous point–that we should only block some browser globals–then updating the browser globals list is a different beast. Exactly which classes are reasonable to override is totally a vibes-based decision. If we want to automate the process of retrieving/generating these lists, we could probably come up with a metric that approximately matches our own personal ✨vibes✨. I propose a metric based on how commonly different keywords appear in JavaScript code on the web. I'm not sure if that data exists anywhere.

To be honest, I think we could write a little script that pulls in Leopard's source code, parses it, and extracts all the method names.

We agree, but we aren't sure that source code parsing is an effective approach. We don't have experience with crawling an AST (although perhaps you do). We would rather import the leopard module outright and crawl its exposed classes directly.
Example script (this works in the Node.js REPL!)
leopard = await import("leopard");

classNames = Object.keys(leopard.default);
/* [
  'Color',   'Costume',
  'Project', 'Sound',
  'Sprite',  'Stage',
  'Trigger', 'Watcher'
] */

getProtoProperties = proto =>
  (proto
    ? Object.getOwnPropertyNames(proto)
        .concat(getProtoProperties(Object.getPrototypeOf(proto)))
    : []);

spriteProperties = getProtoProperties(leopard.default.Sprite.prototype).sort()
/* [
  '__defineGetter__',   '__defineSetter__',  '__lookupGetter__',
  '__lookupSetter__',   '__proto__',         'andClones',
  'answer',             'arrayIncludes',     'askAndWait',
  'askAndWait',         'broadcast',         'broadcastAndWait',
  'clearPen',           'colorTouching',     'compare',
  'constructor',        'constructor',       'constructor',
  'costume',            'costumeNumber',     'createClone',
  'degToRad',           'degToScratch',      'deleteThisClone',
  'direction',          'getSound',          'getSoundsPlayedByMe',
  'glide',              'goto',              'hasOwnProperty',
  'ifOnEdgeBounce',     'indexInArray',      'isPrototypeOf',
  'itemOf',             'keyPressed',        'letterOf',
  'loudness',           'mouse',             'move',
  'moveAhead',          'moveBehind',        'nearestEdge',
  'normalizeDeg',       'penColor',          'penDown',
  'playSoundUntilDone', 'positionInFence',   'propertyIsEnumerable',
  'radToDeg',           'radToScratch',      'random',
  'restartTimer',       'say',               'sayAndWait',
  'scratchTan',         'scratchToDeg',      'scratchToRad',
  'sprites',            'stage',             'stamp',
  'startSound',         'stopAllOfMySounds', 'stopAllSounds',
  'stringIncludes',     'think',             'thinkAndWait',
  'timer',              'toBoolean',         'toLocaleString',
  'toNumber',           'toString',          'toString',
  'touching',           'valueOf',           'vars',
  'wait',               'warp',              'wrapClamp',
  'x',                  'y'
] */

If we want to automate the process of retrieving/generating these lists, we could probably come up with a metric that approximately matches our own personal ✨vibes✨. I propose a metric based on how commonly different keywords appear in JavaScript code on the web. I'm not sure if that data exists anywhere.

We're OK in principle with a "ranking" or "popularity" usage based on keyword usage online. We swear W3C and TC39 (web API and ECMAScript standards organizations) make fairly frequent use of a tool that hooks into exactly this data, but we can't figure out the name of it right now! We'll look into it.
We think that using this tool will be 100% based on, you know, how practical it is to hook into. Obviously if there's a periodically updated npm package that just says how popular JavaScript words are, that would be great. It's mainly a question of practicality. We don't want to introduce a system that could have a lot of edge cases or maintenance upkeep, even if it gives us a nice quantified metric ("used in >1.5% of pages processed by [tool]", etc).
If it's just not practical, then we're opposed to using the full globals.browser list. We'd rather use no names to hard-coding any names, but if it appears necessary to use a subset of globals.browser and there doesn't seem to be a good reliable way to generate that subset, we would cut our losses and hard-code it.
Important reminder that globals.browser is not a superset of globals.builtin, which we strongly believe should be included in full without any vibe-based conditions. Except that "we should include all of it" is vibe-based anyway LOL. ECMAScript receives new features only once a year and generally expects new APIs to be developed over a long period if time. The baseline is that most of it is functionally helpful for most JavaScript developers, regardless the product discipline (they're lower-level / more basic APIs, you know, compared to web APIs). We think it'd be nice for sb-edit to stay on top of new interfaces, and we don't think its comparatively minimal list of names would get in the way of sprites that users want to create (or rather port from existing JavaScript projects).
Maybe there would be a case in the Leopard editor to warn users that the sprite name (or global variable) that they have created overrides the same name as a "popular" JavaScript global? sb-edit can only affect a Leopard project at the time of its generation (and through the generated code's practical consequences), so it doesn't address e.g. a user deciding to create a sprite named Object themselves down the line, unaware that Object is a useful global to have available and certainly not replace with some other value (even if it's just in your own code).


Can't load Azure schema

I'm attempting to generate an object model for the Azure resource manager schema at https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json# and running into an exception with version 9.10.16.
Write the following:
var schema = await NJsonSchema.JsonSchema4.FromUrlAsync(
                @"https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#");

Two InvalidOperationExceptions are thrown:
System.InvalidOperationException: 'Could not resolve the JSON path 'https://schema.management.azure.com/schemas/2015-08-19/Microsoft.Search.json#/resourceDefinitions/searchServices' with the full JSON path 'https://schema.management.azure.com/schemas/2015-08-19/Microsoft.Search.json#/resourceDefinitions/searchServices'.'

System.InvalidOperationException: 'Could not resolve the JSON path 'https://schema.management.azure.com/schemas/2015-08-19/Microsoft.Search.json#/resourceDefinitions/searchServices' with the full JSON path 'https://schema.management.azure.com/schemas/2015-08-19/Microsoft.Search.json#/resourceDefinitions/searchServices'.'

At
   at NJsonSchema.JsonReferenceResolver.<ResolveUrlReferenceWithAlreadyResolvedCheckAsync>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NJsonSchema.JsonReferenceResolver.<ResolveReferenceAsync>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NJsonSchema.JsonReferenceResolver.<ResolveReferenceAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NJsonSchema.JsonSchemaReferenceUtilities.JsonReferenceUpdater.<VisitJsonReferenceAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NJsonSchema.Visitors.JsonReferenceVisitorBase.<VisitAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NJsonSchema.Visitors.JsonReferenceVisitorBase.<VisitAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NJsonSchema.Visitors.JsonReferenceVisitorBase.<VisitAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NJsonSchema.Visitors.JsonReferenceVisitorBase.<VisitAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NJsonSchema.Visitors.JsonReferenceVisitorBase.<VisitAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NJsonSchema.Visitors.JsonReferenceVisitorBase.<VisitAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NJsonSchema.Visitors.JsonReferenceVisitorBase.<VisitAsync>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NJsonSchema.JsonSchemaReferenceUtilities.JsonReferenceUpdater.<VisitAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NJsonSchema.JsonSchemaReferenceUtilities.<UpdateSchemaReferencesAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NJsonSchema.JsonSchema4.<FromJsonAsync>d__29.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NJsonSchema.JsonSchema4.<FromUrlAsync>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NJsonSchema.JsonSchema4.<FromUrlAsync>d__25.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at ConsoleApp56.Program.<Do>d__1.MoveNext() in c:\users\rchande\Source\Repos\ConsoleApp56\ConsoleApp56\Program.cs:line 21
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at ConsoleApp56.Program.<Main>d__0.MoveNext() in c:\users\rchande\Source\Repos\ConsoleApp56\ConsoleApp56\Program.cs:line 15
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at ConsoleApp56.Program.<Main>(String[] args)

Just tested this, it seems the whole referenced document handling has to be reworked to support this..

Hello, can you please provide some indication of the priority of this bug and if there is any attempt to fix it in the foreseeable future?

Hello - I believe i'm also encountering this bug. The maintainers of the Powershell project are explicitly listing the inability of test-json to parse MS's own Azure schema due to this bug. This is rendering it impossible to validate MS azure schema with their own toolset. And news on progress with this issue would be hugely welcomed now the test-json cmdlet has been released with the -schema validation capabilities.

Fixed but the test takes around 40s to complete - many documents to load and parse etc. very good use case to optimize the loader ;-)


Halogen link is missing

I found http://madscript.com/halogen is missing.

This has already been fixed. So closing this out. Thanks


Added in submenus

Description
A few sentences describing the overall goals of the pull request's commits.
Please include

the type of fix - (e.g. bug fix, new feature, documentation)
some details on why this PR should be merged
the details of the testing you've done on it (both manual and automated)
which components are affected by this PR
links to issues that this PR addresses

Todos

[ ] Tests
[ ] Documentation

 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.Mike Stowe seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 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.Mike Stowe seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@robbrockbank @ozdanborne ready for review, and merge (7/20/2017 or later).
This PR:

Updates site navigation to match ProjectCalico.org site
Adds in breadcrumbs
Adds in GitHub Edit Link - see #781
Adds in documentation rating mechanism
Provides link to feedback form on ProjectCalico.org
Get More Help Links (Slack/ MVP)


no code sample

there is not any complete code sample.

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

ID: ee71441f-471a-89cd-0ef4-9b32b5dd85cf
Version Independent ID: 0096c365-2f4e-5d21-89a0-c4f10fcb0ed9
Content: Authorize with a specific scheme in ASP.NET Core
Content Source: aspnetcore/security/authorization/limitingidentitybyscheme.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@HaoK Are there examples of this in the aspnet/AuthSamples repo or elsewhere?

@guojianwei001  there should be sample code in https://github.com/aspnet/AuthSamples

We don't actually show that in auth samples, there's not much to show really:
MVC has a test website
https://github.com/aspnet/Mvc/blob/master/test/WebSites/SecurityWebSite/Controllers/AdministrationController.cs#L25


[Discussion|Onyx] Mixing Onyx.set and Onyx.merge usages leads to race condition

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Discussion
Decide how to deal with a race condition that happens when mixing Onyx.merge and Onyx.set
Problem
It's not obvious that we can introduce changes leading to Onyx.set and Onyx.merge being called close in time with the same key and create a race condition.
Details
During one of our PRs we discovered an issue where storage is getting overwritten with an older value due to using Onyx.set and Onyx.merge to update the same key: https://github.com/Expensify/App/pull/5726#discussion_r729851899
Debugging revealed that Onyx.merge and Onyx.set are called very close in time: https://github.com/Expensify/App/pull/5726#issuecomment-944405977
The problematic code did this

Invite button is pressed
One piece of code calls Onyx.merge to clear policy errors
At the same time another piece of code calls Onyx.set to update the same policy key
The merge from 1) completes last and overwrites local storage with older value

Even though merge and set are called at the same time. merge has to first read the full policy object in order to merge the changes to it. merge starts and gets the value before set has updated it, since it's promise based it would continue on the next tick. In the meantime set saves a new value in storage (step 2). On the next tick (step 3) the merge is applied with the stale data and another call to set overwrites the storage
A debug session that captured the problem
https://user-images.githubusercontent.com/12156624/137510311-327be7bc-d2c2-499c-8513-5d9fc0fc8964.mp4

Triggered auto assignment to @bondydaa (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@NicMendonca This is a discussion issue and does not need to work on or exported.

This is a challenging one to address because it feels like a potential problem with Onyx, but also feels like a potential problem with our conventions of syncing data in New Expensify.
Under normal conditions these race conditions should not be happening and the batching of merge() calls protects us from any really bad effects.
But it does seem likely that when we are using a combination of set() and merge() in the same tick then the outcome would be hard to predict. So maybe we can start by looking at where we made those decisions and why?
It should be more clear what sort of action to take if we audit the workarounds that we suspect cause race conditions.
Enforcing that merge() be preferred over set() could be a great solution. But it's hard to say without considering why we sometimes prefer to use set() over merge(). One reason I've observed is that we are trying to remove some values and "reset" the data by using set() instead of merging new data into stale data. "syncing" local data with an API response is another reason you'll see this happen.


Update config_template.json

I'm going to have to decline this pull request. This update focuses more on user preference as opposed to adding a feature to the global scope of the Bot.


Add more snapshot tests

Improve current and add additional snapshot tests

Integrate verify in github actions
Getting .received in output on GitHub Actions
Use a if: failure() condition to upload any .received. files if the build fails.
- name: Upload Test Results
  if: failure()
  uses: actions/upload-artifact@v4
  with:
    name: verify-test-results
    path: |
      **/*.received.*


Dispose tile textures

I've read through the code and haven't found any mention of deleting old tile textures. In Three.js textures need to be deleted explicitly, see Textures section here: https://threejs.org/docs/#manual/en/introduction/How-to-dispose-of-objects
In this PR I've added Texture.dispose() for color textures and heightmap textures (only for MapHeightNodeShader). I'm not sure whether this is the best way to implement this.

Ha, what an coincidence.
Having troubles which faster moving maps, where memory is eaten more and more up by geo-three to the point the browser crashes.
I started to look into the geo-three myself and came to something similar with disposing objects and tiles, but unfortunately I was unable to compile geo-three only getting this error at runtime, so I could not proceed.:
THREE.WebGLProgram: Shader Error 0 - VALIDATE_STATUS false

Program Info Log: Must have a compiled vertex shader attached:

Here is a memory snapshot during runtime, all this objects and arrays building more and more up, and never gets released, until the point of crash.

I think this are not only map textures, but also meshes and other three.js objects, that never gets disposed.
@tentone Would be great, if you find some time to help us with this issue and maybe we can get to new release together with fixes tackling cleanup issues.

@aldipower Just to clarify, are you talking about RAM or VRAM? In this PR I'm addressing a possible VRAM leak (textures from disposed tiles don't get removed from VRAM). But you've shown a heap snapshot, so I don't really understand what's this about. If you have a heap snapshot it shouldn't be hard for you to find the source of your memory leak.

@StrandedKitty Yes, my post does not address directly, but maybe partly, your PR I guess.
My post is about geo-three is filling up the RAM, when used in long or fast running scences.
The relation to your PR is 'cleaning up unused objects generally'.
My problem is, if I compile geo-three myself, I cannot run the lib, because I get this THREE.WebGLProgram: Shader Error 0 - VALIDATE_STATUS false error, which I do not get at the pre-compiled lib. So, I cannot test any code changes, I potentially can do. How did you develop on geo-three?

Thanks a lot!
Completly missed these. PR merged! Build seems to be failing but should be an easy fix!


System.TypeLoadException: 'Could not load type 'Microsoft.Toolkit.Uwp.Notifications.ToastNotificationManagerCompat' from assembly 'Microsoft.Toolkit.Uwp.Notifications

Using latest nuget in Avalonia raises:
manager = new WindowsNotificationManager(context);
System.TypeLoadException: 'Could not load type 'Microsoft.Toolkit.Uwp.Notifications.ToastNotificationManagerCompat' from assembly 'Microsoft.Toolkit.Uwp.Notifications, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=4aff67a105548ee2'.'

All nuget installed:

Using net6.0, when publishing with net6.0 win-x64 does the same result.

I had the same issue. Setting the TargetOS to 10.0.17763.0 fixed it for me (.NET8)
Solution based on this issue: https://github.com/pr8x/DesktopNotifications/issues/24

Hi,
I changed my project file like that:
`

WinExe
enable
true
app.manifest
true

net8.0

net8.0-windows10.0.17763.0

`
but I still get the error on Windows. Linux is working fine. Can someone assist?


Update Jetty to 9.3.11.v20160721

This PR supersedes #1608:

By updating to a newer version of Jetty
Fixing test case on windows due to window paths
Fixing test failure found in #1608 with new exception comparison. Admittedly, it seems like a worse exception message to test against (SSLException vs SSLHandshakeException)

Changes Unknown when pulling a321a877277f36f12cf82c099ab7407102ce47c0 on nickbabcock:jetty_9311 into ** on dropwizard:master**.

LGTM. 👍
Could you please add this to the release notes, too?

Just pushed a commit to this PR that starts the 1.1.0 release notes.

Changes Unknown when pulling 1687ada4ca385bb42a65bc92d4fdb9b9f3ae9567 on nickbabcock:jetty_9311 into ** on dropwizard:master**.

Once the release notes are in, I can go back and update it for the PR's I merged earlier.

Thanks!


Option to base-64 embed data buffer in GLTF instead of using GLB container

This wil produce a GLTF file that is pure ascii text instead of embedding it into a GLB container.
This will increase file size by around 33%, but should work on applications that do not support GLB containers

Being able to split with a option on what level like discussed in #48 will solve this issue ?

GLTF files are bigger than GLB files since the buffer data is encoded as base64 instead of stored in raw form, so if just the file size is the issue, this won't help. But when writing as GLTF, the buffers are not packed into one single buffer but as a lot of small buffers, so that might help in some cases where a single large buffer is an issue.

Implemented in #52.