[BUG] KeyError: 'nextSequenceToken'

[datitran]

The SequenceToken is ignored by the API and actually deprecated:

The sequenceToken parameter is now ignored in PutLogEvents actions. PutLogEvents actions are now accepted and never return InvalidSequenceTokenException or DataAlreadyAcceptedException even if the sequence token is not valid.

We get this error here because the response expect it:

Traceback...
  File "/usr/local/lib/python3.10/logging/__init__.py", line 1624, in _log
    self.handle(record)
  File "/usr/local/lib/python3.10/logging/__init__.py", line 1634, in handle
    self.callHandlers(record)
  File "/usr/local/lib/python3.10/logging/__init__.py", line 1696, in callHandlers
    hdlr.handle(record)
  File "/usr/local/lib/python3.10/logging/__init__.py", line 968, in handle
    self.emit(record)
  File "/usr/local/lib/python3.10/site-packages/cloudwatch/cloudwatch.py", line 100, in emit
    self.send_log(timestamp, log_entry)
  File "/usr/local/lib/python3.10/site-packages/cloudwatch/cloudwatch.py", line 88, in send_log
    self.next_sequence_token = response['nextSequenceToken']
KeyError: 'nextSequenceToken'

[ernestomi]

Thanks for the report @datitran, could you confirm what Python version you are using when observing this?

[datitran]

Yes we use Python Version 3.10. The error comes from time to time. I guess it's some kind of race condition when multiple stream are used to write to cloudwatch. However, we can safely ignore this. I opened a PR to fix it already.

[ernestomi]

@datitran thanks for the PR! Im just going to test it before merging and deploying