search for: undiscov

...ould be 1, 2 ... not row1, row2 > .... And rownames(mat) is NULL. > > For an interactive function the best solution seems to be to throw an > error when the user asks for the impossible. > > I'll fix it for 2.7.0: it certainly isn't 'important' as it has gone > undiscovered for many years, and edit.matrix is itself little used. > > > BTW, 1:dim(names)[1] is dangerous: it could be 1:0. That was the > motivation for seq_len. I would agree that it is a rare user error, but my original mistake was a little more benign than the one that is depicted in the...

On Mon, Nov 5, 2018 at 11:01 AM Jan Stary <hans at stare.cz> wrote: Attached I send the spectrogram (vic SoX) of the first 20 seconds > for the wav file and the opus file. Indeed, there is extra noise > for the low frequencies, but somewhere around -100 dB. > > Jan > That might be entirely due to SoX treating it as a 16-bit file, which it is not; -100dB is almost

On Thu, 2017-02-02 at 07:16 -0800, Gordon Messmer wrote: > On 02/02/2017 06:51 AM, Leonard den Ottolander wrote: > > pkcheck might not be directly vulnerable. However, pkexec is. > > > If that's so, why are you supplying patches to pkcheck rather than > fixing pkexec? The patch has a fix for three memory leaks. One memory leak that allows heap spraying in pkexec.c that

...be used to cause the > heap and the stack to run in to each other, and that flaw has previously > been combined with bugs in glibc to produce an exploit. The glibc bug > is now fixed, but there is still a risk that collision could be > exploitable in combination with other, as yet undiscovered bugs. Yes. I understand perfectly well how this works, which is why I am so concerned. And that is exactly why I also want to fix those memory leaks in pkcheck.c. There might not be a known exploit for pkcheck.c but the vector ("heap spraying" because of a memory leak) is the same. T...

...ve any > > specific > > ideas on how to test it in mind? And I definitely agree, dominators need > > to > > be tested more thoroughly. I think that because of the manual updates (of > > questionable correctness) and frequent recalculations there must be many > > undiscovered bugs that we just haven't had a chance to observe yet. > > I think we certainly should have standard LLVM-IR style test cases, > where we use -analyze to dump the domtree for a given piece of IR that > clarfies how/what dominator tree is expected for a certain piece of > inp...

> On Jun 21, 2020, at 16:38, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: > This my reply is not intended for the OP, as he stated he will not listen about End Of Life of of PHP 5. Just in case anybody comes across this thread, please read what is written on the page referred to by Alexander Dalloz: > > >> PHP 5.6 is EOL. https://www.php.net/supported-versions.php

...... ..... don't ******* change it ? C7 appears to be a nightmare. So many problems. I do not remember as many problems with the introduction of C6. I like lasting stability. Same commands. Same reliability. No need to waste time learning new tricks when many of the existing old tricks remain undiscovered. Anyone might think RH is attempting to emulate Windoze. -- Regards, Paul. England, EU. No problems with C5 and with C6.

...That memory leak can be used to cause the heap and the stack to run in to each other, and that flaw has previously been combined with bugs in glibc to produce an exploit. The glibc bug is now fixed, but there is still a risk that collision could be exploitable in combination with other, as yet undiscovered bugs. If Red Hat is concerned with changing the behavior of pkexec in scripts, then they can still fix the memory leak without otherwise changing the behavior of the program by adding: if (opt_user != NULL) { g_free(opt_user); } ..instead of the upstream solution of failing on...

...cause the >> heap and the stack to run in to each other, and that flaw has previously >> been combined with bugs in glibc to produce an exploit. The glibc bug >> is now fixed, but there is still a risk that collision could be >> exploitable in combination with other, as yet undiscovered bugs. > Yes. I understand perfectly well how this works, which is why I am so > concerned. I apologize if my intent was unclear. I was providing you with the text that you should use in your bug report. I am not explaining the problem to you, I am showing you a clear way to explain t...

...?id=575738 This adds a Perl library Win::Hivex::Regedit which supports two functions for importing and exporting the format. I've tested this on some real output from the Windows regedit.exe program successfully. However these files are not well specified, and therefore there are bound to be undiscovered inconsistencies and corner cases. The second part will add a command line tool to hivex for merging a regedit file with a local hive. The third part will involve enhancing virt-win-reg to support this for VMs. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~...

...is sample. For instance, encoding it at 130 > gives me a file of 210kbps. Over a wide corpus of music, I've noticed > libopus almost invariably overshoots the bitrate, rather than averaging out > close to it; only speech is consistently at or below it. Maybe there's some bug still undiscovered. Would you agree that Opus should encode a pure sinus tone efficiently? Or would it really prefer to encode white noise? Regards, Ulrich

Scott Robbins wrote: > On Tue, Apr 26, 2016 at 07:27:26PM -0700, Alice Wonder wrote: >> >> Some of the BSDs use to have a bourne shell and maybe some do, I don't know. >> > Yup. > >> bash is mostly compatible with bourne (can run most bourne scripts) which is why /bin/sh is a symlink to /bin/bash on GNU and most other *nix systems. > > Bash can run

...{ +/* XXX printf("Get next page failed, ret is %d.\n", ret); */ return(OV_EOF); /* eof. leave unitialized */ } This is the last of the known issues with large files on my FreeBSD system -- though, as noted, I need to play through an entire >4GB file to make sure there aren't any undiscovered problems. (Some other utilities like `ogginfo' may need attention, or it could be that I simply haven't rebuilt them.) As always, other OSen may have problems with other patches I've already sent, so those need to be massaged into portability. And as noted, playing such a file te...

Undiscovered Gem St0ck_Report Company Profile: +++++++++++++++++++++++++++++++++++++++++++++++++ CEO AMERICA INC. Symbol: CEOA . pk Recent Price: $3.00 Expected Trading Range: $5.50 - $6.00 (post split) Shares Outstanding: 35M (est.) Float (est.): 5M ++++++++++++++++++++++++++++++++++++++++++++++++++ Th...

Hello everyone, I would like to get some advices on using R with some really large datasets. I'm using RH9 Linux R 1.8.1 for a research with a lot of numerical data. The datasets total to around 200Mb (shown by memory.size). During my data manipulation, the system memory usage grew to 1.5Gb, and this caused a lot of swapping activities on my 1Gb PC. This is just a small-scale experiment, the

...ld also make it possible to think in terms of "attaching" directories of objects. (At attach time all the objects in a directory would be registered as loadables, and loaded when required). [Status: I have thought a bit about this. It should be pretty simple but no doubt there are a few undiscovered gotchas in there] 5. Change Internal Handling of Lists Do a rewrite of the internal handing of lists so that they are really generic vectors. This will mean large volumes of fairly flakey subsetting and mutation code can be removed. [Status: It is important to get this done, but it will be...

...re interested. > > This way, you're not relying on the network for anything other than the > copies; everything else takes place on the local or backup system. > > A> Using a scripted rsync is the simpler way but there is something that > A> could be leaved out by me (or undiscovered error). Simple to restore. > > I've never had a problem with rsync, and I've used it to back up Linux > workstations with ~600Gb or so. One caveat -- if you give it a really > big directory tree, it can get lost in the weeds. You might want to do > something like this: &g...

$ c++ --version c++ (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4 On 20.06.2016 21:55, Kevin Duraj wrote: > Emmanuel, > Which version of C++ compiler are you using? > > $ c++ --version > c++ (GCC) 4.9.3 > Copyright (C) 2015 Free Software Foundation, Inc. > > -Kevin > > > On Mon, Jun 20, 2016 at 6:58 AM, Emmanuel Engelhart <kelson at kiwix.org > <mailto:kelson

On 11 March 2015 at 04:14, Chandler Carruth <chandlerc at google.com> wrote: > Just to rebase things a bit, here is some context. > > - This is a 60+ email thread spreading across a month of time. > - I've not read every single email and I don't think it makes sense to > assume the context of the first email applies to the most recent. I think we all agree that

...lication I could use fs like zfs (not available from epel) or use something like stratis (I don't checked if it offer deduplication in this moment). Encryption could be performed on fs level. Using a scripted rsync is the simpler way but there is something that could be leaved out by me (or undiscovered error). Simple to restore. BorgBackup is another solution similar to rsync in some way. It works like rsync through ssh but while rsync simply sends data, borg run deduplication, compression and encryption on place. Why is similar rsync? Because I need another script to run borg. It is not...