forgejo/models/fixtures/action.yml
singuliere b536b65189
GetFeeds must always discard actions with dangling repo_id (#19598)
* GetFeeds must always discard actions with dangling repo_id

See https://discourse.gitea.io/t/blank-page-after-login/5051/12
for a panic in 1.16.6.

* add comment to explain the dangling ID in the fixture

* loadRepoOwner must not attempt to use a nil action.Repo

* make fmt

Co-authored-by: Loïc Dachary <loic@dachary.org>
2022-05-05 11:39:26 -04:00

67 lines
1.1 KiB
YAML

-
id: 1
user_id: 2
op_type: 12 # close issue
act_user_id: 2
repo_id: 2 # private
is_private: true
created_unix: 1603228283
-
id: 2
user_id: 3
op_type: 2 # rename repo
act_user_id: 2
repo_id: 3 # private
is_private: true
content: oldRepoName
-
id: 3
user_id: 11
op_type: 1 # create repo
act_user_id: 11
repo_id: 9 # public
is_private: false
-
id: 4
user_id: 16
op_type: 12 # close issue
act_user_id: 16
repo_id: 22 # private
is_private: true
created_unix: 1603267920
- id: 5
user_id: 10
op_type: 1 # create repo
act_user_id: 10
repo_id: 6 # private
is_private: true
created_unix: 1603010100
- id: 6
user_id: 10
op_type: 1 # create repo
act_user_id: 10
repo_id: 7 # private
is_private: true
created_unix: 1603011300
- id: 7
user_id: 10
op_type: 1 # create repo
act_user_id: 10
repo_id: 8 # public
is_private: false
created_unix: 1603011540 # grouped with id:7
- id: 8
user_id: 1
op_type: 12 # close issue
act_user_id: 1
repo_id: 1700 # dangling intentional
is_private: false
created_unix: 1603011541