Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Per day pagination is off #6230

Closed
rachelhamlin opened this issue Oct 10, 2018 · 2 comments
Closed

Per day pagination is off #6230

rachelhamlin opened this issue Oct 10, 2018 · 2 comments

Comments

@rachelhamlin
Copy link
Contributor

User Story

As a user, I want Status time/dates and pagination to match my current time zone, so that I'm not confused about when messages are sent and received.

Description

Type: Bug

Summary: @yenda sent me a message at 7:47 PM Eastern Time. I first saw it at 11 PM EDT, but Status had placed it under Yesterday.

Expected behavior

Per day pagination is accurate to my time zone. A message received at 7:47 PM is from Today.

Actual behavior

At 11:08 PM -
image

Reproduction

  • Check day of messages sent later in the evening for time zones behind GMT.

Additional Information

  • Status version: Desktop nightly
  • Operating System: Mac OS
@churik
Copy link
Member

churik commented Oct 10, 2018

@rachelhamlin
Is it not the same as #5281?

@rachelhamlin
Copy link
Contributor Author

@churik looks like it :) closing, thanks.

ilmotta added a commit that referenced this issue Dec 27, 2024
…ightmode (#21865)

Upgrades status-go to version v8.0.0, which includes the fix from PR
status-im/status-go#5964 fix_: bad peer check logic for
lightmode and some fixes.

Might resolve #18031

Areas that may be impacted: we are moving from status-go version 7.0.0 to 8.0.0.
These are the changes:

- status-im/status-go@a4e36d49c * fix_: missing message verifier start-stop ,go-waku updates, lightpush service rate limits (#5964)
- status-im/status-go@810468a57 * test_: create private group tests (#6225)
- status-im/status-go@0cf556bdb * test_: unskip test initialize logging (#6229)
- status-im/status-go@b803918c2 * ci_: pytest-lint correct target pr branch (#6230)
- status-im/status-go@d29120447 * chore(block)!: remove desktop BlockContact function for parity (#6172)
- status-im/status-go@309d17ae5 * feat_: status-backend health endpoint (#6201)
- status-im/status-go@6a5623bac * test_: set proxy creds (#6211)
- status-im/status-go@2172abe95 * fix_: add infuraSecret and statusProxyBlockchainPassword to secrets (#6217)
- status-im/status-go@0f7c26dc9 * test_: skip flaky TestService_IncrementalUpdateMixed (#6205)
- status-im/status-go@75bdda271 * fix_: correct sensitive regex (#6188)
- status-im/status-go@08eee8a64 * test_: add python linters (#6212)
- status-im/status-go@66850321e * fix_: remove logging of rpc endpoint (#6195)
- status-im/status-go@c27c773c2 * chore(wallet)_: from and to chains added to send details
- status-im/status-go@74db63143 * test_: contact requests tests (#6167)
- status-im/status-go@5a8310d5a * fix(pins)_: delete pins when the og message is deleted (#6173)
- status-im/status-go@137698e02 * ci_: bring back cmd coverage (#6204)
- status-im/status-go@1795620df * test_: run functional tests on host (no container) (#6159)
- status-im/status-go@ef177c1c6 * feat_: SensitiveString type (#6190)
- status-im/status-go@8b95c8148 * feat_: graceful shutdown with status-backend (#6189)
- status-im/status-go@e6c2f89f0 * chore_: remove endpoint InitLogging (#6182)
- status-im/status-go@4ccb08f11 * test_: WalletService class (#6171)
- status-im/status-go@943ae1335 * fix(functional-tests)_: disable testnet (#6181)
- status-im/status-go@616a76098 * feat_: api logging signals (#6150)
- status-im/status-go@dfb591874 * fix_: check group error in GetBalancesAtByChain (#6169)
- status-im/status-go@3a0080281 * fix_: create/restore account error signal (#6174)
- status-im/status-go@e7cc53529 * feat(telem)_: track total waku message bandwidth (#6157)
- status-im/status-go@d07e61f61 * fix_: nil *MessengerResponse is a valid result (#6175))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants