Skip to content

Commit 6b9e495

Browse files
authored
Merge pull request #657 from donny-wong/v2.8.3
V2.8.3
2 parents bd7fd2e + bf83b14 commit 6b9e495

File tree

3 files changed

+36
-1
lines changed

3 files changed

+36
-1
lines changed

Changelog.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,10 @@
11
# CHANGELOG
22
All notable changes to this project will be documented here.
33

4+
## [v2.8.3]
5+
- Add troubleshooting section talking about Docker Content Trust (DCT) (#653)
6+
- Fixed Python tester to display fully qualified name when running pytest (#656)
7+
48
## [v2.8.2]
59
- Changed tasty-discover argument of source directory to a file (#648)
610
- Disabled access to third-party models in AI tester (#649)

README.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -320,3 +320,34 @@ To see which settings *would be* deleted without actually deleting them, use the
320320

321321
Users who try to run tests after the settings have been cleaned up in this manner will see an error message telling them
322322
that the test settings have expired and prompting them to upload more.
323+
324+
## Troubleshooting
325+
326+
### Docker Content Trust (DCT)
327+
328+
Docker Content Trust (DCT) is a security feature in Docker that ensures container images are trusted using digital signatures. Docker Content Trust is disabled by default in Docker clients. If somehow it was enabled you may receive an error like the following, for example when saving a Haskell assignment automated test settings.
329+
330+
```text
331+
No information from Hackage index, updating
332+
Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
333+
Downloading root
334+
<repo>/root.json does not have enough signatures signed with the appropriate keys
335+
```
336+
337+
This was fixed after disabling the Docker Content Trust. To disable Docker Content Trust for Docker Desktop on a Mac, the most common method involves setting or unsetting an environment variable in your shell.
338+
339+
**Method 1:** Unsetting the `DOCKER_CONTENT_TRUST` environment variable
340+
341+
This method disables Content Trust for the current shell session and any new shell sessions you open afterwards. Open your terminal application (e.g., `Terminal`, `iTerm2`). Execute the following command.
342+
343+
```
344+
unset DOCKER_CONTENT_TRUST
345+
```
346+
347+
**Method 2:** Setting `DOCKER_CONTENT_TRUST` to `0`
348+
349+
This method achieves the same outcome as unsetting the variable. Open your terminal application and execute the following command.
350+
351+
```
352+
export DOCKER_CONTENT_TRUST=0
353+
```

server/autotest_server/testers/py/py_tester.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -196,7 +196,7 @@ def pytest_collectreport(self, report):
196196

197197
def _format_test_name(self, report):
198198
parts = report.nodeid.split("::")
199-
return f"[{parts[0]}] {parts[-1]}" if len(parts) > 1 else f"[{parts[0]}]"
199+
return f"[{parts[0]}] {'.'.join(parts[1:])}" if len(parts) > 1 else f"[{parts[0]}]"
200200

201201

202202
class PyTest(Test):

0 commit comments

Comments
 (0)