[QA] Quota fields with parse errors should not be used
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 17
- Forks
- 19
- Avg merge
- 11h 40m
- Merged PRs (30d)
- 2
Description
Seen in user_ldap 0.15.3-rc1 with core 10.8.0-beta1
In ldap, I specified 12x5 B as a user's quota value. This is a broken syntax. but it is accepted into ownCloud
Expected behaviour: It should be rejected. Fallback to ldap default quota or fallback to owncloud default quota.
Contributor guide
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.
Research direction
Start by reproducing the reported LDAP quota input 12x5 B and trace where the quota value is parsed and accepted. Done means parse errors are rejected and the quota falls back to the LDAP default or the ownCloud default, as described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100