Hi,
I found a quite interesting tool called Overcommit [1].
It provides an easy way for setting up Git commit hooks and provides
some basic checking plugins.
The nice feature of the Git commit hooks is that you can run some checks
automatically and early in the development. For example with the commit hooks you can
run Rubocop check automatically whenever a commit is created. And if the check fails
the commit is not created.
I can see "make Rubocop happy" commits quite often (happens to me as well),
with Overcommit you can easily avoid that.
I have tried several Overcommit checks:
- Rubocop - runs Rubocop at "commit"
- Rspec - runs the tests before "push"
- Branch blacklist - can forbid direct commits to configured branches,
e.g. "master" (forces using pull requests, avoids commits to master my mistake)
- Commit message spellcheck - warns when there is a possible typo
Check my blog post [2] for the details, esp. watch the recorded screencast where
I wanted to show some mistakes which it can catch.
The tool looks promising, I'll try using it for some time. If you want to try it
as well check the blog post for the installation steps.
Enjoy!
[1] https://github.com/brigade/overcommit
[2] http://blog.ladslezak.cz/2016/06/06/overcommit/
--
Ladislav Slezák
Appliance department / YaST Developer
Lihovarská 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak(a)suse.com
SUSE
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi all,
Yesterday I published a short blog post about recording a screencast
(a desktop session) to create a video or an animated image.
So if you want to have nice animated images in READMES [1] or in pull requests [2]
then check this post [3].
Enjoy!
[1] https://github.com/lslezak/build-rake/blob/master/README.md
[2] https://github.com/yast/yast-registration/pull/240
[3] http://lslezak.blogspot.cz/2016/01/recording-screencast-in-linux.html
--
Ladislav Slezák
Appliance department / YaST Developer
Lihovarská 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak(a)suse.com
SUSE
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
...I want to make sure there is a solution that I simply have not yet found.
Expected (OK) fonts results (e.g.):
sw_single @120 DPI in KDE3 on 13.1:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesOK131kde3-120.png
sw_single @132 DPI in KF5 on TW:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesOKtwkde5-132.png
Not expected (undersized) fonts results (e.g.):
sw_single @108 DPI in TDE on 13.2:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall132tde-108.png
sw_single @120 DPI in KDE3 on 42.1:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall421kde3-120.p…
sw_single @168 DPI in KDE3 on 42.1:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall421kde3-168.p…
Clearly sw_single (and other y2 apps) post-13.1 (except in KF5) is using
smaller fonts than those used in the y2 control center and in the rest of DE
UI, as if both the non-KF5 DE's font settings and QT's font setting in
Trolltech.conf are being disregarded.
Is there something that can be installed or removed to bring up font sizes to
match the rest of the DE and y2cc in KDE3 and TDE without loading the
installation with QT5 and/or KF5, or even with QT5 and/or KF5? Or, is this a
bug that's already been filed, or one that needs filing?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi all,
Ruby 2.1+ allows tracing object allocations, see more details in this article [1].
I enabled it and dumped the Ruby memory usage data in a SLES12-SP2 Beta3 installation.
It is related to this Trello card [2] and this bug [3].
You can find more details and the dump in my Gist [4], here is a copy of the most
interesting part:
## The Result
A quick scan found out that the place which consumes most memory is
/usr/share/YaST2/lib/installation/ssh_config_file.rb:45:STRING: count: 4,
total size: 274056
which loads the SSH keys and configuration from the previous installation and needs
about 270kB memory.
The question is we can optimize it better, the SSH keys actually need to be stored
somewhere as the target partition will be reformatted...
The only optimization could be probably possible when the user selects to not copy
the keys. In that case we could drop the loaded keys when the installation starts.
But that's not the default so this improvement would actually help only in some cases...
## TODO
You can collect a different statistics from the data, e.g. the place which creates
the most objects, which methods, check the object "age" (the GC generation value), etc...
[1] http://tmm1.net/ruby21-objspace/
[2] https://trello.com/c/QJ2PHxjs
[3] https://bugzilla.suse.com/show_bug.cgi?id=974601
[4] https://gist.github.com/lslezak/6b99026b7ea9e163cdfd5a6d6d0aca6c
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Here you are another opportunity to lurk into YaST development
https://lizards.opensuse.org/?p=11893
Get it while it's hot!
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org