checker | Simple custom monitoring and alerting tool | Chat library

You need to explicitly create the object for that test suite & execute it. In IDE you're relying on specific runner, but it doesn't work in the notebook environment.

You can use either the .execute function of create object (docs):

The thing the compiler is looking for is a lifetime bound. A lifetime bound of 'a doesn't mean “this type is a reference with lifetime 'a”, but rather “all of the references this type contains have lifetimes of at least 'a”.

(When a lifetime bound is written explicitly, it looks like where T: 'a.)

Thus, any type which does not contain any references (or rather, has no lifetime parameters) automatically satisfies the 'static lifetime bound. If T: 'static, then Arc: 'static (and the same for Box and Rc).

How could Arc::clone(&msg) get a 'static lifetime? The value it points to isn't known at compile-time, and could die before the whole program exits.

It does not point to the value using a reference, so it's fine. The type of your value is Arc>; there are no lifetime parameters here because there are no references. If it were, hypothetically, Arc<'a, Mutex> (a lifetime parameter which Arc doesn't actually have), then that type would not satisfy the bound.

The job of Arc (or Rc or Box) is to own the value it points to. Ownership is not a reference and thus not subject to lifetimes.

However, if you had the type Arc<&'a str>> then that would not satisfy the bound, because it contains a reference which is not 'static.

Maybe try stripping your raw text- readlines() will return \n (newline characters), as well.

How about a repeated group?

^~killc(?: [^ ]+)+$

This will capture one or more usernames when put into the command. Actually parsing them is up to you, but if the usernames are well formatted, this will catch them. Personally, I'd be very careful around [^ ]+ since it's going to accept a newline as a match; try \S+ instead if it's available, which will match anything that's not whitespace.

There is no guarantee checker() gets more than zero arguments, in which case the loop body would be executed zero times, so no return statements would be reached.

So the compiler is rightful to complain about a missing return, as this condition is decided at runtime.

E.g. if you pass 0 arguments: checker(), it's valid and would cause problem if a return would not be demanded.

So simply add a return statement with reasonable return values, often the zero values of the result types:

It looks like the type system of Dart is not so powerful. The only thing that looks (from first glance) possible is to create a custom code analyzer package (or search for one that already exists).

Link to w3School

You have to keep same name. in your case:

The problem is you called read_loggedIn() which is a future but you called it directly and while its not returning value you got a null value. So you have to await until you get the result from read_loggedIn() and then you can use its value.

Replace your main method with bellow code

You can use the JavaScript submit() function to remotely submit your form depending on the response. This would mean that instead of using a submit button, you'd have to use a normal button.