search for: reraised

...is the performance? Performance of the bindings? Fine. My only gripe with LLVM's OCaml bindings is the way an error caught on the LLVM side causes my program to die in a way that the stack trace is unobtainable. So I resort to massively verbose debug logs. I'd much rather the bindings reraised errors as exceptions on the OCaml side. -- Dr Jon Harrop, Flying Frog Consultancy Ltd. http://www.ffconsultancy.com/?e

hi,i don''t know how to capture the following exception if the file directory or name is not correct. ########## def index @csv_array=[] begin CSV.foreach(''files/sample.csv'') do|row| sub_array=row @csv_array<<sub_array end rescue Exception=>e flash.now[:error]="error:#{e}" raise end end ######### after

Attached are updated LLVM-OCaml Bindings Tutorial from Chris Wailes. (http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-April/021804.html) We changed them to work with the latest APIs(LLVM2.6 and the latest LLVM from SVN). Does anyone know if there is any realistic project using LLVM-OCaml Bindings? How is the performance? Jianzhou -------------- next part -------------- A non-text attachment was

Hi all, Every time I try to add options for the find_conditions argument of find_by_contents I get the following: a = AnnotatedLink.find_by_contents(''test'', {}, {:conditions => ''category_id IS NOT NULL''}) >> NoMethodError: You have a nil object when you didn''t expect it! You might have expected an instance of Array. The error occured while

...ror if it meets a certain criteria and otherwise reraise it. I want the error message to indicate the function in which the error occured (and not mention tryCatch). Wanted: > g("foo") ## error caught [1] "caught foo" > g("otherwise") ## error reraised Error in g("otherwise") : otherwise This works: g <- function(msg) { mycall <- sys.call(0) tryCatch(stop(msg), error=function(e) { if ("foo" == conditionMessage(e)) "caught foo" else {...

Hi, I''m writing some scripts on the command line using ActiveRecord, and some interesting (read: confusing) things are happening with the way exceptions are caught and re-raised. In AbstractAdapter.log (connection_adapters/abstract_adapter.rb:144), Exception is rescued and reraised as an ActiveRecord::StatementInvalid exception. While in most cases I''m sure this is fine, Exception includes things like SystemExit and SignalException, which have nothing to do with invalid SQL. If I''m executing a statement when I send a TERM signal to the process (or call exit(...

...l for felix, but it's pretty early. > My only gripe with LLVM's OCaml bindings is the way an error caught on the > LLVM side causes my program to die in a way that the stack trace is > unobtainable. So I resort to massively verbose debug logs. I'd much rather > the bindings reraised errors as exceptions on the OCaml side. Unfortunately most errors are assertions, which we can't hook into. Perhaps though we can recover some type safety. Hypothetically, I can imagine using polymorphic variants just like lablgtk, and type llvalue = [`Value] type lluser = [value | `User] typ...

For all LLVM users out there: what kinds of errors do you spend the most time debugging? On Saturday 15 March 2008 08:03:47 Erick Tryzelaar wrote: > Does this sound like it could work, or am I missing something? Excellent idea. You might also consider building a data structure on the OCaml side that is equivalent to the LLVM code: module Op = struct type int_op = [ `IAdd | ... ]

Hi everyone, I’m testing the new openstack kilo on ubuntu15.04 and hypervisor is xen4.5. I can creat instance successfully , but live migration is always failed. Error report like this: 2015-05-07 10:47:22.135 1331 ERROR nova.virt.libvirt.driver [-] [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] Live Migration failure: this function is not supported by the connection driver:

...be caught. http://github.com/rails/rails/commit/d898a4ba425a201827f07a5bb11c8c6bf85159b8 b) ActionController::TestCase::RaiseActionExceptions#rescue_action_without_handler never gets called, because it''s not overriding anything anymore -- i.e. there''s no way exceptions could be reraised in the rescue_action_in_public! case. What''s the deal here? I prefer to be able to use assert_response consistently in functional tests, rather than having to mix assert_response and assert_raise, so I''d call it a bug. -- You received this message because you are subscribed to...

I was talking to Gordon on #llvm earlier, and he challenged me with coming up with a way to improve the ocaml binding's type safety. We can't go letting haskell beat us now, can we? I think I got an easy solution with phantom types. For those who don't know what the problem is, the ocaml bindings share one type between whole class branches (like values). This means we need to downcast

...Performance of the bindings? Fine. > > My only gripe with LLVM's OCaml bindings is the way an error caught on the > LLVM side causes my program to die in a way that the stack trace is > unobtainable. So I resort to massively verbose debug logs. I'd much rather > the bindings reraised errors as exceptions on the OCaml side. I met the same issue about how to debug assertion failures from C. But I found the latest LLVM fixed the problem I met. So I am fine temporarily. :) HLVM is an interesting project to support multi-language programming in a higher level. In this project, hav...

Daniel, Tobias, Renato and myself have been looking a little bit at the potential underlying reason for why http://llvm.org/perf/ is instable, and have found some clues. I want to share them here to give people with more experience in the frameworks used by LNT (flask, sqlalchemy, wsgi, .) a chance to check if our reasoning below seems plausible. Daniel noticed the following backtrace in the

Hello guys, I went into milestones page (https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/milestones) and found out that Rails 2.3.6 was due Jan 15, 2010. Does it mean all tickets in that milestone should be cleared first? If so, then I would pay attention to clear tickets in that bucket first. Thank you, Prem Sichanugrist (sikachu) -- You received this message because you are

On 07.05.2015 11:26, RockCui@zhaoxin.com wrote: > Hi everyone, > > I’m testing the new openstack kilo on ubuntu15.04 and hypervisor is xen4.5. > I can creat instance successfully , but live migration is always failed. Error report like this: > > 2015-05-07 10:47:22.135 1331 ERROR nova.virt.libvirt.driver [-] [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] Live Migration

I am using RMagick in my app and am having problems in deployment. The deployment machine (Fedora Core 5) can''t find RMagick unless I change the "require" syntax from that used on the dev machine (OS X). And the dev machine doesn''t like the syntax that works on the deployment server! To wit: [OS X] $ script/console Loading development environment. >> require_gem

Hi, I am installing OpenStack on Red Hat 7.5. For Nova compute component, I choose libvirt and Xen. However, I am running into some problems. It seems libvirt is unable to communicate with Xen. Xen installation: I installed Xen410 using "Xen make easy" https://xen.crc.id.au/support/guides/install/. Here is a list of packages installed and verification that Xen is running. #

On 15-09-24 04:42 PM, Ryan, Travis wrote: > Did something change DB-wise with PJSIP and realtime between 13.3.2 > and 13.5.0? I'm getting an unknown column error and unsure where I > need that column and the type it needs to be. Yes, the schema can change between versions. Following the instructions on

I''m doing a redirect in one of my controller actions and somehow I can''t spec it, see this pastie: http://pastie.caboo.se/53120. When following the link from a browser I''m being redirected to the right page. -------------- next part -------------- An HTML attachment was scrubbed... URL:

run on startup by default like the other ovirt services --- conf/ovirt-vnc-proxy | 49 ++++++++ installer/modules/ovirt/manifests/ovirt.pp | 1 + ovirt-server.spec.in | 5 + src/vnc-proxy/vnc-proxy.rb | 167 ++++++++++++++++++++++++++++ 4 files changed, 222 insertions(+), 0 deletions(-) create mode 100755 conf/ovirt-vnc-proxy