All Issues
24,993 verified issues
Tabs for integrated terminal
Status update from @Tyriar: - We started exploring this in March https://github.com/microsoft/vscode/issues/10546#issuecomment-800286034 - April plan: https://github.com/microsoft/vscode/issues/120241 - Tabs have landed in Insiders work in progress & call for feedback https://github.com/microsoft/vscode/issues/10546#issuecomment-823291688 - Moved to backlog to cover terminals in editor area https://github.com/microsoft/vscode/issues/10546#issuecomment-826900427 - Assigned to June for "terminal editors" https://github.com/microsoft/vscode/issues/10546#issuecomment-852971002 - Terminal editors plan filled in (https://github.com/microsoft/vscode/issues/125514), request for feedback https://github.com/microsoft/vscode/issues/10546#issuecomment-860644971 --- Feature request. Default terminal But could be more usable...
Error uploading empty file: "seek() takes 2 positional arguments but 3 were given"
awscli version "1.11.13-1ubuntu1~16.04.0" was installed with the Ubuntu package manager and run like: [code block] It successfully uploads all the files in the source directory except for one zero-byte file. It fails there with: [code block]
Error loading state: AccessDenied: Access Denied (AWS S3 backend)
Terraform Version [code block] Debug Output Crash Output [code block] Also tried with `profile`. Same thing. And when try this: [code block] Expected Behavior Actual Behavior Steps to Reproduce Additional Context User that is trying to access S3, have these policies set: [code block] I also tried adding AdministratorAccess, but it did not change anything. References https://github.com/hashicorp/terraform/issues/13589
Support override keyword on class methods
(Update by @RyanCavanuagh) Please see this comment before asking for "any updates", "please add this now", etc.. Comments not meaningfully adding to the discussion will be removed to keep the thread length somewhat reasonable. ------ (NOTE, this is _not_ a duplicate of Issue #1524. The proposal here is more along the lines of the C++ override specifier, which makes much more sense for typescript) An override keyword would be immensely useful in typescript. It would be an optional keyword on any method that overrides a super class method, and similar to the override specifier in C++ would indicate an intent that "_the name+signature of this method should always match the name+signature of a super class method_". This catches a whole range of issues in larger code bases that can otherwise be easily missed. Again similar to C++, _it is not an error to omit the override keyword from an overridden method_. In this case the compiler just acts exactly as it currently does, and skips the extra compile time checks associated with the override keyword. This allows for the more complex untyped javascript scenarios where the derived class override does not exactly match the signature of the base class. Example use [code block] Example compile error conditions [code block] IntelliSense As well as additional compile time validation, the override keyword provides a mechanism for typescript intellisense to easily display and select available super methods, where the intent is to spe
Support [skip ci] out of box with github actions
Pretty much every other ci/cd solution will skip running a workflow/pipeline if `[skip_ci]` is in the commit text. Currently the hack for this is to add an `if` statement to jobs with something like `"! contains(toJSON(github.event.commits.*.message), '[skip-ci]')"`. However, this still runs the workflow, just not any jobs with the condition. Please provide an out of box way for this to happen. One solution would be something like paths-ignore: [code block] @eseay
Testing in VS Code
State of the World Testing support in VS Code has been a feature request for a long time. The VS Code community has build excellent extensions around testing, for example: - The Test Explorer UI from @hbenl - Wallaby.js from the Wallaby team - Jest from @orta - ...and many more Each implementation of testing presents a different set of features, UI, and idiomaticity. Because there is no sanctioned approach to tests in VS Code, extension developers tend to make bespoke implementations, as we've seen in the Python and Java language extensions. Ideally, like in debugging, a VS Code user would have just about the same experience as they work between projects and languages. VS Code's Approach > Investigate how VS Code can improve the testing support. Several extensions are already providing testing support, explore what APIs/UIs could be added to improve these testing extensions and the test running experience. -- 2020 Roadmap The Test Explorer UI presents the best point of inspiration for us, as there are many existing extensions built on its API: it's capable and proven. Regardless of the direction we take in VS Code, we should have a way for its Test Adapters to be upgraded to the new world. Wallaby is an excellent extension, but it's tailored and purpose-built to JavaScript, and includes functionality which is not readily portable to other languages. While it is a good source for inspiration, we're not aiming to encompass Wallaby's feature set in the extension points we
Define host volumes in the `volumes` section of the Compose file
It seems that there is not the possibility to mount a host directory using the `volumes` section using the versrion 2 I would propose an configuration example [code block] My use case: docker-compose.yml [code block] Override docker-compose.prod.yml [code block]
"Warning: Value for undeclared variable"
Current Terraform Version [code block] Use-cases In our current project, we use a `common.tfvars` file to store shared configurations across multiple modules and plans. Up until recently, this has worked very well in allowing us to dry up configurations to a single location. With recent upgrades we've started seeing `Warning: Value for undeclared variable`, as not all "common" configurations are used in every plan. Proposal I'd like to request that a feature / flag is included to allow for ignoring the "Value for undeclared variable" warning condition, and additionally request that you not make it a breaking error in the future -- as the output indicates is the intention. Being able to include a collection of configurations and have a portion of the ignored is a valuable feature. I do understand that there is also a valid use-case for having it behave in a stricter way to many -- perhaps most. A flag or configuration allowing for opt out of strict checking seems to be an acceptable alternative.
Next Steps for Fully Functioning Composite Actions
NOTE: For those who are not aware, I'm a college student who interned at GitHub for Summer 2020. Thank you all for all the thoughtful comments and feedback on this thread but since I'm not working at GitHub currently, I will not be responding to any new comments below in this thread. ================================================ Hi there 👋 We just released a new feature called composite run steps actions(https://docs.github.com/en/actions/creating-actions/about-actions#composite-run-steps-actions). This issue thread will serve as a point of reference for people who are curious about the next steps after this feature and what we plan to work on next. There are probably quite a few questions about when we are going to support in the future like "when are you going to support 'uses' steps in a composite action"? In this Issue thread, I'll talk about the technical problems that we are planning to solve to accomplish this. Throughout the next week, I'll update it with any additional updates. tl;dr in this issue, I'll go over what we currently support for composite run steps and how we plan on developing fully functioning composite actions. Composite run steps background What is a composite run steps action? Many of you have been asking us to build a feature that enables them to nest actions within actions (ex: https://github.com/actions/runner/issues/438). An important first step for supporting nesting within action is to first start supporting the execution of multi
[Community Contest] A logo for Axios
Axios has grown to become a popular library with over 3 million weekly downloads on npm. I think it's time axios has its own logo, just like many other major libraries out there. I've designed a concept for the logo, and I hope you guys like it. The logo is based on the concept of request and response. The first one is a square icon/profile picture. The second and third are full logos. These images are not full size, so if you do like them and plan to use them, I can send you the full sized files. Edit: Should we count 👍 reactions to this parent comment as votes for this logo submission, or just people in favor of a new logo in general? I can make a a second comment for votes for this submission, or we can do a proper poll with strawpoll later when people are done submitting their ideas.
docker-compose copy file or directory to container
we miss a possibility to copy a file or directory using docker-compose. I find this really useful. Please check many +1 in premature closed https://github.com/docker/compose/issues/2105
New RN project will not build on Xcode 12.5 Beta 3
EDIT (by @kelset): Please read the current status of things at this comment. --- Description Running the latest Xcode/React Native etc. Upgrading an existing project failed so I tested with a new RN project (npx react-native init TestApp --version 0.64.0 --template react-native-template-typescript). It will build and run under Xcode 12.4, but fails when attempting to build with Xcode 12.5 Beta 3 (12E5244e). It's unlikely to be relevant, but the app is targeting an iPhone 12 Simulator running iOS 14.5 React Native version: Run `react-native info` in your terminal and copy the results here. [code block] Steps To Reproduce Provide a detailed list of steps that reproduce the issue. 1. Install the above tools, Xcode 12.5 Beta 3, RN 0.64.0 etc. 2. Create a new app (npx react-native init TestApp --version 0.64.0 --template react-native-template-typescript) 3. [code block] 3. [code block] then [code block] 4. [code block] 5. This error also appears if you replace step 4 with launching Xcode.app and building the app that way Expected Results Describe what you expected to happen. A successful build of the example app, running on the simulator. Snack, code example, screenshot, or link to a repository: Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem. You may provide a screenshot of the application if you think it is relevant to your bug report. Here are some tips for providing a min
Suggestion: allow get/set accessors to be of different types
It would be great if there was a way to relax the current constraint of requiring get/set accessors to have the same type. this would be helpful in a situation like this: [code block] Currently, this does not seems to be possible, and I have to resort to something like this: [code block] This is far from ideal, and the code would be much cleaner if different types would be allowed. Thanks!
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) libjsc.so still occuring on Caterpillar S41 (Android 8.0)
Same as https://github.com/facebook/react-native/issues/24261 but still occuring on device Caterpillar S41 (Android 8.0). React Native version: 0.59.10 [code block]
Custom Cache-Control response header for `/_next/image`
Bug report Describe the bug When requesting `/_next/image(.)`, I'm getting this Response header: [code block] And it's fine... What's not fine is that I'm getting the same exact Response headers even when I use custom headers in `next.config.js`, i.e.: [code block] To Reproduce Try this `next.config.js` above, with an image that uses common `<img>` tag like this: [code block] And another tag that uses the new `next/image` component, with the same or whatever image url, for example: [code block] And try requesting those images in the browser, and look into `Devtools -> Network` tab, the Response headers, and see that for common `<img>` tag it's actually changed, whereas for new `<Image>` component it is not. Expected behavior For `/_next/image(.)` urls, I expected to see Headers that I setup, i.e. `Cache-Control: public, max-age=180, s-maxage=180, stale-while-revalidate=180`. Screenshots Common `<img>`: New `<Image>`: System information - OS: not applicable / any - Browser (if applies): not applicable / any - Version of Next.js: 10.0.3 - Version of Node.js: 12.18.0 - Deployment: both `next start` on development machine, and actual Vercel deployment (screenshots demonstrate the case with local machine, but I've confirmed that the same is happening on a Vercel deployment) Additional context Originally I created an issue using "Feature request" template, and it got translated into "Idea discussion": https://github.com/vercel/next.js/discussions/19896 (how to d
Type checking/VS Code slow when using MUI
TypeScript Version: 3.8.0-dev.20191029 Search Terms: mui, material-ui, typescript, slow Example Project https://github.com/jdoklovic/mui-slowness Expected behavior: Make a bad change to something in src/react/pages/Main.tsx autocomplete seems to be speedy, and error reporting should be too. Actual behavior: Takes forever to see errors Related Issues: #32085, #32229, #31817, #30908 Not exactly sure what's going on, but the error reporting in VS Code is super slow. I've made sure I'm using specific named imports, and I've even forked MUI and mad all of the internal code so the same and removed things like import from '..' but it didn't seem to help. Here's the output from tsserver logs which doesn't seem to contain anything that jumps out at me. Also note, I'm using typescript-eslint with the VS Code ESLint extension, not tslint, but eslint seems to be pretty fast. mui-slowness-tsserver.log
Allow extensions to publish beta releases and users to opt-in to them
Apologies if this has come up before; I'm unable to find any related issues. It would be cool to be able to publish extensions in a beta form (similar to Code Insiders) so that they can be run "in production" with real users that have opted-in. This would reduce the disk in publishing an extension because you can push it to a smaller number of users for testing (I probably don't need to sell this to you, I guess you have Insiders for very similar reasons). I know we can package and distribute extensions ourselves for now, but it's not as easy (eg. updating is not automatic). I originally thought the "Preview" flag might've provided this functionality but unless I've overlooked something, it does not seem to.
How to catch and handle errors to report logs on server side
Hi, I'm in the situation where we want to sent errors, both on server and client side, to Sentry tool. Our app uses Express as a custom server. Basically we create an express app, apply some middlewares but delegate all the real job to the next.js handle: [code block] With this approach next.js takes control over the rendering process and any error is catch by next.js and the only way I have to process it is overriding the `_error.js` page file. Within that `_error.js` file I need a universal way to report errors to Sentry. Currently there are two libraries (`raven` for node and `raven-js` por javascript). The proble is I can't import both of them because `raven` works for SSR but fails when webpack builds the bundle, and also `raven-js` fails due XMLHTTPRequest dependency too. Is there a way I can be notified for next.js error on server side?
[BUG] npm update not updating package.json
npm update does not update and write to package.json node v12.14.1 npm v6.13.4 windows 10 pro 64-bit 1903 build 18362.592 Delete node_modules directory and package-lock.json, open cmd.exe and run the following: [code block] I'm expecting the contents of package.json to be updated. Here is my package.json: [code block]
[image_picker] losing connection with device
I am trying to use image_picker^0.6.1+11 to capture images from camera as the source it works fine for the first time but when I try to retake the image the app crashes with a log lost connection to the device without any exception or error. UseCase: I want to capture three images from camera and view them in an imageview. I have tested the app on the latest flutter master and stable channels but has same issue here's my [code block] output [code block] Steps to Reproduce pubspec.yaml [code block] 1. example from image_picker:https://pub.dev/packages/image_picker 2. capture a image 3. re capture the image it crashes Logs [code block]