[jira] [Resolved] (IO-677) FileSystem.getCurrent() does not return the correct enum
[ https://issues.apache.org/jira/browse/IO-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory resolved IO-677. Fix Version/s: 2.8 Resolution: Fixed > FileSystem.getCurrent() does not return the correct enum > > > Key: IO-677 > URL: https://issues.apache.org/jira/browse/IO-677 > Project: Commons IO > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Gary D. Gregory >Assignee: Gary D. Gregory >Priority: Major > Fix For: 2.8 > > > FileSystem.getCurrent() does not return the correct enum -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IO-677) FileSystem.getCurrent() does not return the correct enum
Gary D. Gregory created IO-677: -- Summary: FileSystem.getCurrent() does not return the correct enum Key: IO-677 URL: https://issues.apache.org/jira/browse/IO-677 Project: Commons IO Issue Type: Bug Affects Versions: 2.7 Reporter: Gary D. Gregory Assignee: Gary D. Gregory FileSystem.getCurrent() does not return the correct enum -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (VALIDATOR-246) EmailValidator should be able to recognize and remove comments
[ https://issues.apache.org/jira/browse/VALIDATOR-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-246. Fix Version/s: (was: 2.0) Resolution: Duplicate > EmailValidator should be able to recognize and remove comments > -- > > Key: VALIDATOR-246 > URL: https://issues.apache.org/jira/browse/VALIDATOR-246 > Project: Commons Validator > Issue Type: Improvement > Components: Routines >Affects Versions: 1.4.0 Release >Reporter: Ben Speakmon >Priority: Minor > > When EmailValidator was moved to routines and refactored, the functionality > for removing comments from emails was also removed due to its dependence on > oro and its lack of tests. It would be nice to have this redone with Java 1.4 > regexps (if it's needed at all). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (VALIDATOR-283) URLValidator should check for illegal Hex characters
[ https://issues.apache.org/jira/browse/VALIDATOR-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-283. Fix Version/s: 1.7 Resolution: Fixed commit f8e4d12aba0872b1f82fd26729a4a23b1bb5fc9e VALIDATOR-283 and VALIDATOR-472 --- src/changes/changes.xml| 6 ++ .../commons/validator/routines/UrlValidator.java | 71 +++--- .../validator/routines/UrlValidatorTest.java | 18 +- 3 files changed, 31 insertions(+), 64 deletions(-) > URLValidator should check for illegal Hex characters > > > Key: VALIDATOR-283 > URL: https://issues.apache.org/jira/browse/VALIDATOR-283 > Project: Commons Validator > Issue Type: Improvement > Components: Routines >Affects Versions: 1.3.1 Release >Reporter: RC Johnson >Priority: Minor > Fix For: 1.7 > > > URLs with illegal hex characters (because of invalid escape sequences) are > not detected as invalid. > Example: > http://finance.yahoo.com/news/Owners-54B-NY-housing-apf-2493139299.html?x=0&ap=%fr > UrlValidator.isValid() returns true, when it should return false. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (VALIDATOR-472) UrlValidator should not be more lax than java.net.URI
[ https://issues.apache.org/jira/browse/VALIDATOR-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-472. Fix Version/s: 1.7 Resolution: Fixed commit f8e4d12aba0872b1f82fd26729a4a23b1bb5fc9e VALIDATOR-283 and VALIDATOR-472 --- src/changes/changes.xml| 6 ++ .../commons/validator/routines/UrlValidator.java | 71 +++--- .../validator/routines/UrlValidatorTest.java | 18 +- 3 files changed, 31 insertions(+), 64 deletions(-) > UrlValidator should not be more lax than java.net.URI > - > > Key: VALIDATOR-472 > URL: https://issues.apache.org/jira/browse/VALIDATOR-472 > Project: Commons Validator > Issue Type: Bug > Components: Routines >Reporter: Sebb >Priority: Major > Fix For: 1.7 > > > UrlValidator should ensure that valid URLs are also valid as far as > java.net.URI is concerned. > i.e. if java.net.URI fails to parse the URL, it should not be considered > valid. > The validator still needs to do additional checks, e.g. to limit which > schemes are allowed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (VALIDATOR-472) UrlValidator should not be more lax than java.net.URI
Sebb created VALIDATOR-472: -- Summary: UrlValidator should not be more lax than java.net.URI Key: VALIDATOR-472 URL: https://issues.apache.org/jira/browse/VALIDATOR-472 Project: Commons Validator Issue Type: Bug Components: Routines Reporter: Sebb UrlValidator should ensure that valid URLs are also valid as far as java.net.URI is concerned. i.e. if java.net.URI fails to parse the URL, it should not be considered valid. The validator still needs to do additional checks, e.g. to limit which schemes are allowed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (VALIDATOR-243) Create standalone domain validator routine
[ https://issues.apache.org/jira/browse/VALIDATOR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated VALIDATOR-243: --- Fix Version/s: 1.4.1 Release > Create standalone domain validator routine > -- > > Key: VALIDATOR-243 > URL: https://issues.apache.org/jira/browse/VALIDATOR-243 > Project: Commons Validator > Issue Type: Task > Components: Routines >Reporter: Ben Speakmon >Assignee: Ben Speakmon >Priority: Major > Fix For: 1.4.1 Release > > > Since EmailValidator and UrlValidator both need domain name validation, and > since that logic is currently duplicated between them, that logic should be > factored out into a standalone routine for reuse by all. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (VALIDATOR-321) ISSN validator and converter to EAN-13
[ https://issues.apache.org/jira/browse/VALIDATOR-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated VALIDATOR-321: --- Fix Version/s: 1.5.0 > ISSN validator and converter to EAN-13 > -- > > Key: VALIDATOR-321 > URL: https://issues.apache.org/jira/browse/VALIDATOR-321 > Project: Commons Validator > Issue Type: Wish > Components: Routines >Reporter: Marco Janc >Priority: Major > Labels: validators > Fix For: 1.5.0 > > > Similar to the ISBNValidator an ISSNValidator would be a great feature. > Conversion from ISSN to EAN by adding the prefix "977" and "00" right before > the checkdigit to the issn code and recalculating the checksum similar to the > ISBN conversion method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (VALIDATOR-325) Improve IBAN validation with format checks
[ https://issues.apache.org/jira/browse/VALIDATOR-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated VALIDATOR-325: --- Fix Version/s: 1.5.0 > Improve IBAN validation with format checks > -- > > Key: VALIDATOR-325 > URL: https://issues.apache.org/jira/browse/VALIDATOR-325 > Project: Commons Validator > Issue Type: New Feature >Reporter: Wim Vleugels >Priority: Major > Fix For: 1.5.0 > > Attachments: IBANValidator.java > > > When I try to validate an incorrect belgian IBAN code "BE7436302152834", than > it passes the validation without any problem although even the length of the > code is invalid. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (VALIDATOR-363) UrlValidator rejects path having two or more successive dots
[
https://issues.apache.org/jira/browse/VALIDATOR-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated VALIDATOR-363:
---
Fix Version/s: 1.5.0
> UrlValidator rejects path having two or more successive dots
>
>
> Key: VALIDATOR-363
> URL: https://issues.apache.org/jira/browse/VALIDATOR-363
> Project: Commons Validator
> Issue Type: Bug
>Affects Versions: 1.4.1 Release
>Reporter: Stefan Pi
>Priority: Major
> Fix For: 1.5.0
>
> Attachments: VALIDATOR-363.patch
>
>
> Minmal example:
> {code}
> UrlValidator urlValidator = new UrlValidator();
> boolean isValidOneDot =
> urlValidator.isValid("http://www.example.org/hello.world/";); // evaluates to
> true
> boolean isValidTwoDots =
> urlValidator.isValid("http://www.example.org/hello..world/";); // evaluates to
> false
> {code}
> Real world example:
> {code}
> UrlValidator urlValidator = new UrlValidator();
> boolean isValidRealWord =
> urlValidator.isValid("http://forum.golem.de/sonstiges/trollwiese/apple-bashing-in-3...2...1...go/98,4089549,4089549,read.html#msg-4089549";);
> // evaluates to false
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (VALIDATOR-367) TLD list of DomainValidator is out of date (159 of 947 not available)
[ https://issues.apache.org/jira/browse/VALIDATOR-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated VALIDATOR-367: --- Fix Version/s: 1.5.0 > TLD list of DomainValidator is out of date (159 of 947 not available) > - > > Key: VALIDATOR-367 > URL: https://issues.apache.org/jira/browse/VALIDATOR-367 > Project: Commons Validator > Issue Type: Bug > Components: Routines >Affects Versions: 1.4.1 Release >Reporter: Ayoma Wijethunga >Priority: Major > Fix For: 1.5.0 > > Attachments: DomainValidator.java.patch > > > TLD list of DomainValidator is out of date. > 159 new TLDs out of 947 are not available in DomainValidator. > Until such time as a better method is implemented, adding new entries from > http://data.iana.org/TLD/tlds-alpha-by-domain.txt > Main reason for creating this issue is that unavailability of relevant TLDs > result in 16% failure in a local parameterised unit test, which tests against > email addressed from all possible TLDs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (VALIDATOR-364) Email Validator does not support quoted/escaped character in the local part of the email address
[
https://issues.apache.org/jira/browse/VALIDATOR-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated VALIDATOR-364:
---
Fix Version/s: 1.5.0
> Email Validator does not support quoted/escaped character in the local part
> of the email address
>
>
> Key: VALIDATOR-364
> URL: https://issues.apache.org/jira/browse/VALIDATOR-364
> Project: Commons Validator
> Issue Type: Bug
> Components: Routines
>Affects Versions: 1.4.1 Release
>Reporter: teo bran
>Priority: Major
> Fix For: 1.5.0
>
> Attachments: VALIDATOR-364.patch
>
>
> Currently the email address validator doesn't support to quote (or escape) a
> character in the local part of the address.
> Examples:
> {noformat}
> Abc\@d...@example.com
> Fred\ blo...@example.com
> Joe.\\b...@example.com
> {noformat}
> Source: [RFC 3696 | http://tools.ietf.org/html/rfc3696#section-3]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (VALIDATOR-380) UrlValidator does not allow for optional port digits
[ https://issues.apache.org/jira/browse/VALIDATOR-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated VALIDATOR-380: --- Fix Version/s: 1.5.0 > UrlValidator does not allow for optional port digits > > > Key: VALIDATOR-380 > URL: https://issues.apache.org/jira/browse/VALIDATOR-380 > Project: Commons Validator > Issue Type: Bug >Reporter: Sebb >Priority: Minor > Fix For: 1.5.0 > > > According to RFC 3986, the port number is defined as: > port= *DIGIT > This means 0 or more digits. > If it required at least one digit then it would be: > port= 1*DIGIT > However the code requires at least one digit. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (VALIDATOR-438) IBANValidator fails for El Salvador
[
https://issues.apache.org/jira/browse/VALIDATOR-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated VALIDATOR-438:
---
Fix Version/s: 1.7
> IBANValidator fails for El Salvador
> ---
>
> Key: VALIDATOR-438
> URL: https://issues.apache.org/jira/browse/VALIDATOR-438
> Project: Commons Validator
> Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Simon Marti
>Priority: Major
> Fix For: 1.7
>
>
> The {{IBANValidator}} does not validate the IBANs from El Salvador, even
> though they are part of the IBAN registry.
> E.g. {{SV62CENR00700025}} fails but should pass.
> See https://www.iban.com/structure.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (VALIDATOR-463) The DomainValidator doesn't work in a hot-reloading context because of the inUse flag
[
https://issues.apache.org/jira/browse/VALIDATOR-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165771#comment-17165771
]
Sebb commented on VALIDATOR-463:
See VALIDATOR-471; overrides can now be changed by creating a new instance
> The DomainValidator doesn't work in a hot-reloading context because of the
> inUse flag
> -
>
> Key: VALIDATOR-463
> URL: https://issues.apache.org/jira/browse/VALIDATOR-463
> Project: Commons Validator
> Issue Type: Wish
>Affects Versions: 1.6
> Environment: {code:java}
> {code}
>Reporter: Christian Kaps
>Priority: Major
>
> We use the DomainValidator in a Play Framework application. The issue is,
> that it breaks the development cycle, because of the following exception:
> {code:java}
> java.lang.IllegalStateException: Can only invoke this method before calling
> getInstance at
> org.apache.commons.validator.routines.DomainValidator.updateTLDOverride(DomainValidator.java:1919)
> {code}
> Play uses hot-reloading, which means that the application compiles changed
> code and reloads the Play server with the changes. So if I change some code,
> then the error occurs because the DomainValidator stores its internal state
> in a global variable. The code that calls `updateTLDOverride` is loaded by
> Guice as an eager singleton. There is no other earliest entry point for the
> application. There is a `clearTLDOverrides` method but this isn't accessible
> from my code. If I had access to this method, then I could add a shutdown
> hook, which could call it.
> The same issue occurs also in our integration tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (VALIDATOR-448) Tests failing on trunk
[
https://issues.apache.org/jira/browse/VALIDATOR-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb updated VALIDATOR-448:
---
Fix Version/s: 1.7
> Tests failing on trunk
> --
>
> Key: VALIDATOR-448
> URL: https://issues.apache.org/jira/browse/VALIDATOR-448
> Project: Commons Validator
> Issue Type: Bug
> Environment: ∴java -version
> java version "11" 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
> ∴jshell -version
> jshell 11
>
> Additionally verified on Java 10 and Java 9.
>
> Hopefully should not matter but worth noting:
> ∴locale
> LANG="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_CTYPE="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_ALL=
>Reporter: Eitan Adler
>Priority: Major
> Fix For: 1.7
>
>
> Commons Validator has failing tests on trunk. The failing tests boils down to
> this:
> {code:java}
> jshell> import org.apache.commons.validator.routines.CalendarValidator;
> jshell> var cv = new CalendarValidator();
> jshell> var i = CalendarValidator.getInstance();
> jshell> i.validate("31 Dez 2005", "dd MMM ", Locale.GERMAN);
> $9 ==> null{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (VALIDATOR-452) Validation of URL containing IPv4-mapped IPv6 address
[ https://issues.apache.org/jira/browse/VALIDATOR-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated VALIDATOR-452: --- Fix Version/s: 1.7 > Validation of URL containing IPv4-mapped IPv6 address > - > > Key: VALIDATOR-452 > URL: https://issues.apache.org/jira/browse/VALIDATOR-452 > Project: Commons Validator > Issue Type: Bug >Affects Versions: 1.4.1 Release, 1.5.0, 1.6 >Reporter: devson >Priority: Major > Fix For: 1.7 > > > Hello, > UrlValidator.isValid treats url containing ipv4-mapped ipv6 address as > invalid. For instance, this is valid url that is returned as invalid by the > validator- "http://[:::129.144.52.38]:80/index.html"; -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (VALIDATOR-470) EmailValidator does not recognize IP-Adresses
[ https://issues.apache.org/jira/browse/VALIDATOR-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165728#comment-17165728 ] Sebb commented on VALIDATOR-470: hostname is not the same as domain name > EmailValidator does not recognize IP-Adresses > - > > Key: VALIDATOR-470 > URL: https://issues.apache.org/jira/browse/VALIDATOR-470 > Project: Commons Validator > Issue Type: Bug >Reporter: Lonzak >Priority: Major > > email@123.123.123.123 > is considered an invalid. This is not correct. > Strangely "email@[123.123.123.123]" is considered to be valid... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (VALIDATOR-471) Allow DomainValidator overrides at run-time
[ https://issues.apache.org/jira/browse/VALIDATOR-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated VALIDATOR-471: --- Fix Version/s: 1.7 > Allow DomainValidator overrides at run-time > --- > > Key: VALIDATOR-471 > URL: https://issues.apache.org/jira/browse/VALIDATOR-471 > Project: Commons Validator > Issue Type: Bug >Reporter: Sebb >Priority: Major > Fix For: 1.7 > > > It would be useful to allow DomainValidator instances to be created with > different overrides. > Currently this is not possible because there are only two cached instances. > As such, it's not possible to make changes after initialisation. > The class could be extended allow further instances to be created, whilst > still keeping the existing behaviour for the cached instances. > This would allow users to create further instances with local changes to the > Generic and CountryCode lists. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (VALIDATOR-445) Inet6Address may also contain a scope id
[ https://issues.apache.org/jira/browse/VALIDATOR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-445. Fix Version/s: 1.7 Resolution: Fixed commit 6d045cbf8613e938c634f0c96305b601aa55dc7d VALIDATOR-445 Inet6Address scope id and bit size --- src/changes/changes.xml| 11 +--- .../validator/routines/InetAddressValidator.java | 30 +- .../routines/InetAddressValidatorTest.java | 28 3 files changed, 64 insertions(+), 5 deletions(-) > Inet6Address may also contain a scope id > > > Key: VALIDATOR-445 > URL: https://issues.apache.org/jira/browse/VALIDATOR-445 > Project: Commons Validator > Issue Type: Bug >Reporter: devson >Priority: Major > Fix For: 1.7 > > > InetAddressValidator.isValidInet6Address incorrectly returns false for IPv6 > address that contains a scope id such as in this: > fe80:0:0:0:c1e1:54cf:68bc:9d5e%12 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (VALIDATOR-445) Inet6Address may also contain a scope id
[ https://issues.apache.org/jira/browse/VALIDATOR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165693#comment-17165693 ] Sebb commented on VALIDATOR-445: I can confirm that the current implementation does not support scope zones introduced by the '%' character. Nor does it support the /dd bit prefix length specifier > Inet6Address may also contain a scope id > > > Key: VALIDATOR-445 > URL: https://issues.apache.org/jira/browse/VALIDATOR-445 > Project: Commons Validator > Issue Type: Bug >Reporter: devson >Priority: Major > > InetAddressValidator.isValidInet6Address incorrectly returns false for IPv6 > address that contains a scope id such as in this: > fe80:0:0:0:c1e1:54cf:68bc:9d5e%12 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (VALIDATOR-267) Email Validator doesn't cope with domain comments, valid user@tld addresses and folding whitespace
[ https://issues.apache.org/jira/browse/VALIDATOR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165641#comment-17165641 ] Sebb commented on VALIDATOR-267: Validator does currently allow user@com. However comments and folding whitespace are not allowed. > Email Validator doesn't cope with domain comments, valid user@tld addresses > and folding whitespace > -- > > Key: VALIDATOR-267 > URL: https://issues.apache.org/jira/browse/VALIDATOR-267 > Project: Commons Validator > Issue Type: Bug >Reporter: Chris Wareham >Priority: Major > > The class org.apache.commons.validator.routines.EmailValidator rejects > certain valid email address constructs. According to RFC2822, domain names > are allowed to have comments in parentheses, addresses of the form user@tld > are legal (albeit rare) and folding whitespace is allowed. Examples are as > follows: > user@(a domain comment)foo.com" > user@com > Test \ > Folding \ > whitesp...@foo.com -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (MATH-1551) Compute Percentile with Weighted Samples
[ https://issues.apache.org/jira/browse/MATH-1551?focusedWorklogId=463583&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-463583 ] ASF GitHub Bot logged work on MATH-1551: Author: ASF GitHub Bot Created on: 27/Jul/20 10:28 Start Date: 27/Jul/20 10:28 Worklog Time Spent: 10m Work Description: coveralls edited a comment on pull request #157: URL: https://github.com/apache/commons-math/pull/157#issuecomment-663976272 [](https://coveralls.io/builds/32340725) Coverage decreased (-0.1%) to 90.817% when pulling **96f1480b048e9b6c6aeafb0f2e4e94f745db49e0 on iii-org-tw:MATH-1551-WeightedPercentile** into **d0ed03c953bf436fc4dc32260c6018a7791c9efc on apache:master**. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 463583) Time Spent: 0.5h (was: 20m) > Compute Percentile with Weighted Samples > > > Key: MATH-1551 > URL: https://issues.apache.org/jira/browse/MATH-1551 > Project: Commons Math > Issue Type: New Feature >Affects Versions: 4.0 >Reporter: institute for information industry >Priority: Major > Labels: features, newbie > Fix For: 4.0 > > Attachments: Percentile.java > > Time Spent: 0.5h > Remaining Estimate: 0h > > The class Percentile only support estimation on non-weighted samples. > I've implement some function to estimate percentiles of weighted samples. > here is the reference: > [https://stats.stackexchange.com/questions/13169/defining-quantiles-over-a-weighted-sample]!https://mail.google.com/mail/u/0?ui=2&ik=6059a2f2a6&attid=0.1&permmsgid=msg-a:r-8896240918589631988&th=1737bdaafc3e228f&view=fimg&sz=s0-l75-ft&attbid=ANGjdJ_GwCQ-hqi0o7ZJTEqcl6JLYbFiR2Y1sqxPL8jDNzheraAkX0beEUtAM4BYI2v_5XGvzCPj2gTBQutHT9bF8hYh7MgdiGYZhn0HtDuVswuCSuwy8aJVsvy3EqI&disp=emb&realattid=ii_kcyrjgea0! > > When all weights are equal to each other, it works like estimation on > non-weighted samples under R-7. > I can't find formulas for other rules but at least, now it can evaluate > percentile for weighted samples. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [commons-math] coveralls edited a comment on pull request #157: MATH-1551: Add Weighted percentile features
coveralls edited a comment on pull request #157: URL: https://github.com/apache/commons-math/pull/157#issuecomment-663976272 [](https://coveralls.io/builds/32340725) Coverage decreased (-0.1%) to 90.817% when pulling **96f1480b048e9b6c6aeafb0f2e4e94f745db49e0 on iii-org-tw:MATH-1551-WeightedPercentile** into **d0ed03c953bf436fc4dc32260c6018a7791c9efc on apache:master**. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (VALIDATOR-470) EmailValidator does not recognize IP-Adresses
[ https://issues.apache.org/jira/browse/VALIDATOR-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165496#comment-17165496 ] Lonzak commented on VALIDATOR-470: -- Ok but according to rfc2822 it is a valid domain name. > EmailValidator does not recognize IP-Adresses > - > > Key: VALIDATOR-470 > URL: https://issues.apache.org/jira/browse/VALIDATOR-470 > Project: Commons Validator > Issue Type: Bug >Reporter: Lonzak >Priority: Major > > email@123.123.123.123 > is considered an invalid. This is not correct. > Strangely "email@[123.123.123.123]" is considered to be valid... -- This message was sent by Atlassian Jira (v8.3.4#803005)
