Michal Čihař - Archive for Jan. 1, 2017

First week in 2017 has been quite busy. There was usual amount of bug screening and fixing on phpMyAdmin, but I've attended other parts of the project as well.

The Docker container got big upgrade to Alpine 3.5 and PHP 7, so it will perform better thanks to performance improvements in PHP 7. Thanks to additional cleanups the image also got 3 MB smaller.

On the libraries side we've started using php-cs-fixer for code cleanup. It all started with pull request for SQL parser, but I've quickly added it to all libraries making the code consistent (this still doesn't apply to phpMyAdmin itself as it has historical mess with own coding style). While visiting SQL parser it got also bunch of fixes which were released as 3.4.16.

Handled issues:

• #12398 Remove file_echo.php
• #12830 PMA_URL_getCommon() undefined
• #12822 #1193 - Unknown system variable 'lc_messages' On Login
• #12850 Sql Format Not Work Return False
• #12868 INSERT INTO .(username, usergroup) VALUES ('spiele', '') after fix eeb016b
• #12872 Drop index; message formating issues
• #10954 signon auth with use_trans_sid results in damaged json
• #12336 Verify checksum after uploading
• #12867 Changed the SQL window suggestion tool to have DELETE...WHERE 0 inste…
• #12818 Copying database with view alters view syntax
• #12857 added required checking if constant PHPMYADMIN is defined
• #12866 Added margins to add_col_div in libraries/central_columns.lib.php
• #12849 Create Temp
• #12853 Fix incorrect comma in message string
• #12855 Fix some Selenium tests
• #12799 Added SignonCookieParams parameter
• #12293 MySQL SSL issues
• #104 docker question
• #102 Upgrade to Alpine 3.5
• #34 Any reason not to update this to use PHP 7?
• #103 Trouble with "Usage with docker-compose and arbitrary server"
• #121 Fix indentation on html format
• #117 Some clean, remove useless brackets
• #119 Make the vendor package smaller
• #118 composer autoload-dev
• #116 String operators not recognized
• #115 What is the function named __
• #114 Apply php-cs-fixer
• #109 The value should not be altered
• #110 Empty lines if formatting in text style (the default)
• #111 Handling merging formats arrays

Today Gammu 1.38.1 has been released. This is bugfix release fixing several minor bugs which were discovered in 1.38.0.

The Windows binaries will be available shortly. These are built using AppVeyor and will help bring Windows users back to latest versions.

Full list of changes and new features can be found on Gammu 1.38.1 release page.

Would you like to see more features in Gammu? You an support further Gammu development at Bountysource salt or by direct donation.

Weblate probably would not exist (or at least would be much harder to manage) without several services that help us to develop, improve and fix bugs in our code base.

Over the time the development world has become very relying on cloud services. As every change this has both sides - you don't have to run the service, but you also don't have control on the service. Personally I'd prefer to use more free software services, on the other side I really love this comfort and I'm lazy to setup things which I can get for free.

The list was written down mostly for showing up how we work and the services are not listed in any particular order. All of the services provide free offerings for free software projects or for limited usage.

GitHub

I guess there is not much to say here, it has become standard place to develop software - it has Git repositories, issue tracker, pull requests and several other features.

Travis CI

Running tests on every commit is something what will make you feel confident that you didn't break anything. Of course you still need to write the tests, but having them run automatically is really great help. Especially great for automatically checking pull requests.

AppVeyor

Continuous integration on Windows - it's still widely used platform with it's quirks, so it's really good idea to test there as well. With AppVeyor you can do that and it works pretty nicely.

Codecov

When running tests it's good to know how much of your code is covered by them. Codecov is one of the best interfaces I've seen for this. They are also able to merge coverage reports from multiple builds and platforms (for example for wlc we have combined coverage for Linux, OSX and Windows coming from Travis CI and AppVeyor builds).

SauceLabs

Unit testing is good, but the frontend testing in browser is also important. We run Selenium tests in several browsers in SauceLabs to verify that we haven't screwed up something from the user interface.

Read the Docs

Documentation is necessary for every project and having it built automatically is nice bonus.

Landscape

Doing code analysis is a way to avoid some problems which are not spot during testing. These can be code paths not covered by test or simply coding style issues. There are several such services, but Landscape is my favorite one right now.