All Issues
24,993 verified issues
[BUG]: Broken shifted columns with leftJoin and same column name (on D1)
What version of `drizzle-orm` are you using? 0.25.4 What version of `drizzle-kit` are you using? 0.17.6 Describe the Bug I got broken results with leftJoin with same columns. Details My schema (partial) [code block] ... and run next query to reduce has many pattern. [code block] I got broken results. [code block] - id is swapped. - post data is shifted. Running query is here. [code block] I think that duplicate id columns have been executed without `as`, causing the ORM to be misaligned when it repackages them into the object. If one id is not referenced, this bug is resolved. Expected behavior I expect I can use both id and correct columns. [code block] Environment & setup I'm using pnpm. [code block] D1 setup [code block]
client-side disconnect is not detected
[code block] The alert shows up if I take down the Node server, but not if I turn off my wireless, or close my laptop and re-open it later. The connection is lost though. Is there a better way to detect disconnect on the client side? This is with the WebSockets transport.
Build error next.js 6.0.0
I just upgraded to `next@6.0.0`, I use a custom server, when I try to `run dev`, I get an error. [code block] > UPDATE all this passed after upgrading all babel packages to v7 Now this is the new error.... See below for complete error message [code block]
Environment variables not updating in new lambda function version
This is a Bug Report Description For bug reports: What went wrong? New environment variables are not deploying to new function version for AWS Lambda. I've verified that the new variables are properly set inside the CloudFormation stack template. I've also ran every variation of deploy (with `-p`, with `-f`, with `--force`, with `--update-config`, and with code changes). My base use case is to `sls package` first, then deploy with `-p` What did you expect should have happened? Changing or adding environment variables in serverless.yml should update environment variables in lambda console for the corresponding function version when deployed. What was the config you used? [code block] What stacktrace or error message from your provider did you see? No error message. Package and Deploy were successful. Similar or dependent issues: https://github.com/HyperBrain/serverless-aws-alias/issues/91 Additional Data Serverless Framework Version you're using: 1.25.0 Operating System: Mac High Sierra locally and Ubuntu in CircleCI Stack Trace: None Provider Error messages*: None
Feedback for “Quering with SQL-like syntax [CRUD]”
OnConflict and Upsert [insert or update] section: It does not appear that the .onConflictDoNothing and .onConflictDoUpdate functionality exists for all db types. specifically I am using the PlanetScaleDatabase and they do not exist. Might want to update the documentation to inform people that it is not universal functionality.
An official Docker Image with the AWS CLI for use in CI/CD scenarios
I read Issue #3529 and #3291 and saw those were closed, with the only reaction hinting it was 'not that complicated'. However, the comment also acknowledged that doing this yourself would run the risk of being out of date. Apart from exactly that point, I would also like to point out that, for commercial users, having an official Amazon image is hugely preferential to "/aws-cli:latest". In my case, I would be using this in a Google Cloud Build because it is far superior than AWS CodeBuild.
S3 Remote State and Credentials in non-default profiles
Terraform Version 0.9.2 Affected Resource(s) terraform s3 remote state backend Terraform Configuration Files ~/.aws/credentials - This would be the entire file, no other entries [code block] MAIN.TF [code block] Debug Output NA Panic Output NA Expected Behavior What should have happened? The expectation is that I should be able to use a non-default profile credential to complete the backend init (`terraform init`) call. Actual Behavior What actually happened? command fails with the following error: [code block] if i simply move the same credentials under the default profile in the standard shared credentials file it works without issue. Steps to Reproduce `terraform init` Important Factoids none References not that i was able to find for 0.9.2
AsyncStorage.getItem() doesn't seem to work
When I try to set a value via `AsyncStorage.getItem()`, I cannot request it back. Environment Environment: OS: macOS High Sierra 10.13.3 Node: 9.8.0 Yarn: 1.5.1 npm: 5.6.0 Watchman: 4.9.0 Xcode: Xcode 9.2 Build version 9C40b Android Studio: Not Found Packages: (wanted => installed) react: ^16.3.0-alpha.1 => 16.3.0-alpha.1 react-native: 0.54.0 => 0.54.0 Expected Behavior await AsyncStorage.setItem('foo', 'bar'); await AsyncStorage.getItem('foo').then(console.log); // 'bar' await AsyncStorage.getAllKeys().then(console.log); // ['foo'] Actual Behavior await AsyncStorage.setItem('foo', 'bar'); await AsyncStorage.getItem('foo').then(console.log); // null await AsyncStorage.getAllKeys().then(console.log); // [] Steps to Reproduce import { AsyncStorage } from 'react-native'; it('should be able to request a value after it was set', async () => { await AsyncStorage.setItem('foo', 'bar'); const output = await AsyncStorage.getItem('foo'); expect(output).toBe('bar'); }); it('should be able to see a new key after a value was set', async () => { await AsyncStorage.setItem('foo', 'bar'); const output = await AsyncStorage.getAllKeys(); expect(output).toContain('foo'); });
[Feature] Strongly Typed Event Type for Stripe.Event
Not too important, but it would be nice if this type: https://github.com/stripe/stripe-node/blob/02da7dc2c5edae280aaf5e3566f3b7b383024371/types/2020-03-02/Events.d.ts#L52 is strongly typed with all possible events. This would help catch bugs within switch statements or other logic statements, while also providing a nice menu of events within your IDE. If you are open to it, I don't mind making a quick script to take the webhook dropdown and convert it to a type definition for this variable in a PR.
Error when trying to run docker-compose up. "oci runtime error: container_linux.go:247..."
When trying to launch a built container with `docker-compose up` I'm getting an error: [code block] I've tried reinstalling docker, docker-compose, virtualbox, rebuilding containers, recreating machines. Downgrading almost all of those things to previous versions. Literally retrying the whole docker instalation flow. The problem occurs only in `docker-compose up`. Everything works fine when I use `docker run ...`. The important thing is the whole setup works correctly on my OSX installation. Unfortunately my Xenial Ubuntu doesn't want to cooperate. I've checked the issues archive and couldn't find an answer that would help me fix the problem. Here are my whole setup configs: `docker-compose.yml`: [code block] `Dockerfile` [code block] `script/docker-entrypoint.sh` [code block] `docker-compose -v`: `docker-compose version 1.8.1, build 878cff1` `docker version`: [code block] `docker info`: [code block]
Error: Connection was closed before we received a valid response from endpoint URL
I am receiving the above error when trying to upload my code to Lambda using the cli: [code block] This was working fine a couple of days ago, but today it just keeps failing. Here is a piece of the debug logs, where the error is thrown: [code block] It retries a few times but continually fails. It finally fails with the following error: [code block] What is the problem?
HTTP/2 support
Is there any plan to add HTTP/2 support for node.js? Since it is now officially supported in node.js 9, I think it's highly desirable to have this library support it as well.
feature: add a GitHub action to quell spam PRs
Problem I was scrolling through Twitter and someone posted about the spam PR. Possible Solution Implement this GitHub action. It'll lessen the workload for maintainers.
Docs page for how to fix deprecation warnings
After #6917 it should now be possible to clear up all deprecation warnings by: Replacing `update()` with `updateOne()`, `updateMany()`, or `replaceOne()` Replacing `remove()` with `deleteOne()` or `deleteMany()` Setting `mongoose.set('useFindAndModify', false);` Setting `mongoose.set('useCreateIndex', true);` * Setting `mongoose.set('useNewUrlParser', true);` Need a docs page to summarize this.
Inconsistent weight and use of color in iconography throughout UI
See images below of the various different icons across the UI at x2 with some comments. This is by no means exhaustive but contains the major icons: /cc @bpasero General comments - Since color is used so sparingly throughout the UI, it draws additional attention to the icons that feature red and green in particular. Clear output should have not have a particularly strong visual presence imo. Explorer - Why is the folder filled in brown and not white? - Why does the collapse all button feature a blue `-`, why is it a different blue than the one used in the status bar? Search - Why is the red `x` an inconsistent style with the `x` used elsewhere? - Why does the clear icon feature a different light gray than the other icons? - Why is there a dark border around these icons in particular? Git - Why is the tick icon a different weight, why isn't it solid? Debug - Why is the debug output icon so short? - Why is the deactivate breakpoints button feature a circle filled with black (vs transparent used elsewhere) - Why is the close all button filled so it's inconsistent with the collapse all? - Why does the close all button button have a black border when collapse all doesn't? Problems Editor
Git: Support WSL
Git: Support WSL
Interest in DiskANN
Hi, at Neon we've been investigating DiskANN, and we believe it would have several advantages compared to HNSW. Last month I prototyped a freestanding DiskANN implementation (not inside Postgres, and not the official DiskANN implementation), and seemed to get very good performance for building the index in parallel compared to libhnsw. Timescale recently published their own DiskANN implementation which (at least according to them) outperforms pgvector's HNSW. DiskANN also has an extension called FreshDiskANN which cleanly supports inserts and deletes. I was wondering if there was any interest in adding DiskANN to pgvector. If so, I'd like to begin working on it!
1.5 - Make COMPOSE_PROJECT_NAME accessible to environment
Given that: - containers join the network under their container name - at least for now - container names depends on the project name I think we need a quick basic solution for 1.5 to allow docker-compose with `--x-networking` enabled to work on a project independently from the project name. The reasoning: project names are variable (they can be different for two users depending on their directory, or can be changed in the CLI). So without forcing the project name, when we up a project, we have no way yet to predict the network name - and worse, no way to predict the hostnames of the other containers in the project. Proposed solution I understand that nice solutions are planned for 1.6, but in the mean time I think we need a solution doable for 1.5. I suggest to set and make the environment variable `COMPOSE_PROJECT_NAME` available. This way we can actually predict at which hostname other containers will be accessible in the current network. Something like `${COMPOSE_PROJECT_NAME}_redis_1`. Example What you do now [code block] [code block] Proposal The proposal is to make that possible: [code block] [code block]
more than one library with package name 'com.google.android.gms.license'
- [ ] I have reviewed the documentation - [ ] I have searched existing issues - [ ] I am using the latest React Native version Environment OS: macOS Sierra 10.12.6 Node: 6.10.2 Yarn: 1.3.2 npm: 3.10.10 Watchman: 4.9.0 Xcode: Not Found Android Studio: 3.0 AI-171.4443003 Packages: (wanted => installed) react: 16.2.0 => 16.2.0 react-native: 0.53.3 => 0.53.3 Steps to Reproduce Expected Behavior Actual Behavior
[BUG] Missing required argument #1
npm ERR! typeerror Error: Missing required argument #1 npm ERR! typeerror at andLogAndFinish (/usr/share/npm/lib/fetch-package-metadata.js:31:3) npm ERR! typeerror at fetchPackageMetadata (/usr/share/npm/lib/fetch-package-metadata.js:51:22) npm ERR! typeerror at resolveWithNewModule (/usr/share/npm/lib/install/deps.js:456:12) npm ERR! typeerror at /usr/share/npm/lib/install/deps.js:457:7 npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50 npm ERR! typeerror at /usr/share/npm/lib/fetch-package-metadata.js:37:12 npm ERR! typeerror at addRequestedAndFinish (/usr/share/npm/lib/fetch-package-metadata.js:82:5) npm ERR! typeerror at returnAndAddMetadata (/usr/share/npm/lib/fetch-package-metadata.js:117:7) npm ERR! typeerror at pickVersionFromRegistryDocument (/usr/share/npm/lib/fetch-package-metadata.js:134:20) npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50 npm ERR! typeerror This is an error with npm itself. Please report this error at: npm ERR! typeerror <http://github.com/npm/npm/issues> npm-debug.log