search for: l171

...in corporate settings. We must not divulge our user IDs in the packages we develop and release. Jim Hester pointed out that these two lines in `add_build_stamp_to_description_file()` <https://github.com/wch/r-source/blob/521c90a175d67475b9f1b43d7ae68bc48062d8e6/src/library/tools/R/build.R#L170-L171> are responsible. Could we consider his suggestion of using an optional environment variable to overwrite the default behavior? user <- Sys.getenv("R_BUILD_USERNAME") if (!nzchar(user)) user <- Sys.info()["user"] if(user == "unknown") user <- Sys.getenv(&q...

...lge our user IDs in the packages we develop and release. > > > Jim Hester pointed out that these two lines in > > `add_build_stamp_to_description_file()` > > < > https://github.com/wch/r-source/blob/521c90a175d67475b9f1b43d7ae68bc48062d8e6/src/library/tools/R/build.R#L170-L171 > > > > are responsible. Could we consider his suggestion of using an optional > > environment variable to overwrite the default behavior? > > > user <- Sys.getenv("R_BUILD_USERNAME") > > if (!nzchar(user)) user <- Sys.info()["user"] > &...

It does give a warning, but then it overwrites the files, anyway. Reproducible example below. This is R 3.4.3, but it does not seem to be fixed in R-devel: https://github.com/wch/r-source/blob/4a9ca3e5ac6b19d7faa7c9290374f7604bf0ef64/src/main/dounzip.c#L171-L174 FYI, G?bor dir.create(tmp <- tempfile()) setwd(tmp) cat("old1\n", file = "file1") cat("old2\n", file = "file2") utils::zip("files.zip", c("file1", "file2")) #> adding: file1 (stored 0%) #> adding: file2 (sto...

...ularly nice form of Python's tuple-unpacking idiom). Am I missing something? cheers Ben https://github.com/r-devel/r-svn/blob/eac72e66a4d2c2aba50867bd80643b978febf5a3/src/library/stats/R/power.R#L38-L52 https://github.com/r-devel/r-svn/blob/master/src/library/stats/R/family.R#L166-L171

The context to this is that nbdkit uses sscanf to parse simple file formats in various places, eg: https://github.com/libguestfs/nbdkit/blob/b23f4f53cf71326f1dba481f64f7f182c20fa3dc/plugins/data/format.c#L171-L172 https://github.com/libguestfs/nbdkit/blob/b23f4f53cf71326f1dba481f64f7f182c20fa3dc/filters/ddrescue/ddrescue.c#L98 We can only do this safely where we can prove that overflow does not matter. In other cases we've had to change sscanf uses to strto* etc which is much more difficult to use...

...gs. We must > not divulge our user IDs in the packages we develop and release. > Jim Hester pointed out that these two lines in > `add_build_stamp_to_description_file()` > <https://github.com/wch/r-source/blob/521c90a175d67475b9f1b43d7ae68bc48062d8e6/src/library/tools/R/build.R#L170-L171> > are responsible. Could we consider his suggestion of using an optional > environment variable to overwrite the default behavior? > user <- Sys.getenv("R_BUILD_USERNAME") > if (!nzchar(user)) user <- Sys.info()["user"] > if(user == "unknown")...

...ackages we develop and release. > > > > > Jim Hester pointed out that these two lines in > > > `add_build_stamp_to_description_file()` > > > < > > https://github.com/wch/r-source/blob/521c90a175d67475b9f1b43d7ae68bc48062d8e6/src/library/tools/R/build.R#L170-L171 > > > > > > are responsible. Could we consider his suggestion of using an optional > > > environment variable to overwrite the default behavior? > > > > > user <- Sys.getenv("R_BUILD_USERNAME") > > > if (!nzchar(user)) user <- Sys.i...

It has long been known that the C specification of *scanf() leaves behavior undefined for things like int i; sscanf("9999999999999999", "%i", &i); C11 7.21.6.2 P12 "Matches an optionally signed integer, whose format is the same as expected for the subject sequence of the strtol function with the value 0 for the base argument." C11 7.21.6.2 P10 "If this

When detecting kernels we have to list the files in the package to find the right /boot/vmlinuz file. In virt-v2v 1.28 we ran: rpm -ql kernel Because multiple kernels can be installed this gave incorrect results, which was reported in RHBZ#1161250 and initially fixed in commit 377bc302f11db3da4263f894c76a7d280fb25dbd. This changed the command to: rpm -ql [epoch:]kernel-version.release

Hi there, Could someone please comment on the following hard-lock (*). Staring at the code, I see `nvkm_rd32` calls are enclosed in a timeout detection, except one. drivers/gpu/drm/nouveau/nvkm/engine/gr/g84.c#L171 ... nvkm_msec(device, 2000, if (!(nvkm_rd32(device, 0x100c80) & 0x00000001)) break; ); ... Would it make sense to also enclose this in the do/while loop ? Full ref: * https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/536 Thanks (*) Oct 20 08:44:13 vostrodell kernel:...

..._opt_set_default_flags https://github.com/freebsd/freebsd/blob/master/lib/libpam/modules/pam_krb5/pam_krb5.c#L242 - Heimdal krb5_get_init_creds_opt_set_default_flags ran the Heimdal version of krb5_appdefault_time: https://github.com/freebsd/freebsd/blob/master/crypto/heimdal/lib/krb5/init_creds.c#L171 - Heimdal function krb5_appdefault_time ran the MIT kerberos version of krb5_appdefault_string: https://github.com/freebsd/freebsd/blob/master/crypto/heimdal/lib/krb5/appdefault.c#L130 This is where the code path cross from using the Heimdal code to the MIT kerberos code, which it should not do....

...t; https://github.com/freebsd/freebsd/blob/master/lib/libpam/modules/pam_krb5/pam_krb5.c#L242 > > - Heimdal krb5_get_init_creds_opt_set_default_flags ran the Heimdal version > of krb5_appdefault_time: > https://github.com/freebsd/freebsd/blob/master/crypto/heimdal/lib/krb5/init_creds.c#L171 > > - Heimdal function krb5_appdefault_time ran the MIT kerberos version of > krb5_appdefault_string: > https://github.com/freebsd/freebsd/blob/master/crypto/heimdal/lib/krb5/appdefault.c#L130 > > This is where the code path cross from using the Heimdal code to the MIT > kerb...