search for: hiroaki

...', mustWork = FALSE) == normalizePath('./a/b', mustWork = FALSE) but it became FALSE at some point in r-devel. I think 'a/b' and './a/b` should be treated as the same path. Does that make sense? Thanks! Regards, Yihui -- https://yihui.org On Thu, Feb 23, 2023 at 11:44 PM Hiroaki Yutani <yutani.ini at gmail.com> wrote: > I confirmed the revert fixed my failing test. Thanks! > > 2023?2?23?(?) 20:12 Hiroaki Yutani <yutani.ini at gmail.com>: > > > Thanks for the prompt response, I'll confirm it after the new R-devel > > binary is availa...

I confirmed the revert fixed my failing test. Thanks! 2023?2?23?(?) 20:12 Hiroaki Yutani <yutani.ini at gmail.com>: > Thanks for the prompt response, I'll confirm it after the new R-devel > binary is available. > Also, thanks for the detailed explanation. I agree with you in general. > > > "/" in "C:/" is a path separator or not,...

...has lagged behind its implementation unfortunately, which may partially my fault for not submitting doc patches for it against the manuals. Sorry for my contribution to that, I'll see if I can loop back around to contributing documentation for ALTREP. Best, ~G On Sun, Apr 21, 2024 at 6:36?PM Hiroaki Yutani <yutani.ini at gmail.com> wrote: > Thanks, Hernando, > > Sorry, "API" is a bit confusing term in this context, but what I want to > discuss is the "API" that Writing R Extension defines as quoted in my > previous email. It's probably different fr...

...that can be called from C code (and some that can be called from Fortran code). Only those documented here are stable enough that they will only be changed with considerable notice. And that's why CRAN does not allow unstable ones = those not documented in R-exts as part of the API. Therefore Hiroaki's question is a very good one. ALTREP is declared as experimental and is not part of the API, but the development and stability of the API in some sense should get better as more packages are using it. Therefore it is currently allowed on CRAN in the hope that it will transition to stable at so...

...> unfortunately, which may partially my fault for not submitting doc > patches for it against the manuals. Sorry for my contribution to that, I'll > see if I can loop back around to contributing documentation for ALTREP. > > Best, > ~G > > On Sun, Apr 21, 2024 at 6:36?PM Hiroaki Yutani <yutani.ini at gmail.com> > wrote: > >> Thanks, Hernando, >> >> Sorry, "API" is a bit confusing term in this context, but what I want to >> discuss is the "API" that Writing R Extension defines as quoted in my >> previous email. I...

...PI > - Without changing how data are accessed > - Compatible with all C code which uses the API > - Compatible with R internals > > > I hope this helps, > Hernando > > > -----Original Message----- > From: R-devel <r-devel-bounces at r-project.org> On Behalf Of Hiroaki Yutani > Sent: Sunday, April 21, 2024 8:48 PM > To: r-devel <r-devel at r-project.org> > Subject: [Rd] Is ALTREP "non-API"? > > Writing R Extension[1] defines "API" as: > > Entry points which are documented in this manual and declared in an > in...

...a breaking change, so I think we can preserve the current (R 4.2.2) behavior. [1]: https://learn.microsoft.com/en-us/dotnet/standard/io/file-path-formats#apply-the-current-directory Best, Yutani 2023?2?23?(?) 17:15 Tomas Kalibera <tomas.kalibera at gmail.com>: > > On 2/23/23 03:27, Hiroaki Yutani wrote: > > Hi, > > > > I found dirname() behaves differently on R-devel on Windows. Since I'm > not > > sure which behavior is right, let me ask here before filing this to R's > > Bigzilla. > > > > On R 4.2.2., we get > > > >...

...tional R C API - Generalizes whats underneath the API - Without changing how data are accessed - Compatible with all C code which uses the API - Compatible with R internals I hope this helps, Hernando -----Original Message----- From: R-devel <r-devel-bounces at r-project.org> On Behalf Of Hiroaki Yutani Sent: Sunday, April 21, 2024 8:48 PM To: r-devel <r-devel at r-project.org> Subject: [Rd] Is ALTREP "non-API"? Writing R Extension[1] defines "API" as: Entry points which are documented in this manual and declared in an installed header file. These can be used...

On 2/23/23 03:27, Hiroaki Yutani wrote: > Hi, > > I found dirname() behaves differently on R-devel on Windows. Since I'm not > sure which behavior is right, let me ask here before filing this to R's > Bigzilla. > > On R 4.2.2., we get > > > dirname("C:/") > [1] &q...

Writing R Extension[1] defines "API" as: Entry points which are documented in this manual and declared in an installed header file. These can be used in distributed packages and will only be changed after deprecation. But, the document (WRE) doesn't have even a single mention of ALTREP, the term "ALTREP" itself or any entry points related to ALTREP. Does this mean,

Hi, I found dirname() behaves differently on R-devel on Windows. Since I'm not sure which behavior is right, let me ask here before filing this to R's Bigzilla. On R 4.2.2., we get > dirname("C:/") [1] "C:/" However, on R-devel (r83888), we get > dirname("C:/") [1] "." ?dirname says 'dirname returns the part of the

...se: Bugs fixed in this release: ----------------------------------- * ASTERISK-25640 - pbx: Deadlock on features reload and state change hint. (Reported by Krzysztof Trempala) * ASTERISK-25364 - [patch]Issue a TCP connection(kernel) and thread of asterisk is not released (Reported by Hiroaki Komatsu) * ASTERISK-25569 - app_meetme: Audio quality issues (Reported by Corey Farrell) * ASTERISK-25609 - [patch]Asterisk may crash when calling ast_channel_get_t38_state(c) (Reported by Filip Jenicek) * ASTERISK-24146 - [patch]No audio on WebRtc caller side when answer waiti...

Hi! I recently tried to mount a filesystem in RAID1 mode using loopback devices. I followed the instructions at [1]. Here''s exactly what I''ve done: $ dd if=/dev/zero of=raid1_0.img bs=1M count=500 $ dd if=/dev/zero of=raid1_1.img bs=1M count=500 $ mkfs.btrfs -m raid1 -d raid1 raid1_0.img raid1_1.img $ losetup /dev/loop0 raid1_0.img $ losetup /dev/loop1 raid1_1.img $ mount -t

...nd caching (Reported by Joshua Colp) * ASTERISK-25615 - res_pjsip: Setting transport async_operations > 1 causes segfault on tls transports (Reported by George Joseph) * ASTERISK-25364 - [patch]Issue a TCP connection(kernel) and thread of asterisk is not released (Reported by Hiroaki Komatsu) * ASTERISK-25619 - res_chan_stats not sending the correct information to StatsD (Reported by Tyler Cambron) * ASTERISK-25569 - app_meetme: Audio quality issues (Reported by Corey Farrell) * ASTERISK-25609 - [patch]Asterisk may crash when calling ast_channel_get_t38_sta...

Hi. While testing subvolumes in btrfs on 2.6.32.9, I hit a kernel BUG: [ 492.164012] kernel BUG at fs/btrfs/inode.c:4365! The commands to reproduce this bug are as follows: # mount -t btrfs /dev/sda5 /scratch # btrfsctl -S subvol /scratch # date > /scratch/date # ln /scratch/date /scratch/subvol/ ln segfaults, and the bug above is found in dmesg. Subsequent accesses to the subvolume

...ead safety (Reported by Joshua Colp) * ASTERISK-25615 - res_pjsip: Setting transport async_operations > 1 causes segfault on tls transports (Reported by George Joseph) * ASTERISK-25364 - [patch]Issue a TCP connection(kernel) and thread of asterisk is not released (Reported by Hiroaki Komatsu) * ASTERISK-25624 - AMI Event OriginateResponse bug (Reported by sungtae kim) * ASTERISK-25619 - res_chan_stats not sending the correct information to StatsD (Reported by Tyler Cambron) * ASTERISK-25569 - app_meetme: Audio quality issues (Reported by Corey Farrell) * A...

...(Reported by George Joseph) * ASTERISK-25442 - using realtime (mysql) queue members are never updated in wait_our_turn function (app_queue.c) (Reported by Carlos Oliva) * ASTERISK-25364 - [patch]Issue a TCP connection(kernel) and thread of asterisk is not released (Reported by Hiroaki Komatsu) * ASTERISK-25569 - app_meetme: Audio quality issues (Reported by Corey Farrell) * ASTERISK-25619 - res_chan_stats not sending the correct information to StatsD (Reported by Tyler Cambron) * ASTERISK-24146 - [patch]No audio on WebRtc caller side when answer waiting time...

...l.com> Hillf Danton <dhillf@gmail.com> Himanshu Madhani <himanshu.madhani@qlogic.com> Hin-Tak Leung <htl10@users.sourceforge.net> Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com> Hiral Patel <hiralpat@cisco.com> Hiro Sugawara <hsugawara@nvidia.com> Hiroaki SHIMODA <shimoda.hiroaki@gmail.com> Hiroo MATSUMOTO <matsumoto.hiroo@jp.fujitsu.com> Hiroshi DOYU <hdoyu@nvidia.com> Hiroshi DOYU <hdoyu@nvidia.com> # (parts) Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com> Hitoshi Mitake <h.mitake@gmail.com> Hitoshi Mi...

...l.com> Hillf Danton <dhillf@gmail.com> Himanshu Madhani <himanshu.madhani@qlogic.com> Hin-Tak Leung <htl10@users.sourceforge.net> Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com> Hiral Patel <hiralpat@cisco.com> Hiro Sugawara <hsugawara@nvidia.com> Hiroaki SHIMODA <shimoda.hiroaki@gmail.com> Hiroo MATSUMOTO <matsumoto.hiroo@jp.fujitsu.com> Hiroshi DOYU <hdoyu@nvidia.com> Hiroshi DOYU <hdoyu@nvidia.com> # (parts) Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com> Hitoshi Mitake <h.mitake@gmail.com> Hitoshi Mi...

...l.com> Hillf Danton <dhillf@gmail.com> Himanshu Madhani <himanshu.madhani@qlogic.com> Hin-Tak Leung <htl10@users.sourceforge.net> Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com> Hiral Patel <hiralpat@cisco.com> Hiro Sugawara <hsugawara@nvidia.com> Hiroaki SHIMODA <shimoda.hiroaki@gmail.com> Hiroo MATSUMOTO <matsumoto.hiroo@jp.fujitsu.com> Hiroshi DOYU <hdoyu@nvidia.com> Hiroshi DOYU <hdoyu@nvidia.com> # (parts) Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com> Hitoshi Mitake <h.mitake@gmail.com> Hitoshi Mi...