Ubuntu 18.04 update errors

in build 1709 I have Ubuntu 18.04 installed from core/docker tar then added packages till normal usable install like www.tinyurl.com/donofrioworkdesk except I am using lxrunoffline w/18.04 and I'm getting a few errors when I do apt-get upgrade: https://github.com/DDoSolitary/LxRunOffline/issues/21#issuecomment-366490465 I'm getting (https://1drv.ms/u/s!AsBlZbBf72iNoL80WYzed14twrwo0Q #ignoreonedrivelogin) "cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file" and "Failed to replace specifiers: /tmp/systemd-private" please advise.

I'm stuck here as packages will not complete installing, help.....

How can I resolve this:
same exact error when I go (do-release-update) from 16.04 to 18.04 I get these "Failed to replace specifiers: /tmp/systemd-private-%b-*" any thoughts on why "Executing: /lib/systemd/systemd-sysv-install enable ondemand" cannot deal with these files if they exist already?

I'm running Bionic in WSL. Never seen that problem. The files that you've mentioned are same. Try to reinstall Bionic.

How did you get bionic on WSL?  I had to use core file from https://partner-images.canonical.com/core/bionic/current/ubuntu-bionic-core-cloudimg-amd64-root.tar.gz because I do not have the store on corp 1709 build.

Download the SquashFS file from https://cloud-images.ubuntu.com/bionic/current/ and convert .squashfs to tar.gz.

@Biswa96 is this looking correct?
https://apaste.info/pFAD I guess I need to rename tar to  install.tar.gz because that is all that ubuntu.exe knows how to see?

See my repository named WSLInstall. You get the command in a .MD file.

where is this repo located?

I was  able to do the squish to tar and 7zip out the ubuntu.exe from the appx and renaming the file to install.tar.gz and it worked perfectly (we so far now on to adding my needed 1k packages) thank you for your help so far.

If your problem solved. You may close this issue.

still seeing got lots of packages to install then well see how it goes when it tries to update systemd

I recently hit this issue too, ended up backing up all my SSH keys and other personal files, then did a clean re-installation. I will stay with 16.04.

so much better once you do the squish to tar when you reinstall the wsl instance.  I have 18.04 working on my left desktop now I used the squash file from https://github.com/Microsoft/WSL/issues/2618 and the ubuntu.exe 7ziped from https://github.com/Microsoft/WSL/issues/2618 (grabbed the ubuntu.exe only and the new renamed install.tar.gz file and it worked like it should!! #sohappy!)

anyone got around add-apt-repository (or rather the underlying apt-key) failing in 18.04 with IPC connect call failed due to a non-running dirmngr?
root@devbox:~# add-apt-repository -y ppa:ondrej/apache2
gpg: keybox '/tmp/tmp1dxzjlmo/pubring.gpg' created
gpg: connecting dirmngr at '/tmp/tmp1dxzjlmo/S.dirmngr' failed: IPC connect call failed
gpg: keyserver receive failed: No dirmngr
Failed to add key.
root@devbox:~# apt-key adv --receive-key 0x4F4EA0AAE5267A6C
Executing: /tmp/apt-key-gpghome.26gIc3RU5y/gpg.1.sh --receive-key 0x4F4EA0AAE5267A6C
gpg: connecting dirmngr at '/tmp/apt-key-gpghome.26gIc3RU5y/S.dirmngr' failed: IPC connect call failed
gpg: keyserver receive failed: No dirmngr
root@devbox:~#

manually adding the key works, but that feels dirty:
root@devbox:~# curl -s "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x4F4EA0AAE5267A6C" | sudo apt-key add -
OK
root@devbox:~#```

I need to try that manual method because I need xfwm4.13 for the opengl support and right now I just get the same dirmngr ipc issue, I've tried to start it manually and no difference....how did you get the receive-key

how did you get the "receive-key?"

how did you get the "receive-key?"

IPC connect call failed due to a non-running dirmngr?

Possibly. The lxrunoffline issue tracker is here. If you have a repro for the dirmngr IPC fail under a supported platform (note: this is entirely doable) please open a new issue following CONTRIBUTING.md. Whether doing so will be constructive for the effort or not I can't say; there is a higher than zero chance it is a dupe.

I need to try that manual method because I need xfwm4.13 for the opengl support and right now I just get the same dirmngr ipc issue, I've tried to start it manually and no difference....how did you get the receive-key - please email me<EMAIL_ADDRESS>how you got the key for that repo?

@heldchen  tried gpg --recv-keys key-id but nope....@therealkenc (I'm not using the lxoffline method)

@lewisdonofrio just let the add-apt-repository run and fail, then execute apt-get update, look for the failing key's id, use that key id with the curl workaround to manually add the gpg key. afterwards, apt-get update will run.
@therealkenc seems like it's a bionic issue - have not had this problem in 17.10 from a manually converted squashfs. possibly a changed gnupg/dirmngr default... will try a gnupg update to 18.04's version later on

@heldchen bingo, that apt-update to get key worked...

I hit the gnupg/dirmngr error with Debian Testing (Codename: Buster) as well. It's odd that on Stretch, I can add whatever repos I want and the keys are fine and the repos are added and when shifted to Buster the keys are retained along with the repos but adding a repo on Buster gets this error.

it's due to the updated gnupg and friend's packages. you can replicate it on stretch/ubuntu 16:04 by just upgrading those packages to the next versions.

life with xfce 4.12 and xfwm-4.13 (with now working experimental repo) is going good, nice workaround to this add-repo issue.

@heldchen Since you've already done to work of repro gnupg/dirmngr error, can you post an issue for it? Not sure if it'll be a WSL specific or if the package maintainer needs to fix something.

@DarthSpock the last 18.04 issue I posted on a maintainers github got closed with the comment 18.04 is not yet stable... so it seems unlike with Debian, in Ubuntu a beta release is not supposed to be usable...  ¯_(ツ)_/¯
I've since switched to the Debian distro.

@heldchen 18.04 isn't stable yet but they are very close to releasing the LTS version later this month. So it will become more and more stable but yes Debian Testing vs Ubuntu betas do have moderate different. Debian is supposed to be one of the most stable distros available. Kali is based on Debian Testing and is quite stable after the work the Kali team does so it would make sense that Debian Testing itself would be more usable than an Ubuntu beta, especially since Ubuntu is based on Debian as well. As far as I understand it, majority of packages made for Debian-based distros release in Debian first, which puts the other distros a little behind, which means they will be more buggy when using a non-stable version of say Ubuntu in this case.
Side note: Ironically even the Debian Stable: Stretch is ahead of 16.04 Ubuntu. Biggest teller is the version of glibc being used and you know how many dependencies there are on that one thing, which of course removes the issue people were experiencing since it's a newer version than the bug exists in 2.23 that wasn't patched by Ubuntu LTS for some reason.

@heldchen do you have the github link where they say that, because 17.04 is out of support they say " Ubuntu 17.04 (Zesty Zapus) was the 26th release of Ubuntu. Support ended on January 13th, 2018. See !eol and https://lists.ubuntu.com/archives/ubuntu-announce/2018-January/000228.html" and 18.04 will be released in two weeks'ish on April 27th so yah I'm saying with stable goodness of ubuntu 18.04 the add-repo workaroudd works fine for me for now...

18.04 isn't stable yet but they are very close to releasing the LTS version later this month.

I know. that's why I was surprised to learn that an issue reported with some package files a few days ago was just closed. as we're using Debian in production anyway, I felt that this was the right time to also switch my local WSL dev env to Debian.

Yes use what you need, I just needed basic linux/gui/bash/remmina setup others will need moar.  Outline your debian adventures - we're all interested.

For people having the "Failed to replace specifiers: /tmp/systemd-private-%b-*" issue. It is a bug in systemd. This is being fixed by the Ubuntu team (see https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1758865).
They have a working package (234-2ubuntu12.4) in "artful-proposed", so it is not published yet. But it is possible to install this package and fix the issue.
For the ones who will go through this, they will likely then encounter an error during bash upgrade. The pre install script crashes. The fix is already available in glibc but you need to force glibc to update before bash: sudo apt install libc6.

I do not know if you can safely mix artful and bionic source's together?
Here are my repo's http://paste.ubuntu.com/p/ZzTrq3DRWF/

How did you get that message I have yet to see it my console when I startxfce4 https://paste.ubuntu.com/p/SVBKczdbdh/

@lewisdonofrio
No, you should not mix artful and bionic repos. But the systemd error happens also when people try to upgrade to 17.10.
For 17.10 there is a fix in the artful-proposed repo. For 18.04 I do not know if the fix is already available or if it is in the bionic-proposed repo or not yet available at all.
I do not understand what you are talking about with xfce. The errors are happening when you run apt from the Ubuntu WSL console. You do not need to start any x server or session.

Yah I don't mix just seen your post and wondered because this post was only about 18.04/bionic.

these messages were from the bash.exe console messages when I start xfce4 (I live in xfce4/ubuntu 18.04 at work with my daily driver - basically use w10 as a 15gb bootloader lol)


Update paths for ArcGIS.xcframework

Update paths for ArcGIS.xcframework as the next release of the ArcGIS SDK now builds a binary framework.

This also includes a change to the ArcGIS Toolkit submodule; the new commit incorporates these same changes in the Toolkit.

@mhdostal i'm not sure v.next-1.3 will be ready come time for U10 cert. Can you cut a v.next.1.2.3 and base these changes to that branch?

Replaced by v.next.1.2.3 PR


Better Rolls for 5e incompatability

Hi just discovered this addon is incompatible with https://github.com/RedReign/FoundryVTT-BetterRolls5e
upon installing hotbar-uses for the first time.

thank you Joe! appreciate all the time and skill you put into these foundryvtt add-ons :)


How to effectively test if gdrcopy is enabled using Real world ML workload ?

I have successfully installed gdrcopy on my host and completed its tests. Afterwards, I launched a container running my language model application, with a focus on profiling the loading of the model from the local disk. I am looking for methods to confirm whether gdrcopy is active when my application is running. Since I am new to this, I would appreciate any guidance on how to verify the operation of gdrcopy in this context.

Hi @pandyamarut,
Based on your question, my guess is that your application does not use GDRCopy directly. Probably you want to confirm that a library (e.g., UCX, NCCL) is properly utilizing GDRCopy? One way to do so is to export the environment variables below and rerun your application. If GDRCopy is used, you should see some output lines from GDRCopy.
export GDRCOPY_ENABLE_LOGGING=1
export GDRCOPY_LOG_LEVEL=1

@pandyamarut where you able to verify it?


Add isGNU and isClang attributes to cc-wrapper

These are meant to replace the current idiom of using stdenv.cc.cc.isGNU or false to check which compiler we're currently building with.

LGTM

Ah, wait, the use of wrapCC in llvm-3.{5,6}/default.nix will break, no?

@shlevy wrapCC checks the given baseCC to determine whether it's gcc or clang. It doesn't require an extra argument (https://github.com/gridaphobe/nixpkgs/blob/cc-wrapper-isgnu-isclang/pkgs/top-level/all-packages.nix#L4483-L4484)

Ah, so we need isClang or isGnu on the unwrapped compilers too?

Ah I understand your concern now, the unwrapped compilers have had those attributes for a while now, that's how the original tests worked :)
https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/compilers/llvm/3.6/clang/default.nix#L43-L47
The problem was that clang didn't have an isGNU attr (and vice versa).

:+1: Fantastic much wanted feature.


NVSHAS-9525 resolve golinter issue

Based on our discussion, we need to address the error with consideration for context. I am closing this PR as it may have significant differences.


[Docs] Update introduction and fix issues

Modification

add an introduction to docs.
fix links and typos.
update docs apis config.

Codecov Report

Merging #10 (b2df6fe) into main (486c8c2) will increase coverage by 0.07%.
The diff coverage is n/a.

:exclamation: Current head b2df6fe differs from pull request most recent head 6a0f379. Consider uploading reports for the commit 6a0f379 to get more accurate results

@@            Coverage Diff             @@
##             main      #10      +/-   ##
==========================================
+ Coverage   71.56%   71.63%   +0.07%
==========================================
  Files         116      116
  Lines        5546     5560      +14
  Branches     1055     1055
==========================================
+ Hits         3969     3983      +14
  Misses       1301     1301
  Partials      276      276

Flag
Coverage Δ

unittests
71.63% <ø> (+0.07%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mmfewshot/utils/infinite_sampler.py
76.59% <0.00%> (-0.65%)
:arrow_down:

mmfewshot/classification/models/heads/base_head.py
100.00% <0.00%> (ø)

mmfewshot/detection/datasets/dataset_wrappers.py
80.40% <0.00%> (+0.08%)
:arrow_up:

...ewshot/classification/datasets/dataset_wrappers.py
86.51% <0.00%> (+0.15%)
:arrow_up:

...fewshot/detection/datasets/pipelines/transforms.py
87.33% <0.00%> (+0.16%)
:arrow_up:

mmfewshot/classification/datasets/base.py
48.31% <0.00%> (+0.58%)
:arrow_up:

...tection/models/detectors/query_support_detector.py
30.10% <0.00%> (+0.75%)
:arrow_up:

mmfewshot/detection/models/detectors/meta_rcnn.py
32.65% <0.00%> (+1.40%)
:arrow_up:

...mfewshot/classification/models/classifiers/base.py
73.80% <0.00%> (+1.65%)
:arrow_up:

Continue to review full report at Codecov.

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


ReferenceError: navigator is not defined

When rendering on the server side.
It's because of the way you defined your module: you assume it's only require()d on the client side.

When rendering on the server side.

This project is only for the browser. It's specifically a wrapper around the W3C standard WebSocket class. If you want a node.js package for a client websocket, check out ws

Ok, then for those coming from Google: the workaround is global.navigator = {}

Are you trying to use webpack or browserify with this?

No, I'm just running my server-side code which happens to require() your package and this seems to trigger that function (something, navigator) is evaluated.
I.e. I'm not even using your library on the server, it just happens to be require()d among the others (this is a React rendering librar)


Missing pnpm dependencies when building Quarkus starter on Jenkins using Gradle

I created an app based on base-starter-flow-quarkus (very few changes, I only added a logo at this time).
I'm building on Jenkins using Gradle, with the vaadinBuildFrontend target.
I get the following error:
13:00:07  > Task :compileJava
13:00:17  > Task :vaadinPrepareFrontend
13:00:17  > Task :processResources
13:00:17  > Task :classes
13:00:23
13:00:23  > Task :vaadinBuildFrontend FAILED
13:00:23  Command `/root/.vaadin/node/node /root/.vaadin/node/node_modules/npm/bin/npx-cli.js --yes --quiet<EMAIL_ADDRESS>--shamefully-hoist=true install` failed:
13:00:23
13:00:23  >>> Dependency ERROR. Check that all required dependencies are deployed in pnpm repositories.
13:00:23
13:00:23  FAILURE: Build failed with an exception.
13:00:23
13:00:23  * What went wrong:
13:00:23  Execution failed for task ':vaadinBuildFrontend'.
13:00:23  > com.vaadin.flow.server.ExecutionFailedException: Pnpm install has exited with non zero status. Some dependencies are not installed. Check pnpm command output

The build runs on a Linux agent based on a amazoncorretto:17.0.0 (Java 17) with Node 14.17.1
The build was successful with the build target but this cannot be deployed to the cloud since it would be running in dev mode.

Hi, which Vaadin version are you using please? I think that at some point Vaadin reverted the default package manager from pnpm to npm, so maybe it's better to use npm. Could you please try running ./gradlew vaadinDance and switch to npm, then try again, whether that would help? Alternatively, could you run ./gradlew --info --stacktrace to obtain more info?

My project is almost identical to the project base at https://github.com/vaadin/base-starter-flow-quarkus/tree/gradle so the Vaadin version is 22.0.2. It also uses vaadinQuarkusVersion=1.0.0.
I tried ./gradlew vaadinDance but this target was not recognized.
Here is the output of ./gradlew --info --stacktrace (I removed the massive dependency download and Java compilation) :
11:01:40  file or directory '/home/jenkins/agent/workspace/fika-admin-tool_master/build/classes/java/quarkus-generated-sources/grpc', not found
11:01:40  file or directory '/home/jenkins/agent/workspace/fika-admin-tool_master/build/classes/java/quarkus-generated-sources/avdl', not found
11:01:40  file or directory '/home/jenkins/agent/workspace/fika-admin-tool_master/build/classes/java/quarkus-generated-sources/avpr', not found
11:01:40  file or directory '/home/jenkins/agent/workspace/fika-admin-tool_master/build/classes/java/quarkus-generated-sources/avsc', not found
11:01:40  Compiling with JDK Java compiler API.
11:01:40  Class dependency analysis for incremental compilation took 0.038 secs.
11:02:19  Created classpath snapshot for incremental compilation in 36.463 secs.
11:02:19  :compileJava (Thread[Daemon worker,5,main]) completed. Took 37.71 secs.
11:02:19  :classes (Thread[Execution worker for ':',5,main]) started.
11:02:19
11:02:19  > Task :classes
11:02:19  Skipping task ':classes' as it has no actions.
11:02:19  :classes (Thread[Execution worker for ':',5,main]) completed. Took 0.0 secs.
11:02:19  :vaadinBuildFrontend (Thread[Execution worker for ':',5,main]) started.
11:02:19
11:02:19  > Task :vaadinBuildFrontend
11:02:19  Caching disabled for task ':vaadinBuildFrontend' because:
11:02:19    Build cache is disabled
11:02:19  Task ':vaadinBuildFrontend' is not up-to-date because:
11:02:19    Task has not declared any outputs despite executing actions.
11:02:19  Running the vaadinBuildFrontend task with effective configuration VaadinFlowPluginExtension(productionMode=false, webpackOutputDirectory=/home/jenkins/agent/workspace/fika-admin-tool_master/build/resources/main/META-INF/VAADIN/webapp, npmFolder=/home/jenkins/agent/workspace/fika-admin-tool_master, webpackTemplate='webpack.config.js', webpackGeneratedTemplate='webpack.generated.js', generatedFolder=/home/jenkins/agent/workspace/fika-admin-tool_master/build/frontend, frontendDirectory=/home/jenkins/agent/workspace/fika-admin-tool_master/frontend, generateBundle=true, runNpmInstall=true, generateEmbeddableWebComponents=true, frontendResourcesDirectory=/home/jenkins/agent/workspace/fika-admin-tool_master/src/main/resources/META-INF/resources/frontend, optimizeBundle=true, pnpmEnable=true, useGlobalPnpm=false, requireHomeNodeExec=false, useDeprecatedV14Bootstrapping=false, eagerServerLoad=false, applicationProperties=/home/jenkins/agent/workspace/fika-admin-tool_master/src/main/resources/application.properties, openApiJsonFile=/home/jenkins/agent/workspace/fika-admin-tool_master/build/generated-resources/openapi.json, javaSourceFolder=/home/jenkins/agent/workspace/fika-admin-tool_master/src/main/java, javaResourceFolder=/home/jenkins/agent/workspace/fika-admin-tool_master/src/main/resources, generatedTsFolder=/home/jenkins/agent/workspace/fika-admin-tool_master/frontend/generated, nodeVersion=v16.13.0, nodeDownloadRoot=https://nodejs.org/dist/, nodeAutoUpdate=falseresourceOutputDirectory=/home/jenkins/agent/workspace/fika-admin-tool_master/build/vaadin-generated)
11:02:19  Reflections took 2090 ms to scan 210 urls, producing 5956 keys and 31627 values
11:02:19  Passing this classpath to NodeTasks.Builder: [vaadin-core-jandex-22.0.2.jar, vaadin-core-22.0.2.jar, vaadin-quarkus-1.0.0.jar, quarkus-undertow-websockets-2.5.4.Final.jar, slf4j-simple-1.7.32.jar, fusion-endpoint-9.0.2.jar, vaadin-dev-server-9.0.2.jar, flow-lit-template-9.0.2.jar, flow-polymer-template-9.0.2.jar, flow-html-components-9.0.2.jar, flow-data-9.0.2.jar, flow-dnd-9.0.2.jar, flow-server-9.0.2.jar, flow-push-9.0.2.jar, flow-client-9.0.2.jar, vaadin-lumo-theme-22.0.2.jar, vaadin-material-theme-22.0.2.jar, vaadin-accordion-flow-22.0.2.jar, vaadin-avatar-flow-22.0.2.jar, vaadin-app-layout-flow-22.0.2.jar, vaadin-button-flow-22.0.2.jar, vaadin-checkbox-flow-22.0.2.jar, vaadin-combo-box-flow-22.0.2.jar, vaadin-date-time-picker-flow-22.0.2.jar, vaadin-date-picker-flow-22.0.2.jar, vaadin-time-picker-flow-22.0.2.jar, vaadin-select-flow-22.0.2.jar, vaadin-dialog-flow-22.0.2.jar, vaadin-details-flow-22.0.2.jar, vaadin-form-layout-flow-22.0.2.jar, vaadin-grid-flow-22.0.2.jar, vaadin-icons-flow-22.0.2.jar, vaadin-iron-list-flow-22.0.2.jar, vaadin-virtual-list-flow-22.0.2.jar, vaadin-list-box-flow-22.0.2.jar, vaadin-messages-flow-22.0.2.jar, vaadin-notification-flow-22.0.2.jar, vaadin-ordered-layout-flow-22.0.2.jar, vaadin-progress-bar-flow-22.0.2.jar, vaadin-radio-button-flow-22.0.2.jar, vaadin-menu-bar-flow-22.0.2.jar, vaadin-context-menu-flow-22.0.2.jar, vaadin-renderer-flow-22.0.2.jar, vaadin-split-layout-flow-22.0.2.jar, vaadin-tabs-flow-22.0.2.jar, vaadin-text-field-flow-22.0.2.jar, vaadin-upload-flow-22.0.2.jar, vaadin-login-flow-22.0.2.jar, vaadin-custom-field-flow-22.0.2.jar, ph-css-6.3.4.jar, quarkus-undertow-2.5.4.Final.jar, quarkus-websockets-2.5.4.Final.jar, quarkus-vertx-http-2.5.4.Final.jar, quarkus-websockets-client-2.5.4.Final.jar, quarkus-vertx-2.5.4.Final.jar, quarkus-mutiny-2.5.4.Final.jar, quarkus-smallrye-context-propagation-2.5.4.Final.jar, quarkus-netty-2.5.4.Final.jar, quarkus-arc-2.5.4.Final.jar, quarkus-security-runtime-spi-2.5.4.Final.jar, quarkus-vertx-http-dev-console-runtime-spi-2.5.4.Final.jar, quarkus-core-2.5.4.Final.jar, spring-data-commons-2.5.6.jar, swagger-codegen-generators-1.0.20.jar, swagger-codegen-3.0.20.jar, swagger-codegen-2.4.14.jar, swagger-parser-2.0.20.jar, swagger-parser-v2-converter-2.0.20.jar, swagger-compat-spec-parser-1.0.51.jar, swagger-parser-1.0.51.jar, slf4j-ext-1.7.32.jar, atmosphere-runtime-2.4.30.slf4jvaadin1.jar, ph-commons-10.1.2.jar, handlebars-4.1.2.jar, swagger-core-1.6.1.jar, swagger-models-1.6.1.jar, swagger-parser-v3-2.0.20.jar, swagger-core-2.1.2.jar, slf4j-api-1.7.32.jar, jackson-dataformat-yaml-2.12.6.jar, quarkus-http-vertx-backend-4.1.4.jar, quarkus-http-websocket-vertx-4.1.4.jar, smallrye-mutiny-vertx-web-2.15.1.jar, vertx-web-4.2.2.jar, smallrye-mutiny-vertx-web-common-2.15.1.jar, smallrye-mutiny-vertx-auth-common-2.15.1.jar, smallrye-mutiny-vertx-bridge-common-2.15.1.jar, smallrye-mutiny-vertx-core-2.15.1.jar, vertx-web-common-4.2.2.jar, vertx-auth-common-4.2.2.jar, vertx-bridge-common-4.2.2.jar, vertx-mutiny-generator-2.15.1.jar, smallrye-mutiny-vertx-runtime-2.15.1.jar, vertx-core-4.2.2.jar, vertx-codegen-4.2.2.jar, jackson-core-2.12.6.jar, jackson-datatype-jsr310-2.12.6.jar, json-patch-1.6.jar, json-schema-validator-2.2.8.jar, json-schema-core-1.2.8.jar, jackson-coreutils-1.8.jar, jackson-databind-2.12.6.jar, swagger-parser-core-2.0.20.jar, swagger-models-2.1.2.jar, jackson-annotations-2.12.6.jar, javaparser-symbol-solver-core-3.23.1.jar, uri-template-0.9.jar, guava-30.1.1-jre.jar, error_prone_annotations-2.2.0.jar, httpclient-4.5.13.jar, commons-codec-1.15.jar, commons-io-2.11.0.jar, quarkus-http-servlet-4.1.4.jar, quarkus-http-core-4.1.4.jar, quarkus-http-http-core-4.1.4.jar, quarkus-http-websocket-core-4.1.4.jar, netty-handler-proxy-4.1.72.Final.jar, netty-codec-http2-4.1.72.Final.jar, netty-codec-http-4.1.72.Final.jar, netty-codec-haproxy-4.1.72.Final.jar, netty-resolver-dns-4.1.72.Final.jar, netty-handler-4.1.72.Final.jar, netty-codec-socks-4.1.72.Final.jar, netty-codec-dns-4.1.72.Final.jar, netty-codec-4.1.72.Final.jar, netty-transport-4.1.72.Final.jar, netty-buffer-4.1.72.Final.jar, netty-resolver-4.1.72.Final.jar, netty-common-4.1.72.Final.jar, netty-tcnative-classes-2.0.46.Final.jar, arc-2.5.4.Final.jar, quarkus-security-1.1.4.Final.jar, quarkus-bootstrap-runner-2.5.4.Final.jar, quarkus-development-mode-spi-2.5.4.Final.jar, quarkus-ide-launcher-2.5.4.Final.jar, mutiny-smallrye-context-propagation-1.1.2.jar, mutiny-1.1.2.jar, smallrye-config-2.7.0.jar, smallrye-config-core-2.7.0.jar, smallrye-common-annotation-1.8.0.jar, smallrye-config-common-2.7.0.jar, smallrye-common-classloader-1.8.0.jar, smallrye-common-expression-1.8.0.jar, smallrye-common-function-1.8.0.jar, smallrye-common-constraint-1.8.0.jar, smallrye-common-io-1.8.0.jar, smallrye-context-propagation-1.2.2.jar, smallrye-context-propagation-api-1.2.2.jar, smallrye-fault-tolerance-vertx-5.2.1.jar, jakarta.xml.bind-api-2.3.3.jar, jakarta.activation-api-1.2.1.jar, jakarta.enterprise.cdi-api-2.0.2.jar, jakarta.interceptor-api-1.2.5.jar, jakarta.annotation-api-1.3.5.jar, jakarta.inject-api-1.0.jar, jakarta.servlet-api-4.0.3.jar, jakarta.transaction-api-1.3.3.jar, jakarta.validation-api-2.0.2.jar, jakarta.websocket-api-1.1.2.jar, commons-compress-1.21.jar, commons-lang3-3.12.0.jar, httpcore-4.4.14.jar, checker-qual-2.5.2.jar, microprofile-config-api-2.0.jar, microprofile-context-propagation-api-1.2.jar, graal-sdk-21.3.0.jar, jboss-logging-annotations-2.2.1.Final.jar, jboss-threads-3.4.2.Final.jar, jboss-logging-3.4.2.Final.jar, jboss-logmanager-embedded-1.0.9.jar, slf4j-jboss-logmanager-1.1.0.Final.jar, jsoup-1.14.2.jar, reactive-streams-1.0.3.jar, wildfly-common-1.5.4.Final-format-001.jar, snakeyaml-1.29.jar, javax.annotation-api-1.3.2.jar, gwt-elemental-2.8.2.vaadin2.jar, commons-fileupload-1.3.3.jar, byte-buddy-1.12.1.jar, gentyref-1.2.0.vaadin1.jar, validation-api-2.0.1.Final.jar, vaadin__vaadin-mobile-drag-drop-1.0.1.jar, mobile-drag-drop-2.3.0-rc.2.jar, commons-logging-1.2.jar, jakarta.el-api-3.0.3.jar, spring-beans-5.3.11.jar, spring-core-5.3.11.jar, javaparser-core-3.23.1.jar, javassist-3.28.0-GA.jar, jmustache-1.12.jar, commons-cli-1.2.jar, commonmark-0.9.0.jar, msg-simple-1.1.jar, btf-1.2.jar, jsr305-3.0.2.jar, spring-jcl-5.3.11.jar, failureaccess-1.0.1.jar, listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar, j2objc-annotations-1.3.jar, jboss-websocket-api_1.1_spec-1.1.4.Final.jar, smallrye-context-propagation-storage-1.2.2.jar, swagger-annotations-1.6.1.jar, swagger-annotations-2.1.2.jar, joda-time-2.9.7.jar, libphonenumber-8.0.0.jar, jopt-simple-5.0.3.jar, rhino-1.7R4.jar, mailapi-1.4.3.jar, activation-1.1.jar, /home/jenkins/agent/workspace/fika-admin-tool_master/build/classes/java/main]
11:02:19  Scanning classes to find frontend configurations and dependencies...
11:02:21  Visited 1938 classes. Took 3083 ms.
11:02:21  Visited 104 classes. Took 64 ms.
11:02:21  Running `pnpm install` to resolve and optionally download frontend dependencies. This may take a moment, please stand by...
11:02:22  using '/root/.vaadin/node/node /root/.vaadin/node/node_modules/npm/bin/npx-cli.js --yes --quiet<EMAIL_ADDRESS>for frontend package installation
11:02:23  Command `/root/.vaadin/node/node /root/.vaadin/node/node_modules/npm/bin/npx-cli.js --yes --quiet<EMAIL_ADDRESS>--shamefully-hoist=true install` failed:
11:02:23
11:02:23  >>> Dependency ERROR. Check that all required dependencies are deployed in pnpm repositories.
11:02:23
11:02:23  > Task :vaadinBuildFrontend FAILED
11:02:23  :vaadinBuildFrontend (Thread[Execution worker for ':',5,main]) completed. Took 7.32 secs.
11:02:23
11:02:23  FAILURE: Build failed with an exception.

Even though the build machine provides nodes+npm, the Gradle plugin appears to install its own copes in the .vaadin directory.
I did a successful build on my Windows machine so the issue appears to be specific to our build agent (a Docker agent running on AWS EKS).

This is not new: https://vaadin.com/forum/thread/18159870/jenkins-build-fails-with-vaadin-gradle-plugin-due-to-missing-dependency

Can you please try to run the command /root/.vaadin/node/node /root/.vaadin/node/node_modules/npm/bin/npx-cli.js --yes --quiet<EMAIL_ADDRESS>--shamefully-hoist=true install manually in your environment? Looks like Gradle plugin doesn't properly read stderr of the process and hides it (which is definitely a bug and should be filed at https://github.com/vaadin/flow/issues

sh-4.2# /root/.vaadin/node/node /root/.vaadin/node/node_modules/npm/bin/npx-cli.js --yes --quiet<EMAIL_ADDRESS>--shamefully-hoist=true install
Already up-to-date

   ╭──────────────────────────────────────────────────────────────────╮
   │                                                                  │
   │                Update available! 6.11.0 → 6.32.3.                │
   │   Changelog: https://github.com/pnpm/pnpm/releases/tag/v6.32.3   │
   │                 Run pnpm add -g pnpm to update.                  │
   │                                                                  │
   │      Follow @pnpmjs for updates: https://twitter.com/pnpmjs      │
   │                                                                  │
   ╰──────────────────────────────────────────────────────────────────╯

I also tried to set HOME as a workaround suggested in https://github.com/vaadin/vaadin-gradle-plugin/issues/54 but it didn't work

The command must be run in the folder of The vaadin project (or where the package.json file is)

@mvysny sorry, here it is:
14:07:18  [Pipeline] sh
14:07:18  + /root/.vaadin/node/node /root/.vaadin/node/node_modules/npm/bin/npx-cli.js --yes --quiet<EMAIL_ADDRESS>--shamefully-hoist=true install
14:07:19  sh: pnpm: command not found

I installed pnpm on the docker agent and set pnpm.global to true, but the build fails to detect the installation:
10:37:52    ======================================================================================================
10:37:52    Vaadin application is configured to use globally installed pnpm ('pnpm.global=true'), but no pnpm tool has been found on your system.
10:37:52    Please install pnpm tool following the instruction given here https://pnpm.io/installation,
10:37:52    or let Vaadin use the default pnpm version by excluding 'pnpm.global' (or setting it to false) from configuration.
10:37:52    ======================================================================================================

When logged in on the agent, I'm able to launch pnpm successfully.

It turns out the plugin is using the where command (https://github.com/vaadin/flow/blob/77d281cce70085a362d238ea413f99f967c69d60/flow-server/src/main/java/com/vaadin/flow/server/frontend/FrontendToolsLocator.java#L78) and the Amazon Coretto Docker image does not include this. After installing where I was able to build successfully.

In conclusion:

The problem is caused by a pnpm issue for certain platforms
The problem is fixed in more recent pnpm versions but the Vaadin 22 & 23 Gradle plugin use the problematic version
A workaround is to install node (v16.14+) and pnpm (v6+) on the build agent and specify -Ppnpm.global=true in the gradle command line. The which command is also required
A more permanent solution would be to modify the plugin to use a more recent version of pnpm (such as 6.32.3)


incorrect 'undefined has no properties' error caused by reverse abstract interpretation

This issue was imported from Closure Compiler's previous home at http://closure-compiler.googlecode.com
The link to the original issue is:
https://code.google.com/p/closure-compiler/issues/detail?id=109

In the NTI you get a "nullability" warning for that value instead.


Using statement missing for IOptionsSnapshot

You need to add a using statement to the home controller to use IOptionsSnapshot.
using Microsoft.Extensions.Options;

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

ID: 80b8d3d6-4125-638f-746a-4bbdf0378625
Version Independent ID: d917d876-79b4-b935-08f0-09ef86038dd7
Content: Tutorial for using Azure App Configuration dynamic configuration in an ASP.NET Core app
Content Source: articles/azure-app-configuration/enable-dynamic-configuration-aspnet-core.md
Service: azure-app-configuration
GitHub Login: @yegu-ms
Microsoft Alias: yegu

@76mel Thanks for the feedback. We are actively investigating and will get back to you soon.

Assigning this to Product PM and Doc Author to evaluate and update as appropriate.

Thanks for reporting this! We'll add this.

We added this and it's now published. #please-close

Thank you @yegu-ms
@76mel - We are closing this issue for now, if you have any further queries please tag us in your reply and happy to take the conversation forward. Thank you.


[5.2] Fixes #12821

As explained on #12821, this fixes a bug where a infinite loop occurs when trying to call any Auth facade method when the Guard Driver defined on auth.php config is set to a invalid driver.
I didn't created any test since there are no test files for this class, but the bug is obvious.

Thanks for following this up. :)


Add workflow for validating integration with Ert & Everest

We should have a standalone workflow that can pull existing wheels and test them with Ert & Everest.
This should be possible to start at will.

Integration testing is done from Everest.


[srp] common utils

This PR contain two commits from #6038 with common util used for SRP.

[logging] add log support for new region SRP
[dns] support new resource records (PTR, SRV, TXT, KEY, SIG, OPT)

Submitting it as a sperate PR so we can maybe review and merge it earlier which would then help with managing the client and server (and test/CI related) PRs.

Thanks @librasungirl . The PR is already merged. I will address these in a small separate PR.

Thanks @librasungirl . The PR is already merged. I will address these in a small separate PR.


Use Sidekiq::Process

This makes the code easier to read and relies on official Sidekiq APIs, which are less likely to break. It also only looks at the current process to see, whether it is still processing jobs, not any quieted process.
identity is inherited from Sidekiq::Util.
However, it relies on APIs added in Sidekiq 5

This would mean removing support for Sidekiq 4.X. This means that we'll have to update our stack (@ccyrille). In the mean time 5.0 is out since April 2017, so it looks pretty safe to upgrade.
Otherwise, LGTM!
For later reviewers, the sidekiq process doc is available here: https://github.com/mperham/sidekiq/wiki/API#processes.

This would mean removing support for Sidekiq 4.X. This means that we'll have to update our stack (@ccyrille). In the mean time 5.0 is out since April 2017, so it looks pretty safe to upgrade.
Otherwise, LGTM!
For later reviewers, the sidekiq process doc is available here: https://github.com/mperham/sidekiq/wiki/API#processes.

Since the PR author is not responding, we're gonna stabilize the code in a new branch. Hence, this PR should be closed. @ccyrille

@pyrsmk I think you could use this PR, committers from a repo are allowed to push to original fork branch. This would leave @iGEL's contribution to our git history, which seams more fair.

@BuonOmo In fact, I couldn't find a way to pull the branch locally. I followed these steps to be able to do it : https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally#modifying-an-inactive-pull-request-locally

Maybe he unchecked this option, that is unfortunate though :/


feat(gradle-inspector): Add an option to provide the init.gradle

The idea is to enable the user to provide a customized init.gradle to gradle-inspector via the analyzer configuration

The idea is to enable the user to provide a customized init.gradle to gradle-inspector via the analyzer configuration

Could you provide an example when using a custom init.gradle could be useful?
Using GI's generated init.gradle is a crucial part in getting the analysis right, as it applies a temporarily extracted Gradle plugin. I cannot think of a case where it makes sense to customize that.

Using GI's generated init.gradle is a crucial part in getting the analysis right, as it applies a temporarily extracted Gradle plugin. I cannot think of a case where it makes sense to customize that.

As a side note, what would make a little bit more sense to me is to allow passing a custom init.gradle for the "legacy" Gradle analyzer instead of GI, because for the former the whole logic is implemented in init.gradle without a separate plugin being applied.

We want to configure a default maven repository (artifactory) which is accessible to all projects.
Is the legacy Gradle analyzer not going to be deprecated in favor of Gradle Inspector?

We want to configure a default maven repository (artifactory) which is accessible to all projects.

So you want to use an additional, custom init.gradle that is used together with ORT's one, correct?
If so, what you considered to put your init.gradle below GRADLE_USER_HOME?

Thanks, using a custom init.gradle also works. Closing this PR.


GC usages of fileSourceHost

@hmusum PR

Should be good to go once #18773 has gone though all tests


For test_setting*: add priority-class and fix toleration

https://github.com/longhorn/longhorn/issues/2482

Regression - Build#209

Regression - Build#214

Should we pass in the chk_removed_tolerations to verify that tolerations are removed?

Thanks for the suggestion. Added.

test_setting* regression - build#334

This is an old PR that almost got forgotten. I've addressed all review comments. PTAL @shuo-wu , @PhanLe1010 , @innobead

test_setting* regression - build#334

@c3y1huang is this still valid? probably @chanow816 can take over.

Not working on this, closing.

Sorry. Will we ignore/discard this PR and the issue?


Issue 209: Compute the relative scores in real-time

This PR loads in data from the real-time runs from Feb 5th to March 11th. It is very much hardcoded to the file structure we saved things in , which changed after Feb 19th.
This creates a function that loops through the specified real-time forecast dates, loads in the draws dataframe for each location and each model, scores it, and combines all the scores with the metadata
The plot function takes in all those scores and filters to only look at locations and forecast dates where the wastewater data was present (approximated by there being any wastewater model draws and the ww model converged). It then computes and plots the average relative crps in heatmap format across forecast dates and locations, as well as providing summaries of the overall relative CRPS in real-time .
The overall crps and the plot of the relative scores can be found here: https://github.com/cdcent/cfa-forecast-renewal-ww/issues/778#issuecomment-2496253614

Thanks @kaitejohnson! A few minor comments, mainly that we shouldn't use rt for "real-time" given that we also use it for R ( t )

Yeah the problem is just length! I will try to think of another way to make the function names short enough and still descriptive and will request re-review


No processor type exists with name [opennlp]

Hi Spinscale,
sorry to bother you again, but I really don't get how to install your this repo.
I am in the situation where I installed ElastcSearch and Kibana (I know they are now required, but I need them) and I want to give the following command:
curl -X PUT "localhost:9200/_ingest/pipeline/opennlp-pipeline" -H 'Content-Type: application/json' -d'
{
  "description" : "A pipeline to do named entity extraction",
  "processors" : [
    {
      "opennlp" : {
        "field": "my_field",
        "ignore_missing": true
      }
    }
  ]
}'

this way I should add data to your plugin.
Sadly when I give that command I receive the following error:
{"error":
  {"root_cause":
    [{ "type":"parse_exception",
       "reason":"No processor type exists with name [opennlp]",
       "header":{"processor_type":"opennlp"}
    }],
  "status":400}

So if no processor exists with that name I thought maybe the installation hasn't finish correctly.
To install it I followed the following steps:

Download it and from within the downloaded folder I ran:
./gradlew clean check

Then I tried to give:
bin/elasticsearch-plugin install file://./Downloads/elasticsearch-ingest-opennlp-master/build/distributions/ingest-opennlp-<IP_ADDRESS>-SNAPSHOT.zip

but I receive an error:

ERROR: plugin directory [./Downloads/elasticsearch-ingest-opennlp-master/build/cluster/integTestCluster node0/elasticsearch-6.5.0/plugins/ingest-opennlp] already exists; if you need to update the plugin, uninstall it first using command 'remove ingest-opennlp'

so I really don't know what to do. Do you have some clue of where the problem is?
Note: Just to be sure, the bin/elasticsearch-plugin folder from where I ran the command was in

elasticsearch-ingest-opennlp-master/build/cluster/integTestCluster node0/elasticsearch-6.5.0

Please, let me know if I could give you some more information to clearify the situation

@spinscale nothing?

can you share the output of plugins/ingest-opennlp (just sth like find plugins -type f should be sufficient.
Also, when elasticsearch is running, can you share the output from the /_nodes/stats endpoint as well.
Thanks!

can you explain why you tried to install that plugin in the tests directory named elasticsearch-ingest-opennlp-master/build/cluster/integTestCluster node0/elasticsearch-6.5.0? I do not understand the intention behind this. Can you clarify?

@spinscale

@Meru3m If possible, I suggest reinstalling with the bundle (.zip file) plugin instead of building it locally.
To do that for elasticseasrch 6.5.3:
(adjust the path as needed, these are specific to CentOS 7)
export ES_PATH_CONF=/etc/elasticsearch;/usr/share/elasticsearch/bin/elasticsearch-plugin remove ingest-opennlp
export ES_PATH_CONF=/etc/elasticsearch;/usr/share/elasticsearch/bin/elasticsearch-plugin install https://github.com/spinscale/elasticsearch-ingest-opennlp/releases/download/<IP_ADDRESS>/ingest-opennlp-<IP_ADDRESS>.zip
Make sure you have downloaded (in the right directory) and have appended the model file config to the elasticsearch.yml file.
# OpenNLP
ingest.opennlp.model.file.persons: en-ner-persons.bin
ingest.opennlp.model.file.dates: en-ner-dates.bin
ingest.opennlp.model.file.locations: en-ner-locations.bin
Restart elasticsearch while tailing the logfile to insure the plugin was loaded, it should look like this:
[2018-12-12T10:18:38,694][INFO ][o.e.p.PluginsService     ] [master-2] loaded plugin [ingest-opennlp]
Or by the API
curl -XGET "https://localhost:9200/_nodes/ingest"
Hopefully then opennlp processor will then be accessible to your ingest pipeline.
Here's screenshot of using opennlp on a twitter displayed through Kibana's graph app.

Thank you @elastickent I'll try and post the result here

Hi @elastickent,
just to be sure, when you wrote:
"Make sure you have downloaded (in the right directory) and have appended the model file config to the elasticsearch.yml file.
OpenNLP
ingest.opennlp.model.file.persons: en-ner-persons.bin
ingest.opennlp.model.file.dates: en-ner-dates.bin
ingest.opennlp.model.file.locations: en-ner-locations.bin"
could you specify where should be the "right" directory?

On centos, for me it worked by dropping them into:
/etc/elasticsearch/ingest-opennlp
e.g.
[root@sensor-01 ingest-opennlp]# pwd
/etc/elasticsearch/ingest-opennlp
[root@sensor-01 ingest-opennlp]# tree
├── en-ner-dates.bin
├── en-ner-locations.bin
└── en-ner-persons.bin


cog build fails at `Adding labels to images...

I'm dumb and am trying to follow this guide to set up this repo on a google cloud instance. It failed multiple times, even after clearing out docker in between runs. Have you seen this before? Here are my logs:
andre@stable-diffusion-api:~/cog-stable-diffusion$ cog build
⚠ Cog doesn't know if CUDA 11.6.2 is compatible with PyTorch 1.12.1 --extra-index-url=https://download.pytorch.org/whl/cu116. This might cause CUDA problems.
Building Docker image from environment in cog.yaml as cog-cog-stable-diffusion...
[+] Building 430.8s (17/17) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 1.69kB                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => resolve image config for docker.io/docker/dockerfile:1.2                                                                                0.4s
 => docker-image://docker.io/docker/dockerfile:1.2@sha256:e2a8561e419ab1ba6b2fe6cbdf49fd92b95912df1cf7d313c3e2230a333fdbcc                     0.6s
 => => resolve docker.io/docker/dockerfile:1.2@sha256:e2a8561e419ab1ba6b2fe6cbdf49fd92b95912df1cf7d313c3e2230a333fdbcc                         0.0s
 => => sha256:e3ee2e6b536452d876b1c5aa12db9bca51b8f52b2505178cae6d13e33daeed2b 528B / 528B                                                     0.0s
 => => sha256:86e43bba076d67c1a890cbc07813806b11eca53843dc643202d939b986c8c332 1.21kB / 1.21kB                                                 0.0s
 => => sha256:3cc8e449ce9f6e0752ede8f50a7334bf0c7b2d24d76da2ffae7aa6a729dd1da4 9.64MB / 9.64MB                                                 0.3s
 => => sha256:e2a8561e419ab1ba6b2fe6cbdf49fd92b95912df1cf7d313c3e2230a333fdbcc 1.69kB / 1.69kB                                                 0.0s
 => => extracting sha256:3cc8e449ce9f6e0752ede8f50a7334bf0c7b2d24d76da2ffae7aa6a729dd1da4                                                      0.2s
 => [internal] load metadata for docker.io/nvidia/cuda:11.6.2-cudnn8-devel-ubuntu20.04                                                         0.5s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 114.38kB                                                                                0.0s
 => [stage-0 1/9] FROM docker.io/nvidia/cuda:11.6.2-cudnn8-devel-ubuntu20.04@sha256:91779650798919050553d6673d04a96bfd7cdf3fa931b6ff32120b7f  88.9s
 => => resolve docker.io/nvidia/cuda:11.6.2-cudnn8-devel-ubuntu20.04@sha256:91779650798919050553d6673d04a96bfd7cdf3fa931b6ff32120b7f2eaaa4ad   0.0s
 => => sha256:624cfe37262e44c78cd50ec7bc8a98e417be3b81bb215eed099bf7da343b1a63 16.20kB / 16.20kB                                               0.0s
 => => sha256:3a665e4036160d33fc32ce19c889271febc4fe4cdb82637cdd8c9ef10ca9541c 23.60MB / 23.60MB                                               0.4s
 => => sha256:91779650798919050553d6673d04a96bfd7cdf3fa931b6ff32120b7f2eaaa4ad 743B / 743B                                                     0.0s
 => => sha256:828017b99ce1b75fe6307d54f97bdd9f224730a1a3f31d935ce85209cb08c93c 2.43kB / 2.43kB                                                 0.0s
 => => sha256:eaead16dc43bb8811d4ff450935d607f9ba4baffda4fc110cc402fa43f601d83 28.58MB / 28.58MB                                               0.6s
 => => sha256:cb69caf25724810d45aec6392c11de6f67c2efde38da9d46402857dedb68aefb 7.93MB / 7.93MB                                                 0.5s
 => => sha256:bcf9a52c75ac54dc66b5b683fc8dc2bb8a1cc8eef9340433a3efbfe8d6fa3006 187B / 187B                                                     0.5s
 => => sha256:8941157b58ada869bd12299ba8a56cdc5317923a5ce7df8158c5a3b44ff2fb67 6.43kB / 6.43kB                                                 0.6s
 => => sha256:9ce4eceb346b57d4be964a3a57551204b7435b2eae1d8c3154ef672661d710e4 1.12GB / 1.12GB                                                28.3s
 => => sha256:01035e520ac2fd77f181410687ecc81e9df074e738f8a4dfea4589572c663bd8 1.44GB / 1.44GB                                                32.8s
 => => sha256:b1c91cec61e689319fc5354207f545dc4d065599ae530f8aae92bded993c72e3 62.66kB / 62.66kB                                               0.7s
 => => extracting sha256:eaead16dc43bb8811d4ff450935d607f9ba4baffda4fc110cc402fa43f601d83                                                      1.0s
 => => sha256:246ba1b32462cea77206e04797df75780a0bdebd112b020b9bf11a7c6694eaa1 85.60kB / 85.60kB                                               0.8s
 => => sha256:dc3b3af10cf618c7b3038ca70bbcc422701fa0bf6cb9afae277406df7140445a 1.48GB / 1.48GB                                                24.5s
 => => extracting sha256:cb69caf25724810d45aec6392c11de6f67c2efde38da9d46402857dedb68aefb                                                      0.3s
 => => extracting sha256:3a665e4036160d33fc32ce19c889271febc4fe4cdb82637cdd8c9ef10ca9541c                                                      0.5s
 => => extracting sha256:bcf9a52c75ac54dc66b5b683fc8dc2bb8a1cc8eef9340433a3efbfe8d6fa3006                                                      0.0s
 => => extracting sha256:8941157b58ada869bd12299ba8a56cdc5317923a5ce7df8158c5a3b44ff2fb67                                                      0.0s
 => => extracting sha256:9ce4eceb346b57d4be964a3a57551204b7435b2eae1d8c3154ef672661d710e4                                                     13.8s
 => => extracting sha256:b1c91cec61e689319fc5354207f545dc4d065599ae530f8aae92bded993c72e3                                                      0.0s
 => => extracting sha256:01035e520ac2fd77f181410687ecc81e9df074e738f8a4dfea4589572c663bd8                                                     21.0s
 => => extracting sha256:246ba1b32462cea77206e04797df75780a0bdebd112b020b9bf11a7c6694eaa1                                                      0.0s
 => => extracting sha256:dc3b3af10cf618c7b3038ca70bbcc422701fa0bf6cb9afae277406df7140445a                                                     20.2s
 => [stage-0 2/9] RUN rm -f /etc/apt/sources.list.d/cuda.list &&     rm -f /etc/apt/sources.list.d/nvidia-ml.list &&     apt-key del 7fa2af80  3.8s
 => [stage-0 3/9] RUN --mount=type=cache,target=/var/cache/apt apt-get update -qq && apt-get install -qqy --no-install-recommends  make  bui  25.5s
 => [stage-0 4/9] RUN curl -s -S -L https://raw.githubusercontent.com/pyenv/pyenv-installer/master/bin/pyenv-installer | bash &&  git clone  134.3s
 => [stage-0 5/9] COPY .cog/tmp/build3839558126/cog-0.0.1.dev-py3-none-any.whl /tmp/cog-0.0.1.dev-py3-none-any.whl                             0.0s
 => [stage-0 6/9] RUN --mount=type=cache,target=/root/.cache/pip pip install /tmp/cog-0.0.1.dev-py3-none-any.whl                              11.4s
 => [stage-0 7/9] RUN --mount=type=cache,target=/root/.cache/pip pip install   diffusers==0.6.0 torch==1.12.1 --extra-index-url=https://dow  146.2s
 => [stage-0 8/9] WORKDIR /src                                                                                0.0s
 => [stage-0 9/9] COPY . /src                                                                                0.1s
 => exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:55b1710a44395212351d427a7761e45845e5136e435145c8c20d4ee3c0cfccdc                                                   0.0s
 => => naming to docker.io/library/cog-cog-stable-diffusion                                                                                0.0s
 => exporting cache                                                                                0.0s
 => => preparing build cache for export                                                                                0.0s
Adding labels to image...

docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: initialization error: nvml error: driver not loaded: unknown.

ⅹ Failed to get type signature: exit status 125

I kicked it enough and it works!

How have you solved it? I am stuck at the same point. Should I wait hours?


How to hide cancel button after verification is finished.

When you completed the process of verification, if you press the X button to cancel in the screen "You're done", apparently you can cancel the process or, at least, the app shows you abandoned the process, but the info has sent and you can be verified anyway.
The cancel button should be hide after send the verification data.

Hello @darwin-morocho we will fix it next version, thx a lot!


Warning about unsampled nodes is unnecessary for pMCMC

When using pMCMC (sampler RW_PF) from nimbleSMC, the warning
[Warning] No samplers assigned for 25 nodes, use conf$getUnsampledNodes() for node names
appears from the compileNimble step because there are, indeed, no samplers on the latent-states of the state-space model.
Can we provide a way to manage that?  Or when the pMCMC sampler is added emit a message saying it is ok to ignore the warning later?

This issue (determining nodes which are sampled by a given sampler, beyond the target nodes) at present is handled as a special case (for the posterior_predictive sampler only) around line 1200 of MCMC_configuration.R.
Quick fix would be adding special cases also for the RW_PF and RW_PF_block samplers, to recognize that the latent nodes are also sampled.  A more general fix would be including an optional method for all samplers, akin to samplerFunction$getNamesOfSampledNodesBeyondTargetNodes().  Let's hold that thought for the future.

This issue is addressed as a special case for the RW_PF and RW_PF_block samplers in PR #1266.


Custom Local logos in Static Folder lost when updating

Describe the bug
I did some custom local logos in Static folder and they were lost when updating
Expected behavior
Logos to remain after updating
Screenshots
Environment details:

Environment (HASSIO, Raspbian, etc): Home Assistant OS
Home Assistant version installed: 2022.3.5
Component version installed: 0.6.1
Last know working version:
TV model: QE65Q7FNA

Output of HA logs

Additional context

Upgrade is not managed by integration, there is nothing that I can do. I will eventually add a warning in Readme.

Might be worth using another folder, say in www to store the logos ?

This should be available with last release. Please check and let me know if everything is ok.

Works great, many thanks


Add ConfigMap as an Owned Resource for Prometheus

Description
Apparently Prometheus instances write owner references to ConfigMaps.

/lgtm

/approve


feat(control plane): allow images to be built

Provide the ability to build container images for the various control
plane components.
Before performing a nix-build, ensure you are in the ../Mayastor
directory.
e.g.
To build a specific control plane service image such as the node
service:
nix-build -A services.node-image
To build a development image, add the "-dev" suffix:
nix-build -A services.node-image-dev
To build all service images:
nix-build -A services
e.g.
To build a specific operator such as the node operator:
nix-build -A operators.node-image
To build a development image, add the "-dev" suffix:
nix-build -A operators.node-image-dev
To build all operator images:
nix-build -A operators

Closing this PR as additional changes are required.

Closing this PR as additional changes are required.


I am trying to port Personnel To My mod pack of sonic.exe 3.0 but with less space (And I dont have 64 bits) and my psych engine just crashes

Describe your bug here.
I am trying to port Personnel To My mod pack of sonic.exe 3.0 but with less space (And I dont have 64 bits) and my psych engine just crashes
Command Prompt/Terminal logs (if existing)
C:\HaxeToolkit\haxe\std/haxe/format/JsonParser.hx (line 223)
C:\HaxeToolkit\haxe\std/haxe/format/JsonParser.hx (line 143)
C:\HaxeToolkit\haxe\std/haxe/format/JsonParser.hx (line 90)
C:\HaxeToolkit\haxe\std/haxe/format/JsonParser.hx (line 57)
StageData.hx (line 91)
StageData.hx (line 63)
editors/ChartingState.hx (line 1657)
flixel/FlxState.hx (line 203)
flixel/FlxGame.hx (line 747)
flixel/FlxGame.hx (line 677)
flixel/FlxGame.hx (line 551)
openfl/events/EventDispatcher.hx (line 402)
openfl/display/DisplayObject.hx (line 1399)

Uncaught Error: Invalid escape sequence \E at position 23
Please report this error to the GitHub page: https://github.com/ShadowMario/FNF-PsychEngine

> Crash Handler written by: sqirra-rng

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no

Not a bug
Broken stage json

It's a problem with Personel's original .json, you're gonna have to edit the json in a text editor or something. (You should move the events that are in notes as -1 to actual events)

Ok Gracias!

Es un problema con el .json original de Personel, tendrá que editar el json en un editor de texto o algo así. (Debe mover los eventos que están en notas como -1 a eventos reales)

Ok Gracias!

Thanks To Gostar64 To help to fix the problem


[Bug]: shopify app deploy still asking for prompt even though --force flag is specified

Please confirm that you have:

[x] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[x] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
App
Expected behavior
It should not prompt for extenson migration if force flag is specified.
Actual behavior
It tried to prompt, and error out:
╭─ info ───────────────────────────────────────────────────────────────────────╮
│                                                                              │
│  Extension migrations can't be undone.                                       │
│                                                                              │
│  Your "X" configuration has been updated. Migrating gives you       │
│  access to new features and won't impact the end user experience. All        │
│  previous extension versions will reflect this change.                       │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯
╭─ error ──────────────────────────────────────────────────────────────────────╮
│                                                                              │
│  Failed to prompt:                                                           │
│                                                                              │
│  Migrate "X"?                                                          │
│                                                                              │
│  This usually happens when running a command non-interactively, for example  │
│   in a CI environment, or when piping to or from another process.            │
│                                                                              │
│  To resolve this, specify the option in the command, or run the command in   │
│  an interactive environment such as your local terminal.                     │
│                                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯

Verbose output

Reproduction steps

Operating System
Github Actions x86 runners
Shopify CLI version (check your project's package.json if you're not sure)
3.68.0
Shell
No response
Node version (run node -v if you're not sure)
No response
What language and version are you using in your application?
No response

Hi @FrankHeijden , i'm afraid that migrations need to be manually accepted, so --force won't have any effect here.
Extension migrations are a one-time thing, so once done, --force will work as normal.
I'll bring this to the team in case we want to revisit this behaviour.

Thanks @isaacroldan ! Makes sense -- might just be an us problem here since we use multiple Shopify Apps as "environments", so by the time it reaches the production app deployment via CI/CD, we already are very sure that we're doing the migration, and want it to be accepted automatically.
I guess it would be nice to have all these migrations/interactive questions be skipped with the --force flag, but not impossible to manage.
I do however have a similar related issue for functions, when one changes the name of the function, a similar prompt appears where Shopify will try to match the name defined locally against the name defined in Partners, and asks if the mapping is correct. It seems that after this prompt, it somehow stores this mapping locally, and doesn't actually change the name in partners, causing this prompt to be asked every time after a rename of a function (breaking CI/CD).

Hi @FrankHeijden!
That is correct, the mapping is stored locally in the .env files of your project. If you track those in git, then all instances of the CLI will get the correct matching and you'd only need to do it once.


Revert "Revert "rustup to rustc 1.15.0-dev (ace092f56 2016-12-13)""

Reverts the revert, #94, bringing #93 back into master.

Compiletest seems to be broken now

Yeah, what happened there?

I get the same failure locally.

Update to 0.2.5

It was released two hours ago

I'm on it.


(scribus) Switch to half-embedded

Description
Switches scribus to be half embedded. If both installers are embedded, the package is over 200mb.
Motivation and Context
Fixes #2397
How Has this Been Tested?
update.ps1 tested on Windows 10, package tested in Chocolatey test env.
Screenshot (if appropriate, usually isn't needed):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] I have updated the package description and it is less than 4000 characters.
[x] All files are up to date with the latest Contributing Guidelines
[x] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

:white_check_mark: Package verification completed without issues. PR is now pending human review


Cloud version update

Dedicated on 22.2.2 and serverless on 22.1.12
(Some serverless clusters are on 22.2 now but rollout will be completed on Jan 18)

@rmloveland good point, i update based off SRE tickets so I can start linking to those. really hoping to get this automated soon...


_source false  issue solved with Union<>

when set source false, Nest consider as exclude:["*"]. it's effect on performance.
i solve using Union<>.

Hi @pathikdevani, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile?

Hi @karmi, #2199 commit is create by my Github account. I am using Github on Visual Studio 2015 and  i have only one common email address.

@karmi i find my mistake, problem with visual studio. so i close this PR and create new from my email.


Add Endpoint to FaceClient Constructors

The update to Microsoft.Azure.CognitiveServices.Vision.Face v2.2.0-preview requires FaceClient .Endpoint to be set.
If EndPoint is not set, the SDK will throw the following ValidationException:

Microsoft.Rest.ValidationException: 'this.Client.Endpoint' cannot be null

Because the SDK requires the developer to set Endpoint, add it to both constructors to ensure it is always added.
We should also utilize the following best practices, which I've included in the Recommended Constructors:

Use nameof when throwing a System.ArgumentNullException
Use is null instead of == null

Current Constructors
First Constructor
public FaceClient(ServiceClientCredentials credentials, params DelegatingHandler[] handlers) : this(handlers)
{
    if (credentials == null)
    {
        throw new System.ArgumentNullException("credentials");
    }

    Credentials = credentials;
    if (Credentials != null)
    {
        Credentials.InitializeServiceClient(this);
    }
}

Second Constructor
public FaceClient(ServiceClientCredentials credentials, params DelegatingHandler[] handlers) : this(handlers)
{
    if (credentials == null)
    {
        throw new System.ArgumentNullException("credentials");
    }

    Credentials = credentials;
    if (Credentials != null)
    {
        Credentials.InitializeServiceClient(this);
    }
}

Recommended Constructor
First Constructor
public FaceClient(ServiceClientCredentials credentials, string endpoint, params DelegatingHandler[] handlers) : this(handlers)
{
    if(string.IsNullOrWhiteSpace(endpoint)
    {
        throw new System.ArgumentNullException(nameof(endpoint));
    }

    if (credentials is null)
    {
        throw new System.ArgumentNullException(nameof(credentials));
    }

    Credentials = credentials;
    Endpoint = endpoint;

    if (Credentials != null)
    {
        Credentials.InitializeServiceClient(this);
    }
}

Second Constructor
public FaceClient(ServiceClientCredentials credentials, string endpoint, params DelegatingHandler[] handlers) : this(handlers)
{
    if(string.IsNullOrWhiteSpace(endpoint)
    {
        throw new System.ArgumentNullException(nameof(endpoint));
    }

    if (credentials is null)
    {
        throw new System.ArgumentNullException(nameof(endpoint));
    }

    Credentials = credentials;
    Endpoint = endpoint;

    if (Credentials != null)
    {
        Credentials.InitializeServiceClient(this);
    }
}

Adding @noellelacharite for visibility


Allow undefined max_age parameter in query_results endpoint

An Error 500 would be returned by the endpoint if you attempt to
pass a query parameter to the dashboard since maxAge is undefined in the JavaScript code. This line of code was being executed:
https://github.com/EverythingMe/redash/blob/74a5121be232a0a6002928c38c7290298370c7e0/rd_ui/app/scripts/services/resources.js#L454

Thanks!


Sourcecode or updated executable for ProtoBufGenerator availabe?

The available ProtoBufGenerator executable does not produce the correct code for the latest version of the library (and not the same code as the one included in the examples). Could you make an updated version of the ProtoBufGenerator executeable available? Or the source code for it?

I added the sourcecode for it in de special sub branch: https://github.com/ultraware/DelphiGrpc/tree/master-Generator
(not sure if it still works though...)

Thank you very much, I will try it out.


image-builder failed with error "qemu-system-x86_64": executable file not found in $PATH

What happened:
Trying to create ubuntu baremetal image for Intel NUC following instructions from https://anywhere.eks.amazonaws.com/docs/reference/artifacts/#build-bare-metal-node-images
Ran the command to build
image-builder build --os ubuntu --hypervisor baremetal --release-channel 1-26

Got error:
Build 'qemu' errored after 964 microseconds: Failed creating Qemu driver: exec: "qemu-system-x86_64": executable file not found in $PATH

What you expected to happen:
The script to
How to reproduce it (as minimally and precisely as possible):

Setup Ubuntu Desktop 22.10 as administrative machine
Follow instructions to install prereqs https://anywhere.eks.amazonaws.com/docs/reference/artifacts/#build-bare-metal-node-images
The instructions have a line that mentions qemu-kvm

sudo apt install jq make python3-pip qemu-kvm libvirt-daemon-system libvirt-clients virtinst cpu-checker libguestfs-tools libosinfo-bin unzip ansible -y

Anything else we need to know?:
Environment:

Ubuntu 22.10

Workaround that remove the error
sudo apt install qemu-system-x86

Docs should be updated with this additional package


Problèmes d'affichage

I'm using the master branch of shaarli community and your theme. I've upgraded shaarli, and your theme. But I encountered some display problems.
Here is how it looks like with a local install. I tried with different browser. It was the same problem on the server installation ( https://id-libre.org/shaarli ), but for this one I went back to the default theme.

I've disabled the plugins I was using (qrcode), but that wasn't the problem. The funny thing is that when I downgraded to the previous versions of the theme, the problem was still there, even after removing the cache of the browser.
Of course I will give you all the missing details, you can ask ! :)

I should have thought of it before : I tried to start from a fresh install of shaarli and your theme, reimport the data, and everything is working fine. Sorry.

No problem ;)
Based on the screenshot, it looks like your version of Shaarli Material was not the last one (based on the presence of search and filter buttons) so yep, a fresh install is what I would have recommended. I'm glad it works now.

By the way you could disable the qrcode plugin as Shaarli Material still includes it's own way of generating qrcodes for now (via the bottom right icon).

That's right, it's even better like this ! Thank you.


React warnings being emitted in block editor

I'm seeing some warnings from React being emitted in the editor which are emanating from carousel.js:

Warning: Invalid DOM property stroke-width. Did you mean strokeWidth?
Warning: Invalid DOM property stroke-linejoin. Did you mean strokeLinejoin?
Warning: Invalid DOM property stroke-linecap. Did you mean strokeLinecap?
Warning: React does not recognize the outsetArrows prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase outsetarrows instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Warning: Received false for a non-boolean attribute rtl. If you want to write it to the DOM, pass a string instead: rtl="false" or rtl={value.toString()}. If you used to conditionally omit it with rtl={condition && value}, pass rtl={condition ? value : undefined} instead.
Warning: Invalid DOM property class. Did you mean className?
Warning: Received false for a non-boolean attribute group. If you want to write it to the DOM, pass a string instead: group="false" or group={value.toString()}. If you used to conditionally omit it with group={condition && value}, pass group={condition ? value : undefined} instead.
Warning: Invalid DOM property tabindex. Did you mean tabIndex?

How are you getting these? 🤔  I'm not seeing any such warnings when testing locally.

I'm seeing them in the console after I add a block, save, and reload the editor.
I see it in 5.8 with both AMP and Gutenberg either active or inactive.
Here's a full stack trace:
Warning: Invalid DOM property `class`. Did you mean `className`?
    at div
    at div
    at qo (https://wordpressdev.lndo.site/content/plugins/gutenberg-bento/build/carousel.js?ver=4868ee5b50f477fce1b19f201957a4ce:107:26002)
    at div
    at div
    at Yn (https://wordpressdev.lndo.site/content/plugins/gutenberg-bento/build/carousel.js?ver=4868ee5b50f477fce1b19f201957a4ce:107:8022)
    at ua (https://wordpressdev.lndo.site/content/plugins/gutenberg-bento/build/carousel.js?ver=4868ee5b50f477fce1b19f201957a4ce:107:31922)
    at figure
    at CarouselEdit (https://wordpressdev.lndo.site/content/plugins/gutenberg-bento/build/carousel.js?ver=4868ee5b50f477fce1b19f201957a4ce:224:5)
    at Edit (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:9417:5)
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:36098:11
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:36302:103
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:37550:112
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:39513:120
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:37867:109
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:38687:11
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-library/index.min.js?ver=0ca86ebaff56771500f4b156db568dd7:32151:5
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/edit-post/index.min.js?ver=0de1c601eddd232b446fe0290b8887f2:23009:5
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/data/index.min.js?ver=de566fe1cefa0f5d7f4d9f61a55fd465:2151:97
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/data/index.min.js?ver=de566fe1cefa0f5d7f4d9f61a55fd465:2274:81
    at <anonymous> (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/compose/index.min.js?ver=c0f29a71b094377d853c6c6379bcdd79:2368:10)
    at FilteredComponentRenderer (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/components/index.min.js?ver=ad5707851313b2b3ceb9d550da4c8d7b:73283:9)
    at BlockEdit (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:9486:5)
    at BlockCrashBoundary (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:9925:5)
    at BlockListBlock (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:10304:3)
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:36145:5
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:36566:5
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:37431:5
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:38363:92
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:39526:51
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:37881:106
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:38706:5
    at FilteredComponentRenderer (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/components/index.min.js?ver=ad5707851313b2b3ceb9d550da4c8d7b:73283:9)
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/compose/index.min.js?ver=c0f29a71b094377d853c6c6379bcdd79:2315:8
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/data/index.min.js?ver=de566fe1cefa0f5d7f4d9f61a55fd465:2151:97
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/data/index.min.js?ver=de566fe1cefa0f5d7f4d9f61a55fd465:2274:81
    at <anonymous> (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/compose/index.min.js?ver=c0f29a71b094377d853c6c6379bcdd79:2360:12)
    at Items (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:10674:3)
    at BlockListItems
    at div
    at Head (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:10556:3)
    at Root (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:10630:3)
    at BlockToolsBackCompat (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:15806:3)
    at BlockList (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:10664:3)
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:34461:5
    at div
    at WritingFlow (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:35180:3)
    at MaybeIframe (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/edit-post/index.min.js?ver=0de1c601eddd232b446fe0290b8887f2:22262:3)
    at div
    at MotionComponent (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/edit-post/index.min.js?ver=0de1c601eddd232b446fe0290b8887f2:5216:80)
    at div
    at MotionComponent (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/edit-post/index.min.js?ver=0de1c601eddd232b446fe0290b8887f2:5216:80)
    at InsertionPoint (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:16973:3)
    at div
    at BlockTools (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:16625:3)
    at VisualEditor (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/edit-post/index.min.js?ver=0de1c601eddd232b446fe0290b8887f2:22299:3)
    at div
    at div
    at div
    at div
    at InterfaceSkeleton (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/edit-post/index.min.js?ver=0de1c601eddd232b446fe0290b8887f2:33454:3)
    at Layout (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/edit-post/index.min.js?ver=0de1c601eddd232b446fe0290b8887f2:18523:3)
    at ErrorBoundary (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/editor/index.min.js?ver=b497131a201b9e9df0f7e76ef6c297a8:3548:5)
    at BlockRefsProvider (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:29659:3)
    at BlockEditorProvider (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:29709:5)
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:30006:5
    at WithRegistryProvider(BlockEditorProvider)
    at BlockContextProvider (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/block-editor/index.min.js?ver=75df474851a95563b250d0be610a7790:8824:3)
    at EntityProvider (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/core-data/index.min.js?ver=ea65fd98d89111cf54aaf650c1c40a18:2951:3)
    at EntityProvider (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/core-data/index.min.js?ver=ea65fd98d89111cf54aaf650c1c40a18:2951:3)
    at EditorProvider (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/editor/index.min.js?ver=b497131a201b9e9df0f7e76ef6c297a8:10531:3)
    at https://wordpressdev.lndo.site/content/plugins/gutenberg/build/editor/index.min.js?ver=b497131a201b9e9df0f7e76ef6c297a8:10802:5
    at WithRegistryProvider(EditorProvider)
    at SlotFillProvider (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/components/index.min.js?ver=ad5707851313b2b3ceb9d550da4c8d7b:83504:3)
    at SlotFillProvider (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/components/index.min.js?ver=ad5707851313b2b3ceb9d550da4c8d7b:83873:5)
    at Provider (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/components/index.min.js?ver=ad5707851313b2b3ceb9d550da4c8d7b:83812:3)
    at Editor (https://wordpressdev.lndo.site/content/plugins/gutenberg/build/edit-post/index.min.js?ver=0de1c601eddd232b446fe0290b8887f2:22747:3)

Ah, I suppose you're using SCRIPT_DEBUG? 💡
Looks like I'll need to file some bugs :)

Ah, I suppose you're using SCRIPT_DEBUG? 💡

Yes, I am.

Reported at https://github.com/ampproject/amphtml/issues/35553


Update pretrained_openvino.rst

Added models examples to docs relating to this given at  https://github.com/luxonis/depthai/tree/main/resources/nn. Also added doc for models to be passed as first cnn (-cnn ) and second cnn (-cnn2)
All the examples added are from the depthai repo and are tested and verified again (Date - 1st March 2021) on armv7l system machine. No errors reported on execution.

Sweet thank you!!!


Chinese translation added

Looks like @avjinder you connect your repo with Travis CI, but you didn't add .travis.yml file. That's the reason of "All checks have failed"


Get the ID of an assistant if we create it from the Open AI website

Hello to all,
Firstly, many thanks for your work on this library. I want to ask something not specifically related with the library, but, that maybe someone here knows and therefore can answer: that can be very useful for me and probably other people who may are questioning itself the same thing. The question is how to get the ID of an assistant if we create it from the Open AI website, in case that this is possible, since I am not sure about it: I try to locate the ID in the Open AI website, but, I can't locate a valid ID that then I can use with the library / API.
The idea is to use the API with an assistant which is already created using the Open AI website. Is this possible? Or may we need to create the assistant using the API in order to get the assistant ID?
Thanks very much for your help!!

There is a page where you can find a list of all Assistants and see their IDs: https://platform.openai.com/assistants
And you can fetch a list of all assistants via API as well: https://github.com/openai-php/client#list-3

Hello to all,
Thanks very much @gehrisandro. Yes... I forget about the ability to list the assistants... but the page that you link can be also really useful. Thanks very much again!


audit: Remove FILEUTILS_METHODS constant

This constant hasn't been used since there was an audit_line method, and as such is vestigial.
Traced back to 3e3a4cad500ccc347209a7df40ad5e73dc6f88f2.

Ah my bad, I missed that.

Not a problem 🙂

Thanks @woodruffw!


DX Spiders on contest days

On contest days, DX Spiders servers are likely to get overloaded and the exception handling is not done well.  The application gets kicked out and the VFO control page becomes unavailable.

I will have to look into logging into DX Spiders and logging out for each data lookup


Add YOLO coder

Let's add this to the glossary and repo page docs

The current UI suggests that pushes to main might be a problem, but I am curious if this is a glossary will we be adding an opinion or suggestion in this context.

My suggestion is we provide context on why pull requests are important for gathering context and storytelling for the future developer. The open source guide kind of provides context on this. https://opensource.guide/how-to-contribute/#opening-a-pull-request


Dashboard settings: date interval

Hi, and sorry for the silly question.
Is there a way to set a different time interval for the data displayed in the dashboard? i.e. last month, last week, last n months.
Thanks and have a nice day.

@jeanpaulrh sorry thought I answered you. There currently is not but I believe is in development by GoAccess. Please refer to https://github.com/allinurl/goaccess/issues/117
There is a limited way I can do it on my end but it would require a restart of the container every day which would not be helpful.


Add utils to parse a CAPI workers spec

Description of changes
Depends on https://github.com/aws/eks-anywhere/pull/3616
For context: https://github.com/aws/eks-anywhere/pull/3432
Testing
Unit tests
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


RIFee Amortization logic does not fully match AWS Cost Explorer

This issue just appeared 9/1/2023. I have a case opened with Amazon to see if they have a Cost Explorer issue, or a CUR issue but wanted to report it here too.
The issue is as follows.
We have many account that have an RIFee on 9/1/2023
The AWS Cost Explorer view of this data shows an amortized value of about 137$ on that single day when looking at 30 days of data and dimension by charge type and Amortized cost data.
The logic for calculating the amortized cost of an RIFee listed here: is
https://wellarchitectedlabs.com/cost/300_labs/300_cur_queries/queries/global/
and
https://wellarchitectedlabs.com/cost/300_labs/300_cur_queries/query_help/#unblended-blended-amortized-and-net-costs
       WHEN (line_item_line_item_type = 'RIFee') THEN (reservation_unused_amortized_upfront_fee_for_billing_period + reservation_unused_recurring_fee)

In the dataset we have, reservation_unused_amortized_upfront_fee_for_billing_period = around 14000 USD, and reservation_unused_recurring_fee is 0. So we are seeing a spike on 9/1 showing a large RIFee that differs from what the AWS Console shows.
Even if we follow the true-up approach which takes into account this: reservation_amortized_upfront_fee_for_billing_period
The math still doesn't match even close to the AWS console (off by about 5000$)

@iakov-aws  case: CASE<PHONE_NUMBER>1] AWS Cost Explorer RIFee is not matching CUR data


(feat) Added support for Custom Annotation

Signed-off-by: Rahul M Chheda<EMAIL_ADDRESS>
What this PR does / why we need it:
- Have added support for custom annotation, with key being custom, but the value still being "true"/"false" to validate the application
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
- https://github.com/litmuschaos/litmus/issues/1252
Special notes for your reviewer:
- Have added comments to show, how it works.
Checklist:

[ ] Fixes #
[ ] Labelled this PR & related issue with documentation tag
[ ] PR messages has document related information
[ ] Labelled this PR & related issue with breaking-changes tag
[ ] PR messages has breaking changes related information
[ ] Labelled this PR & related issue with requires-upgrade tag
[ ] PR messages has upgrade related information
[ ] Commit has unit tests
[ ] Commit has integration tests

Add the custom annotation as ENV, in operator deployment:
spec:
      containers:
      - command:
        - chaos-operator
        env:
        - name: CUSTOM_ANNOTATION
          value: mayadata.io/rahul
        - name: WATCH_NAMESPACE
        - name: POD_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.name
        - name: OPERATOR_NAME
          value: chaos-operator
        image: rahulchheda1997/chaos-operator:latest
        imagePullPolicy: Always
        name: chaos-operator
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File

Now, annotate the application like this:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "1"
    mayadata.io/rahul: "true"

cc: @sumitnagal

The support for custom values to the annotations will be added in a separate PR.


[BUG] Fix incorrect libcuda.so found by cmake when multiple versions of CUDA exist

This PR contains a very minor fix and a modification in cmake.

Enforce NO_DEFAULT_PATH when CUDA path is found. This particularly resolves my issue when building on the server in my university: when multiple CUDA versions exist, the original FindCUDA.cmake could possibly use incorrect libcuda.so.
Print the dependencies found by FindXXXX explicitly. This could make it more friendly to developers who fail to build TVM due to dependency issues.

I posted details of this issue on the TVM forum: https://discuss.tvm.ai/t/incorrect-libcuda-so-when-multiple-versions-of-cuda-exist-problem-and-solution/886.

Re-triggering the CI: test_topi_matmul.test_matmul is flaky.
Related issue: #1784

A side note: It is undefined behavior to exit -1 in shells. Exit code should be unsigned int in [0, 255]. (http://pubs.opengroup.org/onlinepubs/7990989775/xcu/chap2.html#tag_001_014_007)

@tqchen Could you help review this? Thanks!


How to use nacos in sharingsphere

Question
How to config in sharingsphere to support nacos? ths!

Hi @keven0706 ,
now the nacos's support is not enough, ShardingSphere support ZooKeeper very well and you can try it.
Now we are refactoring the orchestration module, after refactor, it will support nacos very well, it will be released at 5.x version. Thanks.

thanks，expectation！


Fix stack traces handling when calling user.* methods

This fixes a bug that Gerardo and I found while implementing #248:
In #216, there is a regression in stack traces when an error is thrown from user.* methods.
For example, if you try to click an element that is invisible:
await user.click(invisibleButton)

Then the correct/ideal behavior would be to show an error message with that line as the first line of the stack.
Since the regression in #216, the stack trace is missing entirely.
This PR adds it back, and adds a test to make sure that it stays there.

Uh oh my solution works locally but not in CI 🤔


Emerging_modes join function with repeating values

In the MVG mode summary function, emerging mode table has multiple repeated rows

I was not able to recreate this bug. Please include which data was used when this bug appeared.

I was not able to recreate this bug. Please include which data was used when this bug appeared.

This has happened with AI4EU data and at least one more validator has seen the same issue. I believe it was sensemore.
Any case, the particular example shown in the morning is available below. It includes the original data and the modeId results
https://github.com/vikinganalytics/vibium-utils/tree/HAT_AI4EU/HAT_AI4EU/Full-Batch/Results/NO_0602_COMBUSTION_BLOWER_HWB_No2


wario_walking.gb won't start (waiting for GL)

Emulator gets stuck with the following output:
$ LD_LIBRARY_PATH=. ./gameboy wario_walking.gb
BOOTROM=0
DEBUG=0
SPEED_LIMIT=1
STDOUT=0
    0.000, GB starting...
    0.000, reset ok, waiting for GL...

I would need more information on the OS and GLFW implementation installed - I used GLFW3 on Mac OS up to Mojave and Ubuntu, please make sure you are using GLFW3 or modify the main_lcd.c code accordingly for some other version. The problem indicates that the program gets stuck in Line 167 of main_lcd.c: while (!gl_ok) usleep(10); - which means that gl_ok never gets set to TRUE. It should happen right after the gl window is created in lcd_init(), so I would suspect that the issue is somewhere between lines 97-107 and may be related to opening GLFW window.

The problem was that when GLFW is compiled with Wayland support then it disables X11 support, and because I am not running a Wayland session OpenGL initialization failed.


Fix StorageSuite.TestConfigStorageRemotes

This tests checks the contents of a map, assuming the maps stores the elements in a certain order. It only failed like once every 6 or 7 runs.
I fixed it by sorting the returned elements before comparing them.

Could you rebase this from origin/master?

I have tried to rebase it several times, with weird rebase conflicts I cannot solve. I will try again later.


Fixed: Missing required parameter: 'tool_resources.code_interpreter.file_ids'

Missing required parameter: 'tool_resources.code_interpreter.file_ids'
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.

Thanks for reporting this bug.
The changes have to go through the typespec as this is generated code by using typesepc.
I created a PR to reflect the changes in https://github.com/Azure/azure-rest-api-specs/pull/30206


README: Should mention IR and link to its description

IR is the central part of all this stuff. README should mention a few words about IR, and link to docs: https://ppci.readthedocs.io/en/latest/reference/ir.html . But that doc is very bare itself, to describe IR in more detail and give an example (I mean textual representation first of all).

This is a good idea. The readme does not mention IR-code. The IR-code is listed on the documentation page (ppci.rtfd.io).


How to yield a list of generators inside another generator?

I have a list of generators and I want to yield each in a series inside co( ) like this:
co(function* () {
  /* for each in generator list
  do something
  yield generator
  do something else
  */
})

Currently I am using a for of loop, but is there a way to accomplish this without mutation?

Recursion :D.
var performTasks = co.wrap(function * performTasks (arr) {
  var task = arr.shift()
  if (task) yield task
  if (arr.length) yield performTasks(arr)
})

co(function * () {
  yield performTasks([fn1, fn2, ...])
})

(Actually, since co lets you yield generators, you could avoid the extra co.wrap I think.)

I mean, yes, I tried recursion, and even a strange recursive generator, but now you tell me wrap was the key to this!! :laugh:
Thanks.


Allow renovatebot to rebase existing PRs on staging after renaming

After renaming of renovate bot name, existing PRs on staging are not getting updates. This PR adds old bot name into exceptions to overwrite changes from, so exiting PRs could be updated.
Needs to be reverted after some time.

/test build-service-e2e

/test build-service-e2e

/test build-service-e2e

/test build-service-e2e


FIRStorageDownloadTask pause problem

I can download a file with no problem using:
FIRStorageDownloadTask* task = [ref writeToFile:[NSURL fileURLWithPath:destinationFile]];

However, if I call the pause method, the download pauses for a few seconds and then resumes automatically! I am not calling the resume method but it resumes automatically.
I wonder what could be the problem?

I am also having this problem. Upon checking the status of the download task after pausing, it is set to .Resume
Can't seem to figure out why it auto restarts the download

That's a pretty interesting bug--definitely shouldn't be doing that! I'll take a look and see if I can resolve.

seeing the same issue, for what its worth the cancel method doesn't seem to work either. thanks in advance

We have been able to reproduce this issue and are working on a fix. Thanks for your patience.

It seems that downloadTask is not actually cancelling itself after completing its task.
Here is the case:

download a file by:
FIRStorageDownloadTask *downloadTask = [bubbleRef writeToFile:localURL completion:^(NSURL *URL, NSError *error){ //.... }];

delete the local file by:
[[NSFileManager defaultManager] removeItemAtPath:filePath error:nil];

downloadTask downloads the file again!!!

but:

download a file by:
FIRStorageDownloadTask *downloadTask = [bubbleRef writeToFile:localURL completion:^(NSURL *URL, NSError *error){ //.... }];

re-run app again.

delete the local file by:
[[NSFileManager defaultManager] removeItemAtPath:filePath error:nil];

no problems!

Any progress with the issue @schmidt-sebastian and @mcdonamp?

I believe that the fix for pause went into the latest release of Firebase (3.10.0 release notes). Do you mind updating and letting us know if this fixes your issue?

Yes, I can confirm that this problem is now fixed. We also updated our ANE to 3.10.0 and the pause/resume now works correctly on iOS too just like the Android side. Thanks.

Thanks for the quick reply but i've noticed that it was my fault and removed the comment already. It works solid with the latest release.


src: remove openwhisk varaiables from context

This commit removes the openwhisk variables that were added to the context object early in this project's life, when we were not sure if we would support running in openwhisk.
 Forgot to add the test file to my commit.


gtechmonitor ui2.awin.com results in this link is inactive

I assume there's an affiliate link set up for certain domains that nopecha is redirecting from. That affiliate link seems to be inactive. Instead of taking me to the destination site, the redirect stops and says "This link is inactive".

We do not have affiliate link redirects in our extension. You are using another extension that is using this shady practice.


CASSANDRA-16808 Fix pre-4.0 FWD_FRM parameter serializer

Committed as https://github.com/apache/cassandra/commit/c1f235f71d013318b86bddee3121beb4923ae0f9


[ASCII-2321] add a new CODEOWNERS linter to check its accuracy

What does this PR do?
This PR introduce a new linter to check correctness of .github/CODEOWNERS.
It checks for each rule that at least one file or a directory match the given pattern in the repo.
Motivation
It happens that the CODEOWNERS file is not updated when files/directorys are moved/deleted due to refactoring or other reason. This leads to a inconsistant CODEOWNERS file.
Describe how to test/QA your changes

/merge