Potential Authorization Bug v0.4.0 about chainclient.py HOT 2 OPEN

It appears that child objects don't always get the authentication information of their parents. The following sequence fails:

• Connect and fetch a site using chainclient.get with the site URL and auth=(..., ...) set. (Succeeds)
• Create a new device within the site. (Succeeds)
• Create a new sensor for the device. (Succeeds)
• Post new data for the sensor. (Fails)

Running the same program again works fine, as the device and sensors already exist, and data can be posted.

from chainclient.py.

Thanks for the info. I suspected it was something like that, but hadn't had time to put together a specific test case.

As workaround until the issue is actually fixed, the create method takes an auth keyword argument as well, so scripts can add the auth information to the individual requests instead of relying on inheriting it from the root object.

from chainclient.py.