- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 6 2021
Build has FAILED
Postfix the type aliases with "T"
Build is green
Build is green
Rebase
Refactor test detection in a function
Actions performed:
- wwn-0x5000c500d5de652a(sdb) : new -> spare
- wwn-0x5000c500a22eed6f(sdh) : spare -> mirror
- wwn-0x5000c500d5dda886(sdc) : new -> mirror
The checks ran without detecting any bad block on the disk.
They can be added on the zfs pool again.
Build is green
Thanks adapted.
Adapt according to last suggestions
May 5 2021
Abandoned in favor of D5687
LGTM
(tests failures are unrelated)
Build is green
Fix migrations
Build is green
Build is green
changelog for the 21.1.5 version
Good day everyone,
- Add the last test!
- reword commit message
Update: Adapt according to reviews
Build is green
Build has FAILED
first diff, achievement unlocked, w00t ;)
is stupid one though :)
Can't the CSS refer to custom-control input and custom-control label instead of custom-control-input and custom-control-label?
- Add missing tests (there remains one to uncomment and make green)
- Adapt according to suggestions
In D5686#144406, @ardumont wrote:first diff, achievement unlocked, w00t ;)
first diff, achievement unlocked, w00t ;)
ack on what you said, thanks.
Proper solution would be to store a list of user ids in the save request model using a django ArrayField.
In D5673#144347, @vlorentz wrote:I'm done now.
Last comment: when someone creates a Save request and it remains in status "not yet scheduled", and a logged in user clicks "Save again", it does not appear when this user selects "show only your requests".
I did not try with other statuses, though.Is it on purpose?
I'm done now.
No API endpoint for this feature?
(I did not finish reviewing, but I'm marking this as "request changes" now so you don't merge it immediately)
lgtm, a couple of question/suggestion and one spurious print to drop inline ;)
rebase
And I think that I found how to fix the last remaining warning cited above.
good news ;)
thanks
And I think that I found how to fix the last remaining warning cited above.
completely remove the -e option