influxdb

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

Scenario

create table tab(f float);
insert into tab(f) values(4273.8);

Results in: org.postgresql.util.PSQLException: ERROR: inconvertible types: DOUBLE -> FLOAT [from=4273.8, to=f]

Expectation

Possibly enhance type compatibility check (SqlCompiler.isAssignableFrom) with extra cases for numeric types:

• Float <- Double: if the double fits in the Float, then

Describe the bug

/usr/share/icinga2/include/command-plugins.conf provides the http CheckCommand. Since version 2.3.0 there is a new option in check_http which allows for checking the correctness of a certificate and hostname match: --verify-host. Please add this to the built in template library.

https://icinga.com/docs/icinga2/latest/doc/10-icinga-template-library/

$ /usr/

Hello David,

I have spent more than 20hours installing unpoller to Ubuntu 21.04 64bit. It seems that everything is working but Unpollen can not pick up settings from unpoller.conf file. Instead of that it is taking some default config file with URL https://127.0.0.1:8443: unifi controller. I have UDM Pro...

I have even try to set path with
docker run -v /home/ubuntu/Docker/unpoller:/config

Writing tests for nodes and workers is complex due to their async nature. In tests we can't use the #[ockam::node] attribute, and instead use the method of

let (ctx, executor) = ockam::start_node()
executor.execute(async move { ...

This method has problems: if a test assertion fails inside of this async block, the test will not fail. Instead, the Node remains alive. I believe

A useful feature where the user specifies the quantity to take in an orderbook and callback returns the average price paid for that lot size. For example if the offers in the order book for BTC-USD was the following:

Price | size
11,000 | 1
10,500 | 1
10,000 | 1

If the user specified quantity 3, the callback would return 10,500.