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

GO-4486 migrating filestore to fileobject #1990

Open
wants to merge 56 commits into
base: main
Choose a base branch
from

Conversation

deff7
Copy link
Member

@deff7 deff7 commented Jan 6, 2025

No description provided.

deff7 added 30 commits November 13, 2024 12:19
go-4486-research-migrating-filestore-fileobject

# Conflicts:
#	core/block/editor/fileobject/file.go
#	core/block/export/export.go
#	core/block/import/importer.go
#	core/files/fileobject/fileindex.go
#	core/files/fileobject/fileindex_test.go
#	core/files/fileobject/filemodels/filerequest.go
#	core/files/fileobject/service.go
#	core/files/fileoffloader/offloader.go
#	core/files/mock_files/mock_File.go
#	core/files/mock_files/mock_Image.go
#	space/internal/components/personalmigration/personalmigration.go
deff7 added 18 commits November 27, 2024 11:37
…l-details-structure' into go-4486-research-migrating-filestore-fileobject

# Conflicts:
#	core/block/editor/factory.go
#	core/files/fileobject/service_test.go
#	pkg/lib/bundle/relation.gen.go
#	pkg/lib/bundle/relations.json
go-4486-research-migrating-filestore-fileobject

# Conflicts:
#	core/block/editor/files.go
#	core/file.go
#	core/files/fileobject/fileindex.go
…o-4486-research-migrating-filestore-fileobject

# Conflicts:
#	core/block/editor/basic/details.go
#	core/block/editor/file/file.go
#	core/block/editor/state/state.go
#	core/block/import/common/objectid/oldfile.go
#	core/files/filesync/stats.go
#	core/files/filesync/upload.go
Copy link

github-actions bot commented Jan 6, 2025

Previous Coverage 50.7% of statements
New Coverage 50.8% of statements
Patch Coverage 48.0% of changed statements (234/487)

Coverage provided by https://github.com/seriousben/go-patch-cover-action

Copy link

Testomat.io Report 🔴 SMOKE-TEST FAILED
Tests ✔️ 16 tests run
Summary 🔴 15 failed; 🟢 1 passed; 🟡 0 skipped
Duration 🕐 21 minutes, 43 seconds
Testomat.io Report 📊 Run #e8429c55
Job 🗂️ Smoke Tests / smoke-test
Operating System 🖥️ Linux X64

✅ Passed Tests (1)

  • Owner changes the rights of a user from Viewer to Editor (1 minute, 45 seconds) Passed on retry: 2

🟥 Failures (15)

🔴 Revoking an invite link

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (138406.87ms)
And the user 1 is using client 1 (0.66ms)
And the user creates a new account on "staging" (1418.50ms)
And the account is synced within 60 seconds (62022.57ms)
Given the user has shared his space and generated an invite link (0.00ms)
When the user revokes the invite link (0.00ms)
Then the invite link should be invalid (0.00ms)
And the account is deleted (0.00ms)
And the server 1 is stopped (0.00ms)

🔴 Revoking an invite link (Will be retried 🔄)

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3314.65ms)
And the user 1 is using client 1 (0.39ms)
And the user creates a new account on "staging" (1436.24ms)
And the account is synced within 60 seconds (62049.63ms)
Given the user has shared his space and generated an invite link (0.00ms)
When the user revokes the invite link (0.00ms)
Then the invite link should be invalid (0.00ms)
And the account is deleted (0.00ms)
And the server 1 is stopped (0.00ms)

🔴 User cancels their join request

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3334.84ms)
And the user 1 is using client 1 (0.36ms)
And the user creates a new account on "staging" (1408.28ms)
And the account is synced within 60 seconds (62036.58ms)
Given the user creates an object 1 in the account (0.00ms)
And the user can open the object 1 (0.00ms)
And the user has shared his space and generated an invite link (0.00ms)
And the account is synced within 60 seconds (0.00ms)
And the server "default" 2 is running (0.00ms)
And the user 2 is using client 2 (0.00ms)
And the user creates a new account on "staging" (0.00ms)
And the user sends requests to join the space (0.00ms)
And the user cancels their join request (0.00ms)
And the user 1 is using client 1 (0.00ms)
Then there is no request pending for joining the space (0.00ms)
And both accounts are deleted (0.00ms)
And both servers are stopped (0.00ms)

🔴 User cancels their join request (Will be retried 🔄)

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3350.11ms)
And the user 1 is using client 1 (0.34ms)
And the user creates a new account on "staging" (1403.92ms)
And the account is synced within 60 seconds (62107.08ms)
Given the user creates an object 1 in the account (0.00ms)
And the user can open the object 1 (0.00ms)
And the user has shared his space and generated an invite link (0.00ms)
And the account is synced within 60 seconds (0.00ms)
And the server "default" 2 is running (0.00ms)
And the user 2 is using client 2 (0.00ms)
And the user creates a new account on "staging" (0.00ms)
And the user sends requests to join the space (0.00ms)
And the user cancels their join request (0.00ms)
And the user 1 is using client 1 (0.00ms)
Then there is no request pending for joining the space (0.00ms)
And both accounts are deleted (0.00ms)
And both servers are stopped (0.00ms)

🔴 User deletes the space and rejoins later

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3352.62ms)
And the user 1 is using client 1 (0.29ms)
And the user creates a new account on "staging" (1421.73ms)
And the account is synced within 60 seconds (62050.62ms)
Given the user creates an object 1 in the account (0.00ms)
And the user can open the object 1 (0.00ms)
And the user has shared his space and generated an invite link (0.00ms)
And the account is synced within 60 seconds (0.00ms)
And the server "default" 2 is running (0.00ms)
And the user 2 is using client 2 (0.00ms)
And the user creates a new account on "staging" (0.00ms)
And the user sends requests to join the space (0.00ms)
When the user 1 approves the join request of user 2 with "Viewer" rights (0.00ms)
And the user 2 is using client 2 (0.00ms)
And the user 2 leaves the shared space (0.00ms)
And the user sends requests to join the space (0.00ms)
Then the request is automatically approved as "Viewer" again (0.00ms)
And both accounts are deleted (0.00ms)
And both servers are stopped (0.00ms)

🔴 User deletes the space and rejoins later (Will be retried 🔄)

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3340.31ms)
And the user 1 is using client 1 (0.27ms)
And the user creates a new account on "staging" (1421.61ms)
And the account is synced within 60 seconds (62064.40ms)
Given the user creates an object 1 in the account (0.00ms)
And the user can open the object 1 (0.00ms)
And the user has shared his space and generated an invite link (0.00ms)
And the account is synced within 60 seconds (0.00ms)
And the server "default" 2 is running (0.00ms)
And the user 2 is using client 2 (0.00ms)
And the user creates a new account on "staging" (0.00ms)
And the user sends requests to join the space (0.00ms)
When the user 1 approves the join request of user 2 with "Viewer" rights (0.00ms)
And the user 2 is using client 2 (0.00ms)
And the user 2 leaves the shared space (0.00ms)
And the user sends requests to join the space (0.00ms)
Then the request is automatically approved as "Viewer" again (0.00ms)
And both accounts are deleted (0.00ms)
And both servers are stopped (0.00ms)

🔴 Owner changes the rights of a user from Viewer to Editor

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3424.80ms)
And the user 1 is using client 1 (0.23ms)
And the user creates a new account on "staging" (1435.98ms)
And the account is synced within 60 seconds (62082.28ms)
Given the user creates an object 1 in the account (0.00ms)
And the user can open the object 1 (0.00ms)
And the user has shared his space and generated an invite link (0.00ms)
And the account is synced within 60 seconds (0.00ms)
And the server "default" 2 is running (0.00ms)
And the user 2 is using client 2 (0.00ms)
And the user creates a new account on "staging" (0.00ms)
And the user sends requests to join the space (0.00ms)
When the user 1 approves the join request of user 2 with "Viewer" rights (0.00ms)
And the user 1 changes the rights of user 2 from "Viewer" to "Editor" (0.00ms)
And the user 2 is using client 2 (0.00ms)
Then the user can open the object 1 (0.00ms)
And the user can rename the object 1 (0.00ms)
And both accounts are deleted (0.00ms)
And both servers are stopped (0.00ms)

🔴 Owner approves a join request with Editor permissions

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3548.65ms)
And the user 1 is using client 1 (0.23ms)
And the user creates a new account on "staging" (1456.77ms)
And the account is synced within 60 seconds (62024.91ms)
Given the user creates an object 1 in the account (0.00ms)
And the user can open the object 1 (0.00ms)
And the user has shared his space and generated an invite link (0.00ms)
And the account is synced within 60 seconds (0.00ms)
And the server "default" 2 is running (0.00ms)
And the user 2 is using client 2 (0.00ms)
And the user creates a new account on "staging" (0.00ms)
And the user sends requests to join the space (0.00ms)
When the user 1 approves the join request of user 2 with "Editor" rights (0.00ms)
And the user 2 is using client 2 (0.00ms)
Then the user can open the object 1 (0.00ms)
And the user can rename the object 1 (0.00ms)
And both accounts are deleted (0.00ms)
And both servers are stopped (0.00ms)

🔴 Owner approves a join request with Editor permissions (Will be retried 🔄)

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3398.70ms)
And the user 1 is using client 1 (0.23ms)
And the user creates a new account on "staging" (1422.98ms)
And the account is synced within 60 seconds (62100.26ms)
Given the user creates an object 1 in the account (0.00ms)
And the user can open the object 1 (0.00ms)
And the user has shared his space and generated an invite link (0.00ms)
And the account is synced within 60 seconds (0.00ms)
And the server "default" 2 is running (0.00ms)
And the user 2 is using client 2 (0.00ms)
And the user creates a new account on "staging" (0.00ms)
And the user sends requests to join the space (0.00ms)
When the user 1 approves the join request of user 2 with "Editor" rights (0.00ms)
And the user 2 is using client 2 (0.00ms)
Then the user can open the object 1 (0.00ms)
And the user can rename the object 1 (0.00ms)
And both accounts are deleted (0.00ms)
And both servers are stopped (0.00ms)

🔴 Owner declines a join request

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3519.97ms)
And the user 1 is using client 1 (0.22ms)
And the user creates a new account on "staging" (1483.00ms)
And the account is synced within 60 seconds (62023.10ms)
Given the user creates an object 1 in the account (0.00ms)
And the user can open the object 1 (0.00ms)
And the user has shared his space and generated an invite link (0.00ms)
And the account is synced within 60 seconds (0.00ms)
And the server "default" 2 is running (0.00ms)
And the user 2 is using client 2 (0.00ms)
And the user creates a new account on "staging" (0.00ms)
And the user sends requests to join the space (0.00ms)
When the user 1 declines the join request of user 2 (0.00ms)
And the user 2 is using client 2 (0.00ms)
Then the user can't open the object 1 (0.00ms)
And both accounts are deleted (0.00ms)
And both servers are stopped (0.00ms)

🔴 Owner declines a join request (Will be retried 🔄)

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3402.90ms)
And the user 1 is using client 1 (0.20ms)
And the user creates a new account on "staging" (1446.64ms)
And the account is synced within 60 seconds (62084.02ms)
Given the user creates an object 1 in the account (0.00ms)
And the user can open the object 1 (0.00ms)
And the user has shared his space and generated an invite link (0.00ms)
And the account is synced within 60 seconds (0.00ms)
And the server "default" 2 is running (0.00ms)
And the user 2 is using client 2 (0.00ms)
And the user creates a new account on "staging" (0.00ms)
And the user sends requests to join the space (0.00ms)
When the user 1 declines the join request of user 2 (0.00ms)
And the user 2 is using client 2 (0.00ms)
Then the user can't open the object 1 (0.00ms)
And both accounts are deleted (0.00ms)
And both servers are stopped (0.00ms)

🔴 Owner removes a participant from the space

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3441.24ms)
And the user 1 is using client 1 (0.24ms)
And the user creates a new account on "staging" (1452.29ms)
And the account is synced within 60 seconds (62094.45ms)
Given the user creates an object 1 in the account (0.00ms)
And the user can open the object 1 (0.00ms)
And the user has shared his space and generated an invite link (0.00ms)
And the account is synced within 60 seconds (0.00ms)
And the server "default" 2 is running (0.00ms)
And the user 2 is using client 2 (0.00ms)
And the user creates a new account on "staging" (0.00ms)
And the user sends requests to join the space (0.00ms)
When the user 1 approves the join request of user 2 with "Editor" rights (0.00ms)
When the user 1 removes the user 2 from the space (0.00ms)
And the user 2 is using client 2 (0.00ms)
Then the user can't open the object 1 (0.00ms)
And both accounts are deleted (0.00ms)
And both servers are stopped (0.00ms)

🔴 Owner removes a participant from the space (Will be retried 🔄)

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3506.96ms)
And the user 1 is using client 1 (0.22ms)
And the user creates a new account on "staging" (1456.20ms)
And the account is synced within 60 seconds (62113.75ms)
Given the user creates an object 1 in the account (0.00ms)
And the user can open the object 1 (0.00ms)
And the user has shared his space and generated an invite link (0.00ms)
And the account is synced within 60 seconds (0.00ms)
And the server "default" 2 is running (0.00ms)
And the user 2 is using client 2 (0.00ms)
And the user creates a new account on "staging" (0.00ms)
And the user sends requests to join the space (0.00ms)
When the user 1 approves the join request of user 2 with "Editor" rights (0.00ms)
When the user 1 removes the user 2 from the space (0.00ms)
And the user 2 is using client 2 (0.00ms)
Then the user can't open the object 1 (0.00ms)
And both accounts are deleted (0.00ms)
And both servers are stopped (0.00ms)

🔴 Sync on staging nodes

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3438.97ms)
And the user is using client 1 (0.27ms)
And the user creates a new account on "staging" (1432.73ms)
And the user creates an object 1 in the account (7.32ms)
And the user can open the object 1 (10006.07ms)
And the account is synced within 80 seconds (82093.83ms)
And the server 1 is stopped (0.00ms)
And data is deleted (0.00ms)
And the server "default" 2 is running (0.00ms)
And the user is using client 2 (0.00ms)
When the user logs in to their account on "staging" (0.00ms)
Then the account should have an analyticsId, profile picture and name (0.00ms)
Then the user can open the object 1 (0.00ms)
And the account is deleted (0.00ms)
And the server 2 is stopped (0.00ms)

🔴 Sync on staging nodes (Will be retried 🔄)

Error: Test failed: The account did not sync within the expected time. Stack trace: Error: Timeout: Condition not met within the specified time. at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at Timeout. (/home/runner/work/anytype-heart/anytype-heart/support/api/services/utils.ts:231:11) at listOnTimeout (node:internal/timers:594:17) at processTimers (node:internal/timers:529:7) at World. (/home/runner/work/anytype-heart/anytype-heart/step_definitions/api/accountSteps.ts:233:13)

################[ Steps ]################
Given the server "default" 1 is running (3419.85ms)
And the user is using client 1 (0.25ms)
And the user creates a new account on "staging" (1428.94ms)
And the user creates an object 1 in the account (8.02ms)
And the user can open the object 1 (10004.90ms)
And the account is synced within 80 seconds (82111.21ms)
And the server 1 is stopped (0.00ms)
And data is deleted (0.00ms)
And the server "default" 2 is running (0.00ms)
And the user is using client 2 (0.00ms)
When the user logs in to their account on "staging" (0.00ms)
Then the account should have an analyticsId, profile picture and name (0.00ms)
Then the user can open the object 1 (0.00ms)
And the account is deleted (0.00ms)
And the server 2 is stopped (0.00ms)

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

Successfully merging this pull request may close these issues.

1 participant