Coder Social home page Coder Social logo

noflo-runtime-webrtc's People

Contributors

bergie avatar dependabot[bot] avatar greenkeeper[bot] avatar greenkeeperio-bot avatar jonnor avatar

Watchers

 avatar  avatar  avatar  avatar

Forkers

wellaged cephdon

noflo-runtime-webrtc's Issues

An in-range update of grunt is breaking the build 🚨

The devDependency grunt was updated from 1.0.3 to 1.0.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

grunt is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 5 commits.

  • 8fcbed1 v1.0.4 (#1668)
  • 0b13970 Update js-yaml to address https://npmjs.com/advisories/788 (#1667)
  • 7db6cf7 Use SOURCE_DATE_EPOCH to render dates in template. (#1596)
  • a2d6d80 Revert "Indicate in package.json that Node.js 4 or newer is required (#1643)" (#1644)
  • 773b7e7 Indicate in package.json that Node.js 4 or newer is required (#1643)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of uuid is breaking the build 🚨

Version 3.1.0 of uuid just got published.

Branch Build failing 🚨
Dependency uuid
Current Version 3.0.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

uuid is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 6 commits.

  • c50ac88 Update readme & package version (#198)
  • 082a0b3 v5 support in CLI (#197)
  • 1d56dc9 V5 support (#188)
  • f37f96a (fix) Add .npmignore file to exclude test/ and other non-essential files from packing. (#183)
  • 3b21880 Fix typo (#178)
  • d8e41bd Simple typo fix (#165)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

Version 3.4.2 of mocha just got published.

Branch Build failing 🚨
Dependency mocha
Current Version 3.4.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes fake-success

3.4.2 / 2017-05-24

🐛 Fixes

🔩 Other

Commits

The new version differs by 7 commits.

  • a15b20a :ship: Release v3.4.2
  • fc802a9 :memo: Add Changelog for v3.4.2
  • 10ff0ec Eagerly set process.exitCode (#2820)
  • fc35691 Merge pull request #2818 from makepanic/issue/2802
  • 3e7152f Remove call to deprecated os.tmpDir (#2802)
  • e249434 Merge pull request #2807 from mochajs/npm-script-lint
  • 17a1770 Move linting into an npm script. Relates to #2805

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of grunt-mocha-test is breaking the build 🚨

Version 0.13.3 of grunt-mocha-test just got published.

Branch Build failing 🚨
Dependency grunt-mocha-test
Current Version 0.13.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As grunt-mocha-test is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 4 commits.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of json-loader is breaking the build 🚨

Version 0.5.5 of json-loader just got published.

Branch Build failing 🚨
Dependency json-loader
Current Version 0.5.4
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As json-loader is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of noflo-core is breaking the build 🚨

Version 0.4.1 of noflo-core was just published.

Branch Build failing 🚨
Dependency noflo-core
Current Version 0.4.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

noflo-core is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 19 commits.

  • 21c8816 Bump
  • b6d1606 Easier bang reading
  • 9b83e7c Wait for options if attached
  • 8389787 Send the original packet
  • 3fbf924 Make scope-safe
  • 3cb316f Make scope-safe
  • dcfed64 Call done
  • 8c46eab Fix the MakeFunction component
  • 2b9b354 Update Kick tests
  • b4929e7 If we have data attached, wait for data
  • 857d5e4 Generators shouldn't forward brackets
  • 1e0335f Merge pull request #105 from noflo/greenkeeper/mocha-4.0.0
  • e6c05ae chore(package): update mocha to version 4.0.0
  • 6ebc34a Merge pull request #103 from noflo/greenkeeper/chai-4.0.0
  • 07d7da0 chore(package): update chai to version 4.0.0

There are 19 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of grunt-noflo-browser is breaking the build 🚨

Version 1.3.0 of grunt-noflo-browser just got published.

Branch Build failing 🚨
Dependency grunt-noflo-browser
Current Version 1.2.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As grunt-noflo-browser is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 14 commits.

  • d01f8b1 Update docs, refs #25
  • a7653fd Bump
  • 83d9573 Merge pull request #25 from noflo/opener_protocol
  • 8a8f257 Fix indent
  • cd150ba Provide runtime type correctly
  • 31acbd7 No need to log the debug URL, since we need to go through the button
  • 6321a65 Switch from iframe+webrtc to postmessage runtime
  • b694bb7 README: Minor doc improvements
  • 24f2afa Merge pull request #24 from noflo/greenkeeper/webpack-3.0.0
  • e8c9cce fix(package): update webpack to version 3.0.0
  • 83a6b19 Merge pull request #23 from noflo/greenkeeper/chai-4.0.0
  • d3e2bcf chore(package): update chai to version 4.0.0
  • 361e0ed Update tests for 0.8
  • 1e6ca6e Abort on parse errors

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of fbp-loader is breaking the build 🚨

Version 0.1.2 of fbp-loader was just published.

Branch Build failing 🚨
Dependency fbp-loader
Current Version 0.1.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

fbp-loader is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 13 commits.

  • f204372 Bump
  • 2f06a6d Test on modern Node.js
  • 7056173 Merge pull request #5 from flowbased/options
  • d827d3b Support passing caseSensitive as a loader option
  • 0dc2e49 Merge pull request #4 from flowbased/greenkeeper/webpack-3.0.0
  • e225af2 chore(package): update webpack to version 3.0.0
  • 016a8b0 Merge pull request #3 from flowbased/greenkeeper/initial
  • e52823c Fix badges
  • 10db592 docs(readme): add Greenkeeper badge
  • eab6a02 Merge pull request #2 from flowbased/greenkeeper-webpack-2.2.1
  • 0a0fba9 Fix resolving path for local fbp-loader
  • 8456bf8 chore(package): update webpack to version 2.2.1
  • 1d6a0ea Remove trailing comma

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of coffee-script is breaking the build 🚨

Version 1.12.7 of coffee-script just got published.

Branch Build failing 🚨
Dependency coffee-script
Current Version 1.12.6
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As coffee-script is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 15 commits.

  • 492111c Bump date
  • 677312a More better
  • c83c47d Disable regex Unicode test for runtimes lacking support. Fixes #4610.
  • 7b0ea20 Updated output
  • 9990771 Improve formatting
  • 019ebcf Update dependencies
  • 0d9ce2c 1.12.7: Update changelog and version number
  • 799bc6e Restrict indented return arg to object (#4605)
  • e4bf163 refine sameLine implicit object tagging [Fixes #4568] (#4598)
  • 9d82bf7 Add more features to the list of reasons to check out CoffeeScript 2
  • ebe8493 Update v2 docs for 2.0.0-beta3
  • b1b34d3 Merge pull request #4585 from helixbass/iss4283_error_message_implicit_call
  • 8234ce2 error message for implicit call [Fixes #4283]
  • 48c7deb Fix REPL assignment (#4559)
  • cd6daf0 2.0.0-beta2 docs

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of peerjs is breaking the build 🚨

Version 0.3.14 of peerjs just got published.

Branch Build failing 🚨
Dependency peerjs
Current Version 0.3.13
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

peerjs is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of grunt-contrib-coffee is breaking the build 🚨

The devDependency grunt-contrib-coffee was updated from 2.0.0 to 2.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

grunt-contrib-coffee is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 8 commits.

  • 14be62b Merge pull request #203 from gruntjs/v210
  • 66dda8c v2.1.0
  • 6879d8f Merge pull request #202 from gruntjs/upt-deps-a
  • 93768c5 Fix tests for latest coffeescript
  • 7d5b1c5 Update deps within delclared range
  • 14315b4 Merge pull request #201 from gruntjs/upt-deps
  • d211122 Drop Node 6 in CI, add node 10
  • 0681fc7 Update dependencies

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of noflo is breaking the build 🚨

Version 0.8.4 of noflo just got published.

Branch Build failing 🚨
Dependency noflo
Current Version 0.8.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As noflo is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 15 commits.

  • e490d54 Bump
  • c1910a0 Update CHANGES
  • 6721dcf Merge pull request #548 from noflo/send_iips_on_finished_network
  • 25d9158 Add test to ensure IIP changes don't re-start network after a stop()
  • efbeff9 Mark network as stopped also when it was finished and stop() is called
  • 5e99b5f Allow execution to restart on IIP changes unless network was explicitly stopped
  • 41d1eba Check the start event again as well
  • c4970b5 Red test for re-activating network when new IIP is registered
  • 5a52790 Scope the graph to each test case
  • b6b1a0b Add a simple IIP test
  • ccf2020 Merge pull request #543 from noflo/greenkeeper/chai-4.0.0
  • 61d143d Fix broken assertions
  • 9c5932f chore(package): update chai to version 4.0.0
  • f88c989 Link to https
  • 072d033 Add a test for falsy output

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of noflo-runtime-base is breaking the build 🚨

Version 0.8.4 of noflo-runtime-base just got published.

Branch Build failing 🚨
Dependency noflo-runtime-base
Current Version 0.8.3
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

noflo-runtime-base is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 18 commits.

  • 303b177 Bump
  • 5b4a086 Merge pull request #95 from noflo/schema_support
  • aa06678 Provide schema for runtime exported ports, if available
  • 4186bcc Provide type and schema for network data events, refs flowbased/fbp-protocol#50
  • 272194f Send schema on component ports when available, refs flowbased/fbp-protocol#50
  • 3f71486 Merge pull request #92 from noflo/ports_api
  • 4698c19 Emit ports the same time as we send ports to FBP protocol client
  • c0b8665 Runtime: Use internal portname when looking up on component
  • 86f2ab1 Rename receivePacke to sendPacket
  • 4b31fb9 Read port metadata from component when available
  • 8c86f2d Export a more sensible outport
  • f4a1558 Add tests for runtime ports JS API
  • 2d298d4 Fix sending of ports
  • 26083b0 Make runtime ports/packets accessible in JS
  • c4a13b0 Merge pull request #91 from noflo/greenkeeper/debug-3.0.0

There are 18 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.