similar to: Problem with scheduled task mysteriously stopping

Hi I just made some changes / additions for myself in facebooker and posted the patches on rubyforge, e.g.: https://rubyforge.org/tracker/index.php? func=detail&aid=18639&group_id=4187&atid=16130 (adds support for fb:dialog FBML tag) Is this the right way to do it? --simon -- http://simonwoodside.com

This is something I just cooked up to allow me to restrict temporarily who can access my app, based on an array of UIDs. It''s messy but works. Put at the top of your controller, at the end of your filters. # This filter is only until we open everything up before_filter do |c| acceptable_uids = [''594180515'', ''122612996''] unless

Can I second this question? Could someone provide a simple example of how they set up a functional test for a controller that uses facebooker?? Do you have to copy a lot of stuff from rails_integration_test.rb ? I guess that since we don''t have a test facebook to test against, we have to stub out a lot of stuff right? --simon > Hi, I''m wondering if folks would care

Sorry ... I''m really lazy (and insanely busy more to the point) .. but you''ll get support for fb:dialog... http://rubyforge.org/tracker/? func=detail&atid=16132&aid=18772&group_id=4187 --simon -- http://simonwoodside.com

Hi. I''m using backgroundrb to, in part, wrap smtp transactions made through actionmailer. The problem is that when smtp fails with a timeout error, the worker simply stops at that point. No exception is returned. I''ve tried wrapping this call in a begin...rescue block but no exception seems to be making it back to the worker (other methods are correctly passing exceptions to

Hi Dylan, looks ok now. One thing: the ISR is now: __vector_21: ; @__vector_21 __vector_21$local: sei push r0 push r1 in r0, 63 push r0 clr r0 push r24 lds r24, v1 sts v2, r24 pop r24 pop r0 out 63, r0 pop r1 pop r0 reti There are unneccessary push/pops of r1 and r0 too, since the clr is useless ... GCC had the same

Is there anything I can do about it? BTW: gcc is loosing the AVR backend, so I would assume, there will be a greater interest to this in llvm compared to the past. Thanks, Wilhelm Am 03.04.20 um 15:09 schrieb Wilhelm Meier via llvm-dev: > Should I create an issue in bugzilla for this? Just to be reminded ... > > Am 31.03.20 um 09:34 schrieb Wilhelm Meier via llvm-dev: >> Hi

Hey Wilhelm, That's a bug, the "interrupt" attribute is not being recognized by the backend. I have fixed it in https://github.com/llvm/llvm-project/commit/339b34266c1b54a9b5ff2f83cfb1da9cd8c9d90a Pull the latest LLVM and it should be fixed. On Tue, Mar 31, 2020 at 8:00 AM Wilhelm Meier <wilhelm.meier at hs-kl.de> wrote: > Hi Dylan, > > I used the following

Hey Wilhelm, Could you post the LLVM IR generated from your C++ file? This can be achieved with 'clang -S -emit-llvm' Cheers On Sat, Mar 28, 2020 at 6:36 PM Wilhelm Meier <wilhelm.meier at hs-kl.de> wrote: > Answering partly to myself there was a extern "C" missing. > > But the register pushes ans reti are still missing. > > Whats wrong? > > Am

I just detected, that det() is not working on complex matrices any more, due to the fix to the bug reports noted above. I am not happy with this, as determinants are perfectly usable on complex matrices. AFAIUI the bugs resulted from less than optimal behaviour of qr() in certain cases. IMHO this is due to the unhappy decision to use a default for parameter tol to decide whether the the

Hi Dylan, the following code volatile uint8_t v1; volatile uint8_t v2; __attribute__((interrupt)) void __vector_21(void) { v2 = v1; } produces in C mode: 00000092 <__vector_21>: 92: 80 91 61 00 lds r24, 0x0061 ; 0x800061 <v1> 96: 80 93 60 00 sts 0x0060, r24 ; 0x800060 <__data_end> 9a: 08 95 ret and in C++ mode: 00000074

Thanks! The new are of xmega3 architecture, which is already included. So this should be simple. Where is the information about ISR-vector table, SRAM addresses and so on stored? -- Wilhelm Am 04.03.20 um 11:03 schrieb Dylan McKay: > Hey Wilhelm, > > This should be possible by editing the 'AVRDevices.td' [1]TableGen > definitions to add an entry for the newer chip types.

Am 04.03.20 um 11:16 schrieb Dylan McKay: > > The new are of xmega3 architecture, which is already included. So this > should be simple. > > Where is the information about ISR-vector table, SRAM addresses and so > on stored? > > > At the moment, this is not implemented in LLVM; these details are left > to the frontend. Clang/compiler-rt does not

Hi, I have a number of servers running mongrel cluster all of whom feed off of a shared filesystem (OCFS2). Each cluster has its own mongrel_cluster_web2.yml file with distinct PID and Log file names. In theory they shouldn''t be aware of each other''s presence. What I have found is that when I want to test a new set of code on one server and I shut just that mongrel cluster

hello all... i am trying to install r v2.0.1 on my suse 9.2 pro box... when i run configure, i get the following error: checking how to get verbose linking output from g77... configure: WARNING: compilation failed checking for Fortran libraries of g77... checking for dummy main to link with Fortran libraries... none checking for Fortran name-mangling scheme... configure: error:

Am 04.03.20 um 13:28 schrieb Dylan McKay: > > * *The C/C++ function needs to be declared with either the calling > convention avr-interrupt or avr-non-blocking-interrupt.* Skipping > this step will cause regular ret instructions to be emitted for > return-from-subroutine, instead of the required reti for interrupt > handlers. ISRs also have stricter

Hi all I'm trying to resolve a problem that's recently popped up by turning on auxillary VLANs for our Linux workstations. The problem shows as DHCP failling for anaconda (but always succeeds for PXE). I tried adding 'ipappend 1' to the pxelinux config files but had no joy. I'm thinking that if I write a COM32 module that adds "ip=1.2.3.4 gateway=1.2.3.1

I'm beginning to use the AVR backend. I ran into the problem, that newer (tiny1, mega0) µC as a tiny1614 are not supported. How do I add these to the AVR backend? Thanks!

Hello all, I am loading a data frame, fitting a model, getting diagnostic plots and they are flagging a couple of observations as problematic. Fair enough, and I want re-fit without them. After I delete an offending row (identified by one of the diagnostic plots), something like data = data[-3,]; then R will no longer print the contents of the data frame; it tells me it is a data frame

Hi, I am not exactly sure what causes your error. But if you have a reduced test case we can try looking at it. Thanks, Arushi Hello, i wrote a little pass. It tries to identify every call- / invoke-instruction recursively and calls computeCalleeCallerMapping for each. The sample program just creates a vector of integer and adds an element to it. Do you know what's wrong? Best,