pyrrd - Project Hosting on Google Code

Today 12 hours ago issue 17 (TypeError: execv() arg 2 must contain only strings) Status changed by duncan.mcgreggor - Are you able to test from a bzr or svn checkout? If so, can you try this against the latest trunk? The reason I ask is that I can't reproduce this problem. If that's not possible for you, I will update this ticket when I've released the next version of PyRRD, so that you can download it from PyPI. Thanks! Status: Incomplete Are you able to test from a bzr or svn checkout? If so, can you try this against the latest trunk? The reason I ask is that I can't reproduce this problem. If that's not possible for you, I will update this ticket when I've released the next version of PyRRD, so that you can download it from PyPI. Thanks! Status: Incomplete 12 hours ago issue 19 (errors don't propogate up to calling methods) Status changed by duncan.mcgreggor - I had to do some tweaking to get this just right for PyRRD, but these changes have been merged to trunk now :-) Thanks guys! Status: FixCommitted I had to do some tweaking to get this just right for PyRRD, but these changes have been merged to trunk now :-) Thanks guys! Status: FixCommitted 13 hours ago r146 (* Added support for catching command-line errors (Modified f...) committed by oubiwann - * Added support for catching command-line errors (Modified fix from Joseph Heck). This fixes issue #19 . * Added support for catching command-line errors (Modified fix from Joseph Heck). This fixes issue #19 . 14 hours ago issue 10 (rrd.RRD takes empty lists as default argument values) Status changed by duncan.mcgreggor - In the course of fixing issue #18 , I was able to create a test case that revealed this bug :-) The fix was committed in bzr revno 123, svn r145. Status: FixCommitted In the course of fixing issue #18 , I was able to create a test case that revealed this bug :-) The fix was committed in bzr revno 123, svn r145. Status: FixCommitted 14 hours ago issue 18 (pyrrd maintaining state in the module itself - reporting inc...) Status changed by duncan.mcgreggor - Okay! I've got a fix in place. It's been pushed up on bzr revno 123, svn r145. There were lots of little problems that contributed to this error. Overall, however, the majority of the fix boiled down to checking for the mode (r/w) when mapping objects. Status: FixCommitted Okay! I've got a fix in place. It's been pushed up on bzr revno 123, svn r145. There were lots of little problems that contributed to this error. Overall, however, the majority of the fix boiled down to checking for the mode (r/w) when mapping objects. Status: FixCommitted 14 hours ago r144 (Updated ChangeLog. ) committed by oubiwann - Updated ChangeLog. Updated ChangeLog. 15 hours ago issue 18 (pyrrd maintaining state in the module itself - reporting inc...) commented on by duncan.mcgreggor - I've have done an enormous amount of work on this bug... lots of new unit tests, lots of changes. I've made some good progress, but I still don't have a fix. Will keep digging... I've have done an enormous amount of work on this bug... lots of new unit tests, lots of changes. I've made some good progress, but I still don't have a fix. Will keep digging... Yesterday 26 hours ago issue 10 (rrd.RRD takes empty lists as default argument values) Status changed by duncan.mcgreggor - Status: Incomplete Status: Incomplete 26 hours ago issue 19 (errors don't propogate up to calling methods) changed by duncan.mcgreggor - Status: InProgress Owner: duncan.mcgreggor Status: InProgress Owner: duncan.mcgreggor 26 hours ago issue 18 (pyrrd maintaining state in the module itself - reporting inc...) changed by duncan.mcgreggor - Status: InProgress Owner: duncan.mcgreggor Status: InProgress Owner: duncan.mcgreggor 26 hours ago issue 17 (TypeError: execv() arg 2 must contain only strings) Status changed by duncan.mcgreggor - Status: New Status: New 26 hours ago issue 17 (TypeError: execv() arg 2 must contain only strings) changed by duncan.mcgreggor - Status: Confirmed Owner: duncan.mcgreggor Status: Confirmed Owner: duncan.mcgreggor 27 hours ago issue 18 (pyrrd maintaining state in the module itself - reporting inc...) commented on by duncan.mcgreggor - Woops, no I take it back -- I think it's because of the class-level attributes in the mapper. Woops, no I take it back -- I think it's because of the class-level attributes in the mapper. 29 hours ago issue 18 (pyrrd maintaining state in the module itself - reporting inc...) commented on by duncan.mcgreggor - Thank you for this report! Yes, that's exactly the error I've been waiting for someone to report. What should fix it is changing the ds and rra list assignments in the RRD constructor to None and assigning them as values passed or empty lists once inside the init method itself. I'll be working on this issue and your other one (#19) today. Thanks again! Thank you for this report! Yes, that's exactly the error I've been waiting for someone to report. What should fix it is changing the ds and rra list assignments in the RRD constructor to None and assigning them as values passed or empty lists once inside the init method itself. I'll be working on this issue and your other one (#19) today. Thanks again! 29 hours ago issue 19 (errors don't propogate up to calling methods) commented on by duncan.mcgreggor - Thanks Joseph and caraldi -- I'm looking at your patches now. Thanks Joseph and caraldi -- I'm looking at your patches now. Last 30 days Nov 26, 2009 issue 19 (errors don't propogate up to calling methods) commented on by caraldi - Same problem for me, here is a patch against 0.0.7 Same problem for me, here is a patch against 0.0.7 Nov 26, 2009 issue 19 (errors don't propogate up to calling methods) commented on by caraldi - Same problem for me, here is a patch against 0.0.7 Same problem for me, here is a patch against 0.0.7 Earlier this year Nov 15, 2009 issue 19 (errors don't propogate up to calling methods) commented on by joseph.heck - proposed fix embedded in bzr branch lp:~heckj/pyrrd/devtest - along with additional tests proposed fix embedded in bzr branch lp:~heckj/pyrrd/devtest - along with additional tests Nov 14, 2009 issue 19 (errors don't propogate up to calling methods) reported by joseph.heck - What steps will reproduce the problem? 1. when using rrd.bufferValue(1000,512) multiple times with the same value, errors aren't being progated up to calling methods, although an Error string is printing out to STDERR What is the expected output? What do you see instead? some error Assertion being "raised" within Python, or a return code to notify of failure. The response instead is of correct implementation with no errors, although an error is printed to the screen. What version of the product are you using? On what operating system? 0.7 release and trunk MacOS X 10.6.2, Python 2.6 What steps will reproduce the problem? 1. when using rrd.bufferValue(1000,512) multiple times with the same value, errors aren't being progated up to calling methods, although an Error string is printing out to STDERR What is the expected output? What do you see instead? some error Assertion being "raised" within Python, or a return code to notify of failure. The response instead is of correct implementation with no errors, although an error is printed to the screen. What version of the product are you using? On what operating system? 0.7 release and trunk MacOS X 10.6.2, Python 2.6 Nov 14, 2009 issue 18 (pyrrd maintaining state in the module itself - reporting inc...) reported by joseph.heck - Summary: While I was trying to verify the functionality of pyrrd with my own unit tests, I ran into a side effect that made me think the pyrrd module was somehow maintaining state, which was unexpected, and I suspect incorrect. What steps will reproduce the problem? The attached python test script (uses unittest, no local rrdtool bindings) fails in a way that is unexpected - after I create an RRD file, I make a new RRD() object and load it. I only put one datasource into it, but it reports two. If I run the tests multiple times, then it reports 3, 4, etc consecutively. What is the expected output? What do you see instead? I expected the number of DS's returned from loading an RRD file to be 1 (since I only created one), but it grows with every invocation. What version of the product are you using? On what operating system? I first found this with the released 0.7.0 release, and then tried it against trunk. Please provide any additional information below. I don't believe it's doing anything incorrect with the RRD file itself, just reporting back strangely. Summary: While I was trying to verify the functionality of pyrrd with my own unit tests, I ran into a side effect that made me think the pyrrd module was somehow maintaining state, which was unexpected, and I suspect incorrect. What steps will reproduce the problem? The attached python test script (uses unittest, no local rrdtool bindings) fails in a way that is unexpected - after I create an RRD file, I make a new RRD() object and load it. I only put one datasource into it, but it reports two. If I run the tests multiple times, then it reports 3, 4, etc consecutively. What is the expected output? What do you see instead? I expected the number of DS's returned from loading an RRD file to be 1 (since I only created one), but it grows with every invocation. What version of the product are you using? On what operating system? I first found this with the released 0.7.0 release, and then tried it against trunk. Please provide any additional information below. I don't believe it's doing anything incorrect with the RRD file itself, just reporting back strangely. Nov 03, 2009 issue 17 (TypeError: execv() arg 2 must contain only strings) reported by alexanderad - What steps will reproduce the problem? 1. create instance of Graph 2. correctly extend it with defs, cdefs, etc 3. call .write() What is the expected output? What do you see instead? Expected: png file Instead of expected: File "my_rrd_graph.py", line 189, in rrd_graph g.write() File "build/bdist.linux-i686/egg/pyrrd/graph.py", line 804, in write rrdbackend.graph(data) File "build/bdist.linux-i686/egg/pyrrd/external.py", line 288, in graph _cmd('graph', parameters) File "build/bdist.linux-i686/egg/pyrrd/external.py", line 17, in _cmd p = Popen([args], shell=True, stdin=PIPE, stdout=PIPE, close_fds=close_fds) File "/usr/lib/python2.5/subprocess.py", line 594, in __init__ errread, errwrite) File "/usr/lib/python2.5/subprocess.py", line 1149, in _execute_child raise child_exception TypeError: execv() arg 2 must contain only strings What version of the product are you using? On what operating system? Stable Debian Etch, python2.5, latest pyrrd. Please provide any additional information below. This happened after regular aptitude safe-upgrade of stable Debian (only secure patches). What steps will reproduce the problem? 1. create instance of Graph 2. correctly extend it with defs, cdefs, etc 3. call .write() What is the expected output? What do you see instead? Expected: png file Instead of expected: File "my_rrd_graph.py", line 189, in rrd_graph g.write() File "build/bdist.linux-i686/egg/pyrrd/graph.py", line 804, in write rrdbackend.graph(data) File "build/bdist.linux-i686/egg/pyrrd/external.py", line 288, in graph _cmd('graph', parameters) File "build/bdist.linux-i686/egg/pyrrd/external.py", line 17, in _cmd p = Popen([args], shell=True, stdin=PIPE, stdout=PIPE, close_fds=close_fds) File "/usr/lib/python2.5/subprocess.py", line 594, in __init__ errread, errwrite) File "/usr/lib/python2.5/subprocess.py", line 1149, in _execute_child raise child_exception TypeError: execv() arg 2 must contain only strings What version of the product are you using? On what operating system? Stable Debian Etch, python2.5, latest pyrrd. Please provide any additional information below. This happened after regular aptitude safe-upgrade of stable Debian (only secure patches). Oct 29, 2009 issue 9 (RRD.load broken on some locales (rrdtool uses the system loc...) Status changed by duncan.mcgreggor - Hrm... I've tried getting rrdtool to output dump data in non-US-English formats (e.g., de_DE.UTF-8), but I've had no success in duplicating the problem. I've tried doing this from Python with the locale.setlocale method, I've tried doing this in _cmd with "LC_ALL=de_DE_UTF-8 rrdtool %" and I've tried directly on the command line. The dump command consistently returns values in scientific notation with no commas, so need an example to work from. Can you do the following for me, so that I can write an appropriate unit test and get a fix for this issue? 1) Paste an RRD create command that breaks with a non-en_US locale. This create command should have values such that, when dumped, the commas that you mentioned are present instead of periods. 2) Paste the exact locale that you're using. I may need more, but let's see if I can duplicate the issue with that info. Thanks! Status: Incomplete Hrm... I've tried getting rrdtool to output dump data in non-US-English formats (e.g., de_DE.UTF-8), but I've had no success in duplicating the problem. I've tried doing this from Python with the locale.setlocale method, I've tried doing this in _cmd with "LC_ALL=de_DE_UTF-8 rrdtool %" and I've tried directly on the command line. The dump command consistently returns values in scientific notation with no commas, so need an example to work from. Can you do the following for me, so that I can write an appropriate unit test and get a fix for this issue? 1) Paste an RRD create command that breaks with a non-en_US locale. This create command should have values such that, when dumped, the commas that you mentioned are present instead of periods. 2) Paste the exact locale that you're using. I may need more, but let's see if I can duplicate the issue with that info. Thanks! Status: Incomplete Oct 29, 2009 issue 10 (rrd.RRD takes empty lists as default argument values) Labels changed by duncan.mcgreggor - Although I agree with the truth of empty lists being problematic in method calls, I haven't experienced any problems with it in this case. The unit tests that I wrote to check if there was a problem are all currently passing. In all likelihood, I'm missing an edge case, and would love to receive a patch for the unit tests that shows a breakage. Until then, I'll set the priority of this ticket to low... Labels: Priority-Low −Priority-Medium Although I agree with the truth of empty lists being problematic in method calls, I haven't experienced any problems with it in this case. The unit tests that I wrote to check if there was a problem are all currently passing. In all likelihood, I'm missing an edge case, and would love to receive a patch for the unit tests that shows a breakage. Until then, I'll set the priority of this ticket to low... Labels: Priority-Low −Priority-Medium Oct 29, 2009 issue 16 (Add support for fine-grained testing in testRunner.py) Labels changed by duncan.mcgreggor - Labels: Priority-Wishlist −Priority-Low Labels: Priority-Wishlist −Priority-Low Oct 29, 2009 issue 15 (Conditionnal run of rrdtool bindings) Status changed by duncan.mcgreggor - Status: FixCommitted Status: FixCommitted Oct 29, 2009 issue 14 (Tests are not portable) Status changed by duncan.mcgreggor - Status: FixCommitted Status: FixCommitted Oct 29, 2009 issue 13 (Fix failing unit tests) Status changed by duncan.mcgreggor - Status: FixCommitted Status: FixCommitted Oct 29, 2009 issue 12 (Wrong expected value in dump test) Status changed by duncan.mcgreggor - Status: FixCommitted Status: FixCommitted Oct 29, 2009 issue 11 (Wrong expected value in epoch test) Status changed by duncan.mcgreggor - Status: FixCommitted Status: FixCommitted Oct 29, 2009 issue 8 (Flag parameters are not handled correctly) Status changed by duncan.mcgreggor - Status: FixCommitted Status: FixCommitted Oct 29, 2009 issue 7 (parameters are not properly quoted for windows) Status changed by duncan.mcgreggor - Status: FixCommitted Status: FixCommitted Oct 29, 2009 issue 6 (rrdfile is not colon escaped in DS) Status changed by duncan.mcgreggor - Status: FixCommitted Status: FixCommitted Oct 29, 2009 issue 5 (Wrapping python-rrdtool) Status changed by duncan.mcgreggor - Status: FixCommitted Status: FixCommitted Oct 29, 2009 issue 3 (Add interface for "rrdtool info") Status changed by duncan.mcgreggor - Status: FixReleased Status: FixReleased Oct 29, 2009 issue 2 (Possible bug in DS signature) Status changed by duncan.mcgreggor - Status: FixReleased Status: FixReleased Oct 29, 2009 issue 1 (external.py, Popen) Status changed by duncan.mcgreggor - Status: FixReleased Status: FixReleased Oct 29, 2009 issue 16 (Add support for fine-grained testing in testRunner.py) Labels changed by duncan.mcgreggor - Labels: Priority-Low −Priority-Medium Labels: Priority-Low −Priority-Medium Oct 29, 2009 issue 16 (Add support for fine-grained testing in testRunner.py) Summary changed by duncan.mcgreggor - Summary: Add support for fine-grained testing in testRunner.py Summary: Add support for fine-grained testing in testRunner.py Oct 29, 2009 issue 16 (Add support for fine-grained testing) reported by duncan.mcgreggor - It would be nice to be able to have the option of testing a specified part of the library. For example: * just one module * just a class' docstrings or a single TestCase * just a method or module-level function's docstring * just a TestCase's method It would be nice to be able to have the option of testing a specified part of the library. For example: * just one module * just a class' docstrings or a single TestCase * just a method or module-level function's docstring * just a TestCase's method Oct 29, 2009 issue 15 (Conditionnal run of rrdtool bindings) Status changed by duncan.mcgreggor - Done! This was added in r136. Status: Fixed Done! This was added in r136. Status: Fixed Oct 29, 2009 issue 13 (Fix failing unit tests) Status changed by duncan.mcgreggor - Okay, r135 fixes the rest of the patched doctests. Status: Fixed Okay, r135 fixes the rest of the patched doctests. Status: Fixed Oct 29, 2009 issue 13 (Fix failing unit tests) Status changed by duncan.mcgreggor - Status: Started Status: Started Oct 29, 2009 issue 10 (rrd.RRD takes empty lists as default argument values) Owner changed by duncan.mcgreggor - Owner: duncan.mcgreggor Owner: duncan.mcgreggor Oct 29, 2009 issue 9 (RRD.load broken on some locales (rrdtool uses the system loc...) Owner changed by duncan.mcgreggor - Owner: duncan.mcgreggor Owner: duncan.mcgreggor Oct 29, 2009 issue 15 (Conditionnal run of rrdtool bindings) Owner changed by duncan.mcgreggor - Owner: duncan.mcgreggor Owner: duncan.mcgreggor Oct 29, 2009 issue 13 (Fix failing unit tests) Status changed by duncan.mcgreggor - Woops, there were more problems with the patch than the one that I originally saw. Reopening until they are fixed. Status: Accepted Woops, there were more problems with the patch than the one that I originally saw. Reopening until they are fixed. Status: Accepted Oct 29, 2009 issue 14 (Tests are not portable) Status changed by duncan.mcgreggor - The patch had some Linux-incompatible changes with regard to the NaN tests. Once the partial patch was applied, there was one small test that hadn't been adjsuted, so I did that too. Patch was applied in r134. Status: Fixed The patch had some Linux-incompatible changes with regard to the NaN tests. Once the partial patch was applied, there was one small test that hadn't been adjsuted, so I did that too. Patch was applied in r134. Status: Fixed Oct 29, 2009 issue 14 (Tests are not portable) commented on by duncan.mcgreggor - In r133, I've added some code that tries to do a portable NaN in pyrrd.backend.common. Let me know how that goes. I'll be applying a partial of your patch next... In r133, I've added some code that tries to do a portable NaN in pyrrd.backend.common. Let me know how that goes. I'll be applying a partial of your patch next... Oct 29, 2009 issue 14 (Tests are not portable) commented on by duncan.mcgreggor - Oh, man -- this old code needed to be cleaned up for ages -- thanks! Oh, man -- this old code needed to be cleaned up for ages -- thanks! Oct 29, 2009 issue 7 (parameters are not properly quoted for windows) Status changed by duncan.mcgreggor - Great. Thanks for the note! Status: Fixed Great. Thanks for the note! Status: Fixed

issue 17 (TypeError: execv() arg 2 must contain only strings) reported by alexanderad - What steps will reproduce the problem? 1. create instance of Graph 2. correctly extend it with defs, cdefs, etc 3. call .write() What is the expected output? What do you see instead? Expected: png file Instead of expected: File "my_rrd_graph.py", line 189, in rrd_graph g.write() File "build/bdist.linux-i686/egg/pyrrd/graph.py", line 804, in write rrdbackend.graph(*data) File "build/bdist.linux-i686/egg/pyrrd/external.py", line 288, in graph _cmd('graph', parameters) File "build/bdist.linux-i686/egg/pyrrd/external.py", line 17, in _cmd p = Popen([args], shell=True, stdin=PIPE, stdout=PIPE, close_fds=close_fds) File "/usr/lib/python2.5/subprocess.py", line 594, in __init__ errread, errwrite) File "/usr/lib/python2.5/subprocess.py", line 1149, in _execute_child raise child_exception TypeError: execv() arg 2 must contain only strings What version of the product are you using? On what operating system? Stable Debian Etch, python2.5, latest pyrrd. Please provide any additional information below. This happened after regular aptitude safe-upgrade of stable Debian (only secure patches).

What steps will reproduce the problem? 1. create instance of Graph 2. correctly extend it with defs, cdefs, etc 3. call .write() What is the expected output? What do you see instead? Expected: png file Instead of expected: File "my_rrd_graph.py", line 189, in rrd_graph g.write() File "build/bdist.linux-i686/egg/pyrrd/graph.py", line 804, in write rrdbackend.graph(*data) File "build/bdist.linux-i686/egg/pyrrd/external.py", line 288, in graph _cmd('graph', parameters) File "build/bdist.linux-i686/egg/pyrrd/external.py", line 17, in _cmd p = Popen([args], shell=True, stdin=PIPE, stdout=PIPE, close_fds=close_fds) File "/usr/lib/python2.5/subprocess.py", line 594, in __init__ errread, errwrite) File "/usr/lib/python2.5/subprocess.py", line 1149, in _execute_child raise child_exception TypeError: execv() arg 2 must contain only strings What version of the product are you using? On what operating system? Stable Debian Etch, python2.5, latest pyrrd. Please provide any additional information below. This happened after regular aptitude safe-upgrade of stable Debian (only secure patches).

Today

Yesterday

Last 30 days

Earlier this year