[jira] [Created] (LOGGING-197) Recursive update exception with SLF4J
Emmanuel Bourg created LOGGING-197:
--
Summary: Recursive update exception with SLF4J
Key: LOGGING-197
URL: https://issues.apache.org/jira/browse/LOGGING-197
Project: Commons Logging
Issue Type: Bug
Affects Versions: 1.3.0
Reporter: Emmanuel Bourg
It looks like there is an issue with the Slf4jLogFactory added to Commons
Logging 1.3, the {{Slf4jLogFactory.getInstance()}} method is called recursively
between SLF4J and Commons Logging. The loop is halted by the
{{ConcurrentHashMap.computeIfAbsent()}} methods that throws an
IllegalStateException, but replacing computeIfAbsent with a classic get, test
if null, set, results in a stack overflow.
This issue triggers test failures in SLF4J and httpcomponents-client:
https://bugs.debian.org/1061025
https://bugs.debian.org/1060960
This issue was reported by Vladimir Petko 7 months ago on the user list with a
link to a reproducer:
https://www.mail-archive.com/user@commons.apache.org/msg12967.html
https://github.com/vpa1977/commons-logging-reproducer
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MATH-1569) Manual array copy
[
https://issues.apache.org/jira/browse/MATH-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320002#comment-17320002
]
Emmanuel Bourg commented on MATH-1569:
--
The changes look good, I'm +1 for applying it.
{{System.arraycopy}} is notoriously faster than loops, others have already
extensively benchmarked it, don't bother checking it again.
https://stackoverflow.com/questions/18638743/is-it-better-to-use-system-arraycopy-than-a-for-loop-for-copying-arrays
> Manual array copy
> -
>
> Key: MATH-1569
> URL: https://issues.apache.org/jira/browse/MATH-1569
> Project: Commons Math
> Issue Type: Sub-task
>Reporter: Arturo Bernal
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Deleted] (JEXL-345) DAFTAR SITUS IDN POKER ONLINE TERPERCAYA 2021
[ https://issues.apache.org/jira/browse/JEXL-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg deleted JEXL-345: > DAFTAR SITUS IDN POKER ONLINE TERPERCAYA 2021 > - > > Key: JEXL-345 > URL: https://issues.apache.org/jira/browse/JEXL-345 > Project: Commons JEXL > Issue Type: Bug >Reporter: Kebas Rasanya >Priority: Major > > • Tidak ada perjalanan > Tidak ada yang lebih membuat frustrasi daripada mengemudi selama satu jam > untuk sampai ke ruang kartu bata dan mortir lokal Anda, hanya untuk menemukan > meja permainan uang tunai penuh dan ada sepuluh pemain dalam daftar tunggu. > Anda telah berusaha keras untuk sampai ke sana, setidaknya Anda ingin bermain > sedikit sebelum pulang. > • Lebih banyak tangan > Poker online juga memungkinkan Anda untuk bermain lebih dari sekadar > permainan poker langsung. Ada alasan mereka mengatakan bahwa generasi online > sangat baik dengan sangat cepat; mereka mampu bermain lebih banyak tangan > dalam setahun daripada veteran beruban yang bermain sepanjang hidup mereka, > bahkan dalam permainan uang. > Dengan bank waktu untuk setiap keputusan, kartu [poker > online|https://defensebusiness.org/] tidak akan pernah terlalu lama. Di meja > poker, bagaimanapun, seri tanking bisa menjadi menjengkelkan, mendorong > pemain untuk terus menelepon. Bermain tangan yang tidak boleh dimainkan > karena bosan bukanlah strategi yang baik. > • Varietas Game > Mungkin No Limit Hold'em bukan urusan Anda, dan Anda lebih suka memainkan > permainan yang berbeda. Nah, kecuali Anda berada di Las Vegas atau ruang > poker spesialis lain, akan sangat sulit bagi Anda untuk menemukan permainan > karena sebagian besar kamar poker memiliki permainan terbatas. Ini tidak > terjadi di poker online. Itulah ulasan tentang panduan bermain di situs [idn > poker]|https://scannewsnigeria.com/] terbaru. Semoga artikel ini bermanfaat. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IO-692) PathUtils delete throws an exception when deleting a symlink that points to a file that does not exist
[
https://issues.apache.org/jira/browse/IO-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg resolved IO-692.
---
Resolution: Fixed
Thank you for the report, the suggested fix has been applied.
> PathUtils delete throws an exception when deleting a symlink that points to a
> file that does not exist
> --
>
> Key: IO-692
> URL: https://issues.apache.org/jira/browse/IO-692
> Project: Commons IO
> Issue Type: Bug
>Affects Versions: 2.8.0
> Environment: {noformat}
> java version "1.8.0_202" Java(TM) SE Runtime Environment (build
> 1.8.0_202-b08) Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed
> mode)
> {noformat}
>Reporter: Matthew Rooney
>Priority: Major
> Fix For: 2.9.0
>
>
> *PathUtils.delete* throws an Exception when deleting a symlink to a file that
> doesn't exist, in our case this was when the files were deleted out of
> sequence.
> Minimal reproducing code running as a unit test (scala). This creates a
> symlink to a fail that does not exist at all.
> {code:java}
> val file = Files.createSymbolicLink(
> Paths.get("target", "x.txt"),
> Paths.get("target", "y.txt").toAbsolutePath,
> )
> PathUtils.delete(file)
> {code}
> This throws the following exception
> {noformat}
> [error]java.nio.file.NoSuchFileException: target/x.txt
> (UnixException.java:86)
> [error] sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> [error] sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> [error] sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> [error]
> sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:55)
> [error]
> sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:144)
> [error] org.apache.commons.io.file.PathUtils.deleteFile(PathUtils.java:361)
> [error] org.apache.commons.io.file.PathUtils.delete(PathUtils.java:304)
> [error]
> org.apache.commons.io.file.PathUtils.delete(PathUtils.java:280){noformat}
> The offending code is this in *PathUtils*
> {code:java}
> public static PathCounters deleteFile(final Path file, final DeleteOption...
> options) throws IOException {
> // Files.deleteIfExists() never follows links, so use
> LinkOption.NOFOLLOW_LINKS in other calls to Files.
> if (Files.isDirectory(file, LinkOption.NOFOLLOW_LINKS)) {
> throw new NoSuchFileException(file.toString());
> }
> final PathCounters pathCounts = Counters.longPathCounters();
> final boolean exists = Files.exists(file, LinkOption.NOFOLLOW_LINKS);
> final long size = exists ? Files.size(file) : 0;
> if (overrideReadOnly(options) && exists) {
> setReadOnly(file, false, LinkOption.NOFOLLOW_LINKS);
> }
> if (Files.deleteIfExists(file)) {
> pathCounts.getFileCounter().increment();
> pathCounts.getByteCounter().add(size);
> }
> return pathCounts;
> }
> {code}
> This manifests because
> {code:java}
> Files.exists(file, LinkOption.NOFOLLOW_LINKS); // this always returns true if
> the symlink exists
> Files.size(file) // this throws an exception because there is no file to
> check the size of{code}
> A guess at the solution would be to only check the size if the file exists
> and is not a symlink
> {code:java}
> final long size = exists && !Files.isSymbolicLink() ? Files.size(file) :
> 0;{code}
> This was discovered when using *FileUtils.deleteDirectory* where we have a
> structure like the following. We clean up these directories when the process
> finishes, since upgrading to 2.8.0 this fails if the parent directory is
> deleted before the child.
> {code:java}
> work_dir/
>parent_dir/
> big_file.txt
>child_dir/
> symlink_to_big_file.txt{code}
> As a work around using *PathUtils.deleteDirectory* seems to work regardless
> of the deletion order
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IO-692) PathUtils delete throws an exception when deleting a symlink that points to a file that does not exist
[
https://issues.apache.org/jira/browse/IO-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated IO-692:
--
Fix Version/s: 2.9.0
> PathUtils delete throws an exception when deleting a symlink that points to a
> file that does not exist
> --
>
> Key: IO-692
> URL: https://issues.apache.org/jira/browse/IO-692
> Project: Commons IO
> Issue Type: Bug
>Affects Versions: 2.8.0
> Environment: {noformat}
> java version "1.8.0_202" Java(TM) SE Runtime Environment (build
> 1.8.0_202-b08) Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed
> mode)
> {noformat}
>Reporter: Matthew Rooney
>Priority: Major
> Fix For: 2.9.0
>
>
> *PathUtils.delete* throws an Exception when deleting a symlink to a file that
> doesn't exist, in our case this was when the files were deleted out of
> sequence.
> Minimal reproducing code running as a unit test (scala). This creates a
> symlink to a fail that does not exist at all.
> {code:java}
> val file = Files.createSymbolicLink(
> Paths.get("target", "x.txt"),
> Paths.get("target", "y.txt").toAbsolutePath,
> )
> PathUtils.delete(file)
> {code}
> This throws the following exception
> {noformat}
> [error]java.nio.file.NoSuchFileException: target/x.txt
> (UnixException.java:86)
> [error] sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> [error] sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> [error] sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> [error]
> sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(UnixFileAttributeViews.java:55)
> [error]
> sun.nio.fs.UnixFileSystemProvider.readAttributes(UnixFileSystemProvider.java:144)
> [error] org.apache.commons.io.file.PathUtils.deleteFile(PathUtils.java:361)
> [error] org.apache.commons.io.file.PathUtils.delete(PathUtils.java:304)
> [error]
> org.apache.commons.io.file.PathUtils.delete(PathUtils.java:280){noformat}
> The offending code is this in *PathUtils*
> {code:java}
> public static PathCounters deleteFile(final Path file, final DeleteOption...
> options) throws IOException {
> // Files.deleteIfExists() never follows links, so use
> LinkOption.NOFOLLOW_LINKS in other calls to Files.
> if (Files.isDirectory(file, LinkOption.NOFOLLOW_LINKS)) {
> throw new NoSuchFileException(file.toString());
> }
> final PathCounters pathCounts = Counters.longPathCounters();
> final boolean exists = Files.exists(file, LinkOption.NOFOLLOW_LINKS);
> final long size = exists ? Files.size(file) : 0;
> if (overrideReadOnly(options) && exists) {
> setReadOnly(file, false, LinkOption.NOFOLLOW_LINKS);
> }
> if (Files.deleteIfExists(file)) {
> pathCounts.getFileCounter().increment();
> pathCounts.getByteCounter().add(size);
> }
> return pathCounts;
> }
> {code}
> This manifests because
> {code:java}
> Files.exists(file, LinkOption.NOFOLLOW_LINKS); // this always returns true if
> the symlink exists
> Files.size(file) // this throws an exception because there is no file to
> check the size of{code}
> A guess at the solution would be to only check the size if the file exists
> and is not a symlink
> {code:java}
> final long size = exists && !Files.isSymbolicLink() ? Files.size(file) :
> 0;{code}
> This was discovered when using *FileUtils.deleteDirectory* where we have a
> structure like the following. We clean up these directories when the process
> finishes, since upgrading to 2.8.0 this fails if the parent directory is
> deleted before the child.
> {code:java}
> work_dir/
>parent_dir/
> big_file.txt
>child_dir/
> symlink_to_big_file.txt{code}
> As a work around using *PathUtils.deleteDirectory* seems to work regardless
> of the deletion order
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (LANG-1621) Add JAVA_VM_COMPRESSED_MODE
[ https://issues.apache.org/jira/browse/LANG-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17242309#comment-17242309 ] Emmanuel Bourg commented on LANG-1621: -- This is a very specialized system property compared to the other ones mostly related to the Java version. Is this really that useful in SystemUtils ? > Add JAVA_VM_COMPRESSED_MODE > --- > > Key: LANG-1621 > URL: https://issues.apache.org/jira/browse/LANG-1621 > Project: Commons Lang > Issue Type: Improvement >Reporter: Arturo Bernal >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Add "java.vm.compressedOopsMode" properties from system. > Do we need to return the value? getCompreesMode maybe ?? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (COMPRESS-507) Commons Compress cannot be built with JDK14 due to Pack200 removal
[ https://issues.apache.org/jira/browse/COMPRESS-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049797#comment-17049797 ] Emmanuel Bourg commented on COMPRESS-507: - I was hoping to build the native library before releasing to Maven Central, but I'm struggling a bit on this part. I'll probably upload a beta release with just the pure Java packer/unpacker and deal with the native library later (the native decompressor is 5 times faster than the Java one). > Commons Compress cannot be built with JDK14 due to Pack200 removal > -- > > Key: COMPRESS-507 > URL: https://issues.apache.org/jira/browse/COMPRESS-507 > Project: Commons Compress > Issue Type: Bug > Components: Build, Compressors >Affects Versions: 1.20 >Reporter: Vincent Privat >Priority: Major > > Oracle dropped Pack200 in JDK14 as per > [https://bugs.openjdk.java.net/browse/JDK-8232022] > Someone expressed his will to maintain Pack200 here: > [https://mail.openjdk.java.net/pipermail/jdk-dev/2020-March/003979.html] > [https://github.com/pfirmstone/Pack200-ex-openjdk] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (COMPRESS-507) Commons Compress cannot be built with JDK14 due to Pack200 removal
[ https://issues.apache.org/jira/browse/COMPRESS-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049402#comment-17049402 ] Emmanuel Bourg commented on COMPRESS-507: - At this point both projects derive from the OpenJDK 14 sources and are basically identical. I've contacted Peter Firmstone to try to merge our efforts. I'm not aware of other pack200 forks. > Commons Compress cannot be built with JDK14 due to Pack200 removal > -- > > Key: COMPRESS-507 > URL: https://issues.apache.org/jira/browse/COMPRESS-507 > Project: Commons Compress > Issue Type: Bug > Components: Build, Compressors >Affects Versions: 1.20 >Reporter: Vincent Privat >Priority: Major > > Oracle dropped Pack200 in JDK14 as per > [https://bugs.openjdk.java.net/browse/JDK-8232022] > Someone expressed his will to maintain Pack200 here: > [https://mail.openjdk.java.net/pipermail/jdk-dev/2020-March/003979.html] > [https://github.com/pfirmstone/Pack200-ex-openjdk] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (COMPRESS-507) Commons Compress cannot be built with JDK14 due to Pack200 removal
[ https://issues.apache.org/jira/browse/COMPRESS-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049082#comment-17049082 ] Emmanuel Bourg commented on COMPRESS-507: - I've also started a project to maintain pack200 at https://github.com/pack200/pack200 > Commons Compress cannot be built with JDK14 due to Pack200 removal > -- > > Key: COMPRESS-507 > URL: https://issues.apache.org/jira/browse/COMPRESS-507 > Project: Commons Compress > Issue Type: Bug > Components: Build, Compressors >Affects Versions: 1.20 >Reporter: Vincent Privat >Priority: Major > > Oracle dropped Pack200 in JDK14 as per > [https://bugs.openjdk.java.net/browse/JDK-8232022] > Someone expressed his will to maintain Pack200 here: > [https://mail.openjdk.java.net/pipermail/jdk-dev/2020-March/003979.html] > [https://github.com/pfirmstone/Pack200-ex-openjdk] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (LOGGING-168) Technical Support Expiration Date
[ https://issues.apache.org/jira/browse/LOGGING-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg resolved LOGGING-168. Resolution: Invalid Closing since Jira isn't the right place for this kind of question. > Technical Support Expiration Date > - > > Key: LOGGING-168 > URL: https://issues.apache.org/jira/browse/LOGGING-168 > Project: Commons Logging > Issue Type: Wish >Reporter: Sergi Comeche >Priority: Minor > Labels: logging > > Hello, > I work for a long-term project which requires strong and stable technical > support for every software used. > I want to know how long you are providing technical support for > Commons-logging 1.1.1. > Please I appreciate so much that you can give me expiration dates for this > software product or expectations of its EOL. > Thank you! > Sergi -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (LOGGING-168) Technical Support Expiration Date
[ https://issues.apache.org/jira/browse/LOGGING-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated LOGGING-168: --- Affects Version/s: (was: 1.1.1) Issue Type: Wish (was: Bug) Priority: Minor (was: Major) > Technical Support Expiration Date > - > > Key: LOGGING-168 > URL: https://issues.apache.org/jira/browse/LOGGING-168 > Project: Commons Logging > Issue Type: Wish >Reporter: Sergi Comeche >Priority: Minor > Labels: logging > > Hello, > I work for a long-term project which requires strong and stable technical > support for every software used. > I want to know how long you are providing technical support for > Commons-logging 1.1.1. > Please I appreciate so much that you can give me expiration dates for this > software product or expectations of its EOL. > Thank you! > Sergi -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (LANG-1494) Add org.apache.commons.lang3.time.CalendarUtils
[
https://issues.apache.org/jira/browse/LANG-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16958675#comment-16958675
]
Emmanuel Bourg commented on LANG-1494:
--
I'm not sure this is a useful addition to the Commons Lang API. I see two use
cases:
1. The user already has a {{Calendar}} instance and wants to extract the day
and the month. With {{CalendarUtils}} he would write:
{code:java}
CalendarUtils utils = new CalendarUtils(calendar);
int dayOfMonth = utils.getDayOfMonth();
{code}
instead of:
{code:java}
int dayOfMonth = calendar.get(DAY_OF_MONTH);
{code}
2. The user doesn't have a {{Calendar}} instance but wants to retrieve the
current year for example:
{code:java}
int year = CalendarUtils.INSTANCE.getYear();
{code}
but Commons Lang 3 depends on Java 8, the java.time API could be used as well:
{code:java}
int year = LocalDate.now().getYear();
{code}
So I see little incentive in using {{CalendarUtils}}, it always end in a longer
syntax. Also the fact that it's a non static Utils class is rather unusual.
> Add org.apache.commons.lang3.time.CalendarUtils
> ---
>
> Key: LANG-1494
> URL: https://issues.apache.org/jira/browse/LANG-1494
> Project: Commons Lang
> Issue Type: New Feature
> Components: lang.time.*
>Reporter: Gary D. Gregory
>Assignee: Gary D. Gregory
>Priority: Major
> Fix For: 3.10
>
>
> Add {{org.apache.commons.lang3.time.CalendarUtils}} to provide util methods
> and wrap a {{Calendar}} to provide shortcuts. Right now, there are only a
> handful of methods.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CLI-298) Define CLI options via configuration file
[ https://issues.apache.org/jira/browse/CLI-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953758#comment-16953758 ] Emmanuel Bourg commented on CLI-298: I admit I'm not seduced either by the format proposed. There is a duplication between the options defined in the file and the options parsed in the listener. Also, the purpose of the listener seems mostly to be to build an object model equivalent to the command line arguments. This problem is more cleanly solved by an annotation based approach like JCommander. We could get some inspiration from other CLI libraries but we would probably end up rewriting the same code. Unless we have a clever novel design idea I don't think it's worth rewriting what others have already done. > Define CLI options via configuration file > - > > Key: CLI-298 > URL: https://issues.apache.org/jira/browse/CLI-298 > Project: Commons CLI > Issue Type: Improvement > Components: Options definition >Affects Versions: 1.5, Nightly Builds >Reporter: Richard >Priority: Minor > Labels: newbie, pull-request-available, ready-to-commit > Original Estimate: 336h > Remaining Estimate: 336h > > Create a configuration that enables users to define CLI options via a > configuration file. Such configuration would normally pre-defined and bundled > inside the executable jar running the application. This would reduce the > amount of code required to define command line options and introduce the > ability to do a lot of the checking a user does (such as converting values to > integers, files, checking if integers are above/below a certain amount, > checking that files or directories do/don't exist etc.) For security > purposes, at compile time calculate an MD5 for the application, if this > doesn't match at runtime warn of corrupted file exception. Also add I18N > since this will be driven via the user experience for exception messages. > So far I've catered for basic options that utilise strings. > Code already started with a pull request at > [https://github.com/zendawg/commons-cli] underneath the branch named > "cli-configuration". > Apologies in advance, never contributed to Apache SWF before. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CLI-298) Define CLI options via configuration file
[ https://issues.apache.org/jira/browse/CLI-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953741#comment-16953741 ] Emmanuel Bourg commented on CLI-298: MD5 is still fine if the purpose is to detect accidental corruption. It isn't if security is at stake. > Define CLI options via configuration file > - > > Key: CLI-298 > URL: https://issues.apache.org/jira/browse/CLI-298 > Project: Commons CLI > Issue Type: Improvement > Components: Options definition >Affects Versions: 1.5, Nightly Builds >Reporter: Richard >Priority: Minor > Labels: newbie, pull-request-available, ready-to-commit > Original Estimate: 336h > Remaining Estimate: 336h > > Create a configuration that enables users to define CLI options via a > configuration file. Such configuration would normally pre-defined and bundled > inside the executable jar running the application. This would reduce the > amount of code required to define command line options and introduce the > ability to do a lot of the checking a user does (such as converting values to > integers, files, checking if integers are above/below a certain amount, > checking that files or directories do/don't exist etc.) For security > purposes, at compile time calculate an MD5 for the application, if this > doesn't match at runtime warn of corrupted file exception. Also add I18N > since this will be driven via the user experience for exception messages. > So far I've catered for basic options that utilise strings. > Code already started with a pull request at > [https://github.com/zendawg/commons-cli] underneath the branch named > "cli-configuration". > Apologies in advance, never contributed to Apache SWF before. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CLI-298) Define CLI options via configuration file
[ https://issues.apache.org/jira/browse/CLI-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953603#comment-16953603 ] Emmanuel Bourg commented on CLI-298: The config file is a properties file or a custom format? > Define CLI options via configuration file > - > > Key: CLI-298 > URL: https://issues.apache.org/jira/browse/CLI-298 > Project: Commons CLI > Issue Type: Improvement > Components: Options definition >Affects Versions: 1.5, Nightly Builds >Reporter: Richard >Priority: Minor > Labels: newbie, pull-request-available, ready-to-commit > Original Estimate: 336h > Remaining Estimate: 336h > > Create a configuration that enables users to define CLI options via a > configuration file. Such configuration would normally pre-defined and bundled > inside the executable jar running the application. This would reduce the > amount of code required to define command line options and introduce the > ability to do a lot of the checking a user does (such as converting values to > integers, files, checking if integers are above/below a certain amount, > checking that files or directories do/don't exist etc.) For security > purposes, at compile time calculate an MD5 for the application, if this > doesn't match at runtime warn of corrupted file exception. Also add I18N > since this will be driven via the user experience for exception messages. > So far I've catered for basic options that utilise strings. > Code already started with a pull request at > [https://github.com/zendawg/commons-cli] underneath the branch named > "cli-configuration". > Apologies in advance, never contributed to Apache SWF before. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CLI-298) Define CLI options via configuration file
[ https://issues.apache.org/jira/browse/CLI-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953167#comment-16953167 ] Emmanuel Bourg commented on CLI-298: Thank you for the contribution Richard. Could you give a short example of options defined with an external file? How do you avoid defining the options twice in the configuration file and in the code handling the option parsing? > Define CLI options via configuration file > - > > Key: CLI-298 > URL: https://issues.apache.org/jira/browse/CLI-298 > Project: Commons CLI > Issue Type: Improvement > Components: Options definition >Affects Versions: 1.5, Nightly Builds >Reporter: Richard >Priority: Minor > Labels: newbie, pull-request-available, ready-to-commit > Original Estimate: 336h > Remaining Estimate: 336h > > Create a configuration that enables users to define CLI options via a > configuration file. Such configuration would normally pre-defined and bundled > inside the executable jar running the application. This would reduce the > amount of code required to define command line options and introduce the > ability to do a lot of the checking a user does (such as converting values to > integers, files, checking if integers are above/below a certain amount, > checking that files or directories do/don't exist etc.) For security > purposes, at compile time calculate an MD5 for the application, if this > doesn't match at runtime warn of corrupted file exception. Also add I18N > since this will be driven via the user experience for exception messages. > So far I've catered for basic options that utilise strings. > Code already started with a pull request at > [https://github.com/zendawg/commons-cli] underneath the branch named > "cli-configuration". > Apologies in advance, never contributed to Apache SWF before. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CLI-298) Define CLI options via configuration file
[ https://issues.apache.org/jira/browse/CLI-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated CLI-298: --- Affects Version/s: (was: 2.0) 1.5 > Define CLI options via configuration file > - > > Key: CLI-298 > URL: https://issues.apache.org/jira/browse/CLI-298 > Project: Commons CLI > Issue Type: Improvement > Components: CLI-2.x >Affects Versions: 1.5, Nightly Builds >Reporter: Richard >Priority: Minor > Labels: newbie, pull-request-available, ready-to-commit > Fix For: 2.1 > > Original Estimate: 336h > Remaining Estimate: 336h > > Create a configuration that enables users to define CLI options via a > configuration file. Such configuration would normally pre-defined and bundled > inside the executable jar running the application. This would reduce the > amount of code required to define command line options and introduce the > ability to do a lot of the checking a user does (such as converting values to > integers, files, checking if integers are above/below a certain amount, > checking that files or directories do/don't exist etc.) For security > purposes, at compile time calculate an MD5 for the application, if this > doesn't match at runtime warn of corrupted file exception. Also add I18N > since this will be driven via the user experience for exception messages. > So far I've catered for basic options that utilise strings. > Code already started with a pull request at > [https://github.com/zendawg/commons-cli] underneath the branch named > "cli-configuration". > Apologies in advance, never contributed to Apache SWF before. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CLI-298) Define CLI options via configuration file
[ https://issues.apache.org/jira/browse/CLI-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated CLI-298: --- Component/s: (was: CLI-2.x) Options definition > Define CLI options via configuration file > - > > Key: CLI-298 > URL: https://issues.apache.org/jira/browse/CLI-298 > Project: Commons CLI > Issue Type: Improvement > Components: Options definition >Affects Versions: 1.5, Nightly Builds >Reporter: Richard >Priority: Minor > Labels: newbie, pull-request-available, ready-to-commit > Fix For: 2.1 > > Original Estimate: 336h > Remaining Estimate: 336h > > Create a configuration that enables users to define CLI options via a > configuration file. Such configuration would normally pre-defined and bundled > inside the executable jar running the application. This would reduce the > amount of code required to define command line options and introduce the > ability to do a lot of the checking a user does (such as converting values to > integers, files, checking if integers are above/below a certain amount, > checking that files or directories do/don't exist etc.) For security > purposes, at compile time calculate an MD5 for the application, if this > doesn't match at runtime warn of corrupted file exception. Also add I18N > since this will be driven via the user experience for exception messages. > So far I've catered for basic options that utilise strings. > Code already started with a pull request at > [https://github.com/zendawg/commons-cli] underneath the branch named > "cli-configuration". > Apologies in advance, never contributed to Apache SWF before. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CLI-298) Define CLI options via configuration file
[ https://issues.apache.org/jira/browse/CLI-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated CLI-298: --- Fix Version/s: (was: 2.1) > Define CLI options via configuration file > - > > Key: CLI-298 > URL: https://issues.apache.org/jira/browse/CLI-298 > Project: Commons CLI > Issue Type: Improvement > Components: Options definition >Affects Versions: 1.5, Nightly Builds >Reporter: Richard >Priority: Minor > Labels: newbie, pull-request-available, ready-to-commit > Original Estimate: 336h > Remaining Estimate: 336h > > Create a configuration that enables users to define CLI options via a > configuration file. Such configuration would normally pre-defined and bundled > inside the executable jar running the application. This would reduce the > amount of code required to define command line options and introduce the > ability to do a lot of the checking a user does (such as converting values to > integers, files, checking if integers are above/below a certain amount, > checking that files or directories do/don't exist etc.) For security > purposes, at compile time calculate an MD5 for the application, if this > doesn't match at runtime warn of corrupted file exception. Also add I18N > since this will be driven via the user experience for exception messages. > So far I've catered for basic options that utilise strings. > Code already started with a pull request at > [https://github.com/zendawg/commons-cli] underneath the branch named > "cli-configuration". > Apologies in advance, never contributed to Apache SWF before. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CLI-298) Define CLI options via configuration file
[ https://issues.apache.org/jira/browse/CLI-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated CLI-298: --- Priority: Minor (was: Trivial) > Define CLI options via configuration file > - > > Key: CLI-298 > URL: https://issues.apache.org/jira/browse/CLI-298 > Project: Commons CLI > Issue Type: Improvement > Components: CLI-2.x >Affects Versions: 2.0, Nightly Builds >Reporter: Richard >Priority: Minor > Labels: newbie, pull-request-available, ready-to-commit > Fix For: 2.1 > > Original Estimate: 336h > Remaining Estimate: 336h > > Create a configuration that enables users to define CLI options via a > configuration file. Such configuration would normally pre-defined and bundled > inside the executable jar running the application. This would reduce the > amount of code required to define command line options and introduce the > ability to do a lot of the checking a user does (such as converting values to > integers, files, checking if integers are above/below a certain amount, > checking that files or directories do/don't exist etc.) For security > purposes, at compile time calculate an MD5 for the application, if this > doesn't match at runtime warn of corrupted file exception. Also add I18N > since this will be driven via the user experience for exception messages. > So far I've catered for basic options that utilise strings. > Code already started with a pull request at > [https://github.com/zendawg/commons-cli] underneath the branch named > "cli-configuration". > Apologies in advance, never contributed to Apache SWF before. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (COMPRESS-487) PKWARE DCL Implode support (ZIP compression method 10)
[
https://issues.apache.org/jira/browse/COMPRESS-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16904105#comment-16904105
]
Emmanuel Bourg commented on COMPRESS-487:
-
I now have a working implementation, it just needs some cleanup/testing and
I'll commit it.
> PKWARE DCL Implode support (ZIP compression method 10)
> --
>
> Key: COMPRESS-487
> URL: https://issues.apache.org/jira/browse/COMPRESS-487
> Project: Commons Compress
> Issue Type: New Feature
> Components: Archivers, Compressors
>Reporter: Emmanuel Bourg
>Assignee: Emmanuel Bourg
>Priority: Minor
> Labels: zip
> Attachments: dclimplode-ascii-1024.zip, dclimplode-ascii-2048.zip,
> dclimplode-ascii-4096.zip, dclimplode-binary-1024.zip,
> dclimplode-binary-2048.zip, dclimplode-binary-4096.zip
>
>
> Commons Compress doesn't yet support the implode compression algorithm
> implemented in the PKWARE Data Compression Library (DCL). This algorithm can
> be used in ZIP files (using the compression method 10, which differs from the
> other implode compression method 6 already supported). It's also used in some
> old file formats like dBASE/xBase and game files from the 90's (.mpq).
> ZIP files using this compression method can be created with recent versions
> of the [PKWARE ZIP Compression Utility|https://www.pkware.com/pkzip]. The
> syntax looks like this:
> {{pkzipc -add -dclimplode=ascii,4096 test.zip *.txt}}
> The format is documented here:
> https://groups.google.com/forum/#!msg/comp.compression/M5P064or93o/W1ca1-ad6kgJ
> and here is the implementation in zlib:
> https://github.com/madler/zlib/blob/master/contrib/blast/blast.c
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (COMPRESS-487) PKWARE DCL Implode support (ZIP compression method 10)
[
https://issues.apache.org/jira/browse/COMPRESS-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated COMPRESS-487:
Assignee: Emmanuel Bourg
> PKWARE DCL Implode support (ZIP compression method 10)
> --
>
> Key: COMPRESS-487
> URL: https://issues.apache.org/jira/browse/COMPRESS-487
> Project: Commons Compress
> Issue Type: New Feature
> Components: Archivers, Compressors
>Reporter: Emmanuel Bourg
>Assignee: Emmanuel Bourg
>Priority: Minor
> Labels: zip
> Attachments: dclimplode-ascii-1024.zip, dclimplode-ascii-2048.zip,
> dclimplode-ascii-4096.zip, dclimplode-binary-1024.zip,
> dclimplode-binary-2048.zip, dclimplode-binary-4096.zip
>
>
> Commons Compress doesn't yet support the implode compression algorithm
> implemented in the PKWARE Data Compression Library (DCL). This algorithm can
> be used in ZIP files (using the compression method 10, which differs from the
> other implode compression method 6 already supported). It's also used in some
> old file formats like dBASE/xBase and game files from the 90's (.mpq).
> ZIP files using this compression method can be created with recent versions
> of the [PKWARE ZIP Compression Utility|https://www.pkware.com/pkzip]. The
> syntax looks like this:
> {{pkzipc -add -dclimplode=ascii,4096 test.zip *.txt}}
> The format is documented here:
> https://groups.google.com/forum/#!msg/comp.compression/M5P064or93o/W1ca1-ad6kgJ
> and here is the implementation in zlib:
> https://github.com/madler/zlib/blob/master/contrib/blast/blast.c
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (FUNCTOR-31) Clean up API for Java 8
[ https://issues.apache.org/jira/browse/FUNCTOR-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899904#comment-16899904 ] Emmanuel Bourg commented on FUNCTOR-31: --- If there isn't much left in the end, maybe we could merge that into commons-lang? > Clean up API for Java 8 > --- > > Key: FUNCTOR-31 > URL: https://issues.apache.org/jira/browse/FUNCTOR-31 > Project: Commons Functor > Issue Type: New Feature >Reporter: Matt Sicker >Priority: Major > > All the interfaces from commons-functor-api have equivalent interfaces in > java.util.function. Several functor implementation classes in the core module > can also be simplified thanks to lambda functions. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CLI-296) CommandLineParser does not throw unrecognized exception if option starts with a prefix substring
[ https://issues.apache.org/jira/browse/CLI-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894789#comment-16894789 ] Emmanuel Bourg commented on CLI-296: Partial option matching is actually a feature of Commons CLI. If the partial option is unambiguous then it's automatically matched. > CommandLineParser does not throw unrecognized exception if option starts with > a prefix substring > > > Key: CLI-296 > URL: https://issues.apache.org/jira/browse/CLI-296 > Project: Commons CLI > Issue Type: Bug > Components: CLI-1.x >Affects Versions: 1.4 >Reporter: Shrikant Dange >Priority: Major > > Suppose the required option is -operation (short and long) for which required > is set to true. > It does not throw unrecognized option exception for following inputs (which > it should throw) > -op, -oper, operation3274y37 > But throws unrecognized option exception for following inputs > -oper5, -o, -operatnn -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (CODEC-253) Upgrade to Java 8
[ https://issues.apache.org/jira/browse/CODEC-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857527#comment-16857527 ] Emmanuel Bourg commented on CODEC-253: -- +1 for preserving Java 7 compatibility. OpenJDK 7 is still maintained by RedHat. Upgrading without leveraging the new language features or APIs in the public code just reduces the user base for no benefit (besides the satisfaction of using a newer version). > Upgrade to Java 8 > - > > Key: CODEC-253 > URL: https://issues.apache.org/jira/browse/CODEC-253 > Project: Commons Codec > Issue Type: Improvement >Reporter: Rob Tompkins >Assignee: Rob Tompkins >Priority: Major > Fix For: 1.13 > > > Upgrade to java 8 as the target of of the build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (COMPRESS-487) PKWARE DCL Implode support (ZIP compression method 10)
Emmanuel Bourg created COMPRESS-487:
---
Summary: PKWARE DCL Implode support (ZIP compression method 10)
Key: COMPRESS-487
URL: https://issues.apache.org/jira/browse/COMPRESS-487
Project: Commons Compress
Issue Type: New Feature
Components: Archivers, Compressors
Reporter: Emmanuel Bourg
Attachments: dclimplode-ascii-1024.zip, dclimplode-ascii-2048.zip,
dclimplode-ascii-4096.zip, dclimplode-binary-1024.zip,
dclimplode-binary-2048.zip, dclimplode-binary-4096.zip
Commons Compress doesn't yet support the implode compression algorithm
implemented in the PKWARE Data Compression Library (DCL). This algorithm can be
used in ZIP files (using the compression method 10, which differs from the
other implode compression method 6 already supported). It's also used in some
old file formats like dBASE/xBase and game files from the 90's (.mpq).
ZIP files using this compression method can be created with recent versions of
the [PKWARE ZIP Compression Utility|https://www.pkware.com/pkzip]. The syntax
looks like this:
{{pkzipc -add -dclimplode=ascii,4096 test.zip *.txt}}
The format is documented here:
https://groups.google.com/forum/#!msg/comp.compression/M5P064or93o/W1ca1-ad6kgJ
and here is the implementation in zlib:
https://github.com/madler/zlib/blob/master/contrib/blast/blast.c
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (COMPRESS-485) Reproducible Builds: keep entries order when gathering ParallelScatterZipCreator
[ https://issues.apache.org/jira/browse/COMPRESS-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834271#comment-16834271 ] Emmanuel Bourg commented on COMPRESS-485: - Well done! It might be nice to also add a test case ensuring the order is preserved. > Reproducible Builds: keep entries order when gathering > ParallelScatterZipCreator > > > Key: COMPRESS-485 > URL: https://issues.apache.org/jira/browse/COMPRESS-485 > Project: Commons Compress > Issue Type: Improvement > Components: Archivers >Affects Versions: 1.18 >Reporter: Hervé Boutemy >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > currently, zip files created using ParallelScatterZipCreator have random > order. > This is causing issues when trying to do Reproducible Builds with Maven > MNG-6276 > Studying ParallelScatterZipCreator, entries are kept sorted in memory in > futures list: instead of writing each full scatter in sequence, iterating > over futures should permit to write each zip entry in original order -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (BEANUTILS-519) setProperty fails silently on null maps
Emmanuel Bourg created BEANUTILS-519:
Summary: setProperty fails silently on null maps
Key: BEANUTILS-519
URL: https://issues.apache.org/jira/browse/BEANUTILS-519
Project: Commons BeanUtils
Issue Type: Bug
Components: Bean / Property Utils
Affects Versions: 1.9.3
Reporter: Emmanuel Bourg
Adding an element to a null map with BeanUtils.setProperty() neither result in
an automatically instantiated Map containing the specified element, nor to a
NullPointerException. The method simply fails and returns silently. If the map
isn't created on the fly an exception should be thrown at least.
Here is a test case illustrating the issue:
{code}
public class BeanUtilsTest extends TestCase {
private static class Bean {
public Map elements;
}
public void testSetPropertyWithNullMap() throws Exception {
Bean b = new Bean();
assertNull(b.elements);
BeanUtils.setProperty(b, "elements(FOO)", "BAR");
assertNotNull("Map is still null after calling
BeanUtils.setProperty()", b.elements);
assertTrue("Element not found", b.elements.containsKey("FOO"));
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (JEXL-254) Tests from IssuesTest100.java and IssuesTest200.java don't fire
[ https://issues.apache.org/jira/browse/JEXL-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg resolved JEXL-254. - Resolution: Fixed Fix Version/s: 3.2 Thank you for spotting this, it's now fixed in Git. > Tests from IssuesTest100.java and IssuesTest200.java don't fire > --- > > Key: JEXL-254 > URL: https://issues.apache.org/jira/browse/JEXL-254 > Project: Commons JEXL > Issue Type: Test >Affects Versions: 3.1 >Reporter: Dmitri Blinov >Priority: Major > Fix For: 3.2 > > > It seems that Jexl build process does not honor tests with class names not > ending with 'Test'. As an experiment I was trying to add another check to the > issue and it was ignored until I renamed IssuesTest100.java to > Issues100Test.java and IssuesTest200.java to Issues200Test.java. Luckiliy all > the tests were passed from those files after name change :) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CLI-179) Needs "standalone" options that can be used even if required options are not set
[ https://issues.apache.org/jira/browse/CLI-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092863#comment-16092863 ] Emmanuel Bourg commented on CLI-179: [~iweiss] That's only the first pass. If the parsing fails because --help and --version are missing, you catch the exception and run a second pass with the other options. > Needs "standalone" options that can be used even if required options are not > set > > > Key: CLI-179 > URL: https://issues.apache.org/jira/browse/CLI-179 > Project: Commons CLI > Issue Type: Improvement > Components: Parser >Affects Versions: 1.2 >Reporter: Joël Royer > Attachments: CLI-179.patch > > > it is currently impossible to have options like "help" or "version" if we > also have some required options. The parsing results in an error "Missing > parameters". > But for an "help" or "version" option, it would be usefull to display the > wanted information, even if required options are not set. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (NUMBERS-43) Remove "round(float)" methods?
[
https://issues.apache.org/jira/browse/NUMBERS-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048795#comment-16048795
]
Emmanuel Bourg commented on NUMBERS-43:
---
I also think we should keep the method, we aren't on a crusade to deprecate
floats in all our components anyway. floats are still there and we don't know
how people are using them.
> Remove "round(float)" methods?
> --
>
> Key: NUMBERS-43
> URL: https://issues.apache.org/jira/browse/NUMBERS-43
> Project: Commons Numbers
> Issue Type: Wish
>Reporter: Gilles
> Labels: api, float
> Fix For: 1.0
>
>
> In class {{Precision}}, there are methods for rounding {{float}} values, e.g.
> {code:java}
> public static float round(float x, int scale, int roundingMethod) { /* ... */
> }
> {code}
> Is there any use for supporting specific handling of floats (in these times
> where memory is not a scarce resources anymore)?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (JEXL-223) Apache Commons JEXL Expression Execute Command Vulnerabilitity
[ https://issues.apache.org/jira/browse/JEXL-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978258#comment-15978258 ] Emmanuel Bourg commented on JEXL-223: - I'm not sure to understand, executing untrusted code in a scripting language is dangerous, that's not really new. The same happens with any implementation of the javax.script API. > Apache Commons JEXL Expression Execute Command Vulnerabilitity > -- > > Key: JEXL-223 > URL: https://issues.apache.org/jira/browse/JEXL-223 > Project: Commons JEXL > Issue Type: Bug >Reporter: cnbird >Priority: Critical > > 0x01 Summary > Apache Commons JEXL Expression Execute Command Vulnerabilitity throught > groovy. > 0x02 POC > POC Report to Apache Security Email Address secur...@apache.org. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CONFIGURATION-258) JSON configuration
[
https://issues.apache.org/jira/browse/CONFIGURATION-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975323#comment-15975323
]
Emmanuel Bourg commented on CONFIGURATION-258:
--
Note that the org.json library can't be used because its license has a field of
use restriction (the famous "The Software shall be used for Good, not Evil"
clause).
> JSON configuration
> --
>
> Key: CONFIGURATION-258
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-258
> Project: Commons Configuration
> Issue Type: New Feature
> Components: Format
>Affects Versions: 1.3
>Reporter: Antonio López-Cerón Vivo
>Priority: Minor
> Fix For: 2.x
>
> Attachments: commons-configuration2-yaml.and.json.support.diff
>
>
> JSON is a lightweight data-interchange format
> {code}
> {"menu": {
> "id": "file",
> "value": "File",
> "popup": {
> "menuitem": [
> {"value": "New", "onclick": "CreateNewDoc()"},
> {"value": "Open", "onclick": "OpenDoc()"},
> {"value": "Close", "onclick": "CloseDoc()"}
> ]
> }
> }}
> {code}
> All references can be located at
> http://www.json.org/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (LANG-1272) Array shuffling
[
https://issues.apache.org/jira/browse/LANG-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg resolved LANG-1272.
--
Resolution: Fixed
Fix Version/s: 3.6
> Array shuffling
> ---
>
> Key: LANG-1272
> URL: https://issues.apache.org/jira/browse/LANG-1272
> Project: Commons Lang
> Issue Type: Improvement
>Reporter: Emmanuel Bourg
>Assignee: Emmanuel Bourg
>Priority: Minor
> Fix For: 3.6
>
>
> I'd like to suggest the addition of methods in ArrayUtils shuffling the
> content of an array (Objects or primitives). This would be similar to the
> {{java.util.Collections.shuffle()}} methods.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CONFIGURATION-258) JSON configuration
[
https://issues.apache.org/jira/browse/CONFIGURATION-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974935#comment-15974935
]
Emmanuel Bourg commented on CONFIGURATION-258:
--
That's up to you. A JSONConfiguration based on javax.script could be
interesting too, probably slower than a javacc parser, but performance isn't
really critical here.
> JSON configuration
> --
>
> Key: CONFIGURATION-258
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-258
> Project: Commons Configuration
> Issue Type: New Feature
> Components: Format
>Affects Versions: 1.3
>Reporter: Antonio López-Cerón Vivo
>Priority: Minor
> Fix For: 2.x
>
>
> JSON is a lightweight data-interchange format
> {code}
> {"menu": {
> "id": "file",
> "value": "File",
> "popup": {
> "menuitem": [
> {"value": "New", "onclick": "CreateNewDoc()"},
> {"value": "Open", "onclick": "OpenDoc()"},
> {"value": "Close", "onclick": "CloseDoc()"}
> ]
> }
> }}
> {code}
> All references can be located at
> http://www.json.org/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CONFIGURATION-258) JSON configuration
[
https://issues.apache.org/jira/browse/CONFIGURATION-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974720#comment-15974720
]
Emmanuel Bourg commented on CONFIGURATION-258:
--
I have no preference, if you can reuse the javacc parser that's great but
jackson is fine too. Nashorn is Java 8+ only and commons-configuration isn't
there yet.
> JSON configuration
> --
>
> Key: CONFIGURATION-258
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-258
> Project: Commons Configuration
> Issue Type: New Feature
> Components: Format
>Affects Versions: 1.3
>Reporter: Antonio López-Cerón Vivo
>Priority: Minor
> Fix For: 2.x
>
>
> JSON is a lightweight data-interchange format
> {code}
> {"menu": {
> "id": "file",
> "value": "File",
> "popup": {
> "menuitem": [
> {"value": "New", "onclick": "CreateNewDoc()"},
> {"value": "Open", "onclick": "OpenDoc()"},
> {"value": "Close", "onclick": "CloseDoc()"}
> ]
> }
> }}
> {code}
> All references can be located at
> http://www.json.org/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (CONFIGURATION-258) JSON configuration
[
https://issues.apache.org/jira/browse/CONFIGURATION-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated CONFIGURATION-258:
-
Assignee: (was: Emmanuel Bourg)
> JSON configuration
> --
>
> Key: CONFIGURATION-258
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-258
> Project: Commons Configuration
> Issue Type: New Feature
> Components: Format
>Affects Versions: 1.3
>Reporter: Antonio López-Cerón Vivo
>Priority: Minor
> Fix For: 2.x
>
>
> JSON is a lightweight data-interchange format
> {code}
> {"menu": {
> "id": "file",
> "value": "File",
> "popup": {
> "menuitem": [
> {"value": "New", "onclick": "CreateNewDoc()"},
> {"value": "Open", "onclick": "OpenDoc()"},
> {"value": "Close", "onclick": "CloseDoc()"}
> ]
> }
> }}
> {code}
> All references can be located at
> http://www.json.org/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CONFIGURATION-258) JSON configuration
[
https://issues.apache.org/jira/browse/CONFIGURATION-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974672#comment-15974672
]
Emmanuel Bourg commented on CONFIGURATION-258:
--
It was on the experimental branch for configuration2:
http://svn.apache.org/repos/asf/commons/proper/configuration/branches/configuration2_experimental/src/main/java/org/apache/commons/configuration2/json/
> JSON configuration
> --
>
> Key: CONFIGURATION-258
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-258
> Project: Commons Configuration
> Issue Type: New Feature
> Components: Format
>Affects Versions: 1.3
>Reporter: Antonio López-Cerón Vivo
>Assignee: Emmanuel Bourg
>Priority: Minor
> Fix For: 2.x
>
>
> JSON is a lightweight data-interchange format
> {code}
> {"menu": {
> "id": "file",
> "value": "File",
> "popup": {
> "menuitem": [
> {"value": "New", "onclick": "CreateNewDoc()"},
> {"value": "Open", "onclick": "OpenDoc()"},
> {"value": "Close", "onclick": "CloseDoc()"}
> ]
> }
> }}
> {code}
> All references can be located at
> http://www.json.org/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (LANG-1272) Array shuffling
[
https://issues.apache.org/jira/browse/LANG-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated LANG-1272:
-
Assignee: Emmanuel Bourg
> Array shuffling
> ---
>
> Key: LANG-1272
> URL: https://issues.apache.org/jira/browse/LANG-1272
> Project: Commons Lang
> Issue Type: Improvement
>Reporter: Emmanuel Bourg
>Assignee: Emmanuel Bourg
>Priority: Minor
>
> I'd like to suggest the addition of methods in ArrayUtils shuffling the
> content of an array (Objects or primitives). This would be similar to the
> {{java.util.Collections.shuffle()}} methods.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (CONFIGURATION-656) YAML Configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973556#comment-15973556 ] Emmanuel Bourg commented on CONFIGURATION-656: -- We could have both: an uber jar (commons-configuration2) and smaller modules (commons-configuration2-core, commons-configuration2-json, commons-configuration2-yaml, etc). > YAML Configuration > -- > > Key: CONFIGURATION-656 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-656 > Project: Commons Configuration > Issue Type: New Feature > Components: Format >Reporter: Gary Gregory > > Like the missing JSON Configuration, we really should also support YAML. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (CONFIGURATION-656) YAML Configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973495#comment-15973495 ] Emmanuel Bourg commented on CONFIGURATION-656: -- Using an external library is fine I think. We could probably consider moving the extra configuration formats into their own modules to avoid overloading the main module with rarely used dependencies. > YAML Configuration > -- > > Key: CONFIGURATION-656 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-656 > Project: Commons Configuration > Issue Type: New Feature > Components: Format >Reporter: Gary Gregory > > Like the missing JSON Configuration, we really should also support YAML. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (JEXL-220) Release 3.1 to Maven Repository
[ https://issues.apache.org/jira/browse/JEXL-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg resolved JEXL-220. - Resolution: Fixed > Release 3.1 to Maven Repository > --- > > Key: JEXL-220 > URL: https://issues.apache.org/jira/browse/JEXL-220 > Project: Commons JEXL > Issue Type: Wish >Affects Versions: 3.1 >Reporter: Doug Whitehead >Priority: Minor > Fix For: 3.1 > > > Any chance version 3.1 is scheduled for a release to the Maven Repository any > time soon? Seems like there are plenty of improvements and bug fixes to > warrant a release, and also -- last release was a year go at this point :) > https://mvnrepository.com/artifact/org.apache.commons/commons-jexl3 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (TEXT-57) Formatting numbers
[ https://issues.apache.org/jira/browse/TEXT-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813363#comment-15813363 ] Emmanuel Bourg commented on TEXT-57: I don't think matrix formatting belongs to [text]. This is clearly [math] stuff. > Formatting numbers > -- > > Key: TEXT-57 > URL: https://issues.apache.org/jira/browse/TEXT-57 > Project: Commons Text > Issue Type: Wish >Reporter: Gilles >Priority: Minor > Labels: api, scope > Fix For: 1.x > > > "Commons Math" contains formatting classes whose purpose are to beautify the > printout of such objects as "complex number" and "matrix" instances. > I suggest that such functionality would be a better fit for "Commons Text". > Rationale is that it is an endeavour unto itself rather than something which > other components can easily implement themselves, aside from their "core > business". > As an example, in "Commons Math", there was an issue in that fixed precision > was maintained in numbers close to 0, leading to meaningless error messages. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEXT-34) Add class to generate random strings
[
https://issues.apache.org/jira/browse/TEXT-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765295#comment-15765295
]
Emmanuel Bourg commented on TEXT-34:
I don't think TEXT should depend on RNG. TEXT can use java.util.Random, and the
RNG implementations will be usable through JDKRandomBridge.
> Add class to generate random strings
>
>
> Key: TEXT-34
> URL: https://issues.apache.org/jira/browse/TEXT-34
> Project: Commons Text
> Issue Type: New Feature
>Reporter: Duncan Jones
>Assignee: Duncan Jones
>
> The {{RandomStringUtils}} class will be deprecated in Commons Lang and reborn
> in Commons Text.
> Because the original class has some complicated parameters and potentially
> unnecessary capabilities, I'll simplify as I move it across. I'll also ensure
> the class plays nicely with Unicode characters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (TEXT-34) Add class to generate random strings
[
https://issues.apache.org/jira/browse/TEXT-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764025#comment-15764025
]
Emmanuel Bourg edited comment on TEXT-34 at 12/20/16 11:53 AM:
---
{quote}
Did you notice the fields I defined?
{quote}
I didn't, sorry. The extra methods would still be useful though. Most people
discover the capabilities of a class by looking at the auto-completion
suggestions from the IDE. In this case the {{withDigits()}} method would pop-up
immediately and look as a more obvious choice than {{filteredBy()}}.
{quote}
Nothing prevents a custom filter from saving the characters seen so far
{quote}
Good point, the interface is good as-is then (well, until we use a parallel
string generation method ;) )
was (Author: ebourg):
{quote}
Did you notice the fields I defined?
{quote}
I didn't, sorry. The extra methods would still be useful though. Most people
discover the capabilities of a class by looking at the auto-completion
suggestions from the IDE. In this case the {{withDigits()}} method would pop-up
immediately and look as a more obvious choice than {{filteredBy()}}.
{quote}
{quote}
{quote}
{quote}
> Add class to generate random strings
>
>
> Key: TEXT-34
> URL: https://issues.apache.org/jira/browse/TEXT-34
> Project: Commons Text
> Issue Type: New Feature
>Reporter: Duncan Jones
>Assignee: Duncan Jones
>
> The {{RandomStringUtils}} class will be deprecated in Commons Lang and reborn
> in Commons Text.
> Because the original class has some complicated parameters and potentially
> unnecessary capabilities, I'll simplify as I move it across. I'll also ensure
> the class plays nicely with Unicode characters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TEXT-34) Add class to generate random strings
[
https://issues.apache.org/jira/browse/TEXT-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764025#comment-15764025
]
Emmanuel Bourg commented on TEXT-34:
{quote}
Did you notice the fields I defined?
{quote}
I didn't, sorry. The extra methods would still be useful though. Most people
discover the capabilities of a class by looking at the auto-completion
suggestions from the IDE. In this case the {{withDigits()}} method would pop-up
immediately and look as a more obvious choice than {{filteredBy()}}.
{quote}
{quote}
{quote}
{quote}
> Add class to generate random strings
>
>
> Key: TEXT-34
> URL: https://issues.apache.org/jira/browse/TEXT-34
> Project: Commons Text
> Issue Type: New Feature
>Reporter: Duncan Jones
>Assignee: Duncan Jones
>
> The {{RandomStringUtils}} class will be deprecated in Commons Lang and reborn
> in Commons Text.
> Because the original class has some complicated parameters and potentially
> unnecessary capabilities, I'll simplify as I move it across. I'll also ensure
> the class plays nicely with Unicode characters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TEXT-34) Add class to generate random strings
[
https://issues.apache.org/jira/browse/TEXT-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15762658#comment-15762658
]
Emmanuel Bourg commented on TEXT-34:
Thank you for the example, I didn't realize the filter could be used this way.
I'd suggest adding more methods like {{withRange(char, char)}},
{{withDigits()}} or {{withLetter()}} to make common cases easier.
Regarding the filter, I wonder if it would be worth making the pending string
accessible to the test method. A test could thus be based on the previous
characters, and it would be possible to write a test avoiding the repetitions
characters.
> Add class to generate random strings
>
>
> Key: TEXT-34
> URL: https://issues.apache.org/jira/browse/TEXT-34
> Project: Commons Text
> Issue Type: New Feature
>Reporter: Duncan Jones
>Assignee: Duncan Jones
>
> The {{RandomStringUtils}} class will be deprecated in Commons Lang and reborn
> in Commons Text.
> Because the original class has some complicated parameters and potentially
> unnecessary capabilities, I'll simplify as I move it across. I'll also ensure
> the class plays nicely with Unicode characters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TEXT-34) Add class to generate random strings
[
https://issues.apache.org/jira/browse/TEXT-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761792#comment-15761792
]
Emmanuel Bourg commented on TEXT-34:
The builder pattern is a good idea, however the implementation will need a bit
more to be feature equivalent with {{RandomStringUtils}}. Being able to select
the characters used is important and simply allowing a range of characters
isn't enough. For example I use {{RandomStringUtils}} to generate license codes
and I use upper case latin letters, excepted those that could be confused with
a digit (O, I).
> Add class to generate random strings
>
>
> Key: TEXT-34
> URL: https://issues.apache.org/jira/browse/TEXT-34
> Project: Commons Text
> Issue Type: New Feature
>Reporter: Duncan Jones
>Assignee: Duncan Jones
>
> The {{RandomStringUtils}} class will be deprecated in Commons Lang and reborn
> in Commons Text.
> Because the original class has some complicated parameters and potentially
> unnecessary capabilities, I'll simplify as I move it across. I'll also ensure
> the class plays nicely with Unicode characters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (LANG-1110) Implement HashSetvBitSetTest using JMH
[ https://issues.apache.org/jira/browse/LANG-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15754476#comment-15754476 ] Emmanuel Bourg commented on LANG-1110: -- JMH is already used with commons-csv and commons-rng, I suggest reusing the same set up. If we have more components adding JMH benchmarks we should probably put the common configuration in the parent pom. > Implement HashSetvBitSetTest using JMH > -- > > Key: LANG-1110 > URL: https://issues.apache.org/jira/browse/LANG-1110 > Project: Commons Lang > Issue Type: Test > Components: lang.* >Reporter: Benedikt Ritter > Fix For: Patch Needed, 3.6 > > Attachments: HashSetvBitSetTest.java > > > HashSetvBitSetTest currently writes to Std out, which is bad practice for > unit tests. Since HashSetvBitSetTest is really a performance test and not a > unit test, we should reimplement it using OpenJMH. The results could then be > published on our website. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (LANG-1298) Add methods to RandomUtils that accept source of randomness
[
https://issues.apache.org/jira/browse/LANG-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752848#comment-15752848
]
Emmanuel Bourg commented on LANG-1298:
--
+1, the class could remain as a convenience, but I don't think it should be
further refined.
> Add methods to RandomUtils that accept source of randomness
> ---
>
> Key: LANG-1298
> URL: https://issues.apache.org/jira/browse/LANG-1298
> Project: Commons Lang
> Issue Type: Improvement
> Components: lang.*
>Reporter: Duncan Jones
>Priority: Minor
>
> We should add overloads to {{RandomUtils}} that accept a {{Random}} instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (RNG-16) Linear congruential generators
[ https://issues.apache.org/jira/browse/RNG-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated RNG-16: -- Assignee: (was: Emmanuel Bourg) > Linear congruential generators > -- > > Key: RNG-16 > URL: https://issues.apache.org/jira/browse/RNG-16 > Project: Commons RNG > Issue Type: Wish >Reporter: Emmanuel Bourg >Priority: Minor > > This is a RFE for implementing linear congruential generators: > https://en.wikipedia.org/wiki/Linear_congruential_generator > This type of random generator is often used in language runtimes (Borland C, > GCC, Delphi, VB and even Java). Preconfigured generators using the same > parameters as these languages would be convenient for reproducing the same > number sequences in Java. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (RNG-19) System generator (/dev/random)
[ https://issues.apache.org/jira/browse/RNG-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg reopened RNG-19: --- I disagree. > System generator (/dev/random) > -- > > Key: RNG-19 > URL: https://issues.apache.org/jira/browse/RNG-19 > Project: Commons RNG > Issue Type: Wish >Reporter: Emmanuel Bourg >Priority: Minor > > Commons RNG could include a random number generator based on the output of > /dev/random or /dev/urandom on Unix systems. > Commons Crypto has an implementation that could be used as a starting point: > https://github.com/apache/commons-crypto/blob/master/src/main/java/org/apache/commons/crypto/random/OsCryptoRandom.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MATH-1389) Runtime Improvement for getSubMatrix in Array2DRowRealMatrix
[ https://issues.apache.org/jira/browse/MATH-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg resolved MATH-1389. -- Resolution: Fixed Fix Version/s: 3.7 4.0 I applied the patch on the 4.x and 3.x branches (with a minor optimization for the instantiation of the sub matrix). Thank you very much Christoph! > Runtime Improvement for getSubMatrix in Array2DRowRealMatrix > > > Key: MATH-1389 > URL: https://issues.apache.org/jira/browse/MATH-1389 > Project: Commons Math > Issue Type: Improvement >Reporter: Christoph Dibak >Priority: Trivial > Fix For: 4.0, 3.7 > > Attachments: 0001-faster-getSubMatrix-for-Array2DRowRealMatrix.patch, > MatrixBenchmark.java, RuntimeTestGetSubMatrix.java > > > Using System.arraycopy() for creating sub-matrices in the getSubMatrix() > method of Array2DRowRealMatrix improves the runtime. Tested for a matrix > with dimension 50x50, the execution time was 16 times faster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MATH-1389) Runtime Improvement for getSubMatrix in Array2DRowRealMatrix
[ https://issues.apache.org/jira/browse/MATH-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562975#comment-15562975 ] Emmanuel Bourg commented on MATH-1389: -- I think it's worth applying too, optimizing the cold scenario is interesting and it seems slightly better even when the JIT kicked in. > Runtime Improvement for getSubMatrix in Array2DRowRealMatrix > > > Key: MATH-1389 > URL: https://issues.apache.org/jira/browse/MATH-1389 > Project: Commons Math > Issue Type: Improvement >Reporter: Christoph Dibak >Priority: Trivial > Attachments: 0001-faster-getSubMatrix-for-Array2DRowRealMatrix.patch, > MatrixBenchmark.java, RuntimeTestGetSubMatrix.java > > > Using System.arraycopy() for creating sub-matrices in the getSubMatrix() > method of Array2DRowRealMatrix improves the runtime. Tested for a matrix > with dimension 50x50, the execution time was 16 times faster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MATH-1389) Runtime Improvement for getSubMatrix in Array2DRowRealMatrix
[
https://issues.apache.org/jira/browse/MATH-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562663#comment-15562663
]
Emmanuel Bourg commented on MATH-1389:
--
By "warmed up" I mean the JVM has compiled the method to native code and
probably figured out how to optimize it properly.
Out of curiosity, could you try running the JMH benchmark on your computer?
Just copy MatrixBenchmark.java to
{{src/test/main/java/org/apache/commons/math4}} and then run {{mvn clean test
-Pbenchmark}}
> Runtime Improvement for getSubMatrix in Array2DRowRealMatrix
>
>
> Key: MATH-1389
> URL: https://issues.apache.org/jira/browse/MATH-1389
> Project: Commons Math
> Issue Type: Improvement
>Reporter: Christoph Dibak
>Priority: Trivial
> Attachments: 0001-faster-getSubMatrix-for-Array2DRowRealMatrix.patch,
> MatrixBenchmark.java, RuntimeTestGetSubMatrix.java
>
>
> Using System.arraycopy() for creating sub-matrices in the getSubMatrix()
> method of Array2DRowRealMatrix improves the runtime. Tested for a matrix
> with dimension 50x50, the execution time was 16 times faster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MATH-1389) Runtime Improvement for getSubMatrix in Array2DRowRealMatrix
[ https://issues.apache.org/jira/browse/MATH-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg updated MATH-1389: - Attachment: MatrixBenchmark.java > Runtime Improvement for getSubMatrix in Array2DRowRealMatrix > > > Key: MATH-1389 > URL: https://issues.apache.org/jira/browse/MATH-1389 > Project: Commons Math > Issue Type: Improvement >Reporter: Christoph Dibak >Priority: Trivial > Attachments: 0001-faster-getSubMatrix-for-Array2DRowRealMatrix.patch, > MatrixBenchmark.java, RuntimeTestGetSubMatrix.java > > > Using System.arraycopy() for creating sub-matrices in the getSubMatrix() > method of Array2DRowRealMatrix improves the runtime. Tested for a matrix > with dimension 50x50, the execution time was 16 times faster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MATH-1389) Runtime Improvement for getSubMatrix in Array2DRowRealMatrix
[
https://issues.apache.org/jira/browse/MATH-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562539#comment-15562539
]
Emmanuel Bourg commented on MATH-1389:
--
Thank you for the benchmark Christoph. I turned it into a JMH benchmark and the
execution time was very similar once the JVM has warmed up (I tested on a Core
2 Duo E8400 3GHz with Java 8u91 on Windows).
With the current Commons Math master I got:
{code}
Benchmark (size) Mode Cnt ScoreError Units
MatrixBenchmark.submatrix 1 avgt5 118,9142,302 us/op
MatrixBenchmark.submatrix 2 avgt5 147,0292,388 us/op
MatrixBenchmark.submatrix 5 avgt5 244,7222,705 us/op
MatrixBenchmark.submatrix 10 avgt5 466,4654,090 us/op
MatrixBenchmark.submatrix 20 avgt5 1058,738 10,147 us/op
MatrixBenchmark.submatrix 30 avgt5 2450,626 25,935 us/op
MatrixBenchmark.submatrix 40 avgt5 4121,504 35,984 us/op
{code}
And with your patch:
{code}
Benchmark (size) Mode Cnt ScoreError Units
MatrixBenchmark.submatrix 1 avgt5 112,9291,169 us/op
MatrixBenchmark.submatrix 2 avgt5 146,7970,968 us/op
MatrixBenchmark.submatrix 5 avgt5 259,948 73,247 us/op
MatrixBenchmark.submatrix 10 avgt5 468,226 48,748 us/op
MatrixBenchmark.submatrix 20 avgt5 1087,570 22,342 us/op
MatrixBenchmark.submatrix 30 avgt5 2301,979 20,295 us/op
MatrixBenchmark.submatrix 40 avgt5 4043,559 62,592 us/op
{code}
> Runtime Improvement for getSubMatrix in Array2DRowRealMatrix
>
>
> Key: MATH-1389
> URL: https://issues.apache.org/jira/browse/MATH-1389
> Project: Commons Math
> Issue Type: Improvement
>Reporter: Christoph Dibak
>Priority: Trivial
> Attachments: 0001-faster-getSubMatrix-for-Array2DRowRealMatrix.patch,
> RuntimeTestGetSubMatrix.java
>
>
> Using System.arraycopy() for creating sub-matrices in the getSubMatrix()
> method of Array2DRowRealMatrix improves the runtime. Tested for a matrix
> with dimension 50x50, the execution time was 16 times faster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CSV-198) Cannot parse file by header with custom delimiter on Java 1.6
[
https://issues.apache.org/jira/browse/CSV-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556117#comment-15556117
]
Emmanuel Bourg commented on CSV-198:
Tomcat has its own UTF-8 decoder due to bugs in the JDK, I wonder if you've hit
one of those bugs with your input file.
https://github.com/apache/tomcat85/blob/TOMCAT_8_5_6/java/org/apache/tomcat/util/buf/Utf8Decoder.java
> Cannot parse file by header with custom delimiter on Java 1.6
> -
>
> Key: CSV-198
> URL: https://issues.apache.org/jira/browse/CSV-198
> Project: Commons CSV
> Issue Type: Bug
> Components: Parser
>Affects Versions: 1.4
> Environment: Java 1.6, Windows
>Reporter: Tadhg Pearson
>
> Reading a CSV file from the parser using the header line results in
> "IllegalArgumentException: Mappng for not found" - even when the
> column exists in the file. In this case, we are using Java 1.6 and the file
> uses the ^ symbol to delimit columns. This works correctly in Java 7 & Java 8.
> The code required to reproduce the issue is below. You can find the
> optd_por_public.csv file referenced at
> https://raw.githubusercontent.com/opentraveldata/opentraveldata/master/opentraveldata/optd_por_public.csv
> It will need to be on the classpath to run the unit test. Hope that helps,
> Tadhg
> You should get the following output
> --
> java.lang.IllegalArgumentException: Mapping for location_type not found,
> expected one of
> [iata_code,icao_code,faa_code,is_geonames,geoname_id,envelope_id,name,asciiname,latitude,longitude,fclass,fcode,page_rank,date_from,date_until,comment,country_code,cc2,country_name,continent_name,adm1_code,adm1_name_utf,adm1_name_ascii,adm2_code,adm2_name_utf,adm2_name_ascii,adm3_code,adm4_code,population,elevation,gtopo30,timezone,gmt_offset,dst_offset,raw_offset,moddate,city_code_list,city_name_list,city_detail_list,tvl_por_list,state_code,location_type,wiki_link,alt_name_section,wac,wac_name]
> at org.apache.commons.csv.CSVRecord.get(CSVRecord.java:104)
> at com.amadeus.ui.CSVRecordTest.test(CSVRecordTest.java:31)
>
> import static org.junit.Assert.assertNotNull;
> import java.io.IOException;
> import java.io.InputStream;
> import java.io.InputStreamReader;
> import java.io.UnsupportedEncodingException;
> import org.apache.commons.csv.CSVFormat;
> import org.apache.commons.csv.CSVParser;
> import org.apache.commons.csv.CSVRecord;
> import org.junit.Test;
> public class CSVRecordTest {
> private static final CSVFormat CSV_FORMAT =
> CSVFormat.EXCEL.withDelimiter('^').withFirstRecordAsHeader();
>
> @Test
> public void test() throws UnsupportedEncodingException, IOException {
> InputStream pointsOfReference =
> getClass().getResourceAsStream("/optd_por_public.csv");
> CSVParser parser = CSV_FORMAT.parse(new
> InputStreamReader(pointsOfReference, "UTF-8"));
> for (CSVRecord record : parser) {
> String locationType = record.get("location_type");
> assertNotNull(locationType);
> }
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CSV-196) Store the info of whether a field is enclosed by quotes
[ https://issues.apache.org/jira/browse/CSV-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556070#comment-15556070 ] Emmanuel Bourg commented on CSV-196: But the parser reads characters, not bytes. That doesn't seem very reliable, and I suspect there are other cases where the parser ignores input characters (such as spaces between a delimiter and a quote). Flagging the quoted fields is likely to be insufficient. > Store the info of whether a field is enclosed by quotes > --- > > Key: CSV-196 > URL: https://issues.apache.org/jira/browse/CSV-196 > Project: Commons CSV > Issue Type: Improvement > Components: Parser >Affects Versions: 1.4 >Reporter: Matt Sun > Labels: easyfix, features, patch > Fix For: Patch Needed > > Original Estimate: 48h > Remaining Estimate: 48h > > It will be good to have CSVParser class to store the info of whether a field > was enclosed by quotes in the original source file. > For example, for this data sample: > A, B, C > a1, "b1", c1 > CSVParser gives us record a1, b1, c1, which is helpful because it parsed > double quotes, but we also lost the information of original data at the same > time. We can't tell from the CSVRecord returned whether the original data is > enclosed by double quotes or not. > In our use case, we are integrating Apache Hadoop APIs with Commons CSV. CSV > is one kind of input of Hadoop Jobs, which should support splitting input > data. To accurately split a CSV file into pieces, we need to count the bytes > of data CSVParser actually read. CSVParser doesn't have accurate information > of whether a field was enclosed by quotes, neither does it store raw data of > the original source. Downstream users of commons CSVParser is not able to get > those info. > To suggest a fix: Extend the token/CSVRecord to have a boolean field > indicating whether the column was enclosed by quotes. While Lexer is doing > getNextToken, set the flag if a field is encapsulated and successfully parsed. > I find another issue reported with similar request, but it was marked as > resolved: [CSV91] > https://issues.apache.org/jira/browse/CSV-91?jql=project%20%3D%20CSV%20AND%20text%20~%20%22with%20quotes%22 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CSV-198) Cannot parse file by header with custom delimiter on Java 1.6
[
https://issues.apache.org/jira/browse/CSV-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15554432#comment-15554432
]
Emmanuel Bourg commented on CSV-198:
I suspect this could be a UTF-8 decoding bug at the Java level, if so I'm not
sure we can fix it.
> Cannot parse file by header with custom delimiter on Java 1.6
> -
>
> Key: CSV-198
> URL: https://issues.apache.org/jira/browse/CSV-198
> Project: Commons CSV
> Issue Type: Bug
> Components: Parser
>Affects Versions: 1.4
> Environment: Java 1.6, Windows
>Reporter: Tadhg Pearson
>
> Reading a CSV file from the parser using the header line results in
> "IllegalArgumentException: Mappng for not found" - even when the
> column exists in the file. In this case, we are using Java 1.6 and the file
> uses the ^ symbol to delimit columns. This works correctly in Java 7 & Java 8.
> The code required to reproduce the issue is below. You can find the
> optd_por_public.csv file referenced at
> https://raw.githubusercontent.com/opentraveldata/opentraveldata/master/opentraveldata/optd_por_public.csv
> It will need to be on the classpath to run the unit test. Hope that helps,
> Tadhg
> You should get the following output
> --
> java.lang.IllegalArgumentException: Mapping for location_type not found,
> expected one of
> [iata_code,icao_code,faa_code,is_geonames,geoname_id,envelope_id,name,asciiname,latitude,longitude,fclass,fcode,page_rank,date_from,date_until,comment,country_code,cc2,country_name,continent_name,adm1_code,adm1_name_utf,adm1_name_ascii,adm2_code,adm2_name_utf,adm2_name_ascii,adm3_code,adm4_code,population,elevation,gtopo30,timezone,gmt_offset,dst_offset,raw_offset,moddate,city_code_list,city_name_list,city_detail_list,tvl_por_list,state_code,location_type,wiki_link,alt_name_section,wac,wac_name]
> at org.apache.commons.csv.CSVRecord.get(CSVRecord.java:104)
> at com.amadeus.ui.CSVRecordTest.test(CSVRecordTest.java:31)
>
> import static org.junit.Assert.assertNotNull;
> import java.io.IOException;
> import java.io.InputStream;
> import java.io.InputStreamReader;
> import java.io.UnsupportedEncodingException;
> import org.apache.commons.csv.CSVFormat;
> import org.apache.commons.csv.CSVParser;
> import org.apache.commons.csv.CSVRecord;
> import org.junit.Test;
> public class CSVRecordTest {
> private static final CSVFormat CSV_FORMAT =
> CSVFormat.EXCEL.withDelimiter('^').withFirstRecordAsHeader();
>
> @Test
> public void test() throws UnsupportedEncodingException, IOException {
> InputStream pointsOfReference =
> getClass().getResourceAsStream("/optd_por_public.csv");
> CSVParser parser = CSV_FORMAT.parse(new
> InputStreamReader(pointsOfReference, "UTF-8"));
> for (CSVRecord record : parser) {
> String locationType = record.get("location_type");
> assertNotNull(locationType);
> }
> }
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CSV-196) Store the info of whether a field is enclosed by quotes
[ https://issues.apache.org/jira/browse/CSV-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15554422#comment-15554422 ] Emmanuel Bourg commented on CSV-196: Do I understand correctly that you need this info only for counting the number of bytes read? > Store the info of whether a field is enclosed by quotes > --- > > Key: CSV-196 > URL: https://issues.apache.org/jira/browse/CSV-196 > Project: Commons CSV > Issue Type: Improvement > Components: Parser >Affects Versions: 1.4 >Reporter: Matt Sun > Labels: easyfix, features, patch > Fix For: Patch Needed > > Original Estimate: 48h > Remaining Estimate: 48h > > It will be good to have CSVParser class to store the info of whether a field > was enclosed by quotes in the original source file. > For example, for this data sample: > A, B, C > a1, "b1", c1 > CSVParser gives us record a1, b1, c1, which is helpful because it parsed > double quotes, but we also lost the information of original data at the same > time. We can't tell from the CSVRecord returned whether the original data is > enclosed by double quotes or not. > In our use case, we are integrating Apache Hadoop APIs with Commons CSV. CSV > is one kind of input of Hadoop Jobs, which should support splitting input > data. To accurately split a CSV file into pieces, we need to count the bytes > of data CSVParser actually read. CSVParser doesn't have accurate information > of whether a field was enclosed by quotes, neither does it store raw data of > the original source. Downstream users of commons CSVParser is not able to get > those info. > To suggest a fix: Extend the token/CSVRecord to have a boolean field > indicating whether the column was enclosed by quotes. While Lexer is doing > getNextToken, set the flag if a field is encapsulated and successfully parsed. > I find another issue reported with similar request, but it was marked as > resolved: [CSV91] > https://issues.apache.org/jira/browse/CSV-91?jql=project%20%3D%20CSV%20AND%20text%20~%20%22with%20quotes%22 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CSV-199) CSVFormat option to defend against CSV Excel Macro Injection (CEMI) attacks
[
https://issues.apache.org/jira/browse/CSV-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15554413#comment-15554413
]
Emmanuel Bourg commented on CSV-199:
Hi Phil, thank you for the suggestion. I'm not convinced commons-csv should
take the responsibility of cleaning the input. This cleaning seems only
relevant if the file is then loaded by Excel, but here the file is actually
processed by a Java application. Also the EXCEL format is just a formatting
convention, formulas could be added to any format and I don't think we want to
end with MYSQL_WITHOUT_FORMULAS, DEFAULT_WITHOUT_FORMULAS, etc.
> CSVFormat option to defend against CSV Excel Macro Injection (CEMI) attacks
> ---
>
> Key: CSV-199
> URL: https://issues.apache.org/jira/browse/CSV-199
> Project: Commons CSV
> Issue Type: New Feature
> Components: Printer
>Affects Versions: 1.4
>Reporter: Phil Varner
>
> A common use for Commons CSV is to export user-generated data for analysis in
> spreadsheet software like Excel. One attack against this usage is for a user
> to create data that appears as a formula to Excel, such that excel executes
> it. For example, a simple non-malicious example of this is a u CSV file like:
> {code}
> Name,Email,Favorite Color
> Aaron Aaronson,a...@example.com,=1+1
> {code}
> When opened, Excel will execute the macro and display "2". A malicious
> example could, for example, use "=cmd|' /C calc'!A0", causing a command
> prompt to be opened.
> This can be exploited with values starting with =, +, -, or .
> This feature would add a flag to CSVFormat called "escapeFormulas" that would
> defend against creating vulnerable CSV files like this by prepending a
> single-quote to any CSV column value starting with the four aforementioned
> characters. Also added would be a predefined format EXCEL_WITHOUT_FORMULAS
> that could be used for safely exporting data that was not intended to contain
> formulas.
> I believe it is important to add this as a feature to CSVFormat rather than
> relying on users to manually escape formulas because many users do not know
> about this security vulnerability, but would prefer to defend against it if
> aware.
> More information:
> https://www.owasp.org/index.php/CSV_Excel_Macro_Injection
> https://hackerone.com/reports/72785
> http://www.contextis.com/resources/blog/comma-separated-vulnerabilities/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IMAGING-188) ICNS Image Parser: Support for large Icons (ic07, ic08, ic09, ic10 [128px, 256px, 512px, 1024px])
[
https://issues.apache.org/jira/browse/IMAGING-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15529340#comment-15529340
]
Emmanuel Bourg commented on IMAGING-188:
Hi marco, thank you for the suggestion. If you'd like to contribute some code
you can either attach a patch to this ticket (ideally with a test case) or
create a pull request on GitHub: https://github.com/apache/commons-imaging
> ICNS Image Parser: Support for large Icons (ic07, ic08, ic09, ic10 [128px,
> 256px, 512px, 1024px])
> -
>
> Key: IMAGING-188
> URL: https://issues.apache.org/jira/browse/IMAGING-188
> Project: Commons Imaging
> Issue Type: New Feature
>Affects Versions: 1.0
> Environment: OS X
>Reporter: Marco Wagner
>
> I needed larger icons of icns files, than currently extracted with the Apache
> Commons Imaging ICNS Image Parser/ICNS Decoder.
> So I edited the Source Code:
> In case an icns element is a PNG (depends on 0-4th byte [header]),
> the bytes can be put in a ByteArrayInputStream and then read by ImageIO.read,
> that returns the BufferedImage needed.
> Then it can be added to the list of List in
> IcnsDecoder#decodeAllImages().
> InputStream in = new ByteArrayInputStream(imageData);
> BufferedImage image = ImageIO.read(in);
> To the enum IcnsType I added:
> ICNS_256x256_32BIT_ARGB_IMAGE("ic08", 256, 256, 32, false),
> ICNS_512x512_32BIT_ARGB_IMAGE("ic09", 512, 512, 32, false),
> ICNS_1024x1024_32BIT_ARGB_IMAGE("ic10", 1024, 1024, 32, false);
> https://en.wikipedia.org/wiki/Apple_Icon_Image_format
> No need for Rle24Compression.decompress() or decode32BPPImage().
> I can upload the code somewhere, please tell me how to do.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (RNG-16) Linear congruential generators
[ https://issues.apache.org/jira/browse/RNG-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg reassigned RNG-16: - Assignee: Emmanuel Bourg > Linear congruential generators > -- > > Key: RNG-16 > URL: https://issues.apache.org/jira/browse/RNG-16 > Project: Commons RNG > Issue Type: Wish >Reporter: Emmanuel Bourg >Assignee: Emmanuel Bourg >Priority: Minor > > This is a RFE for implementing linear congruential generators: > https://en.wikipedia.org/wiki/Linear_congruential_generator > This type of random generator is often used in language runtimes (Borland C, > GCC, Delphi, VB and even Java). Preconfigured generators using the same > parameters as these languages would be convenient for reproducing the same > number sequences in Java. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (LANG-1272) Array shuffling
Emmanuel Bourg created LANG-1272:
Summary: Array shuffling
Key: LANG-1272
URL: https://issues.apache.org/jira/browse/LANG-1272
Project: Commons Lang
Issue Type: Improvement
Reporter: Emmanuel Bourg
Priority: Minor
I'd like to suggest the addition of methods in ArrayUtils shuffling the content
of an array (Objects or primitives). This would be similar to the
{{java.util.Collections.shuffle()}} methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (RNG-19) System generator (/dev/random)
[ https://issues.apache.org/jira/browse/RNG-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15523627#comment-15523627 ] Emmanuel Bourg commented on RNG-19: --- bq. Dealing with OS files (the management it entails cannot be performed through the intended API) With the current API the actual file used can be specified by a String parameter passed to RandomSource.create() (either /dev/random or /dev/urandom). bq. Save/restore (what is the state of "/dev/random"?) This generator isn't deterministic, there is no state. The save/restore methods will just throw an exception. bq. Portability (or more exactly non-portability) This is for UNIX systems only, but there is nothing wrong with that. > System generator (/dev/random) > -- > > Key: RNG-19 > URL: https://issues.apache.org/jira/browse/RNG-19 > Project: Commons RNG > Issue Type: Wish >Reporter: Emmanuel Bourg >Priority: Minor > > Commons RNG could include a random number generator based on the output of > /dev/random or /dev/urandom on Unix systems. > Commons Crypto has an implementation that could be used as a starting point: > https://github.com/apache/commons-crypto/blob/master/src/main/java/org/apache/commons/crypto/random/OsCryptoRandom.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RNG-19) System generator (/dev/random)
[ https://issues.apache.org/jira/browse/RNG-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15523136#comment-15523136 ] Emmanuel Bourg commented on RNG-19: --- bq. Commons RNG provides implementations of pseudo-random numbers generators I take this as a description of the RC2 content, not a strict limitation of the project scope. bq. There will be practical problems when assuming that the API can be an interface to external implementations. What kind of problems? bq. Commons RNG, as a component, should not go down the CM path. This is unlikely, the scope of random number generators is much more limited than the whole field of math algorithms. > System generator (/dev/random) > -- > > Key: RNG-19 > URL: https://issues.apache.org/jira/browse/RNG-19 > Project: Commons RNG > Issue Type: Wish >Reporter: Emmanuel Bourg >Priority: Minor > > Commons RNG could include a random number generator based on the output of > /dev/random or /dev/urandom on Unix systems. > Commons Crypto has an implementation that could be used as a starting point: > https://github.com/apache/commons-crypto/blob/master/src/main/java/org/apache/commons/crypto/random/OsCryptoRandom.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RNG-19) System generator (/dev/random)
[ https://issues.apache.org/jira/browse/RNG-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15523005#comment-15523005 ] Emmanuel Bourg commented on RNG-19: --- I agree it would have been out of scope if the RNG classes were in Commons Math. But in a component dedicated to random numbers generation I think it fits well. > System generator (/dev/random) > -- > > Key: RNG-19 > URL: https://issues.apache.org/jira/browse/RNG-19 > Project: Commons RNG > Issue Type: Wish >Reporter: Emmanuel Bourg >Priority: Minor > > Commons RNG could include a random number generator based on the output of > /dev/random or /dev/urandom on Unix systems. > Commons Crypto has an implementation that could be used as a starting point: > https://github.com/apache/commons-crypto/blob/master/src/main/java/org/apache/commons/crypto/random/OsCryptoRandom.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (RNG-19) System generator (/dev/random)
Emmanuel Bourg created RNG-19: - Summary: System generator (/dev/random) Key: RNG-19 URL: https://issues.apache.org/jira/browse/RNG-19 Project: Commons RNG Issue Type: Wish Reporter: Emmanuel Bourg Priority: Minor Commons RNG could include a random number generator based on the output of /dev/random or /dev/urandom on Unix systems. Commons Crypto has an implementation that could be used as a starting point: https://github.com/apache/commons-crypto/blob/master/src/main/java/org/apache/commons/crypto/random/OsCryptoRandom.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (RNG-18) LICENSE.txt cleanup
Emmanuel Bourg created RNG-18: - Summary: LICENSE.txt cleanup Key: RNG-18 URL: https://issues.apache.org/jira/browse/RNG-18 Project: Commons RNG Issue Type: Bug Reporter: Emmanuel Bourg Priority: Trivial The LICENSE.txt file was apparently inherited from the Commons Math project and contains several licenses unrelated to the code in Commons RNG (minpack, odex, netlib, BracketFinder...). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RNG-16) Linear congruential generators
[ https://issues.apache.org/jira/browse/RNG-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509916#comment-15509916 ] Emmanuel Bourg commented on RNG-16: --- Indeed > Linear congruential generators > -- > > Key: RNG-16 > URL: https://issues.apache.org/jira/browse/RNG-16 > Project: Commons RNG > Issue Type: Improvement >Reporter: Emmanuel Bourg >Priority: Minor > > This is a RFE for implementing linear congruential generators: > https://en.wikipedia.org/wiki/Linear_congruential_generator > This type of random generator is often used in language runtimes (Borland C, > GCC, Delphi, VB and even Java). Preconfigured generators using the same > parameters as these languages would be convenient for reproducing the same > number sequences in Java. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RNG-16) Linear congruential generators
[ https://issues.apache.org/jira/browse/RNG-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509793#comment-15509793 ] Emmanuel Bourg commented on RNG-16: --- Actually every client will use the same random generator with the same parameters regardless of the language used. This ensures that all clients generate the same random events from the seed initially sent by the server. The generator is defined by the protocol, all clients know that they have to reproduce the behavior of the default GCC generator for example. > Linear congruential generators > -- > > Key: RNG-16 > URL: https://issues.apache.org/jira/browse/RNG-16 > Project: Commons RNG > Issue Type: Improvement >Reporter: Emmanuel Bourg >Priority: Minor > > This is a RFE for implementing linear congruential generators: > https://en.wikipedia.org/wiki/Linear_congruential_generator > This type of random generator is often used in language runtimes (Borland C, > GCC, Delphi, VB and even Java). Preconfigured generators using the same > parameters as these languages would be convenient for reproducing the same > number sequences in Java. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (RNG-17) Lagged Fibonacci generators
Emmanuel Bourg created RNG-17: - Summary: Lagged Fibonacci generators Key: RNG-17 URL: https://issues.apache.org/jira/browse/RNG-17 Project: Commons RNG Issue Type: Improvement Reporter: Emmanuel Bourg Priority: Minor This is a RFE to implement Lagged Fibonacci generators: https://en.wikipedia.org/wiki/Lagged_Fibonacci_generator -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RNG-16) Linear congruential generators
[ https://issues.apache.org/jira/browse/RNG-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15508983#comment-15508983 ] Emmanuel Bourg commented on RNG-16: --- The use case I have in mind is a game server distributing a seed to the clients and expecting them to generate an identical sequence of random events. Different implementations of the client in different languages need to be interoperable. > Linear congruential generators > -- > > Key: RNG-16 > URL: https://issues.apache.org/jira/browse/RNG-16 > Project: Commons RNG > Issue Type: Improvement >Reporter: Emmanuel Bourg >Priority: Minor > > This is a RFE for implementing linear congruential generators: > https://en.wikipedia.org/wiki/Linear_congruential_generator > This type of random generator is often used in language runtimes (Borland C, > GCC, Delphi, VB and even Java). Preconfigured generators using the same > parameters as these languages would be convenient for reproducing the same > number sequences in Java. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (RNG-16) Linear congruential generators
Emmanuel Bourg created RNG-16: - Summary: Linear congruential generators Key: RNG-16 URL: https://issues.apache.org/jira/browse/RNG-16 Project: Commons RNG Issue Type: Improvement Reporter: Emmanuel Bourg Priority: Minor This is a RFE for implementing linear congruential generators: https://en.wikipedia.org/wiki/Linear_congruential_generator This type of random generator is often used in language runtimes (Borland C, GCC, Delphi, VB and even Java). Preconfigured generators using the same parameters as these languages would be convenient for reproducing the same number sequences in Java. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (COMMONSSITE-86) Update Logo with new ASF Feather
[ https://issues.apache.org/jira/browse/COMMONSSITE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15461447#comment-15461447 ] Emmanuel Bourg commented on COMMONSSITE-86: --- I think we should drop the URL from the logo. > Update Logo with new ASF Feather > > > Key: COMMONSSITE-86 > URL: https://issues.apache.org/jira/browse/COMMONSSITE-86 > Project: Commons All > Issue Type: Task >Reporter: Benedikt Ritter > Attachments: commons-logo_new.svg, commons-logo_new1.png, > commons-logo_new2.png, commons-logo_new3.png, commons-logo_new4.png, > commons_logo.small.png > > > We should create a new logo from the new ASF Feather logo > (https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces86) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RNG-2) Allow creation and execution of JMH based benchmarks
[ https://issues.apache.org/jira/browse/RNG-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413565#comment-15413565 ] Emmanuel Bourg commented on RNG-2: -- I don't think that would work, unless the CI server doesn't run any other jobs during the execution of the benchmark (and that's probably not the case with the server used at Apache). > Allow creation and execution of JMH based benchmarks > > > Key: RNG-2 > URL: https://issues.apache.org/jira/browse/RNG-2 > Project: Commons RNG > Issue Type: Bug >Reporter: Artem Barger > Attachments: RNG-2.patch > > > Add relevant maven changes to enable creation and execution of benchmarks > based on JMH (Java Microbenchmarks harness) framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RNG-2) Allow creation and execution of JMH based benchmarks
[ https://issues.apache.org/jira/browse/RNG-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413506#comment-15413506 ] Emmanuel Bourg commented on RNG-2: -- Yes that was my intent for CSV. Checking for performance regression is a good idea, but I don't know how this could be automated since different developers will get different results. > Allow creation and execution of JMH based benchmarks > > > Key: RNG-2 > URL: https://issues.apache.org/jira/browse/RNG-2 > Project: Commons RNG > Issue Type: Bug >Reporter: Artem Barger > Attachments: RNG-2.patch > > > Add relevant maven changes to enable creation and execution of benchmarks > based on JMH (Java Microbenchmarks harness) framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RNG-2) Allow creation and execution of JMH based benchmarks
[ https://issues.apache.org/jira/browse/RNG-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413490#comment-15413490 ] Emmanuel Bourg commented on RNG-2: -- I never considered this. The results are so system dependent I'm not sure it would make sense to keep them. > Allow creation and execution of JMH based benchmarks > > > Key: RNG-2 > URL: https://issues.apache.org/jira/browse/RNG-2 > Project: Commons RNG > Issue Type: Bug >Reporter: Artem Barger > Attachments: RNG-2.patch > > > Add relevant maven changes to enable creation and execution of benchmarks > based on JMH (Java Microbenchmarks harness) framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RNG-2) Allow creation and execution of JMH based benchmarks
[ https://issues.apache.org/jira/browse/RNG-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413458#comment-15413458 ] Emmanuel Bourg commented on RNG-2: -- Also, the benchmarks are bound to the test phase, so invoking the benchmark is done with "mvn test -Pbenchmark". https://git-wip-us.apache.org/repos/asf?p=commons-csv.git;a=blob;f=pom.xml;h=9a2b35a995a8e5d037c124a11c82263127dc3595;hb=HEAD#l390 There is also an optional parameter to select the benchmark to run. > Allow creation and execution of JMH based benchmarks > > > Key: RNG-2 > URL: https://issues.apache.org/jira/browse/RNG-2 > Project: Commons RNG > Issue Type: Bug >Reporter: Artem Barger > Attachments: RNG-2.patch > > > Add relevant maven changes to enable creation and execution of benchmarks > based on JMH (Java Microbenchmarks harness) framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (RNG-2) Allow creation and execution of JMH based benchmarks
[ https://issues.apache.org/jira/browse/RNG-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413453#comment-15413453 ] Emmanuel Bourg commented on RNG-2: -- For Commons CSV we used a "benchmark" profile. It might be nice to have the same profile name for the benchmarks across the Commons components. > Allow creation and execution of JMH based benchmarks > > > Key: RNG-2 > URL: https://issues.apache.org/jira/browse/RNG-2 > Project: Commons RNG > Issue Type: Bug >Reporter: Artem Barger > Attachments: RNG-2.patch > > > Add relevant maven changes to enable creation and execution of benchmarks > based on JMH (Java Microbenchmarks harness) framework. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MATH-1196) FastMath.round (like Math.round) returns surprising results for some arguments
[
https://issues.apache.org/jira/browse/MATH-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg resolved MATH-1196.
--
Resolution: Fixed
Fix Version/s: 4.0
> FastMath.round (like Math.round) returns surprising results for some arguments
> --
>
> Key: MATH-1196
> URL: https://issues.apache.org/jira/browse/MATH-1196
> Project: Commons Math
> Issue Type: Bug
>Affects Versions: 3.4.1
>Reporter: Phil Steitz
> Fix For: 4.0
>
> Attachments: MATH-1196.patch
>
>
> The first assertion in the test case below succeeds, but the second fails
> {code}
> /*
> * http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6430675
> */
> @Test
> public void testRoundDown() {
> final double x = 0x1.fp-2;
> Assert.assertTrue(x < 0.5d);
> Assert.assertEquals(0, FastMath.round(x));
> }
> {code}
> This is being tracked as a JDK (actually spec) bug here:
> http://bugs.java.com/bugdatabase/view_bug.do?bug_id=6430675
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CRYPTO-33) SecureRandom shadows JVM class
[ https://issues.apache.org/jira/browse/CRYPTO-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261964#comment-15261964 ] Emmanuel Bourg commented on CRYPTO-33: -- Having the same names in Crypto and in the JDK is a nice feature IMO. It means people can just switch the import statements and benefit from the speed improvements (assuming the API is similar). > SecureRandom shadows JVM class > -- > > Key: CRYPTO-33 > URL: https://issues.apache.org/jira/browse/CRYPTO-33 > Project: Commons Crypto > Issue Type: Bug >Reporter: Sebb >Assignee: Xianda Ke > > The SecureRandom interface also exists as a class in java.security. > This makes it awkward to use, for example in JavaSecureRandom the fully > qualified name has to be used for the java class. > Ideally it should be renamed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CRYPTO-29) Make sure Cypher.ENCRYPT_MODE is consistent with JDK
[ https://issues.apache.org/jira/browse/CRYPTO-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259802#comment-15259802 ] Emmanuel Bourg commented on CRYPTO-29: -- I guess to avoid using fully qualified names since the Cypher class also exist in the JDK. > Make sure Cypher.ENCRYPT_MODE is consistent with JDK > > > Key: CRYPTO-29 > URL: https://issues.apache.org/jira/browse/CRYPTO-29 > Project: Commons Crypto > Issue Type: Bug >Reporter: Sebb >Assignee: Dian Fu > Fix For: 1.0.0 > > > Cypher.ENCRYPT_MODE should be an enum > Or is it supposed to be the same as Openssl.ENCRYPT_MODE? > In which case, why not use that? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (COLLECTIONS-587) commons-collections-3.2.2 does not compile under docker fedora21
[ https://issues.apache.org/jira/browse/COLLECTIONS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg resolved COLLECTIONS-587. Resolution: Won't Fix > commons-collections-3.2.2 does not compile under docker fedora21 > > > Key: COLLECTIONS-587 > URL: https://issues.apache.org/jira/browse/COLLECTIONS-587 > Project: Commons Collections > Issue Type: Bug >Affects Versions: 3.2 > Environment: docker, fedora21 >Reporter: Marc Pawlowsky > > In a clean environment using docker, compile errors > $cat Dockerfile > FROM fedora:21 > RUN yum update -y > RUN yum install -y java-1.8.0-openjdk unzip maven wget > RUN wget > http://apache.mirror.rafal.ca//commons/collections/source/commons-collections-3.2.2-src.zip > RUN unzip commons-collections-3.2.2-src.zip > RUN cd commons-collections-3.2.2-src && mvn initialize > RUN cd commons-collections-3.2.2-src && mvn install > RUN chmod -R 755 /root > CMD /bin/bash > $docker build . > > Downloaded: http://repo.maven.apache.org/maven2/commons-[INFO] Changes > detected - recompiling the module! > [INFO] Compiling 273 source files to > /commons-collections-3.2.2-src/target/classes > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/MultiHashMap.java:[334,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.MultiHashMap cannot implement > remove(java.lang.Object,java.lang.Object) in java.util.Map > return type java.lang.Object is not compatible with boolean > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/MultiMap.java:[69,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.MultiMap clashes with > remove(java.lang.Object,java.lang.Object) in java.util.Map > return type java.lang.Object is not compatible with boolean > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/map/MultiValueMap.java:[156,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.map.MultiValueMap cannot implement > remove(java.lang.Object,java.lang.Object) in java.util.Map > return type java.lang.Object is not compatible with boolean > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/map/MultiKeyMap.java:[200,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.map.MultiKeyMap cannot implement > remove(java.lang.Object,java.lang.Object) in java.util.Map > return type java.lang.Object is not compatible with boolean > [INFO] 4 errors > [INFO] - > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 19.104 s > [INFO] Finished at: 2016-04-26T12:35:24-04:00 > [INFO] Final Memory: 19M/203M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (default-compile) > on project commons-collections: Compilation failure: Compilation failure: > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/MultiHashMap.java:[334,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.MultiHashMap cannot implement > remove(java.lang.Object,java.lang.Object) in java.util.Map > [ERROR] return type java.lang.Object is not compatible with boolean > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/MultiMap.java:[69,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.MultiMap clashes with > remove(java.lang.Object,java.lang.Object) in java.util.Map > [ERROR] return type java.lang.Object is not compatible with boolean > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/map/MultiValueMap.java:[156,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.map.MultiValueMap cannot implement > remove(java.lang.Object,java.lang.Object) in java.util.Map > [ERROR] return type java.lang.Object is not compatible with boolean > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/map/MultiKeyMap.java:[200,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.map.MultiKeyMap cannot implement > remove(java.lang.Object,java.lang.Object) in java.util.Map > [ERROR] return type java.lang.Object is
[jira] [Commented] (COLLECTIONS-587) commons-collections-3.2.2 does not compile under docker fedora21
[ https://issues.apache.org/jira/browse/COLLECTIONS-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258923#comment-15258923 ] Emmanuel Bourg commented on COLLECTIONS-587: This was fixed in Fedora 24. There is a patch available you could use to build with Java 8 in Fedora 21: https://pkgs.fedoraproject.org/cgit/rpms/apache-commons-collections.git/tree/0001-Port-to-Java-8.patch > commons-collections-3.2.2 does not compile under docker fedora21 > > > Key: COLLECTIONS-587 > URL: https://issues.apache.org/jira/browse/COLLECTIONS-587 > Project: Commons Collections > Issue Type: Bug >Affects Versions: 3.2 > Environment: docker, fedora21 >Reporter: Marc Pawlowsky > > In a clean environment using docker, compile errors > $cat Dockerfile > FROM fedora:21 > RUN yum update -y > RUN yum install -y java-1.8.0-openjdk unzip maven wget > RUN wget > http://apache.mirror.rafal.ca//commons/collections/source/commons-collections-3.2.2-src.zip > RUN unzip commons-collections-3.2.2-src.zip > RUN cd commons-collections-3.2.2-src && mvn initialize > RUN cd commons-collections-3.2.2-src && mvn install > RUN chmod -R 755 /root > CMD /bin/bash > $docker build . > > Downloaded: http://repo.maven.apache.org/maven2/commons-[INFO] Changes > detected - recompiling the module! > [INFO] Compiling 273 source files to > /commons-collections-3.2.2-src/target/classes > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/MultiHashMap.java:[334,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.MultiHashMap cannot implement > remove(java.lang.Object,java.lang.Object) in java.util.Map > return type java.lang.Object is not compatible with boolean > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/MultiMap.java:[69,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.MultiMap clashes with > remove(java.lang.Object,java.lang.Object) in java.util.Map > return type java.lang.Object is not compatible with boolean > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/map/MultiValueMap.java:[156,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.map.MultiValueMap cannot implement > remove(java.lang.Object,java.lang.Object) in java.util.Map > return type java.lang.Object is not compatible with boolean > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/map/MultiKeyMap.java:[200,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.map.MultiKeyMap cannot implement > remove(java.lang.Object,java.lang.Object) in java.util.Map > return type java.lang.Object is not compatible with boolean > [INFO] 4 errors > [INFO] - > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 19.104 s > [INFO] Finished at: 2016-04-26T12:35:24-04:00 > [INFO] Final Memory: 19M/203M > [INFO] > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (default-compile) > on project commons-collections: Compilation failure: Compilation failure: > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/MultiHashMap.java:[334,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.MultiHashMap cannot implement > remove(java.lang.Object,java.lang.Object) in java.util.Map > [ERROR] return type java.lang.Object is not compatible with boolean > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/MultiMap.java:[69,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.MultiMap clashes with > remove(java.lang.Object,java.lang.Object) in java.util.Map > [ERROR] return type java.lang.Object is not compatible with boolean > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/map/MultiValueMap.java:[156,19] > remove(java.lang.Object,java.lang.Object) in > org.apache.commons.collections.map.MultiValueMap cannot implement > remove(java.lang.Object,java.lang.Object) in java.util.Map > [ERROR] return type java.lang.Object is not compatible with boolean > [ERROR] > /commons-collections-3.2.2-src/src/java/org/apache/commons/collections/map/Mult
[jira] [Deleted] (CRYPTO-17) cannon printer technical support number 18447733444
[ https://issues.apache.org/jira/browse/CRYPTO-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg deleted CRYPTO-17: - > cannon printer technical support number 18447733444 > > > Key: CRYPTO-17 > URL: https://issues.apache.org/jira/browse/CRYPTO-17 > Project: Apache Commons Crypto > Issue Type: Bug >Reporter: pawan153 > > Kokla chipake jumme raat aayi ae > Jehda ajj vi naa nache > Ohdi shaamat aayi ae (x4) > Yaaran de naal baharan ne > Life ‘ch mauj hazaran ne > Aidaan hi din sare langh jaane > Aaj di raat saanu yaad rave > Nachna main saari raat… > Chak laini duniya… > Photovan te khich lao… > Rehna kuch naiyo yaad… > Kal de assi jawak.. > Saare de saare bebaak.. > Marzi ae karni.. > Saada duniya te raaj.. > Nach lehn de… > Ajj di raat sanu nach lehn de (x2) > Kudiyan di toli jadon club vich aayi > Aayi aayi aayi aayi > Dekhde ne saare ehna karti duhaai > Aayi aayi aayi aayi > Mundeyan de pairan thallo dharti hilaai.. > DJ ne aa beat jadon club ch vajaai.. > Kokla chipaki jumme raat aayi ae > Jehda ajj vi na nache > Ohdi shaamat aayi ae (x4) > Yo Yo Honey Singh Rap > Ajj di ae dekho raat jashan di > Thode bohte dekho gangsta fun di > Gangsters mere yaaran nu na roko > Vairi jithe mile ohnu othe thoko > Peg Patiala > Meat tari wala > Jina marzi maal shako > Chitta bhaven kala > Kaali mainu payi > Meri UK di flight ae > Flight main chalauni > Kyunki jatt ajj tight ae > Kudiyan di toli jadon club vich aayi > Aayi aayi aayi aayi > Dekhde ne saare ehna karti duhaai > Aayi aayi aayi aayi > Mundeyan de pairan thallo dharti hilaai.. > DJ ne aa beat jadon club ch vajaayi.. > Kokla chipake jumme raat aayi ae > Jehda ajj vi naa nache > Ohdi shaamat aayi ae (x4) > Main tan chitte te sutte nu hath naiyo launda > Daaru diyan gallan karo botal makaunda > Main taan sihda sadha banda > Aiven chit parchaunda > Par choti moti gallan utte status ni paunda > Sunakhiyan batheriyan, mere agge piche > Mere yaar ne aashiq, dil de sache > 10 saalan ‘ch koi geet > Main repeat naiyo kita > Meri mashook kidi sohni > Main kade cheat naiyo kita > Yaaran de naal baharan ne > Life ‘ch mauj hazaraan ne > Aidaan hi din sare langh jaane > Aaj di raat saanu yaad rave > Nachna main saari raat.. > Chak laini duniya.. > Photovan te khich lao.. > Rehna kuch naiyo yaad.. > Kal de assi jawaak.. > Saare de sare bebaak.. > Marzi ae karni.. > Sada duniya te raaj.. > Nach lehn de… > Aaj di raat sanu nach lehn de (x2) > Kudiyana di toli jado club vich aayi > Aayi aayi aayi aayi > Dekhde ne saare ehna karti duhaai > Aayi aayi aayi aayi > Mundeyan de pairaan thallon dharti hilaai.. > DJ ne aa beat jadon club ch vajaayi.. > Kokla shapaki jumme raat aayi ae > Jehda ajj vi naa nache > Ohdi shaamat aayi ae (x4) > Yo Yo Honey Singh… > Kudiyaan di toli jado club vich aaye > Aaayi aaayi aaayi > Dekhde ne sare ehna karti duhaai > Aaayi aaayi aaayi > Mundeyan de pairaan thallo dhart hilaai.. > DJ ne aa beat jadon club ch vajaai.. > https://www.linkedin.com/company/hp-tech-support-number-1844-773-3444-printer-help-line-telephone?trk=biz-companies-cym -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (CRYPTO-16) cannon printer helpdesk tech support number 18447733444
[ https://issues.apache.org/jira/browse/CRYPTO-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg deleted CRYPTO-16: - > cannon printer helpdesk tech support number 18447733444 > --- > > Key: CRYPTO-16 > URL: https://issues.apache.org/jira/browse/CRYPTO-16 > Project: Apache Commons Crypto > Issue Type: Bug >Reporter: pawan153 > > Teri khatir laya su kamaake > Chori dekh le tu azma ke (x2) > Na kar marod > Tere pe main kar dyun kharch karod (x3) > Re gale mein chain tu moti le le > Har ik chowk pe kothi lele > Ek baar tu haan toh karde > Rakam chache tu moti lele > Kharch karod main kar doon re chori > Ek baar tere kehne pe > Heere jaisa yaar hai tera > Kyun mar’ri se gehne pe > Jo Radha ne paya Shyam mein > Jo Sita ne paya Ram mein > Mere jaisa na paave gaam mein > Jad bandhoon main mor > Tere pe main kar dyun kharch karod (x3) > Manne qasam kuraan aur geeta ki > Saugandh Ram ki khaunga > Randeep Hooda hai naam mera > Tane izzat badi dilaunga > Main toh bhanga ragad ke piya karoon > Tanne jo chahiye dilaunga > Bhole ka hoon main bhagat bada > Seedha kailas dikhaunga > Tu jaan meri se jaan le > Tu pyaar mera pehchan le > Tu baat meri ya maan le > Phir pattan de tor > Tere pe main kar dyun kharch karod (x3) > Mehnat se kamaya maine loota nahi hai > Dil tujhpe aaya yeh jhootha nahi hai > Rey kharch crore toh dil yeh karde > Dil ki atth bhi meri karde > https://www.linkedin.com/company/hp-tech-support-number-1844-773-3444-printer-help-line-telephone?trk=biz-companies-cym -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (CRYPTO-15) The CaUSA 1-888-461-5771 netflix Customer service number netflix Help Desk Number
[ https://issues.apache.org/jira/browse/CRYPTO-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg deleted CRYPTO-15: - > The CaUSA 1-888-461-5771 netflix Customer service number netflix Help Desk > Number > - > > Key: CRYPTO-15 > URL: https://issues.apache.org/jira/browse/CRYPTO-15 > Project: Apache Commons Crypto > Issue Type: Bug >Reporter: adf sdafsaf asd > > The CaUSA 1-888-461-5771 netflix Customer service number netflix Help Desk > Number > USA Canada UK Australia(((!1 888 461 5771))) netflix Customer service number > netflix tech support number netflix customer phone number, netflix cusomer > service number, netflix help desk number, netflix customer care number, > netflix support phone number, netflix password recovery phone number, > netflix account recovery phone number, netflix toll free numbe help,JUSTs > Call USA 1-888-461-5771 netflix tech support number, Wireless netflix > customer service number, netflix support number, netflix phone number > netflix customer phone number helpline number,USA CANADA>>1888-461-5771 > netflixTECH SUPPORT PHONE NUMBER netflixCUSTOMER SERVICE PHONE > NUMBER here.1888-461-5771 netflix TECH SUPPORT PHONE NUMBER %%% netflix > CUSTOMER SERVICE PHONE NUMBER netflix technical support number netflix > helpdesk number netflix helpdesk phone number netflix Helpline number, > netflix Phone number USA CANADA,(((1888-461-5771- netflix phone > number=== netflixtech support PHONE NUMBER Helpline tollfree > ===!!===1888-461-5771== netflix tech support phone number ==!! > netflix install TECH SUPPORT PHONE NUMBER FREE USA CANADA !!1888-461-5771 > netflix TECH SUPPORT PHONE NUMBER %%% netflixCUSTOMER SERVICE PHONE > NUMBER ===!!! *** netflix customer service phone number!!! netflix phone > number netflixtelephone number!!1888-461-5771== netflixPHONE > NUMBER!!!TECH SUPPORT phone number ++ netflix TOLL FREE PHONE NUMBERPhone > Number 1888-461-5771 USA CANADA, netflix 360 Support Phone Number, > netflix Technical Support Phone Numbe here. netflix tech support number > netflix Help Desk Number !!1888-461-5771 Describe toll free netflix Phone > Number 1888-461-5771 USA CANADA, netflix 360 Support Phone Number, > netflix Technical Support Phone Number here.toll free netflix Phone > Number 1888-461-5771 USA CANADA, netflix 360 Support Phone Number, > netflix Technical Support Phone Number toll free netflix Phone Number > 1888-461-5771 USA CANADA, netflix 360 Support Phone Number, netflix > Technical Support Phone Number, netflix Customer Support Number?? This > article is in need of a technical review. This article is in need of an > editorial review. netflix Phone Number 1888-461-5771 USA CANADA, netflix > Support Phone Number, netflix Technical Support Phone Number, netflix > Customer Support Number?? netflix Support Phone Number 1888-461-5771 USA > CANADA, netflixPhone Number, netflixTechnical Support Phone Number, > netflix Service Support Number netflix Support Phone Number > 1888-461-5771 USA CANADA, netflixPhone Number, netflixTechnical > Support Phone Number, netflix Service Support Number?? netflix Phone > Number 1888-461-5771 USA CANADA, netflix 360 Support Phone Number, > netflix Technical Support Phone Number, netflix Customer Support > Number?? netflix Support Phone Number 1888-461-5771 USA CANADA, netflix > Support Phone Number, netflix Technical Support Phone Number, netflix > Customer Support Number?? netflix phone number #$#1888-461-5771##$ netflix >phone number netflix security phone number netflix 360 phone number > #$#1888-461-5771##$ netflix support phone number netflix symantec phone > number netflix phone number customer service #$#1888-461-5771##$ netflix > tech support number netflix Help Desk Number !!1888-461-5771 netflix > customer service phone number netflix tech support phone number netflix > technical support phone number netflix phone numbers netflix help phone > number netflixsupport phone number #$#1888-461-5771##$ netflix phone > support netflix contact phone number netflix internet security phone > number netflix 360 support phone number netflix phone netflix 1888 > phone number phone number for netflix phone numbers netflixcustomer > service phone number netflix customer support phone number find a phone > number netflix USA CANADA phone number USA CANADA phone number phone > number for netflixtech support phone number netflix 360 phone support > free phone numbers phone number netflix
[jira] [Deleted] (CRYPTO-14) File:+===+++(Netflix 1 888 461 5771 Netflix Tech Support number Netflix Tech support here.TalkNetfli
[ https://issues.apache.org/jira/browse/CRYPTO-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg deleted CRYPTO-14: - > File:+===+++(Netflix 1 888 461 5771 Netflix Tech Support number Netflix Tech > support here.TalkNetfli > > > Key: CRYPTO-14 > URL: https://issues.apache.org/jira/browse/CRYPTO-14 > Project: Apache Commons Crypto > Issue Type: Bug >Reporter: fdsaf asdfasf > Labels: performance > > File:+===+++(Netflix 1 888 461 5771 Netflix Tech Support number Netflix Tech > support here.TalkNetfli > File:+===+++(Netflix 1 888 461 5771 Netflix Tech Support number Netflix Tech > support here.TalkNetflix 1 888 461 5771 Netflix Tech Support number Netflix > Tech support phone number Netflix AntI+@1 888 461 5771 > +===+++(Netflix 1 888 461 5771 Netflix Tech Support number Netflix Tech > support here.Talk:Netflix 1 888 461 5771 Netflix Tech Support number Netflix > Tech support phone number Netflix AntI+@**1 888 461 5771**) Netflix Technical > Support number Netflix Tech support phone number Netflix AntI+@**1 888 461 > 5771**) Netflix Technical Support number Netflix Tech support phone number > Describe *Helpline Number*))) (**1 888 461 5771**) Netflix Technical Support > number Netflix Tech support phone number here.*Helpline Number*))) (**1 888 > 461 5771**) Netflix Technical Support number Netflix Tech support phone > number *Helpline Number*))) (**1 888 461 5771**) Netflix Technical Support > number Netflix Tech support phone number *Helpline Number*))) (**1 888 461 > 5771**) Netflix Technical Support number Netflix Tech support phone number > *Helpline Number*))) (**1 888 461 5771**) Netflix Technical Support number > Netflix Tech support phone number *Helpline Number*))) (**1 888 461 5771**) > Netflix Technical Support number Netflix Tech support phone number *Helpline > Number*))) (**1 888 461 5771**) Netflix Technical Support number Netflix Tech > support phone number *Helpline Number*))) (**1 888 461 5771**) Netflix > Technical Support number Netflix Tech support phone number *Helpline > Number*))) (**1 888 461 5771**) Netflix Technical Support number Netflix Tech > support phone number *Helpline Number*))) (**1 888 461 5771**) Netflix > Technical Support number Netflix Tech support phone number *Helpline > Number*))) (**1 888 461 5771**) Netflix Technical Support number Netflix Tech > support phone number *Helpline Number*))) (**1 888 461 5771**) Netflix > Technical Support number Netflix Tech support phone number *Helpline > Number*))) (**1 888 461 5771**) Netflix Technical Support number Netflix Tech > support phone number *Helpline Number*))) (**1 888 461 5771**) Netflix > Technical Support number Netflix Tech support phone number *Helpline > Number*))) (**1 888 461 5771**) Netflix Technical Support number Netflix Tech > support phone number *Helpline Number*))) (**1 888 461 5771**) Netflix > Technical Support number Netflix Tech support phone number *Helpline > Number*))) (**1 888 461 5771**) Netflix Technical Support number Netflix Tech > support phone number Helpline Number 1 888 461 5771Netflix Technical Support > number Netflix Tech support phone number Helpline @Number ***1888 (461) > 5771*** Netflix Technical Support number Netflix Tech support phone number > Helpline~Number~1888 461 5771 Netflix Tech Support phone number Netflix > Customer Service phone number Helpline Number 1888 461 5771 Netflix > Tech Support phone number Netflix Netflix helpline number Netflix driver > support number Netflix toll free number Netflix tech support Netflix tech > support number Netflix tech support phone number Netflix technical support > Netflix technical support number Netflix technical support phone number > Netflix support phone number Netflix customer service number Netflix customer > service phone number Netflix customer support number Netflix customer support > phone number Netflix customer care number a, @+888 461 5771 @ Netflix Support > phone number, Netflix contact number, Netflix helpline number, Netflix > telephone number, contact number for Netflix, telephone number for Netflix, > @+888 461 5771 @ Netflix customer service number, Netflix Customer service > phone number, Netflix Customer support number, Netflix Customer support phone > number, Netflix Customer care number. Disclaimer: Netflix is an independent > vider of remote tech support for third party ducts. Any use of third party > trademarks, brand names, duct and services is only referential. Netflix > hereby disclaims any sponsorship, affiliation or endorsement of or by any > third-parties. If your duct is covered by warranty, the support service maybe > available for free from manufacturer. Netflix support, Netflixs su
[jira] [Deleted] (CRYPTO-19) 1 855-800-8493 Apple Icloud tech support phone number?
[ https://issues.apache.org/jira/browse/CRYPTO-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg deleted CRYPTO-19: - > 1 855-800-8493 Apple Icloud tech support phone number? > -- > > Key: CRYPTO-19 > URL: https://issues.apache.org/jira/browse/CRYPTO-19 > Project: Apache Commons Crypto > Issue Type: Bug >Reporter: mskmskmkemk > > 1 855-800-8493 Apple Icloud tech support phone number?Add Phone Number to > iCloud technical support number icloud email apple create icloud account > Apple Customer Service Apple Customer Service for iCloud Apple Customer > Service for iCloud Apple iCloud Contacts Apple iCloud Customer Service Apple > iCloud Customer Service Number Apple iCloud Customer Support apple icloud > customer support email Apple iCloud Customer Support apple icloud email apple > icloud email change apple icloud email hacked service apple icloud email > hacked service apple icloud email login apple icloud email problems apple > icloud email settings Apple iCloud Help Phone Number Apple iCloud Scam Apple > iCloud Support Apple iCloud Support Contact apple icloud support contact > number Apple iCloud Support Number apple icloud support phone number Apple > iCloud Support Contact Number Apple iCloud Support Phone Number apple icloud > tech support phone number Apple iCloud Support Phone Number apple iclud email > password rest apple icould email settings apple icould email support apple > icould support phone number Apple ID iCloud Email Apple iPad Telephone Number > Apple iPhone Contact Number Apple Numbers iCloud Apple Phone Number apple > setup icloud account Apple Support iCloud apple support icloud telephone > number Apple Support Phone Number Apple Support Phone Number for iPad Apple > Support Phone Number for iPhone 5S Apple Support Phone Number iPhone Apple > Support Phone Number iTunes Apple Tech Support Apple Tech Support Phone > Number Apple iCloud Support Number Apple iCloud Support Phone Number Apple > Support Phone Number Contact Apple for Refund Contact Apple iCloud Contact > iCloud Support contact icloud support email contact icloud support email > number Contact iCloud Support Phone Number Contact iCloud Support does icould > email support imap Find iPad Serial Number Find iPhone Serial Number Online > Find iPhone Using Phone Number Get Contacts from iCloud How to Contact iCloud > How to Get My Contacts from iCloud How to Sync Contacts to iCloud icloud mail > help icloud smtp server ip address and port icloud address when texting > icloud addresses not syncing icloud apple iphone tech support phone number > canada iCloud Contact Info iCloud Contact Number icloud contact phone number > iCloud Contact Us icloud contacts not syncing with mac icloud contacts not > syncing with opulook2010 iCloud Contacts to Windows Phone iCloud Customer > Care Email icloud customer care number iCloud Customer Service icloud > customer service canada icloud customer service canada number icloud customer > service contact number icloud customer service contact number canada icloud > customer service contact number usa icloud customer service email number > icloud customer service email number canada icloud customer service number > iCloud Customer Service Phone Number iCloud Customer Service Telephone Number > iCloud Customer Service Phone Number iCloud Customer Support icloud customer > support email iCloud Customer Support Number icloud customer support phone > number icloud customer tech support iCloud Customer Care Email icloud email > password icloud email address server number icloud email apple iphone tech > support number usa icloud email apple iphone tech support phone number usa > icloud email apple number icloud email apple phone icloud email apple phone > number icloud email apple phones number icloud email customer number icloud > email customer service number icloud email customer service phone icloud > email customer service phone number icloud email customer service specialist > number icloud email customer tech support icloud email helpdesk icloud email > helpdesk number icloud email helpdesk phone icloud email helpdesk phone > number icloud email helpdesk phone number canada icloud email helpdesk phone > number us icloud email helpdesk support icloud email helpdesk support number > icloud email helpdesk support services icloud email helpdesk support services > number icloud email hp eprint support number icloud email ipad contacts > icloud email ipad customer service phone number usa icloud email iphone tech > support phone icloud email not working september 2012 icloud email not > wotrking sept11 icloud email online computer support icloud email online > computer support number icloud email online computer support number canada > icloud email onli
[jira] [Deleted] (CRYPTO-18) Call Netflix 1-888-461-5771 Netflix technical support phone number,telephone number
[ https://issues.apache.org/jira/browse/CRYPTO-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg deleted CRYPTO-18: - > Call Netflix 1-888-461-5771 Netflix technical support phone number,telephone > number > --- > > Key: CRYPTO-18 > URL: https://issues.apache.org/jira/browse/CRYPTO-18 > Project: Apache Commons Crypto > Issue Type: Bug >Reporter: jay kumar > > Call Netflix 1-888-461-5771 Netflix technical support phone number,telephone > number > Netflix 1-888-461-5771 customer service phone number > Netflix 1-888-461-5771 customer service phone number > Toll Free Number 1-888-461-5771 > Netflix toll free number, > Netflix toll free number, > Netflix toll free number, > Netflix Customer service number, > Netflix Customer service number, > Netflix Customer service number, > Netflix technical support phone number, > Netflix technical support phone number, > Netflix technical support phone number, > Netflix tech support phone number, > Netflix tech support phone number > Netflix password recovery phone number, > Netflix customer service phone number, > Netflix customer service number, > Netflix customer service number usa, > Netflix customer service number canada > Netflix customer care phone number, > Netflix customer service, > Netflix customer service phone number, > Netflix customer service number, > Netflix customer service phone, > Netflix customer service number usa, > Netflix customer service phone number usa, > Netflix customer service canada, > Netflix customer support, > Netflix customer care, > Netflix customer support phone number > Netflix customer care phone number, > Netflix customer service phone number, > Netflix technical support phone number usa, > Netflix technical support phone number, > Netflix technical support number usa, > Netflix technical support phone canada, > Netflix technical support phone number canada, > Netflix tech support, > Netflix technical support, > Netflix tech support, > Netflix password reset, > Netflix contact number, > Netflix phone number, > Netflix support number, > Netflix helpline number, > Netflix tollfree number, > Netflix support phone number, > Netflix tech support number, > Netflix technical support number, > Netflix customer support number, > Netflix customer service phone number, > Netflix customer service number, > Netflix customer service number usa, > Netflix customer service number canada > Netflix customer care phone number, > Netflix customer service, > Netflix customer care phone number, > Netflix customer service, > Netflix customer service phone number, > Netflix customer service number, > Netflix customer service phone, > Netflix customer care number, > Netflix customer service number, > Netflix password reset number, > Netflix password recovery number, > Netflix tech support phone number, > Netflix technical support phone number, > Netflix password reset phone number, > Netflix password recovery phone number, > Netflix customer service phone number, > Netflix customer service number, > Netflix customer service number usa, > Netflix customer service number canada > Netflix support phone number, > Netflix tech support number, > Netflix technical support number, > Netflix customer support number, > Netflix customer care number, > Netflix customer service number, > Netflix password reset number, > Netflix password recovery number, > Netflix tech support phone number, > Netflix technical support phone number, > Netflix password reset phone number, > Netflix password recovery phone number, > Netflix customer service number usa, > Netflix customer service phone number usa, > Netflix customer service canada, > Netflix customer support, > Netflix customer care, > Netflix customer support phone number > Netflix customer care phone number, > Netflix customer service phone number, > Netflix technical support phone number usa, > Netflix technical support phone number, > Netflix technical support number usa, > Netflix technical support phone canada, > Netflix technical support phone number canada, > Netflix tech support, > Netflix technical support, > Netflix tech support, > Netflix password reset, > Netflix contact number, > Netflix phone number, > Netflix support number, > Netflix helpline number, > Netflix tollfree number, > Netflix customer service phone number, > Netflix customer service number, > Netflix customer service phone, > Netflix customer service number usa, > Netflix customer service phone number usa, > Netflix customer service canada, > Netflix customer support, > Netflix customer care, > Netflix customer support phone number > Netflix customer care phone number, > Netflix customer service phone number, > Netflix 1-888-461-5771 customer service phone number > Netflix 1-888-461-5771 customer service phone number > Toll F
[jira] [Deleted] (CRYPTO-20) Hire digital marketing USA 1844-855-8999 get a wedding website call
[ https://issues.apache.org/jira/browse/CRYPTO-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg deleted CRYPTO-20: - > Hire digital marketing USA 1844-855-8999 get a wedding website call > > > Key: CRYPTO-20 > URL: https://issues.apache.org/jira/browse/CRYPTO-20 > Project: Apache Commons Crypto > Issue Type: Bug >Reporter: mskmskmkemk > > Hire digital marketing USA > hire best digital marketing in usa > hire best wordpress developer in usa > hire best website designing company in usa > get a business website call 844-855-8999 > get a wedding website call 844 855 8999 > get digital marketing website call 844 855 8999 > Best digital marketing website designer > Get an digital marketing website Call 844 855 8999 > best digital marketing Websites made in us > best digital marketing Websites made in UK > best digital marketing Websites made in australia > best digital marketing Websites made in DubaiHire digital marketing USA > hire best digital marketing in usa > hire best wordpress developer in usa > hire best website designing company in usa > get a business website call 844-855-8999 > get a wedding website call 844 855 8999 > get digital marketing website call 844 855 8999 > Best digital marketing website designer > Get an digital marketing website Call 844 855 8999 > best digital marketing Websites made in us > best digital marketing Websites made in UK > best digital marketing Websites made in australia > best digital marketing Websites made in DubaiHire digital marketing USA > hire best digital marketing in usa > hire best wordpress developer in usa > hire best website designing company in usa > get a business website call 844-855-8999 > get a wedding website call 844 855 8999 > get digital marketing website call 844 855 8999 > Best digital marketing website designer > Get an digital marketing website Call 844 855 8999 > best digital marketing Websites made in us > best digital marketing Websites made in UK > best digital marketing Websites made in australia > best digital marketing Websites made in DubaiHire digital marketing USA > hire best digital marketing in usa > hire best wordpress developer in usa > hire best website designing company in usa > get a business website call 844-855-8999 > get a wedding website call 844 855 8999 > get digital marketing website call 844 855 8999 > Best digital marketing website designer > Get an digital marketing website Call 844 855 8999 > best digital marketing Websites made in us > best digital marketing Websites made in UK > best digital marketing Websites made in australia > best digital marketing Websites made in DubaiHire digital marketing USA > hire best digital marketing in usa > hire best wordpress developer in usa > hire best website designing company in usa > get a business website call 844-855-8999 > get a wedding website call 844 855 8999 > get digital marketing website call 844 855 8999 > Best digital marketing website designer > Get an digital marketing website Call 844 855 8999 > best digital marketing Websites made in us > best digital marketing Websites made in UK > best digital marketing Websites made in australia > best digital marketing Websites made in DubaiHire digital marketing USA > hire best digital marketing in usa > hire best wordpress developer in usa > hire best website designing company in usa > get a business website call 844-855-8999 > get a wedding website call 844 855 8999 > get digital marketing website call 844 855 8999 > Best digital marketing website designer > Get an digital marketing website Call 844 855 8999 > best digital marketing Websites made in us > best digital marketing Websites made in UK > best digital marketing Websites made in australia > best digital marketing Websites made in DubaiHire digital marketing USA > hire best digital marketing in usa > hire best wordpress developer in usa > hire best website designing company in usa > get a business website call 844-855-8999 > get a wedding website call 844 855 8999 > get digital marketing website call 844 855 8999 > Best digital marketing website designer > Get an digital marketing website Call 844 855 8999 > best digital marketing Websites made in us > best digital marketing Websites made in UK > best digital marketing Websites made in australia > best digital marketing Websites made in Dubai -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MATH-1207) KohonenUpdateActionTest sometimes fails
[
https://issues.apache.org/jira/browse/MATH-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated MATH-1207:
-
Fix Version/s: 3.6.1
> KohonenUpdateActionTest sometimes fails
> ---
>
> Key: MATH-1207
> URL: https://issues.apache.org/jira/browse/MATH-1207
> Project: Commons Math
> Issue Type: Bug
>Reporter: Thomas Neidhart
>Priority: Minor
> Fix For: 4.0, 3.6.1
>
>
> The KohonenUpdateActionTest sometimes failes with the following output:
> {noformat}
> KohonenUpdateActionTest
> testUpdate :
> java.lang.AssertionError
> java.lang.AssertionError: expected:<0.0> but was:<5.551115123125783E-17>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:494)
> at org.junit.Assert.assertEquals(Assert.java:592)
> at
> org.apache.commons.math4.ml.neuralnet.sofm.KohonenUpdateActionTest.testUpdate(KohonenUpdateActionTest.java:90)
> {noformat}
> Investigate why this is happening and fix the test accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CSV-174) Adding methods to support JSON-CSV interchangeability and adding a class/methods to support direct cell modification
[
https://issues.apache.org/jira/browse/CSV-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211685#comment-15211685
]
Emmanuel Bourg commented on CSV-174:
Hi Joey and thank you for the feedback. That makes a lot of points for a single
JIRA issue, it would have been better to discuss this on the mailing list
first, and then open one issue per topic.
1. More feedback on the parsing errors in a good idea
2. JSON integration is out of the scope of Commons CSV in my opinion
3. CSVFile is an Interesting idea. What's your use case? I'm not sure to see
why one would want to manipulate CSV data instead of an object model or a
database later exported to CSV though.
> Adding methods to support JSON-CSV interchangeability and adding a
> class/methods to support direct cell modification
>
>
> Key: CSV-174
> URL: https://issues.apache.org/jira/browse/CSV-174
> Project: Commons CSV
> Issue Type: Improvement
> Components: Build
>Reporter: Joey Pinto
> Labels: gsoc2016
>
> I wish to introduce some major features in the Commons CSV that I found
> really necessary while dealing with CSV file parsing requirements of an ERP
> for a University.
> 1.Custom Exceptions:
> Exceptions to be raised when incorrectly formatted CSVs are parsed
> specifying the row number mentioning reasons like incorrect number of columns.
> 2. Export to JSON:
> PostgreSQL Supports direct import of JSON Code. So to insert data from a CSV
> into the database I had to first convert it to JSON and then make the insert.
> If we could have an option to do this directly it would be a lot more time
> saving.
> 3.New Class CSVFile
> I wish to introduce a new class CSVFile which shall have the entire contents
> of the CSV stored in nested Array Lists.
> I shall have the following methods in the class:
> Constructors:
> void CSVFile(CSVParser);
> void CSVFile(Object [][],boolean has_headers);
> void CSVFile(JSON Array,boolean allow_blanks);
> void CSVFile(String text,String cell_delimiter,String line_delimiter,boolean
> force_headerSchema);
> Printers:
> String CSVFile.toString();
> JSONArray CSVFile.toJSONArray();
> Object[][] CSVFile.toArray();
> ResultSet CSVFile.toResultSet();
> ArrayList CSVFile.toArrayList();
> ArrayList> CSVFile.toNestedArrayList();
> String CSVFile.toString();
> Access:
> CSVFile.setColumnHeader(int col_number);
> String CSVFile.getCell(int row_number,String header);
> String CSVFile.getCell(int row_number,int col_number);
> CSVFile.setCell(int row_number,int col_number,String value);
> CSVFile.setCell(int row_number,String header,String value);
> CSVFile.getRowArray();
> JSONObject CSVFile.getRowJSON();
> Sorting:
> CSVFile.sort(Comparator());
> Extraction:
> CSVFile CSVFile.getColumns(Arraylist headers);
> CSVFile CSVFile.getRows(extractor());
> @override
> public boolean include(CSVRecord record){
> //if satisfies Condition then include
> return true;
> //else return false
>}
> Delete:
> void CSVFile.removeRow(int row_number);
> void CSVFile.remove Section(int start_row,int end_row);
> void CSVFile.CSVFile.removeRows(extractor());
> void CSVFile.removeColumn(int col_number);
> void CSVFile.removeColumn(String header);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (DBUTILS-125) Using Oracle OJDBC7 gives ORA-00933
[ https://issues.apache.org/jira/browse/DBUTILS-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg resolved DBUTILS-125. Resolution: Invalid > Using Oracle OJDBC7 gives ORA-00933 > --- > > Key: DBUTILS-125 > URL: https://issues.apache.org/jira/browse/DBUTILS-125 > Project: Commons DbUtils > Issue Type: Bug >Affects Versions: 1.6 > Environment: JDBC driver version is 12.1.0.1.0 >Reporter: EMR >Priority: Minor > Attachments: JavaApplication35NoDbUtils.tar.bz2, > JavaApplication35WithDbUtils.tar.bz2 > > > Attempting to run an sql query with the latest version of the drivers, it > fails with ERROR (JavaApplication33.java:107) - ORA-00933: SQL command not > properly ended. > However, if I revert to the 11 version of the driver, the query works fine. > Is there a setting that I am missing between the two versions? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (COLLECTIONS-580) Arbitrary remote code execution with InvokerTransformer
[
https://issues.apache.org/jira/browse/COLLECTIONS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated COLLECTIONS-580:
---
Comment: was deleted
(was: dsadas)
> Arbitrary remote code execution with InvokerTransformer
> ---
>
> Key: COLLECTIONS-580
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-580
> Project: Commons Collections
> Issue Type: Bug
>Affects Versions: 3.0, 4.0
>Reporter: Philippe Marschall
> Fix For: 3.2.2, 4.1
>
> Attachments: COLLECTIONS-580.patch
>
>
> With {{InvokerTransformer}} serializable collections can be build that
> execute arbitrary Java code.
> {{sun.reflect.annotation.AnnotationInvocationHandler#readObject}} invokes
> {{#entrySet}} and {{#get}} on a deserialized collection. If you have an
> endpoint that accepts serialized Java objects (JMX, RMI, remote EJB, ...) you
> can combine the two to create arbitrary remote code execution vulnerability.
> I don't know of a good fix short of removing {{InvokerTransformer}} or making
> it not Serializable. Both probably break existing applications.
> This is not my research, but has been discovered by other people.
> https://github.com/frohoff/ysoserial
> http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (COLLECTIONS-580) Arbitrary remote code execution with InvokerTransformer
[
https://issues.apache.org/jira/browse/COLLECTIONS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Bourg updated COLLECTIONS-580:
---
Comment: was deleted
(was:
I am on vacation from Jan 4, 2016 to Jan 15 2016. I will have periodic email
access and will respond to your mails as soon as possible .
thanks
Abhijeet
)
> Arbitrary remote code execution with InvokerTransformer
> ---
>
> Key: COLLECTIONS-580
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-580
> Project: Commons Collections
> Issue Type: Bug
>Affects Versions: 3.0, 4.0
>Reporter: Philippe Marschall
> Fix For: 3.2.2, 4.1
>
> Attachments: COLLECTIONS-580.patch
>
>
> With {{InvokerTransformer}} serializable collections can be build that
> execute arbitrary Java code.
> {{sun.reflect.annotation.AnnotationInvocationHandler#readObject}} invokes
> {{#entrySet}} and {{#get}} on a deserialized collection. If you have an
> endpoint that accepts serialized Java objects (JMX, RMI, remote EJB, ...) you
> can combine the two to create arbitrary remote code execution vulnerability.
> I don't know of a good fix short of removing {{InvokerTransformer}} or making
> it not Serializable. Both probably break existing applications.
> This is not my research, but has been discovered by other people.
> https://github.com/frohoff/ysoserial
> http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (COMPRESS-328) TarArchiveEntry preserveLeadingSlashes has no effect on setName
[
https://issues.apache.org/jira/browse/COMPRESS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085782#comment-15085782
]
Emmanuel Bourg commented on COMPRESS-328:
-
We may also add a {{setName(String, boolean)}} method and keep the current
behavior of {{setName(String)}}.
> TarArchiveEntry preserveLeadingSlashes has no effect on setName
> ---
>
> Key: COMPRESS-328
> URL: https://issues.apache.org/jira/browse/COMPRESS-328
> Project: Commons Compress
> Issue Type: Improvement
>Reporter: Torsten Curdt
>Priority: Minor
>
> We've run into an inconsistency with the TarArchiveEntry at jdeb.
> https://github.com/tcurdt/jdeb/issues/217
> You can create a `TarArchiveEntry(String name, boolean
> preserveLeadingSlashes)` but the `preserveLeadingSlashes` is only applied in
> the constructor.
> https://github.com/apache/commons-compress/blob/master/src/main/java/org/apache/commons/compress/archivers/tar/TarArchiveEntry.java#L392
> I am proposing to turn `preserveLeadingSlashes` into a read-only property and
> use the value on `setName()`, too (instead of just false).
> This has some implications and maybe some backwards compatibility issues -
> but even then I think it would be the right thing to do.
> I am happy to make the change but thought to discuss this first.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (COLLECTIONS-583) JAVA serialization vulnerability "CVE-2015-4852" in commons-collections*.jar
[ https://issues.apache.org/jira/browse/COLLECTIONS-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Bourg resolved COLLECTIONS-583. Resolution: Duplicate Fix Version/s: 4.1 3.2.2 > JAVA serialization vulnerability "CVE-2015-4852" in commons-collections*.jar > > > Key: COLLECTIONS-583 > URL: https://issues.apache.org/jira/browse/COLLECTIONS-583 > Project: Commons Collections > Issue Type: Bug >Reporter: Arnoj Saha > Fix For: 3.2.2, 4.1 > > > The vulnerability we are talking about is known under number CVE-2015-4852. > As far as we know this is only related to the > file commons-collections*.jar. In this jar file is a class that takes care of > the deserialization. > Currently we are using commons-collections-3.2.1.jar. > Is there a version of this jar that does not have this vulnerability? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
