added stripped-down UBX parser that publishes rosflight_msgs

This PR removes support of NMEA messages, through and adds an easily-extendable UBX parser that publishes native rosflight_msgs.
The UBX functionality here is intended as a stop-gap until firmware integration is complete.
The parser is a stripped-down version of my `UBLOX_read package, I removed all the RTCM, Ephemeris and Raw measurement support to keep things lean.

Hey @dpkoch,
I know you're busy this week.  :wedding:
But when you get a chance, could you help me fix this build?

The UBLOX_read package has since been updated to ROS2 and has had numerous changes, which would require that much of this work would need to be redone. I'm going to close this for now, and we can revisit adding a UBLOX driver to rosflight_utils if it's needed.


"ARM Symbol" auto analysis corrupts RAM symbol locations (GBA)

Before:

After:

The "ARM Symbol" analyzer seems designed to shift all symbols located in executable memory; this also applies to memory with read/execute rights (R/X) or full access rights (R/W/X).
Two "solutions":

In Window > Memory Map, untick the X (executable) checkbox in all memory regions except the ones containing code (ideally, nothing but code) such as the .text region (which I assume is where your ROM code and data is?) and possibly the BIOS memory region if that is mapped in your GBA program.
Disable the "ARM Symbol" analyzer. (In fact, once all program code has been found, it shouldn't be needed anymore.)

"ARM Symbol" analyzer is completely useless and be should unchecked by default


Turbo Button

Hello. Tsugaru is a very good emulator. Keep up the great work.
If I may suggest, could you add a Turbo function for gamepads and keyboards? Some games like Rayxanber require the player to be constantly pressing the assigned button in order to fire. Having a function that permits the player to hold down the fire button rather than press it repeatedly would be great.

Actually, that's one of the features I've been thinking to add but postponing.  This time I've done it.  I haven't made a new release yet, but if you can compile, the latest source allows you to turn on/off auto shot from Device->Auto Shot in GUI.


Watching subdirectories unavailable on Linux

Hey @rsms I wasn't immediately sure if this was something on estrella's end or a limitation of esbuild, so excuse my assumptions if they're off!
When I have an entry point file which is importing a module from a sub-directory, estrella only seems to execute a rebuild when something changes in the entry-point file. However if I move my files from the sub-directory to the same directory as the entry-point file, things will rebuild when any file is changed.
I guess my expectation would be to have files, which are referenced by the entry-point file but are not in the base-level directory, trigger a rebuild when they change.
An example set up running on Node 12.16.3.
./src/index.js
import MyModule from "./modules/my-module";

(function () {

   MyModule.foo();
   // returns string bar

})();

./src/modules/my-module.js
const MyModule = (function () {

   return {
       foo: function () {
           return "bar";
       }
   };

})();

export default MyModule;

./build.js
#!/usr/bin/env node

const path = require("path");
const { build, cliopts } = require("estrella");
const { createServer } = require("serve-http");

const options = {
  entry: "./src/index.js",
  outfile: "./public/bundle.js",
  bundle: true,
  minify: true
};

build(options);

cliopts.watch && createServer({
  port: 3000,
  pubdir: path.join(__dirname, "./public"),
});

Thus far whenever I change anything within my-module.js a rebuild won't trigger. Only when the change is within index.js.

What OS are you running this on?

Currently on Ubuntu 18.04.4 LTS via WSL. Your favorite, I know. ;)

I actually have a dedicated Ubuntu MacBook in my office :–)
Unfortunately this is a limitation with NodeJS's fs.watch function. The documentation mentions "The recursive option is only supported on macOS and Windows."
I'll rename this issue to be about improving deep-directory watch support. There are a lot of 3rd party libraries implementing this in JS but they are all rather heavy and I'm trying to keep estrella small.
In the meantime, what you can do is some hack like this:
#!/usr/bin/env node
const { build, scandir, watchdir } = require("estrella")
const fs = require("fs")
build({
  entry: "src/main.ts",
  outfile: "out/foo.js",
})
const srcSubdirs = [ "src/meow", "src/woff" ] // fs.readdir to automate
cliopts.watch && watchdir(srcSubdirs, /\..*$/i,() => {
  fs.writeFileSync("src/dummy.js", "")  // this would trigger a rebuild
})

Idea: Somehow ask esbuild for sources. It resolves all imports and thus after the initial build should know about all in use subdirectories. It might be even better than just blindly rebuilding whenever a file changes.

Thanks for the tip, that should probably suffice in the short term. I agree with the philosophy of keeping things nice and nimble so take your time.

I added chokidar in a branch (https://github.com/rsms/estrella/tree/fswatch). Unfortunately chokidar relies on a another third-party library which uses a "native" nodejs module which esbuild is unable to bundle (naturally, since it needs to be built for every platform.) This means that the average execution time goes from ~35ms to ~60ms on my machine. I suspect a majority of this increase is from nodejs loading the native code module (a .node "module") and wiring it up.
There are other upsides beyond Linux support with chokidar. For example, some code in estrella can be removed as chokidar implements it. This would reduce the effort to maintain estrella, which is good.
@jonathontoon if you're interested, you could check out the "fswatch" branch (git fetch --all && git checkout fswatch && ./build.js and use the file "dist/estrella.js")

Thanks @rsms will try it out and report back.
Alternatively I also hacked something together using node-watch which has a significantly smaller footprint than chokidar (less battle tested though). I don't get the warm and fuzzy feeling of seeing estrella's nice console logs but it solves the problem on Linux for the short term. 😄
#!/usr/bin/env node

(function () {

  const watch = require("node-watch");
  const path = require("path");

  const { build } = require("esbuild");
  const { createServer } = require("serve-http");

  const buildOptions = {
    entryPoints: ["./src/index.js"],
    outfile: "./public/bundle.min.js",
    bundle: true,
    minify: true,
    target: "es2015"
  };

  if (process.env.NODE_ENV === "production") {
    build(buildOptions);
  } else {
    watch("./src", { recursive: true }, function () {
      build(buildOptions);
    });

    createServer({
      port: 3000,
      pubdir: path.join(__dirname, "./public"),
    });
  }

})();

Oh, I hadn't heard of node-watch — it looks pretty good.

Closing since Estrella now uses chokidar and thus supports Linux


Fixed a node label

There was a mistake (thank you @bjlang for catching this!), the Bedtools node in the IP enrichment analysis section was labelled as Preseq.
PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs- [ ] If necessary, also make a PR on the nf-core/chipseq branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

Thank you! :100:


Support auto generation of Safari Web Push Certificates?

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
Is possible auto generate all Safari Web Push Certificates:
https://pushalert.co/creating-safari-web-push-certificate
Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

➜  ~ fastlane env
[12:44:41]: Generating fastlane environment output, this might take a few seconds...
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.3

Ruby
2.4.0

Bundler?
false

Git
git version 2.11.0

Installation Source
/usr/local/opt/rbenv/versions/2.4.0/bin/fastlane

Host
Mac OS X 10.12.3 (16D32)

Ruby Lib Dir
/usr/local/opt/rbenv/versions/2.4.0/lib

OpenSSL Version
OpenSSL 1.0.2j  26 Sep 2016

Is contained
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.12.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.1.0

slack-notifier
1.5.1

i18n
0.7.0

json
1.8.6

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.10.1

activesupport
<IP_ADDRESS>

CFPropertyList
2.3.5

claide
1.0.1

colored
1.2

nanaimo
0.2.3

xcodeproj
1.4.2

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.2.0

addressable
2.4.0

multipart-post
2.0.0

word_wrap
1.0.0

babosa
1.0.2

highline
1.7.8

commander
4.4.3

excon
0.54.0

faraday
0.10.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.0.1

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.26

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.0

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.3

faraday_middleware
0.10.1

io-console
0.4.6

openssl
2.0.2

generated on: 2017-01-29

🙄  Wow, that's a lot of markdown text... should fastlane put it into your clipboard, so you can easily paste it on GitHub? (y/n)
y
[12:44:51]: Successfully copied markdown into your clipboard 🎨
[12:44:51]: Open https://github.com/fastlane/fastlane/issues/new to submit a new issue ✅
➜  ~ fastlane --capture_output
### Captured Output
Command Used: ``
Output/Log

DEBUG [2017-01-29 12:45:11.50]: Checking if there are any plugins that should be loaded...
WARN [2017-01-29 12:45:11.52]: Could not find fastlane in current directory. Would you like to set it up?

Looking for related GitHub issues on fastlane/fastlane...
Search query: Could not retrieve response as fastlane runs in non-interactive mode

URL: https://api.github.com/search/issues?q=Could%20not%20retrieve%20response%20as%20fastlane%20runs%20in%20non-interactive%20mode+repo:fastlane/fastlane
➡  Running fastlane on Bitrise - non-interactive mode
   https://github.com/fastlane/fastlane/issues/5867 [closed] 5 💬
   06 Dec 2016

➡  fastlane env --quiet option or --force
   https://github.com/fastlane/fastlane/issues/6781 [closed] 2 💬
   3 days ago

➡  Platform specific lanes are only parsed if a matching default_platform is specified
   https://github.com/fastlane/fastlane/issues/7979 [open] 6 💬
   3 days ago

and 11 more at: https://github.com/fastlane/fastlane/search?q=Could%20not%20retrieve%20response%20as%20fastlane%20runs%20in%20non-interactive%20mode&type=Issues&utf8=✓

🔗  You can ⌘ + double-click on links to open them directly in your browser.

✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.3

Ruby
2.4.0

Bundler?
false

Git
git version 2.11.0

Installation Source
/usr/local/opt/rbenv/versions/2.4.0/bin/fastlane

Host
Mac OS X 10.12.3 (16D32)

Ruby Lib Dir
/usr/local/opt/rbenv/versions/2.4.0/lib

OpenSSL Version
OpenSSL 1.0.2j  26 Sep 2016

Is contained
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.12.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.1.0

slack-notifier
1.5.1

i18n
0.7.0

json
1.8.6

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.10.1

activesupport
<IP_ADDRESS>

CFPropertyList
2.3.5

claide
1.0.1

colored
1.2

nanaimo
0.2.3

xcodeproj
1.4.2

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.2.0

addressable
2.4.0

multipart-post
2.0.0

word_wrap
1.0.0

babosa
1.0.2

highline
1.7.8

commander
4.4.3

excon
0.54.0

faraday
0.10.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.0.1

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.26

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.0

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.3

faraday_middleware
0.10.1

io-console
0.4.6

openssl
2.0.2

generated on: 2017-01-29

🙄  Wow, that's a lot of markdown text... should fastlane put it into your clipboard, so you can easily paste it on GitHub? (y/n)
y
/usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.12.0/fastlane_core/lib/fastlane_core/ui/interface.rb:132:in `crash!': [!] Could not retrieve response as fastlane runs in non-interactive mode (FastlaneCore::Interface::FastlaneCrash)
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.12.0/fastlane_core/lib/fastlane_core/ui/implementations/shell.rb:120:in `verify_interactive!'
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.12.0/fastlane_core/lib/fastlane_core/ui/implementations/shell.rb:98:in `confirm'
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.12.0/fastlane_core/lib/fastlane_core/ui/ui.rb:14:in `method_missing'
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.12.0/fastlane/lib/fastlane/commands_generator.rb:312:in `ensure_fastfile'
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.12.0/fastlane/lib/fastlane/commands_generator.rb:104:in `block (2 levels) in run'
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/commander-4.4.3/lib/commander/command.rb:178:in `call'
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/commander-4.4.3/lib/commander/command.rb:153:in `run'
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/commander-4.4.3/lib/commander/runner.rb:446:in `run_active_command'
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.12.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:38:in `run!'
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/commander-4.4.3/lib/commander/delegates.rb:15:in `run!'
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.12.0/fastlane/lib/fastlane/commands_generator.rb:302:in `run'
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.12.0/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.12.0/fastlane/lib/fastlane/cli_tools_distributor.rb:59:in `take_off'
	from /usr/local/opt/rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/gems/fastlane-2.12.0/bin/fastlane:15:in `'
	from /usr/local/opt/rbenv/versions/2.4.0/bin/fastlane:22:in `load'
	from /usr/local/opt/rbenv/versions/2.4.0/bin/fastlane:22:in `'
➜  ~ >....
| terminal-table            | 1.7.3        |
| plist                     | 3.2.0        |
| addressable               | 2.4.0        |
| multipart-post            | 2.0.0        |
| word_wrap                 | 1.0.0        |
| babosa                    | 1.0.2        |
| highline                  | 1.7.8        |
| commander                 | 4.4.3        |
| excon                     | 0.54.0       |
| faraday                   | 0.10.1       |
| unf_ext                   | <IP_ADDRESS>      |
| unf                       | 0.1.4        |
| domain_name               | 0.5.20161129 |
| http-cookie               | 1.0.3        |
| faraday-cookie_jar        | 0.0.6        |
| fastimage                 | 2.0.1        |
| gh_inspector              | 1.0.3        |
| uber                      | 0.0.15       |
| representable             | 2.3.0        |
| retriable                 | 2.1.0        |
| mime-types-data           | 3.2016.0521  |
| mime-types                | 3.1          |
| hurley                    | 0.2          |
| little-plugger            | 1.1.4        |
| multi_json                | 1.12.1       |
| logging                   | 2.1.0        |
| jwt                       | 1.5.6        |
| memoist                   | 0.15.0       |
| os                        | 0.9.6        |
| signet                    | 0.7.3        |
| googleauth                | 0.5.1        |
| httpclient                | 2.8.3        |
| google-api-client         | 0.9.26       |
| mini_magick               | 4.5.1        |
| multi_xml                 | 0.6.0        |
| rubyzip                   | 1.2.0        |
| security                  | 0.1.3        |
| xcpretty-travis-formatter | 0.0.4        |
| dotenv                    | 2.2.0        |
| bundler                   | 1.14.3       |
| faraday_middleware        | 0.10.1       |
| io-console                | 0.4.6        |
| openssl                   | 2.0.2        |

generated on: 2017-01-29
:q
zsh: parse error near `<'
➜  ~ ### Captured Output
Command Used: ``
Output/Log

DEBUG [2017-01-29 12:45:11.50]: Checking if there are any plugins that should be loaded...
WARN [2017-01-29 12:45:11.52]: Could not find fastlane in current directory. Would you like to set it up?

Looking for related GitHub issues on fastlane/fastlane...
Search query: Could not retrieve response as fastlane runs in non-interactive mode

URL: https://api.github.com/search/issues?q=Could%20not%20retrieve%20response%20as%20fastlane%20runs%20in%20non-interactive%20mode+repo:fastlane/fastlane
➡  Running fastlane on Bitrise - non-interactive mode
   https://github.com/fastlane/fastlane/issues/5867 [closed] 5 💬
   06 Dec 2016

➡  fastlane env --quiet option or --force
   https://github.com/fastlane/fastlane/issues/6781 [closed] 2 💬
   3 days ago

➡  Platform specific lanes are only parsed if a matching default_platform is specified
   https://github.com/fastlane/fastlane/issues/7979 [open] 6 💬
   3 days ago

and 11 more at: https://github.com/fastlane/fastlane/search?q=Could%20not%20retrieve%20response%20as%20fastlane%20runs%20in%20non-interactive%20mode&type=Issues&utf8=✓

🔗  You can ⌘ + double-click on links to open them directly in your browser.

<2705> fastlane environment <2705>
Stack

Key
Value

OS
10.12.3

Ruby
2.4.0

Bundler?
false

Git
git version 2.11.0

Installation Source
/usr/local/opt/rbenv/versions/2.4.0/bin/fastlane

Host
Mac OS X 10.12.3 (16D32)

Ruby Lib Dir
/usr/local/opt/rbenv/versions/2.4.0/lib

Captured Output
Command Used: ``
Output/Log

DEBUG [2017-01-29 12:45:11.50]: Checking if there are any plugins that should be loaded...
WARN [2017-01-29 12:45:11.52]: Could not find fastlane in current directory. Would you like to set it up?

Looking for related GitHub issues on fastlane/fastlane...
Search query: Could not retrieve response as fastlane runs in non-interactive mode

URL: https://api.github.com/search/issues?q=Could%20not%20retrieve%20response%20as%20fastlane%20runs%20in%20non-interactive%20mode+repo:fastlane/fastlane
➡  Running fastlane on Bitrise - non-interactive mode
   https://github.com/fastlane/fastlane/issues/5867 [closed] 5 💬
   06 Dec 2016

➡  fastlane env --quiet option or --force
   https://github.com/fastlane/fastlane/issues/6781 [closed] 2 💬
   3 days ago

➡  Platform specific lanes are only parsed if a matching default_platform is specified
   https://github.com/fastlane/fastlane/issues/7979 [open] 6 💬
   3 days ago

and 11 more at: https://github.com/fastlane/fastlane/search?q=Could%20not%20retrieve%20response%20as%20fastlane%20runs%20in%20non-interactive%20mode&type=Issues&utf8=✓

🔗  You can ⌘ + double-click on links to open them directly in your browser.

✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.3

Ruby
2.4.0

Bundler?
false

Git
git version 2.11.0

Installation Source
/usr/local/opt/rbenv/versions/2.4.0/bin/fastlane

Host
Mac OS X 10.12.3 (16D32)

Ruby Lib Dir
/usr/local/opt/rbenv/versions/2.4.0/lib

OpenSSL Version
OpenSSL 1.0.2j  26 Sep 2016

Is contained
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.12.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.1.0

slack-notifier
1.5.1

i18n
0.7.0

json
1.8.6

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.10.1

activesupport
<IP_ADDRESS>

CFPropertyList
2.3.5

claide
1.0.1

colored
1.2

nanaimo
0.2.3

xcodeproj
1.4.2

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.2.0

addressable
2.4.0

multipart-post
2.0.0

word_wrap
1.0.0

babosa
1.0.2

highline
1.7.8

commander
4.4.3

excon
0.54.0

faraday
0.10.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.0.1

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.26

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.0

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.3

faraday_middleware
0.10.1

io-console
0.4.6

openssl
2.0.2

generated on: 2017-01-29

Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
✅ fastlane environment ✅
Stack

Key
Value

OS
10.12.3

Ruby
2.4.0

Bundler?
false

Git
git version 2.11.0

Installation Source
/usr/local/opt/rbenv/versions/2.4.0/bin/fastlane

Host
Mac OS X 10.12.3 (16D32)

Ruby Lib Dir
/usr/local/opt/rbenv/versions/2.4.0/lib

OpenSSL Version
OpenSSL 1.0.2j  26 Sep 2016

Is contained
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.12.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.1.0

slack-notifier
1.5.1

i18n
0.7.0

json
1.8.6

thread_safe
0.3.5

tzinfo
1.2.2

minitest
5.10.1

activesupport
<IP_ADDRESS>

CFPropertyList
2.3.5

claide
1.0.1

colored
1.2

nanaimo
0.2.3

xcodeproj
1.4.2

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.7.1

unicode-display_width
1.1.3

terminal-table
1.7.3

plist
3.2.0

addressable
2.4.0

multipart-post
2.0.0

word_wrap
1.0.0

babosa
1.0.2

highline
1.7.8

commander
4.4.3

excon
0.54.0

faraday
0.10.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.0.1

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

mime-types-data
3.2016.0521

mime-types
3.1

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.26

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.0

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.3

faraday_middleware
0.10.1

io-console
0.4.6

openssl
2.0.2

generated on: 2017-01-29

Hey @RafaelPlantard! Thanks for raising this issue. Creating Safari Web Push Certificates is currently not supported by fastlane. We would be happy to have a plugin that could handle this functionality, but our vision is really to be the sharpest tool for mobile app development so this is is not something we would immediately want to include in our main code base. Thanks again! 🐙 👍

Thanks @ohayon

releated to: https://github.com/fastlane/fastlane/pull/6943 seems like only pem is missing - i am going to ping the author if he could share the pem changes

That's sound awesome @hjanuschka


MNE source files are not displayed

The following example:
import numpy as np
import matplotlib.pyplot as plt

import mne
from mne.datasets import sample, fetch_hcp_mmp_parcellation
from mne.minimum_norm import apply_inverse, read_inverse_operator
from mne import read_evokeds

data_path = sample.data_path()
meg_path = data_path / 'MEG' / 'sample'
subjects_dir = data_path / 'subjects'

fname_evoked = meg_path / 'sample_audvis-ave.fif'
fname_stc = meg_path / 'sample_audvis-meg'
fetch_hcp_mmp_parcellation(subjects_dir)

nv = ipyniivue.Niivue(crosshair_color=[0,1,0,1])
nv.add_volume(str(fname_stc) + "-lh.stc")

fails to display the sources stored in the .stc format. According to https://github.com/niivue/niivue, NiiVue supports this format. Here is the results from this code when ran on Google Colab:

@christian-oreilly add_volume adds a voxel-based image (e.g. NIfTI, DICOM, NRRD). An STC file contains the per-vertex values for a mesh. So you would want to add your desired triangular mesh (e.g. left-hemisphere mesh) and then load your STC file as a layer attached to the mesh. Note that you can have multiple meshes open at once (e.g. left and right hemisphere simultaneously) each with its own layer(s). The mesh 4D live demo illustrates the process.

Thanks @neurolabusc for this info. Right, that makes sense. I had in mind that these files embedded the meshes as other MNE structures do (like the source model and the forward model if I am not mistaken)... but you are right, they don't. I'll cycle back to this when I have a moment to try to finish the demo with ipyniivue given this info.


Review: Concat layer

Concat layer implementation detr_layers/concat.py needs to be validated with actual architecture.
Please feel free to submit a PR!

@pranavdurai10, can you assign this issue to me?


Pvh boot

This PR adds the PVH Boot mechnism described here.
It adds some devices, setting MSR and CPUIDs, registers, segment registers and other stuff to allow to boot into EDK2/CloudHv EFI-Shell.
Further work to boot into an operating system is required.

Im aware of the errors, will get rid of them the next couple of days.

Trying to extend it to boot Linux compiled as ELF with pvh support.

I'm aware there are no unit tests in place yet.

Not sure. This is kinda messy, but I also have no clue how to improve structure.
Problem I see is the following:
Multiple boot modes, two in one function, and pvh in a different function. Not ideal.
I know a restructure is required here, but I also don't know how yet. Maybe you have an idea.

#150 must be merged first.
PVH loads linux kernel and initrd now as well.
Last problem to solve:
How to handle the boot modes and cmdline arguments for kernel, initrd and firmware image?

Ok, somehow CI works and not at the same time. Still the issue with commandline args persists.
See: #151

Thanks for the great suggestion!
I am going on a trip for a few days. I may be able to reply to each PR on Friday.

This works with 3G memory for EDK2, and Linux load does not work at the moment. Some memory layout related issue.
So HVM_MemMap_Table_Entries not properly set up. Need to investigate.

Ok, CI runs, but still I have to investigate the memory issues and add a test case to test EDK2 execution

Still not loading kernel/initrd with pvh boot. Still dunno what goes wrong.
  398.885484][    C0] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 53.676 msecs
[  398.885484][    C0] perf: interrupt took too long (1759727 > 1686288), lowering kernel.perf_event_max_sample_rate to 250
[  398.889484][   T21] Trying to unpack rootfs image as initramfs...
[  398.905485][    T1] platform rtc_cmos: registered platform RTC device (no PNP device found)

Still not loading kernel/initrd with pvh boot. Still dunno what goes wrong.
[  398.885484][    C0] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 53.676 msecs
[  398.885484][    C0] perf: interrupt took too long (1759727 > 1686288), lowering kernel.perf_event_max_sample_rate to 250
[  398.889484][   T21] Trying to unpack rootfs image as initramfs...
[  398.905485][    T1] platform rtc_cmos: registered platform RTC device (no PNP device found)

After that the VM exits...

CMOS Device was the issue.....
Linux/Initrd now boots, but only with 4G of memory. For 1G-3G I get errors. Still investigating.

[  369.783040][    C0] watchdog: Watchdog detected hard LOCKUP on cpu 0
[  369.783040][    C0] irq event stamp: 6352
[  369.783040][    C0] hardirqs last  enabled at (6351): [<ffffffff814c132d>] _raw_spin_unlock_irq+0x23/0x34
[  369.783040][    C0] hardirqs last disabled at (6352): [<ffffffff814b9614>] exc_nmi+0x83/0x107
[  369.783040][    C0] softirqs last  enabled at (6038): [<ffffffff814c1e98>] __do_softirq+0x298/0x2c4
[  369.783040][    C0] softirqs last disabled at (6029): [<ffffffff81051772>] irq_exit_rcu+0x9/0x11
[  369.783040][    C0] CPU: 0 PID: 21 Comm: kworker/u128:1 Not tainted 6.5.0-rc5+ #7 7d885148b887b779f025cd7d8b8daf9b731f1e9e
[  369.783040][    C0] Workqueue: events_unbound async_run_entry_fn
[  369.783040][    C0] RIP: 0010:lzma_match+0x2b5/0x2ff
[  369.783040][    C0] Code: 18 0f b6 04 07 8b 7b 04 c1 e7 08 01 f8 89 43 04 44 8b 03 0f b7 3a 01 f6 44 89 c0 c1 e8 0b 0f af c7 8b 7b 04 39 c7 73 19 89 03 <44> 0f b7 02 44 89 df 44 29 c7 44 89 c0 c1 b
[  369.783040][    C0] RSP: 0018:ffffc900002a3c80 EFLAGS: 00000297
[  369.783040][    C0] RAX:<PHONE_NUMBER>63d43a RBX: ffff888003ad8000 RCX:<PHONE_NUMBER>000003
[  369.783040][    C0] RDX: ffff888003ad8700 RSI:<PHONE_NUMBER>00001c RDI: 000000002d36f3c2
[  369.783040][    C0] RBP: ffff888003ad8090 R08:<PHONE_NUMBER>4d1600 R09: ffff888003ad86e4
[  369.783040][    C0] R10:<PHONE_NUMBER>000001 R11:<PHONE_NUMBER>000800 R12:<PHONE_NUMBER>0097bc
[  369.783040][    C0] R13:<PHONE_NUMBER>000003 R14: ffffffff81f72fc4 R15:<PHONE_NUMBER>000000
[  369.783040][    C0] FS:<PHONE_NUMBER>000000(0000) GS:ffff8880bbe00000(0000) knlGS:0000000000000000
[  369.783040][    C0] CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
[  369.783040][    C0] CR2: ffff888002c00000 CR3:<PHONE_NUMBER>c38000 CR4:<PHONE_NUMBER>3506b0
[  369.783040][    C0] Call Trace:
[  369.783040][    C0]  <NMI>
[  369.783040][    C0]  ? watchdog_hardlockup_check+0xaf/0x12f
[  369.783040][    C0]  ? __perf_event_overflow+0x163/0x1a6
[  369.783040][    C0]  ? x86_pmu_handle_irq+0xf4/0x12f
[  369.783040][    C0]  ? vscnprintf+0x14/0x22
[  369.783040][    C0]  ? prb_final_commit+0x16/0x21
[  369.783040][    C0]  ? look_up_lock_class+0x7c/0x95
[  369.783040][    C0]  ? lock_acquire+0x191/0x21d
[  369.783040][    C0]  ? amd_pmu_handle_irq+0x28/0x37
[  369.783040][    C0]  ? perf_event_nmi_handler+0x25/0x3e
[  369.783040][    C0]  ? nmi_handle+0xb9/0x1fc
[  369.783040][    C0]  ? default_do_nmi+0x42/0x20a
[  369.783040][    C0]  ? exc_nmi+0x9e/0x107
[  369.783040][    C0]  ? end_repeat_nmi+0x16/0x67
[  369.783040][    C0]  ? initrd_load+0x61/0x61
[  369.783040][    C0]  ? lzma_match+0x2b5/0x2ff
[  369.783040][    C0]  ? lzma_match+0x2b5/0x2ff
[  369.783040][    C0]  ? lzma_match+0x2b5/0x2ff
[  369.783040][    C0]  </NMI>
[  369.783040][    C0]  <TASK>
[  369.783040][    C0]  lzma_main+0x14d/0x1bf
[  369.783040][    C0]  lzma2_lzma+0x14f/0x1c1
[  369.783040][    C0]  xz_dec_lzma2_run+0x2d5/0x46e
[  369.783040][    C0]  dec_main+0x1b4/0x4da
[  369.783040][    C0]  ? do_copy+0x10b/0x10d
[  369.783040][    C0]  ? initrd_load+0x61/0x61
[  369.783040][    C0]  xz_dec_run+0x2e/0x82
[  369.783040][    C0]  ? write_buffer+0x2f/0x2f
[  369.783040][    C0]  unxz+0x14d/0x2c6
[  369.783040][    C0]  ? write_buffer+0x2f/0x2f
[  369.783040][    C0]  ? unlzo+0x3bc/0x3bc
[  369.783040][    C0]  unpack_to_rootfs+0x15c/0x278
[  369.783040][    C0]  ? initrd_load+0x61/0x61
[  369.783040][    C0]  do_populate_rootfs+0x65/0x13d
[  369.783040][    C0]  async_run_entry_fn+0x58/0xfa
[  369.783040][    C0]  process_one_work+0x1e8/0x334
[  369.783040][    C0]  worker_thread+0x159/0x202
[  369.783040][    C0]  ? process_scheduled_works+0x27/0x27
[  369.783040][    C0]  kthread+0xd3/0xdb
[  369.783040][    C0]  ? kthread_exit+0x1e/0x1e
[  369.783040][    C0]  ret_from_fork+0x20/0x32
[  369.783040][    C0]  ? kthread_exit+0x1e/0x1e
[  369.783040][    C0]  ret_from_fork_asm+0x11/0x40
[  369.783040][    C0]  </TASK>
[  369.783040][    C0] Kernel panic - not syncing: Hard LOCKUP
[  369.783040][    C0] Kernel Offset: disabled
[  369.783040][    C0]
[  369.783040][    C0] ================================
[  369.783040][    C0] WARNING: inconsistent lock state
[  369.783040][    C0] 6.5.0-rc5+ #7 Not tainted
[  369.783040][    C0] --------------------------------
[  369.783040][    C0] inconsistent {INITIAL USE} -> {IN-NMI} usage.
[  369.783040][    C0] kworker/u128:1/21 [HC1[1]:SC0[0]:HE0:SE1] takes:
[  369.783040][    C0] ffffffff81cc4858 ((console_sem).lock){-.-.}-{2:2}, at: down_trylock+0xf/0x2d
[  369.783040][    C0] {INITIAL USE} state was registered at:
[  369.783040][    C0] irq event stamp: 6352
[  369.783040][    C0] hardirqs last  enabled at (6351): [<ffffffff814c132d>] _raw_spin_unlock_irq+0x23/0x34
[  369.783040][    C0] hardirqs last disabled at (6352): [<ffffffff814b9614>] exc_nmi+0x83/0x107
[  369.783040][    C0] softirqs last  enabled at (6038): [<ffffffff814c1e98>] __do_softirq+0x298/0x2c4
[  369.783040][    C0] softirqs last disabled at (6029): [<ffffffff81051772>] irq_exit_rcu+0x9/0x11
[  369.783040][    C0]
[  369.783040][    C0] other info that might help us debug this:
[  369.783040][    C0]  Possible unsafe locking scenario:
[  369.783040][    C0]
[  369.783040][    C0]        CPU0
[  369.783040][    C0]        ----
[  369.783040][    C0]   lock((console_sem).lock);
[  369.783040][    C0]   <Interrupt>
[  369.783040][    C0]     lock((console_sem).lock);
[  369.783040][    C0]
[  369.783040][    C0]  *** DEADLOCK ***
[  369.783040][    C0]
[  369.783040][    C0] 2 locks held by kworker/u128:1/21:
[  369.783040][    C0]  #0: ffff888000158d38 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x123/0x334
[  369.783040][    C0]  #1: ffffc900002a3e78 ((work_completion)(&entry->work)){+.+.}-{0:0}, at: process_one_work+0x123/0x334
[  369.783040][    C0]
[  369.783040][    C0] stack backtrace:
[  369.783040][    C0] CPU: 0 PID: 21 Comm: kworker/u128:1 Not tainted 6.5.0-rc5+ #7 7d885148b887b779f025cd7d8b8daf9b731f1e9e
[  369.783040][    C0] Workqueue: events_unbound async_run_entry_fn
[  369.783040][    C0] Call Trace:
[  369.783040][    C0]  <NMI>
[  369.783040][    C0]  dump_stack_lvl+0x6e/0x9f
[  369.783040][    C0]  lock_acquire+0x1f6/0x21d
[  369.783040][    C0]  ? _printk+0x47/0x49
[  369.783040][    C0]  ? down_trylock+0xf/0x2d
[  369.783040][    C0]  _raw_spin_lock_irqsave+0x3a/0x49
[  369.783040][    C0]  ? down_trylock+0xf/0x2d
[  369.783040][    C0]  ? panic+0x148/0x267
[  369.783040][    C0]  down_trylock+0xf/0x2d
[  369.783040][    C0]  __down_trylock_console_sem+0x1f/0x95
[  369.783040][    C0]  console_unblank+0x19/0x8f
[  369.783040][    C0]  panic+0x148/0x267
[  369.783040][    C0]  nmi_panic+0x27/0x31
[  369.783040][    C0]  watchdog_hardlockup_check+0x10f/0x12f
[  369.783040][    C0]  __perf_event_overflow+0x163/0x1a6
[  369.783040][    C0]  x86_pmu_handle_irq+0xf4/0x12f
[  369.783040][    C0]  ? vscnprintf+0x14/0x22
[  369.783040][    C0]  ? prb_final_commit+0x16/0x21
[  369.783040][    C0]  ? look_up_lock_class+0x7c/0x95
[  369.783040][    C0]  ? lock_acquire+0x191/0x21d
[  369.783040][    C0]  amd_pmu_handle_irq+0x28/0x37
[  369.783040][    C0]  perf_event_nmi_handler+0x25/0x3e
[  369.783040][    C0]  nmi_handle+0xb9/0x1fc
[  369.783040][    C0]  default_do_nmi+0x42/0x20a
[  369.783040][    C0]  exc_nmi+0x9e/0x107
[  369.783040][    C0]  end_repeat_nmi+0x16/0x67
[  369.783040][    C0] RIP: 0010:lzma_match+0x2b5/0x2ff
[  369.783040][    C0] Code: 18 0f b6 04 07 8b 7b 04 c1 e7 08 01 f8 89 43 04 44 8b 03 0f b7 3a 01 f6 44 89 c0 c1 e8 0b 0f af c7 8b 7b 04 39 c7 73 19 89 03 <44> 0f b7 02 44 89 df 44 29 c7 44 89 c0 c1 b
[  369.783040][    C0] RSP: 0018:ffffc900002a3c80 EFLAGS: 00000297
[  369.783040][    C0] RAX:<PHONE_NUMBER>63d43a RBX: ffff888003ad8000 RCX:<PHONE_NUMBER>000003
[  369.783040][    C0] RDX: ffff888003ad8700 RSI:<PHONE_NUMBER>00001c RDI: 000000002d36f3c2
[  369.783040][    C0] RBP: ffff888003ad8090 R08:<PHONE_NUMBER>4d1600 R09: ffff888003ad86e4
[  369.783040][    C0] R10:<PHONE_NUMBER>000001 R11:<PHONE_NUMBER>000800 R12:<PHONE_NUMBER>0097bc
[  369.783040][    C0] R13:<PHONE_NUMBER>000003 R14: ffffffff81f72fc4 R15:<PHONE_NUMBER>000000
[  369.783040][    C0]  ? initrd_load+0x61/0x61
[  369.783040][    C0]  ? lzma_match+0x2b5/0x2ff
[  369.783040][    C0]  ? lzma_match+0x2b5/0x2ff
[  369.783040][    C0]  </NMI>
[  369.783040][    C0]  <TASK>
[  369.783040][    C0]  lzma_main+0x14d/0x1bf
[  369.783040][    C0]  lzma2_lzma+0x14f/0x1c1
[  369.783040][    C0]  xz_dec_lzma2_run+0x2d5/0x46e
[  369.783040][    C0]  dec_main+0x1b4/0x4da
[  369.783040][    C0]  ? do_copy+0x10b/0x10d
[  369.783040][    C0]  ? initrd_load+0x61/0x61
[  369.783040][    C0]  xz_dec_run+0x2e/0x82
[  369.783040][    C0]  ? write_buffer+0x2f/0x2f
[  369.783040][    C0]  unxz+0x14d/0x2c6
[  369.783040][    C0]  ? write_buffer+0x2f/0x2f
[  369.783040][    C0]  ? unlzo+0x3bc/0x3bc
[  369.783040][    C0]  unpack_to_rootfs+0x15c/0x278
[  369.783040][    C0]  ? initrd_load+0x61/0x61
[  369.783040][    C0]  do_populate_rootfs+0x65/0x13d
[  369.783040][    C0]  async_run_entry_fn+0x58/0xfa
[  369.783040][    C0]  process_one_work+0x1e8/0x334
[  369.783040][    C0]  worker_thread+0x159/0x202
[  369.783040][    C0]  ? process_scheduled_works+0x27/0x27
[  369.783040][    C0]  kthread+0xd3/0xdb
[  369.783040][    C0]  ? kthread_exit+0x1e/0x1e
[  369.783040][    C0]  ret_from_fork+0x20/0x32
[  369.783040][    C0]  ? kthread_exit+0x1e/0x1e
[  369.783040][    C0]  ret_from_fork_asm+0x11/0x40

Basically this is the error I get if memory size is between 1G and 3G

nowatchdog and nmi_watchdog=0 fixed the issue for now.

Added the linux_pvh.config. @bobuhiro11 can you build a bzImage and upload it to github, so we can use it in CI?

Moin @ChriMarMe ,
It's really a great improvement! I am impressed.
I can confirm that it works in my machine.
I uploaded the bzImage, so please follow the instructions below.
$ wget https://github.com/bobuhiro11/bins/raw/main/gokvm/bzImage_PVH
$ ./extract-vmlinux ./bzImage_PVH > vmlinux_PVH
$ sudo ./gokvm boot  -k ./vmlinux_PVH -i ./initrd  -m 1G
IsPVH=True # This line was added by me for debugging.
…
2003/07/31 08:01:08 Welcome to u-root!

I used linux_pvh.config as a reference. It helped me a lot.
Linux 6.5.0 was just officially released, so there is a bit of a difference. Please take it out as follows.
$ ./extract-ikconfig bzImage_PVH > linux_pvh.config

Updated the linux_pvh.config the way you suggested.

-5.0# --- FAIL: TestNewAndLoadLinuxPVH (0.62s)

    machine_test.go:30: TUN TUNSETIFF: device or resource busy

FAIL

Hmm what to dooo?

:triumph:

whoops. xD

Ok. Test runs well. Lets clean this mess up and get it merged :)

That's so great. I am amazed at your development skills! I'm not used to reviewing patches of this magnitude, so I just commented on the improvements based on my gut feeling.
It will probably take me a long time to figure it all out. So if the testing is successful by CI and you think it's good, I'm willing to merge it 👍

Thank you for the compliment :)
Take your time for the review. Some parts are still very messy, but I'll do the best to clean up if I see something.
I know this one commit is very huge, but I had no idea how to make the changes smaller or more atomic.

Hey, what is the status? Can you give me an intermediate review this week so I can start doing the corrections?

ignore the 3 commits, they are here until the other PRs are merged.

Added

download of CLOUDHV.fd in the script
entry in .gitignore for that file
Test using the image

Idk, but the CLOUDHV.fd file fails in the CI while working locally........

I have no clue why it works now, but it does. YEEEEEHAAAAAAAAWWWWWWW

I seperated the one commit into several to break up the changes a little. I hope now you'll have an easier time reviewing the changes.

Ok, lets go :)


Add Error Handling to Bootstrapping Logic

This one is recommended in the style guide. https://angular.io/guide/styleguide#style-02-05 If it's part of the blueprint, it'd be better.
I am not sure if I've added it to the right file. Please review and merge if you think it's fine.

I signed it!

@Brocco can you review?
@sanspace CI is failing because of the commit message. We require commit messages to follow a specific format to auto generate the change log. Can you change it to fix(@angular/cli): Add Error Handling to Bootstrapping Logic please?

I think, I will have to send another PR with the correct commit msg format. Please reject/close this one. Thank you.

Sent another PR https://github.com/angular/angular-cli/pull/7242


Add BertConfig and RobertaConfig for hyperparameters

The split-implementation introduces some redundancy since some of the hyperparameters are shared between different model components, but it's more composable overall.


Cannot get Spring context outside a Component

Hi,
How can we get the Spring context outside a @Component?
So far it seems that we cannot as AbstractJavaFxApplicationSupport does not provide any access to it.
Eventually we could define a Component that get it by constructor autowired then init a static variable and only then some Util classes (that we do not want to transform to Component) could poll on it until it is not null anymore.
Am I right?
EDIT: I have modified the util class to become a component but still interested to know what you would recommend.

I am not sure if I get your question correctly.
This seems to be more a question about the Spring Framework, am I right?
What do you mean by "getting the context" outside a component?

I had a Util class that was not supposed to become a @Component so I wanted to be able to get Spring context from "AbstractJavaFxApplicationSupport" class via overriding a public method to allow to get "ConfigurableApplicationContext" that is inside "AbstractJavaFxApplicationSupport" but there was no way to do.
As a result, I modified my code of the Util class to become a @Component and I was able to do what you mentioned which is the proper way to do in Spring.
I think you can mark this issue as solved because to transform to @Component is the best approach.

O.k. Thanks.


Remove dependency on ATL

To resolve issue #848

@googlebot I signed it!

@googlebot I signed it!

@googlebot I fixed it.

@googlebot I fixed it.


The lychee exit status doesn't seem to be be propagated correctly through the action

I have the action currently setup like this:
            -
                name: Link Checker
                uses: lycheeverse/lychee-action@master
                with:
                    args: --verbose --offline --base ./tests/functional/init/public ./tests/functional/init/public

It gives me this output:
+ LYCHEE_TMP=/tmp/lychee/out.md
+ GITHUB_WORKFLOW_URL='https://github.com/sigwinhq/yassg/actions/runs/1750502305?check_suite_focus=true'
++ dirname /tmp/lychee/out.md
+ mkdir -p /tmp/lychee
+ ARGS='--verbose --offline --base ./tests/functional/init/public ./tests/functional/init/public'
+ FORMAT=
+ [[ --verbose --offline --base ./tests/functional/init/public ./tests/functional/init/public =~ --format  ]]
+ FORMAT='--format markdown'
+ lychee --format markdown --output /tmp/lychee/out.md --verbose --offline --base ./tests/functional/init/public ./tests/functional/init/public
Error: Failed to read file: `./tests/functional/init/public`, reason: Is a directory (os error 21)
+ exit_code=1
+ '[' 1 -ne 0 ']'
++ dirname -- lychee/out.md
+ mkdir -p lychee
+ cat /tmp/lychee/out.md
cat: /tmp/lychee/out.md: No such file or directory
+ echo '[Full Github Actions output](https://github.com/sigwinhq/yassg/actions/runs/1750502305?check_suite_focus=true)'
+ cat /tmp/lychee/out.md
cat: /tmp/lychee/out.md: No such file or directory

+ echo

+ echo ::set-output name=exit_code::1
+ '[' false = true ']'

But the action passed? Seems the exit code from any of the commands didn't get propagated correctly.

Reading through the docs, seems this is by design, but IMO it's not a good default to not fail.

Sounds like you found https://github.com/lycheeverse/lychee-action#alternative-approach already.
But just in general, the thought process was that lychee was used as a step within a bigger "linting" pipeline and we didn't want to fail the entire pipeline because of a broken link. Now the question is if broken links are critical for the success of an entire action run.
We have some bigger projects using lychee that would break if we change that, but it's not too late to discuss. Would like to see some strong arguments in favor of failing the pipeline, though, because this would be a major breaking change and making it fail is as simple as adding fail: true.

@mre thanks for the explanation.
From my POV, the GH action is basically "lychee in a box", it should align completely with what the app does by default. If you add a new step / job to a CI, typically it failing short circuits the entire thing by default because that's how the underlying tools work, even doing ls no-such-file will fail the build.
This is somewhat outlined in the Principle of least astonishment where things should happen how  most users expect it to happen. A CI job not failing when the underlying tool fails is not following that.

making it fail is as simple as adding fail: true.

I'd argue that making it not fail is as simple as adding fail: false. :)
Again, the GH action should be "convenience around the tool" and should ideally by default behave exactly like the tool. Any additional features the action provides should be strictly opt-in for users who want more.

I agree. If there are no objections I'm all for changing it.
@lycheeverse/contrib fyi


Standardize theme colors

Description
The theme colors on the _app.scss have gone a bit out of control, many colors overlap and generally speaking there are three main theme colors. Very simple fix but clean up the css colors, might need some guidance from @faithlos

The UI has been changed recently hence this issue is no longer needed


Fix iTerm2 startup issues and additional options

Building off of sammy's patch, this commit fixes script to startup iTerm2 and operate more reliably in a variety of iTerm2 configurations and if it isn't already running.
While in the code I also added two more property options:

always open a new session/tab if Alfred starts iTerm2
whether to raise and switch keyboard focus to show output if iTerm2 is already running

Updated README.md to describe optional property settings.

Will this resolve https://github.com/vitorgalvao/custom-alfred-iterm-scripts/issues/43 @crowedavid? Hopefully, this is merged soon :)

I’ve just released a new version, and ultimately I’m deciding against this.
While I’ve added the option to open in a new window (from the other PR), opening a new session seems useless in that context (it’s either one or the other), and not bringing to front is a bad experience, because the only time it can work is when a window is already open and the user sets to open in a new tab.

I’ve just released a new version, and ultimately I’m deciding against this.
While I’ve added the option to open in a new window (from the other PR), opening a new session seems useless in that context (it’s either one or the other), and not bringing to front is a bad experience, because the only time it can work is when a window is already open and the user sets to open in a new tab.
Thank you anyway for the PR.

I’ve just released a new version, and ultimately I’m deciding against this.

completely understand.

Thank you anyway for the PR.

thanks for the colorful feedback on my coding style. it appears you have included the logic and actions using the nested "if/else/end" even though you didn't like them; they do resolve the startup and operational problems others have noted. the optional properties i included were only to offer a mechanism to enable behaviors i found useful.
i haven't tested your new release but will soon and comment on that thread.

Will this resolve #43 @crowedavid? Hopefully, this is merged soon :)

my updated code did resolve #43. vitor's new release includes the logic and is on the master branch so i'd use it instead of mine.  i haven't tested it yet myself yet however.

thanks for the colorful feedback on my coding style.

I’m unsure if you’ve taken my review badly. If you did, know that was not my intention.
I’m responsible for the code in this repo, which means that long after a PR is merged and the contributor is gone, I’m the one that has to maintain the code and keep it working. There was no criticism on your coding style—you can code however you want—but inside an existing project, consistency with existing code is important. In some cases you didn’t have examples to latch on to, so I needed to make the points now.
That’s what code reviews are for.

it appears you have included the logic and actions using the nested "if/else/end" even though you didn't like them

I didn’t say I didn’t like them, I said I didn’t get the point because in your case it seemed to always lead to the same result, which defeated the purpose of a conditional. I now see one of the cases I wasn’t thinking about, though I haven’t tested.
Your PR did something important for the new release. It and the previous one and all the other code floating around showed how confusing it can be to deal with iTerm in AppleScript. It’s too verbose and conditionals are hard to parse mentally. That’s why I decided to define the handlers, so it can be extended more easily and we can keep the conditional logic short.

review not taken badly - just amused to see the running commentary.  your repo is your repo and i have no bones to pick there. eventually you'll leave as well.
i was solving problems i had with your previous code. it was primarily for myself but i put it up in hopes it would help someone else as well. i am glad it eventually led to an update others might find useful too.
i do like the handlers and will be testing your new code to see if it works as i need.

just amused to see the running commentary.

Again, not supposed to be commentary, it’s a review.
If you check my profile, you might notice a lot of my time is spent on reviews and fixes, mostly maintaining Homebrew Cask. It’s an important part of the process. It’s also one that takes long, so it’s done when improvement is expected. If I didn’t care for and appreciate your contribution, I wouldn’t have bothered.

eventually you'll leave as well.

True, even if by death. But the important distinction is that while this is connected to my account, any issues that need solving will fall on my plate and time, not the ones of previous contributors, so I need to ensure contributions are things I can stand behind.


Develop Documentation Welcome Page

What?
Develop the welcome page in GitBook.
Why?
Will need have a friendly welcome page that can help guide users to the documentation that they need.
How?

To be done in Gitbook.

Acceptance Criteria
A welcome page in Gitbook.
Related Issues

#891 is related because the outcome will inform the development of this ticket.

Welcome page and table of contents mocked up here: https://open.gitbook.com/~space/HUyD42K5NtJHpS8Pytvl


Implement WebSocket client

Closes https://github.com/http4s/http4s-dom/issues/6.
Tests forthcoming.

Ok, this is getting closer. The weirdest issue right now is that the echo web server isn't consistently echoing all the messages. Or at least, they are not being received. Firefox flip-flops between receiving only the first two or all three, whereas Chrome consistently receives only the first one.

Update: the problem seems to be the ember websocket echo server I'm running within sbt, since sending to https://echo.websocket.events seems to work perfect. Running an IO within sbt is generally dodgy, of course 😩

The problem seems to be with ember server's websocket implementation. Switching to blaze works for now 👍

I'm unable to reproduce the problems with Ember server locally. I tried setting the JVM flag -XX:ActiveProcessorCount=1 to more accurately imitate CI but no dice. Maybe just a weird CI thing, idk 🙃

Should be good to go. This adds minimal public API, so there's only room for implementation errors 😆


Change 'PI' to 'pi' in two classes.

Hi,
When building any app with 'great_circle_distance' package it fails. The reason of error is 'PI' which should be 'pi' The two classes are -spherical_lawofcosines.dart and great_circle_distance_base.dart.

Yes, I am facing the same problem.


Add redis humbug reports processing via cli command.

Document describing changes in this PR

@bugout-dev check

[ ] Add env variable to AWS Parameter Store

For test required:
spire branch:
https://github.com/bugout-dev/spire/tree/redis-reports-chache
enviroment variable1:
BUGOUT_REDIS_URL [like localhost:6379]
BUGOUT_REDIS_PASSWORD str
REPORTS_CHUNK_SIZE int default 100
WATING_UNTIL_NEW_REPORTS int default 10
Run loop
python3 -m drones.cli humbug_reports upload_pool
After just send correct reports to spire/humbug endpoint they push to queue

@bugout-dev check

[ ] Redis should start on startup on drones server
[ ] Systemd service which runs python3 -m drones.cli humbug_reports upload_pool

Docs about that pullrequest:
https://docs.google.com/document/d/1y7yp8gKfgRaBkX-xLucwd-Wosk4zICOkaLw6bxHZwXI/edit?usp=sharing

Currently have the following environment variables in parameter store:

BUGOUT_REDIS_PASSWORD
BUGOUT_REDIS_URL
REDIS_FAILED_REPORTS_QUEUE
REDIS_REPORTS_QUEUE
REDIS_REPORTS_CHUNK_SIZE
WAITING_UNTIL_NEW_REPORTS
(among others)


Add UTF-16 option to Base64 encoder/decoder

Adds the UTF-16 encoding type to the Base64 encoder/decoder
Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[X] New feature or enhancement
[ ] UI change (please include screenshot!)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Internationalization and localization
[ ] Other (please describe):

What is the current behavior?
The Base64 encoder/decoder does not support UTF-16 encoding.  This encoding is commonly used when working with PowerShell as it supports encoding commands using the powershel.exe -EncodedCommand option.
Issue Number: https://github.com/DevToys-app/DevToys/issues/661
What is the new behavior?

Adds UTF-16 support

Other information
This only adds support for UTF-16LE with BOM (System.Text.Encoding.Unicode).  I considered adding UTF-16LE and UTF-16BE explicitly as well, but felt that might clutter the UI with too many options.  I think UTF-16LE BOM will be sufficient for most use-cases (PowerShell supports UTF-16LE with BOM).
Quality check
Before creating this PR:

[X] Did you follow the code style guideline as described in CONTRIBUTING.md
[X] Did you build the app and test your changes?
[ ] Did you check for accessibility? On Windows, you can use Accessibility Insights for this.
[X] Did you verify that the change work in Release build configuration
[ ] Did you verify that all unit tests pass
[ ] If necessary and if possible, did you verify your changes on:

[X] Windows
[ ] macOS
[ ] Linux

I realized I failed to actually output the BOM when encoding a Unicode string.  As I've been going through to add that I've found some existing code in the codebase that I have questions about.
In the Base64Helper.FromBase64ToText it looks like we're encoding the UTF-8 preamble (using Encoding.Unicode) and including it in encoded output?
https://github.com/DevToys-app/DevToys.Tools/blob/main/src/DevToys.Tools/Helpers/Base64Helper.cs#L123-L143
I've found the related issue (https://github.com/DevToys-app/DevToys/issues/342) and PR (https://github.com/DevToys-app/DevToys/pull/378) that appears to have driven this change.
I find it strange that the preamble is included in the plain-text output.  The Preamble seems like it should be an implementation detail of the encoding when converting characters to bytes.  The same string could be encoded with or without a preamble depending on the encoder settings.


OMG-363 - Watcher get.block by number

:clipboard: PLAN-51
As a block explorer, I would like to receive the content of all transactions inside a child chain block based on block number, so that I have a better way to visualize transactions based on historical data.

hm, wait, we have https://developer.omisego.co/elixir-omg/docs-ui/?url=master/informational_api_swagger.json#/Transaction/getTransactionsAll where we can filter by blknum.

It doesn't server all the details (we agreed at one point that for details one should rather iterate on transaction.get(hash)
it is subject to the limits (200 max I think), so it would require pagination to be fully usable I suppose
it doesn't mimic block.get from the child chain, which was the plan at some point, but I think this is not what we want here because we want to "receive the content of all transactions inside a child chain block"

So either I'm missing something or perhaps the existing endpoint will do (with the extension of pagination)

as discussed, only pagination is missing #725


Make Reload add-in button.

Comment from @larmarange:

I didn't find any button to change the selected data.frame. If I selected the wrong data frame, I have to close the addin and to restart it

TODO:
-> Make reload button (to re-select variable)

Added reload button


Combination loadBalancerSourceRanges and ECMP doesn't work

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
When a service that specifies loadBalancerSourceRanges is used then some (~25-50%) connect fails if ECMP is used to load-balance incoming traffic between K8s nodes.

If ECMP is not used but with loadBalancerSourceRanges it works
If loadBalancerSourceRanges is not used but with ECMP it works
Same setup works with other CNI-plugins, for example calico, flannel and antrea

So, it's just the combo loadBalancerSourceRanges+ECMP that doesn't work on cilium.
Service manifest;
apiVersion: v1
kind: Service
metadata:
  name: mserver-dual-srange
spec:
  loadBalancerSourceRanges:
  - "<IP_ADDRESS>/24"
  - "<IP_ADDRESS>/24"
  - "1000::1:<IP_ADDRESS>/120"
  - "1000::1:<IP_ADDRESS>/120"
  ipFamilyPolicy: PreferDualStack
  selector:
    app: mserver-deployment
  ports:
  - port: 5001
    name: mconnect
  - port: 5003
    name: ctraffic
  type: LoadBalancer

Example test with mconnect;
# mconnect -address <IP_ADDRESS>:5001 -nconn 100
Failed connects; 53
Failed reads; 0
mserver-deployment-67fb4fc9cf-kgdlz 9
mserver-deployment-67fb4fc9cf-xzf9s 15
mserver-deployment-67fb4fc9cf-qdstc 10
mserver-deployment-67fb4fc9cf-fkdr8 13

Same with Antrea CNI-plugin;
# mconnect -address <IP_ADDRESS>:5001 -nconn 100
Failed connects; 0
Failed reads; 0
mserver-deployment-67fb4fc9cf-8wpl5 24
mserver-deployment-67fb4fc9cf-hct49 25
mserver-deployment-67fb4fc9cf-4f6lp 26
mserver-deployment-67fb4fc9cf-8pskn 25

Cilium Version
# kubectl exec -n kube-system   cilium-5vrgf -- cilium version
Defaulted container "cilium-agent" out of: cilium-agent, mount-cgroup (init), clean-cilium-state (init)
Client: 1.11.6 fee2d77 2022-06-13T16:02:58-07:00 go version go1.17.11 linux/amd64
Daemon: 1.11.6 fee2d77 2022-06-13T16:02:58-07:00 go version go1.17.11 linux/amd64

Kernel Version
# uname -a
Linux vm-001 5.18.1 #8 SMP PREEMPT_DYNAMIC Sat Jun 18 12:53:37 CEST 2022 x86_64 GNU/Linux

Kubernetes Version
# kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.2", GitCommit:"f66044f4361b9f1f96f0053dd46cb7dce5e990a8", GitTreeState:"clean", BuildDate:"2022-06-15T14:22:29Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.2", GitCommit:"f66044f4361b9f1f96f0053dd46cb7dce5e990a8", GitTreeState:"clean", BuildDate:"2022-06-15T14:15:38Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}

Sysdump
No response
Relevant log output
No response
Anything else?
Cilium manifest quick-install.yaml.txt
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Update
It seems like traffic to that enters some K8s nodes (seemingly random) is dropped. So scratch;
~If ECMP is not used but with loadBalancerSourceRanges it works~
I was fooled because I happened to test a node that worked.
My routing with ecmp;
# ip ro
default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/24
        nexthop via <IP_ADDRESS> dev eth1 weight 1
        nexthop via <IP_ADDRESS> dev eth1 weight 1
        nexthop via <IP_ADDRESS> dev eth1 weight 1
        nexthop via <IP_ADDRESS> dev eth1 weight 1
...

In this particular run traffic worked to <IP_ADDRESS> and <IP_ADDRESS> but not to <IP_ADDRESS> and <IP_ADDRESS>. So when using ECMP ~50% traffic was lost.

@uablrek Thanks for opening the issue. That's weird. Maybe you could attach Cilium's sysdump?

FYI, I am using a setup where the K8s master is not a K8s-node;

This works fine with cilium except for web-hooks. I don't think the problem in this issue is caused by this though (I suspect a race somewhere).
This setup is very convenient since it decouples setup for example etcd and master-HA from the cluster. I believe AWS uses a similar setup. IMHO cilium should support it (including web-hooks).

Yes, the normal K8s way. I use kube-proxy replacement, not DSR. Note that this setup work fine without loadBalancerSourceRanges so it's nothing wrong with the test or the system. Only that the precense of loadBalancerSourceRanges seem not to work.

In your sysdump I see many drops due to the LB src range check. My gut feeling is that the dropped packet src IP is something else than the LB allows (thus, my ask for the cilium monitor output).
What is the client IP addr?

Most likely not. Note that the communication fails depending on the receiving K8s node, not the source. An also that the exact same test works with other CNI-plugins.

Tcpdump on a K8s when it fails;
# tcpdump -ni eth1 host <IP_ADDRESS>
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), snapshot length 262144 bytes
12:50:38.639110 IP <IP_ADDRESS>.44582 > <IP_ADDRESS>.5001: Flags [S], seq<PHONE_NUMBER>, win 64240, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr 0,nop,wscale 6], length 0
12:50:39.658679 IP <IP_ADDRESS>.44582 > <IP_ADDRESS>.5001: Flags [S], seq<PHONE_NUMBER>, win 64240, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr 0,nop,wscale 6], length 0
12:50:41.674830 IP <IP_ADDRESS>.44582 > <IP_ADDRESS>.5001: Flags [S], seq<PHONE_NUMBER>, win 64240, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr 0,nop,wscale 6], length 0

Source is <IP_ADDRESS> which match "<IP_ADDRESS>/24".

Side-remark; there is no problem with ipv6. Only ipv4.

Narrowed output from cilium monitor;
>> IPCache entry upserted: {"cidr":"::/0","id":2,"old-id":2,"encrypt-key":0}
xx drop (Denied by LB src range check) flow 0x0 to endpoint 0, , identity world->unknown: <IP_ADDRESS>:57372 -> <IP_ADDRESS>:5001 tcp SYN
xx drop (Denied by LB src range check) flow 0x0 to endpoint 0, , identity world->unknown: <IP_ADDRESS>:57372 -> <IP_ADDRESS>:5001 tcp SYN
xx drop (Denied by LB src range check) flow 0x0 to endpoint 0, , identity world->unknown: <IP_ADDRESS>:57372 -> <IP_ADDRESS>:5001 tcp SYN
^C
Received an interrupt, disconnecting from monitor...

Same on a working node;
level=info msg="Initializing dissection cache..." subsys=monitor
-> overlay flow 0x0 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip <IP_ADDRESS>: <IP_ADDRESS>:36272 -> <IP_ADDRESS>:5001 tcp SYN
-> overlay flow 0x0 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip <IP_ADDRESS>: <IP_ADDRESS>:36272 -> <IP_ADDRESS>:5001 tcp ACK
-> overlay flow 0x0 , identity remote-node->unknown state new ifindex cilium_vxlan orig-ip <IP_ADDRESS>: <IP_ADDRESS>:36272 -> <IP_ADDRESS>:5001 tcp ACK

I can't see any "src range check" logs at all.

Any idea why the request is received over the vxlan tunnel?

No. I have no unusual routes or iptables rules. And IPv6 works, which should be taken into account.

Still a problem, please see https://cilium.slack.com/archives/C53TG4J4R/p1702116817784589.
I don't use the setup described in https://github.com/cilium/cilium/issues/20297#issuecomment-1169681515 any more. The controller is in-cluster (as the normal setup). And I use cilium:v1.14.0.
The problem seem general, to many connect in a short time makes some connects drop, but it is made worse by some setups.


Fix #128: Changed the link to wayback machine version

I have changed the link which was not working to the wayback machine version.

@U8NWXD @seanlip  PTAL.

@seanlip I have changed the link text, PTAL, thanks.


need a little help not much

hi i have and id conflict and i need a little bit of help with your experience with enchantment ids this is not a bug however i do know how to fix it i just need to know ho high your mod increase the enchantment ids
or does it even do that at all

it will be a lot of help

for my personal modpack for myself

there are a lot more mods to this  so ya it would help a lot

found an id it is 100 id closing the issue


SDC: Add set_max_delay command

This PR add basic support of the set_max_delay command.
It depends on #38 with the SdcWriter class.

CI is red. Initial plugin seems ok, but I'm worried that we are missing something.

CI is red because this PR depends on/shouldn't be merged before #38.

For now I believe let's let this through, and as problems arise we'll address them.

I fully agree with that


cython doesn't correctly generate C extension with name different from py file

In my setup.py I have the following code:
    from Cython.Build import cythonize

    extensions = [
        Extension("distributed._cy_schedulerstate",
                  ["distributed/schedulerstate.py"])
    ]
    ext_modules = cythonize(extensions)

    setup(..., ext_modules=ext_modules)

The idea is that i can choose at runtime between the pure Python version (distributed.schedulerstate) and the Cython-accelerated version (distributed._cy_schedulerstate). Unfortunately the C extension fails loading:
>>> from distributed import _cy_schedulerstate
Traceback (most recent call last):
  File "<ipython-input-3-6878069d7b91>", line 1, in <module>
    from distributed import _cy_schedulerstate
ImportError: dynamic module does not define module export function (PyInit__cy_schedulerstate)

And indeed the C code generated by Cython doesn't use the extension name defined in the Extension constructor:
#if PY_MAJOR_VERSION < 3
PyMODINIT_FUNC initschedulerstate(void); /*proto*/
PyMODINIT_FUNC initschedulerstate(void)
#else
PyMODINIT_FUNC PyInit_schedulerstate(void); /*proto*/
PyMODINIT_FUNC PyInit_schedulerstate(void)

The only thing that came in mind as soon as I read _cy_schedulerstate is private variables, even though it should work with two underscores than one.
Could it somehow got confused during parsing?

Might seem like an obvious bug but it isn't that easy. cythonize() has several features that make its interface a little ... special. You can use file patterns, for example, as in Extension("**/*.pyx"). That makes it less obvious to decide (in a user understandable way) when the module name should be overridden. I hope I found a safe way to implement this.


AttributeError: module 'scipy' has no attribute '_lib'

Hello, I encounter the following error for Scipy. Does anyone know the reason? Tks.
~\anaconda3\envs\env_backtrader\lib\site-packages\scipy\_lib\_threadsafety.py in decorate(self, func)
     43             with self:
     44                 return func(*a, **kw)
---> 45         return scipy._lib.decorator.decorate(func, caller)
     46
     47

AttributeError: module 'scipy' has no attribute '_lib'

scipy_lib_threadsafety.py is not a file that's present in SciPy, and apparently it's buggy. You will have to figure out how that got there and how it's called.
It may be a case of import scipy._lib missing there.

@rgommers tks.

@rgommers check out the issue with the formatting fixed. scipy\_lib\_threadsafety.py comes out as one word in markdown because windows uses \ as the directory seperator.
The line of code that's failing is here:
https://github.com/scipy/scipy/blob/2ed8169c5c4c9181cd38a52db614c692eb802c15/scipy/_lib/_threadsafety.py#L45
But the correct includes are definitely there at the top of the file, so I can't see why it would fail.

comes out as one word in markdown because windows uses \ as the directory seperator.

arghh

But the correct imports are definitely there at the top of the file, so I can't see why it would fail.

Yes maybe an install issue or something, or off-label use somehow (embedded interpreter or whatever).
@kianhongT if you want a better guess you'll need to give us more details, like how you installed SciPy and the code you're running to trigger this issue.

@rgommers @peterbell10 I'm unable to debug the error so I uninstalled and re-installed everything again. Then I ran the code and it worked. haha. Many thanks for your input, guys.


When executing test use a different database name

To avoid accidentally dropping the production database if "make test" is being executed on a production machine.

It's already in the refactor roadmap see related issue


NIFI-7892 Created a Logout page to inform users of a complete logout …

…when OIDC is configured.
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Created a new Logout page that informs users of a complete logout when NiFi is configured to use OIDC for authentication.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically main)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[x] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Reviewing...

Tested this out with LDAP, works great.

+1 tested with OIDC and all looks good, going to merge, thanks!


[Discuss] Why did emittedByOrder been deprecated ?

Question:

Why did emittedByOrder been deprecated ?
How to get ordered events with emitted ?

wrapper.emittedByOrder() // => [{name: 'a', args: [1]}, {name: 'b', args: [3]}, {name: 'a', args: [2]}]
wrapper.emitted() // => {a: [[1], [2]], b: [[3]]}

It seems that emitted cannot cover cases where we want to ensure order across different event types, eg. I want to ensure the order of the following event sequence:
emit('click')
emit('change', 1)
emit('invalid', 1)

...while emitted works if we want to check order for a same event type. Not sure why emittedByOrder is marked as deprecated.

It seems that emitted cannot cover cases where we want to ensure order across different event types, eg. I want to ensure the order of the following event sequence:
emit('click')
emit('change', 1)
emit('invalid', 1)

...while emitted works if we want to check order for a same event type. Not sure why emittedByOrder is marked as deprecated.

Hi! Thanks for raising this up.
Could you share a use case where asserting unordered emitted events vs. asserting them ordered yields a fragile test (or a false positive)? I understand why asserting the order seems reasonable, but I'm not entirely sure it is that critical or that it could yield to fragile tests.
Thank you! 🤗

Hi! Thanks for raising this up.
Could you share a use case where asserting unordered emitted events vs. asserting them ordered yields a fragile test (or a false positive)? I understand why asserting the order seems reasonable, but I'm not entirely sure it is that critical or that it could yield to fragile tests.
Thank you! 🤗

Suppose there is a custom input component which will emit input event with value and invalid event with error message when user inputs.
Component:
<custom-input v-model="value" :minlength="2" />

Test:
cy.get('input').type('Hello');
// -----------
let events = wrapper.emittedByOrder()
expect(events[0].name).to.equal('input')
expect(events[0].args[0]).to.equal('H')
expect(events[1].name).to.equal('invalid')
expect(events[1].args[0]).to.equal('too short')
expect(events[2].name).to.equal('input')
expect(events[2].args[0]).to.equal('e')
expect(events[3].name).to.equal('invalid')
expect(events[3].args[0]).to.equal('too short')
expect(events[4].name).to.equal('input')
expect(events[4].args[0]).to.equal('l')
expect(events[5].name).to.equal('input')
expect(events[5].args[0]).to.equal('l')
expect(events[6].name).to.equal('input')
expect(events[6].args[0]).to.equal('o')


Fedora 42 change: composefs enabled by default

For the upcoming Fedora 41 release, we are enabling composefs by default for bootable container images of Fedora Atomic Desktops (not for the classic ostree ones).
See:

https://fedoraproject.org/wiki/Changes/ComposefsAtomicCoreOSIoT
https://gitlab.com/fedora/ostree/sig/-/issues/35

It's enabled in the Rawhide/41 images from ci-test: https://gitlab.com/fedora/ostree/ci-test/-/blob/main/composefs.yaml?ref_type=heads
Before we move people to composefs, we need them to have a BLS capable bootloader (i.e. an updated open), have BLS config enabled and then set sudo ostree config set sysroot.bootloader none. If some of those things are not set, you might end up with a completely unbootable system (i.e. no rollback either).
See:

https://gitlab.com/fedora/ostree/sig/-/issues/35#note_1986555833
https://discussion.fedoraproject.org/t/f41-change-proposal-enabling-composefs-by-default-for-atomic-desktops-coreos-and-iot-self-contained/123166/18

So this is tricky as we don't have a mechanism in Atomic Desktops like we do in Fedora CoreOS to force updates through a barrier releases that would validate all of those elements before updating to a composefs enabled image and setting the ostree repo config.
If that ends up being too much for the F41 release, we can postpone it to F42 or dynamically disable it in a layer (needs an initramfs rebuild).

I've pushed F41 images, and they come with composefs enabled by default.
We don't have a real plan for the transition from F40 yet so we might have to disable it until we do.
See: https://gitlab.com/fedora/ostree/sig/-/issues/35#note_1986555833

WARNING: Rebasing to those images may make your system unbootable / un-upgradeable.

Hi Timothee! Greetings from KubeCon in Hong Kong!
We usually don't ingest on our builds until the beta (For F41 in this case) so no one will be rebasing yet.
From a future proof perspective do we need to manually set ostree config set sysroot.bootloader none for folks? Is this something we can automate in the containerfile? Thanks!

Hi Timothee! Greetings from KubeCon in Hong Kong!

👋🏻

From a future proof perspective do we need to manually set ostree config set sysroot.bootloader none for folks? Is this something we can automate in the containerfile? Thanks!

We can not automate that in the Containerfile, we need this in a system unit running on the systems.
But doing that also means making sure that the bootloader is updated before and BLS properly enabled in the GRUB config.

So in theory, we need a systemd script that somehow (and I know nothing about bootloaders or BLS):
Checks if BLS is enabled and the bootloader is a suitable version
If yes, run ostree config set sysroot.bootloader none
If no, pin the user on their current image and inform the user (or try and remediate it ourselves)

Yes, something like that.
Updating the bootloader is almost the same as having bootupd and this is only in F41, and it does not handle RAID mirrors yet (https://github.com/coreos/bootupd/issues/132) and I've not tested the setup that Anaconda does for RAID mirror.

Summary of what's needed for F41 for the Atomic Desktops to converge with bootc on:

bootupd: https://gitlab.com/fedora/ostree/sig/-/issues/1#note_2062751164
composefs: https://gitlab.com/fedora/ostree/sig/-/issues/35#note_2062769940

The 100% Code Complete Deadline for Fedora 41 is tomorrow and we are not ready with the transition plan for this change in the Atomic Desktops thus I'm pushing this back to Fedora 42.

@bsherman Heads up that this will still affect uCore.

As part of this change, we will be migrating the Atomic Desktops to a static GRUB config file (Fedora CoreOS / uCore already use a static GRUB config file).
While using a static GRUB config file is not strictly needed for composefs, it is currently the only workaround that we have for https://bugzilla.redhat.com/show_bug.cgi?id=2308594, which is not making progress right now.
The current work in progress script for this migration is in https://hackmd.io/B8lMCzLFQjGgr5jhl_Iw-w. Testing welcomed.
The plan is to push that to Fedora Rawhide first, then Fedora 41, to migrate systems ahead of the Fedora 42 release, which will enable composefs by default. This should maximize the opportunity for users to have their system migrated to a static GRUB config or find out that the migration did not succeed (which is something only accessible to advanced users unfortunately) before the switch to composefs in F42 which will block updates if the system has not been migrated.


Bolt connection on non-default port - different behavior between neo4j server and desktop

To avoid opening neo4j ports on firewall, I'm trying to use nginx to port forward port 80 traffic to neo4j. This works in browser but not in Desktop
ie.
project-neo4j.domain.com:80 to local neo4j server on 7474
project-bolt.domain.com:80 to local neo4j server on 7687
So I can then access browser via web server on
http://project-neo4j.domain.com/browser/
once I've changed Connect URL to
bolt://project-bolt.domain.com:80
(default port not accessible through firewall but this works)
HOWEVER in Bloom you get this error if you specify a different port

ServiceUnavailable: WebSocket connection failure. Due to security constraints in your web browser, the reason for the failure is not available to this Neo4j Driver. Please use your browsers development console to determine the root cause of the failure. Common reasons include the database being unavailable, using the wrong connection URL or temporary network problems. If you have enabled encryption, ensure your browser is configured to trust the certificate Neo4j is configured to use. WebSocket readyState is: 3

Ideally what I'd like to do is configure the server so that the default settings specify my non-standard ports in the connection settings in the client WITHOUT changing the server's listening ports (which I haven't changed from the defaults).

I should add that part of the reason for this is that I've got different neo4j servers behind the firewall so simply opening up the neo4j ports on the firewall doesn't scale in this instance.

Hi! Thanks for reporting
Just so we can completely understand what you are trying to do, are you running Bloom from Neo4j Desktop, hosted by the Bloom Neo4j plugin or just self hosted web assets?
If it's Desktop, are you using a remote graph pointed to bolt://project-bolt.domain.com:80?

Yes running Bloom from Desktop with that url and encrypted connection checked. Will Test non encrypted and report back.

Did you manage to get it working? Have you tested without encrypted connection?

Closing b/c of inactivity


error: github.repos.getAll is not a function

I'm reading 'chapter6 > testing > adding new book' but when i implement my web app locally, I can't see a list of 'github repo'. Also, there is an error(error: github.repos.getAll is not a function) in terminal. Please help me. Thanks in advance.

@slkjer Thanks for reporting. Which version of @octokit/rest do you use?
Check version here: https://github.com/builderbook/builderbook/blob/master/book/6-end/package.json#L20
I think authors renamed many methods.
If you use version of @octokit/rest that is newer than that in the book (15.15.1) then you should use github.repos.list. See official docs: https://octokit.github.io/rest.js/#api-Repos-list

Thanks for replying, Tima.
As you mentioned, i've replaced github.repos.getAll with github.repos.list
and it does work well.
But there is an another error when i press 'SYNC WITH GITHUB' Button.
I try to use getContents and listCommits instead of getContent and
getCommits, but i can see an error again.
I feel like the problem is getting bigger :(
I'm using 16.2.0 version of @octokit/rest because i've installed all
packages with the latest version..
Is it the best way to change the version of octokit?
Thanks for helping me :)

@slkjer No problem.
Yes! It would be best to change the version to 15.15.1
We will upgrade all packages and make code changes at the end of December.

I'm sorry .. i made a mistake in Github files.
That's why there was an error.
Now everything is good.
Thank you, Tima :)


Add CODEOWNERS, marking data plane as owners.

This will assign the data plane team as a reviewer, and auto-assign two randomly chosen members like in beats.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-05-12T19:29:47.897+0000

Duration: 8 min 5 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
710

Skipped
5

Total
715

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.


Add unratified Zacas extension

This PR adds support for the unratified fast-track Zacas extension that introduces the following instructions:
amocas.w for RV32 and RV64
amocas.d for RV32 and RV64
amocas.q for RV64 only
The specification is here: https://github.com/riscv/riscv-zacas

@ved-rivos  please change target branch to dev branch. Please see the new CONTRIBUTION Guidelines and requirements in CHANGELOG.md as mentioned in the upstream dev branch. Once done this can be merged.

@neelgala thanks. I have rebased to dev branch.


Support autoFocus attribute in React-wrapped components

Feature request
When using react component bindings, the autofocus/autoFocus prop does not work on <VSCodeTextArea> and <VSCodeTextField>.
Expected behavior
React components <VSCodeTextArea> and <VSCodeTextField> should accept an autoFocus prop which causes the components to focus when mounted.
Current behavior
Note: React polyfills the autoFocus attribute on normal input elements so that they can be consistent and work with mounting component beyond just the first page load. It appears this polyfill does not happen when using with VSCodeTextArea and VSCodeTextField.
You can provide autofocus without a typescript warning, and it will add autofocus to the innermost <textarea> of the <vscode-text-area>. However, this doesn't have the intended effect: the text area is not focused when added to the DOM (because the HTML attribute only applies on first page load in most browsers).
It's possible to work around this issue by re-implementing this behavior using react hooks, however it's quite annoying to do so. (This is a separate issue but refs are difficult to use with this library because of the types of components—you have to do an ugly type cast to make it work)
Use case
It's very common to auto-focus text areas and text fields in forms that you want people to fill out. This is a common react idiom, so not having this makes the textarea/textfield components feel like weird bespoke components instead of acting like textareas and textfields that we're used to using.
Screenshots/references
To test this in an isolated environment, I added a <VSCodeTextArea autofocus>Text Area!</VSCodeTextArea> to the vscode-webview-ui-toolkit sample create-react-app project.
When you launch the webview, it does not auto-focus the text area.

Thanks for filing, @evangrayk. We'll take a look at this and will report back 👍

any way to do a inputRef.current.focus()
when component is mounted?

ref and itemRef doesn't seem to work

I'd like to make the textarea increase height automatically. However, the ref is hard to use:
const textareaRef = useRef<HTMLInputElement>(null);
<VSCodeTextArea ref={textareaRef} ...

and there's an error:
Type 'RefObject<HTMLInputElement>' is not assignable to type 'LegacyRef<Component<PropsWithChildren<Partial<Pick<TextArea, "normalize" | "form" | "slot" | "template" | "title" | "animate" | "className" | "required" | "hidden" | "dir" | "blur" | "click" | "focus" | ... 296 more ... | "handleTextInput">> & ReactEvents<...> & HTMLAttributes<...> & { ...; }>, {}, any>> | undefined'.
  Type 'RefObject<HTMLInputElement>' is not assignable to type 'RefObject<Component<PropsWithChildren<Partial<Pick<TextArea, "normalize" | "form" | "slot" | "template" | "title" | "animate" | "className" | "required" | "hidden" | "dir" | "blur" | "click" | "focus" | ... 296 more ... | "handleTextInput">> & ReactEvents<...> & HTMLAttributes<...> & { ...; }>, {}, any>>'.

But I don't know how to cast it ..

Hi all,
I'm very sorry to say that the toolkit is being deprecated and all active development will be coming to a close.
There was an announcement last week where you can learn more details and leave any questions or comments you may have.
Beyond that, thank you so much filing this issue and apologies for never getting around to addressing it. It means a lot that you contributed to the improvement of this project. I wish you all the best in your future VS Code extension endeavors!


In Solution Explorer the foreground of selected row, should be dark

As shown in the attached screenshot, the white foreground in selected row is less readable.
Thanks in advance.

I have resolved this and published an update v1.2.1

It works fine, thanks.


Installer ISO

How to install this OS and is it supporting .NET binaries?

How to install this OS

Because project is still in development you can try latest test build by building it from source code Wiki

is it supporting .NET binaries

Not really

What's the reason for it to be .net or C Sharp then

.NET are specific to windows platform. But any C# code/library compiled using Atomix Compiler will work.

Who was the US made for what kind of users I mean is it true a production lol I can't replace Ubuntu or Windows or is it more like a devil Upland operating system

Sorry speech to text is worse then google translate :D

Seems like topic of this issue is now closed. You can discuss about project on IRC channel. Join me in #atomos on freenode.net


add SERVICE_DIRECTORY_MULTI_CATEGORY_SELECT context to context processor

Coverage increased (+0.3%) to 37.344% when pulling bfc0d87a4457f310a1b139d4b01e9683e078dc9f on feature/multi-category-service-directory-search into 64d676885c8d090f60d87c0686d8e2c69541a66e on develop.


Fix aggregates variables.

I was too fast and used same vars as in Incidets, which is incorrect
because Aggregate shedule jobs with multiple incidents contained
So we need array of URL's

This PR should fix displaying it within openQA: https://github.com/os-autoinst/openQA/pull/4599


Extension not operative without refresh after fresh installation

Zen Mode icon/menu not visible at first without viewing a conversation.
@liatzionimorad consider this if bug can't be fixed right now.

There is no option of extension visible without refresh .
Dev: this limitation is present in all extensions.
Suggested solution : Inject the extension immediately after the first installation with forced refreshing the WhatsApp page.
Task 74
The initial result of the team is 2 hours
2) In our experience, the team's estimate error is 30%.
2 x 1.3 = 3
3.) Our insurance rate is 30%.
3 x 1.3 = 4
Full optimistic estimate out of 2 pessimistic out of 4 hours
approved

Please evaluate the following additional requirements before automatic refresh :
This dialog only appears immediately after installation.
It does not appear for existing users of Zen Mode:
You need to refresh Whatsapp Web for Zen Mode to work.
Do you want to do it now?"
Two buttons:
"Yes please"
"Not now"
Only If the user presses Yes please -> we inject the extension immediately after installation with force refreshing the WAW page .
In Hebrew:
"יש צורך ברענון  ווטסאפ וב כדי שזן מוד יתחיל לעבוד"
"האם תרצה לעשות זאת כרגע?"
Buttons:
"כן בבקשה " (for yes)
" לא כרגע " (for no)

The initial result of the team is 2-3 hours
2) In our experience, the team's estimate error is 30%.
2 x 1.3 = 3
3.) Our insurance rate is 30%.
3 x 1.3 =4
Full optimistic estimate out of 2 pessimistic out of 4 hours


Incorrect agent result - pretty sure not a bot.

Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 10.0; WOW64; Trident/7.0; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; Tablet PC 2.0; Zoom 3.6.0; Microsoft Outlook 16.0.4954; Microsoft Outlook 16.0.4954; ms-office; MSOffice 16)

(although I could be wrong - have not analyzed the behaviour intensively)

Closed as not entirely sure - probably is a bot.


added add_graph_from_neo4j #226

Added method to add a Neo4j subgraph to a Cytoscape graph. Added example notebook.

Fix lin issues


bug: Error while generating a wasm

Did you check existing issues?

[X] I have read all the tree-sitter docs if it relates to using the parser
[X] I have searched the existing issues of tree-sitter-php

Tree-Sitter CLI Version, if relevant (output of tree-sitter --version)
tree-sitter 0.22.6 (b40f342067a89cd6331bf4c27407588320f3c263)
Describe the bug
scanner.c:1:10: fatal error: '../../common/scanner.h' file not found
    1 | #include "../../common/scanner.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
emcc: error: '/emsdk/upstream/bin/clang -target wasm32-unknown-emscripten -fignore-exceptions -fPIC -mllvm -combiner-global-alias-analysis=false -mllvm -enable-emscripten-sjlj -mllvm -disable-lsr --sysroot=/emsdk/upstream/emscripten/cache/sysroot -DEMSCRIPTEN -Werror=implicit-function-declaration -Xclang -iwithsysroot/include/fakesdl -Xclang -iwithsysroot/include/compat -Os -fno-exceptions -fvisibility=hidden -I. scanner.c -c -o /tmp/emscripten_temp_04ryzxba/scanner_0.o' failed (returned 1)
emcc command failed

The issue seems to be have been fixed as part of PR#3337, but it is still throwing an error.
Steps To Reproduce/Bad Parse Tree
I run this command npx tree-sitter build --wasm node_modules/tree-sitter-php/php/ --output tree-sitter-php.wasm, which results in the above error.
Expected Behavior/Parse Tree
Successful build and WASM gets generated.
Repro
No response

I can confirm if npx tree-sitter --version shows that it's 0.22.6 it works, you are probably on an older version

@amaanq I have mentioned the version in the issue description which is 0.22.6, and it is not working.


Bot doesn't seem to get PokeBalls

Started using pokecli.py -a google -u XXXXX -p XXXXX -c 1 the bot is finding lots of Pokemon but not PokeBalls. Do I need to specify additional parameter when I start or not?

If you run out of pokeballs the bot will automatically go to pokestops and get pokeballs again. (e.g. working on dev branch)

What's the default mode if not specified?

@s1x ?


unbounded type is not strict

TypeScript Version:  4.0.2

Search Terms: unbounded
Code
type Strings = [string, string];
type Numbers = number[];

type Unbounded = [...Strings, ...Numbers, boolean];
//   ^?

const data: Unbounded = ['a', 'b', false, false]; // <-- No error?
console.log(data);

Expected behavior:
The above Unbounded type should allow only the last element in the tuple as boolean, other elements in range [2, -2] if available should be numbers only.
Actual behavior:
[...number[], boolean] is now handled as <number | boolean>[]
Playground Link:
https://www.typescriptlang.org/play?#code/C4TwDgpgBAysBOBLAdgcwM5QLxQNroRVQBooCk0BdAbgChRIoA5AVwFsAjCeTHZdrvFw1a9cNACqyDgHsWyACYQF2PADoNcChlIa1rTt3SlZMgDYQAhshEB6W1EcA9APyiAxjOQEoCy8EsALigpWXklFRxcAHJLaNJojnioADNLM3QIUjSMiBFPb3MINTMZVAAKPwCASmogA
Related Issues:
No.

Tuple types don't support this operation, but we should be issuing the same error at the declaration site as we would if there wasn't a type alias used here
Shorter
type Numbers = number[];
type Unbounded = [...Numbers, boolean];
const data: Unbounded = [false, false];

Tuple types don't support this operation

This seems opposite of the update in 4.0 doc:

The second change is that rest elements can occur anywhere in a tuple - not just at the end!

Previously, rest elements could only occur at the end. Now, that can occur anywhere, as long as they meet the criteria of either being bounded-length tuples themselves, or being type parameters.

Thanks for the reply.

as long as they meet the criteria of either being bounded-length tuples themselves, or being type parameters.

Should this be mentioned in the doc? Or, the Unbounded example used in Variadic Tuple Type looks inappropriate, IMHO.


Integration with spring-state-machine for simple bpm engine

it will be like a stateless bpm. With custom dsl we could register some flow like:
functionFlow {
  consumer(name: 'somename', transport: queue|http, port:9000){
    if (response == 'foo'){
      payload = payload + 'foo')
      send('logger')
    } else send('nop')
  }

  consumer(name: 'logger', transport: queue|http, port:9000){
    println "LOG: $payload"
  }
}

inner {} is a groovy closure, what can be dehydrated(serialized)

Ping @kbastani because he already has his hands dirty with SSM and SCFn.

@zotona Happy to chat. Take a look at this example I put together that is pre-SCF https://github.com/kbastani/event-stream-processing-microservices/blob/master/account/account-worker/src/main/java/demo/config/StateMachineConfig.java.
I'm working on samples that map SSM state transitions to SCFn consumers.
Feel free to e-mail me at kbastani at pivotal.io

Closing it as it seem to go stale. Feel free to reopen it if there are any updates


checkout account visibility

change account visibility to public if it is a public account

Codecov Report

Merging #21 into master will decrease coverage by 1.28%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
- Coverage   87.02%   85.73%   -1.29%
==========================================
  Files          10       10
  Lines         601      610       +9
  Branches      113      115       +2
==========================================
  Hits          523      523
- Misses         78       87       +9

Impacted Files
Coverage Δ

lib/executor.js
66.95% <0%> (-5.69%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ba45909...2d11838. Read the comment docs.


How to generate Railroad diagrams/EBNF/ANTLR grammar

The README mentions that

A more readily consumable form of the grammar is generated as output from the build

How can I generate these outputs? I tried various Maven commands (e.g. mvn compile test), but none produced the ebnf/g4/html files. I also tried searching the code, but did not find the related code.

Hello @szarnyasg and thanks for your question. I'll answer you briefly here and write a more comprehensive guide in the readme in a bit.
mvn clean install to generate the required jars, then run these four commands (which can be found in the .travis.yml file) for the artifacts that currently may be generated:
./tools/grammar/src/main/shell/launch.sh RailRoadDiagramPages -outputDir=grammar/generated/railroad cypher.xml
./tools/grammar/src/main/shell/launch.sh RailRoadDiagrams -DRailRoadDiagrams.inlineNone=true -outputDir=grammar/generated/railroad/raw cypher.xml
./tools/grammar/src/main/shell/launch.sh ISO14977 cypher.xml > grammar/generated/cypher.ebnf
./tools/grammar/src/main/shell/launch.sh Antlr4 cypher.xml > grammar/generated/Cypher.g4

These commands are mostly self-explanatory, and will put all artifacts in grammar/generated, unless modified.

Closing this as answered.


Heating technologies should not have a storage volume

I don't know if these numbers are actually used but I'm worried as they are non-zero:

Volume is always inherited from the buffer to which the heating technology belongs, so that number is not used. Nonetheless, I agree that no value should be set.

I agree that no value should be set.

It would be also good to remove it from the above interface as it would be always be zero.


Set up GA4 for website

Summary:
This was never set up. It's easy enough and we should have some analytics.
Test Plan:
npm run build & diff before & after output. The only change was adding the gtag code.