With Github, you can now pin a repository to the top of the page (up to 6).
Since we have some repositories that aren't really of much interest to the
public, I've pinned these:
* phpmyadmin
* docker
* themes
* sql-parser
* motranslator
* shapefile
You can check it out on the project page at https://github.com/phpmyadmin
and let me know if you have any suggestions for change.
See <https://ci.phpmyadmin.net/job/phpMyAdmin/1924/changes>
Changes:
[Michal ÄŒihaÅ™] Refuse to work with mbstring.func_overload enabled
[devenbansod.bits] Fix order of testing DBConnection with different parameters in Config
[devenbansod.bits] Add tests
[devenbansod.bits] Use IDENTIFIED BY 'auth_string' if password check plugin is active
[weblate] Translated using Weblate (Korean)
[weblate] Translated using Weblate (Indonesian)
[devenbansod.bits] Check if the function actually has arguments or not
[devenbansod.bits] ChangeLog for #12639
[weblate] Translated using Weblate (Indonesian)
[Michal ÄŒihaÅ™] Use 7.1.0RC3 for tests
[weblate] Translated using Weblate (Korean)
[weblate] Translated using Weblate (Korean)
[Michal ÄŒihaÅ™] ChangeLog entry for #12632
[Michal ÄŒihaÅ™] ChangeLog entry for #12472
[Michal ÄŒihaÅ™] Remove the nopasswd setting
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building in workspace <https://ci.phpmyadmin.net/job/phpMyAdmin/ws/>
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://github.com/phpmyadmin/phpmyadmin.git # timeout=10
Fetching upstream changes from https://github.com/phpmyadmin/phpmyadmin.git
> git --version # timeout=10
> git -c core.askpass=true fetch --tags --progress https://github.com/phpmyadmin/phpmyadmin.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 1aee86a4fe40ac88e682b4792b4c67e9c5bcdce2 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 1aee86a4fe40ac88e682b4792b4c67e9c5bcdce2
> git rev-list 04408b1f52165f6253db14b9401a19f7cfcebf87 # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[EnvInject] - Injecting as environment variables the properties content
TESTSUITE_SERVER=localhost
TESTSUITE_USER=pmatest
TESTSUITE_DATABASE=pmatest
TESTSUITE_URL=http://ci-live.phpmyadmin.net/phpMyAdmin/workspace/
XTESTSUITE_BROWSERSTACK_USER=michaliha
[EnvInject] - Variables injected successfully.
[workspace] $ /bin/sh -xe /tmp/hudson6412500550007644295.sh
+ composer update --no-interaction
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- The requested PHP extension ext-mbstring * is missing from your system. Install or enable PHP's mbstring extension.
Problem 2
- The requested PHP extension ext-xml * is missing from your system. Install or enable PHP's xml extension.
Problem 3
- satooshi/php-coveralls v0.7.1 requires ext-simplexml * -> the requested PHP extension simplexml is missing from your system.
- satooshi/php-coveralls v0.7.0 requires ext-simplexml * -> the requested PHP extension simplexml is missing from your system.
- satooshi/php-coveralls v0.6.1 requires ext-simplexml * -> the requested PHP extension simplexml is missing from your system.
- satooshi/php-coveralls v0.6.0 requires ext-simplexml * -> the requested PHP extension simplexml is missing from your system.
- satooshi/php-coveralls v0.7.1 requires ext-simplexml * -> the requested PHP extension simplexml is missing from your system.
- Installation request for satooshi/php-coveralls ~0.6 -> satisfiable by satooshi/php-coveralls[v0.6.0, v0.6.1, v0.7.0, v0.7.1].
To enable extensions, verify that they are enabled in those .ini files:
- /etc/php/7.0/cli/php.ini
- /etc/php/7.0/cli/conf.d/10-mysqlnd.ini
- /etc/php/7.0/cli/conf.d/10-opcache.ini
- /etc/php/7.0/cli/conf.d/10-pdo.ini
- /etc/php/7.0/cli/conf.d/20-calendar.ini
- /etc/php/7.0/cli/conf.d/20-ctype.ini
- /etc/php/7.0/cli/conf.d/20-curl.ini
- /etc/php/7.0/cli/conf.d/20-exif.ini
- /etc/php/7.0/cli/conf.d/20-fileinfo.ini
- /etc/php/7.0/cli/conf.d/20-ftp.ini
- /etc/php/7.0/cli/conf.d/20-gd.ini
- /etc/php/7.0/cli/conf.d/20-gettext.ini
- /etc/php/7.0/cli/conf.d/20-iconv.ini
- /etc/php/7.0/cli/conf.d/20-intl.ini
- /etc/php/7.0/cli/conf.d/20-json.ini
- /etc/php/7.0/cli/conf.d/20-mcrypt.ini
- /etc/php/7.0/cli/conf.d/20-mysqli.ini
- /etc/php/7.0/cli/conf.d/20-pdo_mysql.ini
- /etc/php/7.0/cli/conf.d/20-phar.ini
- /etc/php/7.0/cli/conf.d/20-posix.ini
- /etc/php/7.0/cli/conf.d/20-readline.ini
- /etc/php/7.0/cli/conf.d/20-recode.ini
- /etc/php/7.0/cli/conf.d/20-shmop.ini
- /etc/php/7.0/cli/conf.d/20-sockets.ini
- /etc/php/7.0/cli/conf.d/20-sysvmsg.ini
- /etc/php/7.0/cli/conf.d/20-sysvsem.ini
- /etc/php/7.0/cli/conf.d/20-sysvshm.ini
- /etc/php/7.0/cli/conf.d/20-tokenizer.ini
You can also run `php --ini` inside terminal to see which files are used by PHP in CLI mode.
Build step 'Execute shell' marked build as failure
[CHECKSTYLE] Skipping publisher since build result is FAILURE
[JSLINT] Skipping publisher since build result is FAILURE
[PMD] Skipping publisher since build result is FAILURE
[DRY] Collecting duplicate code analysis files...
[DRY] Finding all files that match the pattern build/logs/pmd-cpd.xml
[DRY] Parsing 1 file in <https://ci.phpmyadmin.net/job/phpMyAdmin/ws/>
[DRY] Successfully parsed file <https://ci.phpmyadmin.net/job/phpMyAdmin/ws/build/logs/pmd-cpd.xml> with 12 unique warnings and 0 duplicates.
[DRY] Computing warning deltas based on reference build #1923
[TASKS] Skipping publisher since build result is FAILURE
[ANALYSIS-COLLECTOR] Computing warning deltas based on reference build #1923
Recording plot data
Publishing Clover coverage report...
Clover xml file does not exist in: <https://ci.phpmyadmin.net/job/phpMyAdmin/ws/> called: build/logs/clover.xml and will not be copied to: /var/lib/jenkins/jobs/phpMyAdmin/builds/1924/cloverphp/clover.xml
Could not find 'build/coverage/build/logs/clover.xml'. Did you generate the XML report for Clover?
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing PHPUnit-3.x (default)
[xUnit] [INFO] - [PHPUnit-3.x (default)] - 1 test report file(s) were found with the pattern 'build/logs/junit.xml' relative to '<https://ci.phpmyadmin.net/job/phpMyAdmin/ws/'> for the testing framework 'PHPUnit-3.x (default)'.
[xUnit] [ERROR] - Test reports were found but not all of them are new. Did all the tests run?
* <https://ci.phpmyadmin.net/job/phpMyAdmin/ws/build/logs/junit.xml> is 23 hr old
[xUnit] [INFO] - Failing BUILD.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] - Skipping tests recording.
[xUnit] [INFO] - Stop build.
[JDepend] JDepend plugin is ready
[JDepend] Couldn't generate JDepend file at 'build/logs/jdepend.xml'java.io.FileNotFoundException: <https://ci.phpmyadmin.net/job/phpMyAdmin/ws/build/logs/jdepend.xml> (No such file or directory)
Dear all,
This is Pranavan. Few weeks before I started examining phpMyAdmin code and I found and opened few bugs in issue tracker forum. Also I have contributed in two bug fixes as well.
This time I come up with a new feature which I feel, would be a really helpful feature to the frequent phpMyAdmin users who use phpMyAdmin for their all querying needs.
Earlier I thought there is no way to record the query history in phpMyAdmin and then after a good amount of surfing, I found and got to know about pma_history relation residing under phpMyAdmin database.
But still I feel it's not much user friendly because whenever we want to know what queries we issued recently and to re-execute the same queries(for select queries), we always want to go to this particular pma_history table, copy the query and then comeback to the place where we are working, paste and execute which is little troublesome for the user. I myself found it difficult many times to do this continuously.
A research by Mark Sanderson and Susan Dumais on"Examining Repetition in User Search Behavior" found that 33% of user queries were repetitions of queries previously issued by the same user. This not only applicable for web surfing but also for database querying required in other applications as well.
Therefore it's better to have an easy way to access the history of the past queries and further having a way to directly re-execute an already executed select query.
I suggest to have an additional tab in table level and DB level GUI of phpMyAdmin by clicking which user will be able to view and further re-execute (if he/she needs to) a past query again easily(If it is possible).
I have already started working on this feature and this mail is to discuss whether what I feel is feasible and to get suggestions from you all.
Please support and suggest me any ideas related to this.
Thanks and Best Regards,
S.Pranavan
Third year Computer Engineering,
University of Peradeniya,
Sri Lanka.