There is something that I would like to ask for...
As my exams were going on, I was not able to fix many bugs, just one for
the deadline thing.
Now that my exams are over I am into this thing, and trying to fix more
bugs.
I would like the organisation to allow me to edit my proposal, so that I
could include details about my contributions to the phpMyAdmin project.
Thanking you
--
Abhishek Kandoi
First Year, Computer Science and Engineering
Indian Institute of Technology Roorkee
About Me : about.me/kandoiabhi
See <http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/3291/changes>
Changes:
[weblate] Translated using Weblate (Azerbaijani)
[weblate] Translated using Weblate (Catalan)
[weblate] Translated using Weblate (Croatian)
[weblate] Translated using Weblate (Danish)
[weblate] Translated using Weblate (French)
[weblate] Translated using Weblate (Italian)
[weblate] Translated using Weblate (Japanese)
[weblate] Translated using Weblate (Kazakh)
[weblate] Translated using Weblate (Korean)
[weblate] Translated using Weblate (Latvian)
[weblate] Translated using Weblate (Malay)
[weblate] Translated using Weblate (Persian)
[weblate] Translated using Weblate (Portuguese (Brazil))
[weblate] Translated using Weblate (Serbian)
[weblate] Translated using Weblate (Spanish)
[weblate] Translated using Weblate (Tamil)
[weblate] Translated using Weblate (Tatar)
[weblate] Translated using Weblate (Thai)
[weblate] Translated using Weblate (Traditional Chinese)
[weblate] Translated using Weblate (Turkmen)
[weblate] Translated using Weblate (Uzbek (latin))
[weblate] Translated using Weblate (Welsh)
[marc] Bug #3908 Calendar widget improperly redirects to home fixed
[marc] Code cleanup
[marc] ChangeLog entry for bug #3908
[marc] Fix merge conflict
------------------------------------------
Started by GitHub push by weblate
Building in workspace <http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/ws/>
Checkout:workspace / <http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/ws/> - hudson.remoting.LocalChannel@108d02eb
Using strategy: Default
Last Built Revision: Revision 9cc9316238c3624fa9e30adcf015c71cf58343cb (origin/master)
Fetching changes from 1 remote Git repository
Fetching upstream changes from origin
Commencing build of Revision fa16a717bca507ce3268cef1bef55b7e34d199a4 (origin/master)
Checking out Revision fa16a717bca507ce3268cef1bef55b7e34d199a4 (origin/master)
[workspace] $ /bin/sh -xe /tmp/hudson1279521022197684311.sh
+ ./scripts/generate-mo --quiet
po/es.po:12546: missing `msgstr' section
po/es.po:12547:2: syntax error
po/es.po:12547: keyword "HEAD" unknown
po/es.po:12561: duplicate message definition...
po/es.po:6840: ...this is the location of the first definition
po/es.po:12565: duplicate message definition...
po/es.po:6844: ...this is the location of the first definition
po/es.po:12569: duplicate message definition...
po/es.po:6849: ...this is the location of the first definition
po/es.po:12576: duplicate message definition...
po/es.po:6855: ...this is the location of the first definition
po/es.po:12580: duplicate message definition...
po/es.po:6859: ...this is the location of the first definition
po/es.po:15235:2: syntax error
po/es.po:15235: keyword "QA_4_0" unknown
msgfmt: found 10 fatal errors
po/fr.po:12537: missing `msgstr' section
po/fr.po:12538:2: syntax error
po/fr.po:12538: keyword "HEAD" unknown
po/fr.po:12539: keyword "HEAD" unknown
po/fr.po:12543: keyword "QA_4_0" unknown
po/fr.po:12546: keyword "QA_4_0" unknown
msgfmt: found 6 fatal errors
po/ms.po:140:2: syntax error
po/ms.po:140: keyword "HEAD" unknown
po/ms.po:147:2: syntax error
po/ms.po:147: keyword "QA_4_0" unknown
msgfmt: found 4 fatal errors
po/th.po:727:2: syntax error
po/th.po:727: keyword "HEAD" unknown
po/th.po:729: missing `msgstr' section
po/th.po:730:2: syntax error
po/th.po:731: missing `msgstr' section
po/th.po:732: keyword "QA_4_0" unknown
po/th.po:781:2: syntax error
po/th.po:781: keyword "HEAD" unknown
po/th.po:786:2: syntax error
po/th.po:790:2: syntax error
po/th.po:790: keyword "QA_4_0" unknown
po/th.po:6761: duplicate message definition...
po/th.po:789: ...this is the location of the first definition
msgfmt: found 12 fatal errors
po/zh_TW.po:8634:2: syntax error
po/zh_TW.po:8634: keyword "HEAD" unknown
po/zh_TW.po:8640:2: syntax error
po/zh_TW.po:8641: keyword "QA_4_0" unknown
msgfmt: found 4 fatal errors
Build step 'Execute shell' marked build as failure
[CHECKSTYLE] 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 files in <http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/ws/>
[DRY] Successfully parsed file <http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/ws/build/logs/pmd-cpd.xml> of module with 45 warnings.
[DRY] Computing warning deltas based on reference build #3290
[TASKS] Skipping publisher since build result is FAILURE
[ANALYSIS-COLLECTOR] Computing warning deltas based on reference build #3290
Recording plot data
[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 '<http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/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?
* <http://ci.phpmyadmin.net/job/phpMyAdmin-continuous/ws/build/logs/junit.xml> is 2 hr 5 min old
[xUnit] [INFO] - Setting the build status to FAILURE
[xUnit] [INFO] - Stopping recording.
Hi,
Can I get some thoughts on [1]? The way the code exists currently, you can
insert bad data (you'll get a standard MySQL warning after the insert). For
example, inserting the output of the MD5() function in to a TINYINT column.
This pull request implements the AES_ENCRYPT function, but silently fails
to show the salt form field in the event the user tries to insert to an
invalid column type...so it looks broken in the case the user is trying to
do something that's a bad idea.
In keeping with the current system, I thought it should always show the
salt field and proceed with the insert regardless of the column type,
however that isn't the most user-friendly idea. To keep users most happy, I
wondered if we should implement some sanity checks for some column types
and show an inline warning as needed (similar to the recently merged
warning when creating a new user with the same username). Some of the
functions require or suggest certain column types which we could easily
check, but I'm not sure it's phpMyAdmin's responsibility to constantly warn
the user in this case.
Regardless, the question at hand is whether this pull request can be merged
as-is or if we should change the behavior in the case of an invalid column
type.
Thanks!
1 - https://github.com/phpmyadmin/phpmyadmin/pull/290#issuecomment-17281963
Hi,
even if [0] looks curious (and I can reproduce the problem with the
sample table), I believe it's an isolated case. Browsing a table is so
frequently done that we would have got more error reports.
So I see no show-stopper for 4.0.0. Comments?
[0] https://sourceforge.net/p/phpmyadmin/bugs/3902/
--
Marc Delisle
http://infomarc.info
Welcome to phpMyAdmin 4.0.0. With this version, the HTML frames are gone
and the navigation panel now presents a tree. This version requires
Javascript.
Version 4.0 contains many bug fixes and smaller new features; moreover,
the documentation has a new look and contains an index.
Details will appear on http://phpmyadmin.net. In a hurry? you can visit
https://sourceforge.net/projects/phpmyadmin/files to download.
Marc Delisle, for the team
Hi all
will there ever be 3.5.9 release? I don't think it's needed as 4.0
should be out pretty soon.
The main reason why I ask is whether it makes sense to show 3.5 branch
on our localization server. Also we could stop doing fixes in QA_3_5
branch, saving us some backporting effort.
--
Michal ÄŒihaÅ™ | http://cihar.com | http://blog.cihar.com
Hi,
I was training someone new to phpMyAdmin this morning and she was
surprised by the interface's behavior.
After Operations > Empty the table, the interface tries to browse the
table, then goes to the Structure page. She did not expect this.
Maybe, when browsing an empty table, we should avoid to go to Structure?
--
Marc Delisle
http://infomarc.info