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

Describe the bug

Currently keys written to server.conf go undetected.

This means that not only typos go undetected, but lack of validation is a risk during version migration as settings that used to apply in a previous version have no effect in a newer one without warning -- even if new settings are supposed to be used.

To reproduce

• Create a key with a typo.
• Watch the QuestDB

In implementations/rust/ockam/ockam_transport_ble/src/driver/packet.rs:104:

// TODO Currently we only support packet lengths up to 2^16
// bits long.
//
// The reason for this is that I'm too lazy right now to setup
// a control channel for this BLE UART implementation and
// instead rely on the probability of receiving an 8 byte long
// packet consisting of 6 zero bytes followed b

The API happily accepts attribute updates for host_name and service_name of Downtime objects. That doesn't sound like a good idea to me, just look at the inconsistency between the object name and its attributes in the console transcript below.

I haven't checked any other object types for similar issues, so there might be more as well.

$ downtime=$(curl -skSu root:icinga -H 

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

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.