Migration does not migrate attachments of issues on a given Gitea instance

[Benjamin-Loison]

Description

To migrate a Gitea repository from https://gitea.lemnoslife.com with Issues need on https://gitea.lemnoslife.com/user/settings/applications Select permissions repository and issue Read.

However, as the target issue:

-----BEGIN PGP MESSAGE-----

hF4DTQa9Wom5MBgSAQdAgCtPFcBBvNjWZeO1ThYoNk50f/Uyau3Am482znzMx3kw
Arz0IO+trzf6KneZoIy88aFrJ33YqSppD7fkspxuAJlZ9uUsgQG8bg129fB4XnHd
0pQBA5kTNrFh1UpYgJ1p2GnkyiMxXmVFVTxQIcuqn2XpjnhlIgRWIqioilvUPQYG
wq6blp7BtOTneEskf7iRVXjB7ReW4hpw7PP39q3tCXKwdjvycgEjuVEStD4qKYcH
yMI8kX2sxUsu+gakHZjGi40kl9zCsJ0pPXIbWKEyHvC/TWs4yYVt31qeEUoMjY2X
VXWBfVVT
=fvvL
-----END PGP MESSAGE-----

shows, the attachments are not imported, while they are important to me, in comparison the initial issue: https://gitea.lemnoslife.com/Benjamin_Loison/Repository_with_an_issue_attachment/issues/1

The attachment URL:

-----BEGIN PGP MESSAGE-----

hF4DTQa9Wom5MBgSAQdAruKBjTwJtyIzPUtF3lQXWqa7iG1f2JJQynN3qtXVT2ww
Fxr/OlfLQg+5pn3rbPD5pnRLEOfgOsA6Ymgb2rempvT/3FaYChZdyCfteSP8HaIj
0rIB+XutUAbivPAQ/sLG6Kqw1sn3gHhkYBKn9Fsx7zq2l3UtwdLTY2FeQUU6FjWp
2a5HJYoYbkgC5sXBZU31cWRtI091JcJDnSH/ZCYHGTfMVFqN0W35Ru98wDYFikwj
V1ZtAncpdKQB0Q51VPAUcu/CLIQcaFK3Fo8xcPaC6s7To+0A2U40IQGi2n0OXJzm
tuVJNc1VV7z+X5NOmnEGHOsoVKuojpxJ3Xyz08NLTWZKRc6V
=/t/s
-----END PGP MESSAGE-----

returns Not Found

Maybe due to URL /git/ introduction, related to Benjamin_Loison/nginx/issues/5.

Creating a repository directly on the target instance make attachment upload and rendering fine in an issue.
Migrating from the target instance itself does not have the issue. It is because the attachment id already works fine, it keeps the issue comment as it is but not specify the attachments, so works fine.

Gitea Version

Not read.

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Not read.

Database

None

[Benjamin-Loison]

I sent a message to the Gitea instance owner:

-----BEGIN PGP MESSAGE-----

hF4DTQa9Wom5MBgSAQdAjNChhMDSUUgvDtXwjb6mh+XppZ9A2kNDEDpbs+zIFWww
2Clejc/XBpLwwbbrD+uJftTqKcmujImIU3NtDeckMvh5jzEQFKx1UtLhjDgPO1mE
0qoB5SSf3j7bhVKIfVnQDq1e8iKftTw9PwLxUDjOhtnAL/3D14XFojkWPLml7ybW
hQTfuHs/6usBHo2hjiHUZxdPTHtK2lUMOXjXjQHiujxdGaDlDLWCwe3/9NEeTVGi
J/0e+1hiwxfj4iIlL5TleS7E3RtXCEu0BN4EQ6eOZ5N7Ii6nol8tSzJjmsu7cRYK
XDc22EoJNM19nOJJxRhGTN2wUF9w7YbipLlpIg==
=dy7Z
-----END PGP MESSAGE-----

[Benjamin-Loison]

The setup is made of a nginx redirecting to an Apache. I compared the BookStack nginx configuration with my /etc/nginx/sites-enabled/gitea and it was looking correct.

This setup may be available at:

-----BEGIN PGP MESSAGE-----

hF4DTQa9Wom5MBgSAQdAnYSwt1yOdSSxKaXWKaOK0+xbPWdX6+FvMfT45wIMPFcw
ipUXYzHSCwiLiwUctfnhCetiZXKBoJzwYNWlGMA+RyHk/41kQICq+HwDNuGZeeNn
0nABZKXmVn0BOzd90q3f7fFFnXyfVoBkw4buZRkrIgarw2Wkq1UndoOIdofKGULs
srvWEJ5PgvtulDPkeZ+eceiPhnmtazXXo+ZTUitflDYeuMmN3BngC8hyQBYzozIX
vqsFvVAy4shcuu1sfewoB5PI
=I5bl
-----END PGP MESSAGE-----

The Stack Overflow answer 25755343 helps with a2enmod/ln -s/ls /etc/apache/mods-{available,enabled}/ getting at Apache level the provided headers and they seem correct. So they seem correctly passed through nginx. The Stack Overflow answer 25714765 is an alternative in PHP as BookStack is PHP made (see BookStack) but may mean to temporarily stop it.

Related to Benjamin_Loison/BookStack/issues/22.

[Benjamin-Loison]

It is not an issue of domain name gitea.lemnoslife.com being blocked like on Eduroam, see Improve_websites_thanks_to_open_source/issues/494, as the issue presence and body is transmitted.

[Benjamin-Loison]

Same issue when migrate a repository with an issue attachment from the given Gitea instance to mine.

[Benjamin-Loison]

find in the Gitea docker does not find any svg or file name mentioning the hash file name c1dd2c05-6be7-41a9-b0b5-2a87b5b5fb4a.

However on OverClock3000:

find /var/lib/gitea/ -name 'c1dd2c05-6be7-41a9-b0b5-2a87b5b5fb4a'

/var/lib/gitea/data/attachments/c/1/c1dd2c05-6be7-41a9-b0b5-2a87b5b5fb4a

Both URLs to the issue attachment:

-----BEGIN PGP MESSAGE-----

hF4DTQa9Wom5MBgSAQdAMLYCglcmW+3tqhBmiljFEZ29TgyMTwheTbIvNs8nkxQw
oIA/K2MGFrYCYdmdeu1UAsc4vvBaK3CHvulxMema6Ujp6YA6KuL+GEKm/5dqn5jA
0sAHAcTSTKupR5PtyFidlJ2VukOVNneIUVz0SmlSLAgfvK0tK2niJ32wtfb0pVdn
KpGWZGDU5/3pUfRsFwvmhdZ0sCvEPOSWjsgQiu/Zs4mxKFboc4SZDpx+jBhQUwfZ
dS+B63+Aaof4CZPHys6GpEs+QKlHEoMkjMZ2abtpckRHgKXe4tuYkHUaX2lfEMt0
e6QV6QqXd210az+7xKHb6OOdu7fy+v/T8z2uD6VdkTmAKXhrqSODCKBZYll2U/Wp
V2vaQkrc6osE9A==
=GOT7
-----END PGP MESSAGE-----

look correct, note that the file name is identical, either because it is enforced during the migration or because it is a hash of the file content.

[Benjamin-Loison]

Investigating migration source code may help but is maybe not the most time efficient.

[Benjamin-Loison]

Maybe I had to some extent this issue on my Gitea instance:

-----BEGIN PGP MESSAGE-----

hF4DTQa9Wom5MBgSAQdAT6ff7s8CeWkZ6V2+mkyfojBA2gXwdHadlfLA12BFiUow
VIYwmssBCYwam3ywSzntrDmHNJkoQ+wdxBa7AVJ2JFWqs5Dpwd0PhjDZQ54dnuRN
0sAAAZ4nnXlnvpH84/MYttaX8n9s8lTuQLSvGFfHFsqxrtv/GCzbo++NokoNxW0q
QNSvGDPJ7T+YJGK8Hn1cW5jH5rb3AfbnIFQNksE6er1e81OR/6rsY0fTIEP09z7y
IWHzMxuZYi6suzuDMMNQlDg1vNDUXyMvJ60zxra9iTjbHAqajg1r+mQv/56WyhEO
bVf6mHKt37o29cAE7YWuNVbwr4SWYqc1Tzx1GQsnHl/o0ddreHfC57e9FlRZzOUW
QvNW
=Vnmw
-----END PGP MESSAGE-----

Tracked at:

-----BEGIN PGP MESSAGE-----

hF4DTQa9Wom5MBgSAQdAxlIFHl5SjzuqV6QSIBj0qg95+f9c6h4+BNg+G6gXvRww
zzQs9ckUDyFw/MIofJF0s42TGPK+AncHRXh9FZ+1ICXnOH6elhLELKc1795oAEZu
0qABK6St+VNifc/UaGAlPD66xgsExF7VPTzEV25JY7CFJaPABOBEWDQreZkXjOz3
BJN4xEfDmEYNqBK/mRyKkve0oSGnawB9mfJTaWJg12fA034TURS5wOrjBJ1GZPUS
+fP09lVMghkQcymbDiAImX0u79O+bYfZUcWnngH5TEEF0dsJM5IPOxwyQyACEsa9
WG9c0r8YwJ15xvXXfJBttxta
=E33E
-----END PGP MESSAGE-----

[Benjamin-Loison]

The persons:

-----BEGIN PGP MESSAGE-----

hF4DTQa9Wom5MBgSAQdAG3z+Gtx8+tVITomU0r99KK2HXT81zcf9XFaiHK9kaQQw
89jBwTElGUf5O/69QunO+Pr+mCFwzDadhVhUItWM2CXYqrBxCnZjSnZrxMtFE+ce
0kgB7SuOLi+f93qLdzRNGD/HgeXwUo2kP+SOw7POzsWELKQZrtkG+pxwSwsMW1YG
uLWInVQm1DQRPel815zxFe+WAvoxeyb0SEs=
=mc+x
-----END PGP MESSAGE-----

do not use the concerned Gitea, so do not face this issue.

[Benjamin-Loison]

Let us wait the domain name migration to .fr, see the message:

-----BEGIN PGP MESSAGE-----

hF4DTQa9Wom5MBgSAQdA83NYc7+9e71sfVw7spGPAsgSZZJf1o80eB20UOMIA3gw
U9mgPesW3P3tg2Dzi52b+Z4cy4WW5mPa40kTZExGA0URVw35Pc/Ibzr/Js97WO/k
0qoBMBARyajCWWJVr8QzHNeDvlhPsiWDq1sRKxDKbSsMoYVR+euhSiAPKy7ebMbk
hzbhVeLmXlYZFpOu/FqrOPxzLgf0Urb6nttOcBqzoBgqnt1JufuD5iMc48QbDFyn
rQTAJBDKx+KvaEEi/iYzVHQa2+sLJwhkxaJCtPzGlLgcWKQtZFQm8npQeWQqm0IQ
iWPOvjX3CUadxxU1AuXSVWxZJrGhae5uioGdxw==
=Yna2
-----END PGP MESSAGE-----

Otherwise having Gitea instance log access (at least logs when the issue happen) or even system admin access would help solving this issue.

[Benjamin-Loison]

Same issue on Codeberg with Benjamin_Loison/Example_to_backup_attachments_of_issues/issues/1.

See the target issue:

-----BEGIN PGP MESSAGE-----

hF4DTQa9Wom5MBgSAQdAZ4UDxp6KkxD9g75cqJiY07epZsxki68/cHIMZY+urBUw
KSLZhbtXRvbpquSV0hxDde4mK6O8N5QhZlFX85VZBIpsLvxsffCdEVDc3fiPMovH
0pUBKq+RCCeB9O0u9Qq2U+KAjW0pzPMVGXEROOyavj5Do3lvit0JhcdSW53QxXCV
llsrRrDnnqP4mQKFKA9AcxDPlyaX2HQ01C8+K15N573BpzIHGZYu+wJI7jBw5Afd
XYExf9SmTkoaDzNuWRZq3037G1VjS00NO8rzfuYjJByQRvAt6rH9jc+bAIc/nPaW
uFGpgN6+SQ==
=T5Wr
-----END PGP MESSAGE-----

I confirm that migrating from the secret instance to Codeberg, leads to the same issue, see Benjamin_Loison/Repository_with_an_actual_issue_attachment/issues/1.

[Benjamin-Loison]

Should try between two Gitea instances without the secret one.

If really a pain to setup another one as https://gitea-test.lemnoslife.com on another server, then could ask the person:

-----BEGIN PGP MESSAGE-----

hF4DTQa9Wom5MBgSAQdAo06OqdFcHkr1aL7L01W1vLSdx09T3hY26EVX+Avx8HQw
C2oJA6nJVq9H0Du1+4tPAsmQRjZAlnsul0exRyy1RSD6Zoa+999B4XeOcaxKqjcw
0oEBXyrHGL/CXr7BLX5GNMDaQ0EutukYmwde+LMdkawE8WGLk5Rlprc7NTiVHDCY
jsEKMLdVwB0PtLpzVqv1zO52zm+3vO2AQKB+MluTk7EEP4KSIxZw/LD5rJwMwHFw
IKdCPssQxXsPIvcQhmwJBCf812TjxVdacoEZjfzrAl1NLdw=
=yq8l
-----END PGP MESSAGE-----

[Benjamin-Loison]

After the migration I still notice the issue, see the message:

-----BEGIN PGP MESSAGE-----

hF4DTQa9Wom5MBgSAQdAfSFc3F3I7h/3GfR4IMrqsvm2hWpTtEB7Wb/DaApn1z0w
WwxI7Le1diDSZzMzHUzEjM/gmNqU7E52ZDmbybuK1Ulixlw62xb7viHgxf8IjFKH
0qoBNUZRuPwl5ihpk/9RSYOAhphpL9z00Dntnxou9Y2zNIXXWgGW9+2/NLAegLR7
UQh+6NJrMdjoMZkJytI1w2PIlp+k93vmLQRbfxEKJEZ56mYI0E+FHH/ZEI1DrAuk
6OCQHNs0xa5ir2X9EgpPcFMo8dj+xzMoQFUWIF0ciDgZ+TpEeCbIZd7tpNC91lE8
pCaAHU3vZVJ1/MefvIBS0z5WDkYG5YzKamuQdQ==
=Rffb
-----END PGP MESSAGE-----