Issue Comment Events

Projects RADIUSS Home

cpraveen commented on issue spack/spack#40232.

I face the same issue. There are too many other packages that break. And Apple wont allow me to install clang14 on sonoma….

View Comment

sethrj commented on issue spack/spack#40226.

@keltonhalbert I think your solution is on the right track. First, it looks like spack doesn’t even have a libcanberra package, which is a problem if Vim requires it. We need to make that dependency clear in the recipe (and for what versions), then mark that it’s only needed when the gui is enabled. …

View Comment

hainest commented on issue spack/spack#40221.

This is an issue with all versions of boost before 1.81.0 (https://github.com/boostorg/config/pull/440) that are using libc++. If we’re going to patch it, let’s do so when any build uses @:1.81.0+clanglibcpp. …

View Comment

Sinan81 commented on issue spack/spack#39908.

All build issues are fixed. the above PR will be merged soon….

View Comment

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

I’ve started that pipeline for you!…

View Comment

scheibelp commented on issue spack/spack#40061.

@spackbot run pipeline…

View Comment

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

## Codecov Report…

View Comment

vsoch commented on issue flux-framework/flux-sched#1080.

boorah!! Thanks everyone!!…

View Comment

grondo commented on issue flux-framework/flux-sched#1080.

Yes! This is approved so that should work…

View Comment

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

You should be able to do an interactive rebase one commit back which will show all the changed files. You can add everything but the CMakeLists.txt and GolangSimple.cmake as one commit with the same message as the current final commit, and then add the cmake-related files as a separate commit. …

View Comment

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

## Codecov Report…

View Comment

psakievich commented on issue spack/spack#39556.

okay that looks like @13.2.0 is the release where the requirement ends then @jrood-nrel …

View Comment

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

Yeah, I plan to put up a PR for that, with the caveat that I want to see at least one successful release before we actually remove autotools. Until we’ve seen it go through buildbot without issues using the cmake process I want us to have the option for anything we deploy as part of the rpms….

View Comment

chu11 commented on issue flux-framework/flux-core#5467.

per offline discussion, re-worked this PR. …

View Comment

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

> should we do this in job-info.lookup and leave job-info.update-watch to be just for update watching? …

View Comment

lindstro commented on issue LLNL/zfp#188.

@GarrettDMorrison Can you please handle this PR?…

View Comment

cyrush commented on issue LLNL/axom#1192.

since this could be an issue in multiple places, should we move to use axom-wide execution polices? …

View Comment

william-silversmith commented on issue LLNL/zfp#201.

It’s really just a matter of bumping the version and releasing new wheels, incl. the ones I posted above….

View Comment

tasansal commented on issue LLNL/zfp#201.

@lindstro @william-silversmith, can we please fix this one way or another? I am unsure what exactly needs to be done if you all tell me I can make a PR! Or is it just a matter of making new wheels?…

View Comment

koning commented on issue LLNL/merlin#442.

I tried this PR, looks good….

View Comment

szaman19 commented on issue LLNL/lbann#2329.

Fix for some errors appearing in #2328 …

View Comment

cameronrutherford commented on issue LLNL/hiop#662.

Again this might technically be an ExaGO issue, but trying to figure out who’s to blame here…

View Comment

nychiang commented on issue LLNL/hiop#662.

@cnpetra @cameronrutherford …

View Comment

slabasan commented on issue LLNL/hatchet#93.

Closing this in favor of #107 …

View Comment

drreynolds commented on issue LLNL/sundials#345.

> > how much testing with various RK table options did you do before settling on these specific default tables? …

View Comment

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

thanks for the update!…

View Comment

aslangil commented on issue LLNL/SAMRAI#215.

When I use a single node (less processor) or use multi node but just 2 AMR levels instead of 3 (kind of larger domain), it dissappears. So my experience is also leading to the similar conclusion with you….

View Comment

hughcars commented on issue GLVis/glvis#106.

Just wanted to say this would be extremely helpful for debugging feature additions in mfem. Even more useful if it would be able to handle NC dofs….

View Comment

agcapps commented on issue LLNL/axom#1156.

In the end, the fix was analogous to the one that @bmhan12 linked. The Hexahedron class has an array of eight Point<T, NDIMS>. The change was from this: …

View Comment

rhornung67 commented on issue LLNL/RAJA#1506.

@MrBurmark are you OK with merging this? @gberg617 will add user docs in a subsequent PR….

View Comment

R0n12 commented on issue LLNL/zfp#144.

@lindstro Thank you for the instructions on running ZFP with AMD support! We have collected some throughput numbers on mi100s and a100s with different thread block size. …

View Comment

cyrush commented on issue LLNL/RAJA#1545.

CMAKE_CUDA_FLAGS should get the flags there. …

View Comment

adayton1 commented on issue LLNL/CHAI#235.

@davidbeckingsale, can you take a review pass and merge if you think this is ready?…

View Comment

rhornung67 commented on issue LLNL/SAMRAI#232.

Correct. The template syntax should not be on the declaration of a destructor in a class template. However, if you provide an implementation in the class header (outside of the class definition), the template syntax is required so the compiler knows which type the destructor is being implemented for….

View Comment

PhilipDeegan commented on issue LLNL/SAMRAI#232.

I was only getting this error with GCC, CLANG doesn’t seem to mind with C++20 …

View Comment

pkoosha commented on issue LLNL/zfp#144.

@lindstro thanks for these numbers, they look promising, could you please let me know which branch contains these and how can I ensure I have the best set of practices when running on AMD GPUs? Thank you very much!…

View Comment

tzanio commented on issue GLVis/glvis#260.

@ddkn, were you able to resolve this?…

View Comment

adam-sim-dev commented on issue LLNL/Caliper#493.

View Comment

v-dobrev commented on issue GLVis/glvis#263.

GLVis uses SDL2, so the question of adding support for space mouse is if SDL2 detects the device and then what type of SDL_* events it generates, so we can process them in various places, e.g. here: https://github.com/GLVis/glvis/blob/c2e621cb042cc0950fc4bc1472a1410bfcbe36bf/lib/sdl.cpp#L362 here: https://github.com/GLVis/glvis/blob/c2e621cb042cc0950fc4bc1472a1410bfcbe36bf/lib/sdl_main.cpp#L188 and probably other places. …

View Comment