done, and released as swh-vault v1.0.0 :)
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 27 2021
Aug 26 2021
Aug 23 2021
Aug 2 2021
Jul 29 2021
Jun 29 2021
Deployed v0.6.4.
status:
- unstable build is fine.
- stable build failed [1] [2]
The build is still breaking in a different way [1]
Debian build is broken [1], currently investigating to reproduce/fix it.
Jun 28 2021
Debian build is broken [1], currently investigating to reproduce/fix it.
May 11 2021
May 10 2021
May 4 2021
I'm going to close this, because we decided to use a different approach for the git bare cooker.
Apr 30 2021
Apr 29 2021
Apr 27 2021
Apr 16 2021
Apr 8 2021
So either the vault is fine and the test needs to be improved.
Or the vault builds the tarball without taking into account the symlink case.
Apr 2 2021
Mar 29 2021
Mar 9 2021
Mar 8 2021
Feb 18 2021
Thanks @anlambert, the monitoring comes back to green
Feb 17 2021
@anlambert agrees with the previous hypothesis ^ and is working on a fix
With tcpdump, it seems swh-web don't add the headers to don't cache the response in case of a 404:
GET /api/1/vault/directory/a317baff051f68e83557d51e59539dac2ff55b34/ HTTP/1.1 Host: archive.softwareheritage.org User-Agent: python-requests/2.21.0 Accept: */* X-Forwarded-For: 128.93.166.14 X-Forwarded-Proto: https Accept-Encoding: gzip X-Varnish: 230399
after digging, it seems the request with a 404 return code are cached by varnish.
When the test is launched, a first request is done which returns a 404 and the post is issued. When the check try to get the status of the cooking, the initial 404 is returned by varnish
It seems the scheduler has missed some updates. After an upgrade of the python3-swh-.* packages, the error is again the initial one.
After an upgrade of the packages on pergamon and vangogh, the error is now :
Feb 17 10:49:38 vangogh python3[1990225]: 2021-02-17 10:49:38 [1990225] root:ERROR <RemoteException 500 InvalidDatetimeFormat: ['invalid input syntax for type timestamp with time zone: "Timestamp(seconds=1613558977, nanoseconds=999614000)"\nCONTEXT: COPY tmp_task, line 1, column next_run: "Timestamp(seconds=1613558977, nanoseconds=999614000)"\n']> Traceback (most recent call last): File "/usr/lib/python3/dist-packages/swh/core/api/asynchronous.py", line 71, in middleware_handler return await handler(request) File "/usr/lib/python3/dist-packages/swh/core/api/asynchronous.py", line 178, in decorated_meth result = obj_meth(**kw) File "/usr/lib/python3/dist-packages/swh/core/db/common.py", line 62, in _meth return meth(self, *args, db=db, cur=cur, **kwargs) File "/usr/lib/python3/dist-packages/swh/vault/backend.py", line 220, in cook self.create_task(obj_type, obj_id, sticky) File "/usr/lib/python3/dist-packages/swh/core/db/common.py", line 62, in _meth return meth(self, *args, db=db, cur=cur, **kwargs) File "/usr/lib/python3/dist-packages/swh/vault/backend.py", line 163, in create_task task_id = self._send_task(obj_type, hex_id) File "/usr/lib/python3/dist-packages/swh/vault/backend.py", line 139, in _send_task added_tasks = self.scheduler.create_tasks([task]) File "/usr/lib/python3/dist-packages/swh/core/api/__init__.py", line 181, in meth_ return self.post(meth._endpoint_path, post_data) File "/usr/lib/python3/dist-packages/swh/core/api/__init__.py", line 278, in post return self._decode_response(response) File "/usr/lib/python3/dist-packages/swh/core/api/__init__.py", line 354, in _decode_response self.raise_for_status(response) File "/usr/lib/python3/dist-packages/swh/core/api/__init__.py", line 344, in raise_for_status raise exception from None swh.core.api.RemoteException: <RemoteException 500 InvalidDatetimeFormat: ['invalid input syntax for type timestamp with time zone: "Timestamp(seconds=1613558977, nanoseconds=999614000)"\nCONTEXT: COPY tmp_task, line 1, column next_run: "Timestamp(seconds=1613558977, nanoseconds=999614000)"\n']>
Feb 3 2021
Jan 25 2021
Deployed configuration change in staging without issues.
Deployed configuration change in produciton as well.
Rebase
Jan 4 2021
Dec 21 2020
Dec 15 2020
Yes, i think it's just the pattern the webapp uses.