search for: _destroy

...alled "admin_email_address" I want to validate when saving the ticket and say "if I have a new admin comment, make sure I have an admin_email_address" In my ticket model, the method to do the validate looks like the following and works as expected except for one thing. If the :_destroy flag on the comment was set in my comment view partial (I want to delete a comment), it seems like this iterating over the comments with new_record? somehow resets that :_destroy flag. Am I doing something wrong here? Or, could someone give me a hint on a more simple way to do this validation.? T...

...f set/get methods for the value class, and initialize it in Value::Value(const Type *ty, ValueTy vty, const std::string &name). But, when I set the privative member of a value in my pass, analyse gives me: analyze[0x83f0a00] analyze[0x83f0c0c] /lib/tls/libc.so.6[0x420275c8] analyze(void std::_Destroy<llvm::Use>(llvm::Use*)+0x11)[0x8296921] analyze(void std::__destroy_aux<llvm::Use*>(llvm::Use*, llvm::Use*, __false_type)+0x1c)[0x8297570] analyze(void std::_Destroy<llvm::Use*>(llvm::Use*, llvm::Use*)+0x1a)[0x82968f0] analyze(std::vector<llvm::Use, std::allocator<llvm::Use&...

...nt to have a Add/Selected checkbox with which the user can pick the items he wants to return. I know I could use a ''selected'' virtual attribute but I don''t want to pollute my model just for this. In fact, there is something that does exactly the opposite that I want, the :_destroy: <%= i_f.check_box :_destroy %> I would like exactly the opposite, :_select. Anybody has figured this out before? Thanks guys, Gam -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyo...

...; </tr> <tr> <td class ="name"> commentaires sur la preparation : </ td><td></td><td><%= f.text_field :preparation %></td> <td></td> </tr> <%= f.hidden_field :_destroy %> <tr><td><%= link_to_function "remove", "remove_fields(this)" %></td></tr> </p> and in the appliction.js file I have: function remove_fields(link) { $(link).previous("input[type=hidden]").value = "1"; $...

...t; class, and initialize it in Value::Value(const Type *ty, ValueTy vty, const std::string &name). But, when I set the privative > member of a value in my pass, analyse gives me: > > analyze[0x83f0a00] > analyze[0x83f0c0c] > /lib/tls/libc.so.6[0x420275c8] > analyze(void std::_Destroy<llvm::Use>(llvm::Use*)+0x11)[0x8296921] > analyze(void std::__destroy_aux<llvm::Use*>(llvm::Use*, llvm::Use*, __false_type)+0x1c)[0x8297570] > analyze(void std::_Destroy<llvm::Use*>(llvm::Use*, llvm::Use*)+0x1a)[0x82968f0] > analyze(std::vector<llvm::Use, std::allocato...

...still be present in memory after the update, and in invalid data being saved (foreign key violations) because the parent record saved still has the association_id set even though the associated record has been destroyed. Here is a test demonstrating the error and the expectations: def test_should_destroy_an_existing_record_if_there_is_a_matching_id_and_destroy_is_truthy @ship.pirate.destroy [1, ''1'', true, ''true''].each do |truth| pirate = @ship.reload.create_pirate(:catchphrase => ''Arr'') @ship.update_attributes(:pirate_attributes =...

...his=0x689648, first=<value optimized out>, last=...) at /home/kharris/llvm30/cl-install/include/llvm/Support/ValueHandle.h:74 #2 ~AssertingVH (this=0x689648, first=<value optimized out>, last=...) at /home/kharris/llvm30/cl-install/include/llvm/Support/ValueHandle.h:182 #3 _Destroy<llvm::AssertingVH<llvm::Instruction> > (this=0x689648, first=<value optimized out>, last=...) at /usr/include/c++/4.5/bits/stl_construct.h:89 #4 __destroy<llvm::AssertingVH<llvm::Instruction>*> (this=0x689648, first=<value optimized out>, last=...)...

...td> <td><%= address_form.select(:country, @countries.map {|u| [u.name,u.id]}) %></td> </tr> </table> <% unless address_form.object.nil? || address_form.object.new_record? %> <div class="field"> <%= address_form.label :_destroy, ''Remove:'' %> <%= address_form.check_box :_destroy %> </div> <% end %> <% end %> Can you guys help me out with what i''m missing? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: T...

...t, shouldn''t the client (since they are providing a patch) be able to only specify which members are be deleted? Possibly support could be added for a new _remove key on the object to be removed from a list? That would seem to be a good name. That way you could either use the existing _destroy key that allows you to destroy the associated object or could use the new _remove key to just indicate that in your patch request you are specifying to remove it from the list. So, if the _method were "patch", then just specifying a list of objects only indicating their IDs wouldn'...

I noticed that in the narrow band and wide band destroy functions only the main pointer is being freed. I think that it should be: void nb_decoder_destroy(void *state) { DecState *st; st=(DecState*)state; speex_free (st->inBuf); speex_free (st->excBuf); speex_free (st->innov); speex_free (st->interp_qlpc); speex_free (st->qlsp); speex_free (st->old_qlsp); speex_free (st->interp_qlsp); spee...

...version); Since dynamic linking is supported, a build-time constant is not suitable. Currently, I resorted to have libcelt generate a dummy header to get the version_id field. * The header_size is set to 56, while the header is actually 60 bytes. Is it normal? * It seems that the celt_*_destroy all accept NULL without choking, just like libc's free. If this is on purpose, could it be stated in the documentation? Regards, -- Nicolas George -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 19...

...ll in buffer_wait_for_empty(). *If* I understand the control flow correctly, the decoder thread waits on a condition variable here that has already been removed by the other thread winding down in buffer_thread_cleanup(). This would result in "undefined behavior". Removing the pthread_*_destroy() calls from buffer_thread_cleanup() eliminates the crash. --- ogg123/buffer.c.orig Thu Dec 20 01:24:53 2001 +++ ogg123/buffer.c Wed Jan 16 03:26:15 2002 @@ -88,9 +88,11 @@ /* Cleanup thread data structures */ pthread_mutex_unlock(&buf->mutex); +#if 0 /* KLUDGE: disabling this keeps...

...picker), the start and end times are selected using a time_select form helper. The examdates are then created using `accepts_nested_attributes_for`: ~~~ {.ruby} class Exam < ActiveRecord::Base has_many :examdates, :dependent => :destroy accepts_nested_attributes_for :examdates, :allow_destroy => true ... end class Examdate < ActiveRecord::Base belongs_to :exam validates_presence_of :date, :from, :to # date + time fields ... end ~~~ When I create a new exam, the following request is issued: ~~~ Started POST "/exams" for 127.0.0.1 at 2013-03-14 10:11:32 +0100 P...

Prepare for transition to RCU-based event handler list; since RCU list traversal may have stale pointers, local storage may go out of scope before handler completes. Introduce nouveau_event_handler_create/_destroy which provides suitable semantics for multiple, temporary event handlers. Signed-off-by: Peter Hurley <peter at hurleysoftware.com> --- drivers/gpu/drm/nouveau/core/core/event.c | 24 +++++++++++++++++++++++ drivers/gpu/drm/nouveau/core/include/core/event.h | 6 ++++++ drivers/gpu/...

Greetings, I noticed a while back someone posted a patch/plugin that allowed Dovecot to use compressed mbox files. I'm now wondering how far that would put us from having compressed maildir? I have a server with more CPU than disk space, and while I can buy more HDD space, my backup solution doesn't make that practical. It seems to me that when looking for a message file, if it

...for the wide-format): > > Event Handler function Container Until > ----- ---------------- --------------- ------------------ > gpio nouveau_connector_hotplug struct nouveau_connector nouveau_connector_destroy > uevent nouveau_fence_wait_uevent_handler local stack object nouveau_fence_wait_uevent returns > cevent none n/a n/a > vblank nouveau_drm_vblank_handler struct nouveau_drm nouveau_drm_remove > vblank...

Following series cleans up a few niggles in the libxl destructor autogeneration. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...{physical_size = 80, virtual_size = 84, lines = 0}, body_size = {physical_size = 4387, virtual_size = 4566, lines = 179}, flags = 72, context = 0x0} (gdb) print in *(input->real_stream) $9 = {iostream = {pool = 0xb9598, refcount = 1, close = 0x615a0 <_close>, destroy = 0x615a8 <_destroy>, set_max_buffer_size = 0x615e4 <_set_max_buffer_size>}, read = 0x61a20 <_read>, seek = 0x61b9c <_seek>, sync = 0x61cc4 <_sync>, stat = 0x61cd8 <_stat>, istream = {v_offset = 1387, stream_errno = 0, mmaped = 0, closed = 0, seekable = 0, eof = 0, real_str...

...quester_contact"=>"chitra", "needed_by(1i)"=>"2013", "needed_by(2i)"=>"2", "needed_by(3i)"=>"12", "w_a_details_attributes"=>{"0"=>{ "description"=>"d", "_destroy"=>"false", "id"=>"5000000015"}}}, "commit"=>"Update A w request", "id"=>"5000000022"} *Stack trace: *activerecord (3.1.3) lib/active_record/nested_attributes.rb:461:in `raise_nested_attributes_record_not_foun...

²Š'