flowbased / fbp-protocol-client Goto Github PK
View Code? Open in Web Editor NEWJavaScript client library for FBP protocol connection handling
fbp-protocol-client's People
Contributors
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
![greenkeeper[bot] avatar](https://avatars.githubusercontent.com/in/505?v=4 "greenkeeper[bot]")
Stargazers
Watchers
fbp-protocol-client's Issues
An in-range update of microflo is breaking the build π¨
Version 0.3.55 of microflo just got published.
| Branch | Build failing π¨ |
|---|---|
| Dependency | microflo |
| Current Version | 0.3.54 |
| Type | optionalDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As microflo is βonlyβ a optionalDependency 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 12 commits.
18e7591Bumpe411576NPM: Don't include removed files30323dcTravis: Don't try to upload .zip to GH releasesf5ea51fTivaC: Remove some leftover stellaris files41c7111microflo flash: Removeedeec26Remove unused MIDI git submoduled49608bMerge pull request #125 from microflo/greenkeeper/grunt-contrib-uglify-3.0.03c02049Merge pull request #131 from microflo/greenkeeper/chai-4.0.1f54ed86Ardino: Remove (patched) libraries for componentsb0ef3bcMakefile: Remove unused OSX compatac7972dchore(package): update chai to version 4.0.1688e440chore(package): update grunt-contrib-uglify to version 3.0.0
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 π΄
WebRTC not working in mocha phantomjs
Cause of limitations in PhantomJS.
Need to use Chromium or Firefox based tests to get this to pass. Karma is one runner which might be suitable for use on Travis CI.
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 | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
coffee-script 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 15 commits.
492111cBump date677312aMore betterc83c47dDisable regex Unicode test for runtimes lacking support. Fixes #4610.7b0ea20Updated output9990771Improve formatting019ebcfUpdate dependencies0d9ce2c1.12.7: Update changelog and version number799bc6eRestrict indented return arg to object (#4605)e4bf163refine sameLine implicit object tagging [Fixes #4568] (#4598)9d82bf7Add more features to the list of reasons to check out CoffeeScript 2ebe8493Update v2 docs for 2.0.0-beta3b1b34d3Merge pull request #4585 from helixbass/iss4283_error_message_implicit_call8234ce2error message for implicit call [Fixes #4283]48c7debFix REPL assignment (#4559)cd6daf02.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 π΄
Add spec/schema for the runtime definition format
We rely on a standard format for runtime information in the client (typically serialized as JSON)
label: "MicroFlo Simulator"
description: "The first component in the world"
type: "microflo"
protocol: "websocket"
address: "ws://localhost:3333"
secret: "microflo32"
id: "2ef763ff-1f28-49b8-b58f-5c6a5c23af2d"
user: "3f3a8187-0931-4611-8963-239c0dff1931"
This is used also when registering with Flowhub, and is proposed to use in fbp-spec and fbp-protocol tester for runtime information.
An in-range update of mocha is breaking the build π¨
Version 3.5.0 of mocha just got published.
| Branch | Build failing π¨ |
|---|---|
| Dependency | mocha |
| Current Version | 3.4.2 |
| 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
free-as-in-freezing3.5.0 / 2017-07-31
π° News
- Mocha now has a code of conduct (thanks @kungapal!).
- Old issues and PRs are now being marked "stale" by Probot's "Stale" plugin. If an issue is marked as such, and you would like to see it remain open, simply add a new comment to the ticket or PR.
- WARNING: Support for non-ES5-compliant environments will be dropped starting with version 4.0.0 of Mocha!
π Security Fixes
- #2860: Address CVE-2015-8315 via upgrade of debug (@boneskull)
π Enhancements
- #2696: Add
--forbid-onlyand--forbid-pendingflags. Use these in CI or hooks to ensure tests aren't accidentally being skipped! (@charlierudolph) - #2813: Support Node.js 8's
--napi-modulesflag (@jupp0r)
π© Other
- Various CI-and-test-related fixes and improvements (@boneskull, @dasilvacontin, @PopradiArpad, @Munter, @ScottFreeCode)
- "Officially" support Node.js 8 (@elergy)
Commits
The new version differs by 34 commits.
82d879fRelease v3.5.0bf687ceupdate mocha.js for v3.5.0ec73c9aupdate date for release of v3.5.0 in CHANGELOG [ci skip]1ba2cfcupdate CHANGELOG.md for v3.5.0 [ci skip]065e14eremove custom install script from travis (no longer needed)4e87046update karma-sauce-launcher URL for npm@56886cccincrease timeout for slow-grepping test2408d90Make dependencies use older version of readable-stream to work around incompatibilities introduced by 2.3.0 on June 19th68a1466Try not clearing the env for debug in the integration test and see if that fixes Node 0.10 on AppVeyor; if need be, some other fix/workaround can be applied to handle whatever was up with debug without causing this issue958fbb4Update new tests to work in browser per test hierarchy reorganization1df7c94Merge pull request #2704 from seppevs/increase_test_coverage_of_mocha_js1f270cdStop timing out (#2889)27c7496upgrade to [email protected]; closes #2859 (#2860)50fc47dfix CI; closes #2867 (#2868)1b1377cAdd test for ignoreLeaks and fix descriptions
There are 34 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 π΄
An in-range update of websocket is breaking the build π¨
The dependency websocket was updated from 1.0.28 to 1.0.29.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
websocket is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- β continuous-integration/travis-ci/push: The Travis CI build failed (Details).
Commits
The new version differs by 6 commits.
6e62787Bumping version and updating readme.0335951Updating dependencies and .ignore files3cb29e1Fix gulp dependency version (git URL no longer required as 4.0.2 is already published)e109ba6Include .git/ into .npmignore (fix #353)58f301aMerge pull request #325 from felixrieseberg/patch-14b593f8docs: Add windows-build-tools for Windows users
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 coffeescript is breaking the build π¨
The devDependency coffeescript was updated from 2.3.2 to 2.4.0.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
coffeescript 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 11 commits.
e6f6aa8Version bump in lockfilec09d8fbRelease 2.4.0 (#5182)f6d6377ES module version of compiler for use in browsers; dynamic import() docs; revised Stage 3 policy (#5177)41b31c7Fix repl.rli deprecation (#5178)ec034e2Fix tests (#5176)ff24e5cDynamic import (#5169)ca275c2Fix #5128: parens around default param (#5167)63ffe0aFix 5085 (#5145)247b511Remove extra word in comment in src/nodes.coffee (#5158)2f82b75implement coffeescript.registerCompiled method (#5130)294bb47Fix #5112: A string of ', ' in an array should not be detected as an elision (#5113)
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 π΄
Build is broken because of microflo-emscripten
Should switch to the grunt-noflo-browser 1.x series to use Webpack instead of Component.io
warning: failed to fetch https://raw.githubusercontent.com/microflo/microflo-emscripten/master/dist/microflo-runtime.js, got 404 "Not Found"οΏ½
Same issue as in noflo/noflo-runtime#84
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.
14be62bMerge pull request #203 from gruntjs/v21066dda8cv2.1.06879d8fMerge pull request #202 from gruntjs/upt-deps-a93768c5Fix tests for latest coffeescript7d5b1c5Update deps within delclared range14315b4Merge pull request #201 from gruntjs/upt-depsd211122Drop Node 6 in CI, add node 100681fc7Update 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-core is breaking the build π¨
The devDependency noflo-core was updated from 0.5.0 to 0.6.0.
π¨ View failing branch.
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 41 commits.
2a0a23fRelease 0.6.047ad50cMerge pull request #128 from noflo/update_eslint1662300Adapt eslint rules for mocha testse64d60eUpdate eslint8fb84c9chore(package): update eslint to version 5.0.17443f82chore(package): update eslint-config-airbnb-base to version 13.0.0db433d9Merge pull request #124 from noflo/greenkeeper/nyc-12.0.1cff01d5chore(package): update nyc to version 12.0.11494dcbAdd changelogc1250f8Merge pull request #125 from noflo/decafec50169Clean up the specsba63c6aRun without browser tests for the while56e2442Fix Chrome headless on Travis2857496Use Chrome from Puppeteer8f08f13Try testing with karma
There are 41 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 π΄
Run checks against protocol schemas
There now exists some JSON schemas which formally describes the protocol, at https://github.com/flowbased/fbp-protocol
We should make it hard to do things which are incompatible/wrong according to the protocol, so we should check both sent and received messages against the JSON schemas.
Initially there are likely incompatiblities between existing implementations and current schemas, either due to bugs in runtime/client following protocol spec, or due to bugs in the schemas. So probably the checks should not fail, but instead raise a warning.
Since the BaseRuntime is an EventEmitter already, I propose we emit a validation-error event. And that we log these warnings, so people are more likely to discover and fix them.
For forward compatibility, unknown messages (not existing in schema) should be ignored. We could emit a unknown-message, and allow to opt-in to log these.
WebDriver transport
Would allow to connect to a runtime in any browser supporting WebDriver. Including hosted by a service like Saucelabs.
Could use executeScriptAsync as the base: http://selenium.googlecode.com/svn/trunk/docs/api/java/org/openqa/selenium/JavascriptExecutor.html
For instance via https://github.com/admc/wd
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.
8fcbed1v1.0.4 (#1668)0b13970Update js-yaml to address https://npmjs.com/advisories/788 (#1667)7db6cf7Use SOURCE_DATE_EPOCH to render dates in template. (#1596)a2d6d80Revert "Indicate in package.json that Node.js 4 or newer is required (#1643)" (#1644)773b7e7Indicate 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 π΄
Support node.js for WebRTC
Could be used to run fbp-spec tests from CLI against NoFlo browser.
With noflo/noflo-runtime-webrtc#1 could also be used against node.js as alternative to WebSockets.
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.
e490d54Bumpc1910a0Update CHANGES6721dcfMerge pull request #548 from noflo/send_iips_on_finished_network25d9158Add test to ensure IIP changes don't re-start network after a stop()efbeff9Mark network as stopped also when it was finished and stop() is called5e99b5fAllow execution to restart on IIP changes unless network was explicitly stopped41d1ebaCheck the start event again as wellc4970b5Red test for re-activating network when new IIP is registered5a52790Scope the graph to each test caseb6b1a0bAdd a simple IIP testccf2020Merge pull request #543 from noflo/greenkeeper/chai-4.0.061d143dFix broken assertions9c5932fchore(package): update chai to version 4.0.0f88c989Link to https072d033Add 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 π΄
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.