as lester pointed out, this seems to have been resolved. For now logging out and then logging back in seems to resolve this issue.
as lester pointed out, this seems to have been resolved. For now logging out and then logging back in seems to resolve this issue.