Nested lists in local files not displaying correctly

Newsboat version (copy the output of newsboat -v or the first line of git show):
newsboat 2.10.2 - https://newsboat.org/
Config file (copy from ~/.newsboat/config or ~/.config/newsboat/config):
#show-read-feeds no
auto-reload yes
goto-next-feed no

external-url-viewer "urlscan -dc -r 'linkhandler {}'"

bind-key j down
bind-key k up
bind-key j next articlelist
bind-key k prev articlelist
bind-key J next-feed articlelist
bind-key K prev-feed articlelist
bind-key G end
bind-key g home
bind-key d pagedown
bind-key u pageup
bind-key l open
bind-key h quit
bind-key a toggle-article-read
bind-key n next-unread
bind-key N prev-unread
bind-key D pb-download
bind-key U show-urls
bind-key x pb-delete

color listnormal cyan default
color listfocus black yellow standout bold
color listnormal_unread blue default
color listfocus_unread yellow default bold
color info red black bold
color article white default bold

browser linkhandler
macro , open-in-browser
macro t set browser "qndl"; open-in-browser ; set browser linkhandler
macro a set browser "tsp youtube-dl" ; open-in-browser ; set browser linkhandler
macro v set browser "setsid nohup mpv"; open-in-browser ; set browser linkhandler
macro w set browser "lynx"; open-in-browser ; set browser linkhandler
macro p set browser "dmenuhandler"; open-in-browser ; set browser linkhandler
macro c set browser "xsel -b <<<" ; open-in-browser ; set browser linkhandler

highlight all "---.*---" yellow
highlight feedlist ".*(0/0))" black
highlight article "(^Feed:.*|^Title:.*|^Author:.*)" cyan default bold
highlight article "(^Link:.*|^Date:.*)" default default
highlight article "https?://[^ ]+" green default
highlight article "^(Title):.*$" blue default
highlight article "\\[[0-9][0-9]*\\]" magenta default bold
highlight article "\\[image\\ [0-9]+\\]" green default bold
highlight article "\\[embedded flash: [0-9][0-9]*\\]" green default bold
highlight article ":.*\\(link\\)$" cyan default
highlight article ":.*\\(image\\)$" blue default
highlight article ":.*\\(embedded flash\\)$" magenta default

Steps to reproduce the issue:

Obtain feed file with nested list. Here's an example from this page -- note that it contains an ordered list whose items all contain unordered lists:

<?xml version="1.0" encoding="utf-8"?>

<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Unqualified Reservations</title>
	<description>Works by Mencius Moldbug.</description>
	<language>en-us</language>
	<item>
		<title>The Case Against Democracy: Ten Red Pills</title>
		<guid>https://www.unqualified-reservations.org/2007/04/case-against-democracy-ten-red-pills/</guid>
		<pubDate>Tue, 24 Apr 2007 00:00:00 </pubDate>
		<description><![CDATA[
Have you ever considered the possibility that democracy is bunk?

I grew up believing in democracy.  I'll bet you did too.  I spent 20 years
of my life in democratic schools.  I'll bet you did too.

Suppose you were a Catholic in 16th-century Spain.  Imagine how hard it
would be for you to stop believing in Catholicism.

You are a Catholic.  Your parents were Catholics.  You were educated by
Catholics.  You are governed by Catholics.  All your friends are
Catholics.  All the books you've ever read were written by Catholics.

Sure, you're aware that not everyone in the world is a Catholic.  You're
also aware that this is the cause of all the violence, death and
destruction in the world.

Look at what
Protestants do when they get into power.  They nail genitals to the city
gates.  They behead their own wives.  Crazy stuff!  And let's not even
start on the Turks…

Now suppose you're you.  But you have a time machine that lets you talk
to this 16th-century Spanish Catholic version of you.

How do you convince this guy or gal that the answer to all the world's
problems is not “more Catholicism”?  How do you say, um, dude, this
Trinity thing—the virgin birth—transsubstantiation… ya
know…

So you see how hard it is to explain that democracy is bunk.

Of course, I could be wrong.  Who the heck am I?  No one.    I'm just suggesting you
might want to consider the possibility.

Or even just consider considering the possibility.  The way you consider,
like, UFOs, or something.  Put it down in the “extremely improbable, but
not inherently impossible” category.

One way to consider this question is to look at an alternative.    If you didn't believe in democracy,
what would you believe in?  Here's
my
answer.  (Warning: it's long.)

Another classic approach, though, is just to write up a list of
heretical theses.  Red
pills, you might say.  It worked for Luther—why shouldn't it work for
me?

I won't (in this post) attempt to explain or justify these theses.  They
are for you, the reader, to analyze, to justify or refute.

For convenience, I've matched each red pill with a blue pill.  The blue
pill represents the orthodox democratic perspective.  If I'm wrong and
democracy is not bunk, the blue pills are reality and the red pills are
poisonous lies.  Swallow at your own risk.

Ten pills:

Peace, prosperity, and freedom

blue pill:
Democracy is responsible for the present state of peace, prosperity,
and freedom in the US, Europe and Japan.

red pill:
The rule of law is responsible for the present state of peace,
prosperity and freedom in the US, Europe and Japan.

Democracy, freedom, and law

blue pill:
Democracy is inseparable from freedom and law.

red pill:
At best, democracy is sand in the gears of freedom and law.  At worst
it excludes them entirely, as in Iraq.

Fascism and communism

blue pill:
The disasters of fascism and communism demonstrate the importance of
representative democracy.

red pill:
Fascism and communism are best understood as forms of democracy.  The
difference between single-party and multiparty democracy is like the
difference between a malignant tumor and a benign one.

The nature of the state

blue pill:
The state is established by citizens to serve their needs.  Its
actions are generally righteous.

red pill:
The state is just another giant corporation.  Its actions generally
advance its own interests.  Sometimes these interests coincide with
ours, sometimes they don't.

The power structure of the West

blue pill:
Power in the West is held by the people, who have to guard it
closely against corrupt politicians and corporations.

red pill:
Power in the West is held by the civil service, that is, the
permanent employees of the state.  In any struggle between the civil
service and politicians or corporations, the civil service wins.

The extent of the state

blue pill:
The state consists of elected officials and their appointees.

red pill:
The state consists of all those whose interests are aligned with the
state.      Domestically, they have little power and are mostly harmless.  Their
international adventures are destructive, but they are inescapable
consequences of democracy itself.

Democracy and nonpartisan government

blue pill:
True democracy is not merely the rule of politicians.  For a
democracy to succeed, a nonpartisan decisionmaking process is
essential.  Civil servants, especially judges, must be isolated from
politics, or they will become corrupt.

red pill:
Democracy is politics.  Any other definition is Orwellian.  The
absence of politics is the absence of democracy, and apolitical
civil-service government is indeed better than democracy.  But this
is a low standard to surpass.

The history of Western government

blue pill:
The present system of Western government is the result of adapting
19th-century classical liberalism to the complex modern world.

red pill:
Western governments today are clones of the quasi-democratic FDR
regime, whose best modern comparisons are leaders like Mubarak,
Putin or Suharto.  Its origin was the Progressive movement, which
broke classical liberalism, then complained that it didn't work.

The future of Western government

blue pill:
The Western world is moving toward a globalized, transnational free
market in which politics is increasingly irrelevant, and
technocratic experts and NGOs play larger roles in fighting
corruption, protecting the environment, and delivering essential
public services.

red pill:
Civil-service government works well at first, but it degrades.  Its
limit as time approaches infinity is sclerotic Brezhnevism.  Its
justification for ruling is inseparable from democracy, which is
mystical nonsense and is rapidly disappearing.  It cannot survive
without a captive media and educational system, which the Internet
will route around.  Also, its financial system is a mess and could
collapse at any minute.  The whole thing will be lucky if it lasts
another ten years.

]]></description>
	</item>
</channel>
</rss>

Add the file to urls. For instance, file:///path/to/file/feed.xml.

Observe that only the first ordered list item is actually labelled with '1'. All other ordered list items are treated as unordered.

Other info you think is relevant:
Unsure if this is the case for feeds specified by URL.

Thank you for the report! I wrote a test that demonstrates this bug (see bugfix/1158-nested-lists branch in this repo), which also confirms that the bug affects all HTML regardless of where it comes from, be it file://, http:// or https://. I won't have time to work on this any time soon, but maybe the test will help someone else tackle this.

Thanks for fixing this, @dennisschagt!


Upgrade JMH gradle plugin to 0.5.0-rc-1

Fixes https://github.com/gradle/gradle/issues/9618

@melix says that he'll attempt to address the JMH relocatability problem I found yesterday. Let's wait to see if he can do another release so we can upgrade directly to that.

Merged, thanks.


pull_request_target: clarify avoid

Why:
The phasing here is ambiguous. The underlying "code" can be modified (ex. actions/checkout@v3 checking out the PR's head ref). However any workflow changes will not execute from a PR until they land on the target branch.
Closes: #26535

What's being changed (if available, include any code snippets, screenshots, or gifs):
Documentation on pull_request_target event.

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@kevingentile Thanks for submitting a PR with your issue! I've edited your post slightly to link your PR to your issue. 👍
I'll get this triaged for review! :zap:

Ju

Hey @kevingentile, thank you so much for opening this PR to update the docs! ⚡
I was hoping you could provide some further clarification on the changes you are making? As far as I understand, the line you are updating advises people not to use pull-request-target as a trigger with an explicit PR checkout because it could be a security risk, as this Security Lab article explains much better than I can. The warning in the red box a little further down on the page you updated also describes this further. Please let me know if I'm misunderstanding your update, and we can work together to make this section more clear.
Thanks again for contributing to the docs! ✨

Hi @SiaraMist, thank you for reaching out for clarification.
There has been much confusion on my end over the years regarding secure usage of pull_request_target vs pull_request events. After re-reading the security document you linked I'm motivated to close this issue with no action.
My suggestions were motivated by a need to access secrets during the build phase which would not be widely applicable for users interacting with public repos or forks as the secret(s) would be necessary for local builds and thus no longer secret.
As an aside, a consequence of the recommended approach is any auto-generated dependabot PRs will always fail to execute a build workflow if a secret is required as part of a build (ex. GITHUB_TOKEN for registry access to dependencies). This is likely the intended behavior but a minor annoyance as my current workaround is to push an empty commit to each dependabot PR to trigger a privileged workflow.

Hey @kevingentile, thank you for explaining your thought process! 💛 Based on what you said and how I read this, I'm going to just close out this PR. For the odd Dependabot behavior you are seeing, you may want to leave feedback in the GitHub Community. Thanks again for contributing to the docs!


Handling QGIS-project so that users can add new layers but can not delete default layers

Users have a ready made QGIS-project with layers and codelists and custom attribute forms. Users can add and edit data, but can not change these items.
Users on the other hand need to be able to add own data/own layers to the QGIS-project and save the project into the database.
Todo:

[x] Find out if it is possible to set parts of the QGIS-project so that the layers can not be removed from the project

Yes it is possible... lock layers form QGIS project database-connection:


url router improperly configured?

Hi
I'm getting such an error:
urlresolvers.py", line 203, in regex
    (regex, six.text_type(e)))
ImproperlyConfigured: "^algebra/(?P<z>[0-9]+)/(?P<x>[0-9]+)/(?P<y>[0-9]+)(?P<format>\.jpg|\.png)\.(?P<format>[a-z0-9]+)/?$" is not a valid regular expression: redefinition of group name u'format' as group 5; was group 4

It also show this on Pythex

Please disregard, seems to stem from conflicts in pip installs


Autoprefixer Error: (node:9236) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module

hi, i get this error when try to use this sublime extension. I'm on bigsure with node last version 16.
Anyone with same error?

Hi, just had this error too.
For a quick fix I just did a npm update into the package folder:
(The path on a MacOS it's someting like /Users/{username}/Library/Application\ Support/Sublime\ Text/Packages/Autoprefixer)
$ cd {path_to_package}/Autoprefixer
$ npm update
Not sure if it will works over time but it does now

Yup, it does for me as well. Thanks for the tip!

Cannot reproduce with latest version. Make sure you are on Node.js 20.


internal error: entered unreachable code when using tokio integration

I'm using an AsyncSession<tokio::net::TcpStream> concurrently across multiple tokio tasks to open channels and execute commands over them.
However, I noticed some of those tasks crashing due to this error:
thread 'tokio-runtime-worker' panicked at 'internal error: entered unreachable code: ', /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/async-ssh2-lite-0.4.1/src/session_stream/impl_tokio.rs:39:21

or this one
thread 'tokio-runtime-worker' panicked at 'internal error: entered unreachable code: ', /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/async-ssh2-lite-0.4.1/src/session_stream/impl_tokio.rs:81:17

What is going on here?

Here's the error backtrace:
stack backtrace:
   0: rust_begin_unwind
             at /rustc/659e169d37990b9c730a59a96081f2ef7afbe8f1/library/std/src/panicking.rs:575:5
   1: core::panicking::panic_fmt
             at /rustc/659e169d37990b9c730a59a96081f2ef7afbe8f1/library/core/src/panicking.rs:64:14
   2: async_ssh2_lite::session_stream::impl_tokio::<impl async_ssh2_lite::session_stream::AsyncSessionStream for tokio::net::tcp::stream::TcpStream>::poll_x_with
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/async-ssh2-lite-0.4.1/src/session_stream/impl_tokio.rs:81:17
   3: async_ssh2_lite::session_stream::AsyncSessionStream::poll_read_with
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/async-ssh2-lite-0.4.1/src/session_stream/mod.rs:102:9
   4: async_ssh2_lite::channel::impl_tokio::<impl tokio::io::async_read::AsyncRead for async_ssh2_lite::channel::AsyncStream<S>>::poll_read
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/async-ssh2-lite-0.4.1/src/channel.rs:341:13
   5: async_ssh2_lite::channel::impl_tokio::<impl tokio::io::async_read::AsyncRead for async_ssh2_lite::channel::AsyncChannel<S>>::poll_read
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/async-ssh2-lite-0.4.1/src/channel.rs:302:13
   6: tokio::io::util::read_to_end::poll_read_to_end
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/io/util/read_to_end.rs:77:23
   7: tokio::io::util::read_to_end::read_to_end_internal
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/io/util/read_to_end.rs:46:26
   8: <tokio::io::util::read_to_end::ReadToEnd<A> as core::future::future::Future>::poll
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/io/util/read_to_end.rs:110:9
   9: ssh_worker::ssh::Client::call::{{closure}}
             at /home/nett/Stuff/sisyphos/ssh-worker/src/ssh.rs:53:41
  10: ssh_worker::job::spawn_job::{{closure}}
             at /home/nett/Stuff/sisyphos/ssh-worker/src/job.rs:34:54
  11: <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tracing-0.1.37/src/instrument.rs:272:9
  12: tokio::runtime::task::core::Core<T,S>::poll::{{closure}}
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/core.rs:223:17
  13: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/loom/std/unsafe_cell.rs:14:9
  14: tokio::runtime::task::core::Core<T,S>::poll
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/core.rs:212:13
  15: tokio::runtime::task::harness::poll_future::{{closure}}
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/harness.rs:481:19
  16: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at /rustc/659e169d37990b9c730a59a96081f2ef7afbe8f1/library/core/src/panic/unwind_safe.rs:271:9
  17: std::panicking::try::do_call
             at /rustc/659e169d37990b9c730a59a96081f2ef7afbe8f1/library/std/src/panicking.rs:483:40
  18: __rust_try
  19: std::panicking::try
             at /rustc/659e169d37990b9c730a59a96081f2ef7afbe8f1/library/std/src/panicking.rs:447:19
  20: std::panic::catch_unwind
             at /rustc/659e169d37990b9c730a59a96081f2ef7afbe8f1/library/std/src/panic.rs:140:14
  21: tokio::runtime::task::harness::poll_future
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/harness.rs:469:18
  22: tokio::runtime::task::harness::Harness<T,S>::poll_inner
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/harness.rs:198:27
  23: tokio::runtime::task::harness::Harness<T,S>::poll
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/harness.rs:152:15
  24: tokio::runtime::task::raw::poll
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/raw.rs:255:5
  25: tokio::runtime::task::raw::RawTask::poll
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/raw.rs:200:18
  26: tokio::runtime::task::LocalNotified<S>::run
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/mod.rs:459:9
  27: tokio::runtime::scheduler::multi_thread::worker::Context::run_task::{{closure}}
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/scheduler/multi_thread/worker.rs:487:21
  28: tokio::runtime::coop::with_budget
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/coop.rs:102:5
  29: tokio::runtime::coop::budget
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/coop.rs:68:5
  30: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/scheduler/multi_thread/worker.rs:463:9
  31: tokio::runtime::scheduler::multi_thread::worker::Context::run
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/scheduler/multi_thread/worker.rs:433:24
  32: tokio::runtime::scheduler::multi_thread::worker::run::{{closure}}
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/scheduler/multi_thread/worker.rs:406:17
  33: tokio::macros::scoped_tls::ScopedKey<T>::set
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/macros/scoped_tls.rs:61:9
  34: tokio::runtime::scheduler::multi_thread::worker::run
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/scheduler/multi_thread/worker.rs:403:5
  35: tokio::runtime::scheduler::multi_thread::worker::Launch::launch::{{closure}}
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/scheduler/multi_thread/worker.rs:365:45
  36: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/blocking/task.rs:42:21
  37: tokio::runtime::task::core::Core<T,S>::poll::{{closure}}
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/core.rs:223:17
  38: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/loom/std/unsafe_cell.rs:14:9
  39: tokio::runtime::task::core::Core<T,S>::poll
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/core.rs:212:13
  40: tokio::runtime::task::harness::poll_future::{{closure}}
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/harness.rs:481:19
  41: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at /rustc/659e169d37990b9c730a59a96081f2ef7afbe8f1/library/core/src/panic/unwind_safe.rs:271:9
  42: std::panicking::try::do_call
             at /rustc/659e169d37990b9c730a59a96081f2ef7afbe8f1/library/std/src/panicking.rs:483:40
  43: __rust_try
  44: std::panicking::try
             at /rustc/659e169d37990b9c730a59a96081f2ef7afbe8f1/library/std/src/panicking.rs:447:19
  45: std::panic::catch_unwind
             at /rustc/659e169d37990b9c730a59a96081f2ef7afbe8f1/library/std/src/panic.rs:140:14
  46: tokio::runtime::task::harness::poll_future
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/harness.rs:469:18
  47: tokio::runtime::task::harness::Harness<T,S>::poll_inner
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/harness.rs:198:27
  48: tokio::runtime::task::harness::Harness<T,S>::poll
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/harness.rs:152:15
  49: tokio::runtime::task::raw::poll
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/raw.rs:255:5
  50: tokio::runtime::task::raw::RawTask::poll
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/raw.rs:200:18
  51: tokio::runtime::task::UnownedTask<S>::run
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/task/mod.rs:496:9
  52: tokio::runtime::blocking::pool::Task::run
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/blocking/pool.rs:159:9
  53: tokio::runtime::blocking::pool::Inner::run
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/blocking/pool.rs:510:17
  54: tokio::runtime::blocking::pool::Spawner::spawn_thread::{{closure}}
             at /home/nett/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-1.23.0/src/runtime/blocking/pool.rs:468:13
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

ssh_worker::ssh::Client::call looks like this:
    pub async fn call(&self, command: &str) -> eyre::Result<CommandResult> {
        debug!("Executing command: {command}");
        let mut channel = self.new_channel().await?;
        channel.exec(command).await?;
        let mut stdout = Vec::new();
        let mut stderr = Vec::new();
        channel.read_to_end(&mut stdout).await?;
        channel.stderr().read_to_end(&mut stderr).await?;
        channel.close().await?;
        let code = channel.exit_status().ok();
        Ok(CommandResult {
            stdout,
            stderr,
            code,
        })
    }

Line 53 is the one with read_to_end.

Hi, @netthier
Please provide an example. Thank you.

Hi, I add tests and run SSH_SERVER_HOST=<IP_ADDRESS> SSH_SERVER_PORT=22 SSH_USERNAME=root SSH_PRIVATEKEY_PATH=~/.ssh/id_rsa cargo test -p async-ssh2-lite --features _integration_tests,_integration_tests_tokio_ext,async-io,tokio -- integration_tests::tokio_spawn_session --nocapture , not crash happened.

But I tend to use bb8-async-ssh2-lite in concurrent case.

Thanks for the response, this bug does seem to be difficult to trigger.
Using bb8 fixed the bug in my main project, but I was still able to trigger it exactly once in a test project (but not anymore after that).
Seems like its related to lots of channels being opened at the same time in the same session?

Yes, theoretically,  should exist one channel in one session simultaneously.

Yes, theoretically, should exist one channel in one session simultaneously.

@vkill Is this documented somewhere? Both this and the fact that you can't call exec on a channel twice are pitfalls I apparently fell into :thinking:
If not, it should be

I'm still getting the panic with your bb8 crate under very high load. I'll try to write a better reproducer over the course of the week, as my program does a ton of stuff over SSH.

Please try change here to BlockDirections::None => continue, , because I found this commit

Thank you for finding this, seems like it has fixed the issue. I have not been able to trigger this bug in my project anymore.
I created a PR containing the patch here: https://github.com/bk-rs/ssh-rs/pull/31

Seems like it's not that easy after all. Instead of panicking, acquiring a session now errors out sometimes:
Err(
        Ssh2(
            Error {
                code: Session(
                    -21,
                ),
                msg: "Unable to startup channel",
            },
        ),
    )

However, handling this kind of error is still way easier than catching a panic.

Do Channels automatically close themselves on Drop? I wasn't able to find any custom Drop impls for it.
Is it possible that a Channel stays open for a short while after being dropped, with bb8 thinking the session can be reused for new channels?

Increasing MaxStartups in my sshd_config fully fixed this issue, meaning a connection limit support is the way forward here.
I'll open a new issue regarding that, and this issue can be closed once the PR is merged.

Do Channels automatically close themselves on Drop?
Yes, https://docs.rs/ssh2/0.9.3/src/ssh2/channel.rs.html#488 and https://www.libssh2.org/libssh2_channel_free.html
But I suggest channel.close().await

In short, I like one channel in one session simultaneously, close the channel actively, and then use bb8 to limit the number of sessions.

Do Channels automatically close themselves on Drop?
Yes, https://docs.rs/ssh2/0.9.3/src/ssh2/channel.rs.html#488 and https://www.libssh2.org/libssh2_channel_free.html
But I suggest channel.close().await

Ah, I overlooked that. I'll need to check closer if it's possible that multiple channels exist concurrently per session.

v0.4.2

https://github.com/bk-rs/ssh-rs/blob/b79d97f5653695dc4b9242635476d400023f4d3d/async-ssh2-lite/tests/integration_tests/tokio_spawn_session.rs#L57-L61
Maybe Ssh2(Error { code: Session(-4), msg: "Unexpected error" })  when open many channels in one session simultaneously.


Add source locations to parsed AST

Currently, only the text is taken into account and parsed into AST.
For more descriptive error messages it would help if source locations are added to the AST as well.
This should be done in such a way that each node in the AST can later contain more info in the future as well.
Look into cofree / annotations package?

Came across "trees that grow" (https://www.microsoft.com/en-us/research/uploads/prod/2016/11/trees-that-grow.pdf), looks like it is a good fit for adding various types of annotation data during each of the compiler phases.

Implemented by #20


New CBC version 2.10.3 released

There is a new version of the CBC solver (2.10.3), with performance improvements.
Can you guys add it to 7.2?

Already integrated on master

Already integrated.


Revert "fix(ui): always pass credentials with fetch()"

This reverts commit c2a1468c5184798efb82ac1a1898a594ad686d09.
Using 'include' requires passing non-wildcard value in Access-Control-Allow-Origin, revert do default for now.
Related to #24

Issue with non-wildcards only applies when UI and backend are under 2 different origins, which happens mostly in dev environment

Based on feedback #24 looks like include is needed for some setups, that means:

Access-Control-Allow-Origin should be configurable, since there's no one-size-fits-all default value
maybe disable include for local dev environment?

Fixed via #90


KOGITO-4451 - Skip metrics generation for requests coming from explainability addon

Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Your code is properly formatted according to this configuration
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

The Linux check has failed. Please check the logs.

The Linux check is successful.

The Linux check is successful.

The Linux check is successful.


Censor Answers from Chat

I've noticed that certain players have a tendency to start guessing in the wrong box, or even give away the answer. I think it would be a helpful improvement to censor out the answers to the currently playing song from chat.

I think that this is a minor problem.
Could be annoying only if a player will constantly give away the answer. In that case would be better to kick the player.
I have also noticed that some player write in the chat the wrong answer to confuse other players and i approve this strategy.

I could try adding this for you :)


access and network policy resources are not added to cloudformation resources tab

Resources created by these methods:
createAccessPolicy, createNetworkSecurityPolicy, createEncryptionSecurityPolicy
need to be returned by custom resource here:
  response.Data = {
    collectionArn: collection.arn!,
    collectionId: collection.id!,
    collectionName: collection.name!,
    collectionEndpoint: collection.collectionEndpoint,
    dataSourceId: dataSource?.dataSource?.dataSourceId,
    knowledgeBaseId: knowledgeBase.knowledgeBase?.knowledgeBaseId,
  };

https://github.com/schuettc/cdk-bedrock-knowledge-base/pull/2
Great!  Thanks!


Analyzer: Hovering over a constructor parameter doesn't show param docs

I am working on a toy app and re-learning how Flutter's layout works :)
Here I am investigating how to properly use Row.mainAxisSize:

When I highlight over this field, I get a preview of the type (somewhat useful), but the rest of the documentation is for Row, not Row.mainAxisSize:

That's unfortunate, because it has really useful information that requires multiple clicks:

Maybe this is WAI (if it is, can we change it?), and if it's not, here is a bug :)

I always thought that the requested behavior would be really helpful and is what I would like to have, too.
For parameters like this.foo or super.foo it's clear from which property the documentation should be taken. But I also think this should be made to work for parameters which, for example, initialize a private field that is exposed through a getter. In this case, the relationship between the parameter and the property that has the corresponding documentation is not as straightforward. It could work by matching parameters and properties with the same name, or through annotations for more flexibility.


Added TeamHighlight step

Created TeamHighlights step for the new Progress report feature.
API PR: https://github.com/SeedCompany/cord-api-v3/pull/2554

As discussed, we will be making the fragment, context and moving changes in the Progress step PR to avoid conflicts in the PRs based on this branch


PostMessage: Data cannot be cloned, out of memory

I'm trying to load Mistral 7B 32K. I've chunked the 4.3GB model and uploaded it to huggingface.
When the download is seemingly complete, there is a warning about being out of memory:

It's a little odd, as I normally load bigger chunked models (Llama 8B) with WebLLM. The task manager also indicates that memory pressure is medium.

Yes seems like the issue is due to the way multiple files are being copied onto web worker: we're currently copying all shards at once, which may cause it to run out of memory. The fix would be:

Copy one file at once
Even better, we can move download function to webworker, so no copy is needed (but with the cost of making harder to control)
Maybe use SharedArrayBuffer when possible to avoid copy

This is becoming a bit of a show stopper unfortunately. It seems to even affect models that would load under llama_cpp_wasm :-(
If you could help fix this issue, or give some pointers on how I could attempt to do so myself, that would be greatly appreciated. At this point I don't mind if a fix is slow or sub-optimal. I just want wllama to be reliable.

I'm planning to work on this issue in next days. It maybe more complicated than it looks, so I'll need time to figure that out. Please be patient.

That's great news! Thank you so much!

FYI, v1.7.0 has been released. It also come with support for progressCallback, please see "advanced" example:
https://github.com/ngxson/wllama/blob/d1ceeb6d38a076045262aeb18a36f7572aaa90d6/examples/advanced/index.html#L53-L57
This issue (out-of-memory) is hopefully fixed by #14 , but I'm not 100% sure. Please try again.
Also, it's now recommended to split the model into chunks of 256MB or 512MB. Again, see "advanced" example:
https://github.com/ngxson/wllama/blob/d1ceeb6d38a076045262aeb18a36f7572aaa90d6/examples/advanced/index.html#L38-L45
Also have a look at updated README: https://github.com/ngxson/wllama/tree/master?tab=readme-ov-file#prepare-your-model
Thank you!

The readme mentions the progress feature (very nice bonus, thank you!), but just to be sure: does this also address the memory issue? Or is the intended fix for that to make the chunks smaller?

I'm seeing this error after creating a chunked model of Open Buddy Mistral 7B 32k Q4_K_M with 50 x 100Mb chunks:

		"download_url":[
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00001-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00002-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00003-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00004-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00005-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00006-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00007-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00008-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00009-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00010-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00011-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00012-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00013-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00014-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00015-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00016-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00017-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00018-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00019-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00020-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00021-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00022-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00023-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00024-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00025-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00026-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00027-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00028-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00029-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00030-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00031-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00032-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00033-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00034-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00035-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00036-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00037-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00038-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00039-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00040-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00041-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00042-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00043-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00044-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00045-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00046-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00047-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00048-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00049-of-00050.gguf",
			"https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked/resolve/main/open_buddy_mistral-00050-of-00050.gguf",
		],

I'm seeing this error after creating a chunked model of Open Buddy Mistral 7B 32k Q4_K_M with 50 x 100Mb chunks:

@flatsiedatsie FYI, I uploaded v1.8.0 which should display a better error message (I don't know if it fixes the mentioned issue or not). Could you try again and see what's the error? Thanks.

I will. I've been trying lots of things actually.  But unfortunately still having trouble loading models that WebLLM does load.
The following screenshots are not so much bugs, I've managed to solve some (basically by reducing context size).

I'm also still looking into your suggestion that it mau be that the model is trying to load twice.

You screenshot still shows "_wllama_decode_exception", which is already been removed in 1.8.0. Maybe your code is not using the latest version.

Correct, those are screenshots from yesterdy. I'm updating it now.

OK, I've done some more testing.  TL/DR: Thing are running a lot smoother now!
But before I get into that, let me give a little context about what I'm trying to achieve. I'm trying to create a 100% browser-based online tool where people can not only chat with AI, but use it to work on documents. For that I need two types of models:

A small model with a huge context for summarization tasks.

Small: Danube with 8K context is great for memory-poor mobile phones.
Medium: NeuralReyna, is a step up, as it has a 32K context.
Large: Phi 3 with 128K context.

Use a large model with a relatively small context for more demanding tasks, like rewriting part of a document in a different tone.

Small: I'm not sure yet.
Medium: Mistral 7B with 4K
Large: Llama 3 8B is the top of the line.

Mistral 7B with 32K context could be a good "middle of the road do-it-all" option, so I've been trying to run that with Wllama today.
I started with by using your example code to eliminate the possiblity of bugs in my project being the cause of issues. I also rebooted my laptop first (Macbook Pro with 16Gb of ram) to have as much available memory as possible. Once I found that I got the same results with the example as with my code, I mostly reverted back to my project.

NeuralReyna

In my main code I can now load NeuralReyna. Howver,  if I try to use the full 32K, there are once again memory issues. With 16K it doesn't crash, which is already reallty great!

Phi 3 - 4K

I chunked it in 250Mb parts, and it loads! Nice!

Phi 3 - 128K

Here I tried to directly load a 1.96Gb .gguf file (Q3_K) and even that worked! This is pretty great, as Llama.cpp support for this model is right around the corner.

Mistral 7B - 32K

This model has memory issues. To make sure it wasn't my code I tried loading the model in the advanced example too. Same result. Even setting the context to 1K doesn't help. The chunks I'm using are available here: https://huggingface.co/BoscoTheDog/open_buddy_mistral_7B_32k_chunked
With version 1.8 Wllama doesn't seem to raise an error though? It just just states the issue in the console. But my code thinks the model has loaded OK, even though it hasn't. Is there a way to get the failed state?

In summary, only the bigger models/contexts now seem to run into issues.

You could argue the model is just "too big". But from using WebLLM I know that it should be possible to run it in the browser, with memory to spare. Similarly, the even bigger Llama 3 8B 4K can run under WebLLM. And since the Mac's have unified memory, I can't blame it on WebLLM offloading it to graphics card memory, right?

You could argue "Well, run Mistral 7B through WebLLM then". But WebLLM only runs when a WebGPU is available. It would be awesome to seemlessly switch between Wllama and WebLLM in the background, depending on WebGPU support.

I stilll have to test what happens on devices with less memory (e.g. 8Gb Macbook Air).
Finally, I just want to say: thank you for all your work on this! It's such an exciting development. Everybody talks about bringing AI to the masses, but too few people realize the browser is the best platform to do that with. Wllama is awesome!

Just a quick check:

Is it reasonable to set the n_ctx and n_seq_max to the same value?
Is it reasonable to have n_batch hardcoded at 1024?

Thank you for the very detailed info!
It's true that we will definitely be struggle with the memory issue, because AFAIK browsers does have some limits on memory usage. Optimizing memory usage will surely be an area that I'll need to invest my time into.

Howver, if I try to use the full 32K, or even 16K, there are once again memory issues. With 8K it doesn't crash.

FYI, n_ctx doesn't have to be power of 2. It can be multiple of 1024, for example 10 * 1024 (= 10K)
Another trick to reduce memory usage is by using quantize q4_0 for cache_type_k, for example:
wllama.loadModelFromUrl(MODEL, {
  n_ctx: 10 * 1024,
  cache_type_k: 'q4_0',
});

WebLLM offloading it to graphics card memory, right?

Yes, WebLLM offload model weight and KV cache to GPU. I couldn't find on google what's the hard limit for WebGPU memory, so I suppose that it can use all available GPU VRAM.
It would be ideal to have support of WebGPU built directly into llama.cpp itself, but that far too complicated, so for now there's not much choice left for us.

Is it reasonable to set the n_ctx and n_seq_max to the same value? In the advanced example you only seem to set n_ctx. Do you recommend doing the same?

n_seq_max is always 1 and should not be modified (I should remove it in next release). The reason is because n_seq_max controls number of sequences can be processed in one batch. This is only useful when you have a big server that processes multiple requests at the same time (provided that the server have a beefy nvidia GPU). In our case, we only have single user at one time, so multi-sequence will decrease the performance.

Is it reasonable to have n_batch hardcoded at 1024?

If you're not using the model for embedding, 1024 is probably fine. However, embedding models like BERT are non-causal, meaning they need n_batch to be bigger than sequence length.

I've got a 7B Q2_K model working!
I wasn't able to run a larger quantization, and the maximum file size I could load was 2.72 GB.
This means that a 7B model will require LASER before being converted and quantized to GGUF Q2_K.
Without LASER, the Q2_K size is 3.01 GB and throws an out-of-memory error.
I was able to use a context up to n_ctx: 9 * 1024 using cache_type_k: "q4_0".
The inference speed was around 2 tokens per second when using 6 threads.

Screenshots from console (click to expand)

I've uploaded the split-gguf here. To try it, you can use this model URL array:
Array.from({ length: 45 }, (_, i) => `https://huggingface.co/Felladrin/gguf-sharded-smashed-WizardLM-2-7B/resolve/main/WizardLM-2-7B.Q2_K.shard-${(i + 1).toString().padStart(5, "0")}-of-00045.gguf`)

Hmm, now I got a 7B Q3_K_M working. I think the previous attempt didn't work because I was setting a too small split-size. I've increased to 96M per chunk and it's now working. Will do a few more experiments before going back here. Stay tuned!

*stops watching this space ;-)

I'm not as lucky it seems. The 7B Q3_K_M with 4K context:

@flatsiedatsie, please confirm if your have set cache_type_k: "q4_0" during Wllama initialization. It seems to be failing due to cache_type_k being f16, as per the screenshot.

@felladrin You're right! I accidentally had that commented out for some testing.
And.. it's working!!
Thank you both so much! Mistral! On CPU! In the browser! This is a game changer!

Does n_batch have an effect on memory consumption? Should I set it lower than 1024 for lower contexts? Or is 1024 generally safe?

I'm happy to see it too!
I usually leave the n_batch unset. By default it will fill it with the same value of n_ctx, and I haven't had problems with memory due to it.
But I use a low n_ctx for my case, 2048. I don't know how it affects the memory when the context is larger.


Updates for ckeditor5 and drupal v10.2

PR looks fine for me (just a compilation of d10.2 and ckeditor5 PRs as I can see)


Improve Plutus script handling and add WebSocket support in browser for Kupmios provider.

This PR includes two changes:

Fix handling Plutus scripts: This commit updates the code to handle Plutus scripts properly, by using the appropriate language version and CBOR encoding.
Add WebSocket support in browser and simplify code: This commit adds support for WebSocket connections in the browser. The commit also includes a few code simplifications.

The PR includes the following changes:

Fix handling of Plutus scripts
Fix Add WebSocket support in browser

Apologies on CI being temporarily broken. Can you rebase on main and commit your pnpm lock with corepack (i.e. corepack pnpm i)?

Hey @EzePze,
It seems that the @blaze-cardano/ogmios package was not bumped nor published. Also, the @blaze-cardano/kupmios should be bumped and published to reflect that ogmios package change.


Occupancy, yield and hist error

I get this bizarre error when trying to run these Poretools commands. I have a brand new macbook and have installed poretools via homebrew and via "python setup.py install".
Could the issue be the fastq_paths variable implementation in  /Library/Python/2.7/site-packages/poretools-0.5.1-py2.7.egg/poretools/Fast5File.py  ??
fastq_paths = {'template' : '/Analyses/Basecall_2D_%03d/BaseCalled_template',
'complement' : '/Analyses/Basecall_2D_%03d/BaseCalled_complement',
'twodirections' : '/Analyses/Basecall_2D_%03d/BaseCalled_2D',
'pre_basecalled' : '/Analyses/EventDetection_000/Reads/'}
Command and sdterr:
$ poretools hist ./
Traceback (most recent call last):
File "/usr/local/bin/poretools", line 9, in
load_entry_point('poretools==0.5.1', 'console_scripts', 'poretools')()
File "/Library/Python/2.7/site-packages/poretools-0.5.1-py2.7.egg/poretools/poretools_main.py", line 430, in main
args.func(parser, args)
File "/Library/Python/2.7/site-packages/poretools-0.5.1-py2.7.egg/poretools/poretools_main.py", line 49, in run_subtool
submodule.run(parser, args)
File "/Library/Python/2.7/site-packages/poretools-0.5.1-py2.7.egg/poretools/hist.py", line 70, in run
fq = fast5.get_fastq()
File "/Library/Python/2.7/site-packages/poretools-0.5.1-py2.7.egg/poretools/Fast5File.py", line 296, in get_fastq
self._extract_fastqs_from_fast5(self.group)
TypeError: _extract_fastqs_from_fast5() takes exactly 1 argument (2 given)

Thanks, caused by a bug in my last commit, fixed now, please update your pore tools to the latest version!


Fortune with default NeDB adapter generates invalid IDs with slashes

If I post a user to my endpoint without specifying an ID:
{
  "@graph": [{
    "@type": "user",
    "firstName": "John",
    "lastName": "Doe"
  }]
}

The user will be assigned a random ID:
{
  "@graph": [{
      "@type": "user",
      "@id": "/users/fckuk1hEVbVYr%2FYs91Kb",
      "id": "fckuk1hEVbVYr/Ys91Kb",
      "firstName": "John",
      "lastName": "Doe"
    }]
}

But if I try to GET by that ID, the server will fail:
$ curl http://localhost:8001/api/users/fckuk1hEVbVYr%2FYs91Kb
{
  "@error": {
    "name": "NotFoundError",
    "message": "The field \"Ys91Kb\" is not a link on the type \"user\"."
  }
}

Looks like it's a bug regarding URI decoding, will investigate a fix.

Fixed in commit https://github.com/fortunejs/fortune/commit/b1a9fa158aa3fb1468affee6538c4d4d6f1f56e6, published as 1.0.0-rc.7.

Awesome. Thank you!


category choice widget

Notes

[ ] add sub category choice for pomodori
[ ] add default value for pause must be choosen with a random pick from the config random choice table

nest steps:

[ ] when add new category it must be added also to the global list ( CATEGORIES = ["pippo", "ciccio", 'piada', NEW_CATEGORY] )

[ ] in the future this must be somewhere in the db (find all unique categories from previous pomodoros and merge them to the global list)

[ ] add a global variable for the chosen category that must be used by the following pomodoro
[ ] disable the category choice while the pomodoro il ticking


'too many placeholders at ' while saving Page.

Describe the Bug
[previous exception] [object] (PDOException(code: HY000): SQLSTATE[HY000]: General error: 1390 Prepared statement contains too many placeholders at /var/www/bookstack/vendor/laravel/framew ork/src/Illuminate/Database/MySqlConnection.php:39) [stacktrace] #0 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/MySqlConnection.php(39): PDO->prepare() #1 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Connection.php(816): Illuminate\\Database\\MySqlConnection->Illuminate\\Database\\{closure}() #2 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Connection.php(783): Illuminate\\Database\\Connection->runQueryCallback() #3 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/MySqlConnection.php(34): Illuminate\\Database\\Connection->run() #4 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(3498): Illuminate\\Database\\MySqlConnection->insert() #5 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php(1982): Illuminate\\Database\\Query\\Builder->insert() #6 /var/www/bookstack/app/Search/SearchIndex.php(33): Illuminate\\Database\\Eloquent\\Builder->__call() #7 /var/www/bookstack/app/Entities/Models/Entity.php(308): BookStack\\Search\\SearchIndex->indexEntity() #8 /var/www/bookstack/app/Entities/Repos/BaseRepo.php(78): BookStack\\Entities\\Models\\Entity->indexForSearch() #9 /var/www/bookstack/app/Entities/Repos/PageRepo.php(101): BookStack\\Entities\\Repos\\BaseRepo->update() #10 /var/www/bookstack/app/Entities/Controllers/PageController.php(225): BookStack\\Entities\\Repos\\PageRepo->update() #11 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(54): BookStack\\Entities\\Controllers\\PageController->update() #12 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(43): Illuminate\\Routing\\Controller->callAction() #13 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/Route.php(259): Illuminate\\Routing\\ControllerDispatcher->dispatch() #14 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/Route.php(205): Illuminate\\Routing\\Route->runController() #15 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Routing/Router.php(806): Illuminate\\Routing\\Route->run()
Steps to Reproduce
Saving big c-header size (3.2Mb) inside pre-tags
Expected Behaviour
code 200
Screenshots or Additional Context
No response
Browser Details
No response
Exact BookStack Version
git head

Looks like we need to add some extra chunking/handling for search term index insertion.
I've assigned this to the next release to be confirmed/addresses.
That said, >3MB of content is pretty massive and BookStack pages are not really intended for that kind of scale, so you may face other issues or side-affects with so much content for a single page.

The handling of this particular error when indexing a page with many terms, has now been addressed as part of 509af2463d94210fd500c10c651fa8f883e87fd8 and will be part of the next feature release.
But as mentioned above, you may run into other issues or limitations with massive pages so they are not advised.
Thanks for originally reporting this issue @OnlySlon!


Cannot connect Fastmail calendar with CalDAV

Whenever I try to link an icloud or caldav calendar, I get the following in the console:
TypeError: Cannot read property 'childNodes' of undefined
at childNodes (eval at  (app.js:1), :34348:29)
at complex (eval at  (app.js:1), :34306:11)
at Object.multistatus2 [as multistatus] (eval at  (app.js:1), :34254:20)
at multistatus (eval at  (app.js:1), :34248:33)
at transformResponse (eval at  (app.js:1), :34443:53)
at Basic.eval (eval at  (app.js:1), :53054:38)
at Generator.next ()
at onFulfilled (eval at  (app.js:1), :38042:23)
I am confident that I'm using correct account details.
I can get an ics (webcal://...) calendar to work. But, I'd really like the ability to have syncing via caldav.
I'm using version 0.6.1 of Full Calendar and 0.14.5 of Obsidian

That likely means you input invalid account details. The package we use doesn’t handle that case well. It assumes the response will be a valid CalDAV response, so it tries to parse it, but that fails. We can try to surface a better error when importing fails.
Did you make sure to create an app specific password as described in the docs?

Yes, I am using app-specific passwords. I  will try to generate new app-specific passwords and see if I get anywhere.

Were you able to get it working?

Hi, I was able to get it working for iCloud, but for another caldav (Fastmail.com) it still does not work.
On Mon, 18 Apr 2022, at 04:09, Nader Akoury wrote:

Were you able to get it working?
—
Reply to this email directly, view it on GitHub https://github.com/davish/obsidian-full-calendar/issues/87#issuecomment-1101048957, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGLBCPDN2Q4IQELA6OOZRYDVFTG67ANCNFSM5TGYZFTA.
You are receiving this because you authored the thread.Message ID: @.***>

--
Geoffrey Makstutis

Do you have a Basic plan? According to the Fastmail docs, in addition to using an app specific password, you also have to be on a Standard or Professional plan.

@gmakstutis Any updates? If not, then @davish I'd recommend closing this as I'm pretty sure this is just user error.

I have tried it with other accounts I have setup in Fastmail, with the same result. I don't think it is 'user error'. Rather, I think it more likely that there is something about the way Fastmail is serving caldav that doesn't work with the particular client that you've implemented.
I'm happy for you to close this, as I don't expect you to solve 'my' problem. Perhaps if you get other issues, along these lines, you can revisit.
Thanks
On Thu, 21 Apr 2022, at 16:37, Nader Akoury wrote:

@gmakstutis https://github.com/gmakstutis Any updates? If not, then @davish https://github.com/davish I'd recommend closing this as I'm pretty sure this is just user error.
—
Reply to this email directly, view it on GitHub https://github.com/davish/obsidian-full-calendar/issues/87#issuecomment-1105392105, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGLBCPF32OU3U3V3YMX45ATVGFY33ANCNFSM5TGYZFTA.
You are receiving this because you were mentioned.Message ID: @.***>

--
Geoffrey Makstutis

@gmakstutis I don't have a Fastmail account, so I cannot test your issue directly. I have tested both iCloud and NextCloud and the CalDAV syncing works correctly for those providers. Can you sync your Fastmail calendar with a different CalDAV client. There are plenty to choose from, see list1, list2. If you can get it to work in one of those, but it doesn't work in this plugin, then you'll need to provide more information that can help pinpoint the specific issue.

I do sync my Fastmail calendars with Apple Calendar (on both Mac and iOS).
If you let me know what information you need, and how to get the info, I'm happy to help hunt down the issue.
On Thu, 21 Apr 2022, at 18:24, Nader Akoury wrote:

@gmakstutis https://github.com/gmakstutis I don't have a Fastmail account, so I cannot test your issue directly. I have tested both iCloud and NextCloud and the CalDAV syncing works correctly for those providers. Can you sync your Fastmail calendar with a different CalDAV client. There are plenty to choose from, see list1 https://devguide.calconnect.org/CalDAV/Client-Implementations, list2 https://wiki.davical.org/index.php/CalDAV_Clients. If you can get it to work in one of those, but it doesn't work in this plugin, then you'll need to provide more information that can help pinpoint the specific issue.
—
Reply to this email directly, view it on GitHub https://github.com/davish/obsidian-full-calendar/issues/87#issuecomment-1105493667, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGLBCPCEMPBJJB5M4QBHB4TVGGFM5ANCNFSM5TGYZFTA.
You are receiving this because you were mentioned.Message ID: @.***>

--
Geoffrey Makstutis

Since this is a specific issue to fastmail, I'll rename the issue to indicate that so that others with the same problem can chime in if they face the same issue.
@dojoteef, you mentioned that Fastmail requires you to be on a Standard or Professional plan. @gmakstutis, did you confirm what plan you're on? It's possible that Apple Calendar is syncing via some other method than CalDAV.

Yes I have a Standard Plan, and I’m using app-specific passwords. Thanks
On Fri, 22 Apr 2022, at 00:19, Davis Haupt wrote:

Since this is a specific issue to fastmail, I'll rename the issue to indicate that so that others with the same problem can chime in if they face the same issue.
@dojoteef https://github.com/dojoteef, you mentioned that Fastmail requires you to be on a Standard or Professional plan. @gmakstutis https://github.com/gmakstutis, did you confirm what plan you're on? It's possible that Apple Calendar is syncing via some other method than CalDAV.
—
Reply to this email directly, view it on GitHub https://github.com/davish/obsidian-full-calendar/issues/87#issuecomment-1105848760, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGLBCPBNSOEIIADOJCZWBVTVGHPBJANCNFSM5TGYZFTA.
You are receiving this because you were mentioned.Message ID: @.***>

--
Geoffrey Makstutis

I can confirm I'm receiving the same error. I have a paid Standard @fastmail account, and generated a new app password for CalDAV. I used the URL  https://caldav.fastmail.com/ from here. I tried again with a fresh app password, with the same result.

Since multiple people are experiencing this, I'll make a note in the documentation that we don't support fastmail yet. After doing that, I'll change this from a bug to a feature request since it's clearly going to require some work. I don't use Fastmail and don't know if it's possible to test out its CalDAV implementation without paying for the service, so I'll also mark this as "help wanted" since it would be great if someone with a paid fastmail account could help out. I'm not sure if it's possible to scope permissions to a single calendar, but if so, someone could also email me an app-specific password for a sample calendar with no private events and I can try and take a look.

if you can give me an email to send details, I'll create an account for you on my Fastmail and share username/app-specific-password.

actually, I've just seen that there is an email on your github profile. I'll send through account details later today.

Actually, the CalDAV package the plugin uses supports debug logging. It
might be good to expose that as a plugin setting. That should allow people
to provide better error reporting (it’s Fastmail today, but another CalDAV
provider could error in the future).
On Mon, Apr 25, 2022 at 11:25 PM Davis Haupt @.***>
wrote:

Since multiple people are experiencing this, I'll make a note in the
documentation that we don't support fastmail yet. After doing that, I'll
change this from a bug to a feature request since it's clearly going to
require some work. I don't use Fastmail and don't know if it's possible to
test out its CalDAV implementation without paying for the service, so I'll
also mark this as "help wanted" since it would be great if someone with a
paid fastmail account could help out. I'm not sure if it's possible to
scope permissions to a single calendar, but if so, someone could also email
me an app-specific password for a sample calendar with no private events
and I can try and take a look.
—
Reply to this email directly, view it on GitHub
https://github.com/davish/obsidian-full-calendar/issues/87#issuecomment-1109265019,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALOP5PF2SJYFVNRCEYCUZ3VG5O3NANCNFSM5TGYZFTA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@davish Just checking that you'd received my email with Fastmail access details. Sent this information a week or so ago.

Hey everyone,
I was able to succesfully add my Fastmail calendar by using the following caldav URL format:
<EMAIL_ADDRESS>
It seemed to sync all of my Fastmail calendars successfully.

Enjoy!

I can confirm that @marcus-crane's solution has worked for me as well. Now... what about two-way syncing?

You can follow issue #25 for updates on two-way sync. I'll close this issue out when PR #106 is merged.


InsertMany then Find will raise duplicate key value violates unique constraint

Describe the bug
I use insertMany to insert multiple record, but if I find right after insertMany, it cause duplicate key value violates unique constraint.
Code describe
await this.em.insertMany(
    City,
    mongoCities.map((city) => this.em.create(City, city as any))
);

// Stop here will not raise error
// But if continute run below find code, it will raise duplicate key value violates unique constraint

const cities = await this.em.find(City, {});

Expected behavior
After insertMany, I can find without cause error !
Versions

Dependency
Version

node
16

mikro-orm
5.8

Btw, anyone know the difference between these two ways to insertMany, about what happens inside, performance? :

Insert many created entity.

await this.em.insertMany(
          City,
          mongoCities.map((city) => this.em.create(City, city as any))
      );

Persist multiple created entity then flush

mongoCities.forEach((city) => {
    const _city = this.em.create(City, city as any);
    this.em.persist(_city);
});
await this.em.flush();


Fix unmocked test call in KFF Vaxx

Description

the third call to github to retrieve the right url for "population_pct_share" was unmocked

mocks call in test missing the mock
adds line to fake github file to handle population_pct_share

Motivation and Context

fixes #1524
How has this been tested?

all tests pass (with internet disconneted)
Types of changes

Bug fix (non-breaking change which fixes an issue)

Thank you Ben!


Add CWE to Vulnerability kind

The OWASP Top 10 is one of the most comprehensive documents for the appsec  vulnerabilities. There is currently little or not support for its integration in security testing tools and secure software development pipelines,  despite the benefits this could bring. I raised a discussion about this in these security stack- exchange posts (1 & 2), where I clearly defined some ways through which this could be leveraged. Since grafeas is coming with a security automation objective, the information in the top 10 could be integrated somehow. This would in no small measure assist in assessing the applications that are deployed in containers.

I think there is some confusion about what Grafeas currently provides and what the OWASP Top 10 list covers.
For example, you might have a vulnerability scanner that notices CVE-2018-3760 applies to one of your resources and writes an occurrence to your Grafeas. It also happens that CVE-2018-3760 can be categorized as "A9:2017-Using Components with Known Vulnerabilities". However, there is no specific spot in a vulnerability to store the OWASP Top 10 mapping besides the description. (There is also no CVE  →  OWASP Top 10 mapping that I know of.)
The OWASP Top 10 list is definitely a useful resource. However, a specific known CVE provides more information about remediation than the generic recommendations of the entire category.

@SyCode7 I was inclined to agree with @Katee here re: top 10 and I empathize with you re: tooling 😢
But then I dug a little deeper (sorry I'm not well versed in appsec). I think CWE's make a great use case for Grafeas. Given CWEs are seemingly mapped to OWASP Top 10 (ref)
Adding support for CWEs seems like the right path for this project imo. Thoughts?

@j0npulsifer thank you for the support 👍 . To the best of my ability, most application vulnerabilities (including those affecting REST-based microservices) are not assigned CVEs. However, 98% of these vulnerabilities have CWEs. Interestingly, OWASP top 10 gives examples of CWEs per category, hence some vulnerability scanners attempt to prioritize support using the listed  CWEs e.g. Acunetix & Nessus.
@Katee , considering the proliferation of microservice architectures, Grafeas support for CWEs will be awesome !

It does seem like the existing vulnerability note isn’t well suited to hold CWEs. (The existing type can be thought of as a “Package Vulnerability” since it holds a bunch of package specific fields in Details).
We would definitely be open to a schema proposal to store CWE notes and occurrences in grafeas. Feel free to open a proposal type issue with such a schema proposal.

Thanks @Katee! I was initially going to suggest PACKAGE_VULNERABILITY but, like you, I feel like it'd be a bit of a stretch. I agree with you re: the new schema proposal
@SyCode7 do you feel comfortable opening a schema proposal for CWEs?

@Katee  thank you considering this proposal 👍
@jonpulsifer  sure, I will gladly like to do this, how do I open the proposal, here or elsewhere ?  Also,  am not yet familiar with how grafeas  works. Will it be fine to propose a generic schema that includes important CWE-related information or there are points /styles to mind?

@SyCode7 this is ready a good proposal, I am also thinking about how to do what you want. Maybe this kind can be a generic kind to support customize code scan?

Any people still there?


culprit should be cropped to 200 chars

Sending a culprit longer than 200 characters will cause sentry to fail inserting the event into the database (see here).
I encountered this while throwing an exception like this:
NSException(name: NSInternalInconsistencyException, reason: "foo is bar", userInfo: nil).raise()

This produced a culprit like this in sentry:
Application threw exception NSInternalInconsistencyException: (null)
Originated at or in a subcall of _TFC7TabTool30AttributedObjectViewController14collectionViewfTCSo16UICollectionView24didSelectItemAtIndexPathCSo11NSIndexPath_T_

So we should probably change how the culprit for exceptions is generated (it should probably just be the last part, demangled) and truncate all culprit strings to 200 characters (we could do something like putting the full culprit string into extra if the original was longer than 200 characters).

I'll probably send a PR tomorrow changing Event-serialization to truncate the culprit if necessary.

Going to close this since I'm just going to remove the culprit completely since not relevant in this client. Thanks for the work though!


Don't extend from MenuItemAction

see https://github.com/microsoft/vscode/blob/2f984aad710215f4e4684a035bb02f55d1a9e2cc/src/vs/workbench/contrib/notebook/browser/contrib/notebookActions.ts#L563
⬆ instead of that, just add a new menu and register a menu item for that command, no duplication required, UX state update etc all for free

@jrieken is there any way to register an action without registering a menu first?

Yeah, it's all just symbolic. Create a new menu id (exported) and register commands for that, then when rendering using the menu service to get the menu

@roblourens I found that ExecuteCellAction is also extending MenuItemAction and it's used programmatically in cell renderers.

Yeah, but the run cell area is not really a "menu" and nobody else should be able to contribute actions to it. If they do it will break the layout. It's just a special button. Thus it seems like an exception to the rule.

Leaving the run button alone. Rewrote the between cell toolbar to be a real toolbar


--raw: erratic behaviour

Seen in f533d15ac25f381138f4be94d9288e06b3bf9ea3:
It seems like phetch is ignoring its first argument after --raw:
$ phetch --raw phkt.io
--raw needs gopher-url
$ phetch --raw IGNORED phkt.io | head -1
i  ____    _   _     _  __    _____	(null)	phkt.io	70
$ phetch --version
phetch v0.1.12-dev

Whoops, thank you! This will be fixed in the next release.


[feature request]each book pages

For Feature Requests
Desired Feature:

Changing defaualt book navigation location in setting.
Setting book navigation to right or left in admin setting screen.

Hiding Book navigation
If we can hide the book navigation by clicking button, it is great.

Folder style book navigation
If we can fold each book, it would be great.

Need more space for html editor
Currently, html editor is not fully expanded so that we can have more edit space.

I found why there is extra space on editor.
There is max-width defined as 840px in css.
When I remove that, it is fully expanded.
Possibly, this should go to issue list.

Hi @msaus, Thank you for your comments.

Changing defaualt book navigation location in setting.
Setting book navigation to right or left in admin setting screen.

I'd prefer to not add an additional setting unless really required. As part of the upcoming redesign the navigation will be moving to the left.

Hiding Book navigation
If we can hide the book navigation by clicking button, it is great.

Not sure about this as there's more than the book nav in the sidebar. I'd suggest waiting for the next release due to design changes.

Folder style book navigation
If we can fold each book, it would be great.

Not sure how this fundamentally differs to the current setup.

Need more space for html editor
Currently, html editor is not fully expanded so that we can have more edit space.

This is done very much so on purpose to emulate how the content will show on the page.
For future reference, issues like this with many requests are quick hard to manage. Separate, Well defined, issues allow each to be separately managed and discussed.

Thank you very much for your comment.
Then, I will wait for the new design and tell  you some feedback.


[backport] Add compute_35 for CUDA 11.0+

Backport of #4137

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit a0bfe8c5e0da99abae9c803e89612915473ba17e, target branch v8) succeeded!

LGTM!


wordcloud problems (python3.7)

Running the script only works with 3.7 for me and generates the following error after installing all dependencies for the correct version with "python3.7 -m pip install -r requirements.txt":
(Someone format this to code it's not working for me sry)
`
Generating Word Cloud.....
Traceback (most recent call last):
File "report.py", line 234, in
visual.wordCloud()
File "report.py", line 83, in wordCloud
max_words=380,contour_width=2, prefer_horizontal=1).generate(unique_string)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 619, in generate
return self.generate_from_text(text)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 601, in generate_from_text
self.generate_from_frequencies(words)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 434, in generate_from_frequencies
max_font_size=self.height)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 483, in generate_from_frequencies
font = ImageFont.truetype(self.font_path, font_size)
File "/home/flew/.local/lib/python3.7/site-packages/PIL/ImageFont.py", line 640, in truetype
return freetype(font)
File "/home/flew/.local/lib/python3.7/site-packages/PIL/ImageFont.py", line 637, in freetype
return FreeTypeFont(font, size, index, encoding, layout_engine)
File "/home/flew/.local/lib/python3.7/site-packages/PIL/ImageFont.py", line 186, in init
font, size, index, encoding, layout_engine=layout_engine
OSError: cannot open resource
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/init.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in
import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in
from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in
import apt
File "/usr/lib/python3/dist-packages/apt/init.py", line 23, in
import apt_pkg
ModuleNotFoundError: No module named 'apt_pkg'
Original exception was:
Traceback (most recent call last):
File "report.py", line 234, in
visual.wordCloud()
File "report.py", line 83, in wordCloud
max_words=380,contour_width=2, prefer_horizontal=1).generate(unique_string)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 619, in generate
return self.generate_from_text(text)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 601, in generate_from_text
self.generate_from_frequencies(words)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 434, in generate_from_frequencies
max_font_size=self.height)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 483, in generate_from_frequencies
font = ImageFont.truetype(self.font_path, font_size)
File "/home/flew/.local/lib/python3.7/site-packages/PIL/ImageFont.py", line 640, in truetype
return freetype(font)
File "/home/flew/.local/lib/python3.7/site-packages/PIL/ImageFont.py", line 637, in freetype
return FreeTypeFont(font, size, index, encoding, layout_engine)
File "/home/flew/.local/lib/python3.7/site-packages/PIL/ImageFont.py", line 186, in init
font, size, index, encoding, layout_engine=layout_engine
OSError: cannot open resource
`

Enclose multi-line code blocks with 3 backticks to format it, like this:
```
multi
line
code
```

Looks more like a problem related to the differences between linux and windows, but I'll have to investigate further to confirm that assumption.

Traceback (most recent call last):
File "report.py", line 234, in
visual.wordCloud()
File "report.py", line 83, in wordCloud
max_words=380,contour_width=2, prefer_horizontal=1).generate(unique_string)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 619, in generate
return self.generate_from_text(text)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 601, in generate_from_text
self.generate_from_frequencies(words)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 434, in generate_from_frequencies
max_font_size=self.height)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 483, in generate_from_frequencies
font = ImageFont.truetype(self.font_path, font_size)
File "/home/flew/.local/lib/python3.7/site-packages/PIL/ImageFont.py", line 640, in truetype
return freetype(font)
File "/home/flew/.local/lib/python3.7/site-packages/PIL/ImageFont.py", line 637, in freetype
return FreeTypeFont(font, size, index, encoding, layout_engine)
File "/home/flew/.local/lib/python3.7/site-packages/PIL/ImageFont.py", line 186, in init
font, size, index, encoding, layout_engine=layout_engine
OSError: cannot open resource
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/init.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in
import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in
from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in
import apt
File "/usr/lib/python3/dist-packages/apt/init.py", line 23, in
import apt_pkg
ModuleNotFoundError: No module named 'apt_pkg'
Original exception was:
Traceback (most recent call last):
File "report.py", line 234, in
visual.wordCloud()
File "report.py", line 83, in wordCloud
max_words=380,contour_width=2, prefer_horizontal=1).generate(unique_string)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 619, in generate
return self.generate_from_text(text)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 601, in generate_from_text
self.generate_from_frequencies(words)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 434, in generate_from_frequencies
max_font_size=self.height)
File "/home/flew/.local/lib/python3.7/site-packages/wordcloud/wordcloud.py", line 483, in generate_from_frequencies
font = ImageFont.truetype(self.font_path, font_size)
File "/home/flew/.local/lib/python3.7/site-packages/PIL/ImageFont.py", line 640, in truetype
return freetype(font)
File "/home/flew/.local/lib/python3.7/site-packages/PIL/ImageFont.py", line 637, in freetype
return FreeTypeFont(font, size, index, encoding, layout_engine)
File "/home/flew/.local/lib/python3.7/site-packages/PIL/ImageFont.py", line 186, in init
font, size, index, encoding, layout_engine=layout_engine
OSError: cannot open resource


Use Numpy infix notation (& clean up code a bit).

Changes proposed in this pull request:

Use Numpy infix notation
Clean up surrounding code (could be broken in another PR)

Checklist

[x] Code complies with PEP-8 and is consistent with the framework.
[x] Code is properly documented.
[x] Tests are included for new functionality or updated accordingly.
[x] Travis CI build passes with no errors.
[x] Test Coverage is maintained (threshold is -0.2%).
[x] Files changed (update, add, delete) are in the PR's scope (no extra files are included).

@AlbandeCrevoisier, please merge the last changes from master into your branch so that we proceed with the reviewing process. Since the creation of this PR, @jacobmontiel and I found some bugs in the Hoeffding Tree Regressors. Very much alike (and unfortunately) you will need to re-apply the infix notation to some of the affected code portions.
Thanks for the hard work so far. Let me know if you need any assistance.

Stale PR, see #238