All Issues

Provide Official AWS CLI Docker Image

I was surprised to find that there is no official Docker image for development with the AWS CLI. The "amazon" user on Docker Hub contains only the these images for working specifically with ECS and Elastic Beanstalk, and there do not appear to be any official Amazon Docker images on the new Docker Store yet. When I searched "aws cli" on Docker Hub, the most popular image (with 1M+ downloads) was this one, created by Mesosphere. It's good enough, with a very simple Dockerfile based on the super-tiny Alpine Linux image. Upon further investigation, I found the `aws-codebuild-docker-images` repo in this organization, with an `ubuntu-base` Dockerfile. This image looks great, so why hasn't it been pushed to Docker Hub/Store? For that matter, why haven't any of the images in that repo been pushed? The Mesosphere `aws-cli` image will work fine, but its simplicity compared to that `ubuntu-base` made me concerned that it hasn't been properly optimized; similarly, the `ubuntu-base` image is based off Ubuntu 14.04.5, which is both old and bulky compared to Alpine Linux. TL; DR I believe there should be an official `aws-cli` Docker image maintained by Amazon and pushed to Docker Hub/Store. Ideally, it should support all the major modern Linux distros, including Alpine Linux. One should be able to run the following command, and have everything just work: `docker run -it amazon/aws-cli` EDIT This Issue is now being tracked at #3553. You should like that one to show your support

Portable version!

You can provide a portable version of it? Or to support the configuration file or plug-sync to the cloud; Otherwise, each computer must be installed once, configured once. . It is a waste of time; Thank you

Feature request: symbols tree view

VSCode very quickly got to _nearly_ being my default editor. One thing I'm missing is something like https://atom.io/packages/symbols-tree-view where I can view the structure of a file whilst editing. I've used this view across many editors for years.

[php] Provide HTML tag matching/language service support

I don't know if it's just me but there's no support for HTML tag matching. If I click on `div`, every instance of `div` are highlighted instead of the closing `</div>`, which is a PITA.

Angular Output/Input decorators are moved to new line

Prettier 1.14.0 Playground link [code block] Input: [code block] Output: [code block] Expected behavior: Decorators are kept on the same line. More details: When using Angular, it's recommended to follow their style guide, which specifies: > Placing the decorator on the same line usually makes for shorter code and still easily identifies the property as an input or output. Put it on the line above when doing so is clearly more readable. Angular classes are a valid (and common) use-case for Prettier, but with Prettier 1.14 (relevant PR) it deviates from the Angular style guide, causing unwanted changed for most people using Angular. Note that the above code example (input) is taken directly from the Angular style guide. The original PR to change this behavior mentions that mobx is the only library using same-line decorators, which is clearly not the case, with Angular being a (big) second one. To avoid reverting the new behavior completely, which is probably still wanted by some people - I suggest adding an option to the config to keep the old behavior, or prefer the new one (default should be discussed further).

Code won't update on macOS

- VSCode Version: Version 1.3.0-insider (1.3.0-insider) 6bc81df453ab2156d2630fbb89ad7d0c80620420 - OS Version: OS X 10.11.5 Steps to Reproduce: 1. A message pops up saying there's a new version and Insiders will be updated after it restarts. 2. Click 'Update Now'. Code closes but doesn't reopen even after waiting a very long time. 3. After manually reopening it it's still on the previous version This has been happening for the last few weeks so it isn't a recent development, but with the daily builds now it's a little more annoying. Downloading the most recent version from the website and replacing it works fine. The stable build of Code I have installed does the automatic update fine. I have both builds installed in my Applications folder.

Vue Support

Let's start a master issue for all the related vue.js progress. List of projects using Vue (based on tweet https://twitter.com/Vjeux/status/873726664630337536 ): - https://github.com/gitlabhq/gitlabhq - https://github.com/bootstrap-vue/bootstrap-vue - https://github.com/ElemeFE/element/ - https://github.com/algolia/vue-instantsearch - https://github.com/vuetifyjs/vuetify - https://github.com/samiheikki/javascript-guessing-game - https://github.com/phanan/koel - https://bitbucket.org/sellvana/core/src/4231c995aff9785ca60a550b0ee06c286f4bf619?at=sn1 - https://github.com/search?utf8=%E2%9C%93&q=language%3AVue+stars%3A%3E1000&type=Repositories&ref=advsearch&l=Vue&l=

The default naming scheme for containers created by Compose

> The default naming scheme for containers created by Compose in this version > has changed from `<project>_<service>_<index>` to > `<project>_<service>_<index>_<slug>` Is there any way to disable this behavior apart from using `container_name` in yaml file? We have many scripts that rely on container names and are not using swarm, just a single container stack. This change is very inconvenient for us.

Navigate through explorer by typing start of file/folder name

- VSCode Version: Any - OS Version: Any Feature Proposal When opening a folder containing hundreds of items (for example: `node_modules`) There is no easy way to get to a child folder/file without scrolling around. Would it be possible to allow the file viewer to navigate down to let's say the first file of the next letter keypressed? [code block] Just an idea, would help navigating large filesystems a bit easier.

[1.7] CTRL+C fails to stop containers when running compose in the foreground

I can't reproduce it but I would say about 10% of the time when I hit CTRL+C, the containers that were started with `docker-compose up` fail to stop. I'll get an ABORT message in the terminal but they are still up. When it works, it says "gracefully stopping..." instead of ABORT. At this point I need to `docker-compose stop` them to "really" stop them. It was much worse in earlier versions of Compose but it's still happening often enough that I feel like it needs some attention. If you need more info let me know. Environment System [code block] Docker [code block] Docker Compose [code block] Potentially relevant information When I encounter the issue I'm always running multiple containers, such as postgres, redis, and multiple web services. I never run 1 container so I can't say for sure if it would happen with only 1. It happens with and without using `links` and both the legacy and v2 `docker-compose.yml` files.

docker-compose hangs

Description of the issue In a new server installation (on a VPS provided by OVH) running Ubuntu 18.x the Docker system works flawlessy and fast but docker-compose sometimes hangs indefinitely for no reason. And for every command, from version to ps, up, logs and so on. I tried everything regarding DNS and name resolution, even disabling systemd-resolved. When it works it is fast. When it hangs I can see the `/tmp/_Mxyz123123` directory created. Running with verbose hangs before any output. And then completes flawlessy. Context information (for bug reports) Output of `docker-compose version` [code block] Output of `docker version` [code block] Output of `docker-compose config` (Make sure to add the relevant `-f` and other flags) [code block] Steps to reproduce the issue 1. docker-compose <command> Observed result Sometimes hangs Expected result Run fast. Stacktrace / full error message No stacktrace but i managed to strace the behavior. [code block] Additional information Linux vps[omit] 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 18.04.2 LTS docker-compose installed with curl I have lot of other docker-compose environments working and this is the first time I see this behavior. Any idea on what to check or where to look?

☁️ Cloud & DevOpsAmazon

📱 Mobile & Cross-Platform

Add support for AWS API Gateway Basic Request Validation

This is a Feature Proposal Description AWS API GW officially supports this now - http://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-method-request-validation.html For example, it could be set as a new property somewhere in `service.function.events.http.validation` config object. Blog post: https://aws.amazon.com/blogs/compute/how-to-remove-boilerplate-validation-logic-in-your-rest-apis-with-amazon-api-gateway-request-validation/

Support third-party 64-bit libraries on Android

Excerpt from the Android Developers Blog article, Get your apps ready for the 64-bit requirement: [added by @hramos] The 64-bit requirement: what it means for developers Starting August 1, 2019: All new apps and app updates that include native code are required to provide 64-bit versions in addition to 32-bit versions when publishing to Google Play. Extension: Google Play will continue to accept 32-bit only updates to existing games that use Unity 5.6 or older until August 2021. Starting August 1, 2021: Google Play will stop serving apps without 64-bit versions on 64-bit capable devices, meaning they will no longer be available in the Play Store on those devices. This will include games built with Unity 5.6 or older. The requirement does not apply to: APKs or app bundles explicitly targeting Wear OS or Android TV, which are form factors that do not currently support 64-bit code. APKs or app bundles that are not distributed to devices running Android 9 Pie or later. Original Issue Hey, it appears that React Native on Android doesn't provide a 64-bit version of the `libreactnativejni.so` native library, which can cause compatibility issues on 64-bit devices. I ran into this while attempting to integrate React Native with a large existing application I'm developing. Steps to reproduce: 1. Create a new application with `react-native init`. 2. In the "android/app/build.gradle" file, add `compile 'io.realm:realm-android:0.82.2'` to the end of the `dependencies {}` b

Supporting HTML

Angular, Vue and Ember all use variants of html/mustache with JS and CSS embedded. It would be really awesome to make prettier support it as well. This would allow the project to be the one stop destination for all the front-end related code.

📱 Mobile & Cross-PlatformGoogle

Auto Indent / Code Formatting / Beautify

This is an ongoing feedback issue from User Voice.

Inline Google Maps support

<a href="https://github.com/Hixie"><img src="https://avatars.githubusercontent.com/u/551196?v=3" align="left" width="96" height="96" hspace="10"></img></a> Issue by Hixie _Thursday Jul 16, 2015 at 22:26 GMT_ _Originally opened as https://github.com/flutter/engine/issues/30_ --- _From @collinjackson on July 8, 2015 20:23_ We are going to want to have support for maps in Sky. There are a few ways we might go about doing this: 1. Use native maps widget for each platform to render the map 2. Use maps widget for each platform to render to a texture and draw the map ourselves 3. Develop a custom maps SDK for Sky The second option would be ideal but may not be possible. We should investigate which approach is best and build a demo app. _Copied from original issue: domokit/mojo#310_

Provide more ways to bail out inside Hooks

There's a few separate issues but I wanted to file an issue to track them in general: `useState` doesn't offer a way to bail out of rendering once an update is being processed. This gets a bit weird because we actually process updates during the rendering phase. So we're already rendering. But we could offer a way to bail on children. Edit: we now _do_ bail out on rendering children if the next state is identical. `useContext` doesn't let you subscribe to a part of the context value (or some memoized selector) without fully re-rendering. Edit: see https://github.com/facebook/react/issues/15156#issuecomment-474590693 for solutions to this.

Support count in resource fields

I would like to be able to define repeated fields the same way I can define repeated resources. For instance, this could be used to set beanstalk environment vars based on a list passed in by a variable. [code block]