Instructions

In product card when you modify lenght, width or heigth, it automatically calculate surface and then you will obtain weird values in surface field in this card.

Bug

If you crate or modify a product card with length, height and length values : it automatically calculate surface value but you have not the good value.

Environment

• Version: develop, Dolibarr v10
• **

Hi,

As per title, it would be a nice improvement to add the tickets reference and links to the release notes and in the change log.

Clearly describe the data problem

The documentation says this is the result to expect

 {
        "symbol": "AAPL",
        "exDate": "2017-08-10",
        "paymentDate": "2017-08-17",
        "recordDate": "2017-08-14",
        "declaredDate": "2017-08-01",
        "amount": 0.63,
        "flag": "Dividend income",
        "currency": "USD",
        "description": "Apple decl

Expected Behavior

Is there an elegant and simple way to visualize a few trading models plotted on 1 chart? In fact a lot of projects like mine are centered around comparing various models (and even groups of models), so that would be handy to have a sugary way around this process, so:

1. individual models with notations on one chart
2. a group of models trading on the same account each ha

Took 58 days to hit the rook-ceph cluster issue again, and I figured I would leave this open until there's the next "days since last accident" event:

jay@home1:/opt/metalnetes$ k get po -n rook-ceph
NAME                                          READY   STATUS             RESTARTS   AGE
rook-ceph-mgr-a-68cb58b456-6m8df              1/1     Running            0          58d
rook-ceph-mon-

How to reproduce:

In [1]: import pyEX
In [2]: client = pyEX.client.Client()

What's your feature?
it's hard to know what the data mean

Why are you interested in it being added?

>>> print(spy.keys())
dict_keys(['margin_initial_ratio', 'rhs_tradability', 'id', 'market', 'simple_name', 'min_tick_size', 'maintenance_ratio', 'tradability', 'state', 'type', 'tradeable', 'fundamentals', 'quote', 'symbol', 'day_trade_ratio', 'name', 'tradable_chain_id', 'splits'

As time has passed, various changes have been made or requested for the Tiingo API as new endpoints were added or removed, which don't really involve Python specific details

• #337
• #82
• #317
• Others that presently escape my memory

In an effort to make it easier for people to work with Tiingo and other APIs as fields are added or removed over time, I've been using stoplight.io to w