Closed sketchkey closed 1 year ago
Hi @sketchkey - Thanks for submitting this issue. Our APIs recently updated how they deliver error messages and we were slow in merging the corresponding fix to gfwr
. This was corrected earlier this week, so try updating gfwr
via devtools
again and see if the error persists.
Yep updated via devtools and problem solved — many thanks!
Great! Thanks again for submitting the issue.
I was just asked this morning by a colleague if I'd ever seen a specific GFWR error before, and after re-running some previously working code it looks like it's a new issue with the events API.
get_vessel_info
works fine, butget_event
just hangs for a while and then throws an error (reprex below is from the GFWR Readme example):After 5-10 mins the following error is given (I've included the backtrace output from
rlang::last_error()
:I also tried force-updating the GFWR package via devtools, but the issue still persists!