{5} Assigned, Active Tickets by Owner (Full Description) (15 matches)
List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.
amerzky
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #38 | Rename advert::entry::store_string/retrieve_string | SAGA Package Advert | 1.2 | enhancement | 2/18/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The API function advert::entry::store_string and retrieve_string need to be renamed to be overloads of the store_object/retrieve_object functions, without an ychange in semantics. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #45 | Complete the Programming Handbook | API Documentation | 1.3 | enhancement | 2/29/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Well, we have _some_ programmers manual now, although it probably needs more work. I thus move this tracker item to v1.0. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #251 | Exception type order does not make sense with multiple adaptors | SAGA Specification | 1.2 | defect | 9/18/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The SAGA spec defines an 'order' of exceptions, from more specific to less specific. Functions must throw the most specific exception possible, which makes sense. However, the C++ engine uses the same order for the type of the nested exception reported to an application. This does not make sense when there are multiple adaptors implementing the same functionality. Example: a user creates an FTP file: saga::file f("ftp://host.com/file.txt", saga::filesystem::Exclusive);
This file happens to already exist, so this call should throw an already_exists exception. Say the engine has two file adaptors: a local one and an FTP adaptor. The local adaptor will throw an incorrect_url exception in its constructor, since it cannot handle FTP URLs. The FTP adaptor will try to create the file and throw an already_exist exception. The type of the nested exception reported by the engine to the user will then be incorrect_url, since that one is 'more specific' than already_exists. Worse, if one adaptor does not implement a method, its not_implemented exception will overrule all more sensible exceptions from adaptors that do implement that method. This is clearly not what a user wants. For a multi-adaptor engine, it makes much more sense to 'order' the exception types differently. In the Java engine, we currently 'invented' this order (from more to less specific): AlreadyExistsException, DoesNotExistException, IncorrectStateException, TimeoutException, AuthenticationFailedException, AuthorizationFailedException, PermissionDeniedException, BadParameterException, IncorrectURLException, NoSuccessException, NotImplementedException. Rationale: if two adaptors report two different exceptions, a user would probably like to see the first one in this list. Shouldn't the C++ engine do something similar? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #262 | job state for default job adaptor needs to reflect reality on get_job() | Default Job Adaptor | 1.3 | defect | 10/2/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
At the moment, that job state is assumed to be Running if the job is found alive (ps). But the job could very well be sleeping, or a zombie. The job state should reflect that. (note to self: If it is a Zombie, can we actually reclaim it?) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #283 | python bindings do not work for python 2.6 | Python Bindings | 1.2 | defect | 10/29/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
When trying to compile SAGA with python bindings (python 2.6, boost 1.36) I get the following in the python config.log file: conftest.o(.text+0x4b): In function `static_initialization_and_destruction_0': /work/yye00/boost_install//include//boost-1_36/boost/python/refcount.hpp:16: undefined reference to `_Py_NoneStruct' conftest.o(.text+0x63): In function `static_initialization_and_destruction_0': /work/yye00/boost_install//include//boost-1_36/boost/python/object_core.hpp:429: undefined reference to `_Py_NoneStruct' conftest.o(.text+0x95): In function `main': /scratch/yye00/SAGA/trunk/bindings/saga/python/conftest.cpp:24: undefined reference to `Py_Initialize' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PySequence?_DelSlice' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyNumber?_InPlaceXor' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyInt?_FromLong' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyNumber?_Subtract' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyMem?_Malloc' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyComplex?_RealAsDouble' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyModule?_Type' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyDict?_Keys' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyMethod?_Type' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyExc?_ReferenceError' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PySequence?_SetSlice' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyObject?_GetAttr' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyExc?_RuntimeError' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyObject?_CallFunction' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyNumber?_InPlaceDivide' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyDict?_Copy' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyErr?_ExceptionMatches' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyFloat?_Type' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyString?_Type' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyNumber?_Or' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyUnicodeUCS2_AsWideChar' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyUnicode?_Type' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyNumber?_Xor' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyStaticMethod?_Type' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyExc?_OverflowError' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyDict?_Clear' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyObject?_ClearWeakRefs' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyErr?_SetString' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyErr?_WarnEx' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyComplex?_Type' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyLong?_AsUnsignedLongLong' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyErr?_Occurred' /work/yye00/boost_install//lib/libboost_python-gcc42-mt.so: undefined reference to `PyBaseObject?_Type' Please assist. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #61 | reorganize package fallbacks | SAGA Engine | 1.2 | enhancement | 3/13/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
the fallback code in the impl packages is obfuscating the packages. A simple extensible mechanism should be introduced to add fallbacks outside of the package source files. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #184 | libname versioning | SAGA Engine | 1.4 | enhancement | 8/10/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
verisoning of library names allows multiple versions to coexist. We should support that. Connected to that, saga/saga/version.hpp should be generated by configure, and version infos should be taken from SAGA_ROOT/VERSION. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #250 | Add configure option to disable creation of static libraries | Build system | 1.3 | enhancement | 9/18/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
It would be nice to have a configure option to disable the creation of the static libraries. The $SAGA_LOCATION/lib/*.a files use a significant amount of disk space and are not always necessary. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
biochimia
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #201 | Temporary logs may linger on | Condor Job Adaptor | 1.2 | defect | 8/22/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
With the default configuration, if an application starts a Condor job and exits before it terminates, the temporary log file used to track the job will be left in the system's temporary directory. The adaptor does try to cleanup on exit, but subsequent job events will cause Condor to recreate the log file. More info here: https://lists.cs.wisc.edu/archive/condor-devel/2008-August/msg00003.shtml |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #202 | Avoid repeating log filenames | Condor Job Adaptor | 1.2 | defect | 8/22/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
IIUC, the only job identifying information showing up in log files is the Cluster and Process ID. (It may be that this is different if more than one pool are actually setup.) Thus, it is very important that log files are not shared across different pools/hosts. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #96 | Status of the SAGA Condor Adaptor | Condor Job Adaptor | 1.2 | enhancement | 6/1/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
... should be part of the 0.9.4 release! |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #209 | Connect to remote submit machine | Condor Job Adaptor | 1.3 | enhancement | 8/22/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Currently the Condor adaptor has to be run on a machine that has Condor installed and configured to submit jobs to a pool. It would be nice to weaken this requirement to the point that SAGA configures Condor automatically or connects to remote machines without a local Condor installation. The former may be feasible, but I currently don't know how. The latter will require communicating with Condor through remote APIs, like SOAP or GAHP, which amounts to a completely new adaptor. In the meantime, any incremental improvements are welcome. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
hkaiser
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #304 | Missing methods in Python bindings | Python Bindings | 1.2 | defect | 11/25/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi, I'm trying to glue together your SAGA C++ Python bindings and the following (higher level) Python SAGA language binding: http://www.few.vu.nl/~pzn400/apidoc/[[BR]] I discovered that there are some methods missing, which are present in the actual C++ API, but not exposed to the Python layer. For example, I didn't find a way to read buffer data into a variable. The methods buffer.get_data() and buffer.set_data() are missing. Should I file more bugs if I find some more missing methods or do you prefer another way?
Thanks very much, |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #1 | Add parameter validation to API calls in the engine | SAGA Engine | 1.2 | enhancement | 10/25/2006 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Adding parameter validation to API calls in the engine will improve reliability of adaptors, since these won't have to validate all of the parameters any more. Parameter handling could be consolidated and unified etc. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
oweidner
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #244 | Globus Adaptor: SAGA Context | GSI Context Adaptor | 1.2 | defect | 9/11/2008 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I am trying to use the SAGA context API to manage different X509 proxies on top of the Globus adaptor: I extracted the key points into following python program: import saga
s = saga.session()
userproxy="/home/luckow/.globus/teraproxy.pem"
ctx = saga.context("globus")
ctx.set_attribute ("UserProxy", userproxy);
ctx.set_defaults ();
s.add_context(ctx)
#register advert entry
lrms_saga_url = saga.url("gram://grid-abe.ncsa.teragrid.org/jobmanager-pbs")
jd = saga.job.description()
jd.numberofprocesses = "1"
jd.spmdvariation = "single"
jd.arguments = ["hello world"]
jd.executable = "/bin/echo"
jd.queue = "loni_jha_big@workq"
jd.workingdirectory = "$(HOME)"
jd.output = "stdout.txt"
jd.error = "stderr.txt"
js = saga.job.service(s, lrms_saga_url)
job = js.create_job(jd)
print "Submit to: " + str(lrms_saga_url)
job.run()
However, the context does not pick up the proxy correctly. As a matter of fact the program already holds during initialization of the context: Successfully created CPI: context_cpi using adaptor instance: globus_gsi_context SAGA(NoSuccess?): globus_gsi_context: globus_gsi_context_adaptor.cpp(91): Couldn't find a valid proxy in /tmp/x509up_u<uid>. You can set 'saga::context::attributes::userproxy' if your proxy file is located somewhere else. globus_sysconfig: Could not find a valid proxy certificate file location globus_sysconfig: Error with key filename globus_sysconfig: File does not exist: /tmp/x509up_u26098 is not a valid file SAGA(NoAdaptor?): adaptor_selector.cpp(181): Could not select any matching adaptor for: context_cpi::sync_set_defaults SAGA(NoAdaptor?): adaptor_selector.cpp(181): Could not select any matching adaptor for: context_cpi::async_set_defaults SAGA(NoAdaptor?): proxy.cpp(209): No (other) adaptor implements context_cpi::set_defaults SAGA(NoAdaptor?): proxy.cpp(276): SAGA(NoAdaptor?): proxy.cpp(209): No (other) adaptor implements context_cpi::set_defaults SAGA(NoSuccess?): globus_gsi_context: globus_gsi_context_adaptor.cpp(91): Couldn't find a valid proxy in /tmp/x509up_u<uid>. You can set 'saga::context::attributes::userproxy' if your proxy file is located somewhere else. globus_sysconfig: Could not find a valid proxy certificate file location globus_sysconfig: Error with key filename globus_sysconfig: File does not exist: /tmp/x509up_u26098 is not a valid file Traceback (most recent call last):
saga.no_success: SAGA(NoSuccess?): globus_gsi_context: globus_gsi_context_adaptor.cpp(91): Couldn't find a valid proxy in /tmp/x509up_u<uid>. You can set 'saga::context::attributes::userproxy' if your proxy file is located somewhere else. globus_sysconfig: Could not find a valid proxy certificate file location globus_sysconfig: Error with key filename globus_sysconfig: File does not exist: /tmp/x509up_u26098 is not a valid file I have of course no standard proxy initialized since I want to use a custom proxy location. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
