All Issues
24,993 verified issues
Graphql support for sort and filter functionalities
Graphql provides an excellent standard for queries and mutations.Is there any support for sorting and filtering(multiple fields) for Graphql queries.If not is there any way to achieve with Graphql + mongoose schema.
General JSX Improvements
Remaining - [ ] Expand last argument of arrow function [code block] Right now turns to [code block] - [ ] Wrong indent for arrow functions inside of `{}` [code block] - [ ] single arrays and objects should stay on the same line and not put on the next indent [code block] should be [code block] and [code block] should be [code block] Fixed - [X] Put parenthesis for bracket-less arrow functions [code block] - [X] Put parenthesis for return [code block] - [X] Puts parenthesis for variable declaration [code block] - [X] Preserve space between text nodes and jsx elements in a single line [code block] - [X] Properly escape quotes [code block] should turn into [code block] - [X] Use double quotes for jsx attributes even with `--single-quote` [code block] - [X] Should print names with `.` correctly [code block] - [X] brackets should be on the same line as the attributes [code block] should be [code block] (Note: the original issue has been replaced with this list of remaining items, so comments below might not make sense)
Self-hosted runners disappeared
Associated GitHub Community topic: https://github.community/t/disappearing-self-hosted-runners/137669 The customer has added some self-hosted runners for his repository, but the runners would completely disappear as if he never added any. When he refreshes, the runners would come back. Some would be `Offline` but would go back to being `Idle` after another refresh. Other times when he refreshes the runners disappear again. When the customer logs into the runner machines to check their status, he can see a lot of connection retries. [code block]
onUploadProgress not being called
I am setting up an axios request like so: [code block] data is a FormData object file a file resource, the data gets posted to my server correctly, but onUploadProgress never gets called, even when uploading large files (I only need to use it to upload images, just using large files for testing).
Setting default max-width and height for img tag
Pull request #426 sets height to auto in combination with a default value of max-width to 100% to the `img` tag. This gives unexpected results. See Codepen. Loading a 100x200px image fills up the whole space although I am setting width and height specifically. @adevade mentioned code from Bootsrap, but this is meant for a fluid image with class name `image-fluid`. I took a look at the source code of BeardCSS. BeardCSS is setting only a max-width of 100%, if width or height attributes are set they will be respected by resetting max-width to none on the `img` tag. I think we should take the BeardCSS approach. Example of same code as above with the BeardCSS approach gives the expected result.
[BUG] npm ERR! Exit handler never called!
Is there an existing issue for this? - [X] I have searched the existing issues Current Behavior Trying to download this tool https://github.com/CesiumGS/gltf-pipeline, I run the command `npm install -g gltf-pipeline` and I get [code block] The log is [code block] Expected Behavior Download the tool Steps To Reproduce 1. In this environment... 2. With this config... 3. Run '...' 4. See error... Environment - OS: Windows 10 - Node: 14.15.4 - npm: 7.20.1
Supabase auth (google) not working properly
Bug report Describe the bug I've implement the supabase auth with google provider in a create-react-app enviroment. Now when i go through the signin process it redirects me to localhost with token instade of signin me in. To Reproduce Steps to reproduce the behavior, please provide code snippets or a repository: Bootstrap CRA and implement supabase auth Expected behavior A clear and concise description of what you expected to happen. Screenshots <img width="830" alt="Screenshot 2023-07-20 at 8 46 37 PM" src="https://github.com/supabase/supabase/assets/33357137/2e07a0dd-55bd-4946-810f-5a4f4c5ff808"> Initial Page <img width="837" alt="Screenshot 2023-07-20 at 8 47 02 PM" src="https://github.com/supabase/supabase/assets/33357137/d19044d2-491e-44dd-a0a1-ad315af588f2"> This is after is signed in with, it just sent me session information in url hast. But doesn't actually log me in. <img width="759" alt="Screenshot 2023-07-20 at 8 40 17 PM" src="https://github.com/supabase/supabase/assets/33357137/3da7ffbf-7d2f-40ff-a8e8-71b086c4a856"> I'm trying to get the user session but it doesn't returns anything. If applicable, add screenshots to help explain your problem. System information - OS: masOs - Browser chrome - Version of supabase-js: 2.26.0 - Version of Node.js: v20.3.1 One thing i've tried the same with Nextjs it worked fine. I'm not sure what is the issue here.
Route 53 alias record silently points to wrong Elastic Beanstalk environment
A production domain (prod.example.com) in Route 53 has an alias record that was accidentally pointed to the dev Elastic Beanstalk environment instead of the production one. Both environments share the same codebase so the bug is invisible until you notice the dev database is being used in production. Route 53 alias targets are not validated — the console accepts any valid EB endpoint without warning.
pgvector cosine similarity returns irrelevant results for short search queries
Semantic search using pgvector returns irrelevant results when the query is 1–3 words. Short queries produce low-quality embeddings because the model has insufficient context to encode a meaningful semantic direction. A query like 'login error' returns documents about unrelated errors. Hybrid search combining vector similarity with keyword matching (pg_trgm or full-text search) with Reciprocal Rank Fusion significantly improves short query results.
add outer padding to rule padded-blocks and cover existing jscs functionality
Update: please refer to this pull request for the current status of this issue: https://github.com/eslint/eslint/pull/8099 1st proposal: updating padded-blocks [code block] The above doesn't yet include additional options for backwards compatibility. related issues: - https://github.com/eslint/eslint/issues/3092 - https://github.com/eslint/eslint/issues/5982 - https://github.com/eslint/eslint/issues/5949 related / converging rules: - http://jscs.info/rule/requirePaddingNewLinesAfterBlocks.html - http://eslint.org/docs/rules/padded-blocks - I think jscs has another rule for padding before blocks? ~~2nd proposal~~ ~~no modifications to `padded-blocks`. new rule that has exceptions to allow `padded-blocks` to work, if there is a conflict an error is thrown (is this even a thing?)~~ [code block] ~~`"afterOpeningBlock"` and `"beforeEndingBlock"` specify whether the rule should apply to a block placed at the beginning or end of the inside of another block. If they are both specified, then `padded-blocks` should work as expected. If they are not specified, then the new rule could potentially result in an error depending how `padded-blocks` is configured.~~
Support response/request templates for APIG in v1
APIG Response/Request templates options are now missing in V1, we need to bring back this functionality. In v0.5.6 we let users define their velocity templates as strings in the `s-function.json` json file, which was very hard to maintain. We can still do that in v1 using our `serverless.yaml` file, but it'd still be really hard to maintain all the templates in all endpoints in all functions in a single file. Someone suggested before that we should let users define their velocity template in a `.vm` file and just reference it in the APIG config object in `serverless.yaml` (or `s-function.json`). I think this will make it much easier to deal with APIG and will provide super flexibility. Another option is for Serverless to provide an abstraction layer on top of velocity templates so that users don't have to provide velocity templates at all, just some yaml config options that will be compiled into valid velocity templates. This will probably be better UX, but will be much less flexible, and users with specific needs might get stuck. Or maybe we can do something in between. Thoughts...? cc/ @flomotlik @pmuens @ac360 Parent Issue: https://github.com/serverless/serverless/issues/1408
TypeORM Attempts to create tables that already exist
Issue type: [ ] question [x ] bug report [ ] feature request [ ] documentation issue Database system/driver: [ ] `cordova` [ ] `mongodb` [x ] `mssql` [ ] `mysql` / `mariadb` [ ] `oracle` [ ] `postgres` [ ] `sqlite` [ ] `sqljs` [ ] `react-native` [ ] `expo` TypeORM version: [ x] `latest` [ ] `@next` [ ] `0.x.x` (or put your version here) Steps to reproduce or a small repository showing the problem: If I delete all the tables in my database and run my app, all tables are created successfully. If I then stop the app and restart it, typeorm attempts to create tables that already exist and then fails. Here is the output from TypeOrm for the second run: Here is the beginning of the definition for the EmployeeAvailabilities table (there are more columns than this): [code block] At first I thought the issue was because the class name and table name do not match. But if I make the class name and table name match, the issue still occurs.
Very slow queuing with plenty of idle runners available
Originally posted here: https://github.community/t/very-slow-queuing-behavior-when-idle-runners-are-available/127674 Describe the bug When no other builds are running (all my runners are idle), there is very delayed behavior from GH actions before builds even start. This is especially noticeable with, for example, a 4^4 matrix (256 checks), even if you have 256 idle self-hosted runners. The UI shows “X queued checks” at a rate of around 4 per second (ie, “4 queued checks”, “8 queued checks”, etc), before it finally gets to 256 checks queued. It takes a full 1min 40sec before the first of my runners even receives a message and starts building. It takes 12-13min for the entire run to be marked as finished, even if each build does no work and completes in 1sec or less. To Reproduce 1. Register (and run) 256 self-hosted runners 2. Run a workflow that uses a 4^4 matrix: [code block] 3. Observe that it takes a long time before the first build message is sent to a runner 4. Observe how, even after all checks are completed, it still takes many minutes (10?) for the entire workflow to be marked as finished You can also observe similar behavior with fewer checks – eg, even just 16 runners and a 4^2 matrix. Even then, checks are queued before the first build will start – and there's a noticeable delay after the 16th check has finished before the whole workflow is marked as complete. I see an overall run time of 1min10sec – even though each worker has completed its build in less tha
Unable to query for MongoDB ObjectIDs
I recently updated from `0.13.2` to `14.0.2` which includes breaking changes. This introduced errors with existing queries which include MongoDB Object Ids (probably from #1382): > ID cannot represent value: { _bsontype: \"ObjectID\", id: <Buffer 5b 96 3d bf 98 0a 04 09 85 c6 6e a1> } Repository with complete, minimal repeatable example here: [code block]
Add custom select and map to property of entity
Issue type: [ ] question [ ] bug report [X ] feature request [ ] documentation issue Database system/driver: [X] `cordova` [X] `mongodb` [X] `mssql` [X] `mysql` / `mariadb` [X] `oracle` [X] `postgres` [X] `sqlite` [X] `sqljs` [X] `websql` TypeORM version: [ ] `latest` [ ] `@next` [ ] `0.x.x` (or put your version here) Steps to reproduce or a small repository showing the problem: What I to accomplish is to add a custom select that maps to a property of my Entity. I've found an work around but would like to know if there is an easier/cleaner way to do this. So I've my model: [code block] This entity has a ManyToMany relationship to User. The `JoinTable` `groups_users` has one extra column `active` this `active` indicates if the group that the user is linked to is visible. When I query the groups to get all the groups for one user (also the inactive groups) I do this: [code block] As you can see the `Group` entity has a property called active. As for now the `active` property is not seen by `typeorm` so what I did was the following: I added this to the active property: [code block] By setting `select` to `false` the other queries won't break (since active isn't a real column inside the `group` table). Now I added this to the query: [code block] By doing this the active property is filled for each user and the `active` is true or false according the 0 or 1 in `JoinTable`. To query I ended up with is: [code block] which leaves me with the correct output. Now thi
dropping node < 4
@luin what do you think? Can this make it into v3? I'm primarily concerned about dependencies and being able to use some of the recent es6 features
Axios returns a generic "Network Error" even when the request got a response code
Describe the bug When making a request to my API, the catch block has a generic "Network Error" message, but when checking in the network inspector the request got a response code 413. This causes my users to incorrectly report that 'the website thinks i dont have a solid internet connection'. I suspect this happens for other codes too because this has been going on for a while. To Reproduce Make a request with a very large payload to trigger a 413 response Expected behavior The catch block should have the response code Environment - Axios Version: 0.25.0 and 0.21.2 - Adapter: xhr (i think? i dont remember changing this, so i guess whatever is default?) - Browser: Chrome - Browser Version: 97.0.4692.99 - Node.js Version: 14.18.1 - OS: OSX 12.1 Additional context/Screenshots [code block] My axios instance code: https://github.com/Miodec/monkeytype/blob/master/src/js/axios-instance.js
Serverless Framework project fails to deploy because of archive size
Bug description Generated bundle of the Serverless project has too big size and exceeds allowed by AWS Lambda 250 MB. It happens because of big sizes of downloaded @prisma/client, which, for some reasons, downloads engines folder that has unzipped size of 96 MB. And the other big files are connected to generated using command `prisma generate` schema. Dependency versions @prisma/client: "^2.20.0" prisma (dev) : "^2.20.1" serverless (dev): "^2.32.1" serverless-webpack: "^5.4.0" webpack: "^5.11.0" @types/webpack: "^4.41.25" Webpack config [code block] Serverless webpack options [code block] Environment & setup - OS: Mac OS Big Sur 11.1 - Database: PostgreSQL - Node.js version: 12 - Prisma version: 2.20.1 Background This is on the first deploy of Prisma to our existing Lambda stack. We have not been able to get Lambda working yet. We bundle our functions through webpack before deploying. I have looked at the webpack bundle and confirm that @prisma/client is being bundled with the lambda function before deploying.
[BUG]:Drizzle-Kit 0.19.0 Fails to Generate Migrations
What version of `drizzle-orm` are you using? 0.27.0 What version of `drizzle-kit` are you using? 0.19.0 Describe the Bug I was using Drizzle Kit version of 0.18.1 and generating migrations with this command. `drizzle-kit generate:pg --config=drizzle.config.ts` As soon as I updated drizzle-kit to 0.19.0 version this command doesn't work anymore throwing the error `TypeError [ERR_INVALID_RETURN_PROPERTY_VALUE]: Expected a url string to be returned for the "url" from the "drizzle-kit/loader.mjs 'resolve'" function but got instance of String.` Expected behavior _No response_ Environment & setup _No response_
Error: Failed to query available provider packages: Client.Timeout exceeded while awaiting headers
Terraform Version [code block] Terraform Configuration Files [code block] Expected Behavior Expected init to work Actual Behavior Initializing provider plugins... - Finding hashicorp/aws versions matching "~> 3.0"... Error: Failed to query available provider packages Could not retrieve the list of available versions for provider hashicorp/aws: could not query provider registry for registry.terraform.io/hashicorp/aws: the request failed after 2 attempts, please try again later: Get "https://registry.terraform.io/v1/providers/hashicorp/aws/versions": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) Steps to Reproduce `terraform init` Additional Context I can use curl and access the url that terraform says it can't access with no issues I've tried multiple times over 2 days and issue doesn't change. Terraform always fails, curl always succeeds Had no issues with 0.12, but 0.13 has not worked yet Terraform section was the only change made going to 0.13 This is on Mac I also tried with only the posted terraform config and still get same issue