search for: raises

Hi, Yesterday, I’ve landed a description for how reported bugs should be flowing through the various stages of a bug’s life (triage, fixing, closing, …) at http://llvm.org/docs/BugLifeCycle.html. Thanks for the many many people who provided ideas and feedback for this! With there now being a description of what is expected during bug triaging

Hi Zach, Thanks for putting the data in a spreadsheet - that’s easier to navigate. And thanks for re-raising the question whether we have the right components in bugzilla. As I think this could be an area for lots of different opinions, without any near-perfect solution, it has the potential to be a discussion that drags on for a long time. I thought half of all bugs not getting triaged was a

Hi Zach, Thanks for elaborating. I like your proposal. I agree it still groups per area of expertise. And it makes the set of components we have easier to manage. Before making changes though I hope to hear opinions from others on this. What do others think? Thanks, Kristof On 9 Nov 2018, at 18:05, Zachary Turner <zturner at google.com<mailto:zturner at google.com>> wrote: To

I had considered a libraries/Backends:Other as well that would be separate from libraries/Other On Fri, Nov 9, 2018 at 11:20 AM Derek Schuff <dschuff at google.com> wrote: > I wonder if backends are a special case to the heuristic of "let's not > make a bug component for code components that are too small". LLVM is > factored to cleanly separate backend code, to the

Hi folks, I''m in the process of converting a Test::Unit functional test to RSpec, but I''ve run into a slight problem. I tried looking through the documentation but I still don''t know what I missed. Thanks in advance, Blake describe VenuesController, "on update" do before(:each) do @venue = mock("venue")

On Tue, 2023-08-15 at 07:34 +0530, Anantha Raghava H A via samba wrote: > Hi, > > We have a test environment with Samba Version 4.18.5 which is set to > Forest, Domain and lowest function Level of 2008 R2. I am trying to > raise the forest and domain levels. > > However, when I try to raise the domain level, I get an error - > "ERROR: > Domain function level

Hi, We have a test environment with Samba Version 4.18.5 which is set to Forest, Domain and lowest function Level of 2008 R2. I am trying to raise the forest and domain levels. However, when I try to raise the domain level, I get an error - "ERROR: Domain function level can't be higher than the lowest function level of a DC!" and when I try to raise the forest level I get an

Hi, Setting up a test environment for 4.19 rc2. However, can't we raise the lowest functional level higher than 2008 R2 in 4.18.x? Thanks & Regards, Anantha Raghava H A DISCLAIMER: This e-mail communication and any attachments may be privileged and confidential to Exzatech Consulting And Services Pvt. Ltd., Bangalore, and are intended only for the use of the recipients named above

...neater than fiddling with lambdas everytime this sort of behaviour is needed But can we go further ? I was writing a test today and I wanted the first call to a method to raise an exception and the next call to return a value (I was testing a method on an ActiveRecord object where if save! raises StaleObjectError then we reload and retry in the proper way, the second call to save! shouldn''t raise.). The same basic method works: lambdas = [lambda {raise ''Foo''}, lambda {return true}] object.stubs(:save!).returns {lambda {lambdas.shift.call}} It''s a lot...

Hi there, I''m using Log4r in my rails projects. On log.error an email is sent using the EmailOutputter. I know changed the EmailOutputter to include a global var in the subject (MDC) since the subject is normally static. I want to set this var to the exception message, so it is sent as the subject. Can anyone tell me how to do this in rails? Basically: raise e or some other cause

Hi, I''m trying to use dtrace to signal threads in my app when certain events happen, and the raise() action seemed adequate -- looking at the kernel sources, it sends a signal to the currently executing thread, and a quick microbenchmark confirmed this. However, further testing showed that if lots of threads hit the event simultaneously, the signal only gets delivered once, and may also

Hi. We are using samba4 as our production AD for a while in a mixed (XP, win2k3, win7, win2k8) environment. This post: http://lists.samba.org/archive/samba-technical/2011-February/076525.html mentions that to raise the functional level one should use this command: samba-tool domainl evel raise --domain=2008 --forest=2008 but in our current git version this command doesn't work due to the

Was hoping it might get some help or a better explanation of this: /ADT/APInt.h:1217: uint64_t llvm::APInt::getZExtValue() const: Assertion `getActiveBits() <= 64 && "Too many bits for uint64_t"' failed. Program received signal SIGABRT, Aborted. 0x00007ffff6eb4d05 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64

G'day All, We are trying to raise the level of our test samba4 DCs. Our windows dude wants the Domain level to be 2012_R2. I am referencing: https://wiki.samba.org/index.php/Raising_the_Functional_Levels#Supported_Functional_Levels We managed to get both domain and forest levels to 2008 R2 - forest was 2003. However, when we try to raise further, we are getting what seems to be a

With : PostgreSQL 8.4 or postgresql-8.3 rails 2.3.4 pg 9.x or pg 8.x I test this code: ========================= class NkiBatch < ActiveRecord::Base Bank.connection.transaction do bank = Bank.new(:name => "ddsjdsjdsjk") bank.save! raise ActiveRecord::Rollback.new end end and this: ========================= class NkiBatch < ActiveRecord::Base

Hi, today I updated my DC debian 12 to samba 4.19rc2 from mjt repository and I tried to increase feature level of domain but failed. First 2 commands was ok: samba-tool domain schemaupgrade --schema=2019 samba-tool domain functionalprep --function-level=2016 the third instead failed: > samba-tool domain level raise --domain-level=2016 --forest-level=2016 > ERROR(<class

Hi David, Any thoughts on either this pull request, or #129? https://github.com/networkupstools/nut/pull/128 https://github.com/networkupstools/nut/pull/129 Also note the mention of the new Python module here: https://github.com/george2/python-nut2/tree/development - Charles Begin forwarded message: > From: george2 <notifications at github.com> > Subject: [nut] PyNUT: Fix error

Hi, have permanent failure when try to create VDI on local SR type=file or type=ext. On both types it failed with the same error: SR_BACKEND_FAILURE_78 VDI Creation failed [opterr=error 127] I am on Debian box with kernel 3.3.0-rc7, Xen version 4.1.2 (Debian 4.1.2-2.1), Xen-API Version: 1.3.2-4 (Kronos) Is it a bug, or am I missing something? Anybody managed to workaround this problem? Here is

Hi all, any body can tell me why i am receiving this message in my sever ? I have running * with 10 Digital Lines, but i am receiving a lot of times this message . Is a software issue or is a hardware issue ? Regards. Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:2672 handle_uc_event: Unicall/5 event Alarm Mar 27 12:58:24 WARNING[2586]: chan_unicall.c:3091 handle_uc_event: Unicall/5 Alarm masks

Hello, Is anyone else having trouble with the and_raise method on mocks, with respect to shared behaviors? If I do the following instead: foo.should_receive(:bar).and_return { raise } everything seems to work. I have been supplying no arguments to and_raise, by the way. Also, you may want to make the background in the code examples on the home page a little lighter. I am hardly able to