Error: Error in migration engine. Reason: [C:\Users\runneradmin.cargo\git\checkouts\quaint-9f01e008b9a89c14\6efc6f6\src\connector\postgres\error.rs:138:29] index out of bounds: the len is 1 but the index is 1

Command: prisma migrate dev --preview-feature
Version: 2.13.0
Binary Version: 833ab05d2a20e822f6736a39a27de4fc8f6b3e49
Report: https://prisma-errors.netlify.app/report/12281
OS: x64 win32 10.0.19041
JS Stacktrace:
Error: Error in migration engine.
Reason: [C:\Users\runneradmin\.cargo\git\checkouts\quaint-9f01e008b9a89c14\6efc6f6\src\connector\postgres\error.rs:138:29] index out of bounds: the len is 1 but the index is 1

Please create an issue in the migrate repo with
your `schema.prisma` and the prisma command you tried to use 🙏:
https://github.com/prisma/migrate/issues/new

    at ChildProcess.<anonymous> (D:\project\waaw-backend\node_modules\@prisma\cli\build\index.js:59340:23)
    at ChildProcess.emit (events.js:210:5)
    at ChildProcess.EventEmitter.emit (domain.js:475:20)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)

Rust Stacktrace:
[C:\Users\runneradmin\.cargo\git\checkouts\quaint-9f01e008b9a89c14\6efc6f6\src\connector\postgres\error.rs:138:29] index out of bounds: the len is 1 but the index is 1

From engine's error reporting meeting. The error is from quant, it needs more flexible error parsing (@do4gr)

same here!

command: npx prisma migrate dev --create-only --preview-feature
client, cli version: 2.13.0
os env: Windows 10 Home x64

PS E:\dev-fullstack\bim-server01> npx prisma migrate dev --create-only --preview-feature
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Datasource "db": PostgreSQL database "bim", schema "bim" at "localhost:5432"
Oops, an unexpected error occured!
Error in migration engine.
Reason: [C:\Users\runneradmin.cargo\git\checkouts\quaint-9f01e008b9a89c14\6efc6f6\src\connector\postgres\error.rs:138:29] index out of bounds: the len is 1 but the index is 1

// schema.prisma file

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

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

generator dbml {
  provider = "prisma-dbml-generator"
}

model User {
  id          Int       @id @default(autoincrement())
  email       String    @unique
  password    String?
  firstName   String?
  lastName    String?
  role        RoleType  @default(guest)

  createdAt   DateTime  @default(now())
  updatedAt   DateTime  @updatedAt
  deletedAt   DateTime?
}

enum RoleType {
  guest
  user
  premium
  admin
}

Same here:

Oops, an unexpected error occured!
Error in migration engine.
Reason: [C:\Users\runneradmin.cargo\git\checkouts\quaint->9f01e008b9a89c14\bc3aa8a\src\connector\postgres\error.rs:138:29] index out of bounds: the len is 1 but the index is 1

Please create an issue in the migrate repo with
your schema.prisma and the prisma command you tried to use 🙏:
https://github.com/prisma/migrate/issues/new

It just happens when I use my local postgreSQL db. When I connect to my PostgreSQL AWS Cloud db it works and I don't get this error.
I tried with: yarn prisma migrate dev --create-only --preview-feature and yarn prisma migrate dev --preview-feature

Same here:

Oops, an unexpected error occured!
Error in migration engine.
Reason: [C:\Users\runneradmin.cargo\git\checkouts\quaint->9f01e008b9a89c14\bc3aa8a\src\connector\postgres\error.rs:138:29] index out of bounds: the len is 1 but the index is 1

Please create an issue in the migrate repo with
your schema.prisma and the prisma command you tried to use 🙏:
https://github.com/prisma/migrate/issues/new

It just happens when I use my local postgreSQL db. When I connect to my PostgreSQL AWS Cloud db it works and I don't get this error.
I tried with: yarn prisma migrate dev --create-only --preview-feature and yarn prisma migrate dev --preview-feature

I had the same problem in Postgres
if template0 || template1 -> deleted or corrupted
just restore (rebuild) template0 (template1) and the migration should work

I had the same problem in Postgres
if template0 || template1 -> deleted or corrupted
just restore (rebuild) template0 (template1) and the migration should work

I had the same error with my locally installed postgres database. To my surprise it worked with a postgres database in a docker container created like this: docker run --name prisma-test -e POSTGRES_PASSWORD=postgres -p 5433:5432 -d postgres:11, only by changing the connection url in the .env file.

I had the same error with my locally installed postgres database. To my surprise it worked with a postgres database in a docker container created like this: docker run --name prisma-test -e POSTGRES_PASSWORD=postgres -p 5433:5432 -d postgres:11, only by changing the connection url in the .env file.


Implement wsl compatibility

The possible ways I found:

cmd /c start URL ==> https://github.com/cpbotha/xdg-open-wsl/blob/7d40d572d0274db4b668b5d42797ebd3d8e16885/xdg_open_wsl/xdg_open_wsl.py#L191
powershell.exe Start URL ==> https://github.com/4U6U57/wsl-open/blob/6419bb63845acd0533f30bdc8258f8df5fbb25cb/wsl-open.sh#L18
wsl-open various tools that call themselves that act as a replacement for xdg-open and may have more methods than the 2 above.

⚠ A problem exists with the fallback chain, which may lead to problems in WSL environments or similar #57. Consider this during testing (there are proposed solutions in the issue) ⚠

Thanks @Nachtalb, for adding to the platform support. My only question about this is can is_wsl be implemented via presences of an environment variable instead of looking up a proc file?

@amodm

Thanks @Nachtalb, for adding to the platform support. My only question about this is - can is_wsl be implemented via presence of an environment variable instead of looking up a proc file?

There seems to be a "WSL_DISTRO_NAME" env var injected by WSL though it is not enforced and not available in every environment:

https://github.com/microsoft/WSL/issues/5914

IMHO checking for /proc/version is safer as one would have to specifically build a custom kernel to get the same outcome on a non-wsl system. It also seems to be a semi-standard way of checking for WSL in general.

https://github.com/microsoft/WSL/issues/4071#issuecomment-496737093
https://stackoverflow.com/questions/38086185/how-to-check-if-a-program-is-run-in-bash-on-ubuntu-on-windows-and-not-just-plain/43618657#43618657

Ok. I'm comfortable with the current determination of WSL env.
Another question I have is: this doesn't really fix #57, does it? I'm talking about the scenario where xdg-open is available, but fails to execute. Have you tested this PR in the WSL envs you mention in #57, and verified it to work?

Ah no it doesn't fix it. This would just be a implementation for wsl like the rest of the custom opener implementations. #57 is an entirely different problem, I just used the wsl as a case where the problem might occur.

Ah, ok. I'll be keeping this PR on hold until I've figured out a good way to handle that, because otherwise we can't declare effective WSL compatibility. I'll be merging this PR right after I've figured out an answer.

@Nachtalb, sorry about the delay here. I got WSL2 setup & running, and found that with wslu installed, the code on current main works fine. Without it, it fails.
Should I look at this PR as supporting WSL independent of wslu? If yes, is that a common enough scenario? If no, then I'd rather debug any bugs on WSL that's preventing this crate from working alongside wslu.
Thanks for helping me develop a better understanding of the WSL ecosystem. I'm not familiar with it enough to answer the above question on my own, so relying on your expertise here.

@Nachtalb, this is now merged, with the following additional changes:

Modified mechanism of is_wsl() to be determined by presence of enabled in /proc/sys/fs/binfmt_misc/WSLInterop. As per the doc, if this is disabled, then we anyways cannot invoke windows programs from linux. wslu seems to be doing the same.
Currently limited to opening only http(s) urls, as file:// urls require some extra handling. Hopefully, I'll find time to build that in before the upcoming v0.8.3 release.

I've tested it on a sandbox WSL setup, both with and without wslu installed, and it seems to work. Can you please give it a shot as well? All the more important, because tests for WSL is not yet automated. You can test for this by including the following in your Cargo.toml
[dependencies]
webbrowser = { git = "https://github.com/amodm/webbrowser-rs" }

Modified mechanism of is_wsl() to be determined by presence of enabled in /proc/sys/fs/binfmt_misc/WSLInterop. As per the doc, if this is disabled, then we anyways cannot invoke windows programs from linux. wslu seems to be doing the same.

Nice! I didn't know that.

I've tested it on a sandbox WSL setup, both with and without wslu installed, and it seems to work. Can you please give it a shot as well? All the more important, because tests for WSL is not yet automated. You can test for this by including the following in your Cargo.toml

I will do that once I am on my PC.

@Nachtalb, this is now out as v0.8.3


[Dev] Port Patch archive test again

Port again https://github.com/MinaProtocol/mina/pull/14712

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-nightly-me


Installing Sui Binaries fails on WSL 2 Ubuntu-20.04 instance

Steps to Reproduce Issue
On a windows machine install WSL and use WSL2 as default. The install Ubuntu-20.04
wsl.exe --install -d Ubuntu-20.04
Once that's done, restart cmd and type wsl to enter the kernel. Follow every step from the Sui docs on installing prerequisities and the Linux commands. Found here: https://docs.sui.io/devnet/build/install#linux-prerequisites
Once that's done install Sui Binaries: cargo install --locked --git https://github.com/MystenLabs/sui.git --branch devnet sui
It will fail. I tried multiple tags like devnet-0.25.0, devnet-0.23.1 and devnet-0.26.0.
Expected Result
Expected Sui to be installed.
Actual Result
error: failed to run custom build command for `protobuf-src v1.1.0+21.5`

Caused by:
  process didn't exit successfully: `/tmp/cargo-installSfhEMl/release/build/protobuf-src-4a75139ac4aec028/build-script-build` (exit status: 101)
  --- stdout
  running: "sh" "-c" "exec \"$0\" \"$@\"" "/home/leslie/.cargo/registry/src/github.com-1ecc6299db9ec823/protobuf-src-1.1.0+21.5/protobuf/configure" "--prefix=/tmp/cargo-installSfhEMl/release/build/protobuf-src-931a8e2d5c80be9f/out/install" "--disable-shared" "--enable-static" "--disable-maintainer-mode"
  checking whether to enable maintainer-specific portions of Makefiles... no
  checking build system type... x86_64-pc-linux-gnu
  checking host system type... x86_64-pc-linux-gnu
  checking target system type... x86_64-pc-linux-gnu
  checking for a BSD-compatible install... /usr/bin/install -c
  checking whether build environment is sane... yes
  checking for a race-free mkdir -p... /usr/bin/mkdir -p
  checking for gawk... gawk
  checking whether make sets $(MAKE)... yes
  checking whether make supports nested variables... yes
  checking whether UID '1000' is supported by ustar format... yes
  checking whether GID '1000' is supported by ustar format... yes
  checking how to create a ustar tar archive... gnutar
  checking whether make supports nested variables... (cached) yes
  checking for gcc... cc
  checking whether the C compiler works... yes
  checking for C compiler default output file name... a.out
  checking for suffix of executables...
  checking whether we are cross compiling... no
  checking for suffix of object files... o
  checking whether the compiler supports GNU C... yes
  checking whether cc accepts -g... yes
  checking for cc option to enable C11 features... none needed
  checking whether cc understands -c and -o together... yes
  checking whether make supports the include directive... yes (GNU style)
  checking dependency style of cc... gcc3
  checking whether the compiler supports GNU C++... no
  checking whether c++ accepts -g... no
  checking for c++ option to enable C++11 features... none needed
  checking dependency style of c++... none
  checking how to run the C preprocessor... cc -E
  checking for gcc... gcc
  checking whether the compiler supports GNU C... (cached) yes
  checking whether gcc accepts -g... yes
  checking for gcc option to enable C11 features... (cached) none needed
  checking whether gcc understands -c and -o together... (cached) yes
  checking dependency style of gcc... (cached) gcc3
  checking how to run the C preprocessor... gcc -E
  checking how to run the C++ preprocessor... /lib/cpp

  --- stderr
  configure: error: in `/tmp/cargo-installSfhEMl/release/build/protobuf-src-931a8e2d5c80be9f/out/install/build':
  configure: error: C++ preprocessor "/lib/cpp" fails sanity check
  See `config.log' for more details
  thread 'main' panicked at '
  command did not execute successfully, got: exit status: 1

  build script failed, must exit now', /home/leslie/.cargo/registry/src/github.com-1ecc6299db9ec823/autotools-0.2.5/src/lib.rs:715:5
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile `sui v0.25.0 (https://github.com/MystenLabs/sui.git?tag=devnet-0.25.0#5d3ff6b3)`, intermediate artifacts can be found at `/tmp/cargo-installSfhEMl`

System Information

OS: Windows 10 with WSL 2 Ubuntu-20.04
Compiler: terminal

@LALauw I was experiencing the same issue but on Debian GNU/Linux 11 (bullseye) as a Proxmox LXC. Turns out I missed some linux dependencies because I followed the build/install/#perquisites doc. I reinstalled following the build/fullnode#software-requirements doc and it build and run without issue.
Hope this resolves your issue.

@LALauw I was experiencing the same issue but on Debian GNU/Linux 11 (bullseye) as a Proxmox LXC. Turns out I missed some linux dependencies because I followed the build/install/#perquisites doc. I reinstalled following the build/fullnode#software-requirements doc and it build and run without issue.
Hope this resolves your issue.

Worked like a charm thanks!


Docker: fix getting openGL version failed when using cyber_visualizer

Rebase your work on top of latest HEAD.

Rebase your work on top of latest HEAD.

OK， I will recommit this patch


Update version of Slang

@ashwinNV This should be a version of Slang that can handle the Hull Shader you showed me.

Closing since PR is for wrong branch.


add * wildcard to synchronize all tables in database

I'm golang newbie
so my code isn't good

Thanks @perfectacle
Can you add some tests and add the doc for this feature?

hey I'm golang newbie, and newbie developer...
so make test code is hard to me...
I don't know how can I make integration test code... sorry...

PTAL @EagleChen

@siddontang I have a some questions about test code...
I'm tried to make test code,
but I can't test... because I typed below command,
go test ./river/river_test.go

but error message is comming
# command-line-arguments
./river_test.go:25:5: undefined: River
FAIL    command-line-arguments [build failed]

How can I fix it...?
and I want to test if it is the same string...
so I use Assert in ./vendor/github.com/pingcap/check/helpers.go
but second parmeter(checker) provides IsTrue, IsFalse, IsNil...
how can I test about string...?
plz help me...!

you can run make test directly.

@siddontang hey, finally I made test code, plz check it!

@siddontang hey... I separated the test code... plz check it haha

@siddontang I use anonymous struct, plz chk it~

I replaced line break to comma, is it right?


When exiting the game, character data is not being saved

Description
When exiting the game, character data is not being saved.
This could be either server side code issue or most likely a stored procedure.
To Reproduce

Create character
Level up
Exit the game
Login back

You'll start over.
Tasks

[ ] Fix character saving issue when exiting the game

@xGuTeK already have it fixed and this is currently pending for a PR.

@stevewgr @xGuTeK  Which PR is this?

@stevewgr @xGuTeK Which PR is this?

There was no PR unfortunately. @xGuTeK mentioned to me back then in regards to some of the tickets that he had fixed some of them, but these were local changes that he never pushed remotely. Feel free to take over if you see similar comments.

I unassigned him from the other tickets as well just to avoid confusion.

@stevewgr Would assign this one to @selcukcukur. He has done some work here #200 and I assume he will open new PRs to address this issue.

You can find the fix for the issue here. #201

This ticket was solved part of this ticket: https://github.com/ko4life-net/ko/issues/94


how to set username/password?

The socks5 client does not support authentication . Socks5 transmission is plain data, It's recommended to use locally.

so what is this? https://github.com/heiher/hev-socks5-server/blob/a517ee48725cad8eb133b33287c2ad875fbebebf/conf/main.yml#L11
if I set username/password in hev-socks5-server, client means this repo (hev-socks5-tunnel) didn't work?
and yes I use tls + http2 to stream data as something like you implement in android (hev-htproxy).

so what is this? https://github.com/heiher/hev-socks5-server/blob/a517ee48725cad8eb133b33287c2ad875fbebebf/conf/main.yml#L11
if I set username/password in hev-socks5-server, client means this repo (hev-socks5-tunnel) didn't work?

Yes. Only the socks5 server supports authentication. :smiley:

and yes I use tls + http2 to stream data as something like you implement in android (hev-htproxy).

You'd better implement encryption and authentication at the transport layer.

if possible implement username/password authentication for clients too, I think that will be useful...
using something like https://github.com/erebe/wstunnel is a good idea?

Could you please verify https://github.com/heiher/hev-socks5-tunnel/commit/935a4006524134aed5e3a4d292f3c3c2a6ff753d ?
Thanks


[iOS] [Linking] Linking.getInitialURL() doesn't work for universal links

When an iOS RN app is launched by clicking an universal link, there is no way to retrieve the url from JS land. Linking.getInitialURL() works only for custom URL schemes and Linking.addEventListener() doesn't work for the initial launch.

Correct. The custom URL scheme API and Universal Links API use very different entry points. We'd need to support Handoff in our AppDelegate (https://developer.apple.com/library/ios/documentation/General/Conceptual/AppSearch/UniversalLinks.html), but abstracting away that difference in Linking would be great.

@javache I have tried to update launchOptions on rootView.bridge from AppDelegate. However, launchOptions turns out to be a readonly property.
Simple solution could be to change launchOptions property to read/write. Do you think that's a possible approach?

Actually, it looks like someone already added support for Universal Links in https://github.com/facebook/react-native/commit/f4c286f7ac0665edc3027e952d3b445703918c9c. Could you see if that works for you?

The commit you referred adds a support for Linking.addEventListener for Universal Links. The problem is that when the app being launched from Universal Link and "application:continueUserActivity:restorationHandler:" is being called, javascript land is not yet loaded and the call gets ignored. (Linking.addEventListener() has not been executed by then.)
That's why there is "Linking.getInitialURL()". When the app is being launched, it needs to check whether the app is being launched by url link and process it accordingly. However, Linking.getInitialURL() depends on launchOptions which only supports custom URL schemes.

I think this will always be a race-condition of some sort, so mutating _launchOptions is not going to help. Would it be possible to guarantee the internal event listener in Linking is setup before the event is dispatched? Inside that JS module, we could also store it until listeners are registered?

Would it be possible to guarantee the internal event listener in Linking is setup before the event is dispatched?

I don't think so. Event dispatch happens in AppDelegate and I would think it happens as soon as the app is launched. Event listener is set up in "Linking/Linking.js". I presume that since Javascript code is executed asynchronously, there is no way that the event listener is set up before the event is dispatched.

Inside that JS module, we could also store it until listeners are registered?

"RCTLinkingManager.application:continueUserActivity:restorationHandler:" uses "NSNotificationCenter". However, it seems that message delivery in NSNotificationCenter happens synchronously. Do you think it is possible to use some sort of queue so that message delivery can hold if no listener for such messages is registered?

I looked into launchOptions in AppDelegate and realized that URL parameter for Universal Links is available under different key than custom URL scheme. I made a change to Linking.getInitialURL() so that it works for both custom URL scheme and Universal Links. Could you review it if I make a PR?

Sure, go for it.


Add versioning requirement with operation and constraint matching

This PR adds a new struct VersioningReq, an analogue to VersionReq from semver but using Versionings instead. This makes it easier to use Versioning when interpreting dependency version requirements for non-Rust languages and frameworks.
This PR is fairly complete, it includes documentation, tests, doctests, etc. Happy to discuss/change anything if needed.

Above changes resolve all the comments, thanks for the suggestions! I also fixed a mistake that allowed == instead of just =, and removed the permissive "if there is no op, treat it as =" behavior because I think it's likely to cause confusion.

Thanks, I'm tweaking a few things and then will merge.

Take a look at what I altered. I'd like your input about the naming of the Requirement type. It could also potentially be called Constraint.

Looks great, I'm also in favor of Requirement as the name. Changes to make the parse functions consistent are nice too!

Great, then I'll merge this tomorrow morning and release.

Released 6.1.0.


🐛 [BUG] - Play window extends beyond screen

Discord Username
No response
Description
The play window extends beyond bottom of the screen. The bottom right corner (see screenshot) is not visible so the play window cannot be resized. The text typed in the game is also below the fold and not visible.
Possibly related: I played the game on a Windows computer in Chrome with a larger resolution immediately before this issue began to occur on my primary computer, a MacBook Air/Chrome. I have also played on my primary computer connected to an external monitor with a different resolution.
Is there any way to reset the state of all windows so that everything fits within the bounds of the screen?
I have tried clearing storage of base assets.
Reproduction steps

Log in and note that the play window extends beyond the top and bottom of the screen.

Screenshots

Logs or Error messages
No response
Browsers
Chrome
OS
Mac

Same issue as #136. This comment helped resolve my issue https://github.com/ClassicUO/classicuo-web/issues/136#issuecomment-2421373260:

You can temporarily zoom out the page using Chrome to then resize the game window.

At the top right, click the settings menu image
Next to zoom click the - a few times to zoom out or until you can see the game window is reachable.
Grab the corner of the game window, resize it to be much smaller
Go back to the settings menu, reset the zoom


Update torchserve docs

What this PR does / why we need it:
Update torchserve docs
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

/assign @jagadeeshi2i


DispersionEntropy should be a ProbabilitiesEstimator

Currently, only the convenience method dispersion_entropy is provided. However, DispersionEntropy is a proper ProbabilitiesEstimator and should follow the main API.
This should be fixed asap so that the current API is obeyed, since dispersion entropy was released in v1.2 (tagged).

Haha, the good thing is that the documentation defines the public API and if this is nowhere documented then its not breaking if you change it hahaha


Does the creation failure mean that the vulnerability does not exist in the system?

Does the creation failure mean that the vulnerability does not exist in the system? I am very confused about this question, I hope someone can answer it, thank you very much！

Hello. Yes, that means the exploit failed :)