Eelco

Thanks for your response @danwild I appreciate it. ~~Before I opened this issue I tried loading the data myself in both a blob and arraybuffer but `geotiff.js` throws an error...

When I run the demo the tif's are only requested once so I assume something must be wrong on my (front- or back-) end.

Increasing the `blockSize` fixes the issue where the tiff is requested multiple times. ~~I can't get the `fromArrayBuffer` to work. [This expression](https://github.com/onaci/leaflet-geotiff-2/blob/d954d78ae69c79dd53d89014d7850e0e7a8d4a1a/src/leaflet-geotiff.js#L156) is always true. First I believed it was...

> For initial load of data, you could use the `sourceFunction` option with something other than `GeoTIFF.fromUrl` (i.e. handle the async pre-load of data yourself). So this suggestion works fine...

An update. I added a test case to reproduce this issue in my cloned repository. Test case can be found [here](https://github.com/eelcocramer/yang/blob/900a2a8ef377e0bc7d110d1aa5349aa93b654246/node/xpath_test.go#L102). The [error is generated in the `resolvePath` function](https://github.com/freeconf/yang/blob/b01a95555007372bdbea8bcb11b549db93c73534/node/xpath_impl.go#L17) of...

I tried running the test with a debugger to see if I could understand how it works but I'm lost at the `yacc` stuff.

But `../status` refers to the parent of `message` and that does have the `status` field. Without the `../` (so when this library does work) [pyang](https://github.com/mbj4668/pyang) and other linters complain with...

When I install the version before the latest PR the error does not occur. I.e. `fisher install gazorby/fifc@1bc301453f674ed21fac4979c65a9a4cb7f2af61`

Yes