fix(MockBuilder): add undecorated classes to providers #2845

closes #2845

Codecov Report

Merging #2847 (29b6591) into master (7422c10) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master     #2847   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          221       220    -1
  Lines         4509      4501    -8
  Branches      1024      1024
=========================================
- Hits          4509      4501    -8

Impacted Files
Coverage Δ

libs/ng-mocks/src/lib/common/func.is-ng-type.ts
100.00% <ø> (ø)

...mocks/src/lib/mock-builder/mock-builder.promise.ts
100.00% <ø> (ø)

...ks/src/lib/mock-builder/promise/init-ng-modules.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

v14.0.1 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.


request: allow for scopes to also use autocomplete prompt

Description
Currently, only commitType uses autocomplete. In our monorepo, we have many scopes. It would be ideal to also be able to filter the scopes via autocomplete.
Expected user experience:
Given "configuration.scopes" is an array and its length is greater than 0
When the user attempts to commit
Then they should be prompted with a list of scopes
And they should be able to filter the list of scopes by typing

Proposed solution

Change the prompt type from list to autocomplete here:
https://github.com/Exlint/cz-vinyl/blob/b949ffb087e617407f768ca7c34fda8b6f9ca066/src/utils/questions.ts#L40
Provide a source to the prompt similar to how it's done with commit type:
https://github.com/Exlint/cz-vinyl/blob/b949ffb087e617407f768ca7c34fda8b6f9ca066/src/utils/questions.ts#L32-L37

Alternatives considered
No response
Do you want to create a pull request?
Yes

@jromero-pg
Supported from version 2.1.0


HTML5 encoded videos

Sample video in HTML5 formats. Need to investigate the formats required for Safari / Chrome, i.e. http://blog.zencoder.com/2010/09/30/how-to-encode-video-for-mobile-use/

Hi have put three sizes of video with an h264 codec (very universal) in the dropbox data folder. These are only test files.

Thanks. Closing this issue.


GridMap with MeshLib always throws error

Godot version:
Godot Engine v3.2.stable.official
OS/device including version:
Windows 10 Home Edition
Issue description:
Whenever you put Gridmap with MeshLib connected in your scene it always throws this error:

get_item_preview: MeshLibrary item previews are only generated in an editor context, which means they aren't available in a running project.
<C++ Source>  scene/resources/mesh_library.cpp:206 @ get_item_preview()

Which in my case completely floods game console.
Steps to reproduce:

Create GridMap instance and connect some MeshLib to it
Start project

Minimal reproduction project:
test.zip

This was fixed in #36288, closing.


Substraction with a bool tensor is not supported, fixes issue #106

This issue fixes issue #106:
Subtraction, the - operator, with a bool tensor is not supported. If you are trying to invert a mask, use the ~ or bitwise_not() operator instead.

The issue is solved by replacing 1 - positive_indices by ~ positive_indices

Thanks for your PR. I've upgraded this repo for pytorch >=1.0 after being very busy for some time. Although I didn't merge this PR, thank you for the help it provided in fixing the issue here.


issue with printing characters in conhost

Windows Build Number
Microsoft Windows [Version 10.0.19043.1202]
WSL Version

[ ] WSL 2
[X] WSL 1

Kernel Version
5.10.16
Distro Version
20.04.3
Other Software
bash
conhost
Repro Steps
cat /dev/urandom
Expected Behavior
This should print characters eternally into the console. Some of them will not render correctly but it should constantly scroll.
Actual Behavior
The printing halts after a certain point and this error is returned:
cat: write error: Input/output error
Diagnostic Logs
No response

My understanding is that this is by-design since you are writing random bytes to the console, which are being interpreted as VT100 sequences.  Adding @DHowett to keep me honest.


about data read

thank you for your project.
when i run feature_extractor.py,i get a error:
TypeError: 'set' object does not support indexing
i  already downloads UCF video data in '--dataset_path', c3d.pickle in '--pretrained_3d',
'--annotation_path' and '--annotation_path_test' default in your project named Train_Annotation.txt and Test_Annotation.txt

thank you for your project.
when i run feature_extractor.py,i get a error:
TypeError: 'set' object does not support indexing
i already downloads UCF video data in '--dataset_path', c3d.pickle in '--pretrained_3d',
'--annotation_path' and '--annotation_path_test' default in your project named Train_Annotation.txt and Test_Annotation.txt

Hi, could you please provide me the UCF dataset? I cannot obtain the normal data due to the unknown corruption.

The feature extracted data is in the README file if you need it but you can fix the set error you have thereby just removing the "set" part from it, detailed in this issue I think.
Hope that helps.


Hubot for Microsoft Teams

Have anyone looked at creating a Hubot adapter for Microsoft Teams (teams.microsoft.com)?

Looking forward to this. It will be better if Hubot can integrate with Microsoft Bot Framework (which may support teams) in someway so that if they add/remove support, it can work well with Hubot.

I've been trying to get some code working, but the bot I made for my company has some proprietary stuff I don't want out in public domain. That and I need a cloud endpoint that the bot can be reached from.
My idea is to use the Microsoft Node.js SDK to create a UniversalBot and setup events in the hubot adapter. As soon as I can get a proper test bed going to make sure it works I have no problem releasing it to the public.

The new custom bot capability in MS teams is heading there. From the look of it, one could now create an Hubot adapter for MS teams.
There is a sample custom bot in C# on Github. I haven't look at the code yet.

According to https://microsoftteams.uservoice.com/forums/555103-public-preview/suggestions/16937848-allow-adding-bots-to-channels this has been completed on Microsoft's side; however I have not verified.

@israelshirk I can verify that you can add bots to channels. Unfortunately, unless you @mention them specifically, they're not allowed to "listen" to the channel. This removes most of the utility of a bot (it makes it a special case of a slash command).
To fix this issue, please vote here: https://microsoftteams.uservoice.com/forums/555103-public/suggestions/18646171-remove-bot-mention-requirement

Thanks @calebmeyer!

Looks like Microsoft has posted a Bot Framework Hubot adapter:  https://github.com/Microsoft/BotFramework-Hubot

Have anyone manage to actually get their hubot connected with ms teams?

@wumingzhang Yes, works great

It looks like with botFramework, hubot needs to be hosted on the public internet per this issue on botframework adapter for Hubot: @Microsoft/BotFramework-Hubot#15.
The issue with that is that it will require some sort of reverse proxy or VPN to reach infrastructure which is only on the intranet.
In the issue above, there is a mention about Orky, which looks like some sort of a botframework proxy, to which Hubot connects thanks to an Hubot adapter.
Hubot (on prem) w/orky adapter ----> Orky bot (internet) <----> MS Teams

I got a question off list about this, which I'm going to answer on-list for posterity.
First, get hubot online
You'll want to have it booted up with BotFramework-Hubot and non-functioning credentials, but the right port.  We'll add credentials later.  Sounds weird, I know, but it'll work out in the end.  Just trust me.  You'll want port 3976 open to the interweb (or at least to Azure's cloud netmasks) so that Microsoft's REST API calls from Teams -> BotFramework -> your botframework implementation -> hubot make it through.
Botframework.com
So, first you're going to want to register yourself at https://dev.botframework.com/.  This is the integration point.

There's a step through the M$ registration, and then you're logged into dev.botframework.com with a header menu that has an option of My Bots.
Click it.
Hit Create and do register an existing bot.
Fill in the next form really good-like.  At messaging endpoint enter the endpoint you created above!
Now we'll create the Microsoft App ID and Password that the local Bot Framework wants.  Just follow the buttons and you'll be good to go.
Paste in your App ID into the Bot Framework form because Microsoft's left hand doesn't talk to its right.
Add any other owners you'd like to have in case you get a cold and don't want to be on call.

Agree, and you're well on your way.  Make sure you have microsoft teams selected as your chat framework (BotFramework is an aggregator service - so failing to select Microsoft Teams and the proper channels here can be painful).
Credential Hubot and restart
Pretty straightforwards.
Test
You can test hubot first from the dev.botframework.com dashboard.  Any connectivity issues between BotFramework's APIs and your hubot can be sussed out by using that integration.  As long as that is working with your hubot, your problem is then between your BotFramework configuration and your Microsoft Teams configuration.  Which can be a hassle, but typically starting from scratch it's fairly straightforwards.  Just make sure you're logged in with the right organization, account, privileges, and you should just end up in the right place from the beginning.
If you have any questions I'm a little time limited, but I'll help where I can on here or every once in a while I'm on the hubot slack.  Hope this helps!

Great input @israelshirk thanks! :+1:

the messaging endpoint require to be https, i guess you need do some haproxy between?

Correct; my apologies.  I used nginx.

On Oct 9, 2017, at 10:42 AM, wumingzhang<EMAIL_ADDRESS>wrote:
the messaging endpoint require to be https, i guess you need do some haproxy between?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

thanks @israelshirk , still missing the last piece of the puzzle. I got it working in "test" mode in dev.botframework.com, but cannot connect properly into teams. anything special need to be done?

@israelshirk How did you configure the end-point? I have hubot running but when I do
curl: (7) Failed to connect to <IP_ADDRESS> port 3976: Connection refused

I get nothing?

Just in case anybody else gets stuck on this it's.
Port 8080 not 3976, you can reverse proxy it with Nginx to expose it publicly.
If you want to keep to hubot spec you should alter BOTBUILDER_ENDPOINT to be /hubot/api/messages as well.
curl -X POST -H "Content-Type: application/json" -d '{"test":"test"}' localhost:8080/api/messages


Can't install addon after update to 2021.1.3

Hi,
I just updated my HA to core-2021.1.3. After the update the Caddy 2 Addon is the only addon which doesn't work anymore.
Tried to re-install the addon but I get the following error:
21-01-16 20:04:25 ERROR (SyncWorker_0) [supervisor.docker.interface] Can't install berichta/caddy-2-amd64:0.1.0 -> 404 Client Error for http+docker://localhost/v1.40/images/create?tag=0.1.0&fromImage=berichta%2Fcaddy-2-amd64: Not Found ("manifest for berichta/caddy-2-amd64:0.1.0 not found: manifest unknown: manifest unknown").
Help is very much appreciated :)
System Health

version
2021.1.3

installation_type
Home Assistant Supervised

dev
false

hassio
true

docker
true

virtualenv
false

python_version
3.8.7

os_name
Linux

os_version
4.19.0-13-amd64

arch
x86_64

timezone
Europe/Berlin

Home Assistant Community Store

GitHub API
ok

Github API Calls Remaining
5000

Installed Version
1.9.0

Stage
running

Available Repositories
773

Installed Repositories
5

Hass.io

host_os
Debian GNU/Linux 10 (buster)

update_channel
stable

supervisor_version
2021.01.4

docker_version
19.03.13

disk_total
105.3 GB

disk_used
21.9 GB

healthy
true

supported
true

supervisor_api
ok

version_api
ok

installed_addons
File editor (5.2.0), Caddy (1.6), MariaDB (2.2.1), Portainer (1.3.0), phpMyAdmin (0.1.4), deCONZ (6.6.0), Check Home Assistant configuration (3.6.0), motionEye (0.10.2), Mosquitto broker (5.1), ESPHome (1.15.3), AppDaemon 4 (0.3.2)

Lovelace

dashboards
1

mode
storage

views
9

resources
2

Same here.

Same here.

This was in fact a supervisor bug, fixed here: https://github.com/home-assistant/supervisor/pull/2443
The add-ons should be installable again.

This was in fact a supervisor bug, fixed here: https://github.com/home-assistant/supervisor/pull/2443
The add-ons should be installable again.


1.12.10 break nuxt compilation

I use Nuxt Config as nuxt.config.ts, and after upgrade to 1.12.10 build started to fail with error Cannot find module nuxt.config

Workaround: downgrade to Jiti 1.12.9 in package.json, if installed through package-lock/yarn.lock:
  "resolutions": {
    "jiti": "1.12.9"
  },

see also https://github.com/nuxt/create-nuxt-app/issues/926

Thanks for reporting. Issue should be resolved in latest hotfix. Please try recreating lockfile.

Can confirm as fixed in 1.12.13. Thanks for quick fix!


Node debugger variables undefined

I was debugging https://github.com/editorconfig/editorconfig-vscode and noticed something odd.

As you can see in the left pane, savedDocument.fileName is undefined. But in reality, it is not because basename(savedDocument.filename) returned .editorconfig, otherwise I couldn't go inside the if statement.
To be clear, it is a TypeScript project (as it is an extension), so not sure for vanilla JavaScript projects. Seems a quite important bug to be honest.
@bpasero Are you able to pass this to the right person? Thanks :)

This bug doesn't always occur. I debugged another project (which is plain JavaScript) and it was working fine.

Experiencing the same with Node.js & babel require hook. Not all values are undefined though.

This should no longer be a problem with the "inspector" protocol debugging.


Issue #1535 Python is strongly but not statically typed.

This was discussed in Issue Issue #1535

thanks!!

Nice catch! :)


Object isnt working

Hey,
I am on a Mac machine (MacOS 10.14) with pd vanilla and the object isnt loading.
is this object made for purr data? because I dont really understand the "l2ork_toggle_console 1" object?
the best,
delmenhorst.

I can confirm that the compiled external from the repository is not loading in Pd 0.50 on Linux.

Seems it works now for me (haven't tested with the sensel yet).

Yes, the new release is now considered stable. I am closing this unless you encounter any further issues.


Show better error when trying to retrieve logs of app without workload.

fix #1458
fix: double reporting of log error
fix: non-reporting of log error details

Codecov Report

Merging #1574 (4792df3) into main (f87ffb9) will decrease coverage by 21.83%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##             main    #1574       +/-   ##
===========================================
- Coverage   61.49%   39.65%   -21.84%
===========================================
  Files         167      167
  Lines       12293    12300        +7
===========================================
- Hits         7559     4877     -2682
- Misses       3761     6699     +2938
+ Partials      973      724      -249

Flag
Coverage Δ

acceptance-api
?

acceptance-apps
38.35% <0.00%> (+0.52%)
:arrow_up:

acceptance-cli
?

unittests
8.61% <0.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

internal/cli/usercmd/app.go
29.03% <ø> (-34.96%)
:arrow_down:

pkg/api/core/v1/client/apps.go
24.02% <0.00%> (-23.56%)
:arrow_down:

helpers/bytes/bytes.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/api/core/v1/models/namespace.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/api/core/v1/models/sort.go
11.11% <0.00%> (-88.89%)
:arrow_down:

internal/api/v1/application/match.go
0.00% <0.00%> (-82.36%)
:arrow_down:

internal/api/v1/configuration/match.go
0.00% <0.00%> (-82.36%)
:arrow_down:

internal/api/v1/configurationbinding/delete.go
0.00% <0.00%> (-82.36%)
:arrow_down:

internal/api/v1/appchart/match.go
0.00% <0.00%> (-80.65%)
:arrow_down:

internal/api/v1/namespace/match.go
0.00% <0.00%> (-80.65%)
:arrow_down:

... and 94 more

Continue to review full report at Codecov.

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

Output looks good now:
~/workspace/epinio/epinio (1458-handle-log-error)$ epinio app create sample2

🚢  Create application
Namespace: workspace
Application: sample2

✔  Ok
~/workspace/epinio/epinio (1458-handle-log-error)$ epinio app logs sample2

🚢  Streaming application logs
Namespace: workspace
Application: sample2

❌  error streaming application logs: Bad Request: No logs available for application without workload
~/workspace/epinio/epinio (1458-handle-log-error)$


feat: cubestore workers statsd sidecar to get metrics

Enabled statsd exporter for cubestore-workers.

@lvauvillier could you please review this PR as well ?

Merged! Thanks a lot @svdimchenko and sorry for the delay.
Thanks @siamak-haschemi for looking at it.


Job listing management

Related to #59

Provide an interface for employers to view, edit, and delete their posted job listings.
Implement search and filter options to allow employers to easily find and manage their job postings based on criteria such as job title, date posted, or application deadline.

Task completed


Feature request: Allow passing named arguments to pear run

This would make it simpler to access passed arguments
https://docs.pears.com/pear-runtime/api#pear.config.args-less-than-array-greater-than
Probably a good idea to make it similar to npm run:
https://docs.npmjs.com/cli/v10/commands/npm-run-script

that's the job of a higher level library, such as https://github.com/holepunchto/paparam : cmd.parse(Pear.config.args)


Blazor WebAssembly dotnet run --pathbase=/ doesn't work

When deploying our Blazor WebAssembly app we have the base href="/Blazor/" because that is where it will live, but when trying to override that while developing locally using the dotnet run --pathbase=/ I get the following text "The server is configured only to handle request URIs within the PathBase '/'." and I get 404 errors for all the resources.

Thanks for contacting us, @jefflangston.
We'll investigate this after we're done with the upcoming 3.0 release.

Given that we heard no more reports of this for quite a while now, we're moving this issue to the Backlog. It will, probably, take some time for us to get to it.


Custom Translator has replaced Hub

#sign-off

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

Thanks @JohanFreelancer9 , I have committed the edit

#sign-off

@SerdarSoysal Thank you for submitting feedback and contributing to the docs. We are currently investigating this.


When pasting CURL request into url input and importing the request,  insomnia creates new request, and keeps old one with corupted imput from CURL

Expected Behavior
After pasting CURL and importing the data into recent Request, it should update the request tab - where the CURL was imported.
Actual Behavior
This behavior is quite anoying as when I want to import new CURL
even if I prepare a new request in advance and paste CURL into its url input and  confirm input modal,
I end with 2 requests

one succesfully imported
second - which I prepared for import with broken URL which colds the CURL string and it is useless

Any time I import CURL I need manually cleanup second request

Reproduction Steps

Open insomnia request
paste CURL string into  url input
Wait for import popup
hit IMPORT

as resolution you end with 2 Request  tabs, where one is corrupted by pasted CURL text
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
9.3.2
What operating system are you using?
macOS
Operating System Version
Sonoma 14.5
Installation method
download
Last Known Working Insomnia version
No response

Can you update to v9.3.3 and see if it still happens?
You can also try this option From Curl:

Thank you for your reply, the error is still present in  9.3.3, however the import from CURL option works great.
For me the option From Curl is enough and perhaps this issue might be closed.

Thanks @petermilan


Display loading spinner while ProtestPage is loading

When the protest page is loading, the following indicator is being shown:

Let's make it look nicer with the LoadingSpinner component.
🧐 How to approach:

Locate the loading indicator on the ProtestPage component
Change it to show a <LoadingSpinner />

can I have this?

@CiTRuS93 sure! it's yours :)


AttributeError: 'NoneType' object has no attribute 'replace'

% ./pt.sh
Reading the config file...
Logging into the Pump server...
Logging into Twitter...
Looking at Pump outbox activity...
> note (2017-07-16 09:31:39+00:00)
> note (2017-07-16 09:05:28+00:00)
> note (2017-07-16 09:03:36+00:00)
> note (2017-07-14 22:22:34+00:00)
> image (2017-07-14 19:40:05+00:00)
> note (2017-07-14 19:38:44+00:00)
New tweet count: 3.
---------------------------------

> for all Twitter did for #NetNeutrality on the day of action, I sure still see Comcast ads on my timeline lying... https://pump.strugee.net/alex/note/ki6CrIJDTXuty2my30KD-Q
---------------------------------

> Dumb Flash keeps hanging my kernel.... https://pump.strugee.net/alex/note/9LL5vmkoT9qUxOmNK11TaA
Traceback (most recent call last):
  File "./pt.py", line 21, in <module>
    pumptweet.pull_and_push(halt_on_error=halt_on_error)
  File "/home/alex/pumptweet/pumptweet/PumpTweet.py", line 202, in pull_and_push
    self.post_all(posts)
  File "/home/alex/pumptweet/pumptweet/PumpTweet.py", line 174, in post_all
    self.post_image(post)
  File "/home/alex/pumptweet/pumptweet/PumpTweet.py", line 147, in post_image
    text = self.make_text(post)
  File "/home/alex/pumptweet/pumptweet/PumpTweet.py", line 101, in make_text
    content = strip_tags(content)
  File "/home/alex/pumptweet/pumptweet/MLStripper.py", line 51, in strip_tags
    text = replace_entities(text)
  File "/home/alex/pumptweet/pumptweet/MLStripper.py", line 45, in replace_entities
    html = html.replace(entity, char)
AttributeError: 'NoneType' object has no attribute 'replace'

% git rev-parse HEAD
3642fa254c527463ac5e0c1bfbf7a8dc2cdbbf7a

I reinstalled since you switched to Python 3, etc., and it just seemed cleaner. So this has the very latest PyPump 0.7 and python-twitter 3.3.
AFAICT https://pump.strugee.net/alex/image/tjIrdCZlSn2UxsVzEMvZuw is what's causing this. Perhaps because it's a profile picture change and not a regular image? I dunno. (Are those even different at the protocol layer? I really should know this, but don't.)

@strugee Sadly, I haven't been using Pump since Microca.st went down. I dunno what is useful for you. You're welcome to file bugs here, but I can't provide any substantive assistance. Sorry!


executeRaw using Prisma.Join damages float values

Bug description
As Prisma doesn't support upsertMany and I'm working with a crazy amount of data, I need to upsert rows to my database. I have chosen using INSERT with ON CONFLICT statement. When I'm having an entity Product with only id (string), price (float), I'm not able to save float values correctly.
How to reproduce
  const items = [{id: 1, priceAmount: 157}]; // Here is usually 1 000 items
  const completeKeys: string[] = Object.keys(items[0]);
  const ingnoredKeys = ["id"];

  const updateFieldsMapper = (item: any) => {
    return Prisma.sql`(${Prisma.join(
      completeKeys.map((key: string) => item[key])
    )})`;
  };

  const insertKeys = completeKeys.map((key) =>
    key.toLocaleLowerCase() !== key ? `"${key}"` : `${key}`
  );

  const insertValues = completeKeys.map((item) => updateFieldsMapper(item));

  const updateSet = completeKeys.reduce((updateSet: string[], key: string) => {
      if (!ingnoredKeys.includes(key)) {
          updateSet.push(`"${key}" = EXCLUDED."${key}"`);
      }
      return updateSet;
  }, []);

  try {
    await prisma.$executeRaw`
      INSERT INTO "Product"  (${Prisma.raw(insertKeys.join(","))})
      VALUES ${Prisma.join(insertValues)}
      ON CONFLICT (id)
      DO UPDATE SET ${Prisma.raw(updateSet.join(","))};`;
  } catch (error) {
    console.error(error);
  }

Expected behavior
The expected behaviour is that number 157 is saved. I have tried to use a simple update query to be sure I'm having correct data and it works well.
await prisma.product.update({
      where: { id: items[0].id?.toString() },
      data: {
        priceAmount: items[0].priceAmount,
      },
});

Prisma information
datasource db {
    provider = "postgresql"
    url      = env("DB_URL")
}

generator client {
    provider = "prisma-client-js"
}

model Product {
    id             String  @id @default(cuid())
    priceAmount    Float?
}

"dependencies": {
    "@prisma/client": "^2.25.0",
},
"devDependencies": {
   "prisma": "^2.25.0",
}

Environment & setup

OS: Mac OS or Debian,
Database: PostgreSQL
Node.js version: 12.20.0

Prisma Version
7.9.0

What are you observing instead of that the data is stored correctly?
What is the Prisma version you are testing with? If it is the 2.25.0 mentioned above, please update to a newer version and see if the problem still exists there.

What are you observing instead of that the data is stored correctly?
What is the Prisma version you are testing with? If it is the 2.25.0 mentioned above, please update to a newer version and see if the problem still exists there.

I'm observing this:

What are you observing instead of that the data is stored correctly?
What is the Prisma version you are testing with? If it is the 2.25.0 mentioned above, please update to a newer version and see if the problem still exists there.

I have tried to create everything as a raw query and it seems that the sort of inserted values is changed. This means that at the end the sql is trying to save priceAmount into the id column and vice versa.

The raw query doing something unexpected sounds unrelated to the original problem though, right? If so, please open a separate issue for this - otherwise we will have a really hard time keeping these things apart and trying to debug - and fix - them.

Ok, I spent the lunch hours with this issue and was able to reproduce it with the version 2.35.0:
datasource db {
  provider   = "postgresql"
  url        = env("DATABASE_URL")
  engineType = "library"
}

generator client {
  provider = "prisma-client-js"
  previewFeatures = ["nApi"]
}

model Product {
  id          String  @id @default(cuid())
  priceAmount Float?
}

The code I cut down to the minimum:
import { PrismaClient, Prisma } from '@prisma/client'

const prisma = new PrismaClient({
  log: ['query', 'info', 'warn', 'error']
})

async function main() {
  await prisma.product.deleteMany();

  const item: any = {id: 1, priceAmount: 157};
  const insertKeys = Object.keys(item);

  const insertValues = insertKeys.map((key: string) => item[key]);

  const updateSet = insertKeys.reduce((updateSet: string[], key: string) => {
    updateSet.push(`"${key}" = EXCLUDED."${key}"`);
    return updateSet;
  }, []);

  await prisma.$executeRaw`
    INSERT INTO "Product" (${Prisma.raw(insertKeys.map((key) => `"${key}"`).join(","))})
    VALUES (${Prisma.join(insertValues)})
    ON CONFLICT (id)
    DO UPDATE SET ${Prisma.raw(updateSet.join(","))};`;

  console.log(await prisma.product.findMany());
}

main()
  .then(async () => {
    await prisma.$disconnect()
  })
  .catch(async (e) => {
    console.error(e)
    await prisma.$disconnect()
    process.exit(1)
  })

Now, the debug output and obviously wrong result:
root@16e64762bf89:/prisma-9195# env DEBUG="*" npx ts-node script.ts
  prisma:tryLoadEnv Environment variables loaded from /prisma-9195/.env +0ms
[dotenv][DEBUG] did not match key and value when parsing line 1: # Environment variables declared in this file are automatically made available to Prisma.
[dotenv][DEBUG] did not match key and value when parsing line 2: # See the documentation for more detail: https://pris.ly/d/prisma-schema#using-environment-variables
[dotenv][DEBUG] did not match key and value when parsing line 3:
[dotenv][DEBUG] did not match key and value when parsing line 4: # Prisma supports the native connection string format for PostgreSQL, MySQL, SQL Server and SQLite.
[dotenv][DEBUG] did not match key and value when parsing line 5: # See the documentation for all the connection string options: https://pris.ly/d/connection-strings
[dotenv][DEBUG] did not match key and value when parsing line 6:
[dotenv][DEBUG] did not match key and value when parsing line 8:
  prisma:tryLoadEnv Environment variables loaded from /prisma-9195/.env +2ms
[dotenv][DEBUG] did not match key and value when parsing line 1: # Environment variables declared in this file are automatically made available to Prisma.
[dotenv][DEBUG] did not match key and value when parsing line 2: # See the documentation for more detail: https://pris.ly/d/prisma-schema#using-environment-variables
[dotenv][DEBUG] did not match key and value when parsing line 3:
[dotenv][DEBUG] did not match key and value when parsing line 4: # Prisma supports the native connection string format for PostgreSQL, MySQL, SQL Server and SQLite.
[dotenv][DEBUG] did not match key and value when parsing line 5: # See the documentation for all the connection string options: https://pris.ly/d/connection-strings
[dotenv][DEBUG] did not match key and value when parsing line 6:
[dotenv][DEBUG] did not match key and value when parsing line 8:
[dotenv][DEBUG] "DATABASE_URL" is already defined in `process.env` and will not be overwritten
  prisma:client clientVersion: 2.30.3 +0ms
  prisma:client:libraryEngine internalSetup +0ms
  prisma:client Prisma Client call: +31ms
  prisma:client prisma.product.deleteMany(undefined) +0ms
  prisma:client Generated request: +0ms
  prisma:client mutation {
  prisma:client   deleteManyProduct {
  prisma:client     count
  prisma:client   }
  prisma:client }
  prisma:client  +0ms
  prisma:client:libraryEngine sending request, this.libraryStarted: false +31ms
  prisma:client:libraryEngine Search for Query Engine Library in /prisma-9195/node_modules/.prisma/client +16ms
  prisma:client:libraryEngine loadEngine using /prisma-9195/node_modules/.prisma/client/libquery_engine-debian-openssl-1.1.x.so.node +1ms
  prisma:client:libraryEngine library starting +3ms
prisma:info Starting a postgresql pool with 33 connections.
  prisma:client:libraryEngine library started +17ms
prisma:query BEGIN
prisma:query SELECT "public"."Product"."id" FROM "public"."Product" WHERE 1=1 OFFSET $1
prisma:query SELECT "public"."Product"."id" FROM "public"."Product" WHERE 1=1
prisma:query DELETE FROM "public"."Product" WHERE "public"."Product"."id" IN ($1)
prisma:query COMMIT
  prisma:client prisma.$executeRaw(
  prisma:client     INSERT INTO "Product" ("id","priceAmount")
  prisma:client     VALUES ($1,$2)
  prisma:client     ON CONFLICT (id)
  prisma:client     DO UPDATE SET "id" = EXCLUDED."id","priceAmount" = EXCLUDED."priceAmount";, [1,157]) +43ms
  prisma:client Prisma Client call: +0ms
  prisma:client Prisma Client call: +1ms
  prisma:client prisma.executeRaw({
  prisma:client   query: '\n    INSERT INTO "Product" ("id","priceAmount")\n    VALUES ($1,$2)\n    ON CONFLICT (id)\n    DO UPDATE SET "id" = EXCLUDED."id","priceAmount" = EXCLUDED."priceAmount";',
  prisma:client   parameters: {
  prisma:client     values: '[1,157]',
  prisma:client     __prismaRawParamaters__: true
  prisma:client   }
  prisma:client }) +1ms
  prisma:client Generated request: +0ms
  prisma:client mutation {
  prisma:client   executeRaw(
  prisma:client     query: "\n    INSERT INTO \"Product\" (\"id\",\"priceAmount\")\n    VALUES ($1,$2)\n    ON CONFLICT (id)\n    DO UPDATE SET \"id\" = EXCLUDED.\"id\",\"priceAmount\" = EXCLUDED.\"priceAmount\";"
  prisma:client     parameters: "[1,157]"
  prisma:client   )
  prisma:client }
  prisma:client  +0ms
  prisma:client:libraryEngine sending request, this.libraryStarted: true +7ms
  prisma:client:libraryEngine library already starting, this.libraryStarted: true +0ms
prisma:query
    INSERT INTO "Product" ("id","priceAmount")
    VALUES ($1,$2)
    ON CONFLICT (id)
    DO UPDATE SET "id" = EXCLUDED."id","priceAmount" = EXCLUDED."priceAmount";
  prisma:client Prisma Client call: +3ms
  prisma:client prisma.product.findMany(undefined) +0ms
  prisma:client Generated request: +0ms
  prisma:client query {
  prisma:client   findManyProduct {
  prisma:client     id
  prisma:client     priceAmount
  prisma:client   }
  prisma:client }
  prisma:client  +0ms
  prisma:client:libraryEngine sending request, this.libraryStarted: true +3ms
  prisma:client:libraryEngine library already starting, this.libraryStarted: true +0ms
prisma:query SELECT "public"."Product"."id", "public"."Product"."priceAmount" FROM "public"."Product" WHERE 1=1 OFFSET $1
[ { id: '1', priceAmount: 7.76e-322 } ]
  prisma:client:libraryEngine library stopping, this.libraryStarted: true +2ms
  prisma:client:libraryEngine library stopping +5ms
  prisma:client:libraryEngine library stopped +0ms
  prisma:client:libraryEngine hookProcess received: beforeExit +1ms
  prisma:client:libraryEngine runBeforeExit +0ms
  prisma:client:libraryEngine hookProcess received: exit +0ms

Running the same script with 4.3.1:
  prisma:tryLoadEnv  Environment variables loaded from /prisma-9195/.env +0ms
  prisma:tryLoadEnv  Environment variables loaded from /prisma-9195/.env +1ms
  prisma:client  dirname /prisma-9195/node_modules/.prisma/client +0ms
  prisma:client  relativePath ../../../prisma +0ms
  prisma:client  cwd /prisma-9195/prisma +0ms
  prisma:client  clientVersion 4.3.1 +1ms
  prisma:client  clientEngineType library +0ms
  prisma:client:libraryEngine  internalSetup +0ms
  prisma:client:libraryEngine:loader  Searching for Query Engine Library in /prisma-9195/node_modules/.prisma/client +0ms
  prisma:client:libraryEngine:loader  loadEngine using /prisma-9195/node_modules/.prisma/client/libquery_engine-debian-openssl-1.1.x.so.node +1ms
  prisma:client  Prisma Client call: +51ms
  prisma:client  prisma.product.deleteMany(undefined) +1ms
  prisma:client  Generated request: +0ms
  prisma:client  mutation {
  deleteManyProduct {
    count
  }
}
 +0ms
  prisma:client:libraryEngine  sending request, this.libraryStarted: false +52ms
  prisma:client:libraryEngine  library starting +0ms
prisma:info Starting a postgresql pool with 33 connections.
  prisma:client:libraryEngine  library started +16ms
prisma:query BEGIN
prisma:query SELECT "public"."Product"."id" FROM "public"."Product" WHERE 1=1 OFFSET $1 /* traceparent=00-00-00-00 */
prisma:query SELECT "public"."Product"."id" FROM "public"."Product" WHERE 1=1 /* traceparent=00-00-00-00 */
prisma:query DELETE FROM "public"."Product" WHERE "public"."Product"."id" IN ($1) /* traceparent=00-00-00-00 */
prisma:query COMMIT
  prisma:client  prisma.$executeRaw(
    INSERT INTO "Product" ("id","priceAmount")
    VALUES ($1,$2)
    ON CONFLICT (id)
    DO UPDATE SET "id" = EXCLUDED."id","priceAmount" = EXCLUDED."priceAmount";, [1,157]) +23ms
  prisma:client  Prisma Client call: +0ms
  prisma:client  Prisma Client call: +1ms
  prisma:client  prisma.$executeRaw({
  query: '\n    INSERT INTO "Product" ("id","priceAmount")\n    VALUES ($1,$2)\n    ON CONFLICT (id)\n    DO UPDATE SET "id" = EXCLUDED."id","priceAmount" = EXCLUDED."priceAmount";',
  parameters: {
    values: '[1,157]',
    __prismaRawParamaters__: true
  }
}) +0ms
  prisma:client  Generated request: +0ms
  prisma:client  mutation {
  executeRaw(
    query: "\n    INSERT INTO \"Product\" (\"id\",\"priceAmount\")\n    VALUES ($1,$2)\n    ON CONFLICT (id)\n    DO UPDATE SET \"id\" = EXCLUDED.\"id\",\"priceAmount\" = EXCLUDED.\"priceAmount\";"
    parameters: "[1,157]"
  )
}
 +1ms
  prisma:client:libraryEngine  sending request, this.libraryStarted: true +9ms
prisma:query
    INSERT INTO "Product" ("id","priceAmount")
    VALUES ($1,$2)
    ON CONFLICT (id)
    DO UPDATE SET "id" = EXCLUDED."id","priceAmount" = EXCLUDED."priceAmount";
  prisma:client  Prisma Client call: +5ms
  prisma:client  prisma.product.findMany(undefined) +0ms
  prisma:client  Generated request: +0ms
  prisma:client  query {
  findManyProduct {
    id
    priceAmount
  }
}
 +0ms
  prisma:client:libraryEngine  sending request, this.libraryStarted: true +5ms
prisma:query SELECT "public"."Product"."id", "public"."Product"."priceAmount" FROM "public"."Product" WHERE 1=1 OFFSET $1 /* traceparent=00-00-00-00 */
[ { id: '1', priceAmount: 157 } ]
  prisma:client:libraryEngine  library stopping +7ms
  prisma:client:libraryEngine  library stopped +0ms
  prisma:client:libraryEngine:exitHooks  exit event received: beforeExit +0ms
  prisma:client:libraryEngine:exitHooks  exit event received: exit +0ms

The differences:

2.35.0 returns [ { id: '1', priceAmount: 7.76e-322 } ] which is wrong.
4.3.1 returns [ { id: '1', priceAmount: 157 } ] which is correct.

Ok, I spent the lunch hours with this issue and was able to reproduce it with the version 2.35.0:
datasource db {
  provider   = "postgresql"
  url        = env("DATABASE_URL")
  engineType = "library"
}

generator client {
  provider = "prisma-client-js"
  previewFeatures = ["nApi"]
}

model Product {
  id          String  @id @default(cuid())
  priceAmount Float?
}

The code I cut down to the minimum:
import { PrismaClient, Prisma } from '@prisma/client'

const prisma = new PrismaClient({
  log: ['query', 'info', 'warn', 'error']
})

async function main() {
  await prisma.product.deleteMany();

  const item: any = {id: 1, priceAmount: 157};
  const insertKeys = Object.keys(item);

  const insertValues = insertKeys.map((key: string) => item[key]);

  const updateSet = insertKeys.reduce((updateSet: string[], key: string) => {
    updateSet.push(`"${key}" = EXCLUDED."${key}"`);
    return updateSet;
  }, []);

  await prisma.$executeRaw`
    INSERT INTO "Product" (${Prisma.raw(insertKeys.map((key) => `"${key}"`).join(","))})
    VALUES (${Prisma.join(insertValues)})
    ON CONFLICT (id)
    DO UPDATE SET ${Prisma.raw(updateSet.join(","))};`;

  console.log(await prisma.product.findMany());
}

main()
  .then(async () => {
    await prisma.$disconnect()
  })
  .catch(async (e) => {
    console.error(e)
    await prisma.$disconnect()
    process.exit(1)
  })

Now, the debug output and obviously wrong result:
root@16e64762bf89:/prisma-9195# env DEBUG="*" npx ts-node script.ts
  prisma:tryLoadEnv Environment variables loaded from /prisma-9195/.env +0ms
[dotenv][DEBUG] did not match key and value when parsing line 1: # Environment variables declared in this file are automatically made available to Prisma.
[dotenv][DEBUG] did not match key and value when parsing line 2: # See the documentation for more detail: https://pris.ly/d/prisma-schema#using-environment-variables
[dotenv][DEBUG] did not match key and value when parsing line 3:
[dotenv][DEBUG] did not match key and value when parsing line 4: # Prisma supports the native connection string format for PostgreSQL, MySQL, SQL Server and SQLite.
[dotenv][DEBUG] did not match key and value when parsing line 5: # See the documentation for all the connection string options: https://pris.ly/d/connection-strings
[dotenv][DEBUG] did not match key and value when parsing line 6:
[dotenv][DEBUG] did not match key and value when parsing line 8:
  prisma:tryLoadEnv Environment variables loaded from /prisma-9195/.env +2ms
[dotenv][DEBUG] did not match key and value when parsing line 1: # Environment variables declared in this file are automatically made available to Prisma.
[dotenv][DEBUG] did not match key and value when parsing line 2: # See the documentation for more detail: https://pris.ly/d/prisma-schema#using-environment-variables
[dotenv][DEBUG] did not match key and value when parsing line 3:
[dotenv][DEBUG] did not match key and value when parsing line 4: # Prisma supports the native connection string format for PostgreSQL, MySQL, SQL Server and SQLite.
[dotenv][DEBUG] did not match key and value when parsing line 5: # See the documentation for all the connection string options: https://pris.ly/d/connection-strings
[dotenv][DEBUG] did not match key and value when parsing line 6:
[dotenv][DEBUG] did not match key and value when parsing line 8:
[dotenv][DEBUG] "DATABASE_URL" is already defined in `process.env` and will not be overwritten
  prisma:client clientVersion: 2.30.3 +0ms
  prisma:client:libraryEngine internalSetup +0ms
  prisma:client Prisma Client call: +31ms
  prisma:client prisma.product.deleteMany(undefined) +0ms
  prisma:client Generated request: +0ms
  prisma:client mutation {
  prisma:client   deleteManyProduct {
  prisma:client     count
  prisma:client   }
  prisma:client }
  prisma:client  +0ms
  prisma:client:libraryEngine sending request, this.libraryStarted: false +31ms
  prisma:client:libraryEngine Search for Query Engine Library in /prisma-9195/node_modules/.prisma/client +16ms
  prisma:client:libraryEngine loadEngine using /prisma-9195/node_modules/.prisma/client/libquery_engine-debian-openssl-1.1.x.so.node +1ms
  prisma:client:libraryEngine library starting +3ms
prisma:info Starting a postgresql pool with 33 connections.
  prisma:client:libraryEngine library started +17ms
prisma:query BEGIN
prisma:query SELECT "public"."Product"."id" FROM "public"."Product" WHERE 1=1 OFFSET $1
prisma:query SELECT "public"."Product"."id" FROM "public"."Product" WHERE 1=1
prisma:query DELETE FROM "public"."Product" WHERE "public"."Product"."id" IN ($1)
prisma:query COMMIT
  prisma:client prisma.$executeRaw(
  prisma:client     INSERT INTO "Product" ("id","priceAmount")
  prisma:client     VALUES ($1,$2)
  prisma:client     ON CONFLICT (id)
  prisma:client     DO UPDATE SET "id" = EXCLUDED."id","priceAmount" = EXCLUDED."priceAmount";, [1,157]) +43ms
  prisma:client Prisma Client call: +0ms
  prisma:client Prisma Client call: +1ms
  prisma:client prisma.executeRaw({
  prisma:client   query: '\n    INSERT INTO "Product" ("id","priceAmount")\n    VALUES ($1,$2)\n    ON CONFLICT (id)\n    DO UPDATE SET "id" = EXCLUDED."id","priceAmount" = EXCLUDED."priceAmount";',
  prisma:client   parameters: {
  prisma:client     values: '[1,157]',
  prisma:client     __prismaRawParamaters__: true
  prisma:client   }
  prisma:client }) +1ms
  prisma:client Generated request: +0ms
  prisma:client mutation {
  prisma:client   executeRaw(
  prisma:client     query: "\n    INSERT INTO \"Product\" (\"id\",\"priceAmount\")\n    VALUES ($1,$2)\n    ON CONFLICT (id)\n    DO UPDATE SET \"id\" = EXCLUDED.\"id\",\"priceAmount\" = EXCLUDED.\"priceAmount\";"
  prisma:client     parameters: "[1,157]"
  prisma:client   )
  prisma:client }
  prisma:client  +0ms
  prisma:client:libraryEngine sending request, this.libraryStarted: true +7ms
  prisma:client:libraryEngine library already starting, this.libraryStarted: true +0ms
prisma:query
    INSERT INTO "Product" ("id","priceAmount")
    VALUES ($1,$2)
    ON CONFLICT (id)
    DO UPDATE SET "id" = EXCLUDED."id","priceAmount" = EXCLUDED."priceAmount";
  prisma:client Prisma Client call: +3ms
  prisma:client prisma.product.findMany(undefined) +0ms
  prisma:client Generated request: +0ms
  prisma:client query {
  prisma:client   findManyProduct {
  prisma:client     id
  prisma:client     priceAmount
  prisma:client   }
  prisma:client }
  prisma:client  +0ms
  prisma:client:libraryEngine sending request, this.libraryStarted: true +3ms
  prisma:client:libraryEngine library already starting, this.libraryStarted: true +0ms
prisma:query SELECT "public"."Product"."id", "public"."Product"."priceAmount" FROM "public"."Product" WHERE 1=1 OFFSET $1
[ { id: '1', priceAmount: 7.76e-322 } ]
  prisma:client:libraryEngine library stopping, this.libraryStarted: true +2ms
  prisma:client:libraryEngine library stopping +5ms
  prisma:client:libraryEngine library stopped +0ms
  prisma:client:libraryEngine hookProcess received: beforeExit +1ms
  prisma:client:libraryEngine runBeforeExit +0ms
  prisma:client:libraryEngine hookProcess received: exit +0ms

Running the same script with 4.3.1:
  prisma:tryLoadEnv  Environment variables loaded from /prisma-9195/.env +0ms
  prisma:tryLoadEnv  Environment variables loaded from /prisma-9195/.env +1ms
  prisma:client  dirname /prisma-9195/node_modules/.prisma/client +0ms
  prisma:client  relativePath ../../../prisma +0ms
  prisma:client  cwd /prisma-9195/prisma +0ms
  prisma:client  clientVersion 4.3.1 +1ms
  prisma:client  clientEngineType library +0ms
  prisma:client:libraryEngine  internalSetup +0ms
  prisma:client:libraryEngine:loader  Searching for Query Engine Library in /prisma-9195/node_modules/.prisma/client +0ms
  prisma:client:libraryEngine:loader  loadEngine using /prisma-9195/node_modules/.prisma/client/libquery_engine-debian-openssl-1.1.x.so.node +1ms
  prisma:client  Prisma Client call: +51ms
  prisma:client  prisma.product.deleteMany(undefined) +1ms
  prisma:client  Generated request: +0ms
  prisma:client  mutation {
  deleteManyProduct {
    count
  }
}
 +0ms
  prisma:client:libraryEngine  sending request, this.libraryStarted: false +52ms
  prisma:client:libraryEngine  library starting +0ms
prisma:info Starting a postgresql pool with 33 connections.
  prisma:client:libraryEngine  library started +16ms
prisma:query BEGIN
prisma:query SELECT "public"."Product"."id" FROM "public"."Product" WHERE 1=1 OFFSET $1 /* traceparent=00-00-00-00 */
prisma:query SELECT "public"."Product"."id" FROM "public"."Product" WHERE 1=1 /* traceparent=00-00-00-00 */
prisma:query DELETE FROM "public"."Product" WHERE "public"."Product"."id" IN ($1) /* traceparent=00-00-00-00 */
prisma:query COMMIT
  prisma:client  prisma.$executeRaw(
    INSERT INTO "Product" ("id","priceAmount")
    VALUES ($1,$2)
    ON CONFLICT (id)
    DO UPDATE SET "id" = EXCLUDED."id","priceAmount" = EXCLUDED."priceAmount";, [1,157]) +23ms
  prisma:client  Prisma Client call: +0ms
  prisma:client  Prisma Client call: +1ms
  prisma:client  prisma.$executeRaw({
  query: '\n    INSERT INTO "Product" ("id","priceAmount")\n    VALUES ($1,$2)\n    ON CONFLICT (id)\n    DO UPDATE SET "id" = EXCLUDED."id","priceAmount" = EXCLUDED."priceAmount";',
  parameters: {
    values: '[1,157]',
    __prismaRawParamaters__: true
  }
}) +0ms
  prisma:client  Generated request: +0ms
  prisma:client  mutation {
  executeRaw(
    query: "\n    INSERT INTO \"Product\" (\"id\",\"priceAmount\")\n    VALUES ($1,$2)\n    ON CONFLICT (id)\n    DO UPDATE SET \"id\" = EXCLUDED.\"id\",\"priceAmount\" = EXCLUDED.\"priceAmount\";"
    parameters: "[1,157]"
  )
}
 +1ms
  prisma:client:libraryEngine  sending request, this.libraryStarted: true +9ms
prisma:query
    INSERT INTO "Product" ("id","priceAmount")
    VALUES ($1,$2)
    ON CONFLICT (id)
    DO UPDATE SET "id" = EXCLUDED."id","priceAmount" = EXCLUDED."priceAmount";
  prisma:client  Prisma Client call: +5ms
  prisma:client  prisma.product.findMany(undefined) +0ms
  prisma:client  Generated request: +0ms
  prisma:client  query {
  findManyProduct {
    id
    priceAmount
  }
}
 +0ms
  prisma:client:libraryEngine  sending request, this.libraryStarted: true +5ms
prisma:query SELECT "public"."Product"."id", "public"."Product"."priceAmount" FROM "public"."Product" WHERE 1=1 OFFSET $1 /* traceparent=00-00-00-00 */
[ { id: '1', priceAmount: 157 } ]
  prisma:client:libraryEngine  library stopping +7ms
  prisma:client:libraryEngine  library stopped +0ms
  prisma:client:libraryEngine:exitHooks  exit event received: beforeExit +0ms
  prisma:client:libraryEngine:exitHooks  exit event received: exit +0ms

The differences:

2.35.0 returns [ { id: '1', priceAmount: 7.76e-322 } ] which is wrong.
4.3.1 returns [ { id: '1', priceAmount: 157 } ] which is correct.


No Diagnostic information

Nvim Roslyn as of commit 31113dc
Roslyn lsp server version 4.13.0-2.24571.8
I had all the diagnostic information before I updated the package and the server and all other lsp's are giving me diagnostic information so I am not unintentionally turning it off and using the basic configuration provided in the docs.
Load into a buffer. No diagnostic information

Same line in VS Code

Again, I have fixed this by setting in the configuration settings
["csharp|background_analysis"]={
    dotnet_analyzer_diagnostics_scope = "openFiles",
    dotnet_compiler_diagnostics_scope = "fullSolution",
},

I'm also not getting diagnostics, here is my config:
require("roslyn").setup({
    config = {
        capabilities = capabilities,
        settings = {
          ["csharp|background_analysis"] = {
            background_analysis = {
              dotnet_analyzer_diagnostics_scope = "openFiles",
              dotnet_compiler_diagnostics_scope = "fullSolution",
            },
          },
          ["csharp|inlay_hints"] = {
            csharp_enable_inlay_hints_for_implicit_object_creation = true,
            csharp_enable_inlay_hints_for_implicit_variable_types = true,
            csharp_enable_inlay_hints_for_lambda_parameter_types = true,
            csharp_enable_inlay_hints_for_types = true,
            dotnet_enable_inlay_hints_for_indexer_parameters = true,
            dotnet_enable_inlay_hints_for_literal_parameters = true,
            dotnet_enable_inlay_hints_for_object_creation_parameters = true,
            dotnet_enable_inlay_hints_for_other_parameters = true,
            dotnet_enable_inlay_hints_for_parameters = true,
            dotnet_suppress_inlay_hints_for_parameters_that_differ_only_by_suffix = true,
            dotnet_suppress_inlay_hints_for_parameters_that_match_argument_name = true,
            dotnet_suppress_inlay_hints_for_parameters_that_match_method_intent = true,
          },
          ["csharp|code_lens"] = {
            dotnet_enable_references_code_lens = true,
          },
          ["csharp|completion"] = {
            dotnet_show_completion_items_from_unimported_namespaces = true,
            dotnet_show_name_completion_suggestions = true,
          },
        },
    }
})

@samwdp @seblj any thoughts?

@elan-hwang here is my full lazyvim file for setting up roslyn and rzls
return {
    {
        "seblj/roslyn.nvim",
        dependencies = {
            "tris203/rzls.nvim",
        },
        config = function()
            require("rzls").setup({})
            require("roslyn").setup({
                filewatching = true,
                args = {
                    '--logLevel=Information',
                    '--extensionLogDirectory=' .. vim.fs.dirname(vim.lsp.get_log_path()),
                    '--razorSourceGenerator=' .. vim.fs.joinpath(
                        vim.fn.stdpath 'data' --[[@as string]],
                        'mason',
                        'packages',
                        'roslyn',
                        'libexec',
                        'Microsoft.CodeAnalysis.Razor.Compiler.dll'
                    ),
                    '--razorDesignTimePath=' .. vim.fs.joinpath(
                        vim.fn.stdpath 'data' --[[@as string]],
                        'mason',
                        'packages',
                        'rzls',
                        'libexec',
                        'Targets',
                        'Microsoft.NET.Sdk.Razor.DesignTime.targets'
                    ),
                },
                config = {
                    handlers = require 'rzls.roslyn_handlers',
                    settings = {
                        ["csharp|background_analysis"] = {
                            dotnet_analyzer_diagnostics_scope = "fullSolution",
                            dotnet_compiler_diagnostics_scope = "fullSolution",
                        },
                        ["csharp|inlay_hints"] = {
                            csharp_enable_inlay_hints_for_implicit_object_creation = true,
                            csharp_enable_inlay_hints_for_implicit_variable_types = true,
                            csharp_enable_inlay_hints_for_lambda_parameter_types = true,
                            csharp_enable_inlay_hints_for_types = true,
                            dotnet_enable_inlay_hints_for_indexer_parameters = true,
                            dotnet_enable_inlay_hints_for_literal_parameters = true,
                            dotnet_enable_inlay_hints_for_object_creation_parameters = true,
                            dotnet_enable_inlay_hints_for_other_parameters = true,
                            dotnet_enable_inlay_hints_for_parameters = true,
                            dotnet_suppress_inlay_hints_for_parameters_that_differ_only_by_suffix = true,
                            dotnet_suppress_inlay_hints_for_parameters_that_match_argument_name = true,
                            dotnet_suppress_inlay_hints_for_parameters_that_match_method_intent = true,
                        },
                    },
                },
            })
        end
    }
}

And this does produce diagnostics inline for cs and razor files

@elan-hwang no because the package should provide default capabilities unless you have explicitly passing it through

@elan-hwang actually this could be your problem. This is in the source code. Since you are overwriting the default capabilities you may have to add this in

so your capabilities may have to end up looking like
local capabilities = vim.lsp.protocol.make_client_capabilities()
-- capabilities = vim.tbl_deep_extend('force', capabilities, require('cmp_nvim_lsp').default_capabilities())
capabilities = require('blink.cmp').get_lsp_capabilities(capabilities)
capabilities = vim.tbl_deep_extend("force", capabilities, {
    textDocument = {
        diagnostic = {
            dynamicRegistration = true,
        },
    },
})

@elan-hwang I can confirm that its your overwriting of the capabilities because you are using the blink cmp framework. I don't use it but just installed and set it up and the snippet i sent with the capabilities does not work with your setup, but adding in the force of the capabilities for diagnostic does work
return {
    {
        "seblj/roslyn.nvim",
        dependencies = {
            "tris203/rzls.nvim",
        },
        config = function()
            require("rzls").setup({})
            local capabilities = vim.lsp.protocol.make_client_capabilities()
            -- capabilities = vim.tbl_deep_extend('force', capabilities, require('cmp_nvim_lsp').default_capabilities())
            capabilities = require('blink.cmp').get_lsp_capabilities(capabilities)
            capabilities = vim.tbl_deep_extend("force", capabilities, {
                textDocument = {
                    diagnostic = {
                        dynamicRegistration = true,
                    },
                },
            })
            require("roslyn").setup({
                filewatching = true,
                args = {
                    '--logLevel=Information',
                    '--extensionLogDirectory=' .. vim.fs.dirname(vim.lsp.get_log_path()),
                    '--razorSourceGenerator=' .. vim.fs.joinpath(
                        vim.fn.stdpath 'data' --[[@as string]],
                        'mason',
                        'packages',
                        'roslyn',
                        'libexec',
                        'Microsoft.CodeAnalysis.Razor.Compiler.dll'
                    ),
                    '--razorDesignTimePath=' .. vim.fs.joinpath(
                        vim.fn.stdpath 'data' --[[@as string]],
                        'mason',
                        'packages',
                        'rzls',
                        'libexec',
                        'Targets',
                        'Microsoft.NET.Sdk.Razor.DesignTime.targets'
                    ),
                },
                config = {
                    capabilities = capabilities,
                    handlers = require 'rzls.roslyn_handlers',
                    settings = {
                        ["csharp|background_analysis"] = {
                            -- background_analysis = {
                            --     dotnet_analyzer_diagnostics_scope = "openFiles",
                            --     dotnet_compiler_diagnostics_scope = "fullSolution",
                            -- },
                            dotnet_analyzer_diagnostics_scope = "fullSolution",
                            dotnet_compiler_diagnostics_scope = "fullSolution",
                        },
                        ["csharp|inlay_hints"] = {
                            csharp_enable_inlay_hints_for_implicit_object_creation = true,
                            csharp_enable_inlay_hints_for_implicit_variable_types = true,
                            csharp_enable_inlay_hints_for_lambda_parameter_types = true,
                            csharp_enable_inlay_hints_for_types = true,
                            dotnet_enable_inlay_hints_for_indexer_parameters = true,
                            dotnet_enable_inlay_hints_for_literal_parameters = true,
                            dotnet_enable_inlay_hints_for_object_creation_parameters = true,
                            dotnet_enable_inlay_hints_for_other_parameters = true,
                            dotnet_enable_inlay_hints_for_parameters = true,
                            dotnet_suppress_inlay_hints_for_parameters_that_differ_only_by_suffix = true,
                            dotnet_suppress_inlay_hints_for_parameters_that_match_argument_name = true,
                            dotnet_suppress_inlay_hints_for_parameters_that_match_method_intent = true,
                        },
                    },
                },
            })
        end
    }
}

This screenshot is with that configuration above

Ah, this is a "bug" from me as I was refactoring things. Previously it was not possible to override the dynamicRegistration = true for capabilities, and it shouldn't be, because otherwise diagnostics will not work.
I will fix

@seblj just pulled the latest changes, removed the code I added in the example to force the capabilities, and the diagnostics still work


Error building iOS app

There is probably a basic solution to this problem but cloning the repository and building the project for the iOS app in Xcode results in the error 'SDWebImage/UIImageView+WebCache.h' file not found in PWBeaconCell.m on the import line #import <SDWebImage/UIImageView+WebCache.h> -- wondering if anyone else has seen this.

Found a solution elsewhere. This can be fixed by running git submodule update --init --recursive in the physical-web directory immediately after you clone.

hi please explain how this is done.. do I have to clone it or can I just download it first?
Also how do I run the command posted
thanks for your help

Hi, did you ever get this working or ios? If so can you share?
Thanks


Switch to using st2client

Requires st2client.js 0.4.1. ETA: EoD PST

I agree that we need to kind of take a step back and see the whole picture. At the same time, I really see a value for us to switch to stream as it is definitely the better communication channel than calling a webhook.
The thing I need to know is whether we use ST2_ROUTE somewhere else at the moment. If we don't, it seems like an extremely easy way for us to support both channels for the time being and figure out what we want at the end by fiddling in code rather than having a scientific discussion. If we don't, we should merge that one and start playing with it. It would unblock me on getting custom formatting and it won't block us from using and improving the old mechanics in case we find a good reason to stick with that.
You're saying we want to be able to skip some notifications. Ok, lets do that. With stream we can make it by a) adding a flag in execution context or b) by emitting specific event for chatops results (same way we do now with webhook, short of webhook itself). How exactly do you want to differentiate between actions that will or won't notify?

I'm +1 on merging this: ChatOps works right now, sure, but it still needs some love from us, and since we have time to focus on this right now, I'd say streams is a good place to start. Some minor things may regress for a while, but we can get this polished before the next release, and nobody will notice a thing unless they're running bleeding edge. This PR is great to get the ball rolling.
Re actions that will or won't notify: I think we should treat chatops-triggered executions and other executions as we do now, but extend it a bit:
— notify of every execution triggered by a chatops command UNLESS specified otherwise in an alias YAML definition (I have this working on my local instance, that's what @enykeev referenced before)
— not notify of anything else UNLESS there's a custom rule a user created

ChatOps works right now, sure, but it still needs some love from us, and since we have time to focus on this right now, I'd say streams is a good place to start. Some minor things may regress for a while, but we can get this polished before the next release, and nobody will notice a thing unless they're running bleeding edge. This PR is great to get the ball rolling.

I agree and admire the spirit but I do not think we have discussed the use-cases. It is not like this approach was not available when we/I originally designed it the way it is right now. Like I said lets have a clear discussion on what and where and then move this PR forward based on a shared understanding.

That's nothing if not sensible, I agree.


Automated cherry pick of #2873: fix: fail to update reserved ip notes

Cherry pick of #2873 on release/2.10.0.
#2873: fix: fail to update reserved ip notes

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@aaf1faf). Click here to learn what that means.
The diff coverage is 0%.

@@               Coverage Diff                @@
##             release/2.10.0   #2874   +/-   ##
================================================
  Coverage                  ?    7.6%
================================================
  Files                     ?     411
  Lines                     ?   64692
  Branches                  ?       0
================================================
  Hits                      ?    4923
  Misses                    ?   59346
  Partials                  ?     423

Flag
Coverage Δ

#aFlag
7.6% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/reservedips.go
11.68% <0%> (ø)

Continue to review full report at Codecov.

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

/approve
/lgtm


Using Predicates for Verification

Context

Previously all our verification happened depending on the type of the claim value. This can be seen in the verifyClaimValues method with so many instanceof checks.
This caused us to implement unwanted hacks like NonEmptyClaim type to do certain validations
To avoid this, we are moving all our claim validations to a collection of predicates that can be built.

Changes

All assertion calls (assertValidInstantClaim, assertValidAudienceClaim) are moved into BaseVerification
Asserting Collections (old code - Link) now has its own method assertValidCollectionClaim
requireClaim method is renamed to checkIfNeedToRemove to resemble its functionality which is to remove validation for any claim for which the value is passed as null
We have rearranged the position of the methods for better readability. This causes the diff to be really tough to compare with.
Introduced getLeewayFor method which will be used get leeway for each claim.
customLeeways will now store the custom leeway value provided for corresponding Claims. This avoids the old behavior where leeway as a claim value to be checked.
We will no longer need to store Generic Objects in the expectClaim method
Hack used to compare aud claim using AUDIENCE_EXACT and AUDIENCE_ANY has now been removed. Since same claim name is used for key, Map ensures uniqueness mentioned in the document
NonEmptyClaim class removed

Testing

We made few fixes to existing test cases to make it compatible to our new changes
We haven't added more tests since this was only an internal refactor and no behaviour has been added or modified to be tested

This is a seperate PR into the existing predicates support branch, so as to ensure the unrefactored version is left clean for us to make flexible decisions

Going ahead with the merge here. I have addressed the reviews mentioned here. Since another PR will be created to merge into v4-dev, We can go through this again if needed


Problem loading config in Windows platform

Hi,
I am trying to load config .toml file using below command in windows.
gitleaks --path="F:\Test\secret_scan\vuln_app" --no-git --report="F:\Test\secret_scan\scan_report.json" --config-path="F:\Test\secret_scan\gitleaks\examples\leaky-repo.toml"
But it is giving me below error.
time="2021-02-24T10:46:49+05:30" level=error msg="problem loading config: error parsing regexp: invalid escape sequence: \\T"
I have tried with multiple .toml files however nothing works. Even for a blank .toml file also it gives same error.
However same command works fine in linux platform.

cc @zricethezav
Best Regards

any toml config manifested the same way actually.

I unfortunately do not have a windows machine to test on. If someone could provide a solution that would be great

Reverse the slashes will work. Use / instead of \

Problem does not exist anymore with Gitleaks v8


WIP: Radiology processing job endpoints

Basic prototype done:

Codecov Report

Merging #121 (355493f) into master (453d957) will decrease coverage by 2.21%.
The diff coverage is 0.88%.

@@            Coverage Diff             @@
##           master     #121      +/-   ##
==========================================
- Coverage   64.59%   62.38%   -2.22%
==========================================
  Files          41       42       +1
  Lines        2627     2722      +95
==========================================
+ Hits         1697     1698       +1
- Misses        930     1024      +94

Impacted Files
Coverage Δ

data_processing/common/Container.py
0.00% <0.00%> (ø)

data_processing/scanManager/extractRadiomics.py
0.00% <0.00%> (ø)

data_processing/scanManager/generateScan.py
0.00% <0.00%> (ø)

data_processing/scanManager/windowDicoms.py
0.00% <0.00%> (ø)

data_processing/services/radiology_service.py
0.00% <0.00%> (ø)

data_processing/common/config.py
86.27% <25.00%> (-2.51%)
:arrow_down:

Continue to review full report at Codecov.

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


feat(docdb): Add restore from snapshot and point in time

Description of your changes
This adds AWS restore features for DocumentDB to DBCluster. Restore works in the same way as for RDS.
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
Unit tests and the existing examples.

@safboukhari  @MisterMX  please rebase and solve conflicts


Any plans for Docker image?

Would love to give this a go in a Docker container if possible. 🐳

Hello @ItsNoted
Yep the application Dockerization is in the project RoadMap, not really right now but will be done ASAP.
I will put this issue as a project task, so you can check when it will be done.

Hello @ItsNoted
A new PR #45 is just merged into the repository and released (v1.2.2)
And the repository is configured to push a new docker image automatically when a release is created, you can check the image here: https://hub.docker.com/r/eloufirhatim/helper
If you can test it, and give me your feedback (errors if exists, enhancement, ...) it will be great.

Thanks for the deployment!
Could you please tag the version on docker hub? It will really improve the migration process in a near future.

@matbgn indeed it will be good, thanks for pointing that.
It's done on the last commit on the repo, now the docker hub image will contains the release tag in addition to the latest version.

Many thanks I will prepare a Caprover https://caprover.com/ definition file to able One-click app deployment based on tagged version.


refactor to rdFingerprintGenerator

Changelogs
This PR addresses the fingerprint deprecation warnings, see issue #225.

Refactoring fingerprint atom pair, rdkit, morgan, topological, and their count fingerprints to FingerprintGenerator.
ecfp-count now use the ECFP-6, to stay consistent.
added new decorator function dm.no_rdkit_log which disable RDKit log for a whole function.
set minimum rdkit version to avoid pandas based error for this version of datamol.

Checklist:

[x] Was this PR discussed in an issue? It is recommended to first discuss a new feature into a GitHub issue before opening a PR.
[x] Add tests to cover the fixed bug(s) or the new introduced feature(s) (if appropriate).
[ ] Update the API documentation is a new function is added, or an existing one is deleted.
[x] Write concise and explanatory changelogs below.
[x] If possible, assign one of the following labels to the PR: feature, fix or test (or ask a maintainer to do it for you).

The rdFingerprintGenerator.GetCountFingerprint can be used to compute the count based fingerprint.
The argument countSimulationindicates whether to compute the count fingerprint by bites simulation for computing efficiency. See more in this blog.
I assume in datamol, we want to compute the exact count-based fingerprint. Therefore, countSimulation should be set to False.

Since it's still draft, I can wait.

The tests are failing, probably due to the different set arguments in the fingerprint generators.
@maclandrol I need your help with revising default parameters.
And I think the values in the tests for fingerprints need to be updated.

Since it's still draft, I can wait.

The tests are failing, probably due to the different set arguments in the fingerprint generators. @maclandrol I need your help with revising default parameters. And I think the values in the tests for fingerprints need to be updated.

Ok, will do.

@zhu0619, the default parameters were wrong.  They are fixed now.
Still have to address this: https://github.com/danielfrg/mkdocs-jupyter/issues/200
Ideally in the next release, we should also have a minimum version for rdkit. As the pandas error still exists.

I also replaced seaborn by pure matplotllib in one of the notebook. Was getting an error and not sure how.
Feel free to merge anytime.


Fixes Issue #8: Add GitHub template for PRs

Description
Added the Pull Request template to the repository under .github directory as per GitHub's guidelines.
Fixes #8

PTAL!


When copying to clipboard remove delimiters

When you copy from input field to buffer text contains delimiters
789·954·654·987
12,345,655
I don't think that is right for all the cases.
Maybe manage this behavior by some option? { copy-delimiter: [false, true] }, for example

http://output.jsbin.com/ruhitifilo/1/
I will make a PR....

Thanks @cht8687
Released in v0.7.0


addition creates recurison error

[x] I am on the latest Poetry version.

[x] I have searched the issues of this repo and believe that this is not a duplicate.

[x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: MacOS 10.13

Poetry version: 0.11.4

Link of a Gist with the contents of your pyproject.toml file:

[tool.poetry]
name = "mypkg"
version = "2018.0.0"
description = "mypkg module"
authors = ["Devin Fee"]

[tool.poetry.dependencies]
python = "^3.6.5"
rasa_core = "^0.10.3"

[tool.poetry.dev-dependencies]
pytest = "^3.0"

Issue
Adding rasa_core bottoms out the recursion limit:
:$ poetry add rasa_core
Using version ^0.10.3 for rasa_core

Updating dependencies
Resolving dependencies... (2.6s)

[RecursionError]
maximum recursion depth exceeded

add [-D|--dev] [--git GIT] [--path PATH] [-E|--extras EXTRAS] [--optional] [--python PYTHON] [--platform PLATFORM] [--allow-prereleases] [--dry-run] [--] <name> (<name>)...

My recursion limit is set at 3000, and I updated it to the point where a segfault happens before the recursion limit is hit.

Alright, I've narrowed the problem space down quite a bit. The problem appears when keras is version 2.2 (or above):
[tool.poetry]
name = "demo"
version = "0.1.0"
description = ""
authors = ["Devin Fee"]

[tool.poetry.dependencies]
python = "3.6.5"

keras = "~2.1"
rasa_core = "^0.10.3"

[tool.poetry.dev-dependencies]
pytest = "^3.0"

Allowing keras v2.2+ raises a RecursionError, which is effectively what's in rasa_core's setup.py: "keras~=2.0" (which appears to mean keras >= 2.0, < 3.0).
Strangely, if you were to install every dependency of rasa_core except for rasa_core itself, then keras can be v2.2+:
[tool.poetry]
name = "demo"
version = "0.1.0"
description = ""
authors = ["Devin Fee"]

[tool.poetry.dependencies]
python = "^3.6"

jsonpickle = "^0.9.6"
six = "^1.11"
redis = "^2.10"
fakeredis = "^0.10.3"
future = "^0.16.0"
numpy = "^1.15"
typing = "^3.6"
requests = "^2.19"
graphviz = "^0.8.4"
keras = "^2.0" # TODO: revert to: keras = "~2.0"
tensorflow = ">= 1.7, < 1.9"
h5py = "^2.8"
apscheduler = "^3.5"
tqdm = "^4.24"
configargparse = "^0.13.0"
networkx = "^2.1"
fbmessenger = "^5.3"
pykwalify = "<= 1.6.0"
coloredlogs = "^10.0"
"ruamel.yaml" = "^0.15.50"
flask = "^1.0"
flask_cors = "^3.0"
scikit-learn = "^0.19.2"
rasa-nlu = "^0.13.1"
slackclient = "^1.2"
python-telegram-bot = "^10.1"
twilio = "^6.16"
mattermostwrapper = "^2.1"
colorhash = "^1.0"

# rasa_core = "^0.10.3" # TODO: notice how this isn't installed, so keras can be 2.2+

[tool.poetry.dev-dependencies]
pytest = "^3.0"
ipython = "^6.5"

This is really strange. I am not sure where the issue is coming from.
I will investigate and get back to you.

Do you know when the bug fix with the patch related to this issue will be out? It is blocker to our team adapting poetry

This is fixed in the latest 0.11.5 release :-)


Uncaught TypeError: t is undefined

Trying to use frappe-gantt in my Django projetc.
I have install npm install frappe-gantt and serve dist folder in my Django project :
<link` rel="stylesheet" href="{% static 'dist/frappe-gantt.css' %}">

Trying to run simple example :

seems to be due to the way call the constructor. correct code seems to be: var gantt = new Gantt("#gantt", tasks, {});

Thanks for this catch! Fixed now.

I'm trying the same code with the default dict and I don't face this error. Perhaps it's since been updated. I'm leaving this open for now so that you can check again in the new version (to be released soon).

Sorry, I expressed myself badly
In github source code (https://github.com/frappe/gantt/README/), it is mentionned in "start hacking:" section to instanciate Gantt object like this : var gantt = new Gantt("#gantt", tasks);
but in fact, right code should be var gantt = new Gantt("#gantt", tasks, {});
But maybe I missunderstand

@LECARROU, no I understood you. I'm saying that I don't face that error with var gantt = new Gantt("#gantt", tasks);.

Closing as can't reproduce.


Create bands on line charts

Is it possible to limit the area drawn by a serie to the value of another serie as in grafana or dygraphs?

That's not possible as of yet. Let's track this as an enhancement.

I would also be interested by that.
I'm trying to implement it, but I don't well see how area is drawn using SVG... (and I think it's not that easy :) )

We had a similar discussion already here #283 and I've produced an example with masking http://jsbin.com/yahuzun/4/edit?css,js,output which was only to test the mechanism.
After closer consideration I believe that the easiest way to enable users to build band area charts would be to add an option to Chartist that allows you to associate two series together to form a band.
I have something like this in mind:
var chart = new Chartist.Line('.ct-chart', {
  labels: ['1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12'],
  series: [
    {
      name: 'max',
      data: [12, 9, 7, 8, 5, 4, 6, 2, 3, 3, 4, 6]
    },
    {
      name: 'min',
      data: [4,  5, 3, 7, 3, 5, 5, 3, 4, 4, 5, 5]
    }
  ]
}, {
  bands: [
    {lower: 'min', upper: 'max'}
  ]
});

This would still draw the regular series min and max (if not prevented with showLine and showPoint set to false) but would also create a band on the line chart canvas that is constructed from the series referenced by name in the bands objects. Its also possible to add options into the bands objects and of course create multiple bands.
Thoughts?
Btw. I renamed the issue to something more generic.

Since you're taking a closer look at it, let me show you a really nice implementation of this feature (scroll down).
I know that chartist is not intended to provide that kind of time-serie data on the x-axis but I don't really want it
Also, most common usage of this feature would be something like this, which I think you already have it in mind since you've said that it'd be possible to create multiple bands.
bands: [
  {lower: 'mean', upper: 'max'},
  {lower: 'min', upper: 'mean'}
]

I thought that it could be to use the areaBase option for an area to define the lower bound of the area.
new Chartist.Line('.ct-chart', {
  labels: [1, 2, 3, 4, 5, 6, 7, 8],
  series: [
	{
	  name: 'mini',
	  data: [0, 0, 0, 0, 0, 1, 3, 4, 5, 6]
	},
	{
	  name: 'maxi',
	  data: [5, 2, 3, 4, 6, 8.5, 11, 13, 15, 16]
	}
  ]
}, {
  low: -2,
  // showLine: false,
  showPoint: false,
  series: {
	'maxi': {
	  showArea: true,
	  areaBase: 'mini'
	},
  }
});

This way, it's easy to keep Chartist draw lines or points for each serie.

@maftieu that's also an interesting approach! But then it will be hard to attach band options like custom class name etc. I also thought of something like this:
var chart = new Chartist.Line('.ct-chart', {
  labels: ['1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12'],
  series: [
    {name: 'max', data: [12, 9, 7, 8, 5, 4, 6, 2, 3, 3, 4, 6]},
    {name: 'avg', data: [6, 7, 5, 7.5, 4, 3, 5.5, 2, 3, 3, 4, 6]},
    {name: 'min',  data: [4,  5, 3, 7, 3, 5, 5, 3, 4, 4, 5, 5]}
  ]
}, {
  plugins: [Chartist.plugins.ctBands({
      bands: [
        {lower: 'avg', upper: 'max', className: 'avg-to-max'},
        {lower: 'min', upper: 'avg', className: 'avg-to-min'}
      ],
      removeSeries: ['avg']
  })]
})

Where removeSeries would remove those series (including points, lines and regular areas) after the bands were created. I want to make sure someone can still show some lines and / or points if desired but can also remove series that were only used to draw the bands.
I think this functionality fits nicely into a plugin. What do you think? It's just a matter of including an other script and referencing the plugin on the chart.

It certainly looks promising! I still wonder if there's a possibility this way to make a chart like this: http://jsbin.com/suquco/1/edit?html,js,console,output without too much hassle.

@Martinomagnifico for this use-case we can easily make the areaBase configurable per series with the series config object and then just have regular step line charts with two different bases (one at 0 and the other at 100). I can add this change for the series based areaBase value into 0.9.0.

I think this functionality fits nicely into a plugin.
Yeah! It'd be even better!

Wow, that would be very cool!!!

What is the progress on this?

Hi Gion,
I'm still struggling with the masking plugin. Would it be an option to use (svg) clipPath instead of mask? And how would that be defined? Imagine a funnel-shape, starting at 10 at left and diverging to the right, (to 30 and 250 for example) consisting of multiple lines (either stacked or not). Would the clip path then be a clip path of the whole group where the highest and lowest points of it are the highest and lowest points of all lines?
The masking thing had funny side effects in combination with transparency, so I hope using clip-path does allow that.

Any progress on this?

Hi, any news on this?

We have recently updated the stack and backbone of Chartist, and we're ready again to work on enhancements and plugins. Just wanted to know if this is still desired.

Yes, to me that would be awesome.


Modify the peerDependencies to reflect the need for react 16.3.0

When using the alpha build of ReDoc, running in an environment with React 16.2.0 results in an error due to the missing createContext API. This PR updates the package.json peerDependencies to reflect the need for react >= 16.3

Coverage remained the same at 78.105% when pulling 4c0f8b1fd00e570d68ad63654cf88958bee331ea on fritz-c:fix-peer-deps into 3fabce4d1912671c97bed17cfa4e4f5b37b1b2b9 on Rebilly:master.

Seems that something wrong is with Travis and env variables. Anyway looks good!
Thanks for PR!


wasmtime: enable stack probing for x86_64 targets.

This PR unconditionally enables stack probing for x86_64 targets.
On Windows, stack probing is always required because of the way Windows commits stack pages (via guard page access).
Fixes #5340.

I'll see if I can update the test not to use SIMD.

/bench_x64
Curious!

instantiation :: cycles :: benchmarks/bz2/benchmark.wasm
No difference in performance.
[157158 193189.52 549782] commit.so
[159262 173947.68 198430] main.so
execution :: cycles :: benchmarks/bz2/benchmark.wasm
No difference in performance.
[128304680 135393814.80 220629322] commit.so
[128044472 130380997.52 132394284] main.so
compilation :: cycles :: benchmarks/bz2/benchmark.wasm
No difference in performance.
[205479004 221452290.72 251142766] commit.so
[202111130 220026159.20 254842212] main.so
instantiation :: cycles :: benchmarks/pulldown-cmark/benchmark.wasm
No difference in performance.
[186726 204750.96 228796] commit.so
[185846 205393.68 235104] main.so
compilation :: cycles :: benchmarks/spidermonkey/benchmark.wasm
No difference in performance.
[6658721004<PHONE_NUMBER>.44<PHONE_NUMBER>] commit.so
[6638935210<PHONE_NUMBER>.16<PHONE_NUMBER>] main.so
execution :: cycles :: benchmarks/spidermonkey/benchmark.wasm
No difference in performance.
[1102708506<PHONE_NUMBER>.84<PHONE_NUMBER>] commit.so
[1101851712<PHONE_NUMBER>.84<PHONE_NUMBER>] main.so
compilation :: cycles :: benchmarks/pulldown-cmark/benchmark.wasm
No difference in performance.
[297517394 323611868.32 376552374] commit.so
[292725104 324405945.28 358608704] main.so
instantiation :: cycles :: benchmarks/spidermonkey/benchmark.wasm
No difference in performance.
[487538 508903.04 619584] commit.so
[483196 508709.36 553900] main.so
execution :: cycles :: benchmarks/pulldown-cmark/benchmark.wasm
No difference in performance.
[9578432 9776958.56 10226136] commit.so
[9591706 9780255.04 9987402] main.so


fix: Set correct version of AWS provider on module root

Description

Set correct version on module root

Motivation and Context

The root version was not updated in https://github.com/terraform-aws-modules/terraform-aws-acm/pull/125
Resolves #127

Breaking Changes

No

How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[ ] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

This PR is included in version 4.3.1 :tada:


Current CI/CD pipeline for Python 3.7 fails because of issue with importlib_metadata and flake8

Example pipeline that fails: https://github.com/rstudio/py-shiny/actions/runs/3183453613
See also relevant issues here and here.

Tried to fix it with #349, but the issue persists because flake8>5.0.0 is still installed by py-htmltools:
https://github.com/rstudio/py-shiny/actions/runs/3183453613/jobs/5192917088#step:5:21
I opened a Pull Request in py-htmltools as well; https://github.com/rstudio/py-htmltools/pull/44

I figured we don't need to install the full requirements-dev.txt from py-htmltools, but only the wheel package. Therefore I propose the following change: https://github.com/rstudio/py-shiny/pull/349/files#diff-038d392b404f94b2ee8e3f10b6ae76784160379d9e90638f78ee65df63353221L36
However, the issue still persists, because the following command:
python3 -m pip install --force-reinstall dist/shiny*.whl --find-links ../py-htmltools/dist/

seems to install importlib-metadata 5.0.0 anyway:
https://github.com/rstudio/py-shiny/pull/349/checks#step:7:1711

Weirdly enough, after pinning importlib_metadata in setup.cfg, the tests for Python 3.7 succeed, but they fail for 3.8.

@fpgmaas Yeah, I think the random port number generator just happened to pick a port number that browsers refuse to connect to. I'll fix that.

@jcheng5 I will close this issue since the original issue seems to be resolved.


issue with 3.10 flutter

please upgrade dependencies

@micodev I published the new version 0.1.9 with latest dependencies
Let's me know if you have any trouble.


Optimised svg icons via SVGO

JIRA issue: https://digital-engagement.atlassian.net/browse/SDPA-4520
Changed

Optimised Icon component's scgs assets/img/ via svgo command

Notes

Custom library is one of the the culprits for the loading script https://github.com/dpc-sdp/ripple/blob/master/packages/components/Atoms/Icon/icon-library.js#L12
We also need to minimised other websites svgs?
Haven't spent much time to look into making icon-library.js better. I'm thinking of removing this as dependency in Icon.vue and adding a static Object listing of Icon names but this could be breaking change. Happy to proceed if everyone agrees.
Any suggestions?

Screenshots

Comparison between develop and this branch
Develop: Summary total scripting time: 3187
This branch: 2957
This branch

Develop

@rubyllamadora In my opinion, just need merge this change into #774 to update the icon paths. Other svg should still go through the webpack svgo plugin, so no need to worry I think.

Thanks @tim-yao. #774 is using JS so no need to optimise. We can probably take this as first step and will rethink of how we can handle other issues later? I avoided applying other refactor in here as there's already several file changes.

@rubyllamadora In my opinion, just need merge this change into #774 to update the icon paths. Other svg should still go through the webpack svgo plugin, so no need to worry I think.

Will update #774 PR with optimised paths.

Closing as this has been applied to #774


feat: add Python install script and package.json for mip

hey @SpotlightKid
This one needs a bit more work.
It is advised for the package files to be placed in their own folder mrequests to cleanup the repo.
This of course requires the install scripts to be reworked slightly.
If you want I can take a stab at it starting from the latest master :)

Let's do the re-organization after I merge this.


Edit schedule item height issue (buttons not visible)

Description of bug
I wanted to edit a scheduler item (persona bar > Scheduler > Second tab > Click on edit button
I see the specific scheduler item panel expand, however the height is not enough to show the buttons for this item
Screenshots

Affected version

[x]  9.5.0 latest supported release

Affected browser

[x] Chrome

What resolution is your display?

Crap could it be that simple...

I'm going to make a note that we should establish a "minimum" recommendation for display resolution

Meh, well as I will work on those modules in the future, I would really like them to be properly responsive, but well that is what we have and it is a massive undertaking to rewrite it all. But yeah right now this was not build to be used on smaller screens :(


local contact section should be collapsable even when no search is started

According to @AmandineLP:

the known contacts header should be displayed when no search is started too, with the label: "Known contacts (-)" and the following message: "Too many contacts, please use the search field"

Validated and covered by automated test


react-elements: DbChip component should process parameter checked

It would be great, if it were possible to include DbChip with the information, if the input should be checked or not.
Examples for possible implementations:

This will get released as v0.21.0 soon.


Allow setting throwable for CommandResult.

API | Common
Resolves SpongePowered/SpongeAPI#1073

I'm new to contributing, and this has an API change. Any guidance would be appreciated.

Closing, see API PR for explanation


Allow configuring sections

Currently, each script is emitted as an individual ROMX section.

One may want to emit scripts to ROM0, for example (and, if RGBDS later allows arbitrary section kinds via hardware description files, others);
One may want all scripts to lie within a single section.

I think this could be solved via a CLI switch; in particular, if the section type given is empty, no section directives would be emitted.

In my original drafts of the language (and maybe the c++ version?), this was determined by the env; i must have just forgotten it.
That being said, i don't think a command line flag is the right option. I think the best way to do it would be to define a default per env, with overrides for individual scripts. The only issue is that i don't have any ideas for the latter's syntax.


PEAR-2169: Responsive cart

Description
Also, updated the remove from cart button across the app for consistency.
Checklist

[ ] Added proper unit tests
[ ] Left proper TODO messages for any remaining tasks
[ ] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)

this looks good to me! 👍


[BUG] Supabase Setup

Using the same template to query a csv file works with Pinecone but not with Supabase. I get the following error with Supabase:
Error searching for documents: PGRST202 Could not find the function public.CFP(match_count, query_embedding) in the schema cache Searched for the function public.CFP with parameters match_count, query_embedding or with a single unnamed json/jsonb parameter, but no matches were found in the schema cache.
I am attaching a screenshot:

I have triple-checked the Supabase API Key and Project URL. They seem to be OK

Yeah I'm getting some other type of errors with Supabase.. Seems like there is an update needed perhaps?

you'll have to use the pg-vector extension. you can follow the guide here:
1.) Register Supabase account
2.) Dashboard => New Project =>  SQL Editor => New Query
3.) Copy & Paste queries below and execute:
-- Enable the pgvector extension to work with embedding vectors
create extension vector;

-- Create a table to store your documents
create table documents (
  id bigserial primary key,
  content text, -- corresponds to Document.pageContent
  metadata jsonb, -- corresponds to Document.metadata
  embedding vector(1536) -- 1536 works for OpenAI embeddings, change if needed
);

-- Create a function to search for documents
create function match_documents (
  query_embedding vector(1536),
  match_count int,
  filter jsonb DEFAULT '{}'
) returns table (
  id bigint,
  content text,
  metadata jsonb,
  similarity float
)
language plpgsql
as $$
#variable_conflict use_column
begin
  return query
  select
    id,
    content,
    metadata,
    1 - (documents.embedding <=> query_embedding) as similarity
  from documents
  where metadata @> filter
  order by documents.embedding <=> query_embedding
  limit match_count;
end;
$$;

I have it working now. I also have a couple of comments regarding the "Supabase Upsert Document" module:

The Supabase API Key corresponds to the "service_role" key
The Query Name field corresponds to the name of the function, in the code you presented above, the function is "match_documents".

Best.
Jay

I tried everything as described here, documents are being upserted however there is an error: 42883 operator does not exist: extensions.vector <=> extensions.vector null
I couldn't run this command as it said its already installed: "create extension vector;"

Regards

I solved the issue.

@HenryHengZJ and @mgunnin just wanted to say ty. Reading both your comments allowed me to set up a working example. I wish some of that was in official documentation or something tho, cause I was lost for a good while. Anyway, thanks again.

@sunnythaper its now available - https://docs.flowiseai.com/vector-stores/supabase

@HenryHengZJ wow, thank you so much! I hope this saves future users some time! Potentially future me when I try to do this again after a brief hiatus.


Enables linux-aarch64 builds

Checklist

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

@danielnachun: can you please reviewthis MR? It is required to have a linux-aarch64 build of the nvim-feedstock.  Thanks in advance!


Add finalizer to on-demand backup spec

@delgod @blez This is already added on the release branch: https://github.com/percona/percona-xtradb-cluster-operator/blob/release-1.8.0/deploy/backup/backup.yaml#L5 but there it is commented since the default storageName: fs-pvc

@delgod , what should we do in such case?

is the finalizer works fine for PVC storage?
it shouldn't be any issues with PVC storage

Test name
Status

haproxy
passed

big-data
passed

storage
passed

recreate
passed

upgrade-haproxy
passed

scaling
passed

self-healing
failed

init-deploy
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

upgrade-proxysql
passed

limits
passed

security-context
passed

monitoring-2-0
passed

demand-backup
passed

smart-update
passed

self-healing-advanced
passed

affinity
passed

one-pod
passed

auto-tuning
passed

operator-self-healing
failed

pitr
failed

proxysql-sidecar-res-limits
failed

upgrade-consistency
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/846/commits/6246d51c9d65c273f8b369b1e551d91e755b3f19
image: perconalab/percona-xtradb-cluster-operator:PR-846-6246d51c

@delgod @tplavcic
I've added the logic which checks if S3 finalizer was set for non S3 backup and remove it in such case.

Test name
Status

big-data
passed

upgrade-haproxy
passed

storage
passed

recreate
passed

haproxy
passed

scaling
passed

self-healing
passed

init-deploy
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

limits
passed

self-healing-advanced
passed

monitoring-2-0
passed

demand-backup
passed

smart-update
passed

affinity
passed

operator-self-healing
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
passed

upgrade-consistency
passed

tls-issue-self
passed

demand-backup-encrypted-with-tls
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

scheduled-backup
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/846/commits/48a11fce16afeb3dd855e6b51fd471d3760db1d6
image: perconalab/percona-xtradb-cluster-operator:PR-846-48a11fce

Test name
Status

recreate
passed

big-data
passed

storage
passed

haproxy
passed

upgrade-haproxy
passed

scaling
passed

init-deploy
passed

scaling-proxysql
passed

self-healing
passed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

limits
passed

self-healing-advanced
passed

monitoring-2-0
passed

demand-backup
passed

smart-update
passed

operator-self-healing
failed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

pitr
passed

users
failed

demand-backup-encrypted-with-tls
passed

upgrade-consistency
passed

scheduled-backup
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/846/commits/aa556f0d30b4cfaa61d2d864d5308b031b26477b
image: perconalab/percona-xtradb-cluster-operator:PR-846-aa556f0d

Test name
Status

big-data
passed

storage
passed

self-healing
passed

upgrade-haproxy
passed

self-healing-advanced
passed

operator-self-healing
passed

scaling
passed

scaling-proxysql
passed

security-context
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/846/commits/aa556f0d30b4cfaa61d2d864d5308b031b26477b
image: perconalab/percona-xtradb-cluster-operator:PR-846-aa556f0d

Test name
Status

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/846/commits/aa556f0d30b4cfaa61d2d864d5308b031b26477b
image: perconalab/percona-xtradb-cluster-operator:PR-846-aa556f0d

Test name
Status

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/846/commits/aa556f0d30b4cfaa61d2d864d5308b031b26477b
image: perconalab/percona-xtradb-cluster-operator:PR-846-aa556f0d

Test name
Status

haproxy
passed

init-deploy
passed

limits
passed

upgrade-haproxy
passed

monitoring-2-0
passed

affinity
passed

storage
passed

one-pod
passed

self-healing
passed

auto-tuning
passed

self-healing-advanced
passed

proxysql-sidecar-res-limits
passed

operator-self-healing
passed

users
passed

recreate
passed

restore-to-encrypted-cluster
passed

scaling
passed

demand-backup
passed

scaling-proxysql
passed

pitr
passed

security-context
passed

demand-backup-encrypted-with-tls
passed

scheduled-backup
passed

big-data
passed

upgrade-proxysql
passed

smart-update
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/846/commits/aa556f0d30b4cfaa61d2d864d5308b031b26477b
image: perconalab/percona-xtradb-cluster-operator:PR-846-aa556f0d


Responsive design / Mobile friendly interface

Hey!! First of all, thank you very much for this great app!
I'd like to share a thought: I think that it's a huge downside the fact that YOURLS isn't responsive and mobile-friendly.
Are there any plans on that matter?
Once again, thank you for your efforts!

Lots of work has gone into redesigning for 2.0, see #1383 for example. It's not finished yet (e.g. #1621), and there's no ETA for when 2.0 will come out, but there are plans. :smile_cat:

Looking forward to it! Keep up the good work! :)

I wish YOURLS v2 is responsive,SEO friendly, Multi domains and multi themes ready ... I got stuck restyling the old up to my tasre :( http://icu2.cf/r/