Azure CLI 2.30.0 broke the az snapshot create

Describe the bug
As of Azure CLI 2.30.0, the "az snapshot create" logic broke for us.
We would use that to try to create a snapshot and in 2.29.2 (and before) it would create the snapshot.  With 2.30.0 it produces an error of the resource not being found.
To Reproduce
We use snapshot of VMSS disk instances in our system but it now has stopped working.
What we do:
We pick an instance (this case, #14)
We first read the data about that instance to get the disk:
'az' 'vmss' 'show' '--subscription' '3a96ef56-41a9-40a0-b0f3-fb125c2b8798' '--resource-group' 'SCM__msinz1' '--name' 'k8s-agentpool1-18861755-vmss' '--instance-id' '14'
This gets us storageProfile.osDisk.managedDisk.id = /subscriptions/3a96ef56-41a9-40a0-b0f3-fb125c2b8798/resourceGroups/SCM__msinz1/providers/Microsoft.Compute/disks/k8s-agentpool1-18861k8s-agentpool1-188617OS__1_897a52de44e94f1eac3e422b2aaa07d5
Then we stop the instance such that it is in stable state:
'az' 'vmss' 'stop' '--subscription' '3a96ef56-41a9-40a0-b0f3-fb125c2b8798' '--resource-group' 'SCM__msinz1' '--name' 'k8s-agentpool1-18861755-vmss' '--instance-ids' '14'
Then we try to snapshot that disk:
'az' 'snapshot' 'create' '--subscription' '3a96ef56-41a9-40a0-b0f3-fb125c2b8798' '--resource-group' 'SCM__msinz1' '--name' 'snapshot_k8s-agentpool1-18861755-vmss' '--source' '/subscriptions/3a96ef56-41a9-40a0-b0f3-fb125c2b8798/resourceGroups/SCM__msinz1/providers/Microsoft.Compute/disks/k8s-agentpool1-18861k8s-agentpool1-188617OS__1_897a52de44e94f1eac3e422b2aaa07d5' '--tags' 'BuiltFrom=k8s-agentpool1-18861755-vmss00000e' 'BuiltAt=2021-11-12 13:47:06.889728'
This has worked for well over a year without failure.
However, as of our execution with version 2.30.0, it returns with this failure:
(ResourceNotFound) The Resource 'Microsoft.Compute/disks/k8s-agentpool1-18861k8s-agentpool1-188617OS__1_897a52de44e94f1eac3e422b2aaa07d5' under resource group 'SCM__msinz1' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix
Code: ResourceNotFound
Message: The Resource 'Microsoft.Compute/disks/k8s-agentpool1-18861k8s-agentpool1-188617OS__1_897a52de44e94f1eac3e422b2aaa07d5' under resource group 'SCM__msinz1' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix

This is causing failures of our processes across all of azure right now.
Expected behavior
It should have created the snapshot - if I revert to 2.29.2, it does.
Environment summary
This is failing on Ubuntu 18.04 and 20.04 VMs with Azure CLI 2.30.0 installed.
This works in the same Ubuntu VMs with Azure CLI 2.29.2 (and prior) installed.
Additional context
This is extra complex to deal with reverting since the auth mechanism changed in 2.30.0 and reverting an instance in pipelines is tricky to do correctly.

@zhoxing-ms @jiasli to help with

Duplicate with #20258, so close this first

Seems like the --copy-start false workaround works for us too.


Bugs

Changes made:
Description
Images now load correctly when loaded on screen.
Added control props to the viz section component, so when you don't want figures or a fig caption you can just add the props and forgo the html templates associated with them.
Added these to the intro and impact components
Testing:
Before making this pull request, I:

[ ] Cleaned the code the way Vue likes it - run 'npm run lint --fix'
[x] Made sure all tests run
[ ] Ran WAVE plugin 508 compliance tool

I can confirm this has been checked on:

[x] Chrome
[x] Safari
[ ] Edge
[x] Firefox
[ ] Samsung Internet
[ ] Internet Explorer 11 (not supported, but still needs at least a working user redirect page)

Bleh, somehow I had the safari fix bleed into this branch...

and I fixed the pr issue, yay!


WebSocketTests.FalseUpgradeTest fails when DOTNET_SYSTEM_NET_HTTP_SOCKETSHTTPHANDLER_HTTP2UNENCRYPTEDSUPPORT=1

Describe the bug
Unit test WebSocketTests.FalseUpgradeTest fails on both netcoreapp3.1 and netcoreapp5.0 when environment variable DOTNET_SYSTEM_NET_HTTP_SOCKETSHTTPHANDLER_HTTP2UNENCRYPTEDSUPPORT=1.
This is likely by design at the moment (in which case having this issue around will help future people who may hit this). YARP currently always attempts to issue outgoing calls as HTTP/2. And when this env var is set, the outgoing HTTP stack will indeed honor that and issue an HTTP2 unencrypted request. However the simulated target server tries to handle it as HTTP/1.1 (which makes sense, since there's no ALPN step without TLS).
To Reproduce

Set environment variable DOTNET_SYSTEM_NET_HTTP_SOCKETSHTTPHANDLER_HTTP2UNENCRYPTEDSUPPORT=1
Run Microsoft.ReverseProxy.FunctionalTests unit tests

Unit test WebSocketTests.FalseUpgradeTest fails:
 Microsoft.ReverseProxy.WebSocketTests.FalseUpgradeTest
   Source: WebSocketTests.cs line 127
   Duration: 505 ms

  Message:
    Assert.Equal() Failure
    Expected: OK
    Actual:   InternalServerError
  Stack Trace:
    WebSocketTests.FalseUpgradeTest() line 154
    --- End of stack trace from previous location ---

Digging deeper, when ReverseProxy issues the outgoing request to the simulated target destination, the destination server is encountering the following exception from Kestrel:
Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Unrecognized HTTP version: ''
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpParser`1.RejectUnknownVersion(Int32 offset, ReadOnlySpan`1 requestLine)

Possible solutions

Do not always attempt HTTP/2 on outbound requests; perhaps only attempt HTTP/2 if the outbound request is using https?
Configure Kestrel on the target sample server in the functional test to use only HTTP/2? Doesn't seem sensible, as nobody (sane) should run WebSockets on HTTP/2 😄.

Further technical details

Latest master, commit 8841dac2a64b90a0eb6144f229885e832110bace
Platform: Windows 10

Yup, by design. Note DOTNET_SYSTEM_NET_HTTP_SOCKETSHTTPHANDLER_HTTP2UNENCRYPTEDSUPPORT was just removed from 5.0 in favor of a public API so we should be able to provide a better experience here: https://github.com/microsoft/reverse-proxy/issues/282

This does not reproduce on 5.0.0-rc.1.20451.14 on which the current 5.0 tests run.
Problem is now isolated to netcoreapp3.1 target.

Since this doesn't reproduce on 5.0, I'm closing it.


arch-x86: Revert Fix misc registers in mov instructions

Reverts gem5/gem5#593

I only created this PR to see if reverting this changed fixed a bug I'm observing with the X86 boot tests. This does not appear to be the case. I'm therefore closing.


WIP: adding shogun

Coverage decreased (-0.5%) to 93.958% when pulling f265cc6cc41029d9c4c1b5fecc07a610b5685b68 on antgonza:shogun into 77e5cd3ad4c819e39fcd2932b4617df4fad48461 on qiita-spots:master.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@77e5cd3). Click here to learn what that means.
The diff coverage is 86.66%.

@@            Coverage Diff            @@
##             master      #37   +/-   ##
=========================================
  Coverage          ?   86.84%
=========================================
  Files             ?        5
  Lines             ?      403
  Branches          ?       78
=========================================
  Hits              ?      350
  Misses            ?       24
  Partials          ?       29

Impacted Files
Coverage Δ

qp_shotgun/qc_filter/qc_filter.py
94.59% <100%> (ø)

qp_shotgun/shogun/utils.py
78.94% <78.94%> (ø)

qp_shotgun/shogun/shogun.py
90.16% <90.16%> (ø)

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 77e5cd3...05170e0. Read the comment docs.

The error is a timeout from the humman2 tests that we will move to a new repo. Thus, @semarpetrus, @tanaes and I decided to be ok to merge.


Python data model generation instructions don't work anymore in Ubuntu 24.04

Building on Noble beta / Rolling, Python / pip became a lot more conservative and the following error is returned when trying to install datamodel-code-generator:
$ pip3 install datamodel-code-generator
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.

    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.

    See /usr/share/doc/python3.12/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

Passing --break-system-packages works but there is probably a reason this was upgraded to an error, I haven't tried using pipx yet.

Is anyone in the ROS community looking at the current state of the python ecosystem. I've heard rumours that Python is also planning on moving to a rust/cargo like packaging format via the pyproject.toml.  In any case I don't think mixing pip packages with ros2 system packages is good practice in the longer term.


Operator should fail if attempting to upgrade knative from N to N+2 or greater

When the user upgrades the operator, the operator should evaluate the current version of knative and if the operator is unable to update the version one at a time, then the operator should fail the upgrade.

Interesting question - how does one know what version of knative is currently installed? AFAIK we don't have anything from serving that says this

There is actually an annotation in all the yaml files which gets snapped
with the release version.
On Tue, Jun 11, 2019 at 9:04 AM Gregory Haynes<EMAIL_ADDRESS>wrote:

Interesting question - how does one know what version of knative is
currently installed? AFAIK we don't have anything from serving that says
this
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/knative/serving-operator/issues/3?email_source=notifications&email_token=AB4XENZNHX6JYJSPKKOMYB3PZ7EJRA5CNFSM4HUMQVY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXNUS5Y#issuecomment-500910455,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB4XEN4UNG3JCGGRHHRKNWLPZ7EJRANCNFSM4HUMQVYQ
.

--
Evan Anderson<EMAIL_ADDRESS>

There is a label in all the resources, e.g. https://github.com/openshift-knative/knative-serving-operator/blob/v0.6.0/deploy/resources/knative-serving-0.6.0.yaml#L6
But because it was set to "devel" in the 0.5.2 manifest, we used this instead: https://github.com/openshift-knative/knative-serving-operator/blob/master/version/version.go#L1
The operator set KnativeServing.Status.Version to the value in the second file after applying the first file.
So whenever upstream cut a new release, we'd update both files.

Possibly relevant: https://groups.google.com/d/msg/operator-framework/NkC43XyMqWc/iV4NeO0ZBQAJ

I'm curious why we want to fail an upgrade to N+2 or greater. What's the harm in doing so? Just trying to be clear about the justification for this issue.

Personally, I don't think we should fail, but rather follow an upgrade path that's been tested.
I don't think we should allow customers using the Operator to take upgrade paths that are untested and thus potentially unsafe.

It was inspired from the 0.6 -> 0.9 (I think) upgrade. It was a migration from clusterroute to route IIRF. Users needed to migrate from 0.6 -> 0.7 or 0.8 before going to 0.9.

I'd like to be able to say something like this: for any version X of the operator, we'll support upgrades from the last N releases of the operand. I think serving mandates N=4 (where is that doc'd, btw?) but that would mean the 0.9 operator would've needed to be able to update a 0.6 operand to 0.8 before installing 0.9. Is that reasonable?

0.6->.8 and then .9 is probably fine. or if jumping from 0.6 -> 0.12 then have 0.6 -> 0.8 -> 0.10 -> 0.12.

fwiw: jumps by two are tested nowhere. Serving only tests upgrading from N-1.


Fix next() method in Cycler class for Python 3

issue https://github.com/mitsuhiko/jinja2/issues/474

s/Standart/Standart/ but I think you could easily squash those three commits into a single one.


Service provider breaks on RHEL/CentOS 7.3

Description
RHEL 7.3/CentOS 7.3 moves chkconfig from 1.3.x to 1.7.x which has drastically different expectations: instead of on and off, it wants enable and disable:
$ chkconfig --help
getopt: unrecognized option '--help'
Usage: /usr/sbin/chkconfig [--root=path] enable|disable|is-enabled <sysv script name>

This leads Chef to break on any :enable or :disable rule.
Chef Version
chef-12.13.37-1.el7.x86_64
Platform Version
RHEL 7.3
Replication Case
Upgrade... try to :enable a service
Client Output
[2016-12-18T18:06:09-08:00] FATAL: Mixlib::ShellOut::ShellCommandFailed: service[mysvc] (fb_hardware::default line 240) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of /sbin/chkconfig mysvc on ----
STDOUT:
STDERR: Usage: /sbin/chkconfig [--root=path] enable|disable|is-enabled <sysv script name>
---- End output of /sbin/chkconfig 2x_refresh on ----
Ran /sbin/chkconfig mysvc on returned 1

Stacktrace
Not relevant.

so 1.3 only supports on or off, and 1.7 only supports enable and disable? this is gonna be heaps of fun.
Reading further, can we just do systemctl enable foo or systemctl disable foo, even for things that have init scripts? I believe that systemctl does the right thing and just proxies to chkconfig in that case...

Reading further, can we just do systemctl enable foo or systemctl disable foo, even for things that have init scripts? I believe that systemctl does the right thing and just proxies to chkconfig in that case...

I believe, it depends on the verison of systemd and how the distro has integrated it.  Systemd used to have direct support for chkconfig.  After systemd@0f0467e63b0e0688ae9edb1512c1a2637d62ddb4 (systemd v221) it is up to the distributions to provide a helper script systemd-sysv-install which handles enable, disable, etc.

There must be something else going on. There was no such changes in chkconfig in 7.3 (although we did a rebase) and on my machine it works just fine.
enable|disable|is-enabled  would match the interface for the systemd-sysv-install mentioned above, But our implementation in chkconfig does not handle the --root parameter.
https://git.fedorahosted.org/cgit/chkconfig.git/tree/chkconfig.c#n47

Yeah... this is probably related to our backport of systemd and some weird combination of other stuff that hit us only in 7.3. I'm going to close this and if I find there's something chef can/should do I'll open up a follow up.

OK, cause others are likely to run into this...
As of RHEL 7.3, /usr/lib/systemd/systemd-sysv-install is a symlink to ../../..//sbin/chkconfig.
If you are backporting newer systemd per the Facebook repo (https://github.com/facebookincubator/rpm-backports) or the resulting Redhat copr repo (https://copr.fedorainfracloud.org/coprs/jsynacek/systemd-backports-for-centos-7/) then you've probably been dropping off /usr/lib/systemd/systemd-sysv-install - probably with Chef.
Once you upgrade to 7.3, Chef will of course write through this symlink, overwriting chkconfig and the world comes falling down. :)


Fixed the vulnerability message due to an issue with @svgr/webpack

Fixes #11174, #13186, #13227 thanks to https://github.com/facebook/create-react-app/issues/12132#issuecomment-1146858610 by @GlennVialli and @FernandoPerezLara
When running npm audit, this message shows:

And after modifying it to version 8.0.1, it shows:

I think you also need to commit the package-lock otherwise the pipelines will fail. See the ADO logs:

Forgot about it, but why don't package-lock.json be hidden instead?

Hidden? You mean ignored? No it is best practice to update and commit your package-lock.json when you update your package.json to create a consistent and reproducible tree for your node modules.

Workflow fails for some reason

workbox-webpack-plugin dependencies depreciated

An issue with Node JS 14

Fixes #11174, #13186, #13227 thanks to #12132 (comment) by @GlennVialli and @FernandoPerezLara
When running npm audit, this message shows:
And after modifying it to version 8.0.1, it shows:
And after modifying it to version 8.0.1, it shows:

Modifying what exactly?

Hi @dave9123 sorry I don't understand but why did you close this PR? This is a valid fix right?

Nope, another issue with postcss

Gotta do both nth-check and postcss


h :)

@coldfusion39 Hello.
These requirements written in the Python programming language, can use for instagram. thank

Could you please provide more information on this issue? Are you asking if Instagram can be added to geOSINT?

yes. @coldfusion39
instagram is easy to get access token.
fb is complication.
Do you have any file.php example
python get_location.py -i ( id photo or id video ) 2232323
longitude:<PHONE_NUMBER>.23
latitude: 323237273.3232
without "token id"
An friend have said me, EXIF DATA erased.
Is there any opportunity to find location of photo or video of user facebook or of location position.

@coldfusion39 Please. Can you add Instagram OSINT.
thank


Not sort by latency

From: Qing Liu
Sent: Thursday, February 25, 2016 7:26 PM
To: Blair Chen
Subject: help with azurespeed.com
Is that possible to not sort by latency on your azurespeed.com
It is hard to find the azure region when test is running and the sort order is keeping as well.

Fixed


Test for shared object dependencies

Just a simple ldd on the binaries and check there's nothing new.

https://github.com/ambiata/zodiac/pull/103 has a partial fix for this.


Fix day number in template creation message

Just a tiny fix for the console output!
Thanks for creating this template ❤

Good catch, thank you for taking your time to fix this.
Have a happy new year!


About max_steps

hey, I've generated the mesh! thanks.
and I want to ask, is the 3000 max_steps enough for most case? or the more the better? I want to get the best quality

Hello. More max_steps lead to better results, but usually 3000 steps are enough and the most important keys that influences the final mesh results are the choices of loss weights and view weights. I am busy with CVPR in the days, and I will make a detailed and interactive mesh reconstruction tutorial as soon as possible.

the result is amazing! I've generated hundreds of character in one night

 the result is amazing! I've generated hundreds of character in one night

Wow! That's quite cool!

 the result is amazing! I've generated hundreds of character in one night

Hello. Could you please drop me an email, I would like to make friends with you :)

nice, i've send you email


@import rule being (partially) removed => broken CSS

Hey, thanks for your work on this.
Spotted an issue where it's partially removing an @import rule (well, most of it).
I get it why, it's not "used" anywhere in the HTML. But this shouldn't be removed, it's needed for web fonts where <link> is not an option.

Good one, I'll try sort this tonight, can't promise, but should get my Monday

Yup, working fine now, thank you!

phew
👍


Create a Fairing section for the documentation

fixes #590

This change is

Preview https://deploy-preview-599--competent-brattain-de2d6d.netlify.com/docs/fairing/

Thanks @abhi-g! I think we should hold off on adding the section until we have some content to include. Readers may be surprised and even frustrated to find no content, especially as there's no indication of what Fairing is.
FYI I have a meeting later today with @joeliedtke to discuss the Fairing docs. He's the tech writer working with the Fairing team.
I'll apply a hold, to stop this PR from being merged without direct intention. Please do cancel the hold if you disagree. :)
/hold

Sounds reasonable. I created a bunch of issues in the website repo to add
various documentation for Fairing.
On Thu, Apr 4, 2019 at 9:26 PM Sarah Maddox<EMAIL_ADDRESS>wrote:

Thanks @abhi-g https://github.com/abhi-g! I think we should hold off on
adding the section until we have some content to include. Readers may be
surprised and even frustrated to find no content, especially as there's no
indication of what Fairing is.
FYI I have a meeting later today with @joeliedtke
https://github.com/joeliedtke to discuss the Fairing docs. He's the
tech writer working with the Fairing team.
I'll apply a hold, to stop this PR from being merged without direct
intention. Please do cancel the hold if you disagree. :)
/hold
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubeflow/website/pull/599#issuecomment-480144022, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALOqZrC2gUoziUIjxpaQwgttqvIMKpD_ks5vdtBcgaJpZM4cdwdz
.

We now have a candidate page that will appear in this section. See PR https://github.com/kubeflow/website/pull/603
I'll LGTM this PR and remove the hold, so that you can approve and merge as soon as the above PR is approved. :)

/hold cancel
/lgtm

Thanks.
On Fri, Apr 5, 2019 at 8:50 PM Sarah Maddox<EMAIL_ADDRESS>wrote:

/hold cancel
/lgtm
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubeflow/website/pull/599#issuecomment-480471485, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALOqZhGm1xSQCvVQKZ0JXb-3KsEAngimks5veBl-gaJpZM4cdwdz
.

/hold cancel
/approve


Braft-editor wont work in SSR webpack application?

Hi there,
braft editor wont really render into my application, does this plugin supported ssr application?
Or there is alternative that i can do in the webpack to render this plugin?

Hi，I don't think it's an option to render an rich text editor on the server side, it's unnecessary, because it's not a component which only contains static contents, and the BraftEditor component uses some methods under the window object, such as getBoundingRectClient, to make sure the dropdown controls showing at a correct position.
You can use the React No SSR to prevent components from rendering on the server side.

@margox I was thinking to use this amazing editor with the readOnly flag of draftJS to actually render the content (without showing the controls) so that I feel way more secure then rendering HTML since users have the freedom to use the editor on the site.
Although with this issue it prevents me to render the editor on the server side.
Even though the library does use of getBoundingRectClient it would be great if it could be wrapped around an if statement to check the existence of window
if (typeof window !== "undefined") {
   window. getBoundingRectClient()
}

Any suggestions on this?

@fameoflight Hi, I just published a new version of braft-editor(v2.3.0), you may take a look, thanks so much for using this project, :)

"braft-editor": "^2.3.9", 一樣發生錯誤 :(

"braft-editor": "^2.3.9", 一樣發生錯誤 :(

// This is the problem that I used in nextjs project
// 这个是我在nextjs项目中使用出现的问题
import dynamic from 'next/dynamic'
// components/edit is Your custom components
// 这里是你自定义的组件，这个组件中是那个出现window或document is not defined
const EditWithNoSSR = dynamic(import('components/edit'), {
ssr: false
})

// This is the problem that I used in nextjs project
// 这个是我在nextjs项目中使用出现的问题
import dynamic from 'next/dynamic'
// components/edit is Your custom components
// 这里是你自定义的组件，这个组件中是那个出现window或document is not defined
const EditWithNoSSR = dynamic(import('components/edit'), {
ssr: false
})

dynamic(() => import("../editor"), { ssr: false })


Prisma deploy schema generation post-deploy hook failing cause of 2 versions of GraphQL using both graphql-yoga & graphqlgen

Description
prisma generate called as a post-deploy hook by prisma deploy fails (see screenshot below)
Steps to reproduce
Having this package.json :
{
  "name": "prisma-typescript",
  "version": "0.1.0",
  "author": "Kevin Marrec",
  "private": true,
  "scripts": {
    "lint": "tslint --project .",
    "lint:fix": "tslint --project . --fix",
    "start": "nodemon src/index.ts",
    "debug": "nodemon --inspect src/index.ts"
  },
  "nodemonConfig": {
    "exec": "ts-node -r dotenv/config",
    "watch": "src",
    "ext": "ts,graphql"
  },
  "dependencies": {
    "bcrypt": "^3.0.2",
    "graphql-yoga": "^1.16.7",
    "jsonwebtoken": "^8.3.0",
    "prisma-client-lib": "^1.18.1"
  },
  "devDependencies": {
    "dotenv": "^6.0.0",
    "graphqlgen": "^0.2.2",
    "nodemon": "^1.18.4",
    "prisma": "^1.18.1",
    "ts-node": "^7.0.1",
    "tslint": "^5.11.0",
    "tslint-config-standard": "^8.0.1",
    "typescript": "^3.1.3"
  }
}

Expected results
No errors / Schema generated correctly
Actual results
It seems there is a bug having 2 versions of graphql from both graphql-yoga & graphqlgen during prisma generation.

yarn.lock (only the weird part with 2 different graphql version definitions) :
<EMAIL_ADDRESS>  version "1.16.7"
  resolved "https://registry.yarnpkg.com/graphql-yoga/-/graphql-yoga-1.16.7.tgz#05bdfadf9a4623b0409bee3c5b75b7b3f7249e6f"
  integrity sha512-N82SmBpKyDD7GXXo2NbVBMPffbxFWD+YOf/Vqx3Kujj/hNOX+0s/7G+EPp4TgJZqHQjcOw5TqQ0kOANO8w6Kmg==
  dependencies:
    "@types/cors" "^2.8.4"
    "@types/express" "^4.11.1"
    "@types/graphql" "^14.0.0"
    "@types/graphql-deduplicator" "^2.0.0"
    "@types/zen-observable" "^0.5.3"
    apollo-server-express "^1.3.6"
    apollo-server-lambda "1.3.6"
    apollo-upload-server "^5.0.0"
    aws-lambda "^0.1.2"
    body-parser-graphql "1.1.0"
    cors "^2.8.4"
    express "^4.16.3"
    graphql "^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0"
    graphql-deduplicator "^2.0.1"
    graphql-import "^0.7.0"
    graphql-middleware "1.7.7"
    graphql-playground-middleware-express "1.7.6"
    graphql-playground-middleware-lambda "1.7.6"
    graphql-subscriptions "^0.5.8"
    graphql-tools "^4.0.0"
    subscriptions-transport-ws "^0.9.8"

<EMAIL_ADDRESS>  version "0.13.2"
  resolved "https://registry.yarnpkg.com/graphql/-/graphql-0.13.2.tgz#4c740ae3c222823e7004096f832e7b93b2108270"
  integrity sha512-QZ5BL8ZO/B20VA8APauGBg3GyEgZ19eduvpLWoq5x7gMmWnHoy8rlQWPLmWgFvo1yNgjSEFMesmS4R6pPr7xog==
  dependencies:
    iterall "^1.2.1"

<EMAIL_ADDRESS>|| ^0.12.0 || ^0.13.0 || ^14.0.0"<EMAIL_ADDRESS>|| ^14.0.0"<EMAIL_ADDRESS>  version "14.0.2"
  resolved "https://registry.yarnpkg.com/graphql/-/graphql-14.0.2.tgz#7dded337a4c3fd2d075692323384034b357f5650"
  integrity sha512-gUC4YYsaiSJT1h40krG3J+USGlwhzNTXSb4IOZljn9ag5Tj+RkoXrWp+Kh7WyE3t1NCfab5kzCuxBIvOMERMXw==
  dependencies:
    iterall "^1.2.2"

<EMAIL_ADDRESS>  version "0.2.5"
  resolved "https://registry.yarnpkg.com/graphqlgen-json-schema/-/graphqlgen-json-schema-0.2.5.tgz#a458c55ecb99926b3ee8cf4eacb97915b7085c9a"
  integrity sha512-p5Oq0aigusiSYdpuGwST7mfHk91hrzL27HaOqBW2Y7Y0GgiMH7TJYa/WIqf95uH8bSyRzvBzawTQF7/WqnymPQ==

<EMAIL_ADDRESS>  version "0.2.6"
  resolved "https://registry.yarnpkg.com/graphqlgen/-/graphqlgen-0.2.6.tgz#6adef254ca8ad9692ae4b5ce418fc8ab4889b4fd"
  integrity sha512-Vyd/sR6DvGlXjXgMqziSmmn0421pOENYUkIbryUo+JR4ZpsyrLwz7wITO+GmrwyJx7dVb7ZGYg1aeDV+rS0TvQ==
  dependencies:
    ajv "^6.5.4"
    camelcase "5.0.0"
    chalk "2.4.1"
    graphql "^0.13.0 || ^14.0.0"
    graphql-import "0.7.1"
    graphqlgen-json-schema "0.2.5"
    js-yaml "3.12.0"
    mkdirp "0.5.1"
    prettier "1.14.3"
    reason "3.3.4"
    rimraf "2.6.2"
    typescript "3.1.3"
    yargs "12.0.2"

Versions

graphql-yoga: 1.16.7
graphqlgen: 0.2.6

Can you confirm this also happens when running prisma generate manually (without running prisma deploy)?

@schickling It was happening, yes.
The problem is that prisma-lib-core (dependency of prisma) use<EMAIL_ADDRESS>and I had prisma as devDependecy.
I fixed it removing prisma dependency and install it globally but I would want to find a way to have it as a devDependency and use yarn prisma.
Somtimes you just don't have access to sudo privileges so you can't sudo yarn global add prisma to have the prisma binary.

Thanks @kevinmarrec for the information! That means for us that we have to upgrade the complete prisma cli to graphql@14, which is a bigger tasks, as there are many dependencies.
We want to tackle this next week!
One alternative workaround right now could be npx though :) So by using npx prisma in your package.json script, you could also circumvent the global sudo stuff.

@timsuchanek It will be fixed in Prisma 1.21 ?
https://github.com/prisma/prisma/releases/tag/1.21.0-beta
https://github.com/prisma/prisma/commit/8eb1623ad7ac2f676bcc029b933884b778fa3d28

Updating to last Prisma version (at the time I write 1.20.1) fixes this issue.


Support node_id

I did not want to support this, because I desperately did not want to have to add 4 bytes to every node. Unfortunately, in order to support all of the functionality of CRuby, this is a requirement. Hopefully we can mitigate this memory by reducing the size of our location fields at some point.
Fixes https://github.com/ruby/prism/issues/2383.

Please take a look at https://github.com/ruby/prism/issues/2383#issuecomment-1934920712, I think that would be one way to have this functionality without degrading memory footprint.

Closing for now.


Error":"missing required startup taint, karpenter.sh/unregistered" in the karpenter logs.

Description
Observed Behavior:
I have startup taints in my nodepool but I still see this error
{"level":"ERROR","time":"2024-09-04T20:20:36.965Z","logger":"controller","message":"Reconciler error","commit":"62a726c","controller":"nodeclaim.lifecycle","controllerGroup":"karpenter.sh","controllerKind":"NodeClaim","NodeClaim":{"name":"deployment-rqczg"},"namespace":"","name":"deployment-rqczg","reconcileID":"db521016-5e44-4c77-9352-f07bbb44197d","error":"missing required startup taint, karpenter.sh/unregistered"}
Expected Behavior:
This error should not coming up and the start up taints should be applied.
Reproduction Steps (Please include YAML):
apiVersion: karpenter.sh/v1
kind: NodePool
metadata:
name: deployment
spec:
template:
metadata:
labels:
type: DeploymentRunners
spec:
expireAfter: 19m
terminationGracePeriod: 20m
requirements:
- key: kubernetes.io/arch
operator: In
values: ["amd64"]
- key: kubernetes.io/os
operator: In
values: ["linux"]
- key: karpenter.sh/capacity-type
operator: In
values: ["on-demand"]
- key: karpenter.k8s.aws/instance-category
operator: In
values: ["c", "m", "r"]
- key: karpenter.k8s.aws/instance-generation
operator: Gt
values: ["2"]
- key: node.kubernetes.io/instance-type
operator: Exists
minValues: 10
nodeClassRef:
group: karpenter.k8s.aws
kind: EC2NodeClass
name: default
taints:
- key: "deployment_runners_workload"
value: "true"
effect: NoSchedule
startupTaints:
- key: karpenter.sh/unregistered
effect: NoSchedule
limits:
cpu: 1000
memory: 1000Gi
disruption:
consolidationPolicy: WhenEmptyOrUnderutilized
consolidateAfter: 20m
Versions:

Chart Version: v1.1.0

The startupTaints in nodepool only works after node is registered which is added by karpenter core controller. The karpenter.sh/unregistered should be added by kubelet not the karpenter controller. You might check how the aws provider pr https://github.com/aws/karpenter-provider-aws/pull/6388/files.

No, I’m exploring about karpenter for my eks cluster that hosts  GH runners. I’m using custom AMI. Could you please assist on how can I add the required taint karpenter.sh/unregistered via user data ?

No, I’m exploring about karpenter for my eks cluster that hosts GH runners. I’m using custom AMI. Could you please assist on how can I add the required taint karpenter.sh/unregistered via user data ?

If you are using karpenter-aws-provider, the provider will do these things. If the aws provider doesn't do this, I think you should add an issue in https://github.com/aws/karpenter-provider-aws not here.

From the karpenter upgrade guide- “ Karpenter now adds a karpenter.sh/unregistered:NoExecute taint to nodes in injected UserData when using alias in AMISelectorTerms or non-Custom AMIFamily. When using amiFamily: Custom, users will need to add this taint into their UserData, where Karpenter will automatically remove it when provisioning nodes”. Would be helpful if you could elaborate on how taints can be added to user data .

Here is more documentation on adding taints: https://karpenter.sh/docs/concepts/nodeclasses/#specuserdata

So I am having exactly the same issue - however I have added this as part of my UserData script:
apiVersion: karpenter.k8s.aws/v1
    kind: EC2NodeClass
    metadata:
      name: default
    spec:
      amiFamily: Custom
      userData: |
        #!/bin/bash
        set -e
        B64_CLUSTER_CA=${module.eks.cluster_certificate_authority_data}
        API_SERVER_URL=${module.eks.cluster_endpoint}
        /etc/eks/bootstrap.sh ${module.eks.cluster_name} --b64-cluster-ca $B64_CLUSTER_CA --apiserver-endpoint $API_SERVER_URL \
          --kubelet-extra-args='--register-with-taints="karpenter.sh/unregistered:NoExecute"'

I can see the taint when the node is initialised, and then it is removed, however the nodeclaim still says False for ready with the same error:
  Conditions:
    Last Transition Time:  2024-11-15T17:10:23Z
    Message:
    Reason:                Initialized
    Status:                True
    Type:                  Initialized
    Last Transition Time:  2024-11-15T17:08:57Z
    Message:
    Reason:                Launched
    Status:                True
    Type:                  Launched
    Last Transition Time:  2024-11-15T17:10:23Z
    Message:               Registered=False
    Reason:                UnhealthyDependents
    Status:                False
    Type:                  Ready
    Last Transition Time:  2024-11-15T17:10:00Z
    Message:               Invariant violated, karpenter.sh/unregistered taint must be present on Karpenter-managed nodes
    Reason:                UnregisteredTaintNotFound
    Status:                False
    Type:                  Registered
  Image ID:                ami-01a816a693a50ab5c
  Provider ID:             aws:///eu-west-2a/i-0ec526c836ff8574f
Events:
  Type    Reason             Age    From       Message
  ----    ------             ----   ----       -------
  Normal  Launched           7m19s  karpenter  Status condition transitioned, Type: Launched, Status: Unknown -> True, Reason: Launched
  Normal  DisruptionBlocked  7m18s  karpenter  Cannot disrupt NodeClaim: state node doesn't contain both a node and a nodeclaim
  Normal  Ready              6m16s  karpenter  Status condition transitioned, Type: Ready, Status: Unknown -> False, Reason: UnhealthyDependents, Message: Initialized=Unknown, Registered
=False
  Normal  Registered         6m16s  karpenter  Status condition transitioned, Type: Registered, Status: Unknown -> False, Reason: UnregisteredTaintNotFound, Message: Invariant violated,
karpenter.sh/unregistered taint must be present on Karpenter-managed nodes
  Normal  Initialized        5m52s  karpenter  Status condition transitioned, Type: Initialized, Status: Unknown -> True, Reason: Initialized
  Normal  Unconsolidatable   5m48s  karpenter  NodePool "default" has consolidation disabled

I have been trying this with version 1.0.7 and 1.0.8...

have raised this under #1828 as I believe it to be seperate


Return some method to understand the Checkout version before initialization

Is your feature request related to a problem? Please describe.
Want to know version of the SDK before initialising it.
Describe the solution you'd like
Add Some static variable to the export.

Hey @oleksii-loian .
What is the use-case for this? You know the version since you are integrating directly with it, no?

Use case is to send to Product Back-end version. Then product back-end will decide what version of Adyen will be using.

@oleksii-loian - can you elaborate on what exactly it is that you want?


How can I increase the speed of the render to react native camera?

I use the react navigation module for routing, when I go to screen of module react native camera fps drops to 2, but when the module is loaded, fps 60. How to solve this problem?
THANKS
IT IS VERY IMPORTANT !!

The only real ways to somewhat solve it that I know of are to either, a) preload the component you're switching to and then show the camera with a state toggle, or b) get faster hardware.
Initialising the camera (whether it's the native camera built into the OS or through an abstracted layer like RN with this library) is inherently expensive and will consume a lot of your resources.
Also, sidenote: ALL-CAPS and exclamation marks make it much less likely for people to want to help you. Especially when you already have an existing issue for the problem mentioned on the repo you're asking on.

Please open a new issue if you are still experiencing these issues with the newest version of RNCamera.


fix: use alias for schemas

Hi :wave:
This adds an alias for generated schemas. There's two reasons:

we can't use #build alias in nitro types
it can be a DX improvement so users don't have to import from a long path

Would be nice to have a single alias for everything or to add auto-import maybe ?

Thank you 💚


Added CyberGhost VPN

CyberGhost VPN is a free and simple Internet security, access to content from all over the world.
Main URL: http://www.cyberghostvpn.com/

Are you sure this is :freemium and not :gratis?

a free app to access a paid service is still :gratis, not :freemium

My bad. Updated license.

Thank you, could you please squash your commits?

Update it and CI pass.


Add User-Exit in zcl_abapgit_oo_serializer methods

Method serialize_abap_clif_source in zcl_abapgit_oo_serializer contains a user exit (custom_serialize_abap_clif) that enables me to perform a custom Pretty print different from the one I use on my system (cf. https://gist.github.com/mbtools/71aa345a8ccb8f375568f9f337569154).
Such a User Exit is missing in the following methods:

serialize_locals_def
serialize_locals_imp
serialize_macros
serialize_testclasses

Thanks,

it should be a "code post-processing" exit and also available for object types like prog, fugr, type, and others that have embedded code.

user exit referenced = https://docs.abapgit.org/ref-exits.html#custom_serialize_abap_clif
Suggest a new exit SERIALIZE_POSTPROCESS, which can be used to change everything

Ideally, user exit execution could be restricted to push. (My use case : Code pushed to public git repo should be formatted but code pulled from other repo (eg. abap2xlsx) should be copied as is, in order to avoid false flag diff after import).


{Bp-13895} board/arm/nrf52: fix use up_interrupt_context to is_nesting_interrupt

Summary
The case want to determine if a interrupt with higher priority the interrupt preemption occurred,
but up_interrupt_context indicates that we self inside interrupt/handedr mode.
As we previously did not handle the ramvector interrupt correctly, after update breaked the case.
We should use a more clear private function is_nesting_interrupt.
https://github.com/apache/nuttx/issues/13831
Impact
RELEASE
Testing
CI

[Experimental Bot, please feedback here]
The PR summary doesn't fully meet NuttX requirements. Here's why and how to improve it:
What's Missing/Needs Improvement:

Insufficient Detail in "Summary":

Why is the change necessary?  The summary mentions a problem with determining interrupt preemption and a broken case.  It needs to explicitly state the negative impact of these issues (e.g., system instability, unexpected behavior in specific scenarios).
What functional part is changed? Be specific. Mention the exact functions, modules, or subsystems modified (e.g., interrupt handling subsystem, up_interrupt_context function,  RAM vector handling).
How does it work (at a high level)? Briefly explain the solution's logic (e.g., "Introduced is_nesting_interrupt to accurately track interrupt nesting by...").

Impact Section:

"RELEASE" is not informative. You must elaborate on all "YES" answers in the Impact section. Briefly explain each potential impact:

Impact on existing features?  Does this fix a bug in an existing feature? Does it change the behavior of an existing feature?
Impact on documentation? Since a new function is added, documentation is likely required. State that you've added it.
Anything else? Think about potential edge cases or subtle interactions this change might introduce.

Testing Section:

"CI" is not enough.  While CI is important, you MUST provide details about your local testing:

Specific host OS and versions: e.g., "Ubuntu 20.04, GCC 9.4.0"
Target details: e.g., "QEMU-based RISC-V simulation, stm32f4discovery:nsh"
Testing logs snippets: Include relevant portions that demonstrate the issue before and the fix after your change.

Example of an Improved Summary:
## Summary

This PR addresses an issue where interrupt preemption detection was unreliable, leading to potential system instability when nested interrupts occurred.  Specifically, the `up_interrupt_context` function was incorrectly indicating interrupt nesting in certain scenarios involving RAM vector handling.

The fix introduces a new private function, `is_nesting_interrupt`, to accurately track interrupt nesting based on [explain the mechanism]. This change primarily affects the interrupt handling subsystem within the NuttX kernel.

This addresses issue [#13831](https://github.com/apache/nuttx/issues/13831).

## Impact

* **Is existing feature changed?** YES - This fixes a bug in the interrupt handling system that could lead to incorrect behavior in interrupt handlers.
* **Impact on documentation?** YES - Documentation has been added for the new `is_nesting_interrupt` function.
* **Anything else to consider?**  [Mention any potential edge cases or areas where further testing might be beneficial].

## Testing

I confirm that changes are verified on the following setups:

* **Build Host:** Ubuntu 20.04, GCC 9.4.0
* **Target:**
    * QEMU-based RISC-V simulation, `qemu-rv32:nsh` config
    * STM32F4Discovery board, `stm32f4discovery:nsh` config

**Testing Logs (Before Change):**

[Include relevant snippets showing the incorrect behavior]

**Testing Logs (After Change):**

[Include relevant snippets demonstrating the fix]

Remember: Clear, concise, and detailed PRs are crucial for maintainers to review and merge your code quickly!


Rao

Description
Bittensor-RAO

This has to go in first : https://github.com/opentensor/subtensor/pull/638


Merge master to live

Docs Build status updates of commit 644df65:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

office-365-management-api/office-365-management-activity-api-schema.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


How to put image URL in image view

How to put image url instead of image. in custom cell image view

We are discussing it right now on stackoverflow here let me know if you have more questions an I will try to see what I can do to help.

Hello everyone!
I'm sorry to inform the community that I'm officially deprecating this project. 😢 Please read my blog post for details:
http://www.jessesquires.com/blog/officially-deprecating-jsqmessagesviewcontroller/
Thus, I'm closing all issues and pull requests and making the necessary updates to formally deprecate the library. I'm sorry if this is unexpected or disappointing. Please know that this was an extremely difficult decision to make. I'd like to thank everyone here for contributing and making this project so great. It was a fun 4 years. 😊
Thanks for understanding,
— jsq


Method DATE_TO_EXCEL_STRING: Date field = space

Sometimes you get date field empty - containing only space(s) (not zeroes '00000000'). This value treated as not initial in ABAP for fields typed as D. This resulted in passing by
CHECK ip_value IS NOT INITIAL
and calculating
lv_date_diff = ip_value - c_excel_baseline_date + 1.
which returns "-693596". In EXCEL this displayed as #########...

Here's little more details about problem.
Test code:
REPORT  ztest_a2x.
CONSTANTS: gc_save_file_name TYPE string VALUE 'ZTEST_A2X.XLSX'.
INCLUDE zdemo_excel_outputopt_incl.
START-OF-SELECTION.
  PERFORM main.
*&---------------------------------------------------------------------*
*&      Form  main
*&---------------------------------------------------------------------*
FORM main.
  DATA:
    lo_excel         TYPE REF TO zcl_excel,
    lo_worksheet     TYPE REF TO zcl_excel_worksheet,
    lo_hyperlink     TYPE REF TO zcl_excel_hyperlink,
    column_dimension TYPE REF TO zcl_excel_worksheet_columndime,
    lt_data TYPE TABLE OF anla.
*--------------------------------------------------------------------*
  SELECT * INTO TABLE lt_data
    FROM anla.
  CREATE OBJECT lo_excel.
  lo_worksheet = lo_excel->get_active_worksheet( ).
  lo_worksheet->bind_table( ip_table = lt_data ).
  lcl_output=>output(
    cl_excel            = lo_excel
    iv_writerclass_name = 'ZCL_EXCEL_WRITER_HUGE_FILE'
  ).
ENDFORM.                    "main

Debug data:

Result:

This bug happens because IP_VALUE typed as D actually IS NOT INITIAL. Because for type D initial value is '00000000'.

Result after implementing this fix in method DATE_TO_EXCEL_STRING:

Thank you for the fix


The new placeholder are not correctly showed in wiki

When I try to use the newly updated placeholder in action bar, it not work.
Only the old one in eCloud works.
Then I try to use %eternalnature_temperature_color%, it works.
Seem like a typo :0

Fixed typo in wiki. This was a mistake on my side forgetting to add the identifier at the start of them. For version 2.1.1 the identifier is still eternalnature but future versions will use the identifier nature to slightly shorten the placeholders.


"torch.cuda.OutOfMemoryError: CUDA out of memory" when deploy LLM with TGI in Kubernetes cluster

When deploy the LLM with TGI in k8s cluster with the pod  like below:
apiVersion: v1
kind: Pod
metadata:
name: text-generation-inference
labels:
run: text-generation-inference
spec:
containers:
- name: text-generation-inference
image: ghcr.io/huggingface/text-generation-inference:latest
env:
- name: RUST_BACKTRACE
value: "1"
command:
- "text-generation-launcher"
- "--model-id"
- "macadeliccc/laser-dolphin-mixtral-2x7b-dpo"
- "--num-shard"
- "1"
ports:
- containerPort: 80
name: http
volumeMounts:
- name: falcon-40b-instruct
mountPath: /data
- name: shm
mountPath: /dev/shm
volumes:
- name: falcon-40b-instruct
persistentVolumeClaim:
claimName: falcon-40b-instruct
- name: shm
emptyDir:
medium: Memory
sizeLimit: 1Gi
restartPolicy: Never
Got the error log in the pod as below:
2024-03-31T18:30:09.175228Z  INFO text_generation_launcher: Args { model_id: "macadeliccc/laser-dolphin-mixtral-2x7b-dpo", revision: None, validation_workers: 2, sharded: None, num_shard: Some(1), quantize: None, speculate: None, dtype: None, trust_remote_code: false, max_concurrent_requests: 128, max_best_of: 2, max_stop_sequences: 4, max_top_n_tokens: 5, max_input_length: 1024, max_total_tokens: 2048, waiting_served_ratio: 1.2, max_batch_prefill_tokens: 4096, max_batch_total_tokens: None, max_waiting_tokens: 20, max_batch_size: None, enable_cuda_graphs: false, hostname: "text-generation-inference", port: 80, shard_uds_path: "/tmp/text-generation-server", master_addr: "localhost", master_port: 29500, huggingface_hub_cache: Some("/data"), weights_cache_override: None, disable_custom_kernels: false, cuda_memory_fraction: 1.0, rope_scaling: None, rope_factor: None, json_output: false, otlp_endpoint: None, cors_allow_origin: [], watermark_gamma: None, watermark_delta: None, ngrok: false, ngrok_authtoken: None, ngrok_edge: None, tokenizer_config_path: None, disable_grammar_support: false, env: false }
2024-03-31T18:30:09.175390Z  INFO download: text_generation_launcher: Starting download process.
2024-03-31T18:30:12.843982Z  INFO text_generation_launcher: Files are already present on the host. Skipping download.
2024-03-31T18:30:13.781674Z  INFO download: text_generation_launcher: Successfully downloaded weights.
2024-03-31T18:30:13.781977Z  INFO shard-manager: text_generation_launcher: Starting shard rank=0
2024-03-31T18:30:18.238592Z  WARN text_generation_launcher: Unable to use Flash Attention V2: GPU with CUDA capability 7 5 is not supported for Flash Attention V2
2024-03-31T18:30:23.795409Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2024-03-31T18:30:33.806809Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2024-03-31T18:30:43.817973Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2024-03-31T18:30:53.829077Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2024-03-31T18:31:03.840976Z  INFO shard-manager: text_generation_launcher: Waiting for shard to be ready... rank=0
2024-03-31T18:31:04.932785Z ERROR text_generation_launcher: Error when initializing model
Traceback (most recent call last):
File "/opt/conda/bin/text-generation-server", line 8, in
sys.exit(app())
File "/opt/conda/lib/python3.10/site-packages/typer/main.py", line 311, in call
return get_command(self)(*args, **kwargs)
File "/opt/conda/lib/python3.10/site-packages/click/core.py", line 1157, in call
return self.main(*args, **kwargs)
File "/opt/conda/lib/python3.10/site-packages/typer/core.py", line 778, in main
return _main(
File "/opt/conda/lib/python3.10/site-packages/typer/core.py", line 216, in _main
rv = self.invoke(ctx)
File "/opt/conda/lib/python3.10/site-packages/click/core.py", line 1688, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/opt/conda/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/opt/conda/lib/python3.10/site-packages/click/core.py", line 783, in invoke
return __callback(*args, **kwargs)
File "/opt/conda/lib/python3.10/site-packages/typer/main.py", line 683, in wrapper
return callback(**use_params)  # type: ignore
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/cli.py", line 89, in serve
server.serve(
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/server.py", line 235, in serve
asyncio.run(
File "/opt/conda/lib/python3.10/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/opt/conda/lib/python3.10/asyncio/base_events.py", line 636, in run_until_complete
self.run_forever()
File "/opt/conda/lib/python3.10/asyncio/base_events.py", line 603, in run_forever
self._run_once()
File "/opt/conda/lib/python3.10/asyncio/base_events.py", line 1909, in _run_once
handle._run()
File "/opt/conda/lib/python3.10/asyncio/events.py", line 80, in _run
self._context.run(self._callback, *self._args)

File "/opt/conda/lib/python3.10/site-packages/text_generation_server/server.py", line 196, in serve_inner
model = get_model(
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/init.py", line 472, in get_model
return FlashMixtral(
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/flash_mixtral.py", line 22, in init
super(FlashMixtral, self).init(
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/flash_mistral.py", line 356, in init
model = model_cls(config, weights)
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/custom_modeling/flash_mixtral_modeling.py", line 814, in init
self.model = MixtralModel(config, weights)
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/custom_modeling/flash_mixtral_modeling.py", line 751, in init
[
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/custom_modeling/flash_mixtral_modeling.py", line 752, in
MixtralLayer(
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/custom_modeling/flash_mixtral_modeling.py", line 691, in init
self.moe = moe_cls(f"{prefix}.block_sparse_moe", config, weights)
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/custom_modeling/flash_mixtral_modeling.py", line 362, in init
self.w3 = _load_experts(config, f"{prefix}.experts", "w3", weights)
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/custom_modeling/flash_mixtral_modeling.py", line 184, in _load_experts
tensor[i * block_size : (i + 1) * block_size] = expert_slice.to(
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 112.00 MiB. GPU 0 has a total capacty of 14.58 GiB of which 81.56 MiB is free. Process 166095 has 14.50 GiB memory in use. Of the allocated memory 14.20 GiB is allocated by PyTorch, and 189.40 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

2024-03-31T18:31:06.544787Z ERROR shard-manager: text_generation_launcher: Shard complete standard error output:
Traceback (most recent call last):
File "/opt/conda/bin/text-generation-server", line 8, in
sys.exit(app())
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/cli.py", line 89, in serve
server.serve(
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/server.py", line 235, in serve
asyncio.run(
File "/opt/conda/lib/python3.10/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/opt/conda/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
return future.result()
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/server.py", line 196, in serve_inner
model = get_model(
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/init.py", line 472, in get_model
return FlashMixtral(
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/flash_mixtral.py", line 22, in init
super(FlashMixtral, self).init(
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/flash_mistral.py", line 356, in init
model = model_cls(config, weights)
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/custom_modeling/flash_mixtral_modeling.py", line 814, in init
self.model = MixtralModel(config, weights)
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/custom_modeling/flash_mixtral_modeling.py", line 751, in init
[
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/custom_modeling/flash_mixtral_modeling.py", line 752, in
MixtralLayer(
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/custom_modeling/flash_mixtral_modeling.py", line 691, in init
self.moe = moe_cls(f"{prefix}.block_sparse_moe", config, weights)
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/custom_modeling/flash_mixtral_modeling.py", line 362, in init
self.w3 = _load_experts(config, f"{prefix}.experts", "w3", weights)
File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/custom_modeling/flash_mixtral_modeling.py", line 184, in _load_experts
tensor[i * block_size : (i + 1) * block_size] = expert_slice.to(
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 112.00 MiB. GPU 0 has a total capacty of 14.58 GiB of which 81.56 MiB is free. Process 166095 has 14.50 GiB memory in use. Of the allocated memory 14.20 GiB is allocated by PyTorch, and 189.40 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
rank=0
2024-03-31T18:31:06.635158Z ERROR text_generation_launcher: Shard 0 failed to start
2024-03-31T18:31:06.635190Z  INFO text_generation_launcher: Shutting down shards
Error: ShardCannotStart
Someone has seen similar issue?  I am quite new in the area, and can not find the root cause of the issue.

What's the GPU ?
You are using compute_cap 7.5 so I'll guess T4. T4 simply don't have enough vram to run this model out of the box, you can try using quantization maybe
macadeliccc/laser-dolphin-mixtral-2x7b-dpo


Fix runtime errors new to Python 3.8

Don't change dict while iterating
Use time.process_time instead of time.clock for Python 3

Fixes #11

Codecov Report

Merging #12 into master will decrease coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
- Coverage   85.23%   85.19%   -0.04%
==========================================
  Files          39       39
  Lines        2634     2635       +1
  Branches      277      277
==========================================
  Hits         2245     2245
  Misses        335      335
- Partials       54       55       +1

Impacted Files
Coverage Δ

blazeutils/containers.py
100% <100%> (ø)
:arrow_up:

blazeutils/strings.py
77.27% <100%> (ø)
:arrow_up:

blazeutils/tests/test_importing.py
96.55% <0%> (-3.45%)
:arrow_down:

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 c944763...1432fbb. Read the comment docs.


Right side drawer height and position, animation customization

I can set width with [drawerViewController setMaximumRightDrawerWidth:200.0f], but how to set height and starting point with coordinate x and y, since I want right side drawer is between top nav bar and bottom tool bar, it also just covers on center view transparently rather than move center view to left side.
Thanks in advance for any idea.

I mean the side menu overlay the home page, like:
https://github.com/evnaz/ENSwiftSideMenu


Fix encoding and nodata issues

Resolve #58
@giswqs, would you be able to test?

It works like a charm! Many thanks


Synced with ps2sdk, corrected some logic

Pull Request checklist
Note: these are not necessarily requirements

[ ] I reformatted the code with clang-format
[ ] I checked to make sure my submission worked
[x] I am the author of submission or have permission from the original author
[x] Requires update of the PS2SDK
[ ] Requires update of the gsKit
[ ] Others (please specify below)

Pull Request description
I just was trying to unify some things - and make them as it is in mainstream ps2sdk. I also fixed some errors which capture modern toolchain. there are still many things to do but at least for now opl can be compiled on modern gcc.

@sp193, with this commit after update the PS2SDK no game works!
At least with the internal HDD all the games got a BSOD.
Best regards.

At least with the internal HDD all the games got a BSOD.
Best regards.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ifcaro/Open-PS2-Loader/pull/188#issuecomment-459963155,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAl8SLNnJ8aCS_2bhPnp3tpCiy_Z2O_Dks5vJYshgaJpZM4aaHno
.

I think the problem is with UDNL. I didn't realize that the pointers were not pointers to bytes, so the new code is not very compatible with the original logic.
I'll issue a patch soon.


Autocomplete Select component does populate with the value that has been selected if enter is pressed

OS - MacOS High Sierra
Node - 8.11.2
Vuesax - 3.1.1
Browser - Chrome 66.0.3359.18
Package Manager - npm
If you begin typing the beginning of an item in the component and try to hit enter, the field will not populate with the input that had been highlighted.
https://lusaxweb.github.io/vuesax/components/selects.html#autocomplete

Thank you very much for the message to review the problem most likely is that there is no option to be selected at the previous value do you think it would be good functionality or would it be better otherwise?

I think it would be good functionality. Maybe I am doing something incorrectly however I tried it in Safari as well and got the same result. I was not expecting to select square when I actually meant to select rectangle in the recording attached to this comment. I hope this helps.

Thank you very much I understand better I will fix it and I will advise you to check if it works as it should :+1:

Ready and the update was completely complete thanks for the contribution please check if it works as it should thanks


fix Channel.close, Connection._connect

Channel.close, When closing the channel, the connection has been closed and the channel status has not been closed

Connection._connect, Blocking due to network or service issues when creating a connection

@gmr Can you please review this request?


Hello World! - Jinlu Zhang's Blog

http://jinluzhang.site/2020/02/16/hello-world.html
Hi everyone, welcome come to my blog website.:wink:I start this blog website by myself and Powered by Jekyll & TeXt Theme. Thanks for the authorIf you li...

test


FEAT: docker compose support

add docker-compose.yml file

Hi, thanks for your contribution, have you tested locally?

Hi, thanks for your contribution, have you tested locally?

yes, it runs successfully in windows with Docker Desktop


API Docs correction

https://github.com/orbitdb/orbit-db/blob/main/API.md#orbitdbopenaddress-options
The API definition for orbit.open() says

create (boolean): Whether or not to create the database if a valid OrbitDB address is not provided. (Default: false)

And also says

You can use  orbitdb.feed(address, options) instead of orbitdb.open(address, { type: 'feed', ...options })

However, inspecting the code of orbit.keyvalue()
async keyvalue (address, options = {}) {
    options = Object.assign({ create: true, type: 'keyvalue' }, options)
    return this.open(address, options)
}

It seems that it defaults create to true,  which makes it not equivalent to calling orbit.open() with type keyvalue.
Sorry if I misunderstood the docs somehow. I am new to orbit-db, and don't know the underlying concepts well enough yet.

Ok thanks

Store-specific repos have been merged into @orbitdb/core package. See latest API.


[SPARK-48780][SQL] Make errors in NamedParametersSupport generic to handle functions and procedures

What changes were proposed in this pull request?

This PR makes errors in NamedParametersSupport generic so that we can reuse that class to handle argument rearrangement both in functions and procedures. It is a subset of changes from PR #47183.
Why are the changes needed?

These changes are needed in preparation for adding support for stored procedures.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Exists tests.
Was this patch authored or co-authored using generative AI tooling?

No.

cc @cloud-fan @viirya @dongjoon-hyun @huaxingao @sunchao @HyukjinKwon @gengliangwang

Hm, seems like a failure in streaming. I'll check tomorrow.
[info] - SPARK-41224: collect data using arrow *** FAILED *** (39 milliseconds)
[info]   VerifyEvents.this.executeHolder.eventsManager.hasError.isDefined was false (SparkConnectServiceSuite.scala:888)
[info]   org.scalatest.exceptions.TestFailedException:
[info]   at org.scalatest.Assertions.newAssertionFailedException(Assertions.scala:472)
[info]   at org.scalatest.Assertions.newAssertionFailedException$(Assertions.scala:471)
[info]   at org.scalatest.Assertions$.newAssertionFailedException(Assertions.scala:1231)
[info]   at org.scalatest.Assertions$AssertionsHelper.macroAssert(Assertions.scala:1295)

I retried the streaming test and it is all green now.

Merged to master.


Using line numbering changes coloring of certain JSON elements to black color

Describe the bug
Using the latest version of highlight.js (9.12) and the line numbers library (2.3), certain elements in JSON (curly braces, colons, commas, and brackets) are now in black color. Not using the line numbering library does not produce this effect. It also changes the font size, but that's not too much of a concern for me.
To Reproduce
Steps to reproduce the behavior:

Clone the repo here: https://github.com/klische/HighlightJSLineNumbers/tree/master
Open the index.html and observe that those elements listed above are in black color

Expected behavior

Clone the repo here: https://github.com/klische/HighlightJSLineNumbers/tree/master
Open the index_no_line_number.html and observe that those elements listed above are in the correct color

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: macOS 10.13.4 (17E202)
Browser: Safari Version 11.1 (136<IP_ADDRESS>.4) and Chrome Version 67.0.3396.62 (Official Build) (64-bit)

Smartphone (please complete the following information):

Device: iPhone X, iPad Pro 12.9"
OS: iOS 11.3
Browser: WKWebView
Version: iOS 11.3

Hi @klische thank you for the feedback!
Interesting issue, I will think about the better solution.
Workaround
I propose to set color for .hljs-ln, because default styles of table override style-properties of .hljs)
.hljs-ln {
    color: #f8f8f2;
}

That works! Unfortunately, the spacing is ignored :( I just noticed that. It shifts everything to the left.

Yes, you are right.
I already created the issue #39 about this.


Feat 444 organize warning labels

Pull Request instructions:

Please follow the update protocol
Answer the questions below in detail. Your responses will be emailed to experimenters.
If the experimenters must do anything new, provide detailed step by step instructions on the wiki
If computer maintainers need to manually update anything, provide detailed step by step instructions
Use markdown syntax in order for your comments to be rendered reliably in the email: "1." instead of "1)", use four spaces for indents.
If you use the keyword "skip email" in the title, it will skip the email updates
Merges from "develop" into "production_testing" should use the keyword "production merge" in the title for reliable indexing of updates
Merges from "production_testing" into "main" should use the keyword "update main"

Describe changes:

warning box is now a widget what displays log warnings

What issues or discussions does this update address?

resolves https://github.com/AllenNeuralDynamics/dynamic-foraging-task/issues/444

Describe the expected change in behavior from the perspective of the experimenter

Warning box will display newest log messages at top of box. Warning will not be removed anymore

Describe any manual update steps for task computers

None

Was this update tested in 446/447?

[x] 446/447

Added camera warnings back into dialog


Add instructions on how to vendor

Right now it's not clear how the vendor directory was constructed or how to update a dependency that's present there. I checked the README, the vendor directory, the top level of the project and CONTRIBUTING.md.

That's a good point. I've constructed the vendor/ directory manually. I agree that we should ship a script that updates a certain dependency, or switch to a tool that does this for us.


how can I get each tab memory usage like chrome task manager

What versions are you running?
$ go list -m github.com/chromedp/chromedp
github.com/chromedp/chromedp v0.7.7

$ google-chrome --version
99.0.4844.51

$ go version
go version go1.16.6 darwin/arm64

The Protocol Monitor does not show anything when the Task manager is opened. So it's very likely that the Task manager is not implemented using the Chrome DevTools Protocol. You can check the CDP document here: https://chromedevtools.github.io/devtools-protocol/tot/Performance/. Maybe you can find something helpful.

thanks for reply!


Remove association of delete with name property

delete method does not show when associated with name.  updateName is already associated thus.

Thanks for the PR.  I've made this fix by hand to both this app and hellworld.


Could I override the carret position to get custom offsets?

I'd like to calculate pixel offsets of other "carrets" than the selected one. Could I provide my own character offset for which I want the pixel offset?

API example?

What you you mean by API example?

@Darker: please reopen if you're still looking for this feature and can provide an example of some sort. Thanks!


Correct lognormal test

Corrected the error for the test:

distLog = LogNormal(μ=μ, σ=σ)

instead of

distLog = LogNormal(μ, σ)

as the order of mu and sigma not correctly read. Now it works with reasonably small mu and sigma

Thanks. I wonder whether we should open an issue about it. Thus is regular python syntax and people should pay attention to the ordering. But mu looks more optional than sigma so I get where the mistake comes from.
I'll merge when the tests pass.


Simplex integration

Description
Simplex integration
Other Changes
Tested
Simplex staging. Android 11.
Related issues

Fixes #29
Fixes #110

Hey @tarikbellamine Thanks for giving more information regarding country list & issue related to our query. Here are our observations for "Not currently available" text:

We are able to see "Not currently available" text below Simplex provider for above mentioned countries using Valora.
Attachment: NotSupportedForSimplex.jpg

Verified On Devices: iPhone SE (14.2), Redmi Note 8 (9.0)
Thanks..!!


fix namespaces already exists error when registtering cluster with pu…

…ll mode
Signed-off-by: bruce<EMAIL_ADDRESS>What type of PR is this?
/kind documentation

What this PR does / why we need it:
when registerring cluster with 'Pull' mode, a namespaces already exists error will be found.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
none

/assign @rainbowmango

/approve


Fix inconsistency between API specification and actual implementation

Currently the API specification doesn't reflect fully what the actual API is doing in the backend.
Expected Behavior
Ideally, the specification should correctly reflect what the actual code is doing.
Current Behavior
The specification does not reflect the actual code.
Possible Solution
I suggest that we fix the backend code to reflect the specification if the frontend follows it exactly, or update the specification to reflect what is actually happening in the code.
Context (Environment)

This issue has made the integration of the frontend and backend a bit difficult as both ends have been following different specifications. It also means our API documentation does not reflect the actual code and will make it harder for future developers to understand our project.
Detailed Description

Our specification details that our endpoints are "/api/post" but in our code it is just "/posts"
The Comments Schema saves "comment_id" in it's body instead of "children_id"
Posts and comments use "createdAt" for the parameter name instead of "date_created"

Would this fall under #89 as it’s a fix to the documentation?
Cheers,
Timo
On Wed, Mar 18, 2020 at 10:19 PM GrunWong<EMAIL_ADDRESS>wrote:

Currently the API specification doesn't reflect fully what the actual API
is doing in the backend.
Expected Behavior
Ideally, the specification should correctly reflect what the actual code
is doing.
Current Behavior
The specification does not reflect the actual code.
Possible Solution
I suggest that we fix the backend code to reflect the specification if the
frontend follows it exactly, or update the specification to reflect what is
actually happening in the code.
Context (Environment)
This issue has made the integration of the frontend and backend a bit
difficult as both ends have been following different specifications. It
also means our API documentation does not reflect the actual code and will
make it harder for future developers to understand our project.
Detailed Description

Our specification details that our endpoints are "/api/post" but in
our code it is just "/posts"
The Comments Schema saves "comment_id" in it's body instead of
"children_id"
Posts and comments use "createdAt" for the parameter name instead
of "date_created"

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/se701-group6/se701-assignment1/issues/90, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AANUN6TLDHQVENR4N5DTNTTRICGX7ANCNFSM4LOMJQXQ
.

Would this fall under #89 as it’s a fix to the documentation? Cheers, Timo
…
On Wed, Mar 18, 2020 at 10:19 PM GrunWong @.***> wrote: Currently the API specification doesn't reflect fully what the actual API is doing in the backend. Expected Behavior Ideally, the specification should correctly reflect what the actual code is doing. Current Behavior The specification does not reflect the actual code. Possible Solution I suggest that we fix the backend code to reflect the specification if the frontend follows it exactly, or update the specification to reflect what is actually happening in the code. Context (Environment) This issue has made the integration of the frontend and backend a bit difficult as both ends have been following different specifications. It also means our API documentation does not reflect the actual code and will make it harder for future developers to understand our project. Detailed Description 1. Our specification details that our endpoints are "/api/post" but in our code it is just "/posts" 2. The Comments Schema saves "comment_id" in it's body instead of "children_id" 3. Posts and comments use "createdAt" for the parameter name instead of "date_created" — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#90>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANUN6TLDHQVENR4N5DTNTTRICGX7ANCNFSM4LOMJQXQ .

I believe the frontend has been basing their development on the API specification, so I was thinking we may need to end up changing the backend code to also reflect the specification.

Both frontend and backend needs to update their API urls, as they both do not use the /api prefix that is required to get the proxy working, and this prefix is needed to distinguish between app's pages and API endpoints.

@WaiHaiDere what do you have set up to get the demo working?

I approve the need to fix this.

Contacted Frontend team and they use the API documentation. Will need to change on Backend to do the same.

i approve

i approve


Entry URL rewriting

Hi,
instead of having url such as /myblog/2012/01/10/the-post-of-the-day/, I would like to have urls such as /myblog/categ1/categ2/the-post-of-the-day/ ...
According to you, what is the best way to obtain that ?
Cheers

This new document should close this issue.
http://django-blog-zinnia.com/documentation/how-to/rewriting_entry_url/
Regards


Backport HHH-15022 to branch 5.6 - Test and fix deleting all entities of a given type in a table-per-class hierarchy with a default schema

https://hibernate.atlassian.net/browse/HHH-15022
It turns out the problem only affects 5.6, not 6.0. So the fix is only present in this PR, not in #4658

I changed the test to execute with postgresql only, because the bug report was for postgresql and because we need to specify a schema name, which is inherently vendor-specific.

Thanks!


test: Port interactive transaction tests to new setup

Close prisma/client-planning#23

Going to draft it until all CI issues are fixed

Needs prisma/client-planning#65 to proceed


Missing dependencies in v 16 0rc3

Hey there,
Attempting to run singularity container of QSIprep v 16 0rc3
Check out the following errors with the dependencies.
Commandline: module load singularity
Running task 1
Commandline: singularity run qsiprep_160rc3.sif 10527bids_data/ 10527qsiprep_out/ participant --participant_label 10527 --output-resolution 1.3 --dwi_denoise_window auto --denoise-method dwidenoise --unringing-method mrdegibbs --distortion-group-merge none --output-space T1w --template MNI152NLin2009cAsym --b0-to-t1w-transform Affine --b0-motion-corr-to iterative --hmc-transform Affine --hmc_model eddy --shoreline_iters 2 --skull-strip-template OASIS --fs-license-file license.txt --do-reconall -w 10527tmpdir/
        1: [WARN] The recommended file /README is missing. See Section 03 (Modality agnostic files) of the BIDS specification. (code: 101 - README_FILE_MISSING)

        Please visit https://neurostars.org/search?q=README_FILE_MISSING for existing conversations about this issue.

        Summary:                  Available Tasks:        Available Modalities:
        42 Files, 324.31MB        bart                    T1w
        1 - Subject               bht                     dwi
        1 - Session               pamret                  bold
                                  pamenc                  events
                                  rest                    physio
                                  stopsignal
                                  scap
                                  taskswitch

        If you have any questions, please post on https://neurostars.org/tags/bids.

Making sure the input data is BIDS compliant (warnings can be ignored in most cases).
220729-22:11:00,332 nipype.workflow INFO:
         Running with omp_nthreads=8, nthreads=16
220729-22:11:00,336 nipype.workflow IMPORTANT:

    Running qsiprep version 0.16.0RC3:
      * BIDS dataset path: /home/bdeck8317_gmail_com/10527bids_data.
      * Participant list: ['10527'].
      * Run identifier: 20220729-221059_05343a3d-7ae1-4207-b896-f4f77265b9d2.

220729-22:11:00,840 nipype.utils WARNING:
         A newer version (1.8.3) of nipy/nipype is available. You are using 1.8.1
220729-22:11:01,683 nipype.workflow INFO:
         Combining all 1 dwis within the single available session
220729-22:11:01,691 nipype.workflow INFO:
         [{'dwi_series': ['/home/bdeck8317_gmail_com/10527bids_data/sub-10527/dwi/sub-10527_dwi.nii.gz'], 'fieldmap_info': {'suffix': None}, 'dwi_series_pedir': 'j-', 'concatenated_bids_name': 'sub-10527'}]
220729-22:11:01,745 nipype.workflow IMPORTANT:
         Creating dwi processing workflow "dwi_preproc_wf" to produce output sub-10527 (1.04 GB / 75 DWIs). Memory resampled/largemem=1.15/1.19 GB.
220729-22:11:01,747 nipype.workflow INFO:
         Automatically using 5, 5, 5 window for dwidenoise
220729-22:11:01,764 nipype.workflow INFO:
         Using 8 threads in eddy
220729-22:11:04,80 nipype.workflow IMPORTANT:
         Works derived from this qsiprep execution should include the following boilerplate:

Preprocessing was performed using *QSIPrep* 0.16.0RC3,
which is based on *Nipype* 1.8.1
(@nipype1; @nipype2; RRID:SCR_002502).

Anatomical data preprocessing

: The T1-weighted (T1w) image was corrected for intensity non-uniformity (INU)
using `N4BiasFieldCorrection` [@n4, ANTs 2.3.1],
and used as T1w-reference throughout the workflow.
The T1w-reference was then skull-stripped using `antsBrainExtraction.sh`
(ANTs 2.3.1), using OASIS as target template.
Brain surfaces were reconstructed using `recon-all` [FreeSurfer 6.0.1,
RRID:SCR_001847, @fs_reconall], and the brain mask estimated
previously was refined with a custom variation of the method to reconcile
ANTs-derived and FreeSurfer-derived segmentations of the cortical
gray-matter of Mindboggle [RRID:SCR_002438, @mindboggle].
Spatial normalization to the ICBM 152 Nonlinear Asymmetrical
template version 2009c [@mni, RRID:SCR_008796] was performed
through nonlinear registration with `antsRegistration`
[ANTs 2.3.1, RRID:SCR_004757, @ants], using
brain-extracted versions of both T1w volume and template.
Brain tissue segmentation of cerebrospinal fluid (CSF),
white-matter (WM) and gray-matter (GM) was performed on
the brain-extracted T1w using `FAST` [FSL <IP_ADDRESS>:57b01774, RRID:SCR_002823,
@fsl_fast].

Diffusion data preprocessing

: Any images with a b-value less than 100 s/mm^2 were treated as a *b*=0 image. MP-PCA denoising as implemented in MRtrix3's `dwidenoise`[@dwidenoise1] was applied with a 5-voxel window. After MP-PCA, Gibbs unringing was performed using MRtrix3's `mrdegibbs` [@mrdegibbs]. Following unringing, B1 field inhomogeneity was corrected using `dwibiascorrect` from MRtrix3 with the N4 algorithm [@n4]. After B1 bias correction, the mean intensity of the DWI series was adjusted so all the mean intensity of the b=0 images matched across eachseparate DWI scanning sequence.

FSL (version <IP_ADDRESS>:57b01774)'s eddy was used for head motion correction and Eddy current correction [@anderssoneddy]. Eddy was configured with a $q$-space smoothing factor of 10, a total of 5 iterations, and 1000 voxels used to estimate hyperparameters. A linear first level model and a linear second level model were used to characterize Eddy current-related spatial distortion. $q$-space coordinates were forcefully assigned to shells. Field offset was attempted to be separated from subject movement. Shells were aligned post-eddy. Eddy's outlier replacement was run [@eddyrepol]. Data were grouped by slice, only including values from slices determined to contain at least 250 intracerebral voxels. Groups deviating by more than 4 standard deviations from the prediction had their data replaced with imputed values. Final interpolation was performed using the `jac` method.

Several confounding time-series were calculated based on the
preprocessed DWI: framewise displacement (FD) using the
implementation in *Nipype* [following the definitions by @power_fd_dvars].
The head-motion estimates calculated in the correction step were also
placed within the corresponding confounds file. Slicewise cross correlation
was also calculated.
The DWI time-series were resampled to ACPC,
generating a *preprocessed DWI run in ACPC space* with 1.3mm isotropic voxels.

Many internal operations of *QSIPrep* use
*Nilearn* 0.9.1 [@nilearn, RRID:SCR_001362] and
*Dipy* [@dipy].
For more details of the pipeline, see [the section corresponding
to workflows in *QSIPrep*'s documentation](https://qsiprep.readthedocs.io/en/latest/workflows.html "QSIPrep's documentation").

### References

[WARNING] This document format requires a nonempty <title> element.
  Please specify either 'title' or 'pagetitle' in the metadata.
  Falling back to 'CITATION'
Cannot run qsiprep. Missing dependencies:
        mri_label2vol (Interface: Label2Vol)
        mri_label2vol (Interface: Label2Vol)
        mri_convert (Interface: MRIConvert)
        mri_convert (Interface: MRIConvert)
        mris_convert (Interface: MRIsConvert)
        mris_expand (Interface: MakeMidthickness)
        recon-all (Interface: ReconAll)
        recon-all (Interface: ReconAll)
        recon-all (Interface: ReconAll)
        recon-all (Interface: ReconAll)
        recon-all (Interface: ReconAllRPT)

A note, this issue only occurs if the user supplies the --do-reconall  flag. Otherwise, Freesurfer is not loaded and QSIprep v 16.0RC3 runs properly.

The container then gets killed

duplication of #384, sorry about that!


Needs new maintainers

Hi guys,
Since writing f.lux-indicator-applet I've been doing less and less python. The current version, with all the great additions from people, is not something I want to or can maintain, at least not by myself.
It is my intention to rewrite the bindings to xflux in node so I can have a better interface and easier (to me) to manage code. I do not know when that happens though, and it's a waste to let all the great suggestions and pull requests go to waste on this version.
So I'm looking for other people to step in. I want to start a github organisation and we can have a team of people to manage and maintain the code. I'd like to be involved, obviously, but this way, I'm not a bottleneck.
So, who's up for it?
Kilian

Nice move, Kilian.
I definately am up, but still am quite new to Git/Github and don't know all the processes yet. If nobody else would volounteer for it, I would just try do it.
Thinks asking you for help wouldn't be a big deal.
Thorsten

@ntc2, @NHellFire and @ev1l0rd: All of you are active in this repository. How do you feel about the above plans and would you participate?

@Kilian: I'm afraid I'm too busy to promise to take on any real responsibility here.
I have been using the indicator applet for a few weeks now and have tweaked some small things, as needed, to get it working for me.  I would like to make some small enhancements -- like showing in the GUI what start and end times were computed based on zip code or latitude + longitude, and making the transition from full brightness (day time) to blue filtered (night time) more gradual -- but I have no idea when I'd actually get around to it.
Re node.js, are you saying you plan to port the applet to JavaScript?

@Kilian: I have only bumped up the distro version each time in launchpad. I will continue doing so (and provide mirrors when someone elses PPA goes live by cloning the package to my PPA), but as I'm pretty much a dummy on linux development beyond bash scripting, I won't be able to help you update.
Also, @synthor: committing stuff to git (and github afterwards) is usually as easy as running the following commands in your directory:
 git add -A # Stages all changes for commit.
 git commit -m "messagehere" # Commits everything with the message 'messagehere'
 git push origin branch # Sends everything to github. Change branch to the current branch. github uses master by default.

tl;dr: I will keep up a mirror, but won't be able to help development.

@ntc2 yes, I have a far better grasp at making and maintaining javascript applications, and the communication model to the xflux binary should be much simpler. For the python/gtk version I'm looking for someone that can and wants to make such improvements, together with having a firmer grasp on the code. I dont think it should be someone’s day-task to do so, but having more people involved and with access to update the code seems a good idea.
@ev1l0rd The reason I don't do that is because I can not guarantee that it still works on more recent ubuntu versions; it requires proper testing and updating. If you've found that it works that's actually pretty useful.
Other people that have worked on pullrequests: @mystro256, @daTokenizer, @aaferrari and @petracvv what do you think of the above idea(s)?

@ev1l0rd Thanks, but that is not the deal. I already contributed to some repositories. At work I have an own git server and manage the code in that. No external contrubutions which I have to handle...so maybe it's time now for the next step.
I haven't created a fork yet, because I saw there are a lot of them already. Bet someone fixed that .pid bug already. Would be nice if this changes would be merged into this (main) repository.

@Kilian Let me have a look on the interface, if I find the time for it. xflux is propritary or? I found no further information or documentation. If you have something handy you're welcome.

Merging back all the pull request is something that the new github org could do, If many people look into merging small parts back into the main repository, it's manageable. There are some PID-related fixes waiting in the pull requests so it's worth checking those out.
F.lux and the xflux binary are proprietary and built by @herf and Lorna, but this project has their blessing. The documentation has been a combination of the binary it's output, the options their mac version offers and simply asking them.

But regarding that I also removed that searching for the old pid file and killing this process bug, I will submit a pull request. That problem was/is larger than the place of the pid file itself. ;)

Searched for xflux alternatives and found redshift. Installed it, and works like a charm. Even automaticly sets coordinates depending on libgssglue1. It even changed the color temperature now, whereas xflux didn't. It only did exactly at the time of dusk, which is +2 hours from now on here.

Hi everyone - I'm ready to update the xflux binary with something like the version we're using for Android. Has every feature in the Mac version and some extras too. There's a new communication API (based on abstract sockets).
90% of what's wrong with this project so far is I picked a blocking pipe to send/receive commands, and when that pipe fills up, we use 100% CPU and nothing works after that. So the new thing is fully async and a lot better.
All that is needed is to update the UI and communication protocol to match.

Yes, I also see the xflux path much more convenient than a redshift one.
From looking at the issues, I see mainly packaging requests for different distributions and package managers. Ubuntus, Feboras, Debians and CentOSes should at least be provided. I have had good experiences with packages out of the OpenSUSE build pipeline.
Insofar it is only questionable why the xflux community relies on a non-open source binary to achieve the goal of colour temperature aware desktop rendering. Native Wayland support'd be another topic, too.
Where's a list of most urgent issues to be resolved for this repo, before being completely able to hand over to the community?

@synthor redshift has GUIs available, but I'm neither interested in using it (xflux is superior in its color management) or writing a gui for it (as there are already gui's for it) Simply, this repository or the new community repository is not the place for that. :)
@almereyda has the right idea (thanks for the clear message!) Packaging (and testing etc) for multiple systems is a totally different beast from building things. General issues in short would be:

updating the xflux binary (with help of @herf)
update the gui to no longer use a subproces and dbus, but use a non-blocking communication channel to xflux. This should fix 80% of the issues, the rest being either real bugs or packaging/distribution requests.
take stock on if the api's we use for the indicator-applet are as they should be, or if we should switch to something like systray for better support on multiple distributions (or both, there is a pull request available that does this.)
get packages for different distributions.

I didn't know that the author of xflux is under us. Tried to find some information on Duckduckgo but wasn't successful with that. So I looked out for an alternative. There was no intention to move the project from xflux to redshift. Just brainstormed a bit.. :)

No harm done!

@Kilian I created a PR #72 as replacement of #69, which fixes the xflux renaming bug. Please merge it and close #69.
Strangely I forked from @Mystro256 at home. That's where this strange pid file/killing random process on boot comes from. You already have merged the appropriate PR into master. :)

@Kilian And finally I found the reason why a clone of your repo does not run on (X)Ubuntu 14.04: the xflux binary in /usr/bin/local has simply no execution permission.
Chmod +x and it will start.. :)

See, this is why I need help ;) awesome. What I want to do is actually set up the community repository, and then I'll also add you, and we can make that pullrequest number 1. Sounds like a plan?

Go for it. :)
@Mystro256's pull request also looks nice. I will watch them all later, if I find the time.

@Kilian Reminder.. :ghost:

I've been busy offline, will pick this up soon :)

Unfortunately I can not take charge of the program maintenance because I'm not very familiar with the fluxgui code (and I'm too busy with other things), but I compromise to keep updated the Gentoo ebuild in this overlay.

Where's a list of most urgent issues to be resolved for this repo, before being completely able to hand over to the community?
General issues would be:

#7 high cpu usage for fluxgui
#16 No multi-monitor Support (Linux)
#28 xflux sources?
#46 PPA needs the multi-monitor update, duplicate of #16
#56 setup.py renames xflux64/32 whenever it runs
#57 Dual screen support, duplicate of #16
#66 applet fails to launch silently
#68 High usage of processor, duplicate of #7

Most of the issues on multimonitor support would believe that already were resolved in the latest versions of xflux, the #56 is due to this commit that I sent a few months ago to include the 32-bit version of xflux (I apologize for not having these details in mind, but I see that @synthor already resolved), and #66 is possible that there been resolved with the aforementioned commit (more precisely with the fluxapp.py modification that I did when checks whether a previous instance is running).

The new community repository now exists at https://github.com/xflux-gui/xflux-gui
@herf @synthor @ntc2 @aaferrari I have invited you all to join the github organisation.
I have copied over the repository, but none of the pull requests or issues are linked. @synthor we found pull request #1, can you shoot that in soon? I will update this repository to link to the new one.

@Kilian I was going to merge some documentation related pull requests (https://github.com/xflux-gui/xflux-gui/pulls 11 and 12) and apparently I don't actually have write access to the repo.

@ntc2 sorry! apparently being a member of the organisation doesn't automatically mean write access. You should have full access now.

@Kilian Thanks, I merged some pull requests!


Allow retrieving associated values from DragState

Depending on the use case, it is very important to know the current DIODragState–specifically the location (CGPoint)– and getting the data out of enums with associated values is actually an issue I ended up running into.
This PR basically makes use of other language constructs to allow us to access the inner details of the enum–yeah, I just couldn’t find any other way to have access than the enum-case-pattern-matching-alike stuff.
Now, in my receivedDragWithDragInfo method from DIODestinationView I can, for instance:
switch(dragState) {
...
case .ended:
    let position = dragState.ended
    let exampleView: UIImageView = UIImageView(image: UIImage(named: example))
    sticker.frame = CGRect(x: (position?.x)!, y: (position?.y)!, width: 100, height: 100)
    self.addSubview(sticker)
...
default:
    break

And my exampleView will be plotted based on dragging location state.

Nice one!
suggestion: use just one computed property .location instead of one for every case.

Oh, my bad 😢
I've just refactored it! Now the example above goes like:
switch(dragState) {
...
case .ended:
    let position = dragState.location // .location 🔝👌😂
...
default:
    break

Thanks for contributing and making this library more delightful


Add a carousel at the home page

I would like to work on this issue under LGM-SOC'21 @QAZIMAAZARSHAD Can you please assign me

@coding-geek21 slideshow is already available on the home page, so I think no need for a carousel.


cloud: Overview does not show data generated after Reset website

Describe the Bug
https://cloud.umami.is/ Overview does not show data generated after Reset website.

Database
Umami Cloud
Relevant log output
No response
Which Umami version are you using? (if relevant)
No response
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response

This is confirmed. There is an issue with querying date ranges for reset websites and our database views that are truncated to the hour. There should be data showing after an hour, but let me know if its still blank. We we get this fixed anyways.


overlay: start open-vm-tools services

vSphere tools services should autorun on masters.
Related: https://github.com/openshift/okd/issues/483

We need a few vSphere fixes to land before it can be properly tested though

We need a few vSphere fixes to land before it can be properly tested though

/cherrypick release-4.6

/cherrypick release-4.6


Package Requirements

Is it possible to attach a package requirements file for either pip or conda.It will remove the guess work when installing packages.
Thank you

Now the requirements are in readme.md


Map centres to already on-screen unit.

Sounds odd, but most noticable with a new game and just 1 settler.
Civ allows a unit to move upto 6 map sqaures away from the centre of the screen before recentering on that unit.  When the key is pressed to move the unit, the screen should centre on the square the unit is currently in as the movement animation is played.

This bug was introduced due to some experimental unfinished AI code. I will find a good solution for this.


Script5022 error when trying to view pdf with scanned image in ie11

Pdf:
2_birds.pdf
Configuration:

Web browser and its version: ie11
Operating system and its version: window 7 64 bit
PDF.js version: pdfjs-dist v1.5.415
Is an extension:

Steps to reproduce the problem:
let pdfData = this.base64ToPdfData(encodedDoc);

            window.document.write('<canvas id="af-canvas"></canvas>');
            PDFJS.workerSrc = '../assets/pdf.worker.js';
            PDFJS.getDocument(pdfData).then(function(pdf) {
              pdf.getPage(1).then(function(page) {
                var scale = 1.5;
                var viewport = page.getViewport(scale);

                var canvas = window.document.getElementById('af-canvas');
                var context = canvas.getContext('2d');
                canvas.height = viewport.height;
                canvas.width = viewport.width;

                var renderContext = {
                  canvasContext: context,
                  viewport: viewport
                };
                page.render(renderContext);
              });
            });

  base64ToPdfData(base64) {
    var raw = atob(base64);
    var uint8Array = new Uint8Array(raw.length);
    for (var i = 0; i < raw.length; i++) {
      uint8Array[i] = raw.charCodeAt(i);
    }
    return uint8Array;
  },

The pdf comes down in base64 encoded data, thus the above. I'm hoping this reproduces in a more basic sense for someone.
What is the expected behavior? Display the pdf - see pdf in chrome for it working
What went wrong? It doesnt render at all in ie11 and shows script5022 error in the debugger. It seems to fail at the line  this.ctx.drawImage(groupCtx.canvas, 0, 0); in the endGroup: function.

Since there is complete example online to test your, the problem can be with mode HTML in e.g. non-HTML5. Check <!DOCTYPE definition and check if web/compatibility.js is included. Closing as incomplete.

@yurydelendik where is the complete example online to test this?. I have both doctype and web compatibility setup.
I managed to get more detail on the exception - drawImage is throwing a typeMismatchError.

Nevermind - although the original page has <!DOCTYPE - this was opening into a new window, if I open onto the same page it works. The new window doesnt have <!DOCTYPE, so could well be it, ill see if i can add that to the new window.


New version: Microsoft.EdgeWebView2Runtime version 124.0.2478.80

Created by 🥟 Dumplings in workflow run #4836.
Logs
Updated: 124.0.2478.67 → 124.0.2478.80
Submitting WinGet manifests
The manifests for the last version 124.0.2478.67 will be removed

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

@wingetbot run


Android: externalize strings for i18n

Instead of hard-coded in java code.

Note that English is fine, i18n would be a nice-to-have later, depending on adoption.