search for: disquieting

On 07/26/2016 1:26 PM, Rowland penny wrote: > On 26/07/16 19:08, Jim Seymour wrote: >> On Tue, 26 Jul 2016 12:37:51 -0500 >> Dale Schroeder <dale at BriannasSaladDressing.com> wrote: >> >> [snip] >>> Jim, >>> >>> This may be your problem: Samba 4.3.9 >>> >>> Upgrading my NT4 domain from 4.2.x to 4.3.x and beyond broke

...obabilities, I think everyone will benefit from reading at least the first 6 pages of a 19 pages English criminal sentencing statement about a child, in England, successfully breaking into the home and business computer systems of top USA CIA, FBI and Homeland Security entities. It is shocking and disquieting. Security is more than a firewall and SELINUX - it is procedures too. When the CIA director is easily hacked and his family pestered, how safe are you and your systems ? In the Crown Court at Leicester (England) The Queen versus Kane Gamble Sentenced at the Central Criminal Court (Old Bailey, Lond...

...2 requesting 0x80 returning 0x0 (NT_STATUS_OK) which makes me wonder if the code's not broken. (The thing's lying. The user's id is "Domain User", the directory is group "Domain User" and the permissions were "rwxrwxrwt".) I find more than a little disquieting is that nobody seems able to actually *troubleshoot* issues like this. Somebody ought to be able to look at logfiles and say "Oh, well, *this* is what's you're doing wrong" or "Ah! The code's broken because of <this>", or whatever. Regards, Jim -- Note: My ma...

...rning 0x0 (NT_STATUS_OK) > > which makes me wonder if the code's not broken. (The thing's lying. > The user's id is "Domain User", the directory is group "Domain User" > and the permissions were "rwxrwxrwt".) > > I find more than a little disquieting is that nobody seems able to > actually *troubleshoot* issues like this. Somebody ought to be able to > look at logfiles and say "Oh, well, *this* is what's you're doing > wrong" or "Ah! The code's broken because of <this>", or whatever. > > Rega...

This smells like a bug to me. The error is triggered by the line: variables <- eval(predvars, data, env) inside model.frame.default(). At that point, na.action has not been applied, so poly() ended being called on data that still contains missing values. The qr() that issued the error is for generating the orthogonal basis when evaluating poly(), not for fitting the linear model itself.

This smells like a bug to me. The error is triggered by the line: variables <- eval(predvars, data, env) inside model.frame.default(). At that point, na.action has not been applied, so poly() ended being called on data that still contains missing values. The qr() that issued the error is for generating the orthogonal basis when evaluating poly(), not for fitting the linear model itself.