Menu ▾ ▴

#2907 another "finished called twice" warning in stderr

nextrelease
closed-works-for-me
nobody
None
5
4 hours ago
2 days ago
No

The progress monitor finished method should only be called once. It's likely that this is not causing any problems, but if a process were being monitored by a machine that could cause problems. This should be cleaned up by calling monitor.getSubTaskMonitor. This is with v2026a_8.

monitor finished was called twice!
here was the first call:
at java.lang.Thread.getStackTrace(Thread.java:1564)
at org.das2.components.DasProgressPanel.finished(DasProgressPanel.java:499)
at org.das2.qds.ops.Ops.fftPower(Ops.java:9286)
at org.das2.qds.ops.Ops.fftPower(Ops.java:8679)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.python.core.PyReflectedFunction.call(PyReflectedFunction.java:173)
at org.python.core.PyReflectedFunction.call(PyReflectedFunction.java:181)
at org.python.core.PyObject.call(PyObject.java:509)
at org.python.pycode._pyx84.f$0(msc_bac_power.jyds:8)
at org.python.pycode._pyx84.call_function(msc_bac_power.jyds)
at org.python.core.PyTableCode.call(PyTableCode.java:217)
at org.python.core.PyCode.call(PyCode.java:14)
at org.python.core.Py.runCode(Py.java:1224)
at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:165)
at org.autoplot.datasource.jython.JythonDataSource.getDataSet(JythonDataSource.java:317)
at org.autoplot.dom.DataSourceController.loadDataSet(DataSourceController.java:1900)
at org.autoplot.dom.DataSourceController.updateImmediately(DataSourceController.java:1495)
at org.autoplot.dom.DataSourceController.access$1300(DataSourceController.java:65)
at org.autoplot.dom.DataSourceController$11.run(DataSourceController.java:1594)
at org.das2.system.RequestProcessor$Runner.run(RequestProcessor.java:253)
at java.lang.Thread.run(Thread.java:750)
... and the second call:
java.lang.Exception
at org.das2.components.DasProgressPanel.finished(DasProgressPanel.java:495)
at org.das2.qds.ops.Ops.fftPower(Ops.java:9286)
at org.das2.qds.ops.Ops.fftPower(Ops.java:8679)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.python.core.PyReflectedFunction.call(PyReflectedFunction.java:173)
at org.python.core.PyReflectedFunction.call(PyReflectedFunction.java:181)
at org.python.core.PyObject.call(PyObject.java:509)
at org.python.pycode._pyx84.f$0(msc_bac_power.jyds:9)
at org.python.pycode._pyx84.call_function(msc_bac_power.jyds)
at org.python.core.PyTableCode.call(PyTableCode.java:217)
at org.python.core.PyCode.call(PyCode.java:14)
at org.python.core.Py.runCode(Py.java:1224)
at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:165)
at org.autoplot.datasource.jython.JythonDataSource.getDataSet(JythonDataSource.java:317)
at org.autoplot.dom.DataSourceController.loadDataSet(DataSourceController.java:1900)
at org.autoplot.dom.DataSourceController.updateImmediately(DataSourceController.java:1495)
at org.autoplot.dom.DataSourceController.access$1300(DataSourceController.java:65)
at org.autoplot.dom.DataSourceController$11.run(DataSourceController.java:1594)
at org.das2.system.RequestProcessor$Runner.run(RequestProcessor.java:253)
at java.lang.Thread.run(Thread.java:750)
monitor finished was called twice!
here was the first call:
at java.lang.Thread.getStackTrace(Thread.java:1564)
at org.das2.components.DasProgressPanel.finished(DasProgressPanel.java:499)
at org.das2.qds.ops.Ops.fftPower(Ops.java:9286)
at org.das2.qds.ops.Ops.fftPower(Ops.java:8679)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.python.core.PyReflectedFunction.call(PyReflectedFunction.java:173)
at org.python.core.PyReflectedFunction.call(PyReflectedFunction.java:181)
at org.python.core.PyObject.call(PyObject.java:509)
at org.python.pycode._pyx83.f$0(msc_bac_power.jyds:8)
at org.python.pycode._pyx83.call_function(msc_bac_power.jyds)
at org.python.core.PyTableCode.call(PyTableCode.java:217)
at org.python.core.PyCode.call(PyCode.java:14)
at org.python.core.Py.runCode(Py.java:1224)
at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:165)
at org.autoplot.datasource.jython.JythonDataSource.getDataSet(JythonDataSource.java:317)
at org.autoplot.dom.DataSourceController.loadDataSet(DataSourceController.java:1900)
at org.autoplot.dom.DataSourceController.updateImmediately(DataSourceController.java:1495)
at org.autoplot.dom.DataSourceController.access$1300(DataSourceController.java:65)
at org.autoplot.dom.DataSourceController$11.run(DataSourceController.java:1594)
at org.das2.system.RequestProcessor$Runner.run(RequestProcessor.java:253)
at java.lang.Thread.run(Thread.java:750)
... and the second call:
java.lang.Exception
at org.das2.components.DasProgressPanel.finished(DasProgressPanel.java:495)
at org.das2.qds.ops.Ops.fftPower(Ops.java:9286)
at org.das2.qds.ops.Ops.fftPower(Ops.java:8679)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.python.core.PyReflectedFunction.call(PyReflectedFunction.java:173)
at org.python.core.PyReflectedFunction.call(PyReflectedFunction.java:181)
at org.python.core.PyObject.call(PyObject.java:509)
at org.python.pycode._pyx83.f$0(msc_bac_power.jyds:9)

Discussion

  • Jeremy Faden

    Jeremy Faden - 2 days ago
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,6 +1,6 @@
     The progress monitor finished method should only be called once.  It's likely that this is not causing any problems, but if a process were being monitored by a machine that could cause problems.  This should be cleaned up by calling monitor.getSubTaskMonitor.  This is with v2026a_8.
    
    -```
    +~~~~
     monitor finished was called twice!
     here was the first call:
        at java.lang.Thread.getStackTrace(Thread.java:1564)
    @@ -91,5 +91,4 @@
        at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:181)
        at org.python.core.PyObject.__call__(PyObject.java:509)
        at org.python.pycode._pyx83.f$0(msc_bac_power.jyds:9)
    
    - ```
    - 
    + ~~~~
    
     
  • Jeremy Faden

    Jeremy Faden - 2 days ago
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,6 +1,5 @@
     The progress monitor finished method should only be called once.  It's likely that this is not causing any problems, but if a process were being monitored by a machine that could cause problems.  This should be cleaned up by calling monitor.getSubTaskMonitor.  This is with v2026a_8.
    
    -~~~~
     monitor finished was called twice!
     here was the first call:
        at java.lang.Thread.getStackTrace(Thread.java:1564)
    @@ -91,4 +90,4 @@
        at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:181)
        at org.python.core.PyObject.__call__(PyObject.java:509)
        at org.python.pycode._pyx83.f$0(msc_bac_power.jyds:9)
    
    - ~~~~
    + 
    
     
  • Jeremy Faden

    Jeremy Faden - 4 hours ago
    • status: open --> closed-works-for-me
     
  • Jeremy Faden

    Jeremy Faden - 4 hours ago

    This was my bug, where I was misusing a progress monitor in a script.