search for: l129

...I don't understand the benefit of using it here. [1] https://github.com/llvm/llvm-project/blob/47a0e9f49b903aa4ef821d2c7a679a145ee983f9/llvm/include/llvm/ADT/CachedHashString.h#L35-L36 [2] https://github.com/llvm/llvm-project/blob/3f5f8f39734e88c797b003d4a0002b2eaef1ac17/lld/COFF/SymbolTable.h#L129 [3] https://github.com/llvm/llvm-project/blob/3f5f8f39734e88c797b003d4a0002b2eaef1ac17/lld/COFF/SymbolTable.cpp#L458 [4] https://github.com/llvm/llvm-project/blob/3f5f8f39734e88c797b003d4a0002b2eaef1ac17/lld/COFF/SymbolTable.cpp#L727

...ups where the locate tool >> finds upsd.pid, and I don't see it in /run or /var/run where I see >> upsmon.pid. >> > ... it seems that the timers are only stored in memory. See > checktimers(): > https://github.com/networkupstools/nut/blob/master/clients/upssched.c#L129 Hello Charles, thanks for the link. If timers are only stored in memory then the example given at http://networkupstools.org/docs/user-manual.chunked/ar01s07.html chapter 7.2 is wrong. It is not possible to turn off a timer with rm as shown in #! /bin/sh case $1 in...

Hi, I'm trying to get a better understanding of what a timer is, so I added the following line to upssched.conf # Debug - turn on long-running timer to find out where upssched puts it AT ONBATT * START-TIMER where-am-I 1000 I can then start this timer by pulling the power cord from the wall for just a few seconds. I now have 1000 seconds to find the timer. I don't see it in

...nd if it is, where should I find it? Any suggestion would be much appreciated. Thanks, Roger I don't use upssched myself, but from looking at the code, it seems that the timers are only stored in memory. See checktimers(): https://github.com/networkupstools/nut/blob/master/clients/upssched.c#L129 -- Charles Lepple clepple at gmail

...>>> finds upsd.pid, and I don't see it in /run or /var/run where I see >>> upsmon.pid. >>> >>> ... it seems that the timers are only stored in memory. See >> checktimers(): https://github.com/networkupst >> ools/nut/blob/master/clients/upssched.c#L129 >> > > Hello Charles, thanks for the link. If timers are only stored in memory > then the example given at http://networkupstools.org/doc > s/user-manual.chunked/ar01s07.html chapter 7.2 is wrong. It is not > possible to turn off a timer with rm as shown in > >...

...#39;', ''%?'').to_sql }) AND created_at > ?", Date.yesterday).to_sql It will fail, because inner SQL will contain qmark inside of literal, which AR will count as query parameter (https://github.com/rails/rails/blob/master/activerecord/lib/active_record/sanitization.rb#L129), but there is only one argument. However, this will work (because AR skip parameter binding when no arguments are given): User.where("NOT EXISTS (#{ Comment.where(''user_id = users.id AND body ILIKE ?'', ''%?'').to_sql })").to_sql So is it a minor bug...

...bably are not set too often this probably won't affect many people. And a simple workaround exists. So maybe this is a wontfix, but I figured I'd still report it and let you decide. [1]: https://github.com/openssh/openssh-portable/blob/b4ac435b4e67f8eb5932d8f59eb5b3cf7dc38df0/ssh-keyscan.c#L129-L130 [2]: `SSH_SYSFDMAX` is defined as `sysconf(_SC_OPEN_MAX)` -- You are receiving this mail because: You are watching the assignee of the bug.

Can you send me a patch with instructions to reproduce? I can take a look. -- adrian > On Jun 15, 2017, at 2:23 PM, Sergei Larin <slarin at codeaurora.org> wrote: > > Yes, it does for us. My tree is couple days off the tip, and I see it there. > > Sergei > > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Keno Fischer via llvm-dev > Sent: