All Issues
24,993 verified issues
[webview_flutter] not working choose file (input type file)
Steps to Reproduce 1. Run simple index.html with tag `<input type="file">` in webview_flutter 2. Try to click to input (choose file) and nothing happens
Unclear documentation: create() doesn't actually insert new row
Issue type: [ ] question [ ] bug report [ ] feature request [x] documentation issue Database system/driver: [ ] `cordova` [ ] `mongodb` [ ] `mssql` [ ] `mysql` / `mariadb` [ ] `oracle` [ ] `postgres` [x] `sqlite` [ ] `sqljs` [ ] `websql` TypeORM version: [x] `latest` [ ] `@next` [ ] `0.x.x` (or put your version here) Steps to reproduce or a small repository showing the problem: Currently, `repository.create()` creates new instance of entity, but doesn't put it into db - you have to manually call `repository.save()` afterwards so that typeorm would actually run INSERT statement. I think that a lot of developers may not understand it from current documentation, and that it should be said so explicitly to avoid confusion. (Will submit PR to docs myself if maintainers approve this).
Prettier 2.0 (old)
Note added by @j-f1: This is NOT the current plan for Prettier v2.0. We’ve significantly scaled back our plans for what Prettier 2.0 will do, allowing us to get a less-controversial release out sooner: https://github.com/prettier/prettier/issues/6888 --- I've been thinking a bit about what we would do if (don't create a milestone just yet :wink:) we were to do a Prettier 2.0 release with some API/CLI breaking changes. No significant changes to code formatting other than perhaps changing some defaults. Easy? #68/#3469 - Change default value for `trailingComma` to `"es5"`. The diff advantages alone are excellent, and this seems to be commonplace among the most popular JS projects. CLI: #2691 - CLI defaults to `"*/.{js,ts,...}"`. People should just be able to do `prettier --write` without passing messy globs _#0CJS_ #2846 - Replace the "parser" option with "language". e.g. `echo ".foo {}" | prettier --language css` Keep `--parser flow` or perhaps support something like `--parser.js flow` for future extensibility. Remove `--flow-parser` option. Has been deprecated for a long time. For debate - #838 - Consistently add quotes to object keys. e.g. put quotes around `origin` in this example: [code block] - Change the default value for `singleQuote` to `true` Airbnb, standard, xo, and probably the majority of JS devs prefer this. Maybe do a Twitter poll to gauge opinions on this. > To be clear, the Airbnb config requires single quotes for JS and doub
Use @map'ed enum values as TS enum values
Problem Consider the following schema: [code block] In database, it works as expected, the enum name and values are taken from the `@map` and `@@map` directives. In TypeScript, however, the generated values are as follows: [code block] Which is a problem, because every time you want to serialize the object returned from the database by prisma, you have to remap these values to the ones that the project uses (which is the database version). A simplified example would look like this: [code block] It gets much worse when there are nested includes. Suggested solution If explicitly defined, use values from `@map` directives as enum values, like so: [code block]
[BUG]: type obtained with $inferInsert is empty
What version of `drizzle-orm` are you using? 0.32.0 What version of `drizzle-kit` are you using? 0.23.0 Describe the Bug I defined a users table in my drizzle schema, and the NewUser type obtained with users.$inferInsert is empty: Expected behavior NewUser type should have most of the users table properties. Environment & setup Fedora Linux node-postgres typescript: 5.5.3
Update rpm dependencies file for newer CXXABI requirement
VS Code Version: 1.53.0 OS: RHEL7.9 Error: The terminal process failed to launch: A native exception occurred during launch (/lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /usr/share/code/resources/app/node_modules.asar.unpacked/node-pty/build/Release/pty.node)). [code block]
Extend config
Inside an org with a lot of repos we would like to maintain a consistent code style by sharing formatting/linting configuration files. TSLint, ESLint, TypeScript tsconfig etc. all allow this by specifying an `extends` property that points to another config, resolved by node module resolution algorithm. Meaning it's possible to do this: [code block] The rules get shared, but individual rules can still be overridden where it makes sense for only that project. Just passing the path to the config file also prevents editors from detecting that they should use prettier.
[BUG] NMP v7 error on install — 'must provide string spec'
Current Behavior: Trying to run `npm install` on my project `api-server-boilerplate` gives error [code block] Full error log [code block] Expected Behaviour: I expected it to install as per normal, or at least get an error that tells me what to do to fix it. I have searched for this "must provide string spec" and can't find any results. The only fix is to roll back npm to v6 Steps To Reproduce: [code block] Environment: - OS: macOS 10.15.7 (19H2) - Node: 15.0.1 - npm: 7.0.7
Feature Request: SVN Support
Add VCS Subversion Support - Simple file changes tracking as git.
Less strict validation of input objects
I'm wondering if we really need raise an error wen additional field is passed as part of an input object. see: https://github.com/graphql/graphql-js/blob/master/src/utilities/isValidJSValue.js#L67-L72 Any additional fields could just be ignored or dropped and warnings rather than errors produced.
Express v5 blockers
_I started writing this as a reply to https://github.com/expressjs/express/issues/4920#issuecomment-1575599117 but the issue was locked just before I finishing typing my comment._ @dougwilson Thanks for your continued work on express. I'm sorry you've had to deal with reports of bogus security vulnerabilities as well as folks who don't know better assuming that you've abandoned the project. I hope it doesn't get you down. ❤️ I do have a question re: > reach out and I would be happy to Zoom with you or similar and we can work on the remaining items together, like see what you want to help with or hear what there is and you can let me know what you can do. Are you open to the idea of enumerating the remaining work to be done in public, rather than in private Zoom calls, e.g. on this issue or another one? It may seem like asking folks to get on a Zoom call is not a big ask, but time zones and other factors could make that a nontrivial barrier. Moreover, documenting this in a public issue would eliminate the need for repeating yourself over `N` Zoom calls. The last update said: > Express 5 is pretty much completed at this point, and we're just finishing up the last code merges in upstream modules in order to bump the dependencies finally in the 5.0 branch. If this is still the case, perhaps you could provide more details about which modules are currently blocked and link to any relevant PRs/issues that are stalled. Even if you'd still prefer to for folks that want to help t
Ng new project isn't working
i am trying to create a new angular project , it's not working and having this output : i have node v : v13.13.0 angular v : Angular CLI: 9.1.2 npm v : '6.14.4' \ Installing packages...npm WARN deprecated tslint@6.1.1: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated fsevents@1.2.12: fsevents 1 will break on node v14+. Upgrade to fsevents 2 with massive improvements. npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm ERR! Unexpected end of JSON input while parsing near '...},"4.2.1":{"name":"@a' npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\dell\AppData\Roaming\npm-cache\_logs\2020-04-22T08_41_24_031Z-debug.log × Package install failed, see above. The Schematic workflow failed. See above.
[google_maps_flutter] App crashes with a java.lang.NullPointerException while popping a screen with a GoogleMaps widget
Internal: b/292548402 Steps to Reproduce I have reproduced it on a Pixel 3 in debug mode REAL (Android 12) and emulated (api level 30). 1. Execute `flutter run` on the code sample with `google_maps_flutter: ^2.1.7` dependency 2. Press the "Push map" button 3. Press the top right "x" IconButton or the back arrow to pop the screen 4. repeat from 2 until a crash occurs Expected results: No crash. Actual results: This 👇 https://user-images.githubusercontent.com/13722041/173616129-4cce324d-3481-4ea7-bc16-5c52c0493f10.mp4 <details> <summary>Code sample</summary> [code block] </details> <details> <summary>Logs</summary> [code block] Flutter doctor -v [code block] </details>
After upgrade to 1.0 GET request with parameters in the url fail
Working request with Axios v1.0.0-alpha.1: [code block] Same request with 1.0.0 fails with a 404. 1.0.0 was promoted today. When I print the failed response it looks like something is parsed/encoded incorrectly. [code block] To me the `?` is missing in between `commits` and `q`. When I don't parse the parameters on the URL and use `config.params` it works with Axios `1.0.0`. [code block] The success response then shows this `_header`: [code block] In the working version I do see the `?`. So right now the workaround is either sticking with v1.0.0-alpha.1 or using config.params instead of passing them with the .get call.
App Crashes - On upgrading to Android 14(SDK 34)
Description Currently, my codebase supports Android 13 (SDK version: 33). I wanted to upgrade to SDK 33(Android 14) On Android 14 updates, the following changes have been made: kotlinVersion = "1.6.0" buildToolsVersion = "34.0.0" minSdkVersion = 23 compileSdkVersion = 34 targetSdkVersion = 34 My current React Native version is 0.70.8. However, upon launching the application, I encountered an issue where the App Crashes immediately on the launch. To investigate this, I pulled a Bug Report, which provided the following insights: 1. Caused by: java.lang.RuntimeException: Requested enabled DevSupportManager, but BridgeDevSupportManager class was not found or could not be created. 2. Caused by: java.lang.SecurityException: : One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively for system broadcasts. 3. Caused by: java.lang.reflect.InvocationTargetException. 4. Caused by: android.os.RemoteException: Remote stack trace. React Native Version 0.70.8 Output of `npx react-native info` System: OS: macOS 14.0 CPU: (8) arm64 Apple M1 Memory: 65.91 MB / 16.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 20.4.0 - /opt/homebrew/bin/node Yarn: 1.22.19 - /opt/homebrew/bin/yarn npm: 9.8.1 - /opt/homebrew/bin/npm Watchman: 2023.07.10.00 - /opt/homebrew/bin/watchman Managers: CocoaPods: 1.13.0 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: DriverKit 23.0, iOS 17.0, macOS 14.
[BUG]: Importing drizzle-kit/api fails in ESM modules
What version of `drizzle-orm` are you using? 0.33.0 What version of `drizzle-kit` are you using? 0.24.2 Describe the Bug When I import `pushSchema` from `drizzle-kit/api` in ESM files it fails with the following error: https://codesandbox.io/p/devbox/drizzle-kit-import-xkmlfw? [code block] [code block] Expected behavior Import without a problem like the commonJS file. [code block] [code block] Environment & setup I saw this problem first when I tried to use pushSchema in my unit tests for my Typescript(ESM) package. When I changed to CommonJS it just worked. So I created this empty ESM javascript package to make sure nothing is interfering with the imports. https://codesandbox.io/p/devbox/drizzle-kit-import-xkmlfw [code block]
aws ecr get-login should use --password-stdin if available
Currently, on Docker 17.07+, when evaling the output of `aws ecr get-login`, the following error message appears: [code block] It would be nice if `aws ecr get-login` could use `--password-stdin` if it's available. The workaround is to use `get-authorization-token`, but that involves everyone writing code, whereas `--password-stdin` is a good idea for everyone who'd ever use `aws ecr get-login`.
AWS EC2 Behind ELB Always Prints Error Unexpected response code: 400
Hey guys - Can't seem to find out a solution for this, but when I run my app behind a load balancer, I get this error on the client: [code block] I understand the error, since it's trying to talk to the load balancer and now the EC2 instance (I'm not great with AWS so feel free to offer help on this one!) but what I don't understand is how to make the error not show up! I'd love to fix the root cause but I'm guessing it involves a separate dedicated socket.io server to handle all the real time stuff which I don't have time for at the moment, but could someone please run me through supressing this error? I'm assuming it's falling back to polling, which seems to work just fine (I have the socket connection connected and it fires) but I don't want to launch with a red error in my console. Thanks in advance for any advice you might have!
[v2] credentials supplied by aws sso login do not conform to AWS standards
AWS documents that credentials generated by `aws configure` are stored in the standard path `~/.aws/credentials`: > The AWS CLI stores the credentials that you specify with aws configure in a local file named credentials, in a folder named .aws in your home directory. https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html This path is not utilized by credentials stored by `aws configure sso` or `aws sso login`. Other tools (like Terraform and Boto3) that rely on this standard do not function because they do not see the credentials stored in the `~/.aws/cli/cache/` JSON files. > Shared credential file (~/.aws/credentials) https://boto3.amazonaws.com/v1/documentation/api/latest/guide/configuration.html
Many-to-Many with custom fields
Hi guys I was wandering if its possible to have a many-to-many relationship where I can add some custom fields to the created table. I was looking at previous issues and someone told to create the other table and use one-to-many relationship. However I'm not understanding how I would acomplish that where then I would do something like: `const user = await this.userRepository.findOne(id)` and get the result as a many-to-many. Something on this lines: User: n------ n :Group And get the output as: ` { "id": 1, "firstName": "firstname", "lastName": "lastname", "groups": [ { "id": 1, "name": "Group1" } ] } ` Behind this there is the table user_group that makes this connection between User and Groups and has for example a field called isDeleted that helps me to know is this was soft deleted and not show this entry. Could you guys help me on the right path?