Displaying 6 results from an estimated 6 matches for "baz1".
Did you mean:
baz
2013 Mar 29
1
Asterisk 11 - Change CDR in hangup exten [Was: CDR values changed in hangup handler not saved]
...erfield)=bar)
same => n, Hangup()
exten => h,1,Verbose(0,Entering context ${CONTEXT} from
${CHANNEL(channeltype)} channel ${CHANNEL} with EXTEN and CID set to
${EXTEN} and ${CALLERID(num)})
same => n,
ExecIf($["x${CHANNEL(channeltype)}"="xLocal"]?Set(CDR(userfield)=baz1:baz2)
My goal is to get either baz1 or baz2 value in
/var/log/asterisk/cdr-csv/Master.csv.
Typing channel originate Local/7005 at from-foobar application Playback
tt-monkeys, I can see that the line with ExecIf is run but CDR still
contains foo value (the one set before Dial).
The strange thing i...
2018 Jan 12
0
best way to represent this pseudocode in LLVM IR?
...roof of concept of something I'm calling "error return
traces" in my frontend (screenshot and explanation at this link):
https://github.com/zig-lang/zig/pull/684
Now I'm trying to minimize the runtime size.
Here's some example IR that I generate:
define internal fastcc i16 @baz1(%StackTrace* nonnull) unnamed_addr #2 !dbg
!69 {
Entry:
%1 = getelementptr inbounds %StackTrace, %StackTrace* %0, i32 0, i32 0,
!dbg !70
%2 = getelementptr inbounds %StackTrace, %StackTrace* %0, i32 0, i32 1,
!dbg !70
%3 = load i64, i64* %1, align 8, !dbg !70
%4 = urem i64 %3, 31, !dbg !70...
2018 Apr 02
5
[Bug 13364] New: rsyncd clips trims relative symlinks outside of source tree
https://bugzilla.samba.org/show_bug.cgi?id=13364
Bug ID: 13364
Summary: rsyncd clips trims relative symlinks outside of source
tree
Product: rsync
Version: 3.1.3
Hardware: x64
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: core
Assignee:
2018 Apr 04
0
[Bug 13364] rsyncd clips trims relative symlinks outside of source tree
...y to silence the warnings out of the -v listing.
Shortening the rsyncd "path=" so that the links become inside the tree could
work but rsync has no usable way to specify only one directory without causing
the links to be considered outside outside the tree.
cd baz2; rsync ./ rsync://.../baz1/ # original case
rsync bar2/ rsync://.../root/bar1/ # shortened path=
Links going to bar1 accessible by /root/ are considered outside of the bar1
tree and clipped.
--
You are receiving this mail because:
You are the QA Contact for the bug.
2005 Jan 26
2
reshape (a better way)
Hi,
I am using the NLSY79 data (longitudinal data from the Bureau of labour
stats in the US). The extractor exctracts this data in a "wide" format and
I need to reshape it into a long format.
What I am doing right now is to do it in chuncks for each and evry
variable that is varying and then I merge the data together. This is
taking a long time. my question is:
How do I specify that
2009 Aug 10
12
v2.0 configuration parsing
I'm trying to figure out how exactly v2.0 should be parsing
configuration files. The most annoying part is if it should always just
"use whatever comes first in config" or try some kind of a "use most
specific rule". The "most specific" kind of makes more sense initially,
but then you start wondering how to handle e.g.:
1) User logs in to imap from 192.168.0.1.