Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • fractal fractal
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 280
    • Issues 280
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • fractalfractal
  • Issues
  • #341

Closed
Open
Created Sep 27, 2018 by Daniel Garcia Moreno@danigmDeveloper0 of 6 tasks completed0/6 tasks

Sync and Initial sync problems

With the inclusion of the since always in the sync in the backend we've some issues that we need to solve. The workflow has changed so we need to test all corner cases and refactor the code to fix those problems.

Tests to make:

  • New messages comes
  • New room, you join to a new room and the room should appear in your list
  • Delete room, leave a room and see the action
  • Initial sync after several days, with an old since in the cache. The message history should be consistent
  • Load more shows the corresponding messages
  • Load more shows the corresponding messages if we've an old cache (two days?)

Feel free to edit this issue description and add more test to make.

Assignee
Assign to
Time tracking