search for: untest

Hi, Can you give me some councils of remotely rebooting sip phones in asterisk server? How to configure sip_notify.conf and sip.conf? Kind regards, Guan ; Reboot Polycom Phone Event=>check-sync Content-Length=>0 ; Untested (Reboot Sipura Phone) Event=>resync Content-Length=>0 ; Untested (Reboot GrandStream Phone) Event=>sys-control ; Untested (Reboot Cisco Phone) Event=>check-sync Content-Length=>0

Fresh off the presses, completely untested... use at your own risk... -hpa -------------- next part -------------- A non-text attachment was scrubbed... Name: tmpfs-root.patch Type: text/x-patch Size: 1493 bytes Desc: not available Url : http://www.vas.nu/pipermail/klibc/attachments/20050404/dd420f06/tmpfs-root.bin

...ty = LDPV_DEFAULT; - break; case GlobalValue::HiddenVisibility: sym.visibility = LDPV_HIDDEN; break; - case GlobalValue::ProtectedVisibility: - sym.visibility = LDPV_PROTECTED; - break; } } all the tests still pass. Is it just dead, or untested? Thanks, -- Davide "There are no solved problems; there are only problems that are more or less solved" -- Henri Poincare

...40..283b9db 100644 --- a/usr/klibc/README.klibc +++ b/usr/klibc/README.klibc @@ -33,7 +33,7 @@ b) If you're cross-compiling, you need to set KLIBCARCH to the The following is the last known status of various architectures: - alpha: Working + alpha: Runtime breakage arm-thumb: Untested arm: Working arm26: Not yet ported @@ -44,19 +44,18 @@ b) If you're cross-compiling, you need to set KLIBCARCH to the ia64: Working static, shared untested m32r: Untested m68k: Working - m68knommu: Not yet ported mips: Working mips64: Not yet ported -...

...g repo. I've also uploaded libvirt 1.2.15. As you may have seen earlier today, virt6-testing also includes an updated 4.4.2 package with the latest security update (XSA-133). The kernel has had some basic testing (by myself, Johnny, and another community member), but libvirt is at the moment untested, so caveat emptor. With such a large change, I want to leave both up for a few weeks before pushing them into the main repo. Please test them and report any errors you find. As a reminder, you can use the virt6-testing repo by putting the following file into /etc/yum.repos.d: [virt-testing] n...

Seems to be largely untested... anyone using this? (cc'ing Kevin as he's the most likely candidate). At the least for MCAnalysis this appears to be unused, any ideas on what else can be deleted? I'll remove just this file unless there are objections tomorrow (or earlier if I get an ack from Kevin about it). -er...

On 2019/9/8 ??7:05, Michael S. Tsirkin wrote: > iovec addresses coming from vhost are assumed to be > pre-validated, but in fact can be speculated to a value > out of range. > > Userspace address are later validated with array_index_nospec so we can > be sure kernel info does not leak through these addresses, but vhost > must also not leak userspace info outside the allowed

On 2019/9/9 ??10:45, Michael S. Tsirkin wrote: > On Mon, Sep 09, 2019 at 03:19:55PM +0800, Jason Wang wrote: >> On 2019/9/8 ??7:05, Michael S. Tsirkin wrote: >>> iovec addresses coming from vhost are assumed to be >>> pre-validated, but in fact can be speculated to a value >>> out of range. >>> >>> Userspace address are later validated with

The attached patch attempts to implement Theora's cropping frame in Cortado. I make no claim that it is likely to work, as I have no clue how to build and test Jheora/Cortado. Please test. Thank you. I can at least confirm that CropImageFilter and FilteredImageSource were present in JDK 1.1. Performance impact in the absence of cropping should be negligible. With cropping, there might be

The two patches attached allow 9p filesystems to be mounted and listed. Note that I did *not* test the new list-9p function, because I don't have a guest with a new enough kernel handy. 9p filesystems are not included in the output of list-filesystems. Because a lot of existing code feeds the output of list-filesystems directly into the input of mount-options, mount-ro or (even worse) plain

.... Without this we might free a page (and have another user touch it) while the hypervisor is unprepared for it. But, if the bit is _not_ set, we are under no obligation to reverse the order. Furthermore, all modern qemus set this bit. So, the "tell second" code is completely unused and untestable. Quoting Anthony: "untested code is broken code". This _also_ means that we don't have to preserve a pfn list after the pages are freed, which should let us get rid of some temporary storage (vb->pfns) eventually. Signed-off-by: Dave Hansen <dave at linux.vnet.ibm.com>...

.... Without this we might free a page (and have another user touch it) while the hypervisor is unprepared for it. But, if the bit is _not_ set, we are under no obligation to reverse the order. Furthermore, all modern qemus set this bit. So, the "tell second" code is completely unused and untestable. Quoting Anthony: "untested code is broken code". This _also_ means that we don't have to preserve a pfn list after the pages are freed, which should let us get rid of some temporary storage (vb->pfns) eventually. Signed-off-by: Dave Hansen <dave at linux.vnet.ibm.com>...

On Tue, Sep 10, 2019 at 09:52:10AM +0800, Jason Wang wrote: > > On 2019/9/9 ??10:45, Michael S. Tsirkin wrote: > > On Mon, Sep 09, 2019 at 03:19:55PM +0800, Jason Wang wrote: > > > On 2019/9/8 ??7:05, Michael S. Tsirkin wrote: > > > > iovec addresses coming from vhost are assumed to be > > > > pre-validated, but in fact can be speculated to a value

Hi all, I built my first asterisk using the traditional (?) .conf files and constructs. I recall reading books at the time about AEL but it seemed "new" and untested so I left it alone. Now, I'm interested to poll the audience here to see if I should look into using AEL instead (or in addition to) for future work. TIA

iovec addresses coming from vhost are assumed to be pre-validated, but in fact can be speculated to a value out of range. Userspace address are later validated with array_index_nospec so we can be sure kernel info does not leak through these addresses, but vhost must also not leak userspace info outside the allowed memory table to guests. Following the defence in depth principle, make sure the

iovec addresses coming from vhost are assumed to be pre-validated, but in fact can be speculated to a value out of range. Userspace address are later validated with array_index_nospec so we can be sure kernel info does not leak through these addresses, but vhost must also not leak userspace info outside the allowed memory table to guests. Following the defence in depth principle, make sure the

Random old patch that I had in my queue. Posting it as a backup, it is still untested. Rich.

...t;-2 >> cat.pfoa[pfas.pheno$log2pfoa >=quantile(pfas.pheno$log2pfoa,0.25, na.rm =T) >> &pfas.pheno$log2pfoa <=quantile(pfas.pheno$log2pfoa,0.75, na.rm =T)]<-1 >> } > > This would be somewhat more compact and easier to maintain if you used findInterval (untested in the absence of a data object, which is your responsibility): > > pfas.pheno <-within(pfas.pheno, { > cat.pfoa <- findInterval( log2pfoa , c(-Inf, quantile( log2pfoa,c(.25,.75), Inf), na.rm =T), Inf)]-1 } ) > > > `findInterval` numbers its intervals from 1, so to get...

...ed FAIL 25 ( 22%) tests unexpected PASS After: 112 tests total 110 ( 98%) tests as expected 2 ( 2%) tests unexpected FAIL Regression Test Results Before: 869 tests total 831 ( 96%) tests as expected 5 ( 1%) tests unexpected FAIL 1 ( 0%) tests unexpected UNTESTED 32 ( 4%) tests unexpected PASS After: 869 tests total 866 (100%) tests as expected 2 ( 0%) tests unexpected FAIL 1 ( 0%) tests unexpected UNTESTED Vladimir

On Mon, Sep 09, 2019 at 03:19:55PM +0800, Jason Wang wrote: > > On 2019/9/8 ??7:05, Michael S. Tsirkin wrote: > > iovec addresses coming from vhost are assumed to be > > pre-validated, but in fact can be speculated to a value > > out of range. > > > > Userspace address are later validated with array_index_nospec so we can > > be sure kernel info does not