Closed greenkeeper[bot] closed 7 years ago
Update to this version instead š
The new version differs by 26 commits .
5b31b4c
Bump release
97be913
Mention asCallback in the changelog
4a6be4d
Merge pull request #538 from noflo/as_callback
513a72a
Add file header
ffa4454
Get baseDir from loader if passed
84c4242
Support for portmap sequences like in fbp-spec
e134208
Add test for concurrent runs
90f3031
Add support for the raw option
fc5765f
Arrayize streams
382c242
Initial noflo.asCallback implementation
c21a9d0
Document 'grunt watch' with partial test suite
f3cd402
Merge pull request #537 from noflo/fix_iips_scope
982dfa4
Add a note to Changelog
82c144a
Merge branch 'master' of github.com:noflo/noflo into fix_iips_scope
d02ccf1
Add a test with addressable port
There are 26 commits in total. See the full diff.
Tests are failing on 2/2 Travis CI runs, with errors:
1) Mount , variant=MQTT_single: IIPs specified on commandline with component "after each" hook for "should send the IIP out":
Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
2) Mount , variant=MQTT_dedicated: IIPs specified on commandline with component "after each" hook for "should send the IIP out":
Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
3) Mount , variant=AMQP_single: IIPs specified on commandline with component "after each" hook for "should send the IIP out":
Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
4) Mount , variant=AMQP_dedicated: IIPs specified on commandline with component "after each" hook for "should send the IIP out":
Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
Whats odd is that the after_each
here just calls mount.stop
like all the other tests (which are working). Not seeing any obvious reasons why stopping would hang in this particular scenario..
Ah, the failing case was the only one directly using the core/Kick
component. And this had an old syncronous shutdown
function
Version 0.8.0 of noflo just got published.
The version 0.8.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of noflo. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
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.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: