[jira] [Updated] (JEXL-399) Needs support more javascript syntax
[
https://issues.apache.org/jira/browse/JEXL-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Pengcheng updated JEXL-399:
--
Description:
Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
lightweight, secure, easy to communicate with host solution, I think is the
best option for java world as a bridge between chatgpt and app.
Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
ask chatgpt to write as javascript, I had implements most of the javascript
build-in objects (like Array, Object, Math, console, etc) for JEXL, 95% cases
generated by chatgpt can run successfully.
However, some syntax error will cause the 5% failure, for example:
# a === b
# a !== b
# a = b ** 2
# const \{a, b} = x;
# a = \{x: 1, y: 2,}
# func = () => (\{"a":1, "b": 2})
# for (let k in map)
# for (ket value of map)
These syntax looks very reasonable, It will be great to support these
javascript syntax to let both chatgpt and developer easy to use.
Thanks!
was:
Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
lightweight, secure, easy to communicate with host solution, I think is the
best option for java world as a bridge between chatgpt and app.
Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
ask chatgpt to write as javascript, I had implements most of the javascript
build-in objects (like Array, Object, Math, console, etc) for JEXL, 95% cases
generated by chatgpt can run successfully.
However, some syntax error will cause the 5% failure, for example:
# a === b
# a !== b
# a = b ** 2
# const \{a, b} = x;
# a = \{x: 1, y: 2,}
# func = () => (\{"a":1, "b": 2})
These syntax looks very reasonable, It will be great to support these
javascript syntax to let both chatgpt and developer easy to use.
Thanks!
> Needs support more javascript syntax
>
>
> Key: JEXL-399
> URL: https://issues.apache.org/jira/browse/JEXL-399
> Project: Commons JEXL
> Issue Type: New Feature
>Reporter: Xu Pengcheng
>Priority: Major
>
> Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
> lightweight, secure, easy to communicate with host solution, I think is the
> best option for java world as a bridge between chatgpt and app.
> Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
> ask chatgpt to write as javascript, I had implements most of the javascript
> build-in objects (like Array, Object, Math, console, etc) for JEXL, 95% cases
> generated by chatgpt can run successfully.
> However, some syntax error will cause the 5% failure, for example:
> # a === b
> # a !== b
> # a = b ** 2
> # const \{a, b} = x;
> # a = \{x: 1, y: 2,}
> # func = () => (\{"a":1, "b": 2})
> # for (let k in map)
> # for (ket value of map)
> These syntax looks very reasonable, It will be great to support these
> javascript syntax to let both chatgpt and developer easy to use.
> Thanks!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JEXL-399) Needs support more javascript syntax
[
https://issues.apache.org/jira/browse/JEXL-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Pengcheng updated JEXL-399:
--
Description:
Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
lightweight, secure, easy to communicate with host solution, I think is the
best option for java world as a bridge between chatgpt and app.
Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
ask chatgpt to write as javascript, I had implements most of the javascript
build-in objects (like Array, Object, Math, console, etc) for JEXL, 95% cases
generated by chatgpt can run successfully.
However, some syntax error will cause the 5% failure, for example:
# a === b
# a !== b
# a = b ** 2
# const \{a, b} = x;
# a = \{x: 1, y: 2,}
# func = () => (\{"a":1, "b": 2})
# for (let k in map)
# for (let value of map)
These syntax looks very reasonable, It will be great to support these
javascript syntax to let both chatgpt and developer easy to use.
Thanks!
was:
Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
lightweight, secure, easy to communicate with host solution, I think is the
best option for java world as a bridge between chatgpt and app.
Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
ask chatgpt to write as javascript, I had implements most of the javascript
build-in objects (like Array, Object, Math, console, etc) for JEXL, 95% cases
generated by chatgpt can run successfully.
However, some syntax error will cause the 5% failure, for example:
# a === b
# a !== b
# a = b ** 2
# const \{a, b} = x;
# a = \{x: 1, y: 2,}
# func = () => (\{"a":1, "b": 2})
# for (let k in map)
# for (ket value of map)
These syntax looks very reasonable, It will be great to support these
javascript syntax to let both chatgpt and developer easy to use.
Thanks!
> Needs support more javascript syntax
>
>
> Key: JEXL-399
> URL: https://issues.apache.org/jira/browse/JEXL-399
> Project: Commons JEXL
> Issue Type: New Feature
>Reporter: Xu Pengcheng
>Priority: Major
>
> Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
> lightweight, secure, easy to communicate with host solution, I think is the
> best option for java world as a bridge between chatgpt and app.
> Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
> ask chatgpt to write as javascript, I had implements most of the javascript
> build-in objects (like Array, Object, Math, console, etc) for JEXL, 95% cases
> generated by chatgpt can run successfully.
> However, some syntax error will cause the 5% failure, for example:
> # a === b
> # a !== b
> # a = b ** 2
> # const \{a, b} = x;
> # a = \{x: 1, y: 2,}
> # func = () => (\{"a":1, "b": 2})
> # for (let k in map)
> # for (let value of map)
> These syntax looks very reasonable, It will be great to support these
> javascript syntax to let both chatgpt and developer easy to use.
> Thanks!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [commons-pool] psteitz commented on pull request #228: POOL-391 fixes, docs
psteitz commented on PR #228: URL: https://github.com/apache/commons-pool/pull/228#issuecomment-1624547407 Yes, I think this is the same failure in POOL-411. Very rare, so good the CI caught it. -- 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. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-pool] garydgregory commented on pull request #228: POOL-391 fixes, docs
garydgregory commented on PR #228: URL: https://github.com/apache/commons-pool/pull/228#issuecomment-1624529441 Capturing some sample failures for when the build logs age out: ``` [INFO] Running org.apache.commons.pool2.pool407.Pool407Test Error: Exception in thread "pool-3-thread-4" java.lang.RuntimeException: java.lang.NullPointerException: Pool407NullObjectFactory.makeObject() = null at org.apache.commons.pool2.pool407.Pool407Test$Pool407RoundtripRunnable.run(Pool407Test.java:51) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:833) Caused by: java.lang.NullPointerException: Pool407NullObjectFactory.makeObject() = null at org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:568) at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:299) at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:227) at org.apache.commons.pool2.pool407.Pool407Test$Pool407RoundtripRunnable.run(Pool407Test.java:46) ... 3 more Error: Exception in thread "pool-3-thread-1" java.lang.RuntimeException: java.lang.NullPointerException: Pool407NullObjectFactory.makeObject() = null at org.apache.commons.pool2.pool407.Pool407Test$Pool407RoundtripRunnable.run(Pool407Test.java:51) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:833) Caused by: java.lang.NullPointerException: Pool407NullObjectFactory.makeObject() = null at org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:568) at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:299) at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:227) at org.apache.commons.pool2.pool407.Pool407Test$Pool407RoundtripRunnable.run(Pool407Test.java:46) ... 3 more ``` -- 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. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-scxml] garydgregory merged pull request #137: Bump Saxon-HE from 12.2 to 12.3
garydgregory merged PR #137: URL: https://github.com/apache/commons-scxml/pull/137 -- 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. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-io] garydgregory merged pull request #465: Bump jimfs from 1.2 to 1.3.0
garydgregory merged PR #465: URL: https://github.com/apache/commons-io/pull/465 -- 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. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (JEXL-399) Needs support more javascript syntax
[
https://issues.apache.org/jira/browse/JEXL-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Pengcheng updated JEXL-399:
--
Description:
Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
lightweight, secure, easy to communicate with host solution, I think is the
best option for java world as a bridge between chatgpt and app.
Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
ask chatgpt to write as javascript, I had implements most of the javascript
build-in objects (like Array, Object, Math, console, etc) for JEXL, 95% cases
generated by chatgpt can run successfully.
However, some syntax error will cause the failure, for example:
# a === b
# a !== b
# a = b ** 2
# const \{a, b} = x;
# a = \{x: 1, y: 2,}
# func = () => (\{"a":1, "b": 2})
These syntax looks very reasonable, It will be great to support these
javascript syntax to let both chatgpt and developer easy to use.
Thanks!
was:
Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
lightweight, secure, easy to communicate with host solution, I think is the
best option for java world as a bridge between chatgpt and app.
Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
ask chatgpt to write as javascript, and I had implements most of the javascript
build-in objects (like Array, Object, Math, console, etc) for JEXL, and 95%
cases generated by chatgpt can run successfully.
However, some syntax error will cause the failure, for example:
# a === b
# a !== b
# a = b ** 2
# const \{a, b} = x;
# a = \{x: 1, y: 2,}
# func = () => (\{"a":1, "b": 2})
These syntax looks very reasonable, It will be great to support these
javascript syntax to let both chatgpt and developer easy to use.
Thanks!
> Needs support more javascript syntax
>
>
> Key: JEXL-399
> URL: https://issues.apache.org/jira/browse/JEXL-399
> Project: Commons JEXL
> Issue Type: New Feature
>Reporter: Xu Pengcheng
>Priority: Major
>
> Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
> lightweight, secure, easy to communicate with host solution, I think is the
> best option for java world as a bridge between chatgpt and app.
> Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
> ask chatgpt to write as javascript, I had implements most of the javascript
> build-in objects (like Array, Object, Math, console, etc) for JEXL, 95% cases
> generated by chatgpt can run successfully.
> However, some syntax error will cause the failure, for example:
> # a === b
> # a !== b
> # a = b ** 2
> # const \{a, b} = x;
> # a = \{x: 1, y: 2,}
> # func = () => (\{"a":1, "b": 2})
> These syntax looks very reasonable, It will be great to support these
> javascript syntax to let both chatgpt and developer easy to use.
> Thanks!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JEXL-399) Needs support more javascript syntax
[
https://issues.apache.org/jira/browse/JEXL-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Pengcheng updated JEXL-399:
--
Description:
Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
lightweight, secure, easy to communicate with host solution, I think is the
best option for java world as a bridge between chatgpt and app.
Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
ask chatgpt to write as javascript, I had implements most of the javascript
build-in objects (like Array, Object, Math, console, etc) for JEXL, 95% cases
generated by chatgpt can run successfully.
However, some syntax error will cause the 5% failure, for example:
# a === b
# a !== b
# a = b ** 2
# const \{a, b} = x;
# a = \{x: 1, y: 2,}
# func = () => (\{"a":1, "b": 2})
These syntax looks very reasonable, It will be great to support these
javascript syntax to let both chatgpt and developer easy to use.
Thanks!
was:
Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
lightweight, secure, easy to communicate with host solution, I think is the
best option for java world as a bridge between chatgpt and app.
Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
ask chatgpt to write as javascript, I had implements most of the javascript
build-in objects (like Array, Object, Math, console, etc) for JEXL, 95% cases
generated by chatgpt can run successfully.
However, some syntax error will cause the failure, for example:
# a === b
# a !== b
# a = b ** 2
# const \{a, b} = x;
# a = \{x: 1, y: 2,}
# func = () => (\{"a":1, "b": 2})
These syntax looks very reasonable, It will be great to support these
javascript syntax to let both chatgpt and developer easy to use.
Thanks!
> Needs support more javascript syntax
>
>
> Key: JEXL-399
> URL: https://issues.apache.org/jira/browse/JEXL-399
> Project: Commons JEXL
> Issue Type: New Feature
>Reporter: Xu Pengcheng
>Priority: Major
>
> Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
> lightweight, secure, easy to communicate with host solution, I think is the
> best option for java world as a bridge between chatgpt and app.
> Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
> ask chatgpt to write as javascript, I had implements most of the javascript
> build-in objects (like Array, Object, Math, console, etc) for JEXL, 95% cases
> generated by chatgpt can run successfully.
> However, some syntax error will cause the 5% failure, for example:
> # a === b
> # a !== b
> # a = b ** 2
> # const \{a, b} = x;
> # a = \{x: 1, y: 2,}
> # func = () => (\{"a":1, "b": 2})
> These syntax looks very reasonable, It will be great to support these
> javascript syntax to let both chatgpt and developer easy to use.
> Thanks!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JEXL-399) Needs support more javascript syntax
[
https://issues.apache.org/jira/browse/JEXL-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Pengcheng updated JEXL-399:
--
Description:
Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
lightweight, secure, easy to communicate with host solution, I think is the
best option for java world.
Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
ask chatgpt to write as javascript, and I had implements most of the javascript
build-in objects (like Array, Object, Math, console, etc) for JEXL, and 95%
cases generated by chatgpt can run successfully.
However, some syntax error will cause the failure, for example:
# a === b
# a !== b
# a = b ** 2
# const \{a, b} = x;
# a = \{x: 1, y: 2,}
# func = () => (\{"a":1, "b": 2})
These syntax looks very reasonable, It will be great to support these
javascript syntax to let both chatgpt and developer easy to use.
Thanks!
was:
Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
lightweight, secure, easy to communicate with host solution, I think is the
best option for java world.
Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
ask chatgpt to write as javascript, and I had implements most of the javascript
build-in objects (like Array, Object, Math, console, etc) for JEXL, and 95%
cases generated by chatgpt can run successfully.
However, some syntax error will cause the failure, for example:
# a === b
# a !== b
# a = b ** 2
# const \{a, b} = x;
# a = \{x: 1, y: 2,}
# func = () => (\{"a":1, "b": 2})
These syntax looks very reasonable, It will be great to support these
javascript syntax to let both chatgpt and developer easy to use.
> Needs support more javascript syntax
>
>
> Key: JEXL-399
> URL: https://issues.apache.org/jira/browse/JEXL-399
> Project: Commons JEXL
> Issue Type: New Feature
>Reporter: Xu Pengcheng
>Priority: Major
>
> Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
> lightweight, secure, easy to communicate with host solution, I think is the
> best option for java world.
> Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
> ask chatgpt to write as javascript, and I had implements most of the
> javascript build-in objects (like Array, Object, Math, console, etc) for
> JEXL, and 95% cases generated by chatgpt can run successfully.
> However, some syntax error will cause the failure, for example:
> # a === b
> # a !== b
> # a = b ** 2
> # const \{a, b} = x;
> # a = \{x: 1, y: 2,}
> # func = () => (\{"a":1, "b": 2})
> These syntax looks very reasonable, It will be great to support these
> javascript syntax to let both chatgpt and developer easy to use.
> Thanks!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JEXL-399) Needs support more javascript syntax
[
https://issues.apache.org/jira/browse/JEXL-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Pengcheng updated JEXL-399:
--
Description:
Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
lightweight, secure, easy to communicate with host solution, I think is the
best option for java world as a bridge between chatgpt and app.
Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
ask chatgpt to write as javascript, and I had implements most of the javascript
build-in objects (like Array, Object, Math, console, etc) for JEXL, and 95%
cases generated by chatgpt can run successfully.
However, some syntax error will cause the failure, for example:
# a === b
# a !== b
# a = b ** 2
# const \{a, b} = x;
# a = \{x: 1, y: 2,}
# func = () => (\{"a":1, "b": 2})
These syntax looks very reasonable, It will be great to support these
javascript syntax to let both chatgpt and developer easy to use.
Thanks!
was:
Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
lightweight, secure, easy to communicate with host solution, I think is the
best option for java world.
Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
ask chatgpt to write as javascript, and I had implements most of the javascript
build-in objects (like Array, Object, Math, console, etc) for JEXL, and 95%
cases generated by chatgpt can run successfully.
However, some syntax error will cause the failure, for example:
# a === b
# a !== b
# a = b ** 2
# const \{a, b} = x;
# a = \{x: 1, y: 2,}
# func = () => (\{"a":1, "b": 2})
These syntax looks very reasonable, It will be great to support these
javascript syntax to let both chatgpt and developer easy to use.
Thanks!
> Needs support more javascript syntax
>
>
> Key: JEXL-399
> URL: https://issues.apache.org/jira/browse/JEXL-399
> Project: Commons JEXL
> Issue Type: New Feature
>Reporter: Xu Pengcheng
>Priority: Major
>
> Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
> lightweight, secure, easy to communicate with host solution, I think is the
> best option for java world as a bridge between chatgpt and app.
> Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
> ask chatgpt to write as javascript, and I had implements most of the
> javascript build-in objects (like Array, Object, Math, console, etc) for
> JEXL, and 95% cases generated by chatgpt can run successfully.
> However, some syntax error will cause the failure, for example:
> # a === b
> # a !== b
> # a = b ** 2
> # const \{a, b} = x;
> # a = \{x: 1, y: 2,}
> # func = () => (\{"a":1, "b": 2})
> These syntax looks very reasonable, It will be great to support these
> javascript syntax to let both chatgpt and developer easy to use.
> Thanks!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (JEXL-399) Needs support more javascript syntax
Xu Pengcheng created JEXL-399:
-
Summary: Needs support more javascript syntax
Key: JEXL-399
URL: https://issues.apache.org/jira/browse/JEXL-399
Project: Commons JEXL
Issue Type: New Feature
Reporter: Xu Pengcheng
Hi, I am trying ask chatgpt to generate code for some cases, JEXL, as a
lightweight, secure, easy to communicate with host solution, I think is the
best option for java world.
Unfortunately, chatgpt seems is not familiar with Jexl syntax, so I tried to
ask chatgpt to write as javascript, and I had implements most of the javascript
build-in objects (like Array, Object, Math, console, etc) for JEXL, and 95%
cases generated by chatgpt can run successfully.
However, some syntax error will cause the failure, for example:
# a === b
# a !== b
# a = b ** 2
# const \{a, b} = x;
# a = \{x: 1, y: 2,}
# func = () => (\{"a":1, "b": 2})
These syntax looks very reasonable, It will be great to support these
javascript syntax to let both chatgpt and developer easy to use.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (POOL-411) NPE when deregistering key at end of borrow
[
https://issues.apache.org/jira/browse/POOL-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz reopened POOL-411:
--
The added test case has failed at least once now. I think there is a problem
with register/deregister protection of pools. Very low probability, but the
following seems like it could happen:
Thread 1
# Enter register
# get the read lock
# get a non-null, existing pool
Thread 2
# Clear the pool
# Deregister and remove it
Thread 1
# Register interest in the now orphaned pool
This may be possible because deregister can escalate to write lock while others
are holding read locks. The Thread 2 actions have to happen between two
instructions in register (when it gets the pool and when it increments its
numInterested).
> NPE when deregistering key at end of borrow
> ---
>
> Key: POOL-411
> URL: https://issues.apache.org/jira/browse/POOL-411
> Project: Commons Pool
> Issue Type: Task
>Affects Versions: 2.11.1
>Reporter: Richard Eckart de Castilho
>Priority: Major
> Fix For: 2.12.0
>
>
> There is a potential for an NPE happening in the finally block of
> borrowObject:
> {noformat}
> Caused by: java.lang.NullPointerException: Cannot invoke
> "org.apache.commons.pool2.impl.GenericKeyedObjectPool$ObjectDeque.getNumInterested()"
> because "objectDeque" is null
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.deregister(GenericKeyedObjectPool.java:821)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:507)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:350)
>
> {noformat}
> From reading the code, it seems this could happen e.g. if a pool is
> concurrently cleared while a borrow is in progress.
> Not sure what a proper solution here would be. Maybe deregister should
> silently do nothing if poolMap.get(k) returns null?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [commons-pool] psteitz opened a new pull request, #228: POOL-391 fixes, docs
psteitz opened a new pull request, #228: URL: https://github.com/apache/commons-pool/pull/228 (no comment) -- 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. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (MATH-1656) Classical multivariate optimizers (gradient descent, Raphson-Newton, BFGS) are missing
[
https://issues.apache.org/jira/browse/MATH-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17740671#comment-17740671
]
Gilles Sadowski edited comment on MATH-1656 at 7/6/23 6:13 PM:
---
{quote}please find a patch with a provisional version [...]
{quote}
Thanks!
Here is a (probably non-exhaustive) list of issues from a first look.
# The default build fails. Log excerpt:
{noformat}
[...]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:3.0.0:test (default-test) on
project commons-math4-legacy:
Please refer to
/home/gilles/gilles/devel/java/apache/commons-math/trunk/commons-math-legacy/target/surefire-reports
for the individual test results.
Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump
and [date].dumpstream.
There was an error in the forked process
Error occurred in starting fork, check output in log
0
java.lang.SecurityException: 0
at
org.apache.commons.math4.test.util.DiffTest$TestSecurityManager.checkExit(DiffTest.java:150)
at java.base/java.lang.Runtime.exit(Runtime.java:114)
at java.base/java.lang.System.exit(System.java:1752)
at
org.apache.maven.surefire.booter.ForkedBooter.acknowledgedExit(ForkedBooter.java:381)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:178)
at
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
[...]
{noformat}
# Files location of
** *source code* is in directory
{noformat}
commons-math-legacy/src/main/java/org/apache/commons/math4/optim/
{noformat}
but should be in
{noformat}
commons-math-legacy/src/main/java/org/apache/commons/math4/legacy/optim/
{noformat}
** *test source code* is in directory
{noformat}
commons-math-legacy/src/test/java/org/apache/commons/math4/optim/
{noformat}
but should be in
{noformat}
commons-math-legacy/src/test/java/org/apache/commons/math4/legacy/optim/
{noformat}
** *(test) resources* are in directory
{noformat}
commons-math-legacy/src/test/resources/org/apache/commons/math4/optim
{noformat}
but should be in
{noformat}
commons-math-legacy/src/test/resources/org/apache/commons/math4/legacy/optim
{noformat}
# Strange (spurious ?) files in resources directories:
** {{stdout.txt}}
** {{stderr.txt}}
** {{status.txt}}
# Additions to the _public_ API need prior discussion (to avoid code bloat),
e.g.
** {{DebugMode}}
** {{DoubleData}}
** {{DoubleStrictlyPostiveData}}
** {{ObjectiveFunctionDimension}}
** {{OptimizationStatus}}
** {{SearchRange}}
** {{MinDirectionNorm}}
** {{LinearUtil}}
** ...
# {{LinearUtil}} defines many utilities already present in (or that should
belong to) class
[{{MathArrays}}|https://github.com/apache/commons-math/blob/master/commons-math-legacy-core/src/main/java/org/apache/commons/math4/legacy/core/MathArrays.java].
# The test infrastructure may be a neat idea (I didn't look at the details)
but it completely departs from the existing approach (Junit 4) and the expected
upgrade path using Junit 5 features (see e.g. in
["SimplexOptimizerTest.java"|https://github.com/apache/commons-math/blob/master/commons-math-legacy/src/test/java/org/apache/commons/math4/legacy/optim/nonlinear/scalar/noderiv/SimplexOptimizerTest.java])
# New _public_ or _protected_ methods (like {{{}initOptimization{}}}) should
be discussed.
Other, comparatively smaller, issues:
* We don't use {{@author}} tags.
* All fields and methods (including _private_ ones) must be documented.
* Abbreviated names should be avoided ({{{}initOptimization{}}} for example
should be {{{}initializeOptimization{}}}, or perhaps just {{{}initialize{}}})
unless they have become "well-known" (like "BFGS" maybe).
* The "default constructor" should not be explicitly declared.
was (Author: erans):
{quote}please find a patch with a provisional version [...]
{quote}
Thanks!
Here is a (probably non-exhaustive) list of issues from a first look.
# The default build fails. Log excerpt:
{noformat}
[...]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:3.0.0:test (default-test) on
project commons-math4-legacy:
Please refer to
/home/gilles/gilles/devel/java/apache/commons-math/trunk/commons-math-legacy/target/surefire-reports
for the individual test results.
Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump
and [date].dumpstream.
There was an error in the forked process
Error occurred in starting fork, check output in log
0
java.lang.SecurityException: 0
at
org.apache.commons.math4.test.util.DiffTest$TestSecurityManager.checkExit(DiffTest.java:150)
at java.base/java.lang.Runtime.exit(Runtime.java:114)
at
[jira] [Resolved] (JEXL-398) Allow 'trailing commas' or ellipsis while defining array, map and set literals
[
https://issues.apache.org/jira/browse/JEXL-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro resolved JEXL-398.
Resolution: Fixed
Commit
[ab1a6d9|https://github.com/apache/commons-jexl/commit/ab1a6d9c3c32fd9c5e49def7fe8f1763dce09d7d]
> Allow 'trailing commas' or ellipsis while defining array, map and set literals
> --
>
> Key: JEXL-398
> URL: https://issues.apache.org/jira/browse/JEXL-398
> Project: Commons JEXL
> Issue Type: New Feature
>Affects Versions: 3.3
>Reporter: Xu Pengcheng
>Assignee: Henri Biestro
>Priority: Minor
> Fix For: 3.3.1
>
>
> Allowing trailing commas in structured literals (array, set, map) as a
> convenient syntactic leniency. :)
> {code:java}
> let m = { "foo": 1, "bar": 2, };
> let a = [ 1, 2, ];
> let s = (1, 2, );{code}
> Using a trailing ellipsis (...) to alter the concrete class materialized as a
> convenient semantic shortcut.
> {code:java}
> let m = { "foo": 1, "bar": 2, ... }; // LinkedHashMap
> let a = [ 1, 2, ...]; // ArrayList
> let s = (1, 2, ...); // LinkedHashSet{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MATH-1656) Classical multivariate optimizers (gradient descent, Raphson-Newton, BFGS) are missing
[
https://issues.apache.org/jira/browse/MATH-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17740671#comment-17740671
]
Gilles Sadowski commented on MATH-1656:
---
{quote}please find a patch with a provisional version [...]
{quote}
Thanks!
Here is a (probably non-exhaustive) list of issues from a first look.
# The default build fails. Log excerpt:
{noformat}
[...]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:3.0.0:test (default-test) on
project commons-math4-legacy:
Please refer to
/home/gilles/gilles/devel/java/apache/commons-math/trunk/commons-math-legacy/target/surefire-reports
for the individual test results.
Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump
and [date].dumpstream.
There was an error in the forked process
Error occurred in starting fork, check output in log
0
java.lang.SecurityException: 0
at
org.apache.commons.math4.test.util.DiffTest$TestSecurityManager.checkExit(DiffTest.java:150)
at java.base/java.lang.Runtime.exit(Runtime.java:114)
at java.base/java.lang.System.exit(System.java:1752)
at
org.apache.maven.surefire.booter.ForkedBooter.acknowledgedExit(ForkedBooter.java:381)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:178)
at
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
[...]
{noformat}
# Files location of
** *source code* is in directory
{noformat}
commons-math-legacy/src/main/java/org/apache/commons/math4/optim/
{noformat}
but should be in
{noformat}
commons-math-legacy/src/main/java/org/apache/commons/math4/legacy/optim/
{noformat}
** *test source code* is in directory
{noformat}
commons-math-legacy/src/test/java/org/apache/commons/math4/optim/
{noformat}
but should be in
{noformat}
commons-math-legacy/src/test/java/org/apache/commons/math4/legacy/optim/
{noformat}
** *(test) resources* are in directory
{noformat}
commons-math-legacy/src/test/resources/org/apache/commons/math4/optim
{noformat}
but should be in
{noformat}
commons-math-legacy/src/test/resources/org/apache/commons/math4/legacy/optim
{noformat}
# Strange (spurious ?) files in resources directories:
** {{stdout.txt}}
** {{stderr.txt}}
** {{status.txt}}
# Additions to the _public_ API need prior discussion (to avoid code bloat),
e.g.
** {{DebugMode}}
** {{DoubleData}}
** {{DoubleStrictlyPostiveData}}
** {{ObjectiveFunctionDimension}}
** {{OptimizationStatus}}
** {{SearchRange}}
** {{MinDirectionNorm}}
** {{LinearUtil}}
** ...
# {{LinearUtil}} defines many utilities already present in (or that should
belong to) class
[{{MathArrays}}|https://github.com/apache/commons-math/blob/master/commons-math-legacy-core/src/main/java/org/apache/commons/math4/legacy/core/MathArrays.java].
# The test infrastructure may be a neat idea (I didn't look at the details) but
since it completely departs from the existing approach (Junit 4) and the
expected upgrade path using Junit 5 features (see e.g. in
["SimplexOptimizerTest.java"|https://github.com/apache/commons-math/blob/master/commons-math-legacy/src/test/java/org/apache/commons/math4/legacy/optim/nonlinear/scalar/noderiv/SimplexOptimizerTest.java])
# New _public_ or _protected_ methods (like {{initOptimization}}) should be
discussed.
Other, comparatively smaller, issues:
* We don't use {{@author}} tags.
* All fields and methods (including _private_ ones) must be documented.
* Abbreviated names should be avoided ({{initOptimization}} for example should
be {{initializeOptimization}}, or perhaps just {{initialize}}) unless they have
become "well-known" (like "BFGS" maybe).
* The "default constructor" should not be explicitly declared.
> Classical multivariate optimizers (gradient descent, Raphson-Newton, BFGS)
> are missing
> --
>
> Key: MATH-1656
> URL: https://issues.apache.org/jira/browse/MATH-1656
> Project: Commons Math
> Issue Type: Wish
> Components: legacy
>Affects Versions: 4.0-beta1
>Reporter: François Laferrière
>Priority: Major
> Labels: features
> Attachments: MATH-1658-GradientDescent-Newton-BFGS.patch
>
>
> Some classical multivariate such as
> * gradient descent,
> * Raphson-Newton,
> * BFGS
> are missing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [commons-net] garydgregory merged pull request #162: Add FTPFile tests and fix Javadoc typos
garydgregory merged PR #162: URL: https://github.com/apache/commons-net/pull/162 -- 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. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] (JEXL-398) Allow 'trailing commas' or ellipsis while defining array, map and set literals
[ https://issues.apache.org/jira/browse/JEXL-398 ]
Henri Biestro deleted comment on JEXL-398:
was (Author: henrib):
Can be extended to map literals and sets.
> Allow 'trailing commas' or ellipsis while defining array, map and set literals
> --
>
> Key: JEXL-398
> URL: https://issues.apache.org/jira/browse/JEXL-398
> Project: Commons JEXL
> Issue Type: New Feature
>Affects Versions: 3.3
>Reporter: Xu Pengcheng
>Assignee: Henri Biestro
>Priority: Minor
> Fix For: 3.3.1
>
>
> Allowing trailing commas in structured literals (array, set, map) as a
> convenient syntactic leniency. :)
> {code:java}
> let m = { "foo": 1, "bar": 2, };
> let a = [ 1, 2, ];
> let s = (1, 2, );{code}
> Using a trailing ellipsis (...) to alter the concrete class materialized as a
> convenient semantic shortcut.
> {code:java}
> let m = { "foo": 1, "bar": 2, ... }; // LinkedHashMap
> let a = [ 1, 2, ...]; // ArrayList
> let s = (1, 2, ...); // LinkedHashSet{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JEXL-398) Allow 'trailing commas' or ellipsis while defining array, map and set literals
[
https://issues.apache.org/jira/browse/JEXL-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated JEXL-398:
---
Fix Version/s: 3.3.1
> Allow 'trailing commas' or ellipsis while defining array, map and set literals
> --
>
> Key: JEXL-398
> URL: https://issues.apache.org/jira/browse/JEXL-398
> Project: Commons JEXL
> Issue Type: New Feature
>Affects Versions: 3.3
>Reporter: Xu Pengcheng
>Assignee: Henri Biestro
>Priority: Minor
> Fix For: 3.3.1
>
>
> Allowing trailing commas in structured literals (array, set, map) as a
> convenient syntactic leniency. :)
> {code:java}
> let m = { "foo": 1, "bar": 2, };
> let a = [ 1, 2, ];
> let s = (1, 2, );{code}
> Using a trailing ellipsis (...) to alter the concrete class materialized as a
> convenient semantic shortcut.
> {code:java}
> let m = { "foo": 1, "bar": 2, ... }; // LinkedHashMap
> let a = [ 1, 2, ...]; // ArrayList
> let s = (1, 2, ...); // LinkedHashSet{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (JEXL-398) Allow 'trailing commas' or ellipsis while defining array, map and set literals
[
https://issues.apache.org/jira/browse/JEXL-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Biestro updated JEXL-398:
---
Description:
Allowing trailing commas in structured literals (array, set, map) as a
convenient syntactic leniency. :)
{code:java}
let m = { "foo": 1, "bar": 2, };
let a = [ 1, 2, ];
let s = (1, 2, );{code}
Using a trailing ellipsis (...) to alter the concrete class materialized as a
convenient semantic shortcut.
{code:java}
let m = { "foo": 1, "bar": 2, ... }; // LinkedHashMap
let a = [ 1, 2, ...]; // ArrayList
let s = (1, 2, ...); // LinkedHashSet{code}
was:
For example,
{code:java}
let m = {
"foo": 1,
"bar": 2,
}{code}
It fails because there is a comma after last entry `"bar": 2`, do we have any
plan to support it?
Thanks!
Summary: Allow 'trailing commas' or ellipsis while defining array, map
and set literals (was: Allow 'trailing commas' while defining array, map and
set literals)
> Allow 'trailing commas' or ellipsis while defining array, map and set literals
> --
>
> Key: JEXL-398
> URL: https://issues.apache.org/jira/browse/JEXL-398
> Project: Commons JEXL
> Issue Type: New Feature
>Affects Versions: 3.3
>Reporter: Xu Pengcheng
>Assignee: Henri Biestro
>Priority: Minor
>
> Allowing trailing commas in structured literals (array, set, map) as a
> convenient syntactic leniency. :)
> {code:java}
> let m = { "foo": 1, "bar": 2, };
> let a = [ 1, 2, ];
> let s = (1, 2, );{code}
> Using a trailing ellipsis (...) to alter the concrete class materialized as a
> convenient semantic shortcut.
> {code:java}
> let m = { "foo": 1, "bar": 2, ... }; // LinkedHashMap
> let a = [ 1, 2, ...]; // ArrayList
> let s = (1, 2, ...); // LinkedHashSet{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (STATISTICS-74) Add descriptive module to the release build
[ https://issues.apache.org/jira/browse/STATISTICS-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Herbert updated STATISTICS-74: --- Summary: Add descriptive module to the release build (was: Add descriptive module to site) > Add descriptive module to the release build > --- > > Key: STATISTICS-74 > URL: https://issues.apache.org/jira/browse/STATISTICS-74 > Project: Commons Statistics > Issue Type: Task > Components: descriptive >Affects Versions: 1.1 >Reporter: Alex Herbert >Priority: Trivial > > Incorporate the descriptive module into the full build. This should be > performed when the module is ready for release. This includes: > * Aggregate site reports (docs-module) > * BOM > * Release module -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (STATISTICS-74) Add descriptive module to site
Alex Herbert created STATISTICS-74: -- Summary: Add descriptive module to site Key: STATISTICS-74 URL: https://issues.apache.org/jira/browse/STATISTICS-74 Project: Commons Statistics Issue Type: Task Components: descriptive Affects Versions: 1.1 Reporter: Alex Herbert Incorporate the descriptive module into the full build. This should be performed when the module is ready for release. This includes: * Aggregate site reports (docs-module) * BOM * Release module -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (STATISTICS-73) Create a new o.a.c.s.descriptive module
[ https://issues.apache.org/jira/browse/STATISTICS-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Herbert resolved STATISTICS-73. Fix Version/s: 1.1 Resolution: Implemented Added in commit: e11d8e58c8e2c6de9173d0e8a590082ddf07a2ef > Create a new o.a.c.s.descriptive module > --- > > Key: STATISTICS-73 > URL: https://issues.apache.org/jira/browse/STATISTICS-73 > Project: Commons Statistics > Issue Type: Sub-task > Components: descriptive >Reporter: Anirudh Joshi >Priority: Minor > Labels: gsoc, gsoc2023 > Fix For: 1.1 > > > Create a new commons-statistics-descriptive module which contains the > implementation of all univariate statistics. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [commons-statistics] aherbert merged pull request #45: [STATISTICS-73] Add a new commons-statistics-descriptive module
aherbert merged PR #45: URL: https://github.com/apache/commons-statistics/pull/45 -- 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. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MATH-1656) Classical multivariate optimizers (gradient descent, Raphson-Newton, BFGS) are missing
[
https://issues.apache.org/jira/browse/MATH-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17740493#comment-17740493
]
François Laferrière commented on MATH-1656:
---
Hello,
please find a patch with a provisional version of Gradient-like optimizer. The
abstract class GradientLikeOptimizer contains the common code for the 3
methods: gradient descent, Newton-Raphson and BFGS. In fact only the
direction(...) method that compute the search direction for the next iteration
differs.
*Tests*
A group of junit tests covers >95% of the new code. The principle of the test
is to generate a set of gnuplot data/command file. A DiffTest utility class is
the ancestor of the classes containing the junit @test. The idea is to compare
the files produced by the test with a reference stored in git. If a difference
occurs during junit test execution, an assertion raised an exception
(indicating the first line that differs) and the test fails.
The test results are stored in resource sub-tree with a path corresponding to
the test method qualified name. For instance the result and reference of test
testRosenbrockMax of test class
org.apache.commons.math4.optim.NewtonRaphsonOptimizerTest is in directory
{code:java}
commons-math/commons-math-legacy/src/test/resources/org/apache/commons/math4/optim/NewtonRaphsonOptimizerTest/testRosenbrockMax{code}
. This directory contains two sub-directories : ref for the test references and
res for test results.
It is possible to visualize the results using gnuplot: for instance:
{code:java}
cd commons-math/commons-math-legacy
gnuplot -persist
src/test/resources/org/apache/commons/math4/optim/NewtonRaphsonOptimizerTest/testRosenbrock/res/gnuplot.plt{code}
[^MATH-1658-GradientDescent-Newton-BFGS.patch]
> Classical multivariate optimizers (gradient descent, Raphson-Newton, BFGS)
> are missing
> --
>
> Key: MATH-1656
> URL: https://issues.apache.org/jira/browse/MATH-1656
> Project: Commons Math
> Issue Type: Wish
> Components: legacy
>Affects Versions: 4.0-beta1
>Reporter: François Laferrière
>Priority: Major
> Labels: features
> Attachments: MATH-1658-GradientDescent-Newton-BFGS.patch
>
>
> Some classical multivariate such as
> * gradient descent,
> * Raphson-Newton,
> * BFGS
> are missing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MATH-1656) Classical multivariate optimizers (gradient descent, Raphson-Newton, BFGS) are missing
[ https://issues.apache.org/jira/browse/MATH-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] François Laferrière updated MATH-1656: -- Attachment: MATH-1658-GradientDescent-Newton-BFGS.patch > Classical multivariate optimizers (gradient descent, Raphson-Newton, BFGS) > are missing > -- > > Key: MATH-1656 > URL: https://issues.apache.org/jira/browse/MATH-1656 > Project: Commons Math > Issue Type: Wish > Components: legacy >Affects Versions: 4.0-beta1 >Reporter: François Laferrière >Priority: Major > Labels: features > Attachments: MATH-1658-GradientDescent-Newton-BFGS.patch > > > Some classical multivariate such as > * gradient descent, > * Raphson-Newton, > * BFGS > are missing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
