similar to: rawk no longer works on Rails 2.2.2

Hi all, I am in the process of adding Migration support to the Ingres ActiveRecord adapter and have run in to a problem. During the call to create_table the Ingres adapter some how causes ruby to blow the stack and coredump/segv. I have tracked down the problem down to "add_column_options!" in "lib/active_record/connection_adapters/abstract/schema_statements.rb".

Hi all, I am in the process of adding Migration support to the Ingres ActiveRecord adapter and have run in to a problem. During the call to create_table the Ingres adapter some how causes ruby to blow the stack and coredump/segv. I have tracked down the problem down to "add_column_options!" in "lib/active_record/connection_adapters/abstract/schema_statements.rb".

So Rails2 provides a new BufferedLogger class that is used for logging. The old monkey-patched Logger class is deprecated. It''s nice that the new BufferedLogger doesn''t do that weird monkey patching thing, making it easier to sub-class for custom behavior and set your sub-class as the logger, etc. But oddly, BufferedLogger is not a sub-class of the Ruby logger. It''s

Hi there, I''m wondering if there''s a way to have any log statements generated from a specific method on a model get logged into a separate file from the normal development/production log files? i.e. I want the whole app to log as normal, apart from the Sprinter.run_often method, which I''d like to log to sprinter_running.log Cheers, Tim.

Dear CentOS folk, I've been try to solve one issue with rsyslog on CentOS 6, but can't figure it out. I've searched through rsyslog documentation, and used Google but not found anything that matches my issue. I'm sending output of a program to rsyslog using "logger -t progname". I've got the following config snippet in /etc/rsyslog.d: $FileCreateMode 0644 if

On 31/10/2023 4:32 a.m., Tomas Kalibera wrote: > > On 10/30/23 19:07, Yihui Xie wrote: >> Sure. I'm not sure if it's possible to make it easier to reproduce, >> but for now the example would require installing TinyTeX (via >> tinytex::install_tinytex(), which can be later uninstalled cleanly via >> tinytex::uninstall_tinytex() after you finish the

On 10/30/23 19:07, Yihui Xie wrote: > Sure. I'm not sure if it's possible to make it easier to reproduce, > but for now the example would require installing TinyTeX (via > tinytex::install_tinytex(), which can be later uninstalled cleanly via > tinytex::uninstall_tinytex() after you finish the investigation). Then > run: > > ? system2('fmtutil-sys',

On 10/31/23 10:05, Duncan Murdoch wrote: > On 31/10/2023 4:32 a.m., Tomas Kalibera wrote: >> >> On 10/30/23 19:07, Yihui Xie wrote: >>> Sure. I'm not sure if it's possible to make it easier to reproduce, >>> but for now the example would require installing TinyTeX (via >>> tinytex::install_tinytex(), which can be later uninstalled cleanly via

The entries in xenstore have permission attributes. The attributes can be easily altered by xenstore-chmod, however, I cannot find a easy way to see them. I''ve modified xenstore_client.c to raise a new utility. The utility checks the permission and makes an easy-look output. Please tell me any suggestions. Thanks. Signed-off-by: Frank Pan <frankpzh@gmail.com> ---

Otherwise, we get a failure due to Numerical result out of range. And for safety's sake, we are best capping our request to an aligned value, if the server insists on minimum alignment. Fixes: f3fd935c --- info/nbdinfo.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/info/nbdinfo.c b/info/nbdinfo.c index 1afdf98..2b22f51 100644 --- a/info/nbdinfo.c +++

Hi, as discussed in [1], this series adds a new getprogname module. All it does is providing a getprogname function, much like what is found on e.g. *BSD systems, and using it in gnulib instead of progname. Also, using it explicitly by modules avoids gnulib users the need of either use the progname module (GPL), or to provide program_name (and call set_program_name manually, which is not always

hello hpa, nothing particular stands out, just syncing with latest Debian upload and subsequent patch emails. please review merge or nack. thanks :) maks git pull git://git.debian.org/~maks/klibc.git maks for the changes: Aaron Griffin (1): [klibc] kinit: skip md assembly if mdX exists Colin Watson (1): [klibc] mount/umount FUSE support Harald Jenny (1): [klibc] fstype:

I have some binaries I would like to distribute with a package (I am not the original author; I have the source code but can't distribute it because it contains _Numerical Recipes_ code. The long-term solution is to replace the code with new code written in R, or in clean C, but in the meantime ...) I'm uncertain both where they ought to go and where they will work (and hoping there

On Tue, May 30, 2023 at 04:06:32PM +0200, Laszlo Ersek wrote: > On 5/25/23 15:00, Eric Blake wrote: > > Support sending 64-bit requests if extended headers were negotiated. > > This includes setting NBD_CMD_FLAG_PAYLOAD_LEN any time we send an > > extended NBD_CMD_WRITE; this is such a fundamental part of the > > protocol that for now it is easier to silently ignore

Hi, We have experienced some problems with ActiveRecord::Base class of Ruby-Rails. We are building a web-application based on the Ruby-rails framework and the web-application needs to access to difference databases, so we do not pre-define our database accesses in the database.yml file. In fact, we are using the ActiveRecord::Base.establish_connection() to connect to our database, the function

I tried to extend it , with this class , loaded at config time : config.autoload_paths += Dir["#{config.root}/lib", "#{config.root}/lib/**/", "#{config.root}/app/inputs"] lib/extension.rb class ActiveSupport::BufferedLogger def detailed_error(e) error(e.message) e.backtrace.each{|line| error line } end end but calling it in my controller rescue

hello hpa, please pull latest git pull git://git.debian.org/~maks/klibc.git maks forgot to ask to keep git port open for our boxes at university, thus moved my tree over too the alioth box. for the changes maximilian attems (4): [klibc] klibc/socketcalls/.gitignore addition [klibc] elf.h add support for st_info field [klibc] remove local insmod.c copy [klibc] ipconfig

Here is a very simple spec: -- require File.expand_path(File.dirname(__FILE__) + ''/../spec_helper'') describe Product, "The Product model" do describe "When a new blank product object gets created" do before(:each) do @product = Product.new end it "should not be valid" do @product.should_not be_valid

Nearly any program that writes to standard output can benefit from this sort of fix. Without it, running e.g., ./guestfish --version > /dev/full would exit successfully, even though it got ENOSPC when writing to the full device. That means regular output redirected to a file on a full partition may also fail to be written, and the error ignored. Before: $ guestfish --version >

First off, I managed to build iceS 0.2.2 with Python 2.1, though I had to add -lutil to the $LIBS definition whilst ./configure'ing. Otherwise, configure won't find Py_Initialize Secondly - multiple streams I've added a second "stream" definition to my ices.conf, and both streams show up as sources for icecast, (http://blah.com:8000/list.cgi), though when i try to connect