Displaying 11 results from an estimated 11 matches for "checkmate".
2008 Mar 06
2
audio file validation tool ?
I need a command line tool to validate mp3 file(s).... just something
that scans the file and looks for structural errors and reports it.
background, I've recovered a few 1000 MP3 files off a dying disk drive
for a radio station, some of the other files I recovered had several K
byte long blocks of zeros splatted in the middle where the dying drive
did bad sector remapping (SMART
2006 Apr 06
3
Drag and drop events. Or: How I learned to take over the world.
...e 100%
possible to do everything I want with it. But that has not stopped
me from trying thus far.
The project: a javascript drag-n-drop chess game.
The goal: Make a chess game that can track movements for players,
make sure moves are valid, remove pieces on capture. I figure
stalemate/checkmate calculations can be left to the players for now.
What do I have done? Not a ton. I got stuck. Which is why I need
you all.
What is my problem(s)? Simply, events. I think I need to use a lot
of event listeners to handle this well, but there does not appear to
be a ton of doc on draggab...
2019 Aug 28
1
R CMD check issue
...ice?
By the way, the failure shown was an (uncaught) bug in cox.zph wrt putting dimnames on one
of the result matrices.
Terry T
----------------------
--- re-building ?timeSplitter.Rmd? using rmarkdown
Loading required package: forestplot
Loading required package: grid
Loading required package: checkmate
Loading required package: Gmisc
Loading required package: Rcpp
Loading required package: htmlTable
Attaching package: 'dplyr'
The following objects are masked from 'package:stats':
??? filter, lag
The following objects are masked from 'package:base':
??? intersect, se...
2016 Feb 11
2
inconsistency in treatment of USE.NAMES argument
...atasets.R:226
/BBmisc/R/toRangeStr.R:33
/DBI/R/DBDriver.R:205
/Kmisc/R/str_rev.R:37
/Matrix/R/diagMatrix.R:98
/MuMIn/R/utils-models.R:110
/OpenMx/R/MxNamespace.R:702
/OrthoPanels/R/opm.R:167
/XML2R/R/utils.R:16
/assertive.base/tests/testthat/test-utils.R:14
/bigrquery/R/utils.r:13
/bold/R/zzz.R:29
/checkmate/R/checkList.r:56
/coin/R/ExactDistributions.R:80
/coin/R/ExactDistributions.R:97
/coin/R/ExactDistributions.R:234
/coin/R/SymmetryTests.R:217
/copula/R/aux-acopula.R:950
/covr/R/data_frame.R:13
/covr/R/display_name.R:40
/cplm/R/lme4_lmer.R:423
/crunch/R/batches.R:71
/crunch/R/batches.R:102
/crunch/...
2019 Nov 07
5
[PATCH v2 02/15] mm/mmu_notifier: add an interval tree notifier
...interval_tree_insert(&mrn->interval_tree,
> + &mmn_mm->itree);
> + }
> + mrn->invalidate_seq = mmn_mm->invalidate_seq;
> + } else {
> + WARN_ON(mn_itree_is_invalidating(mmn_mm));
> + mrn->invalidate_seq = mmn_mm->invalidate_seq - 1;
Ohhh, checkmate. I lose. Why is *subtracting* the right thing to do
for seq numbers here? I'm acutely unhappy trying to figure this out.
I suspect it's another unfortunate side effect of trying to use the
lower bit of the seq number (even/odd) for something else.
> + interval_tree_insert(&mrn->...
2019 Nov 07
2
[PATCH v2 02/15] mm/mmu_notifier: add an interval tree notifier
...mp;mmn_mm->itree);
> > > + }
> > > + mrn->invalidate_seq = mmn_mm->invalidate_seq;
> > > + } else {
> > > + WARN_ON(mn_itree_is_invalidating(mmn_mm));
> > > + mrn->invalidate_seq = mmn_mm->invalidate_seq - 1;
> >
> > Ohhh, checkmate. I lose. Why is *subtracting* the right thing to do
> > for seq numbers here? I'm acutely unhappy trying to figure this out.
> > I suspect it's another unfortunate side effect of trying to use the
> > lower bit of the seq number (even/odd) for something else.
>
> I...
2019 Nov 07
0
[PATCH v2 02/15] mm/mmu_notifier: add an interval tree notifier
...erval_tree,
> > + &mmn_mm->itree);
> > + }
> > + mrn->invalidate_seq = mmn_mm->invalidate_seq;
> > + } else {
> > + WARN_ON(mn_itree_is_invalidating(mmn_mm));
> > + mrn->invalidate_seq = mmn_mm->invalidate_seq - 1;
>
> Ohhh, checkmate. I lose. Why is *subtracting* the right thing to do
> for seq numbers here? I'm acutely unhappy trying to figure this out.
> I suspect it's another unfortunate side effect of trying to use the
> lower bit of the seq number (even/odd) for something else.
If there is no mmn_mm->...
2019 Nov 07
0
[PATCH v2 02/15] mm/mmu_notifier: add an interval tree notifier
...es that if seq does wrap we
> * will always clear the below sleep in some reasonable time as
> * mmn_mm->invalidate_seq is even in the idle state.
> */
>
OK, that helps a lot.
...
>>> + mrn->invalidate_seq = mmn_mm->invalidate_seq - 1;
>>
>> Ohhh, checkmate. I lose. Why is *subtracting* the right thing to do
>> for seq numbers here? I'm acutely unhappy trying to figure this out.
>> I suspect it's another unfortunate side effect of trying to use the
>> lower bit of the seq number (even/odd) for something else.
>
> No,...
2016 Feb 08
2
inconsistency in treatment of USE.NAMES argument
Hi,
Both vapply() and sapply() support the 'USE.NAMES' argument. According
to the man page:
USE.NAMES: logical; if ?TRUE? and if ?X? is character, use ?X? as
?names? for the result unless it had names already.
But if 'X' has names already and 'USE.NAMES' is FALSE, it's not clear
what will happen to the names. Are they going to propagate to the
result
2019 Nov 07
1
[PATCH v2 02/15] mm/mmu_notifier: add an interval tree notifier
...erval_tree,
> > + &mmn_mm->itree);
> > + }
> > + mrn->invalidate_seq = mmn_mm->invalidate_seq;
> > + } else {
> > + WARN_ON(mn_itree_is_invalidating(mmn_mm));
> > + mrn->invalidate_seq = mmn_mm->invalidate_seq - 1;
>
> Ohhh, checkmate. I lose. Why is *subtracting* the right thing to do
> for seq numbers here? I'm acutely unhappy trying to figure this out.
> I suspect it's another unfortunate side effect of trying to use the
> lower bit of the seq number (even/odd) for something else.
No, this is actually done...
2019 Oct 28
32
[PATCH v2 00/15] Consolidate the mmu notifier interval_tree and locking
From: Jason Gunthorpe <jgg at mellanox.com>
8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1,
scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where
they only use invalidate_range_start/end and immediately check the
invalidating range against some driver data structure to tell if the
driver is interested. Half of them use an interval_tree, the others