When a user does not define `$cfg['Servers'][$i]['host']` but does set
`$cfg['Servers'][$i]['connect_type'] = 'tcp';`, the default host of
'localhost' is used, forcing the connection over socket because of how
MySQL interprets the host.
Would it be helpful to detect when the user specifies 'tcp' and use a
default host of '127.0.0.1' instead of 'localhost', or is that getting to
be too much guessing about what the user wants?
See <https://ci.phpmyadmin.net/job/documentation/265/>
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building in workspace <https://ci.phpmyadmin.net/job/documentation/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/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from https://github.com/phpmyadmin/phpmyadmin.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:810)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1066)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1097)
at hudson.scm.SCM.checkout(SCM.java:495)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1278)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1729)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress https://github.com/phpmyadmin/phpmyadmin.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout:
stderr: fatal: unable to access 'https://github.com/phpmyadmin/phpmyadmin.git/': gnutls_handshake() failed: Error in the pull function.
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1719)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1463)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:808)
... 11 more
ERROR: null
[WARNINGS] Skipping publisher since build result is FAILURE
Welcome to phpMyAdmin 4.7.0-beta1, the first public beta release of the
upcoming version 4.7.0.
This version is available for public testing before the actual release
of 4.7.0. You can see existing issues or log new ones at
<https://github.com/phpmyadmin/phpmyadmin/issues>.
A complete list of new features and bugs that have been fixed is
available in the ChangeLog file or changelog.php included with this release.
A few highlights:
* Log failed authentication attempts to syslog (useful for parsing by
fail2ban, for example)
* Add filtering for the database list
* Add table filtering to the database 'Structure' tab
* Add support for exporting user settings as a config.inc.php snippet
* Add option to delete settings from browser storage
* Changes to the JSON import and export format to better follow the JSON
specification, however this breaks
compatibilty with older versions. See
https://docs.phpmyadmin.net/en/latest/import_export.html#json
* Support for IPv6 proxies
* Allow more connection parameters for the controluser connection
* Rename 'Relations' to 'Relationships' in many places as it's a more
correct term
* More documentation for export configuration options
* Remove support for Swekey authentication
* Remove support for old, unsupported versions of Microsoft Internet
Explorer
* Removed $cfg['ThemePath']
Starting with this version, phpMyAdmin uses Composer to manage PHP
library dependencies while under development. Users downloading the
official source distribution will not notice a difference, however users
of the git repository should refer to
https://docs.phpmyadmin.net/en/latest/setup.html#installing-from-git for
details.
Also beginning with this version, we've made some changes to the files
available for download. There are now three different packages
available: `all-langauges` and `english` are the same downloads we've
offered for some time, the former featuring all languages for which we
have a reasonable amount of translations and the latter being a smaller
English-only download. We have added a `source` download, which includes
the unit test suite, Gettext po files, documentation source, and
JavaScript source files; these are omited from the other packages as
most users have no need for them. We have also reduced the number of
compression formats available due to low utilization; for each package
we have .tar.gz, .tar.xz, and .zip formats available.
There are many more improvements; please refer to the ChangeLog for full
details.
As always, downloads are available at https://www.phpmyadmin.net
Thanks to our sponsors for helping to make this work possible!
The phpMyAdmin Team
The phpMyAdmin project is seeking a contract developer to assist with
project development, including bug fixing and refactoring.
For full details including application instructions, please see the news
announcement at
https://www.phpmyadmin.net/news/2017/1/25/seeking-phpmyadmin-developer-one-…
The deadline for this initial round of proposals is 2017-02-06.
For the team,
Isaac
I plan to release -beta1 later today, please commit any last minute fixes or submit and tag known issues in the tracker in order to be included in the release/notes.
Hello All
I am Anirud Samala, a 3rd year Computer Science undergraduate, and a
newcomer open source. I was hoping to be able to contribute to this
project, but I'm confused on how to start. I would really appreciate some
guidance on how to start contributing, or which issues I could start to
work on
Thank You
Anirud Samala
Since we do not intend to release 4.6.7 and plan to instead jump to 4.7.0
in two months, what should we do with QA_4_6? Should we still merge bug
fixes in to QA_4_6 just in case we need a 4.6.7, or are we prepared to
commit fully to 4.7.0?
The phpMyAdmin project is pleased to announce the release of
phpMyAdmin versions 4.6.6 (including bug and security fixes), 4.4.15.10
(security fixes), and 4.0.10.19 (security fixes). We recommend all
users update their phpMyAdmin installations.
There have been changes in the behavior since previous version:
* Changed the suggested text in the query window for delete queries to
avoid accidental data loss
* Re-introduce a page which shows the output of phpinfo()
Aside from the changes and security improvements, many bugs have been
fixed including:
* Parsing of SQL queries with the BINARY function
* Syntax error when adding or changing TIMESTAMP columns with default
value as NULL
* Broken "Edit" and "Export" links in the Routines tab
* Creating a new user on older MariaDB servers
* Format button in the SQL tab broken
* Fixes for PHP 7.1
* Problems with MySQL servers running with `lower_case_names=2`
* Fixes for several PHP notices/warnings being shown
Please note that, as previously announced, the 4.4 branch is no longer
supported. This security release is planned as the final 4.4 release.
See the 4.4.15.10 release notes for more information.
As always, downloads and release notes are available at
https://www.phpmyadmin.net/downloads
For more information, please see
* <https://www.phpmyadmin.net/files/4.6.6/>
* <https://www.phpmyadmin.net/files/4.4.15.10/>
* <https://www.phpmyadmin.net/files/4.0.10.19/>
The phpMyAdmin team
Hello developers,
We are less than a week away from the scheduled release of 4.6.6 and
4.7.0-beta (at least, I'm anticipating calling it 'beta' with no
public 'alpha' release, as we get lots of reports on 'master' as it
is, feel free to object if you disagree).
We currently have two issues marked as blocking 4.6.6 [1], although
the search issue has a patch and appears to be a trivial fix. Fixing
Designer may be more difficult.
Anyway, we have a number of issues remaining on 4.7.0, but currently
nothing that I think should block the beta release.
Unless we hit a blocker on 4.6.6, I intend to go ahead with the
releases pretty much on schedule, as well as create the QA_4_7 branch
so that we can easily feature-freeze 4.7.x. So for a short while,
we'll be supporting QA_4_6, QA_4_7, and master branches. Strings for
4.7.x will freeze next week as well so that translators can finish
their work before the final release.
I believe we discussed the possibility of calling the upcoming release
5.0.0, due to the change to using Composer for dependency handling,
and I believe no one really supported that proposal mostly because we
aren't changing anything for the users in a way to justify a major
version change.
Regards,
Isaac
1 - https://github.com/phpmyadmin/phpmyadmin/milestones/4.6.6