Essential components for NoFlo
- 0.6.1 (December 27th 2018)
- Fixed an issue where
RunInterval
wouldn't deactivate when stopped
- Fixed an issue where
- 0.6.0 (December 7th 2018)
- Ported the library from CoffeeScript to ES6
Core components for NoFlo
Branch | Build failing π¨ |
---|---|
Dependency | coveralls |
Current Version | 3.0.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
coveralls 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.
Maintenance:
The new version differs by 9 commits.
e7ae2bf
version bump; logger test fix
9b892bf
Verbose use log level debug
9cfb496
Add buildkite support (#177)
aa8c257
Done callback waits for unlink in testRepoTokenDetection to prevent race condition (#179)
18c71c2
Fix a mistype in tests: fs.exists -> fs.existsSync (#184)
bd667c6
Add Semaphore support (#180)
10d8b3e
Update examples to include Jest (#183)
720ee7c
Add license (#175)
83ff2cb
Add mention about AppVeyor to the README (#164)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
The try {@f(true) ... } catch (e) { blow_up() } block doesnt work for any function that throws an exception when passed true... if this is by design, a note in the documentation somewhere would have saved a few hours of head scratching. it also swallows the details of the exception which I most definitely want to see!
Branch | Build failing π¨ |
---|---|
Dependency | grunt-contrib-uglify |
Current Version | 2.2.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As grunt-contrib-uglify 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 πͺ
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency | coffeescript |
Current Version | 2.2.4 |
Type | devDependency |
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.
The new version differs by 8 commits.
8061ecf
2.3.0 (#5043)
6df8f5f
Remove references to Node's experimental modules support
776e7e5
Docs improvements (#5042)
871079b
Fix #4876: remove polyfill for object rest/spread (#4884)
be2b243
Fix: a test relied on faulty behavior (#5028)
1f9cd4e
Fix #4875: Asynchronous iterators (#4893)
47c491f
Regular expressions s
(dotAll) flag (#4880)
195a46a
Fix #4877: Exponentiation operators (#4881)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
This means that NoFlo thinks the network is not running. If using noflo-nodejs --batch with this, the network and program will just shut down immediately when the in
packet has been delivered,
instead of waiting for the Timer to fire and sending on out
.
This problem exists both in 0.2.x and 0.3.x.
4.35.3
to 4.36.0
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
webpack 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.
append
option now supports the default placeholders in addition to [url]
"..."
when overriding options.The new version differs by 42 commits.
95d21bb
4.36.0
aa1216c
Merge pull request #9422 from webpack/feature/dot-dot-dot-merge
b3ec775
improve merging of resolve and parsing options
53a5ae2
Merge pull request #9419 from vankop/remove-valid-jsdoc-rule
ab75240
Merge pull request #9413 from webpack/dependabot/npm_and_yarn/ajv-6.10.2
0bdabf4
Merge pull request #9418 from webpack/dependabot/npm_and_yarn/eslint-plugin-jsdoc-15.5.2
f207cdc
remove valid jsdoc rule in favour of eslint-plugin-jsdoc
31333a6
chore(deps-dev): bump eslint-plugin-jsdoc from 15.3.9 to 15.5.2
036adf0
Merge pull request #9417 from webpack/dependabot/npm_and_yarn/eslint-plugin-jest-22.8.0
37d4480
Merge pull request #9411 from webpack/dependabot/npm_and_yarn/simple-git-1.121.0
ce2a183
chore(deps-dev): bump eslint-plugin-jest from 22.7.2 to 22.8.0
0beeb7e
Merge pull request #9391 from vankop/create-hash-typescript
bf1a24a
#9391 resolve super call discussion
bd7d95b
#9391 resolve discussions, AbstractMethodError
4190638
chore(deps): bump ajv from 6.10.1 to 6.10.2
There are 42 commits in total.
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency | noflo |
Current Version | 0.7.9 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As noflo 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 πͺ
The new version differs by 325 commits (ahead by 325, behind by 2).
a1187c6
Bump
d1c13f2
Update Flowhub docs link
49cfb8b
Update fbp-protocol link
b25001e
Update MsgFlo link
9757b8d
Merge pull request #534 from noflo/update_copyrights
f84ca06
Reassign copyrights
a790ba4
Make 'grunt test' run the build task instead of duplicating
593a39d
Bump
05d38ad
Document WirePattern Process API changes, refs #526
452c57f
Merge pull request #526 from noflo/process_wirepattern
6ceab6f
Merge pull request #532 from noflo/fix_null_undefined
efaba77
Fix ip.data turned from null to undefined
76d10c6
Provide postpone/resume functions that throw a more user-friendly error
4db7e7b
Plug deprecation warnings back in
9d15d3c
Collation support for WirePattern group and field options in Process API
There are 250 commits in total. See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency |
nyc
|
Current Version | 11.7.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
nyc 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.
The new version differs by 6 commits.
4bdd42c
chore(release): 11.7.2
bd77538
test: cache clear was breaking build (#835)
a522dd9
chore: add Node.js 8 and 10, remove Node.js 4 (#829)
99576fb
chore: clone only last commit (#831)
ef550bf
docs: added "temp-directory" to configuring nyc (#828)
d76744a
chore: update all the things (#832)
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Not attached output ports are kind of a problem right now, because they pretty much stop your application when throwing an exception.
Non attached ports can be part of one's development/debug workflow.
Is there a plan to check for the attach state in the components or switch to the 0.5 port API to get rid of these?
Branch | Build failing π¨ |
---|---|
Dependency | noflo |
Current Version | 1.0.0 |
Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
noflo 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.
The new version differs by 42 commits.
d0b907a
Bump
966fe0f
Document babel drop
5312c13
Merge pull request #580 from noflo/setsource_tests
bdcd27f
Bump grunt-noflo-browser dep
efa896d
Add test loading non-existing module
dfe346a
Add test for setting source using deprecated API
5a6273b
Catch component loading failures
5ec0016
Add test with component without exported interface
23d6acc
Include CoffeeScript compiler in the browser test runner
b4b2bdc
Skip CoffeeScript setSource test on browser if there is no CoffeeScript compiler available
5817a12
Re-enable setSource tests for browser
6c24672
Add ES6 setSource test
d15a9e4
No need to Babelize ES6 on modern Node.js that we require now
1ae96be
Add CoffeeScript setSource test
931d46c
actually run the set component
There are 42 commits in total.
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
It correctly sends the result from the function to the out port, but there is never a disconnect. Conversion to WirePattern will help resolve this issue.
Quick function maker, for example return Math.sin(x);
Hi,
I am following the MsgFlo tutorial and the core/Output component does not print the message on console, even though it receives it.
I did some debugging at it looks like the component receives the IP, but returns at Output.js:36 at the statement:
if (input.attached('options').length && !input.hasData('options')) { return; }
The line was added in 9b83e7c.
I don't really understand what the purpose of this line is.
Debugging information is:
noflo-runtime-msgflo:newrelic Transaction.open 1 +1s
noflo:component null port 'in' entered auto-ordering mode +0ms
noflo:component null packet on 'in' didn't match preconditions: data +3ms
noflo:component null packet on 'in' didn't match preconditions: closeBracket +1ms
I also printed out the IP buffer as it is at component level, and there are both opening and cloing bracket IPs present. Reading the error messages, it seems that the IPs did not cause the component to activate.
Also only one message gets delivered. When I restart the component, the next one gets delivered. Does it not acknowledge the messages?
Does anyone has an idea what is going on?
Hello,
As a beginner in the NoFlo world of things, even after reading the docs paragraph "Ports and events" and the Group component page I still don't understand what a Group is for... Could you add a description ? And maybe clarify the docs about them ? Maybe we need a graph to understand what a group is :)
Hello,
As a beginner in the NoFlo world of things, even after reading the docs paragraph "Ports and events" and the Group component page I still don't understand what a Group is for... Could you add a description ? And maybe clarify the docs about them ? Maybe we need a graph to understand what a group is :)
3.3.4
to 3.3.5
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
webpack-cli 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.
Webpack-CLI v3.3.5 has a patch to remove the donation banner that causes some irritation around donations to webpack and for windows users. We've removed this and a full changelog is found here
The new version differs by 16 commits.
30b1b8d
chore: v3.3.5
76b75ac
chore: remove donation section
8913928
chore: update pkg lock
a37477d
cli: remove donation prompt
002a6ac
Merge pull request #970 from dhruvdutt/postinstall
cd54ba5
chore(scripts): clean opencollective
0c1f6b6
chore(scripts): clean postinstall
313e83e
chore(deps): update major versions (#969)
6105ef1
fix(deps): move prettier from dependencies to devDependencies (#968)
dad54f4
chore(ts): enables source map in the ts (#961)
d7cdab9
Merge pull request #960 from DanielRuf/fix/use-strict
6015bad
chore: added await in order to resolve the pending promise (#948)
670efc7
fix: change "usr strict" to "use strict"
dc25beb
Merge pull request #959 from webpack/fix/deps
69f364e
fix: update deps
There are 16 commits in total.
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
see: https://github.com/noflo/noflo-core/blob/master/components/Group.coffee#L41
The @groups
member is never actually used in this component. Should this be re-initializing @newGroups
instead?
Branch | Build failing π¨ |
---|---|
Dependency | grunt-noflo-browser |
Current Version | 1.3.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
grunt-noflo-browser 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.
The new version differs by 8 commits.
49cbe83
Bump
f6ac38e
Merge pull request #30 from noflo/noflo_component_loader
9935b00
Try to match also Windows paths with regexp
c188098
Bump noflo-component-loader dep
84cec54
Update to legacy-free component versions
821de79
Test on modern Node.js
ea16584
Use noflo-component-loader to build the loader
f00089b
Remove obsolete grunt-noflo-manifest
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency | noflo-nodejs |
Current Version | 0.7.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As noflo-nodejs 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 πͺ
The new version differs by 40 commits .
0862625
Update deploy token
68acfa5
Bump
bb0febb
Merge pull request #108 from noflo/greenkeeper/noflo-0.8.0
a53b838
Update noflo-runtime-websocket
daba6d3
fix(package): update noflo-runtime-websocket to version 0.8.0
bc980e8
Update fbp-protocol
466f815
Update noflo-runtime-base
28958a2
fix(package): update noflo-runtime-base to version 0.8.1
0b3d74c
Update noflo-core
a267845
Merge remote-tracking branch 'origin/greenkeeper/noflo-runtime-base-0.8.0' into greenkeeper/noflo-0.8.0
b07d13f
fix(package): update noflo-runtime-base to version 0.8.0
b94f99f
fix(package): update noflo to version 0.8.0
9959355
Merge pull request #104 from noflo/greenkeeper-flowhub-registry-0.1.0
7dc1480
chore(package): update flowhub-registry to version 0.1.0
2aed272
Merge pull request #84 from noflo/greenkeeper-password-maker-1.1.3
There are 40 commits in total. See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
Branch | Build failing π¨ |
---|---|
Dependency |
grunt-contrib-watch
|
Current Version | 1.0.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
grunt-contrib-watch 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.
The new version differs by 4 commits.
3b7ddf4
v1.1.0
72b1214
Updating dependencies, async, lodash and tiny-lr
5adb27c
Merge pull request #543 from digitalbazaar/master
f07311b
Update tiny-lr dependency to 1.x
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
Per the conversation at noflo/noflo-ui#9 , I think that there should be a start
inport, instead of starting when the interval
IIP hits. This will make it easier to stop / start the interval from the UI.
This will break the clock example, so need to add a Kick component.
Branch | Build failing π¨ |
---|---|
Dependency |
mocha
|
Current Version | 5.1.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
mocha 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.
mocha.opts
(@plroebuck)before
hooks when using --bail
(@outsideris)Buffer.from()
(@harrysarson)The new version differs by 30 commits.
5bd33a0
Release v5.2.0
0a5604f
reformat missed files
7c8f551
ensure scripts/*.js gets prettiered
d8ea2ba
update CHANGELOG.md for v5.2.0 [ci skip]
7203ed7
update all dependencies
fb5393b
migrate Mocha's tests to Unexpected assertion library (#3343)
fae9af2
docs(docs/index.md): Update "mocha.opts" documentation
9d9e6c6
feat(bin/options.js): Add support for comment lines in "mocha.opts"
e0306ff
fix busted lint-staged config
f2be6d4
Annotate when exceptions are caught but ignored; closes #3354 (#3356)
889e681
remove dead code in bin/_mocha
8712b95
fix(ocd): re-order Node.js tests in .travis.yml (descending)
3ab0e7e
fix to exit correctly when using bail flag
d87b12e
add Node.js v10 to build; fix win32 issues (#3350)
b392af5
update package-lock.json for npm@6 [ci skip]
There are 30 commits in total.
See the full diff
There is a collection of frequently asked questions. If those donβt help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot π΄
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.