Wrong davis version on diagnostics page
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start by tracing the /dashboard/diagnostics page to find where it reads and displays the Davis version, then check how the Docker image supplies that version. Reproduce with the v5.6.2 image and compare the displayed value with the image version; done means the diagnostics page reports the correct Davis version.
Written by the indexing model from the issue text.
Description
Davis version
v5.6.2
Installation method
Docker – (Davis + MariaDB + nginx)
PHP version (bare metal only)
No response
Database
MariaDB
Reverse proxy
Nginx
Authentication method
Internal (ADMIN_LOGIN / ADMIN_PASSWORD)
Affected protocol(s)
- CalDAV
- CardDAV
- WebDAV
- Admin dashboard
- API
Client(s) exhibiting the issue
I think diagnostics page sows wrong davis version. Running latest davis docker image for v5.6.2 the diagnostics page still shows version 5.5.0
Relevant environment variables
APP_ENV=prod
...
Steps to reproduce
Open /dashboard/diagnostics of your davis instance
Expected behaviour
Diagnostics page should show correct versions of davis etc.
Actual behaviour
wrong software version
Logs
Additional context
Running davis together with nginx reverse proxy, I also cleared nginx www cache, but diagnostics page still shows wrong davis version.
- Dominant language
- PHP
- Stars
- 760
- Forks
- 45
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tchapi/davis
-
Run Doctrine migrations automatically on container startPossibly taken A pull request linked to this issue is open or already merged. Openfeature request
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Add an updaterOpenfeature request
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 45/100
Similar issues
-
bug webbackend
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
DOMjudge/domjudge#3886 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
opensourcepos/opensourcepos#4794 ·
Maintainers usually reply within 1 day
-
repo:cms
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
craftcms/cms#20235 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
REST API: decimal ids like 1.5 give 500 on folder and report endpointsPossibly taken @console-log-life claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 3 days