All Issues
24,993 verified issues
Consider re-licensing to AL v2.0, as RocksDB has just done
Hi there, The Apache Software Foundation Legal Affairs Committee [has announced][1] that the so-called 'Facebook BSD+Patents License' is no longer allowed to be used as a direct dependency in Apache projects. This has lead to a lot of upset and frustration in the Apache community, especially from projects requiring similarly-licensed code as direct dependencies - the chief of these being RocksDB. However, we (the Apache Software Foundation) have just received word that [RocksDB will be re-licensing their code under the dual Apache License v2.0 and GPL 2 licenses][2]. As a user of React.JS in an ASF top-level project (Apache CouchDB), please consider re-licensing React.JS under similar terms. Otherwise, many ASF projects such as our own will have to stop relying on and building with React. A previous bug (#9760) suggested I mention @lacker in this issue when asking licensing questions, so I'm doing so. Thank you kindly for your consideration. [1]: https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088663&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088663 [2]: https://issues.apache.org/jira/browse/LEGAL-303?focusedCommentId=16088730&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16088730
Create Ansible provisioner
I'd like to use Terraform to build infrastructure then configure it with Ansible, similar to the Chef provisioner.
Getting 'Cross-Origin Request Blocked' on a GET request
Summary I'm making a GET request to 4chan's API for retrieving threads from a board. This is my code: [code block] I receive the following warning: `Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://a.4cdn.org/a/threads.json. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). ` As seen above, I have added the relevant header, but it does not solve the issue. I made the same request from my terminal using cURL and it worked fine. Context - axios version: e.g.: v0.16.0 - Environment: e.g.: node v6.9.4, Firefox 51.0.1, Ubuntu 14.04
Duplicate type declarations with npm link
Using TypeScript 1.7.3. Suppose I have the below npm packages. The declaration files are generated by TypeScript compiler, and referred to from the other packages by means of the way described here. package-a ts src: [code block] ts declaration: [code block] package-b (depends on package-a): ts src: [code block] ts declaration: [code block] package-c (depends on package-a and package-b): ts src: [code block] The last line causes an error during compilation: [code block] When I remove the line `private foo;` from the declaration of package-a, TypeScript does not emit any error. However this workaround is a bit painful. I understand that exposing private properties to declaration is by design (https://github.com/Microsoft/TypeScript/issues/1532). I think TypeScript should ignore private properties when compiling variable assignment. Or is there any better workaround for this?
React 16 RC
The third React 16 RC is now available for public testing. 🎉 Installation Instructions The RC has been published to NPM with the tag "next". Regular NPM installs will continue to use the 15.6 release. To install the RC use: [code block] Or: [code block] What Does React 16 Mean for You? React 16 is the first release that ships with a rewrite of the React core (previously codenamed “Fiber”). This rewrite had a few goals: Remove old internal abstractions that didn’t age well and hindered internal changes. Let us ship some of the most requested features like returning arrays from render, recovering from component errors, and readable component stack traces for every error. Enable us to start experimenting with asynchronous rendering of components for better perceived performance. This initial React 16.0 release is mostly focused on compatibility with existing apps. It does not enable asynchronous rendering yet. We will introduce an opt-in to the async mode later during React 16.x. We don’t expect React 16.0 to make your apps significantly faster or slower, but we’d love to know if you see improvements or regressions. JavaScript Environment Requirements React 16 depends on the collection types Map and Set. If you support older browsers and devices which may not yet provide these natively (eg <IE11), consider including a global polyfill in your bundled application, such as core-js or babel-polyfill. A polyfilled environment for React 16 using core-js to support olde
Error during WebSocket handshake: Unexpected response code: 400
Can't find out a solution, I get this error on the browser console: WebSocket connection to 'ws://.../socket.io/?EIO=2&transport=websocket&sid=p3af7ZNfvogtq6tAAAG0' failed: Error during WebSocket handshake: Unexpected response code: 400. Hava any advice ?
Is there a way to delay container startup to support dependant services with a longer startup time
I have a MySQL container that takes a little time to start up as it needs to import data. I have an Alfresco container that depends upon the MySQL container. At the moment, when I use fig, the Alfresco service inside the Alfresco container fails when it attempts to connect to the MySQL container... ostensibly because the MySQL service is not yet listening. Is there a way to handle this kind of issue in Fig?
Glob based configuration
Glob based configuration Goal Currently ESLint allows you to cascade the configurations based on the directory structure of your project. This approach is not flexible enough if you have files that don’t share the same parent directory but you still want to have a specific ESLint configuration just for those files. This could be solved by specifying a configuration that applies to all files which match a given glob pattern. How it works - The glob patterns can be configured within `.eslintrc` files - glob patterns are relative to the location of the `.eslintrc` in which they are defined - if an already resolved file matches a glob pattern in one of its corresponding `.eslintrc` files, the glob pattern specific configuration will be applied - a glob pattern based configuration has a higher precedence than the regular configuration in the same `.eslintrc` file - A glob specific configuration works exactly the same as the regular configuration in your `.eslintrc`, except that you can’t define nested glob based configurations. That means you can configure `globals`, `env`, `ecmaFeatures`, `rules`, `plugins`, `extends` and `parser`. Note: The glob patterns are NOT used for file resolving / directory traversal. Example for relative glob patterns Given the following directory tree: [code block] The config in `app/.eslintrc` defines the glob pattern `*/Spec.js`. This pattern is relative to the base directory of `app/.eslintrc`. So, this pattern would match `app/lib/fooSpec.js`
http://socket.io website is down
http://socket.io website is down. Many people on social network are reporting the same.
docker-compose up doesn't pull down latest image if the image exists locally
It would be nice if there were an option to check for new versions of images when running `docker-compose up`. We already have this functionality with `docker build --pull` as was discussed here https://github.com/docker/docker/issues/4238 and there is an open issue to bring `--pull` to `docker run` here https://github.com/docker/docker/issues/13331. I propose adding `--pull` to `up` to always attempt to pull a newer version of the images in the compose file.
No bundle url present
Description I noticed some people recently asking about this "No bundle url present" error and I just faced it myself. Reproduction I had just run ˜react-native init projectName˜, setup my App.js file (a simple Hello World), called it in both iOS and Android indexes and run ˜react-native run-ios˜. Then the No bundle url present error appeared. Solution I tried to delete my node_modules and npm install, close the packager and run the project again, but it could only be solved when I follow the steps given here (http://stackoverflow.com/questions/42610070/what-means-of-no-bundle-url-present-in-react-native). Run "react-native run-ios" When the error appears, run "npm install" * Then run "react-native run-ios" again. Additional Information This is the first project I started using RN 0.42. Since it never happened before and I am not the only one facing this issue, I guess it should be taken a closer look to it. Here's my package.json: [code block] If I can be more helpful to make any further test, it would be a pleasure.
Add fragment API to allow returning multiple components from render
--- Note from maintainers: We know this is an issue and we know exactly what set of problem can be solved. We want this too but it is a _hard problem_ with our current architecture. Additional comments expressing desire for this feature are not helpful. Feel free to subscribe to the issue (there's button in the right hand column) but do not comment unless you are adding value to the discussion. "Me too" and "+1" are not valuable, nor are use cases that have already been written in the comments (e.g., we know that you can't put `<tr>` or `<dd>` elements with a `<div>`). --- Consider the following: [code block] If you remove the `<div></div>` in the `map`, you get the following error: _Adjacent XJS elements must be wrapped in an enclosing tag_ it isn't till I re-add the surrounding, and rather pointless, divs that it compiles with out issue. I am running 0.11.1 Is this being addressed? It adds extra, and again - IMO - useless and pointless html to the page, that while harming nothing - looks messy and unprofessional. Maybe I am just doing something wrong, please enlighten me if I am.
Allow configuring remote storage via config file
https://www.terraform.io/docs/commands/remote-config.html It's ok to configure storage via CLI once as one member of the team, but it's pain to do this repeatedly and to share this with team members in a form of a Readme file suggesting "do the following": [code block]
terraform get: can't use variable in module source parameter?
I'm trying to avoid hard-coding module sources; the simplest approach would be: [code block] The result I get while attempting to run `terraform get -update` is [code block]
Status bar background color
The blue color is very distracting.. a way to change the color of that would be great! <img src="http://content.screencast.com/users/joe-watkins-emerge/folders/Snagit/media/412cd601-ba5d-4ccf-a0b5-25bc36237ff0/2016-01-08_10-14-31.png">
Vscode New logo
- VSCode Version:1.17.0 - OS Version:windows 10 X64 15063.632 Steps to Reproduce: new logo put into the start menu is ugly！
Feature request: Assume role with EC2 instance profile as the source profile
Right now you can execute commands using credentials from one of these sources: root credentials, IAM credentials, temporary credentials from an EC2 instance profile, and temporary credentials from assuming a role via IAM credentials. I would like to execute commands by using temporary credentials from assuming a role via the EC2 instance profile. I need this ability because I'm using two AWS accounts and I'm using an EC2 instance to run AWS CLI commands against both accounts. The EC2 instance profile allows me to perform tasks for one account, but I need to assume a cross-account role to perform tasks for the other account. Unfortunately there is no way to get AWS CLI to assume the cross-account role even though the EC2 instance profile has permissions to assume that role. I tried removing the source_profile property from my role-based profile in hopes that the source_profile would use the instance profile, but that failed. After looking at AssumeRoleProvider in awscli/customizations/assumerole.py, I see that AWS CLI can only assume a role if the source profile has actual credentials in the config file. So currently that excludes any use of an instance profile to assume a different role.
Git status in File Explorer
Similar to what atom provides in the project explorer: 1. New files are displayed green. 2. Modified are displayed yellow/orange. 3. Ignored files are displayed transparent-ish. Thanks
Setting a timer for a long period of time, i.e. multiple minutes
I want to use firebase auth with react native for Login and Signup but I got a yellow error: Setting a timer for a long period of time, i.e. multiple minutes, is a performance and correctness issue on Android as it keeps the timer module awake, and timers can only be called when the app is in the foreground. See (https://github.com/facebook/react-native/issues/12981) for more info. (Saw setTimeout with duration 111862ms) How Can I Fix That? I don't want to ignore that, I want to understand this error and solve that with the best and Standard way. And This is my Code: [code block] I Asked From Stackoverflow too, Link
Top-level app component and animated route transitions
Having animated route transitions would be nice, as this is one of the many benefits through client-side routing. Doing so should be left up to the user in my opinion (some people prefer CSS transitions over more fine-grained control with `react-motion` etc). As I understand it, one would need to modify the top-level App component. The client entry file seems to look for a globally assigned `__NEXT_DATA__.app` variable but I can't find any documentation on that.