389-devel May 2018

389-devel@lists.fedoraproject.org

6 participants
30 discussions

Start a nNew thread

389 DS nightly 2018-05-31 - 60% PASS
by vashirov＠redhat.com 31 May '18

31 May '18

https://fedorapeople.org/groups/389ds/ci/nightly/2018/05/31/report-389-ds-b…

1 0

please review: Ticket 49732 - Optimize resource limit checking for rootdn issued searches
by Mark Reynolds 30 May '18

30 May '18

https://pagure.io/389-ds-base/pull-request/49733

1 0

389 DS nightly 2018-05-30 - 100% PASS
by vashirov＠redhat.com 29 May '18

29 May '18

https://fedorapeople.org/groups/389ds/ci/nightly/2018/05/30/report-389-ds-b…

1 0

please review: Ticket 49683 - Add JSON option for lib389 CLI tools
by Mark Reynolds 29 May '18

29 May '18

https://pagure.io/389-ds-base/issue/49683 https://pagure.io/389-ds-base/pull-request/49699

1 1

Reminder: please review: Ticket 49675 - latest coverity fixes
by Mark Reynolds 29 May '18

29 May '18

https://pagure.io/389-ds-base/issue/49675

1 1

389 DS nightly 2018-05-29 - 59% PASS
by vashirov＠redhat.com 29 May '18

29 May '18

https://fedorapeople.org/groups/389ds/ci/nightly/2018/05/29/report-389-ds-b…

1 0

Please review: Issue 49646 - Improve TLS cert processing in lib389 CLI
by Simon Pichugin 28 May '18

28 May '18

Hi team, https://pagure.io/389-ds-base/issue/49646 https://pagure.io/389-ds-base/pull-request/49709 And the issues were fixed: https://pagure.io/389-ds-base/issue/49381 https://pagure.io/389-ds-base/pull-request/49708 Thanks, Simon

1 0

New DS CLI design
by Viktor Ashirov 25 May '18

25 May '18

Hi, I'd like to continue our discussion about feature parity with perl tools and overall user experience of the new CLI tools. Here are some projects where we can take inspiration for our own design: * bpython interpreter https://bpython-interpreter.org/screenshots.html * fish shell http://fishshell.com/docs/current/design.html * Python Prompt Toolkit https://github.com/jonathanslenders/python-prompt-toolkit (it's used to build tools like pgcli and mycli: https://github.com/dbcli) * OpenStack CLI: https://docs.openstack.org/python-openstackclient/pike/cli/commands.html https://docs.openstack.org/python-openstackclient/pike/cli/interactive.html Common theme is that all of these CLIs are primarily used in REPL mode, but they can be used in script mode as well. Here's the quote from fish shell's design page about the law of discoverability: * Everything should be tab-completable, and every tab completion should have a description. * Every syntax error and error in a built-in command should contain an error message describing what went wrong and a relevant help page. Whenever possible, errors should be flagged red by the syntax highlighter. * The help manual should be easy to read, easily available from the shell, complete and contain many examples * The language should be uniform, so that once the user understands the command/argument syntax, they will know the whole language, and be able to use tab-completion to discover new features. Please let me know what do you think. Thanks! -- Viktor

3 9

please review: Ticket 49722 - Fix "WARNING" error log messages when using entrydn in filter
by Mark Reynolds 25 May '18

25 May '18

https://pagure.io/389-ds-base/issue/49722 https://pagure.io/389-ds-base/pull-request/49723

1 0

Please review: Issue 49717 - Add conftest.py for tests
by Viktor Ashirov 24 May '18

24 May '18

https://pagure.io/389-ds-base/issue/49717 https://pagure.io/389-ds-base/pull-request/49718

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-devel May 2018