Issue Comment Events

Projects RADIUSS Home

JustinPrivitera commented on issue visit-dav/visit#20216.

Yes, the date in the modification comment doesn’t matter too much. It’s just to get a sense of around when the changes were made. …

View Comment

heidrifx commented on issue visit-dav/visit#20216.

I just pushed another commit which resolves the remark and adds modification comments as well as changes the release notes. …

View Comment

kwryankrattiger commented on issue spack/spack#48815.

Verified locally that py-ruff@0.9: is bootstrapped when a newer python is available….

View Comment

yahooguntu commented on issue spack/spack#45102.

I think this is caused by a too-new texinfo. When I try and install GCC 11 on Ubuntu 22.04.5 I get a similar error:…

View Comment

alecbcs commented on issue spack/spack#48507.

@MatthewLieber thanks for the quick turn around! This PR looks good to me and I’ve asked @nhanford to quick take a look since he’s more familiar with how we package mvapich….

View Comment

afzpatel commented on issue spack/spack#47273.

@tldahlgren could you please review this pr?…

View Comment

eugeneswalker commented on issue spack/spack#48868.

> I cannot reproduce, tried it twice using that lock file….

View Comment

spackbot-app[bot] commented on issue spack/spack#48876.

View Comment

PhilipFackler commented on issue spack/spack#48876.

@spackbot re-run pipeline…

View Comment

victorapm commented on issue hypre-space/hypre#1226.

Hi Junchao,…

View Comment

trws commented on issue flux-framework/flux-sched#1322.

Just glanced again, and the generic predicates rather than the explicit pair look better to me. 👍 on the fixups …

View Comment

milroy commented on issue flux-framework/flux-sched#1322.

Thanks for the feedback @trws! I’ll implement it shortly. …

View Comment

codecov[bot] commented on issue flux-framework/flux-sched#1268.

## Codecov Report…

View Comment

wihobbs commented on issue flux-framework/flux-sched#1268.

Thanks @trws!…

View Comment

kkier commented on issue flux-framework/flux-core#6586.

Just confirming - this is a priority for me (and the people I report to on both sides of the aisle, as it were), but if it ends up in an off-cycle release that I have to manually distribute, that’s a thing I can deal with. …

View Comment

garlick commented on issue flux-framework/flux-core#6586.

I think this is a priority for @kkier but there is little advantage in putting this in as is - in fact it may cause problems. Let’s try to deliver a good first step in the next release….

View Comment

grondo commented on issue flux-framework/flux-core#6586.

I’m not sure there’s a rush to add this as experimental because I’m not sure there’s an immediate use case without the Python consumer class (unless I’m forgetting something!)…

View Comment

codecov[bot] commented on issue flux-framework/flux-core#6603.

## Codecov Report…

View Comment

trws commented on issue flux-framework/flux-core#6597.

That all sounds right to me, maybe throw up an issue so we don’t lose track of it referencing the docs and test suite?…

View Comment

kab163 commented on issue LLNL/Umpire#931.

See generated updated docs: https://umpire.readthedocs.io/en/bugfix-kab163-fix-mpi-leak/sphinx/cookbook/shared_memory.html…

View Comment

cyrush commented on issue Alpine-DAV/ascent#1454.

also working on #1438…

View Comment

Arpan3323 commented on issue visit-dav/visit#20218.

Thank you for your prompt and thorough investigation. I appreciate the VisIt development team’s efforts in maintaining and continuously improving the tool. …

View Comment

tzanio commented on issue mfem/mfem#4682.

We want this PR to go in before any other PRs in master (as of commit https://github.com/mfem/mfem/commit/c9db272586e87b66bd2d780ab0b7c32fa1c1d60d). …

View Comment

pazner commented on issue mfem/mfem#4646.

Good points @YohannDudouit. I did a quick test on Lassen, adding timing for the assembly: …

View Comment

cyrush commented on issue LLNL/conduit#1361.

the reason:…

View Comment

rhornung67 commented on issue LLNL/axom#1188.

Cannot reproduce…

View Comment

markcmiller86 commented on issue visit-dav/visit#20217.

Whoops. This is a duplicate….

View Comment

nychiang commented on issue LLNL/hiop#706.

> > @pelesh Have you ever seen this kind of error? Does ReSolve require some specific cusolver packages? …

View Comment

pelesh commented on issue LLNL/hiop#706.

> @pelesh Have you ever seen this kind of error? Does ReSolve require some specific cusolver packages? …

View Comment

chapman39 commented on issue LLNL/hatchet#155.

Closing, having been told from the Thicket team that Hatchet should not be used on lassen….

View Comment

Staudey commented on issue LLNL/zfp#227.

I see, that all makes sense. I’m going to take another stab at this tomorrow (or the day after tomorrow, depending on how much time I can find)…

View Comment

lindstro commented on issue LLNL/zfp#227.

@Staudey Thank you so much for these latest updates. Before I merge, I have two comments: …

View Comment

liyangrock commented on issue GEOS-DEV/LvArray#342.

> I’m not familiar with Kokkos. but no there really isn’t any unordered map or set in LvArray. If this data doesn’t need to go on the GPU then just use the standard libraries implementation….

View Comment

corbett5 commented on issue GEOS-DEV/LvArray#342.

I’m not familiar with Kokkos. but no there really isn’t any unordered map or set in LvArray. If this data doesn’t need to go on the GPU then just use the standard libraries implementation,…

View Comment

mplegendre commented on issue hpc/Spindle#59.

JSC = Juelich Supercomputing Center. They submitted the #52 PR….

View Comment

mattaezell commented on issue hpc/Spindle#59.

Thanks for the quick response! I’m not familiar with JSC. We are building the spank plugin but haven’t enabled/tested it yet. Are there known issues? I saw #52 but don’t fully understand the impact yet….

View Comment

kminemur commented on issue LLNL/zfp#244.

@lindstro …

View Comment

jessdagostini commented on issue LLNL/Caliper#629.

No worries! I was just wondering if we could try to look over it again since it will be nice to collect some data from my application using Caliper :smile: …

View Comment

ilumsden commented on issue LLNL/Caliper#629.

@jessdagostini I’ve done a bit more work on this. I can get the current version to run on LLNL’s Ruby system using PAPI 6.0.0.1. The values I’m getting are not correct right now, but I may not be running long enough to get valid data from PAPI. I’ll need to look into that before I can determine if the invalid values are due to the runtime being too short or due to bad logic….

View Comment