All Issues
24,993 verified issues
Feature: Ability to clear log history
A feature I've thought would be useful since originally using Fig, and now Compose would be the ability to clear the log history for Composed-managed containers. Long-running or "chatty" containers can end up with a lot of log noise that may not be wanted. I'd expect a command like the following would solve the problem: `$ docker-compose logs --clear [service]`
aws s3 ls - find files by modified date?
Hi, We'd like to be able to search a bucket with many thousands (likely growing to hundreds of thousands) of objects and folders/prefixes to find objects that were recently added or updated. Executing aws s3 ls on the entire bucket several times a day and then sorting through the list seems inefficient. Is there a way to simply request a list of objects with a modified time <, >, = a certain timestamp? Also, are we charged once for the aws s3 ls request, or once for each of the objects returned by the request? New to github, wish I knew enough to contribute actual code...appreciate the help.
Path mappings based module resolution
Proposed module resolution strategy UPDATE: proposal below is updated based on the results of the design meeting. Initial version can be found here. Primary differences: - instead of having `baseUrl` as a separate module resolution strategy we are introducing a set of properties that will allow to customize resoluton process in existing resolution strategies but base strategy still is used as a fallback. - `rootDirs` are decoupled from the `baseUrl` and can be used without it. Currently TypeScript supports two ways of resolving module names: `classic` (module name always resolves to a file, module are searched using a folder walk) and `node` (uses rules similar to node module loader, was introduced in TypeScript 1.6). These approaches worked reasonably well but they were not able to model _baseUrl_ based mechanics used by RequireJS or SystemJS. We could introduce third type of module resolution that will fill this gap but this will mean that once user has started to use this new type then support to discover typings embedded in node modules (and distributed via `npm`) is lost. Effectively user that wanted both to use `baseUrl` to refer to modules defined inside the project and rely on `npm` to obtain modules with typings will have to choose what part of the system will be broken. Instead of doing this we'll allow to declare a set of properties that will augment existing module resolution strategies. These properties are: `baseUrl`, `paths` and `rootDirs` (`paths`
Execute a command after run
Hi, It will be very helpful to have something like "onrun" in the YAML to be able to run commands after the run. Similar to https://github.com/docker/docker/issues/8860 [code block] After the mongodb start, It will dump db2dump.domain.lan and restore it. When I will stop and then start the container, onrun part will no be executed to preserve idempotency. EDIT 15 June 2020 5 years later, Compose wan't to "standardize" specifications, please check https://github.com/compose-spec/compose-spec/issues/84
Setting header: 'Content-Type': 'application/json' is not working
Hi. I'm passing a custom header like this [code block] But it doesn't seem to work. Any ideas?
Support final classes (non-subclassable)
I was thinking it could be useful to have a way to specify that a class should not be subclassed, so that the compiler would warn the user on compilation if it sees another class extending the original one. On Java a class marked with final cannot be extended, so with the same keyword on TypeScript it would look like this: [code block]
Request feature "Integrated terminal"
It would be great if vscode has integrated terminal feature refer vim or atom https://atom.io/packages/term3 I saw this suggestion pending in uservoice(https://visualstudio.uservoice.com/forums/293070-visual-studio-code/suggestions/7752357-integrated-terminal) and repost here since it has specific repo
Proper tabs for open files
I _really_ miss proper tabs for open files (like VS proper), and the ability to rip a tab out into its own window.
Depends_on for module
Possible workarounds For module to module dependencies, this workaround by @phinze may help. Original problem This issue was promoted by this question on Google Groups. Terraform version: `Terraform v0.3.7` I have two terraform modules for creating a digital ocean VM and DNS records that are kept purposely modular so they can be reused by others in my organisation. I want to add a series of provisioners using local_exec after a VM has been created and DNS records made. Attempted solution I tried adding a provisioner directly to my terraform file (i.e. not in a resource) which gave an error. I then tried using the `null_resource` which worked but was executed at the wrong time as it didn't know to wait for the other modules to execute first. I then tried adding a `depends_on` attribute to the null resource using a reference to a module but this doesn't seem to be supported using this syntax: [code block] Expected result Either a way for a resource to depend on a module as a dependency or a way to "inject" (for lack of a better word) some provisioners for a resource into a module without having to make a custom version of that module (I realise that might be a separate issue but it would solve my original problem). Terraform config used [code block]
Hooks/ Plugins support to run arbitrary scripts
It would be nice if `docker-compose up|down|..` would look for custom scripts in the current directory, like: [code block] I guess this is mostly helpful when docker-compose is used to run the development environment. These scripts should not be meant to configure containers. My current use-cases include: - set up hostnames in `/etc/hosts` after container startup - run docker-rsync after container started Eventually docker-compose should allow these scripts to run in the background and stream stdout/stderr to `docker-compose logs`. Related https://github.com/docker/compose/pull/74 https://github.com/docker/compose/issues/57
Support use cases with conditional logic
It's been important from the beginning that Terraform's configuration language is declarative, which has meant that the core team has intentionally avoided adding flow-control statements like conditionals and loops to the language. But in the real world, there are still plenty of perfectly reasonable scenarios that are difficult to express in the current version of Terraform without copious amounts of duplication because of the lack of conditionals. We'd like Terraform to support these use cases one way or another. I'm opening this issue to collect some real-world example where, as a config author, it seems like an `if` statement would really make things easier. Using these examples, we'll play around with different ideas to improve the tools Terraform provides to the config author in these scenarios. So please feel free to chime in with some specific examples - ideally with with blocks of Terraform configuration included. If you've got ideas for syntax or config language features that could form a solution, those are welcome here too. (No need to respond with just "+1" / :+1: on this thread, since it's an issue we're already aware is important.)
Using shell command in docker-compose.yml
Hello, is there a way to use shell commands in `docker-compose.yml` file? Here is my use case: [code block] Currently it's giving me this error: [code block]
Facebook Engineers - Thank You For 2016
To all the Facebook Engineers working on open source, We at Reactiflux just wanted to take a moment to thank you for all your hard work in 2016. Your job isn’t easy. You have a million requests coming at you all the time from both your internal teams and the external community. Dan Abramov once compared managing issues and pull requests to juggling chainsaws on fire. Yes, we know all of you get paid really well to do open source full time, and that your work meets Facebook’s needs, but we think that you have gone above and beyond in the way that you have treated the community. The way that you guys respond to emails and Twitter mentions. The attention you give to each issue/PR. The time you give to different organizations doing podcasts and AMAs. The list goes on. We’ve personally seen an amazing humility in each of you, and it’s a pleasure to be around you wonderful people. Thank you for what you do and the excellence you put into all your efforts. We’d like to invite the React community to reply to this thread with your own “thank you” comments to the team at Facebook. Let’s show them how grateful we are! Feel free to include experiences with the team or just how the React ecosystem has helped you as a developer. Sincerely, On behalf of the Reactiflux community: @gabegreenberg @markerikson @KyleAMathews @taion @jquense @vcarl @benigeri @Phoenixmatrix
Latest react-native app doesn't work ":CFBundleIdentifier", Does Not Exist
On OS X El Capitan v10.11.4 node --version v6.0.0 npm --v 3.8.8 react-native-cli: 0.2.0 react-native: 0.24.1 watchman --v 4.4.0 xcode 7.3 $ react-native init AwesomeProject $ cd AwesomeProject $ react-native run-ios [code block]
Attempted to transition from state `RESPONDER_INACTIVE_PRESS_IN` to `RESPONDER_ACTIVE_LONG_PRESS_IN`, which is not supported.
Similar to #1693. It seems to be an issue with the `Touchable` component with Chrome Debugging on React Native 0.19.0. [code block] The code that produces this error is from a freshly started application using a TouchHighlight component: [code block] P.S. Is there a better way to copy a stacktrace? I'm just copying from the Chrome dev tools console
Error boundaries: Recover from errors thrown in `render`
So I'm trying to put some graceful error handling in case 1 of my views crap out: [code block] However, `MyGoodView` does not get rendered w/ the following stack trace: Seems like error throw React in a bad state where `renderedComponent` is `undefined`, thus cannot be unmounted. How do I handle this scenario?
Make Socket.IO great again
(yep, that headline is overrused) Disclaimer: - I have no control over the website (socket.io), to my knowledge only @rauchg has, so I'm unfortunately not able to fix those issues: https://github.com/socketio/socket.io/issues/2807 https://github.com/socketio/socket.io/issues/2791 https://github.com/socketio/socket.io/issues/2781 https://github.com/socketio/socket.io/issues/2773 https://github.com/socketio/socket.io/issues/2753 https://github.com/socketio/socket.io/issues/2743 https://github.com/socketio/socket.io/issues/2736 - I have no control over the chat example repository, that is the one that is behind the chat example, so I'm unfortunately not able to fix those issues: https://github.com/socketio/socket.io/issues/2821 (and all open PR over there) - I'm not even an expert in Socket.IO, just a developer digging around during his free time between two freelance contracts Now, enough about my limitations. The Server API and Client API were added on Github, do not hesitate if you find something missing! Current to-do list: - [x] release the version `2.0` of Engine.IO Engine.IO will now default to uws as WebSocket engine, that should bring great performance improvements. An important issue about double UTF-8 encoding was also fixed in the parser. The only "problem" is that one of the numerous issues open could need a fix over there, hence the delay. - [ ] complete the API docs (missing methods, code examples...): https://github.com/socketio/socket.io/issues/2350#issuecomm
Add option for parentheses around JSX.
I think prettier should have an option ~for TypeScript~ to omit JSX parentheses. Instead of this: [code block] Expected behavior: [code block]
Narrowing the Serverless IAM Deployment Policy
I’ve been spending time recently trying to remove Admin rights as a requirement for sls deployments. Still a work in progress, but so far I have this policy that I can attach to any “serverless-agent” AWS user, so that the serverless-agent user is empowered enough to deploy: [code block] Right now, I'm focused on a single policy that can deploy to all stages. But some enterprises may need this IAM policy to allow dev and staging deployments, but limit who can deploy to production. So, I've also been experimenting with adding "${stage}" to some of the resource ARNs, but don't have it fully worked out yet. For example: [code block] There are still a few places where the permissions could be narrowed further. Specifically, the REST API section allows delete of ALL apis right now. And the lambda permissions are too broad. But I’ve had some annoying technical issues trying to narrow those two sections. The API Gateway policy is still broad because you must have the 'api-id' in the ARN. But you don't know that until a deployment generates it. So on the surface, seems like a chicken/egg problem to me, but maybe there is a way to supply that api-id, instead of having AWS generate it. And the lambda permissions are still broad because I can't see the particular Arn it is trying to manipulate to add an event mapping to a lambda, and the obvious ARNs don't work. Maybe there is a way to show the ARN being accessed in serverless, when the deployment fails so that I can add it to th
Allow enums of types other than number
I'm reopening this issue, because it was closed with the move from codeplex, and doesn't seem to have been re-opened. https://typescript.codeplex.com/workitem/1217 I feel like this is very important for a scripting language.-- Especially for objects that are passed back and forth over web service calls.-- People generally don't use integer based enums in json objects that are sent over the wire, which limits the usefulness of the current enum implementation quite a bit. I would like to re-propose the original contributor's suggestions verbatim.