All Issues
24,993 verified issues
Preview feature feedback: Integrated seeding
Please share your feedback about the integrated seeding functionality that was released in v2.15.0 in this issue. - If you encounter a bug, please open a bug report in this repo. - If the feature is working well for you, please share this in a comment below or leave a 👍 on this issue. If you have any questions, don't hesitate to ask them in the `#prisma-migrate` channel in the Prisma Slack.
[BUG]: `SyntaxError: Cannot use import statement outside a module` with drizzle-kit
What version of `drizzle-orm` are you using? ^0.27.0 What version of `drizzle-kit` are you using? ^0.19.2 Describe the Bug I have the following syntax error when trying to use drizzle-kit: [code block] Expected behavior _No response_ Environment & setup - pnpm - monorepo - Mac OS [code block] [code block]
self hosted runner is not accepting jobs from queue.
Describe the bug Self hosted idle runner is not consuming queued jobs (runner version 263, release version). To Reproduce Steps to reproduce the behavior: 1. Assume you have a runner in the state offline (self-hosted) 2. New action workflow is triggered 3. Create a new runner (config and run). We scale them automatically 4. New runner is not consuming the queued jobs. This was working perfectly for a few months, but got recently broeken. 5. It got a bit more strange, trigger a new workflow. The runner wil see this jobs, start an upgrade to the prereleas, see #581 . And jobs stars, Queued jobs remains stucks today (2020-07-15 between 12 and 18 CET). Now around 20:30 CET the queued jobs are consumed as well. But all still strange since it is the event of the second trigger that cause the update of a non released version. Should 267 not be released? Expected behavior Runner in the idle status should consume jobs (labels are matching). Runner Version and Platform GitHub cloud + runner version 263 OS of the machine running the runner? OSX/Windows/Linux/... What's not working? No error message, see behaviror above. Job Log Output If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here. Runner and Worker's Diagnostic Logs n/a reference: our setup is available here: https://github.com/philips-labs/terraform-aws-github-runner
Uncaught (in promise) TypeError: Cannot read property 'protocol' of undefined
Hi! I'm trying to use your library but I get an error: [code block] I was using your example [code block] The error happens here. I'm using browserify and chrome 45.
trailing slash in link for legit page works for client side navigation but leads to not found bundle and 404 on hard refresh (ssr)
trailing slash in link for legit page works for client side navigation but leads to not found bundle and 404 on hard refresh (ssr) Bug report Describe the bug let me know if title needs further clarification. all relevant issues has been closed with reasoning that its been fixed in 6-canary (I believe it is not) or by improved serve (which is true only in perhaps production static export). I'm rewriting my existing blog to next.js and i previously used trailing slashes. Latest `serve` can help with it once i build my next.js powered blog. But in order to fix dev env i need either to get rid of trailing slashes and utilize `301 Moved Permanently` in prod; or live with broken trailing slash support in dev. To Reproduce Here is minimal reproducible case (link to repro repo is below snippet): [code block] Minimal reproducible repo https://github.com/iamstarkov/next.js-trailing-slash-bug-demo 1. clone repo `git clone https://github.com/iamstarkov/next.js-trailing-slash-bug-demo` 1. change directory `cd next.js-trailing-slash-bug-demo` 1. install deps `yarn` 1. run dev: `yarn dev` 1. open http://localhost:3000/ 1. open devtools' network tab 1. observe `http://localhost:3000/_next/static/development/pages/about.js` being 200ed 1. observe `http://localhost:3000/_next/on-demand-entries-ping?page=/about/` being 200ed 1. observe `http://localhost:3000/about/` being 404ed 1. observe persistent attempts to resolve `http://localhost:3000/about/` 1. observe in the terminal `Clien
GitHub Actions 403 "Resource not accessible by integration" on PR comment
GitHub Actions workflows that post comments on pull requests, create releases, or write to packages fail with '403: Resource not accessible by integration'. This started when GitHub changed the default GITHUB_TOKEN permissions to read-only for all scopes. Workflows that relied on implicit write access must now explicitly declare the permissions they need.
Add ability to opt out of agent auto-update
Describe the enhancement Running the agent within docker and having it auto update causes the container to throttle and never succeed without having to manage PID 1 It would be nice to have something in `config.sh` or `run.sh`, possibly environment variables to help opt out of auto-update Code Snippet n/a Additional information n/a
tailwindcss v3.0.5 is not picking up changes unless I change tailwind.config.js file
What version of Tailwind CSS are you using? v3.0.5 What build tool (or framework if it abstracts the build tool) are you using? "postcss": "^8.4.5" What version of Node.js are you using? v16.6.2 What browser are you using? Chrome What operating system are you using? macOS Reproduction URL [code block] Describe your issue Sometimes tailwind is not adding classes to final CSS when I'm adding them to my HTML files unless I edit the `tailwind.config.js` file, I usually comment and uncomment some line in that file and all of sudden I see the class has been added to the CSS file, I had this very same issue on my Next.js project as well. I made a new reproduction repository and tested things there, it was all good and working. Not really sure why it's not working on my own projects at some point. This may sound stupid but maybe tailwind is not picking up changes as the project get's more complicated? I made this issue to know if anyone had some similar experience or not, so maybe someone can guide me on how to resolve this. But if I change to the old version tailwindcss 2.2.19, there will be no problem [code block]
[Question] Is it possible to include Nth-level relationship data using find options?
If I have a Person entity with a one-to-many relationship with a Home entity, and then the Home entity has a many-to-one relationship with a HomeType entity, is there a way to get the Home entities to include their HomeType data when selecting Person's and including their Home relations? `let personsWithHomes = await Person.find({ where: { id: id }, relations: ["homes"] })` This would return my Person records with their associated Home records, but the Home records do not include their associated HomeType. I tried adding the type as an eager loaded relationship, but it still does not get included. Is there a way to specify the sub relations to include? `let personsWithHomes = await Person.find({ where: { id: id }, relations: ["homes", "homes.homeType"] })`
Implement multi-select in left-panel file tree
It would be good to be able to move/copy/delete/etc. multiple files in the tree view at once using combinations such as: Mouse - <kbd>shift</kbd>+`left click`: Select all items from the currently focused item to the clicked item - <kbd>ctrl</kbd>+`left click`: Add the clicked item to the selection Keyboard - <kbd>shift</kbd>+<kbd>↑</kbd>: Add the item above the focused item to the selection (or reduce the selection) - <kbd>shift</kbd>+<kbd>↓</kbd>: Add the item below the focused item to the selection (or reduce the selection) - <kbd>ctrl</kbd>+<kbd>↑</kbd>: Move the focus up without selecting the item - <kbd>ctrl</kbd>+<kbd>↓</kbd>: Move the focus down without selecting the item - <kbd>ctrl</kbd>+<kbd>space</kbd>: Add/remove the focused item from the selection
capture output of provisioners into variables
so that they could be referenced in other TF resources
Content-Type application/x-www-form-urlencoded
Try to send request with content type application/x-www-form-urlencoded [code block] but there is no such header in request. I tried to use code: [code block] same problem jquery code works fine: [code block] How can I use axios to send request with this header?
Support for Lambda@Edge
This is a (Feature Proposal) Description For feature proposals: What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us. https://aws.amazon.com/blogs/aws/lambdaedge-intelligent-processing-of-http-requests-at-the-edge/ Today, Lambda@Edge has been GA released. When CloudFormation will support for this, would be great that implement this as a new event source. If there is additional config how would it look So I think it would be something like this: [code block]
Serverless using AWS profiles only half working
This is a Bug Report Description When using the `serverless deploy --aws-profile` or using the `EXPORT AWS_PROFILE=<profile>; serverless deploy` or the `AWS_PROFILE=<profile> serverless deploy` it only reads from the credentials file, but that should also be reading from the config file like the default `aws cli` tools does. For example I have the following two files [code block] If I run `serverless deploy --profile dev` it will fail with [code block] Then I tried `AWS_PROFILE=dev serverless deploy` and it failed with the above error And finally I ran `export AWS_PROFILE="dev" && export AWS_REGION=us-east-1` and then ran the `serverless deploy` and the same error occur. So reading more in depth the above small link and talking to people on Gitter I moved that dev profile to `~/.aws/config`, creating new keys since the previous used a cross account mfa role. Its my experience using Troposphere and tools that rely on AWS Profiles, they should be looking into all of them and if they have an mfa, request the code about it. Additional Data Serverless Framework Version you're using: 1.15.3 Operating System: Mac OS 10.12.5 Stack Trace*: Shown above Workaround Create an additional profile and store it inside the ~/.aws/config to use and then you can refer to it using --profile <profile>
[BUG] Error installing relative paths using workspaces
EDIT See https://github.com/npm/cli/issues/3847#issuecomment-1219533329 for minimum reproduction case. --@wraithgar ------- Is there an existing issue for this? - [X] I have searched the existing issues Current Behavior Running `npm install --workspace=<workspace>` is resulting in npm exiting with an errorcode and the following stack trace: [code block] Dockerfile for container I'm running the command in: [code block] node_modules seem to successfully install but npm exits with an error code Expected Behavior npm install completes without raising an error Steps To Reproduce 1. Setup an npm project with workspaces 2. Create a docker container according to the above specifications, with one of the commands attempting to run npm install for a specific workspace 2. Attempt to build the container 4. npm installs node_modules successfully but exits with error Environment - OS: Debian GNU/Linux 9 (stretch) - Node: 14.16.1 - npm: 7.24.2
[FEATURE]: Merge multiple calls to `where` when in dynamic mode
Describe what you want It would be great if multiple calls to the `where` method could be merged with an `and` when the query was in dynamic mode. This would be fantastic for scenarios where you want to apply filtering in a centralised way, like using access filters. e.g. [code block] Would be equivalent to: [code block] I think the implementation would be: 1. Tracking when a query is in dynamic mode, and 2. When `where` is called, check if there is already a `where` in the config and in dynamic mode, then wrap current `where` in `and` with the new `where` clause. e.g. in `PgSelectQueryBuilderBase` [code block]
[BUG]: drizzle-kit push is not detecting Postgres enum label already exists
What version of `drizzle-orm` are you using? 0.30.9 What version of `drizzle-kit` are you using? 0.21.2 Describe the Bug This bug happens every so often. Is there a work around? pnpm drizzle-kit push drizzle-kit: v0.21.2 drizzle-orm: v0.30.9 No config path provided, using default path Using 'pg' driver for database querying Warning You are about to execute current statements: ALTER TYPE "job_name" ADD VALUE 'SET_PCS_POWER_KW'; error: enum label "SET_PCS_POWER_KW" already exists kit@0.21.2/node_modules/drizzle-kit/bin.cjs:113632:7) { length: 102, severity: 'ERROR', code: '42710', detail: undefined, hint: undefined, position: undefined, internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, column: undefined, dataType: undefined, constraint: undefined, file: 'pg_enum.c', line: '293', routine: 'AddEnumLabel' } Expected behavior _No response_ Environment & setup _No response_
New rule: destructuring-property-newline
Please describe what the rule should do: It would function almost exactly like object-property-newline except on destructured variables. Much of the below is an adaptation of that rule. It destructure lots of variables at once like so: const { foo, bar, baz, abc, xyz, foobar, foobaz, bazfoo, barfoo, abcxyz, xyzabc, foobarbaz, bazbarfoo } = foobarbazabcxyz; the line length can get pretty long. Readability decreases. I think it could be useful if there was a rule that detected the amount of characters in a line or the amount of variables being destructured. If that number happens to be too large (not sure what the right number here is), throw a warning/error suggesting a multiline destructuring like so: [code block] Is this rule preventing an error or is it stylistic? What category of rule is this? (place an "X" next to just one item) [x] Enforces code style [ ] Warns about a potential error [ ] Suggests an alternate way of doing something [ ] Other (please specify:) Provide 2-3 code examples that this rule will warn about: Examples of incorrect code for this rule: [code block] Examples of correct code for this rule: [code block] Options This rule has an object option: * `"allowMultiplePropertiesPerLine"`: `true` allows all keys and values to be on the same line allowMultiplePropertiesPerLine Examples of additional correct code for this rule with the `{ "allowMultiplePropertiesPerLine": true }` option: [code block] Why should this rule be included in ESLint (inste
How to implement shouldComponentUpdate with this.context?
I know `this.context` is not officially there but quite a few libraries rely on it, and it seems like it's getting into shape with #2509. I'm trying to understand how exactly `shouldComponentUpdate` is supposed to be implemented with `context` in mind. I noticed it accepts a third argument (`nextContext`) and I can extend `PureRenderMixin` to also check it: [code block] Components that don't opt into `this.context` by not omitting `contextTypes` will not get this third argument, which is understandable. However this presents a problem when we have a `<Middle />` component in between between `<Top />` context owner and `<Bottom />` context consumer. If `<Middle />` implements a restrictive `shouldComponentUpdate`, there is no way for `<Bottom />` to react to `<Top />`'s context updates at all: (fiddle) [code block] The same problem would occur if I tried to give `Middle` a generic context-aware `shouldComponentUpdate` as I wrote above, because `Middle` has no `this.context` unless it opts in. This is possible to work around by adding `contextTypes` to `Middle`, but it doesn't look like a good solution. You'd need to explicitly add necessary `contextTypes` on every level with smart `shouldComponentUpdate` so it's too easy to slip up. Will this be solved by #2112? Is there another solution in the meantime? What is the recommended way?
SASL_SIGNATURE_MISMATCH: The server did not return the correct signature
Bug report - [ ] I confirm this is a bug with Supabase, not with my own application. - [x] I confirm I have searched the Docs, GitHub Discussions, and Discord. Describe the bug I recently switched from a local postgres database to supabase and using drizzle as the ORM. This is the drizzle configuration (the app is a discord bot, so long-running) [code block] EDIT: All these throw a connection error, whether it is `pg` or `postgres` [code block] On the first request to the database I get the following: [code block] However, if use a connection string with the exact same values (env variables joined in the format of the connection string) the connection works. I'd prefer to use the object notation in the `postgres()` connection options To Reproduce Source code can be found here <https://github.com/noook/discord-mbti> Expected behavior Object notation should behave the same as the connection string Screenshots Database connection on supabase dashboard <img width="893" alt="image" src="https://github.com/supabase/supabase/assets/19751938/bb29b5fa-55f6-4e8b-8f2c-197ee4ed7a84"> System information - OS: Linux (docker) - Version of supabase-js: not used - bun 1.0.29 Additional context -