Server Not Starting Via API

I have been using DS 2.2.2 for several weeks without problem, but now I upgraded to 2.3.4 and I can't seem to start the server using the Node API.  Has the Node server API changed in 2.3.x?

It shouldn't have no. Can you please post your config? Thanks!
On Mon 12. Jun 2017 at 10:32, Sanjay Kannan<EMAIL_ADDRESS>wrote:

I have been using DS 2.2.2 for several weeks without problem, but now I
upgraded to 2.3.4 and I can't seem to start the server using the Node API.
 Has the Node
server API changed in 2.3.x?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/deepstreamIO/deepstream.io/issues/721, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ACm7Sy8HQEHDM6HDivEHIm6yKp4naE0Vks5sDQXEgaJpZM4N23Vu
.

I am running a minimal script with the following contents:
var Deepstream = require('deepstream.io');
var server = new Deepstream({ port: 7000 });
server.start();

That should certainly not have changed.
I know this certainly works:
X = new Deepstream()
X.set('port', 7000)
X.start()
I'll also test your issue once i have access to a computer later today or
tomorrow.
Can you let me know if that works for you?
On Mon 12. Jun 2017 at 10:39, Sanjay Kannan<EMAIL_ADDRESS>wrote:

I am running a minimal script with the following contents:
var Deepstream = require('deepstream.io');
var server = new Deepstream({ port: 7000 });
server.start();
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/deepstreamIO/deepstream.io/issues/721#issuecomment-307739804,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACm7S1rj0pTjhZSo4N_OYCW236sVNgdOks5sDQc7gaJpZM4N23Vu
.

Didn't work, unfortunately. For debugging purposes, here are my environment details:

Attempted to run the provided script on Windows 10 (running Node 6.10.2) as well as a remote Ubuntu 16.04 box (running Node 4.2.6).
In both cases, I created a fresh directory, ran npm install deepstream.io, then attempted to run the given script. The npm install gave no errors.
If I use the Deepstream release executables instead, there are no problems initializing the server.

Thank you for the details!
Can you set the log level to debug? Might capture some more event logs.
Thanks!
On Mon 12. Jun 2017 at 11:15, Sanjay Kannan<EMAIL_ADDRESS>wrote:

Didn't work, unfortunately. For debugging purposes, here are my
environment details:

Attempted to run the provided script on Windows 10 (running Node
6.10.2) as well as a remote Ubuntu 16.04 box (running Node 4.2.6).
In both cases, I created a fresh directory, ran npm install
deepstream.io, then attempted to run the given script. The npm install
gave no errors.
If I use the Deepstream release executables instead, there are no
problems initializing the server.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/deepstreamIO/deepstream.io/issues/721#issuecomment-307748430,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACm7S0GiyYVtNKl1R-2Q4DO9In0pGTGZks5sDQ_AgaJpZM4N23Vu
.

Hey we've discovered the root cause of this. We'll have a fix out soon

I believe the cause is the new version of javascript-state-machine! When I reverted that module from 3.0.1 to 3.0.0-rc1 the issue was resolved.

Yeah, we just realized that too! Looking into fixing the version dependency
On Mon 12. Jun 2017 at 11:28, Sanjay Kannan<EMAIL_ADDRESS>wrote:

I believe the cause is the new version of javascript-state-machine! When
I reverted that module from 3.0.1 to 3.0.0-rc1 the issue was resolved.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/deepstreamIO/deepstream.io/issues/721#issuecomment-307751179,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACm7S8nBsO934qrppF9XbFrAnpB6z-hwks5sDRK5gaJpZM4N23Vu
.


Image profile coordinates

This PR scales horizontal and vertical profile x coordinates according to image origin and scale.
It does nothing for free line profile and nothing for stack profile.
related to #1642

LGTM


Remove $basepath from Eve class

Just use the constant DIR. All the files are relative to eve.class.php file location

Solved!


pipenv won't install on current nixpkgs-unstable

Describe the bug
nix-shell -p python3 -p pipenv fails.
This is because of from pip._internal.cli.main import main', "ModuleNotFoundError: No module named 'pip._internal.cli.main'" which was previously addressed in #71178.
I've been having trouble with pipenv on my main machine (MacOS 10.15/Catalina with /nix provisioned via @steshaw's method) for the past little bit, and I thought I had an isolated problem. Today, I fired up a spare Macbook Pro and installed 10.15, fresh, used the same method for /nix, and ran through the regular curl https://nixos.org/nix/install | sh method. It failed there too.
Here is a full log of this command on a fresh nix install.
To Reproduce
Steps to reproduce the behavior:

nix-shell -p python3 -p pipenv

Expected behavior
A working pipenv. What I actually got is at the end of the above-linked log.
Screenshots

Additional context
Brand new nix install. No local overlays. Not even anything installed with nix-env -i ….
Nix channel is:
sean@saarcosm ~ % nix-channel --list
nixpkgs https://nixos.org/channels/nixpkgs-unstable

Metadata
sean@saarcosm ~ % nix-shell -p nix-info --run "nix-info -m"
these paths will be fetched (0.01 MiB download, 0.03 MiB unpacked):
  /nix/store/01ksiwn033npsbhkpj4n6kf8z2inkrmn-nix-info
  /nix/store/wjm15sdvqrpkbxn4hmz1s3hjnsxg5gcd-DarwinTools-1
copying path '/nix/store/wjm15sdvqrpkbxn4hmz1s3hjnsxg5gcd-DarwinTools-1' from 'https://cache.nixos.org'...
copying path '/nix/store/01ksiwn033npsbhkpj4n6kf8z2inkrmn-nix-info' from 'https://cache.nixos.org'...
 - system: `"x86_64-darwin"`
 - host os: `Darwin 19.3.0, macOS 10.15.3`
 - multi-user?: `no`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.3.2`
 - channels(sean): `"nixpkgs-20.03pre212770.cc1ae9f21b9"`
 - nixpkgs: `/Users/sean/.nix-defexpr/channels/nixpkgs`

Follow up to this:
TLDR: Python is a pain in the ass. Unset the PYTHONPATH in your shell and you can make it work.
It seems to be that that the PYTHONPATH set by the nix shell clobbers the PYTHONPATH pipenv needs to be able to call pip. When pipenv installs the virtualenv it makes a link to the current python it can find on the PATH and then downloads a NEW pip from pypi into the virtualenv. This new pip executable is basically just a bootstrap script that gets called to find the "real" pip, intending to find the pip it just installed.
So taking a look at the pip executable created by pipenv:
import re
import sys

from pip._internal.cli.main import main

if __name__ == '__main__':
   sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
   sys.exit(main())

The offending line is from pip._internal.cli.main import main. Now the PYTHONPATH set in the nix shell points to the PYTHONPATH of the pipenv's python not of the python pipenv just installed. This seems to get passed through the execution of pipenv, into the above executable, meaning that the first pip source found is the pip installed by Nix, not the pip installed by pipenv. Usually, even though this breaks the purity of pipenv, it doesnt matter because pip is able to execute under a bunch of different versions of python (its still 2.7 compatible...), but the guys managing pip have shifted the location of the main module twice over the last two releases. This means that when the above script intended for the 20.0.2 version pipenv installed tries to import main from _internal.cli.main it errors out because its looking at the 19.3.1 version installed by nix.
Seems that unsetting the python path forces the PYTHONPATH to get set properly by the time pip is called by pipenv. But it also seems like either the way pipenv is being wrapped needs to be changed or pipenv needs to change how its setting the path for its call of pip. More research may be needed here to get a good solution.

(Thank you for your analysis. I do really appreciate it.)

Unset the PYTHONPATH in your shell

Is there a good way to do this in shell.nix? I need it to happen after python and before pipenv, right?

FWIW, this appears to fix it: https://github.com/NixOS/nixpkgs/commit/5ca385e1e9f2db0caa93721d147f89c0d9ea0f0d  (but also does not yet seem to be in -unstable)

Going to close this one since nix-shell -p pipenv -I nixpkgs=https://github.com/NixOS/nixpkgs/archive/477ea066ca1.tar.gz (which is a build from today) fixes it. nixpkgs-unstable isn't being updated right now for unknown reason, but that's unrelated to this.

Thanks for this!

FWIW, this appears to fix it: 5ca385e (but also does not yet seem to be in -unstable)

Just in case anyone else lands here as well, just as I did - this is now in nixpkgs-unstable.


Investigate how to become an official Hall integration

Integrating Bugsnag with Hall is a messy process - it's buried and unclear.
Expected: When you click "Add Integrations" in Hall, you should see a Bugsnag logo in the list of available integrations. When you click on it, it should lead you to a page that says "How to Integrate Bugsnag with Hall." This page should give a small Introduction that briefly explains what Bugsnag is and what the integration does, and provide the Group API token.
Actual: Bugsnag doesn't appear in the list of available integrations. Instead you have to click a big gray question mark labeled "other" and then click "Get Started" under Build your Own. This lands on a generic integration page that says "How to Integrate your Service with Hall."

This is probably a little obsolete now that Atlassian have bought Hall.

We're not working on this right now, but thanks for looking into it @jacobmarshall!


cellNav in 3.0.0-rc.18: multiple selection with shift+click is not supported.

Hi Angular UI team,
Thank you for the great work!
After upgrade to 3.0.0-rc.18 we noticed then while using cellNav feature the multiple selection with ctrl+click works great, but shift+click is not supported. Unfortunately this lead to overriding the core shift+click behavior. Are there any chances to use cellNav feature to extend the core functionality by turning on arrow keys but inherit the click behavior from the core?

@PaulL1 please, look at my comment in #2109 about evt.stopPropagation() for click event.


Receiving an error: Profile production does not exist

I'm using my dev credentials for AWS - and do not have production creds.
serverless --version:
Your Environment Information ---------------------------
Operating System:          darwin
Node Version:              14.8.0
Framework Version:         2.16.0
Plugin Version:            4.3.0
SDK Version:               2.3.2
Components Version:        3.4.3
serverless.yml:
plugins:

serverless-python-requirements

custom:
stage: ${opt:stage, self:provider.stage}
AccountId:<PHONE_NUMBER>1111
pythonRequirements:
layer: true
name: ${self:service}-${self:custom.stage}-layer
compatibleRuntimes:
- python3.8
noDeploy:
- pytest
- pytest-cov
- pytest-mock
- boto3
provider:
name: aws
runtime: python3.8
stage: dev
region: us-east-1
versionFunctions: false
environment:
ENVIR: ${self:custom.stage}
QUEUE_URL: !Ref SQSQueue
memorySize: 128
profile: dev
$ export SLS_DEBUG=*
$ sis deploy --stage dev -v
....
Error Message:
Error: Profile production does not exist
at Object.addProfileCredentials (/usr/local/lib/node_modules/serverless/lib/plugins/aws/provider.js:136:15)
at Object.addEnvironmentProfile (/usr/local/lib/node_modules/serverless/lib/plugins/aws/provider.js:150:12)
at AwsProvider.getCredentials (/usr/local/lib/node_modules/serverless/lib/plugins/aws/provider.js:1365:10)
at AwsProvider.request (/usr/local/lib/node_modules/serverless/lib/plugins/aws/provider.js:1204:48)
at AwsCompileLayers.compareWithLastLayer (/usr/local/lib/node_modules/serverless/lib/plugins/aws/package/compile/layers.js:124:26)
at /usr/local/lib/node_modules/serverless/lib/plugins/aws/package/compile/layers.js:166:54
at /usr/local/lib/node_modules/serverless/node_modules/graceful-fs/graceful-fs.js:123:16
at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
From previous event:
at /usr/local/lib/node_modules/serverless/lib/plugins/aws/package/compile/layers.js:166:38
at Array.map ()
at AwsCompileLayers.compileLayers (/usr/local/lib/node_modules/serverless/lib/plugins/aws/package/compile/layers.js:165:17)
From previous event:
at Object.package:compileLayers [as hook] (/usr/local/lib/node_modules/serverless/lib/plugins/aws/package/compile/layers.js:21:59)
From previous event:
at PluginManager.invoke (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:521:22)
at /usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:556:24
From previous event:
at PluginManager.run (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:556:8)
at /usr/local/lib/node_modules/serverless/lib/Serverless.js:203:33
at processImmediate (internal/timers.js:458:21)
From previous event:
at Serverless.run (/usr/local/lib/node_modules/serverless/lib/Serverless.js:190:74)
at /usr/local/lib/node_modules/serverless/scripts/serverless.js:50:26

Followup:
I made a fake AWS profile in my .aws/credentials file called [production] using my dev profile credentials - and it appears to work. This is a bug in the most recently available serverless-python-requirements code.


Mac OS X Catalina cannot find STM32 via USB port

Hello,
I connected my STM32 board and it's blinking.
However, I get "Found 0 stlink programmers" when I run
st-info --probe

I am running Catalina 10.15.2. No USB device was added to /dev, so maybe I am missing a driver?
The hardware is from Amazon:
[initeq] STM32 ARM STM32F103C8T6 Blue Pill Minimum System Development Board with ST-Link V2 USB Programmer (2-Pack + ST-Link V2)
Would anyone know how to resolve this? I looked for info/drivers but did not find anything.
st-info was built manually from git.
Thanks so much for your help!
Itamar

@ihassin: The current macOS driver package dedicated for stlink_v1 has been sucessfully tested on OS X 10.11 El Capitan. As to my current state of knowledge no later versions have been tested so far. However, if anyone did, there is no documentation on this. Also it remains unclear if the driver supports stlink_v2 as well. I am really sorry that I can't give you a more useful feedback by now. I feel that the current state of support for macOS is not where I'd like it to be. I am putting this up on the agenda for one of the upcoming releases as I feel we deserve better support for this platform.
Can anyone who is able to program and/or test driver-related issues on macOS please help out on this? We should ensure that stlink is working properly on macOS 10.14 & 10.15. Older versions may be dropped from support as very rarely seen by now. 10.14 is the latest system version to support x86 apps and binaries and therefore should see good support for several years.

Thanks so much for your reply. I could not get it to work on 10.15.3 Catalina, and have shelved my efforts :(

@ihassin: Thx for your feedback. I’m sorry to hear that. Will pull this issue forward to the upcoming release, as I feel it is too significant to push it out any further.

Greatly appreciated! I had plans to write an RTOS for it.

The first thing here is: We need at least one contributor on a macOS 10.14 (Mojave) and 10.15. (Catalina) environment. And it would also be a nice to have, if a STlink-v1 programmer was present besides a STLink-v2, as this would also help to fix/verify the other two issues already linked. Volunteers step forward!

@ihassin: Can you describe more precisely what you did? You wrote that you connected the Bluepill and that it is blinking, this is just fine as the Blinky program is linkely to be preflashed prior to shipping. Here there is not driver to expect, as the USB port only serves to power the board in this state. Is your STLink-v2-clone Programmer recognised on USB?

Hi, and thanks for following up!
Correct - Blinky works, so I used that to validate that I have a good board.
Inserting the USB cable to my Mac Catalina 10.15.3 did not make a USB device appear, hence could not communicate with it. Am I doing something wrong? I’d love to be able to help somehow. I’ve never programmed MacOS at the device level, but am willing to learn, if you can take on an apprentice :) Definitely willing to help in testing etc.
Itamar
On Mar 23, 2020, 12:28 PM -0400, nightwalker-87<EMAIL_ADDRESS>wrote:

@ihassin: Can you describe more precisely what you did? You wrote that you connected the Bluepill and that it is blinking, this is just fine as the Blinky program is linkely to be preflashed prior to shipping. Here there is not driver to expect, as the USB port only serves to power the board in this state. Is your STLink-v2-clone Programmer recognised on USB?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

What was connected via the USB you attached, the Board or the STLink-v2-Programmer?

Related to #672.

Hi there - connected to the programmer.
Itamar
On Mar 23, 2020, 20:41 -0400, nightwalker-87<EMAIL_ADDRESS>wrote:

Related to #672.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

ok, and what does "System Profiler" say? (/Programs/Utilities/System Profiler.app)
Take a look at "Hardware --> USB" in the sidebar within the program window.
I expect to see something there like a device and manufacturer ID.
If it powers up it should actually tell us something...

Reading through this thread, I think the OP simply connected the Blue Pill via its USB connector. No ST-Link, i.e. no way it can be programmed that way. An ST-Link of some kind needs to be connected to the 4 SWD/power pins on the other side of the Blue Pill to reprogram it.
IOW, this is not macOS related, this is simply a misunderstanding as to how Blue Pills can be re-flashed.

@jcw: I did think that before, but he explained later...
Just to make it very clear:

USB-Port <---> STlink-v2 (Programmer) <--SWD+PWR-Wires--> SWD-Pins on Bluepill-Board
=> programming works
USB-Port <---> Bluepill-Board
=> not detected by mac AND programming not possible; only PWR supply via USB-Port, USB will not work - this is normal and not an error

@ihassin: if 1) is your setup, then we can continue to look for a solution, as a problem appears to be present.

ping @ihassin ?

Yes getting the messages but need to find time to test again. I’ll try to do it today.
Itamar
On Mar 30, 2020, 07:11 -0400, nightwalker-87<EMAIL_ADDRESS>wrote:

ping @ihassin ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@jcw: I did think that before, but he explained later...
Just to make it very clear:

USB-Port <---> STlink-v2 (Programmer) <--SWD+PWR-Wires--> SWD-Pins on Bluepill-Board
=> programming works
USB-Port <---> Bluepill-Board
=> not detected by mac AND programming not possible; only PWR supply via USB-Port, USB will not work - this is normal and not an error

@ihassin: if 1) is your setup, the

n we can continue to look for a solution, as a problem appears to be present.

@Nightwalker-87 @jcw : I think I am on (1). Attaching photo. I also tried with a Mac that has native USB ports, so I don't think it's the converter that is the problem.

As far as I can see your SWDCLK and SWDIO lines are swapped.

I found this on the web: https://wiki.cuvoodoo.info/doku.php?id=jtag
However, your programmer looks similar, but has a different case marking.
Can you open it by carefully pulling back the metal case over the usb connector. It would be helpful if you could take a closeup picture from the board inside (front side and back side). The resolution of the last picture you sent was quite good BTW. :+1:
This would allow a look at the µC, the board marking and if the soldering is nicely done.
I have read reports that this caused some issues on some devices. Keep in mind that they are cheap china clones (which does not necessarily mean that they are not useful, but they ship with issues sometimes as many are soldered very quickly by hand and are not always tested well).
I would just like to try to rule out any hardware issue.

FWIW, I have a couple of ST-Link clones, which seem to fall into two variants and different header pins:

The chips on both are labeled STM32F103CBT6, i.e. 128k flash F103's.
I can't say with 100% certainty, but I don't think I've ever run into issues with one or the other.
(didn't mean to speak for @ihassin of course, just adding some more info, in case this helps ...)

@jcw: I am aware of that, but have two here with different pinouts as well. As one could read the pinout in the picture, I was able to identify.
The upper one of yours has a foam pad, which addresses a common issue as well, where the case can short-circuit the pin row of the connector - that's good. Thx for providing this example though, as it shows how the quality of the assembly can vary (but there are even worse - I can tell).
OK, so let's turn back to the topic...

This is the one I got from Amazon:
https://www.amazon.com/gp/product/B079B95L9Y/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
Itamar
On Apr 5, 2020, 19:21 -0400, nightwalker-87<EMAIL_ADDRESS>wrote:

@jcw: I am aware of that, but have two here with different pinouts as well. As one could read the pinout in the picture, I was able to identify.
The upper one of yours has a foam pad, which addresses a common issue as well, where the case can short-circuit the pin row of the connector - that's good. Thx for providing this example though, as it shows how the quality of the assembly can vary (but there are even worse - I can tell).
OK, so let's turn back to the topic...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I found this on the web: https://wiki.cuvoodoo.info/doku.php?id=jtag
However, your programmer looks similar, but has a different case marking.
Can you open it by carefully pulling back the metal case over the usb connector. It would be helpful if you could take a closeup picture from the board inside (front side and back side). The resolution of the last picture you sent was quite good BTW. 👍
This would allow a look at the µC, the board marking and if the soldering is nicely done.
I have read reports that this caused some issues on some devices. Keep in mind that they are cheap china clones (which does not necessarily mean that they are not useful, but they ship with issues sometimes as many are soldered very quickly by hand and are not always tested well).
I would just like to try to rule out any hardware issue.

The case is super-glued to the connector. At least they did a good job on that...

Unfortunate - Can't get an impression from here then, whether it is defective.
Maybe it it a solution to buy a new (cheap) programmer, but make sure you get one of these "known ones" with a "ST" printing on the case (these can also be opened BTW) as shown in the link I've sent before. You may consider to order from a local (known) online-distributor or shop, maybe on ebay, but that's up to you. Can you try to get a refund from amazon?
It could be that you ordered non-functional crap, the board might be ok, but we can't confirm this now, that is just a vague assumption...
I'm not aware of any general issues with STLink-v2 programmers on macOS. Also note that up to now we haven't done anything with the stlink tools yet, as the hardware detection of the programmer is not related to the tools, as no driver is necessary for that (this is different for the older STLink-v1 though, now obsolete).

Thanks so much for your help thus far. I’ll get another set/programmer and let you know.
Itamar
On Apr 6, 2020, 05:13 -0400, nightwalker-87<EMAIL_ADDRESS>wrote:

Unfortunate - Can't get an impression from here then, whether it is defective.
Maybe it it a solution to buy a new (cheap) programmer, but make sure you get one of these "known ones" with a "ST" printing on the case (these can also be opened BTW) as shown in the link I've sent before. You may consider to order from a local (known) online-distributor or shop, maybe on ebay, but that's up to you. Can you try to get a refund from amazon?
It could be that you ordered non-functional crap, the board might be ok, but we can't confirm this now, that is just a vague assumption...
I'm not aware of any general issues with STLink-v2 programmers on macOS. Also note that up to now we haven't done anything with the stlink tools yet, as the hardware detection of the programmer is not related to the tools, as no driver is necessary for that (this is different for the older STLink-v1 though, now obsolete).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@ihassin: Let me give you some final advice how to proceed further: As soon as you have the new device, simply plug it into an usb port on your computer without any board connected to it and refer to the following:

ok, and what does "System Profiler" say? (/Programs/Utilities/System Profiler.app)
Take a look at "Hardware --> USB" in the sidebar within the program window.
I expect to see something there like a device and manufacturer ID.

If this is the case, you can proceed as originally intended.
... and let me give you some general advise for further proceedings:

avoid to connect wires while the programmer is plugged into the usb port and thus is powered on
don't connect any pins from the programmer to the board other than VCC, GND, SWDCLK and SWDIO (as intended)

@ihassin: I hope to have helped you along with the provided feedback.
Thx also to @jcw for the given input.
I am closing this now as resolved, as this issue is not related to the stlink toolset itself.

I’d like to thank you for the time and effort you spent on this and how helpful you were with your explanations and support. Really commendable, thank you for help and attention!

You are welcome.

Just following up - I just got the new programmer from Adafruit, and it works well. Recognized and st-info --probe sees it. Thank you so much for spending time with me to resolve this. I will leave a comment on Amazon regarding the one I originally bought.

@ihassin: Thx for your feedback. That is good news and I'm happy that we were able to help.


runtime: possible contention on epollwait

What version of Go are you using (go version)?

$ go version go1.17.1 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.17.1"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build771282332=/tmp/go-build -gno-record-gcc-switches"

What did you do?

I had implement some kind of redis proxy which dose encode/decode on behave of each command.
By doing some benchmark against this tiny project, I found some maybe interesting things.
With redis pipeline disabled(memtier_benchmark --pipeline 1), as concurrent connection increase,
the throughput continue to increasing , until a certain level, with whatever GOMAXPROCESS.
Taking a look at /proc/pid/stack by a bit sampling, I found all of the Ms are sitting in syscall(entry_SYSCALL_64_after_hwframe namely).
Using ebpf to step down the sample call stack:
#!/usr/local/bin/bpftrace

kprobe:osq_lock
{
  if( comm=="some_command" ){
   @stack[kstack()] += 1;
  }
}

It appears to be contention on the global single epoll fd used by netpoller.
@stack[
  osq_lock+1
  __mutext_lock_slowpath+19
  mutxt_lock+47
  ep_scan_ready_list.constprop.17+497
  ep_poll+483
  sys_epoll_pwait+414
  do_syscall_64+115
  entry_SYSCALL_64_after_hwframe+61
] : 17325

My suspicion is that:

When there are relative small packet and high concurrent connection  involved
most Gs are eager to do net IOs
thus all Ps are eager to do netpoll
which will epollwait on the single epfd
and contention on lock associated with it
It should become worse as the core of CPU increased.

A possible solution is to associate each M with its private epfd?
Note:
Running on Ubuntu Xenial(kernel 4.15.0)
What did you expect to see?
What did you see instead?

That description doesn't really match how the Go runtime works.  At most one M will sleep in epoll_pwait.  When there is an M sleeping in epoll_pwait, other M's will not call the poller.
That said, if there is no M sleeping in epoll_pwait, then as each M looks for which goroutine to run next, it will call epoll_pwait with a zero timeout.  It is possible that in this case multiple M's will compete for the poller descriptor.
Normally it doesn't help to set GOMAXPROCS to be much larger than the number of cores on the system.  How many cores do you have, and what are you setting GOMAXPROCS to?

The benchmark run at a 64 Core CPU with GOMAXPROCS settting ranging from 4 to 64, with 4 as step.
It reach ~64w QPS at GOMAXPROCS=40, and hardly improve as more are given.
However, If running in muti-process mode, such as 20 Cores per Process but with 2 Process listening on the same port, it can keep scale as perform under GOMAXPROCS<40(as close as projected data).

CC @aclements @prattmic @mknyszek


Remove debugging names info! call

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Related issues
A list of issues either fixed, containing architectural discussions, otherwise relevant
for this Pull Request.
Additional Notes
Anything else we should know when reviewing?

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1020  👈
#1019
#1017
#1016
#1015
#1012
#1011
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @blt and the rest of your teammates on  Graphite

Merge activity

Oct 2, 11:00 PM EDT: @blt merged this pull request with Graphite.


Resolve module to full implementation

This is useful so we can:

skip special Webpack configuration for ESM configuration
remove special behavior for @rollup/plugin-node-resolve and browser entries

Use browser field resolving for specific modules (e.g. Browserify module such as process use browser field) and for other rely on main/module/exports.

There are module which have multiple browser-specific entries so this can potentially be harmful.

Consider using enhanced-resolve for this.


Greenkeeper/initial

This sample code for Appium is no longer maintained or used. Please see https://github.com/appium/appium/tree/master/sample-code


Opening N64 ROMs to Mupen64 does not work

When I try to open any N64 ROM I get a "couldn't find ROM" error in Mupen64.
My ROMs are in the SD card, I already tried to re-add the path multiple times
https://user-images.githubusercontent.com/70247300/196203664-c925375c-bd0c-4f67-a5fc-18aa570708cf.mp4

So try changing file.uri with file.path in the platform settings or viceversa. Also assure that mupen64fz has storage permission

It is possible that the SAF fix might have caused some problems with newer version of mupen64fz


Errors to solve

Hi,
I am not a JS master and having a few difficulties to debug.
First there seem to be a new JS version which makes impossible to use variable between quotes.
I replaced by backtick in examples like here: https://github.com/ondrejklejch/MT-ComparEval/blob/master/app/templates/Tasks/list.latte#L20
seems good.
Next: Edit / Save a Task does not work, I am getting a nasty error:
Line 23 of TaskPresenter:
Trying to get property 'id' of non-object
$this->template->experimentId = $this->template->experiment->id;
Cn you help ?

Hi Vincent, thank you for the bug report. I fixed both issues.


Added Table of Contents

Description
Added table of contents and removed rate limiting info
Must

[ ] Tests
[X] Documentation (if applicable)

@dorsha Can we merge this now?


forEach for OrderedMap doesn't return iterator param

Consider:
Immutable.OrderedMap(...).forEach(function (item, i) {
	// Here I'm expecting 'i' to be 0, 1, 2, 3 etc...
	// However, it's actually the value of whatever the OrderedMap is keyed off
});

Why is this? In regular Javascript, when you iterate using forEach, the second param is always the iteration index.

It makes sense for Maps, and it matches the spec: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map/forEach. My question is why do you care about the index?

Ok that makes sense. I guess I'm still struggling with the different between OrderedMaps and Lists and when to use what. In my head, I way to create a collection (array) of objects (maps). In ImmutableJS it seems the best way to do this is to create an OrderedMap (a map) or Records (another map). At one point, I want to loop over the OrderedMap and render each item (say in a table). For this I need an index.
I suppose I can just use MyOrderedMap.toArray.forEach instead.

I would suggest:
var index = 0;
myOrderedMap.forEach(function (item) {
  // do what you need to do with item and index
  index += 1;
});

As this will reduce the need to build a new structure, as toArray would.
Also, you may re-evaluate your use case and prefer to use a List if your primary need is to iterate over in a specific order with incrementing indices akin to an Array. OrderedMap is designed to mirror the behavior of the native Map and in many ways is similar to the native Object. Both of these native collections are not indexed, however happen to iterate over their entries in the order in which they were inserted (insertion order). Immutable.js's unordered Map does not make this iteration ordering guarantee, but has considerably better performance at nearly all operations and lower memory usage, as maintaining insertion ordering is not free.

Another way to think of this is:
Would I usually use an Array? Use an Immutable.List.
Would I usually use an Object or ES6 Map? Use an Immutable.Map
But I need to preserve that insertion-ordering iteration order quirk JavaScript Objects have! Use an Immutable.OrderedMap

Thanks for that @leebyron. The most common use case for us are lists like this:
var collection = [{
	id: 1,
	key: 'val'
}, {
	id: 2,
	key: 'val'
}]

And our requirements are:

Good performance for looking up objects via 'id' - as that will be very common (therefore Immutable.Map is probably best)
Order of objects is important, as these objects may be reordered by the user via a UI (therefore Immutable.OrderedMap sounds better)
To allow for custom re-ordering we want ability to get the order index of an item by id, ie. User drags object id 2 into position 1, therefore we want ability to do collection.indexOf({id: 1}) to get it's index (therefore Immutable.List sounds closer to what we need).

Hence the confusion. But it sounds like OrderedMap is still the way to go for this based on what I'm reading. We'll just have to convert it to an array whenever we need index values.

Depending on how long these lists actually are, you may be better off sticking with a List and using the find method if you need to lookup by id.
Another thing you may consider is keeping both a List and Map together in parallel. Use the List when you need to work with orderings, use Map as a lookup from id to value. This is roughly how OrderedMap works.

Apologies for bringing this up again now, I was confused by this & raised a question on SO to seek clarification. My impression was that immutable.js follows closely the convention that native functions have. Ala, map & filter, forEach should also follow the convention.
In my current use-case, I need a Map, which is also used in a function to identify which of its properties has a particular value, the function returns the index of the object holding the property.
My understanding was that post for loop time, the new method to use for side-effect loop is forEach.


[Suggestion] Prefix Changer

You should make it so that we can change the prefix for example replace the prefix $ to .

Added in SongPlayer 3.0


On macOS, you can scroll away from the alternate screen in which the application is being displayed

Note: This is probably just a case of documenting the limitation, because it seem to be inherent to the terminal applications on macOS (even man's display behaves this way).
On Windows and Linux, Terminal.Gui applications render on a separate, singe-page screen (no scroll bars shown by the terminal program) that is independent of the regular terminal screen, to which you return on exiting such an application.
On macOS, you can unexpectedly use the terminal's scroll bars to scroll away from this screen, back to the previous terminal output. Seemingly just the latest "screenful" of the regular screen is overlaid with the GUI.
Example: running in iTerm.app, scrolling back up to previous terminal output while the example application is running:

Yes it happens to me too.


use deliver_now if possible in preparation for Rails 5

This fixed https://github.com/mhfs/devise-async/issues/59.

Side note: as rails 4.2 ships with activejob you can simply do this to achieve what devise-async is doing. Sooo... this kinda makes this gem obsolete (more or less, depending on your needs obviously).

This seems interesting, is it going to be merged ?

@marcgg as @emq and Devise information is pointing out its a tiny 3 line method (+ tests) that's kind of superseeds this gem. And it works very well.

@barelyknown I guess this is still somewhat useful. Could you fix the merge conflicts? Then we would be able to merge it.

@barelyknown Thanks!


Add test for plans in TiStrategy

We don't have specific plan test for TiStrategy.
Refer to spark's own plan test framework and we need something like that.

Refer to https://github.com/pingcap/tispark/pull/127

Already had tests


Calling seek fails to start playing if file has already played

When playing an audio clip, calling seek(Duration.zero) should start playing the audio again from the beginning. This works as expected if seek is called while the clip is still playing, but if the audio clip has finished playing nothing happens.

+1 on this issue, facing the same.


Running `` gives no output

What version of nocode are you using (run  )?

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using?
Ubuntu 16.04
What did you do?

What did you expect to see?

What did you see instead?

Good issue, need to fix it.

have you tried this :

you should see the following output :

I think the issue can be closed because the output is exactly the same as expected.

Operating system should be

@iamandrewluca's comment helped me diagnose the issue:
For everyone else that encounters this issue coming from google, here's what I did:
I ran this command:

If it gives the following output, it means the issue is fixed:

@zakkor Glad I could help 😀

``

``

`
`

`
`

<br/>


[Enhancement] Be able to delete actions during the recording

Feature summary
As a user of the Script Recorder
I want to be able to delete an action whilst recording
So that I can remove unnecessary browser interactions
ACs:

I can delete an action even if the recording is in progress, or paused

Why is this feature important?
When using the script recorder, one can easily click on things by mistake (e.g. identifying a selector), which creates unnecessary noise in the recording.
It’s not currently possible to delete these whilst recording, and although it is possible once the recording is stopped, it can be be difficult to remember which were the unnecessarily captured actions, once finished (i.e. it’s easier to be aware of them when the additional actions are captured rather than at the end).
Linked resources
No response
Additional information
No response

We kind of mutate the PW actions for Assertions as they are not emitted from the Playwright directly instead we generate our own when merging the actions from PW.
I think we might need to do the same for deletion as you stated here and kind follow the same approach (mark them as delete and skip it from code generation). I don't see any way around it.

I think we can amend the diffing algorithm to handle deletions as well. I think we will want to invest time in writing unit tests for this feature too because it's going to get pretty complicated.

(oops, accidentally assigned myself to post-FF test this one but I had already tested the original PR)

POST FF Testing. I can verify that user can delete actions now whilst recording.


Move import lock onto backend

Partially addresses #2532  by moving get_import_lock onto the backend, rather than exposing it through client.
Unlike the ticket suggested, this has not been moved to ImportQueue. While exposing it from there would make intuitively sense, it turns out that this would create an indirection that isn't easy to resolve. That is mostly cause by the fact that ImportQueue itself isn't "really driving" the import process, but itself is a part of that. Client, Backend and the new SelectChain are the ones, that actually care about the lock and they all share access to B: Backend. Thus, though Backend itself doesn't use the lock in this PR, it makes sense to locate it there - at the shared instance used for clearing an import. Another neat side effect of moving it there is, that we can drop the Arc and only use &Mutex as no one needs to hold it anymore but only takes the reference when needed.
This is what this PR does: it removes import_lock() from client and instead exposes get_import_lock from Backend. Note: This also provides a default implementation on the trait that uses a lazy_static Mutex for the entire instance, which simplifies the implementation (and API) of Backend.

Also bumped the parking_lot version to 0.8.0 accros the board.


Flash Alert "Slug has already been taken" When Uploading Gemfile.lock

Description
When I try to upload my Gemfile.lock file to railsbump.org, I receive a flash alert message stating "Slug has already been taken". This issue occurs even when I use a known good Gemfile.lock file from another comment in a different issue.
Steps to Reproduce

Navigate to https://www.railsbump.org/lockfiles/new.
Upload a Gemfile.lock file. For testing purposes, I used this Gemfile.lock from the fastruby/points repository.
Click on the "Check Now" button.

Expected Behavior
The Gemfile.lock file should be uploaded successfully.
The application should analyze the dependencies without any errors.
Actual Behavior
A flash alert message appears stating "Slug has already been taken".
The upload fails, and no analysis is performed.
Screenshot

Additional Context
I first encountered this issue with my own Gemfile.lock file.
To rule out any file-specific issues, I tried using a known good Gemfile.lock from this comment, but the same error occurred.
This suggests the problem is not specific to any particular Gemfile.lock file.
My browser and OS details:
Browser: Safari - Version 18.1 (206<IP_ADDRESS>.10)
Operating System: MacOS Sequoia - 15.1

@nathanberg Thanks for submitting this issue! I've found it in the past so I think it should be easy to reproduce.
I see two potential solutions: (1) Redirect to the existing slug or (2) change the way that the slug is calculated. The way it gets generated is based on the gem names: https://github.com/railsbump/app/blob/3ea9a311c1e5a6d0e6bd2cb682c6a61adb2acf4f/app/models/lockfile.rb#L45-L49
I'm inclined to go with (1) -- Thoughts?

@etagwerker I agree with your inclination of using option (1).
Really appreciate you looking into this so quickly!

@nathanberg This should now be patched in production. Thank you! 🙏🏼


Part of onvim in fullscreen is visible on a second monitor

When I fullscreen onivim, part of the window is visible on my second monitor. That's the small white stripe in the image.
When I fullscreen it again after louding it takes the color of the window. It's not possible to interact with these 10 pixels or so, they are just "bleeding" over.

Machine: Windows 10

Thanks for logging the issue, @noahhaasis - I think this is the same underlying issue @vhanla mentioned here: https://github.com/revery-ui/revery/issues/1001


period = x.shape[1] // top_list   top_list里边是frequency的 index,请问这里用时序长度/index，为何得到的是周期？？？如果/frequency似乎更容易理解，期待回复，非常感谢！

def FFT_for_Period(x, k=2):#x torch.Size([2, 31, 32]) #31?????############
[B, T, C]
xf = torch.fft.rfft(x, dim=1)#torch.Size([2, 16, 32])
find period by amplitudes
frequency_list = abs(xf).mean(0).mean(-1)#abs measures how strong the signal is
##both x and y are averaged along batch_size and along (x and y)
frequency_list[0] = 0 # common practice
_, top_list = torch.topk(frequency_list, k)#return values indexes
#_, top_list = torch.topk(frequency_list[1:], k, largest=False)#, largest=False
#pdb.set_trace()
top_list = top_list.detach().cpu().numpy()
# Get all indices and shuffle them
all_indices = np.arange(len(frequency_list[1:]))
np.random.shuffle(all_indices)
# Select the first k shuffled indices
top_list = all_indices[:k]
##用days除以頻率，確定每個k有幾個週期
period = x.shape[1] // top_list# higher index means higher frequency
#pdb.set_trace()
return period, abs(xf).mean(-1)[:, top_list]                                                                                period = x.shape[1] // top_list                                                                                top_list里边是frequency的 index,请问这里用时序长度/index，为何得到的是周期？？？如果/frequency似乎更容易理解，期待回复，非常感谢！                                             read the whole code, top_list here is index of frequency , why here x.shape[1] //top_list = period, if use frequency, it seems meaningful, but using index of frequency seems meaningless

this is gpt4's answer, is this explanation ok?                                                                                The line of code period = x.shape[1] // top_list is calculating the period of each of the highest k frequencies found in the time series data.
In the context of Fourier analysis, frequency and period are inversely related. The higher the frequency, the shorter the period, and vice versa. Since top_list contains the indices of the top k frequencies, these indices are used as a proxy for the frequencies themselves.
The reasoning behind this is that the output of the FFT function in PyTorch is ordered by increasing frequency. That is, the first component (index 0) corresponds to the lowest frequency (DC or 0 frequency), the second component (index 1) corresponds to the next higher frequency, and so on. Therefore, the index of each component in the FFT output can be seen as a representation of its frequency.
Therefore, x.shape[1] // top_list calculates the period corresponding to each of the top k frequencies. x.shape[1] corresponds to the total length of the time series data (or the total number of time steps), and // is the integer division operator in Python. Thus, the line of code is dividing the total length of the time series by each of the top k frequencies (represented by their indices) to calculate their corresponding periods.
However, this is a somewhat rough approximation, as it assumes a linear relationship between the index in the FFT output and the actual frequency, which may not always be the case, especially for longer time series or those with non-uniform sampling rates. But in many cases, especially for simple analysis or initial exploratory work, this approximation can still provide useful insights about the periodic patterns in the time series data.

but in my example,frequency_list =  tensor([0.0000, 7.2521, 2.8845, 2.9960, 5.1468, 2.2075, 4.2677, 3.7666, 3.1520,
6.1255, 4.6509, 4.9537, 3.1828, 7.7338, 7.4764, 3.3870],
device='cuda:0', grad_fn=)           then top_list = [2,2]

您好，请详细读一下torch.fft的含义：https://pytorch.org/docs/stable/generated/torch.fft.fft.html#torch.fft.fft
fft的结果只是说明了每个频率的强度，index表示频率的值。

您好，来信已收到，多谢！

非常感谢您的解释！我从中学到了很多！根据我从OpenAI的GPT-4获取的信息，我想补充一些关于torch.fft.fft函数的信息...这个函数是PyTorch库中用于计算一维离散傅立叶变换（Discrete Fourier Transform，简称DFT）的。它接收一个输入张量，返回一个与输入同形状的复数张量，这个复数张量中的每个元素都表示输入中对应频率的振幅和相位。所以，torch.fft.fft函数的输出实际上是一种频域表示，反映了输入信号在各个频率上的强度。在FFT的输出中，"频率"是由其对应的索引值（index）表示的，而每个频率的"强度"则是由该频率对应的复数值的模来表示的。然而，FFT输出的索引与实际频率之间的关系并非一对一的。在FFT输出中，索引值从0开始，到n/2（n为FFT的大小或者输入信号的长度）时，对应的频率从0Hz增加到采样频率的一半。然后，从n/2到n的索引值，对应的频率从负的采样频率的一半增加到接近0Hz。因此，虽然可以将FFT输出的索引看作是表示频率的值，但这种表示方式是基于特定的FFT大小和采样频率的，并且对于大于n/2的索引值，其实是表示负频率。
FFT输出的索引可以看作是频率的表示，而具体对应到何种频率则取决于数据的采样率和FFT的大小。同时，我也了解到，通过计算 abs(xf).mean(0).mean(-1) 得到的是所有频率分量强度的整体度量，而不是特定的频率或索引。
关于如何确定信号中最强的频率，我认为这是一个非常值得深入研究的话题，我会继续思考和探索。非常期待和大家一起讨论和交流。
再次感谢您的回答，祝您一切顺利。


Updated to work with vn3.0.5 of the cf-checker

Version number is at 3.0.1.

Dependency on CDAT (cdms) has been removed.
Added dependence on netCDF4 and cfunits libraries.

Please pull this change to conda-forge and test it integrates with other packages.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Now updated to work with v3.0.5 of cfchecker (latest release and in PyPI).

You need to update the checksum in https://github.com/conda-forge/cfchecker-feedstock/pull/5/files#diff-e178b687b10a71a3348107ae3154e44cR10

Hi @ocefpaf, The patch was needed when the cfchecker directly interacted with udunits2. However, the dependency has now moved to the cfunits package which is also part of conda-forge:
https://github.com/conda-forge/cfunits-feedstock/
I had assumed we can depend on cfunits to resolve the dependency now. Is that not right? :-)

@ocefpaf, does the patch need to be moved into cfunits - or at least a version of it moved there?

I had assumed we can depend on cfunits to resolve the dependency now. Is that not right? :-)

If the new code does not load udunits2 this is fine. However, we may need to do something like this in the cfunits package then.

@cehbrecht: just copying you in to this conversation as it might impact on the cfunits feedstock recipe.

@agstephens consider adding yourself as a maintainer for this package.

@ocefpaf: point me to where I can make myself a maintainer. Thanks
I'm getting the hang of seeing that I check the CI output myself and fix things without hassling you. Clever!

@ocefpaf: point me to where I can make myself a maintainer. Thanks

All you need to do is to add your GitHub handle in the recipe-maintainers section.

I'm getting the hang of seeing that I check the CI output myself and fix things without hassling you. Clever!

Take it to the next level and build it locally before pushing :wink:
http://conda-forge.github.io/docs/testing.html#run-docker-tests-locally-for-feedstock

@agstephens two more things before we merge this:

Can you rerender the feedstock? See http://conda-forge.github.io/docs/conda_smithy.html
It would be nice to have an actual file test. PR #4 added one, maybe we can use that or we can use a local file instead if you have a small one to commit to the repo,

@ocefpaf, thanks for accepting the PR.
I am installing conda-smithy.
Regarding point (2) about a test file. Indeed, a local file is preferable. Does the test run inside the main directory of the repo? If so, we already have gzipped ".nc" files accessible. Can a test command include two shell commands, e.g.:
 $ gunzip test_files/data.nc.gz ; cfchecks test_files/data.nc
Also, does it care about the return code? The checker returns a code for the number of problems it found in the file (but it still ran correctly). Thanks

Does the test run inside the main directory of the repo?

You need to make the test file/directory available visible to conda by adding a subsection named files in the test secton, like this

If so, we already have gzipped ".nc" files accessible. Can a test command include two shell commands, e.g.:
 $ gunzip test_files/data.nc.gz ; cfchecks test_files/data.nc

You can run as many commands as you like, but I would not add unpacking as part of the test. Just add the unpackage file, see these lines for an example.

Also, does it care about the return code? The checker returns a code for the number of problems it found in the file (but it still ran correctly). Thanks

Anything non-zero will be treated as an error.


First release of databricks.ManagedTableDataset

Description
Creating first of few PRs to add functionality for Databricks in Kedro datasets. This PR includes the ManagedTableDataset which will allow users to interface with managed Delta tables in Databricks or locally in PySpark.
Development notes
Changes include a net new dataset, databricks.ManagedTableDataSet, which allows users to interface with managed delta tables inside of Databricks.
Checklist

[x] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[ ] Added a description of this change in the relevant RELEASE.md file
[ ] Added tests to cover my changes

Thank you for creating this PR! I took a quick glance and wonder how specific this is coupled with databricks? Any chance that you checked the SparkDataSet and DeltaTableDataSet already? https://kedro.readthedocs.io/en/stable/kedro.extras.datasets.spark.DeltaTableDataSet.html


fix: #610 field alias not mapping prisma value

Per #610, Prisma model fields that specify an alias return null in the GraphQL responses. For example:
const Customer = objectType({
  type: "Customer",
  definition(t) {
    t.model.full_name({alias: "fullName"})
  }
})

The root cause appears to be that the publisher is not providing a resolver in the field config. So when we have a source record from Prisma that looks like this:
const prismaSourceObject = {
  "full_name": "Jane Smith"
}

Since no custom resolver is specified, the defaultResolver picks it up. The defaultResolver understandably tries extract that value from the source using the alias (e.g. prismaSourceObject['fullName']) when it fact it should be extracted from the source via the field name (e.g. prismaSourceObject['full_name']). Add a custom resolver appears to fix this.

I think Prisma should have some eslint/tslint, this seems to happen tad too often.


viceroy: 0.9.5 -> 0.9.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/fastly/viceroy/releases.
meta.description for viceroy is: Viceroy provides local testing for developers working with Compute@Edge
meta.homepage for viceroy is: https://github.com/fastly/Viceroy
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.6 with grep in /nix/store/mpzjn1a7gk28vzis49a3sz3kxmw2bw67-viceroy-0.9.6
found 0.9.6 in filename of file in /nix/store/mpzjn1a7gk28vzis49a3sz3kxmw2bw67-viceroy-0.9.6

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
fastly
viceroy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mpzjn1a7gk28vzis49a3sz3kxmw2bw67-viceroy-0.9.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A viceroy https://github.com/r-ryantm/nixpkgs/archive/036d7eb0e709d5d86075c7761bbdcdcc2635635e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/036d7eb0e709d5d86075c7761bbdcdcc2635635e#viceroy

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mpzjn1a7gk28vzis49a3sz3kxmw2bw67-viceroy-0.9.6
ls -la /nix/store/mpzjn1a7gk28vzis49a3sz3kxmw2bw67-viceroy-0.9.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages built:

fastly
viceroy

Maintainer pings
cc @ereslibre @shyim for testing.

Result of nixpkgs-review pr 302603 run on x86_64-linux 1

2 packages built:

fastly
viceroy


ci: release darwin arm64 build

Is your feature request related to a problem? Please describe.
Only an amd64 release is included for darwin
Describe the solution you'd like
It would be great to have a native arm64 release included, though I haven't had any issues running the current darwin build with Rosetta
Additional context
Related: asdf-community/asdf-cue#20
It does appear that goreleaser supports this target as of v0.157.0, Go 1.16

Hi @spencergilbert welcome to the CUE project!
Thanks for raising this. @caarlos0 kindly contributed https://github.com/cue-lang/cue/commit/370fac9b49332b5c22cba6731e539925e0215e29 recently which should address this in the next release.
On the basis I'll close this issue, but please shout if there's anything I've missed in that conclusion.

Dang, I searched issues and didn't see anything, I swear GitHub search never works for me.
Thanks!

GitHub search never works for me.

It's funny you say that, because I also struggle. Instead I tend towards using a Google search with site:github.com/cue-lang/cue as part of the search condition. But for some reason that I am following up with GitHub, that is not working for CUE's new home. So I'm limited to GitHub search too these days!


Please update react-jPlayer to support react-redux version 6.x and above

Any known fix for this?

@MartinDawson @Mattomanka hey, i am wondering if you are planning to update react-jPlayer  & react-jPlaylist to support react 16 +  and react redux 6 + versions

@MartinDawson @Mattomanka hey, i am wondering if you are planning to update react-jPlayer  & react-jPlaylist to support react 16 +  and react redux 6 + versions

@iholovach-amplify I recommend not using this package and use another react player.
I am no longer using it or updating it. If someone else wants to take over the contributions to the package then they can.

@iholovach-amplify I recommend not using this package and use another react player.
I am no longer using it or updating it. If someone else wants to take over the contributions to the package then they can.

@singhjagmohan1000 @isautkin-nv hey, looks that one easy way to fix it just remove react, redux, react-redux  dependencies from dependencies in reacy-jplaylist, react-jplayer and react-jplayer-utils libs
(but live in devDependencies)
so in such case it will use you aplications libs versions without any problems
@MartinDawson hey, if this fix works for you, could you please create 3 PRS to remove those dependencies?


Setup code coverage report

Never tried this sort of thing before, so have to reasearch exactly what they do, why they're useful, and how/if to fit them in the environment.

After some reseach (gcov vs lcov vs bcov vs kcov), I'll be adding support for gcov. kcov seems interesting for interactive use (directly creates the report index.html file), but gcov seems better-known and is supported by CMake.


exchange variable value without a deploy

I written a simple node with a button and a textbox in node-red.
Now i try to put out the value from the textbox, in a console (server side) with a click on a button(client side/node-red).
But i find no way to do this without using the 'Deploy-Button'.
Has anyone an ideer to do this with the node-red api or with ajax?

HI, for questions like this please use the mailing list, linked at the bottom of nodered.org

Please use the mailing list for how to type questions-
https://groups.google.com/forum/#!forum/node-red


Cant initialize function filemanager('image') for standalone button from layout view with child views

Please help...
In my laravel porject
I include <script src="/vendor/laravel-filemanager/js/lfm.js"></script>  on my layout view
and called $('#lfm').filemanager('image'); after inside a $(document).ready(function(){});
Im sure that
-jquery was loaded before
-the view (childview) that contains the html extends the layout
the plugin will work only if i import the lfm.js inside the childview and call the function after.

@johnguild Is there any errors in console?

Says filemanager is not a function
jQuery.Deferred exception: $(...).filemanager is not a function TypeError: $(...).filemanager is not a function
    at HTMLDocument.<anonymous> (http://myproject.dev/js/custom.js:69:12)
    at j `(http://myproject.dev/js/jquery-3.1.1.min.js:2:29948)`
    at k (http://myproject.dev/js/jquery-3.1.1.min.js:2:30262) undefined
r.Deferred.exceptionHook @ jquery-3.1.1.min.js:2
k @ jquery-3.1.1.min.js:2
jquery-3.1.1.min.js:2 Uncaught TypeError: $(...).filemanager is not a function
    at HTMLDocument.<anonymous> (custom.js:69)
    at j (jquery-3.1.1.min.js:2)
    at k (jquery-3.1.1.min.js:2)

As i mention above it will work once i import the js and call the function inside my childview, i could work with that way, however it would be great if it can be called and use inside the layout page.

Are you using Blade or Jade or Pug for your template engine?
Please paste the code of your view here.

I found the issue.
In the layout view the
<script src="/vendor/laravel-filemanager/js/lfm.js"></script>
should be called after the default
<script src="/js/app.js"></script>
of laravel
For some reason having this
`
`
will throw an error
app.js:3 jQuery.Deferred exception: $(...).filemanager is not a function TypeError: $(...).filemanager is not a function     at HTMLDocument.<anonymous> (http://site.dev/testing:48:17)     at c (http://site.dev/js/app.js:3:14745)     at l (http://site.dev/js/app.js:3:15060) undefined gt.Deferred.exceptionHook @ app.js:3 l @ app.js:3 app.js:3 Uncaught TypeError: $(...).filemanager is not a function     at HTMLDocument.<anonymous> (testing:48)     at c (app.js:3)     at l (app.js:3)

Understood.
I guess jQuery is contained in app.js.
Glad you found it out.


Issue 289 clarify js globals

Addresses #289.
Add LookupButton static vars:
  static TERM_FORM_CONTAINER = null;
  static TERM_DICTS = null;
  static LANG_ID = null;

The existing code creates global vars in a few places (either with let or const), and the LookupButton class uses these globals.  Declaring them static clarifies the intent of the variables, removes any ambiguity, and moves declaration into one place.
Many changed lines just add the LookupButton name to the var, eg TERM_DICTS becomes LookupButton.TERM_DICTS.

Launched in 3.2.4.


fix change in request/time meaning introduced by d2c729a, fixes #1102

LGTM

Though, it would be nice if there were a way to unit test that it sends the value after everything has been consumed...  Might not be something for today, but if we are ever doing surgery on this code, something we should think about.


Multiples improvements: share, config, requirements

Codecov Report
Attention: Patch coverage is 48.06867% with 121 lines in your changes are missing coverage. Please review.

Project coverage is 56.34%. Comparing base (6abe945) to head (aa7eb07).

Files
Patch %
Lines

src/Analyzer/RequirementsEvaluator.go
0.00%
66 Missing :warning:

src/Engine/Php/PhpVisitor.go
57.89%
17 Missing and 7 partials :warning:

src/Command/AnalyzeCommand.go
18.75%
11 Missing and 2 partials :warning:

src/Command/InitConfigurationCommand.go
0.00%
10 Missing :warning:

src/Configuration/ConfigurationLoader.go
87.30%
4 Missing and 4 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #42      +/-   ##
==========================================
- Coverage   57.30%   56.34%   -0.97%
==========================================
  Files          39       42       +3
  Lines        2949     3152     +203
==========================================
+ Hits         1690     1776      +86
- Misses       1067     1173     +106
- Partials      192      203      +11

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


Fizz buzz

Level 0 and 1 of the fizzbuzz test

This branch is intentionally left in conflict state. A rebased version is at https://github.com/anuragaw/cloudstack/pull/2

Will review #2, the point of the review exercise to show the kind of review we do at ACS


How to differentiate between HMR change on template vs script

Related plugins

[X] plugin-vue

[ ] plugin-vue-jsx

Description
Hi there,
For the TresJS library, we need to dispose of 3D scene objects on HMR, the problem is that right now we have no way of differentiating whether the change came from the <template> or from <script>.
  if (import.meta.hot) {
    import.meta.hot.on('vite:beforeUpdate', context => {
      console.log('vite:beforeUpdate', context)
      scene.value.remove(instance)
    })

    import.meta.hot.on('vite:afterUpdate', context => {
      console.log('vite:afterUpdate', context)
      instance = createInstance(threeObj, attrs, slots)
      processProps(attrs, instance)

      if (instance.isObject3D) {
        scene?.value.add(instance)
      }
    })
  }

The problem is that this code works well when the change comes from the template, but if the change comes from the script tag the creation of 3D instances is loaded again, causing duplicate objects on the scene
I checked the value coming from both vite:beforeUpdate and vite:afterUpdate but I don't see any info that could help me differentiate between both
{
    "type": "update",
    "updates": [
        {
            "type": "js-update",
            "timestamp":<PHONE_NUMBER>707,
            "path": "/src/components/TheEvents.vue",
            "explicitImportRequired": false,
            "acceptedPath": "/src/components/TheEvents.vue"
        }
    ]
}

Suggested solution
Maybe return a property with the origin of the change?  Like so
{
    "type": "update",
    "updates": [
        {
            "type": "js-update",
            "timestamp":<PHONE_NUMBER>707,
            "path": "/src/components/TheEvents.vue",
             "block": "template"
            "explicitImportRequired": false,
            "acceptedPath": "/src/components/TheEvents.vue"
        }
    ]
}

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Possible Solution  https://github.com/vitejs/vite/issues/12097

I guess you can differentiate the update by checking _rerender_only variable.
https://github.com/vitejs/vite-plugin-vue/blob/2050ad3dc568b4d051d19611aad34693e9a917ec/packages/plugin-vue/src/main.ts#L146-L164

@alvarosabu
Does the above solution solve your problem?

Hi there @edison1105 the truth is that I haven't yet tried it out the solution @sapphi-red proposed. I will give it a try. Thanks


[Bug]: [Sentry] AppsmithPluginException   com.internal.helpers.DataUtils in parseJsonBody | CLOUD-SERVICES-8

Is there an existing issue for this?

[X] I have searched the existing issues

Description
https://appsmith.sentry.io/issues/4303630673/
Steps To Reproduce
NA
Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Cloud

Checked out this issue briefly, it looks like a legit issue from user's end, where the JSON is not in the correct format. Also looking at sentry, the issue has occurred only for this 1 user for 819 times, In such case:

We can either reach out to this user, if possible, to help them correct the JSON formatting for this specific action
Or we can suppress this event on sentry as it's a legit issue in JSON

CC: @rohan-arthur

Closing this as this is a user issue. Also the occurrences are limited.

reopening this issue because it is a valid error for malformed json, we should not be logging to sentry.

From the sentry logs, it seems that this issue is only occurring for the Airtable plugin.
This is evident from the response structure.

Closing this as completed in https://github.com/appsmithorg/cloud-services/pull/1564


Release/1.4.0 beta.1

Coverage increased (+0.04%) to 68.25% when pulling 3ee67fdd41115c869aede238c3b9d9be417ec3f7 on release/1.4.0-beta.1 into 84c1c070ebdfeeb9d4e63d9809cff90fa0cf596e on develop.

Failing due to hitting job limit again. 😞


Fix Docker CI workflow

As we are triggered by the PyPI workflow and not directly by the push of the Git tag, extracting the version from GITHUB_REF_NAME won't work. Calling git describe instead also allows the workflow to be run manually, which makes things easier in general.
Fixes: #118

Test run: https://github.com/UpstreamDataInc/goosebit/actions/runs/10710072820


Remove leftover of tripleoclient image

This removes the file which should have been removed by the previous commit[1].
[1] 2bed4991d78bedf010f24fd7bae2b9883e64ea64.

/lgtm


no download version 5.6(

[InvalidArgumentException]
Package halaxa/json-machine at version  has a PHP requirement incompatible
with your PHP version (5.3.28)
error composer. Help me please
my version php 5.6.36

Is this message from composer? It says zour PHP version is 5.3.28. Are you sure you're running the version you think you run?

правильно вы говорите 5.3.28 в консоли выдает. А на странице  выдает PHP Version 5.6.36. Ничего не понимаю(

correctly you say 5.3.28 in the console issues. And on the page  Produces PHP Version 5.6.36. I don’t understand anything (

Your version in console and in web server may differ. Especially if you install PHP manually. I'd suggest to read some tutorial on PHP installation on your platform.

Thank! I will sort this out


Vscode does not support PYQT5 automotical prompt ?

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.64.2
OS Version: WIN10

Steps to Reproduce:

install pyqt5
the ide dont have any help mesassgers when I was coding.

Thanks for the report. Are you looking for completions as you type?

do you have a code example?
i'm seeing some completions

most likely you'll need to file a bug with pyqt5
https://www.riverbankcomputing.com/software/pyqt/


Chatterino freezes when you turn on mod mode for the first time.

Describe the bug
Chatterino freezes for less than a second when you turn on mod mode for the first time.
To reproduce
Turn off mod mode in every tab opened
Restart chatterino.
You should see the the freezing when you turn it on again.
Chatterino version
Chatterino Nightly 2.2.3-beta2 (commit e00938dfd, )
Operating system
Windows 10

Unable to reproduce.
Chatterino 2.2.3-beta2 (commit f9246a9e3)
Arch Linux, Linux Zen 5.11.11-zen1

Unable to reproduce.
Chatterino Nightly 2.3.3 (commit 4dee7ad7, )
Windows 8.1
Does this still happen?
Otherwise I will close this.

Yes, it still happens.... at least to me. I asked a few people that run windows too and none of them could reproduce it! I have no idea why it only happens to me.
But at least I was able to find a more reliable way to reproduce it. As you can see in the screenshot, Chatterino only freezes and becomes unresponsive exactly when you try to load a normal user's message that has the moderation buttons next to their username. (not a mod or a broadcaster)

Chatterino Nightly 2.3.4 (commit f74b2770, )
Windows 10 Pro (20H2)

Cannot reproduce
Chatterino 2.3.4 (commit 4e5170799)
Windows 10 Pro (21H1)


Add RedactedEnv function to utils package

This PR adds a RedactedEnv function to util package for relaxing terraform output to redact only hex values.

Codecov Report
Patch coverage: 70.58% and project coverage change: +0.21 :tada:

Comparison is base (760a9e6) 38.08% compared to head (151175e) 38.29%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #394      +/-   ##
==========================================
+ Coverage   38.08%   38.29%   +0.21%
==========================================
  Files          49       49
  Lines        2920     2935      +15
==========================================
+ Hits         1112     1124      +12
- Misses       1688     1691       +3
  Partials      120      120

Impacted Files
Coverage Δ

pkg/environment/environmentApply.go
15.00% <0.00%> (ø)

pkg/util/util.go
60.67% <80.00%> (+3.91%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Site: Plans

Define structure to save payment plan user chosen.
For all current people use free plan with its limits.
Paid plans mark as "Coming soon" or "Contact us".

Currently, add limitations for free plan. Then think about paid plans.

So I made limits for free plan and now every one has free plan. Because we don't handle payments yet.


Is there a Swfit 3.0 version?

 See:
https://github.com/steadicat/Advance/network
To use them, for pod, just specify the git location, e.g.
pod 'Advance', :git => 'https://github.com/steadicat/Advance.git'  #swift3 fork for Advance
It is still the best if the main project get updated.

Alright, I went ahead and created a pull request for Swift 3 support (#18). @joeldev or @timdonnelly, you there? :)

Thanks @steadicat

@timdonnelly I don't see version 0.9.2 on Cocoapods although the podspec file is up to date, did you forgot to update it on https://github.com/CocoaPods/Specs ?

Closed?

Cocoapods is still on 0.9.1, can you update?

+1


add automatic PyPI upload on creation of github release and separate changelog

closes #38 (separate CHANGELOG.rst)
closes #91 (automate release)

ToDo:

add PYPI_API_TOKEN to project secrets

@shoyer PyPI allows us to create an API Token for uploading. I've created one such token with h5netcdf-scope under my account (thanks for adding me there). Now we would need to place this token in the h5netcdf repo secrets. Seems that I'm not able to add the secret with my current role permissions.

@kmuehlbauer This looks great! You should have permission to add repo secrets now.

@shoyer Great, the secret is in place now. I'm going to merge this PR and #92 by tomorrow if you are OK with that.

@shoyer Great, the secret is in place now. I'm going to merge this PR and #92 by tomorrow if you are OK with that.

Sounds good to me!


vSphere/ESXi 7.0 VM provisioning that requires modifying the VM properties fails (Ie adding devices)

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Create a vSphere node template containing multiple networks. Use this template to provision a cluster to a vSphere 7 & ESXi7 environment
Result:
The following is presented in vSphere and the node fails to provision. Note, single NIC nodes provision without issue.

Other details that may be helpful:
Trace logs from Rancher (However, these don't add anything extra)
2020/06/25 12:40:52 [INFO] [node-controller-rancher-machine] (m1-1) Adding network: /Homelab/network/VDS-MGMT-DEFAULT
2020/06/25 12:40:52 [TRACE] REST UPDATE apis/management.cattle.io/v3/c-9nsw7/nodes/m-lwljm
2020/06/25 12:40:52 [DEBUG] stdout: (m1-1) Adding network: /Homelab/network/VDS-NEST-DEFAULT
2020/06/25 12:40:52 [INFO] [node-controller-rancher-machine] (m1-1) Adding network: /Homelab/network/VDS-NEST-DEFAULT
2020/06/25 12:40:52 [TRACE] REST UPDATE apis/management.cattle.io/v3/c-9nsw7/nodes/m-lwljm

2020/06/25 12:40:55 [TRACE] REST UPDATE apis/management.cattle.io/v3/c-9nsw7/nodes/m-lwljm
2020/06/25 12:40:55 [TRACE] NodeController calling handler rke-worker-upgrader c-9nsw7/m-lwljm
2020/06/25 12:40:55 [ERROR] NodeController c-9nsw7/m-lwljm [node-controller] failed with : Error creating machine: Error in driver during machine creation: A specified parameter was not correct: deviceChange[1].device.key
2020/06/25 12:40:55 [TRACE] NodeController calling handler cluster-provisioner-controller c-9nsw7/m-lwljm
2020/06/25 12:40:55 [TRACE] NodeController calling handler cluster-stats c-9nsw7/m-lwljm
2020/06/25 12:40:55 [TRACE] NodeController calling handler nodepool-provisioner c-9nsw7/m-lwljm
2020/06/25 12:40:55 [TRACE] NodeController calling handler node-controller c-9nsw7/m-lwljm
2020/06/25 12:40:55 [TRACE] NodeController calling handler rke-worker-upgrader c-9nsw7/m-lwljm
2020/06/25 12:40:55 [TRACE] NodeController c-9nsw7/m-lwljm completed with dropped err: [node-controller] failed with : Error
2020/06/25 12:40:55 [DEBUG] Triggering auth refresh on u-4r7xs

vCenter VPXD logs (Note the key as -1 for both vNICs)
2020-06-25T13:20:04.116Z info vpxd[10851] [Originator@6876 sub=Default opID=97e94a2-01] [VpxLRO] -- ERROR lro-1115251 -- vm-8840 -- vim.VirtualMachine.reconfigure: vmodl.fault.InvalidArgument:
--> Result:
--> (vmodl.fault.InvalidArgument) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "com.vmware.vim.vpxd.vmprov.duplicateDeviceKey",
-->          arg = <unset>,
-->          message = <unset>
-->       }
-->    ],
-->    invalidProperty = "deviceChange[1].device.key"
-->    msg = ""
--> }
--> Args:
-->
--> Arg spec:
--> (vim.vm.ConfigSpec) {
-->    changeVersion = <unset>,
-->    name = <unset>,
-->    version = <unset>,
-->    createDate = "2020-06-25T13:20:00.543008Z",
-->    uuid = <unset>,
-->    instanceUuid = <unset>,
-->    npivNodeWorldWideName = <unset>,
-->    npivPortWorldWideName = <unset>,
-->    npivWorldWideNameType = <unset>,
-->    npivDesiredNodeWwns = <unset>,
-->    npivDesiredPortWwns = <unset>,
-->    npivTemporaryDisabled = <unset>,
-->    npivOnNonRdmDisks = <unset>,
-->    npivWorldWideNameOp = <unset>,
-->    locationId = <unset>,
-->    guestId = <unset>,
-->    alternateGuestName = <unset>,
-->    annotation = <unset>,
-->    files = (vim.vm.FileInfo) null,
-->    tools = (vim.vm.ToolsConfigInfo) null,
-->    flags = (vim.vm.FlagInfo) null,
-->    consolePreferences = (vim.vm.ConsolePreferences) null,
-->    powerOpInfo = (vim.vm.DefaultPowerOpInfo) null,
-->    numCPUs = <unset>,
-->    vcpuConfig = <unset>,
-->    numCoresPerSocket = <unset>,
-->    autoCoresPerSocket = <unset>,
-->    memoryMB = <unset>,
-->    memoryHotAddEnabled = <unset>,
-->    cpuHotAddEnabled = <unset>,
-->    cpuHotRemoveEnabled = <unset>,
-->    virtualICH7MPresent = <unset>,
-->    virtualSMCPresent = <unset>,
-->    deviceChange = (vim.vm.device.VirtualDeviceSpec) [
-->       (vim.vm.device.VirtualDeviceSpec) {
-->          operation = "add",
-->          fileOperation = <unset>,
-->          device = (vim.vm.device.VirtualVmxnet3) {
-->             dynamicProperty = <unset>,
-->             key = -1,
-->             deviceInfo = (vim.Description) null,
-->             backing = (vim.vm.device.VirtualEthernetCard.DistributedVirtualPortBackingInfo) {
-->                port = (vim.dvs.PortConnection) {
-->                   switchUuid = "50 3b f7 94 0f 8f 73 20-24 0f a4 38 2b 85 b7 c9",
-->                   portgroupKey = "dvportgroup-27",
-->                   portKey = <unset>,
-->                   connectionCookie = <unset>
-->                }
-->             },
-->             connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
-->             slotInfo = (vim.vm.device.VirtualDevice.BusSlotInfo) null,
-->             controllerKey = <unset>,
-->             unitNumber = <unset>,
-->             addressType = <unset>,
-->             macAddress = <unset>,
-->             wakeOnLanEnabled = <unset>,
-->             resourceAllocation = (vim.vm.device.VirtualEthernetCard.ResourceAllocation) null,
-->             externalId = <unset>,
-->             uptCompatibilityEnabled = <unset>
-->          },
-->          profile = <unset>,
-->          backing = (vim.vm.device.VirtualDeviceSpec.BackingSpec) null
-->       },
-->       (vim.vm.device.VirtualDeviceSpec) {
-->          operation = "add",
-->          fileOperation = <unset>,
-->          device = (vim.vm.device.VirtualVmxnet3) {
-->             dynamicProperty = <unset>,
-->             key = -1,
-->             deviceInfo = (vim.Description) null,
-->             backing = (vim.vm.device.VirtualEthernetCard.DistributedVirtualPortBackingInfo) {
-->                port = (vim.dvs.PortConnection) {
-->                   switchUuid = "50 3b f7 94 0f 8f 73 20-24 0f a4 38 2b 85 b7 c9",
-->                   portgroupKey = "dvportgroup-48",
-->                   portKey = <unset>,
-->                   connectionCookie = <unset>
-->                }
-->             },
-->             connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
-->             slotInfo = (vim.vm.device.VirtualDevice.BusSlotInfo) null,
-->             controllerKey = <unset>,
-->             unitNumber = <unset>,
-->             addressType = <unset>,
-->             macAddress = <unset>,
-->             wakeOnLanEnabled = <unset>,
-->             resourceAllocation = (vim.vm.device.VirtualEthernetCard.ResourceAllocation) null,
-->             externalId = <unset>,
-->             uptCompatibilityEnabled = <unset>
-->          },
-->          profile = <unset>,
-->          backing = (vim.vm.device.VirtualDeviceSpec.BackingSpec) null
-->       }
-->    ],
-->    cpuAllocation = (vim.ResourceAllocationInfo) null,
-->    memoryAllocation = (vim.ResourceAllocationInfo) null,
-->    latencySensitivity = (vim.LatencySensitivity) null,
-->    cpuAffinity = (vim.vm.AffinityInfo) null,
-->    memoryAffinity = (vim.vm.AffinityInfo) null,
-->    networkShaper = (vim.vm.NetworkShaperInfo) null,
-->    cpuFeatureMask = <unset>,
-->    extraConfig = <unset>,
-->    swapPlacement = <unset>,
-->    bootOptions = (vim.vm.BootOptions) null,
-->    vAppConfig = (vim.vApp.VmConfigSpec) null,
-->    ftInfo = (vim.vm.FaultToleranceConfigInfo) null,
-->    repConfig = (vim.vm.ReplicationConfigSpec) null,
-->    vAppConfigRemoved = <unset>,
-->    vAssertsEnabled = <unset>,
-->    changeTrackingEnabled = <unset>,
-->    firmware = <unset>,
-->    maxMksConnections = <unset>,
-->    guestAutoLockEnabled = <unset>,
-->    managedBy = (vim.ext.ManagedByInfo) null,
-->    memoryReservationLockedToMax = true,
-->    nestedHVEnabled = <unset>,
-->    vPMCEnabled = <unset>,
-->    scheduledHardwareUpgradeInfo = (vim.vm.ScheduledHardwareUpgradeInfo) null,
-->    vmProfile = <unset>,
-->    messageBusTunnelEnabled = <unset>,
-->    crypto = (vim.encryption.CryptoSpec) null,
-->    migrateEncryption = <unset>,
-->    sgxInfo = (vim.vm.SgxInfo) null,
-->    ftEncryptionMode = <unset>,
-->    guestMonitoringModeInfo = (vim.vm.GuestMonitoringModeInfo) null
--> }
2020-06-25T13:20:04.116Z info vpxd[10851] [Originator@6876 sub=vpxLro opID=97e94a2] [VpxLRO] -- FINISH task-3072
2020-06-25T13:20:04.116Z info vpxd[10851] [Originator@6876 sub=Default opID=97e94a2] [VpxLRO] -- ERROR task-3072 -- vm-8840 -- vim.VirtualMachine.reconfigure: vmodl.fault.InvalidArgument:
--> Result:
--> (vmodl.fault.InvalidArgument) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "com.vmware.vim.vpxd.vmprov.duplicateDeviceKey",
-->          arg = <unset>,
-->          message = <unset>
-->       }
-->    ],
-->    invalidProperty = "deviceChange[1].device.key"
-->    msg = ""
--> }

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
Installation option (single install/HA):

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version):

vSphere IaaS
2vCPU 4GB Ram
N/A - Cluster does not provision

Docker version (use docker version):

N/A - Cluster does not provision

Useful
Info

Versions
Rancher v2.4.3 UI: v2.4.22

Route
undefined

Possibly related: https://github.com/rancher/rancher/issues/25404

I also have the same problem with all the recent versions of Rancher include the latest as of today.  Tried with vCenter 7.0:
A specified parameter was not correct: deviceChange[1].device.key Cannot add multiple devices using the same device key..

我对Rancher的所有最新版本（包括今天的最新版本）也有同样的问题。尝试使用vCenter 7.0：
A specified parameter was not correct: deviceChange[1].device.key Cannot add multiple devices using the same device key..

yeah，My situation is the same as you, using rancheros-vmware.iso to create a host template. Then vpshere creates a new cluster and reports the same error as you in vcenter。

@albal @ipyker
Can you please post your node template configurations?

Here is my node template configuration:
`
None
Not available
Not available
Not available
admin Log Out
{
"amazonec2Config": null,
"annotations": {
"ownerBindingsCreated": "true"
},
"baseType": "nodeTemplate",
"cloudCredentialId": "cattle-global-data:cc-567c5",
"created": "2020-06-30T10:45:12Z",
"createdTS":<PHONE_NUMBER>000,
"creatorId": "user-b8ljz",
"driver": "vmwarevsphere",
"engineInstallURL": "https://releases.rancher.com/install-docker/19.03.sh",
"engineRegistryMirror": null,
"id": "cattle-global-nt:nt-pcs4v",
"labels": {
"cattle.io/creator": "norman"
},
"links": {
"nodePools": "…/v3/nodePools?nodeTemplateId=cattle-global-nt%3Ant-pcs4v",
"nodes": "…/v3/nodes?nodeTemplateId=cattle-global-nt%3Ant-pcs4v",
"self": "…/v3/nodeTemplates/cattle-global-nt:nt-pcs4v",
"update": "…/v3/nodeTemplates/cattle-global-nt:nt-pcs4v"
},
"name": "vCenter",
"principalId": "local://user-b8ljz",
"state": "active",
"transitioning": "no",
"transitioningMessage": "",
"type": "nodeTemplate",
"useInternalIpAddress": true,
"uuid": "c6c04403-babe-11ea-9ae4-0242ac110002",
"vmwarevsphereConfig": {
"boot2dockerUrl": "",
"cfgparam": [
"disk.enableUUID=TRUE"
],
"cloneFrom": "/TSEW/vm/Docker-Template",
"cloudConfig": "#cloud-config",
"cloudinit": "",
"contentLibrary": "",
"cpuCount": "4",
"creationType": "template",
"customAttribute": null,
"datacenter": "/TSEW",
"datastore": "/TSEW/datastore/HDD_RAID10",
"datastoreCluster": "",
"diskSize": "20000",
"folder": "/TSEW/vm/Kube",
"hostsystem": "/TSEW/host/Lab/<IP_ADDRESS>",
"memorySize": "8192",
"network": [
"/TSEW/network/10G"
],
"pool": "/TSEW/host/Lab/Resources",
"sshPassword": "tcuser",
"sshPort": "22",
"sshUser": "docker",
"sshUserGroup": "staff",
"tag": null,
"username": "",
"vappIpallocationpolicy": "fixedAllocated",
"vappIpprotocol": "IPv4",
"vappProperty": [ 5 items
"guestinfo.dns.servers=${dns:/TSEW/network/10G}",
"guestinfo.dns.domains=${searchPath:/TSEW/network/10G}",
"guestinfo.interface.0.ip.0.address=ip:/TSEW/network/10G",
"guestinfo.interface.0.ip.0.netmask=${netmask:/TSEW/network/10G}",
"guestinfo.interface.0.route.0.gateway=${gateway:/TSEW/network/10G}"
],
"vappTransport": "com.vmware.guestInfo",
"vcenter": "",
"vcenterPort": "443"
}
}`

Same issue here:
I'm using rancher v2.4.5 and vCenter 7.
The user I'm using in the Cloud Credentials has admin rights on the vSphere Cluster.
Using boot2docker with the rancheros image.
All information in the NodeTemplate seems to be valid.
When I create a cluster (single node with all roles) with the node template, rancher creates the virtual machine but is not able to add a network adapter and the CD Drive to mount the rancherOS image. Instead there is this error message popping out in vSphere: "A specified parameter was not correct: deviceChange[1].device.key Cannot add multiple devices using the same device key"
With rancher v2.3.2 and vSphere 6.5 it was working.

Here is my node template:
nodetemplate.txt

I can confirm v2.3.2 does not work with vSphere 7.0 either.

In some circumstances, It works with Rancher 2.4.5 and vSphere 7. Where I currently see it fail is when:

Multiple instances of a device type are added to a VM (ie multiple NICS)
Instances launched with boot2docker
(Possibly) modification of existing VM resources.

CC @luthermonson

This is still an issue with Rancher v.2.4.7

Have been able to reproduce this issue with vanilla Docker-Machine (https://github.com/docker/machine). It looks like there might be a compatibility issue upstream with vSphere 7.

Still the same issue with Rancher v2.5.0 and v.2.5.1 - it seems this won't be fixed.  I am struggling to find any documentation on how to create a vCenter VM template which would be suitable for the "Deploy from template: Data Center" in node-templates - can someone point me in the right direction?

Still the same issue with Rancher v2.5.0 and v.2.5.1 - it seems this won't be fixed. I am struggling to find any documentation on how to create a vCenter VM template which would be suitable for the "Deploy from template: Data Center" in node-templates - can someone point me in the right direction?

Are you referring to just making a VM Template and not really related to the issue discussed in this thread? If so, what I ended up doing was just grabbing an Ubuntu cloud-image from: https://cloud-images.ubuntu.com/ (OVA is an option), deploy that to vCenter, then convert that VM to a template and boom.
I then have the cloud-init file in the node template install any additional packages I need that is not included by default (nfs-common for instance) and add a service account I can use to sign into the node with (separate from the ssh user Rancher adds for it's use)

Still the same issue with Rancher v2.5.0 and v.2.5.1 - it seems this won't be fixed. I am struggling to find any documentation on how to create a vCenter VM template which would be suitable for the "Deploy from template: Data Center" in node-templates - can someone point me in the right direction?

Are you referring to just making a VM Template and not really related to the issue discussed in this thread? If so, what I ended up doing was just grabbing an Ubuntu cloud-image from: https://cloud-images.ubuntu.com/ (OVA is an option), deploy that to vCenter, then convert that VM to a template and boom.
I then have the cloud-init file in the node template install any additional packages I need that is not included by default (nfs-common for instance) and add a service account I can use to sign into the node with (separate from the ssh user Rancher adds for it's use)

Thanks so much for this extremely useful info cloud-image , rancher has lots of problems to provision ubuntu from vmware template by manually installed.
Confirm that provisioning kubernetes cluster on vSphere successfully with following specifications :

rancher 2.5.1
vSphere 7.0 U1
ubuntu-bionic-18.04-cloudimg

On the subject of VM templates:
As previously discussed the cloud-image templates work well. Additionally, consider using packer to create templates (https://github.com/David-VTUK/Rancher-Packer).
The main bit is to ensure cloud-init is in a state accepting of new instance-metadata. Typically this involves "cleaning" cloud-init in your template (the aforementioned Packer templates do this by default, ie:)
# Reset any existing cloud-init state
#
cloud-init clean -s -l

The cloud-image template does this by default I believe.
On the subject of vSphere 7 support:
We're working on it, but unfortunately we cannot share an ETA at this time
As a workaround (admittedly, not ideal:)
Try to configure your template to mimic the desired end configuration state in terms of attached port groups. Currently, I can get it to work cloning a VM template with the desired port group already attached.

@albal @agepi477 @ipyker - Would you be willing to test an experimental version of Rancher that we have modified to address vSphere 7, please?
If so, on any machine with Docker:
docker run -d --restart=unless-stopped \
  -p 80:80 -p 443:443 \
  --privileged \
  rancher/rancher:v2.4-head

Log into Rancher
Configure Cloud Credential and Node Template
Attempt to create a cluster

I did some quick testing, and it all came up (using a template generated via Packer (David-VTUK/Rancher-Packer).
I'll test pvc with a vsphere backend to ensure it does what it should.

Works for me now @DH-Rancher - version v2.4-4037-head reported in the UI.  Created the credentials, added a new single node cluster using boot2docker.  Thank you very much.

Thank you very much @systemmonkey42 @albal

v2.4-head, v2.5-head, master-head tested in this issue: https://github.com/rancher/rancher/issues/29519#issuecomment-712872322

Tested on 2.5.2 with vApp properties and It fails to add IP address.

@aledr - Are there any errors reported in vSphere,?
Are you using the vapp properties in combination with a cloud-init script to set the IP address of a node?

No errors on vSphere.
Only vApp without cloud-init script personalization.
I see only IPv6 at the Virtual Machine status at vSphere.
At Rancher I see "Waiting for SSH to be available." and then "Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded".

@aledr - I'd say in that instance it isn't a vSphere 7 issue as addressed by this GH issue. If vSphere is only reporting the ipv6 address of the VM then the IPv4 properties haven't been set, which may indicate a configuration issue.
Can you please raise a separate GH issue for this and/or mention this in the community slack channel (https://slack.rancher.io/) and we'll dig into this further.
It may be as simple as the cloud-init script referencing the wrong interface name.


eq.deep

right now eq is a strict equality check. eq.deep would be a deep strict equality check
eq.deep(identity, { a: 1, b: 2, c: 3 })({ a: 1, b: 2, c: 3 }) // true

Is using an npm module a respected solution?

I'd like to stick to being dependency free.. for now. I would prefer having an own implementation to iterate on.

duplicate of https://github.com/a-synchronous/rubico/issues/207


Better error message for an easy mistake to make

If people put the impl pallet_xxx::Config for Runtimes in impl_runtime_apis! then at the moment there's an error saying to rename Config trait so that the ids do not clash, but the Config traits should not be in there, so this error message makes it clear what mistake the user has made and how to fix it:
Compiling test-runtime v0.1.0 (/Users/bit/p/substrate/test/runtime)
  error: Config trait implementations should be outside the impl_untime_apis! macro.
     --> /Users/bit/p/substrate/test/runtime/src/lib.rs:569:23
      |
  569 | impl pallet_offences::Config<Block> for Runtime {
      |                       ^^^^^^

also find this a bit over the top. It think the difference between:

impl pallet::Config for Runtime
impl pallet::SomeAPI for Runtime

have you actually heard that people make this mistake often? Also if an API is called Config then what?

I managed to make that mistake. I am pretty sure I won`t be the only one. @bkchr how about if I change the error to only spit out if there are multiple "Config" defined for which we would error out anyway? That would let someone do one if they wanted. but someone who got the wrong idea would likely have multiple...

Here come multiple things into play:

Runtime api is not Frame specific, it is Substrate core.
No one forces you to name your pallet trait Config, before it was for example called Trait(really bad naming). However, this name could maybe change again in the future.

Can we not improve the error message when you implement the "same" runtime api?


Fix behavior of data-turbolinks-preview attribute

I'm using AngularJS with Rails5 and I found the cache of turbolinks may cause angular's re-bootstrap problem when click the back button of browser.
I tried to solve it with the data-turbolinks-preview attribute but it seems that the attribute doesn't work as it was described at Detecting When a Preview is Visible. So I fixed it and added a testcase:)

I’m afraid I don’t understand... the data-turbolinks-preview attribute is working exactly as designed. A loaded snapshot is a preview if it’s going to be replaced by a subsequent fresh page load. So application visits to cached pages will show previews, but restoration visits will not.

Thanks for reply! I'm sorry for misunderstanding the document... But it means that there's no way to determine whether a page is loaded from the network or cache? In my case, the AngularJS rendered the original html before turbolinks caches it. So I need to know this to avoid re-rendering on turbolinks:loadevent when the page is loaded from cache, as it has been rendered.