search for: duplicat

Hi, It's my problem, supppose that we have a data.frame: t a b c 1 1 1 1 2 0 1 1 3 1 1 1 4 0 0 0 5 1 0 1 6 0 1 0 7 1 1 1 8 0 1 0 I need extract duplicat row i.e i nedd frame like this a b c 3 1 1 1 8 0 1 0 I try use subset(t, duplicated(t)) and t[duplicated(t), ] but this command return a b c 3 1 1 1 7 1 1 1 8 0 1 0 Best Marcin M. -- View this message in context: http://r.789695.n4.nabble.com/Removing-all-duplicate-row-except-by-one-tp37...

Every time I have upgraded via CVS in last few weeks, the queue and agent program doesn't appear to function together. The calls are not getting passed: Agent 308 is logged in and idle. Yet I have a customer that has been on hold for over 8 minutes. Any Ideas? =================================================== pbx*CLI> show agents 301 (Lee) not logged in (musiconhold is

...> it appears that 95-99 % of them are not being used. De anyone know if pch > can help here? My feeling is not much as template instantiation still > generates a ton of weak symbols on the pch users, but I might be confused. > This probably has to do with the fact that most types are duplicates. If there is a class Foo in a header file, and you include that header file in 100 different translation units, all 100 of them of them will get full type information for that class in its object file. This is the /Z7 semantics that clang-cl implements. The alternative is /Zi which uses a type...

...rote: > > Later loop unroll comes and unrolls the loop and then suddenly we have > two absolutely identical dbg.declares and the assert in addFragmentOffset() > blows. Who's at fault? > > Without having read the code yet, my intuition says that the unroller > should not be duplicating dbg.declares, only dbg.values. > I think it's a bug in both places: the backend should tolerate identical, duplicate dbg.declares, and the loop unroller probably shouldn't duplicate dbg.declare, since there is no point. IR is supposed to be duplicatable unless it is marked noduplica...

...m.org>> wrote: > > Later loop unroll comes and unrolls the loop and then suddenly we have two absolutely identical dbg.declares and the assert in addFragmentOffset() blows. Who's at fault? > > Without having read the code yet, my intuition says that the unroller should not be duplicating dbg.declares, only dbg.values. > > I think it's a bug in both places: the backend should tolerate identical, duplicate dbg.declares, I guess that's fair, yes. -- adrian > and the loop unroller probably shouldn't duplicate dbg.declare, since there is no point. > >...

...is split up into multiple fragments (such as SROA) there may be one dbg.declare per variable fragment. A dbg.declare has no means of describing liveness of a variable and is always describing the location of the variable for its entire lexical scope. > > A similar fix as yours was made for duplicate non-fragment dbg.declares in r305244 and there is a bit of discussion about it in https://bugs.llvm.org//show_bug.cgi?id=33157 > Maybe you've seen that? > > I've run into a case where the inliner leaves two dbg.declares (with different locations since they origin from two differe...

Hi all, Thanks for the answers! I feel like I've hijacked your thread now though Björn, sorry for that. But from the answers it sounds like there is agreement that it's reasonable to remove the duplicates as done in Björn's patch? --- A couple of more things around the problem I saw. On 09/19/2017 05:40 PM, Adrian Prantl wrote: > A dbg.declare describes a stack-allocated variable. There may only be > one dbg.declare per source variable, with the one exception that if > the sour...

...ignore_timeout variable is what allows the I/O code to continue updating last_io (the old method of clearing io_timeout in the generator used to leave last_io unchanged, which is no longer desireable). How short is your timeout? Are you using a delete option? I tried some tests, and couldn't duplicat the problem, so I'll need more details. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

Hi, Heiko Schlittermann <hs at schlittermann.de> (Mo 21 Nov 2016 11:50:13 CET): > a) Routing stage > You need to interact with the user database dovecot uses. > Either you access the user database directory (flat file, LDAP, > whatever) or you use the ${readsocket?} feature of Exim to talk to > dovecot. The readsocket trick doesn't seem to work anymore. Using $

Hi, I''m a newbie in both Ruby and Ruby on Rails. I finished the Ruby on Rail Tutorial on Todo list and it was great. But, now I''m trying to understand the logic behind it, that is something that is not obvious on how each one of them ties together. Is there a flowchart that shows how the inner working of Ruby on Rails? In another words, let''s suppose we consider the

For anyone following along on ToT using the gc.statepoint mechanism, you should know that ToT is currently not able to express arbitrary exceptional control flow and relocations along exceptional edges. This is a direct result of moving the gc.statepoint representation to using a token type landingpad. Essentially, we have a design inconsistency where we expect to be able to

...t;> > > > 1min6s-1min20s) I see two things: > > > > >> > > > > > > > >> > > > 1) LookupBucketFor(Val, ConstFoundBucket); takes 35s so > > > > >> > > > almost half of the time of linking, mostly finding > duplicates > > > > >> > > > 2) There is no parallelization inside of addObjectsToPDB > > > > >> > > > > > > > >> > > > Is anyone working on those? Also has anyone thought about > > > > >> > > > mergin...