tonic | A pre/post processing toolbox for hydrologic models | Machine Learning library

Just replace everything excluding alphanumerics with nothing. Code below.

The option is #[cfg(test)] (singular), not #[cfg(tests)] (plural). This is probably not failing because it's not being compiled or run at all, since the option is never set.

Thank you Omer Erden for answering this. So it came down to implementing AsyncRead based on the futures::Stream trait, which tonic::Streaming implements. Here is the code I actually used.

We can leverage the fact that we can pass tuples as a MultiIndex slicer. Also we slightly adjust your my_dict. Then we apply a simple for loop:

There is currently (as of version 0.2.1 of scalapb-validate) no way to suppress the generation of validation classes once you add the validation plugin. The only way, right now to do that would be to separate the messages you don't want to have validators for to separate SBT subprojects which doesn't have the validator plugin turned on.

Feel free to start a github issue on scalapb-validate github to discuss this as a feature request, and include also the motivation for a change like this. This would require some thought since messages that have validators require all the message that they transitively reference to have validators as well, so the plugin would have to detect this situation when disabling generation.

From the Tonic documentation:

Sending a request on a channel requires a &mut self and thus can only send one request in flight. This is intentional and is required to follow the Service contract from the tower library which this channel implementation is built on top of.
...
To work around this and to ease the use of the channel, Channel provides a Clone implementation that is cheap. This is because at the very top level the channel is backed by a tower_buffer::Buffer which runs the connection in a background task and provides a mpsc channel interface. Due to this cloning the Channel type is cheap and encouraged.

Therefore, you can clone the client for each concurrent request you make. This eliminates the possibility of a single client being mutably borrowed more than once at any given time, so the borrow checker is appeased.

You can use aggregation:

deriveAll is a routine defined on ConcreteScale instances. You attempted to call it on an instance of AbstractScale. Try calling it on your variable myScaleA, which is concrete.

Try adding the link attribute to v-list-items and wrapping them in a v-list-item-group

Edit with the modification:

It is enough to wrap your sublist items in a v-list-item-group: