Open Source Heartbeat: Open Source Heartbeat

Open Source Heartbeat

vsoch commented on issue flux-framework/flux-framework.github.io#205.

Thanks for the 3rd comment, Mergify bot. I almost forgot you were there after the first two. You and coffee bot must be good buds. …

View Comment

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

Thanks for these changes! Everything is merged and should be released in VisIt 3.5.1….

View Comment

tpatki commented on issue llnl/variorum#591.

Spent a few hours debugging the segfault with amd_smi APIs. Summary from claude below. …

View Comment

BradWhitlock open issue llnl/axom#1530.

Add function to compute curvature of a NURBSCurve/BezierCurve at a given parametric location

Functions to compute local curvature within a NURBS curve was removed from the C2CReader in #1526 …View Comment

grondo open issue flux-framework/flux-core#7732.

idea: define queue membership by hostlist with implied property == queue name

This is an alternate take on #5741, with the end result being similar for admins configuring queues….View Comment

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

I repushed with the suggested changes, plus addressed some test failures that were a bash (redhat) vs dash (debian) thing….

View Comment

alecbcs commented on issue spack/spack-packages#5620.

Package names appear to always be normalized by PyPi so we just need to match the same case / separator as is used in the actual tarball name for {name} and it’ll work….

View Comment

imguoguo closed issue sipeed/NanoKVM#551.

API endpoints throwing errors when HID-Only mode is enabled

API endpoints “/api/storage/image/mounted” and “/api/storage/cdrom” throw errors when HID-Only mode is enabled…View Comment

camierjs commented on issue mfem/mfem#5387.

Really neat! Thank you @tdrwenski !…

View Comment

jandrej commented on issue mfem/mfem#5387.

> We should mention this new feature in the CHANGELOG. …

View Comment

adrienbernede open issue llnl/radiuss-spack-configs#191.

Consider using /p/vast1 instead of /usr/workspace/${user} for spack install and buildcache storage

/p/vast1 now has daily snapshot….View Comment

cyrush closed issue llnl/conduit#1649.

c++20 fmt runtime param issue with relay silo paths

Another case we need to use conduit_fmt::runtime, it may be that our c++20 testing doesn’t have silo enable?…View Comment

JustinPrivitera commented on issue llnl/conduit#1651.

what is conduit_fmt::runtime and why do we need it?…

View Comment

adayton1 commented on issue llnl/axom#1912.

Instead of removing the cpp14 variant, can’t you just make it conflict with the version that requires c++17 and any version newer than it?…

View Comment

adrienbernede commented on issue llnl/CARE#379.

> > If you can get access to a bank (other than guests) on matrix, the best is to define it as the default one. But otherwise, yes, we can easily set the CI to use it in the alloc options (.gitlab/custom-variables.yml). …

View Comment

chu11 commented on issue flux-framework/rfc#535.

doh! i totally forgot about the rfc. thanks!…

View Comment

tpatki open issue flux-framework/flux-sched#1532.

Support per-xor-slot duration and tasks for XOR jobspecs?

## Problem…View Comment

tpatki open issue flux-framework/flux-multi-cluster-utilities#33.

Add a "optimize-all" policy

Design a policy that optimizes for “predicted shortest makespan” : this will combine the least-pending-jobs and the performance-based policies to demonstrate an overall optimization….View Comment

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

> These are vendors being motivated to be flux developers so I figured that was probably the right location? …

View Comment

cmoussa1 commented on issue flux-framework/flux-accounting#556.

Going to close this for now….

View Comment

cjekel commented on issue cjekel/piecewise_linear_fit_py#134.

@doronbehar should be fixed now…

View Comment

cbritopacheco commented on issue cbritopacheco/rodin#314.

Superseded by #315. This branch still carried the six commits that #312 squash-merged into develop, so it conflicted with develop

jeremylt commented on issue CEED/libCEED#1988.

Yeah, go ahead and remove the one outside of the init function since it isn’t helping us anymore …

View Comment

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

Yes, space is tight for static cuda builds – working on a potential fix. …

View Comment

jeremylt commented on issue 4C-multiphysics/4C#2012.

Fantastic, then the user just needs to get the correct flags sent to Kokkos via building Trilinos correctly. …

View Comment

tgamblin commented on issue spack/governance#6.

@rbberger yes please update Phil to https://sig.com…

View Comment

imguoguo commented on issue sipeed/sipeed_wiki#988.

v-dobrev commented on issue mfem/mfem#5406.

Merged in next for testing……

View Comment

artv3 commented on issue llnl/RAJA#2006.

@llnl/raja-core , is this ready to go? …

View Comment

tomstitt commented on issue llnl/RAJA#2059.

from an app perspective this looks great! thanks @artv3 !…

View Comment

samuelkgutierrez commented on issue hpc/quo-vadis#542.

And I guess qv_process_scope_get could become qv_process_get and qv_mpi_scope_get could become qv_mpi_get? This one isn’t as clear to me, however. Open to suggestions here….

View Comment

eleon commented on issue hpc/quo-vadis#540.

Thanks for asking, @samuelkgutierrez . I prefer CLOSE. Close seems to be a more straightforward concept, while affinity preserving, in my opinion, would require explaining to users (including me) what it means :) …

View Comment

sam-maloney commented on issue flux-framework/flux-core#7488.

To add the only salient info from my duplicate issue, my log was missing the “got SIGTERM” from rank 1 instead of rank 0, so it could be either order….

View Comment

jameshcorbett commented on issue flux-framework/flux-coral2#161.

@behlendorf indicated that this issue and https://github.com/flux-framework/flux-coral2/issues/175 are the highest priority right now….

View Comment

camierjs commented on issue GLVis/data#10.

Is this on top of #9 ? macos-10.15 was not affected then….

View Comment

jandrej commented on issue EnzymeAD/Enzyme#2948.

updated and removed inactivity list file from history…

View Comment

hppritcha commented on issue open-mpi/ompi#14171.

oh ignore my comments about Fortran. I forgot we’d already added a sub implementation that had the fortran interfaces….

View Comment

hppritcha commented on issue open-mpi/mtt#956.

The error that started this problem is likely this based on the error log:…

View Comment

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

It might, I’d have to look at the modprobe settings. That’s my best bet for the issue cause though, if feasibility stayed loaded then the dependent so would too. Also this would always happen on systems with musl, and there’s no way to fix it there (musl doesn’t actually unload shared objects)….

View Comment

sam-maloney commented on issue flux-framework/flux-sched#1529.

It’s not making my life particularly difficult, no, but I did find it a bit needlessly confusing if the listed versions aren’t actually indicating real requirements

jameshcorbett commented on issue flux-framework/flux-sched#1530.

I just ran module remove sched-fluxion-qmanager/resource && flux module reload resource && module load sched-fluxion-resource, I didn’t manually touch feasibility at all. I thought removing resource or sched-fluxion-resource would force feasibility to exit?…

View Comment

sam-maloney commented on issue flux-framework/flux-accounting#885.

Everything seems to be passing well in my latest builds! Many thanks @cmoussa1

tgamblin commented on issue spack/spack#52665.

@haampie ok, caching is disabled for spliced specs, and the traversal logic is simpler. I think this is a decent backport. the diff looks big but some code just moved into a try/finally block. …

View Comment

wihobbs open issue flux-framework/flux-sched#1531.

valgrind test is noisy due to hwloc errors

With some frequency on the ci / jammy - test-install (pull_request) check we’re seeing the following issue, which appears to be from hwloc and goes away. Is this a known issue? Is there something we should be doing to suppress the warning?…View Comment

wihobbs commented on issue flux-framework/rfc#529.

Ok, that seems to have consensus. Can someone push the approve button? Then I’ll go update my PR to Fluxion….

View Comment

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

Thanks for the helpful feedback and improvements @vsoch, @jameshcorbett, and @trws! Setting MWP….

View Comment

sam-maloney commented on issue flux-framework/flux-pmix#131.

As a follow-up (ideally once #132 is also decided) perhaps a v0.7.1 bugfix release could be triggered to make it easy to package this fix? …

View Comment

samuelkgutierrez closed issue hpc/quo-vadis#105.

Test double split operations

Create a program in tests to test the following scenarios. Let’s say we have a dual socket node with 2 GPUs per socket. We also have four MPI tasks. …View Comment

wihobbs commented on issue flux-framework/rfc#529.

Oh, of the options so far I like sched.selection_type the most. @cmoussa1 @garlick your thoughts?…

View Comment

trws commented on issue flux-framework/rfc#529.

I’m leaning toward something like your suggestion @grondo, maybe alloc_type or sched_selection_type? That and make the strings the same here and in the PR and I think we’re probably good….

View Comment

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

I’ll look at #1424, as you point out with this going into the next release it might be good to tackle that as well….

View Comment

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

That’s a fair point. The advantage to having the reserved boolean tracked here is I think I would need to do the same thing to solve #1424, because we need to know that something was reserved (and thus sent a time estimate) to clear those estimates the next time around. I suppose we could separate them and set “reserved” along with the time estimate but not track that it was reserved at the end? …

View Comment

vsoch open issue converged-computing/fleetq#4.

Descriptive Dispatch Experiments Planning

Putting some notes here before I head out:…View Comment

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

Hi @marcdurant. I apologize if you have already done this, but I asked codex to have a look at your crash report and comments here and it had a theory about what might be going wrong:…

View Comment

alecbcs commented on issue spack/spack-packages#4437.

@bernhardkaindl went in and fixed the merge conflicts on the behalf of @dacolombo. …

View Comment

v-dobrev commented on issue spack/spack-packages#143.

Update: I planning to run some tests with GPU builds and also see if more of the conflicts("^mfem build_system=cmake") are really necessary….

View Comment

gardner48 commented on issue llnl/sundials#976.

This will depend on the index size selected at configuration time. By default this is a 64-bit signed integer type e.g., int64_t….

View Comment

JustinPrivitera commented on issue llnl/conduit#1646.

@cyrush can you have a look at this? We discovered that the blueprint transforms can give wrong results if you call them with empty nodes. …

View Comment

adrienbernede commented on issue llnl/Umpire#1076.

Can’t merge it myself……

View Comment

artv3 commented on issue llnl/RAJA#2054.

> > Regarding old implementation of atomicGeneric in CUDA is giving incorrect results is that a CUDA related bug? or why is that happening? …

View Comment

adayton1 commented on issue llnl/CARE#379.

> If you can get access to a bank (other than guests) on matrix, the best is to define it as the default one. But otherwise, yes, we can easily set the CI to use it in the alloc options (.gitlab/custom-variables.yml). …

View Comment

adrienbernede commented on issue llnl/CARE#379.

If you can get access to a bank (other than guests) on matrix, the best is to define it as the default one. …

View Comment

vsoch commented on issue kubeflow/trainer#3712.

Primarily “here is a container or Dockerfile with out app and the command to run it at a small size.” The goal would be to reproduce what you want to do for testing….

View Comment

tgamblin open issue hpsfoundation/tac#88.

[Project Proposal] mars-earth / pymars readiness inquiry

### 1. Name of Project…View Comment

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

> Final review from @trws then merge? …

View Comment

jameshcorbett commented on issue flux-framework/flux-sched#1316.

Final review from @trws then merge?…

View Comment

tpatki commented on issue flux-framework/flux-rest-server#3.

No worries, @garlick. The new PR is up….

View Comment

garlick commented on issue flux-framework/flux-pmix#131.

It was kind of a baddie, and @sam-maloney ‘s excellent issue description made it easy to quickly narrow down. Thanks for the review! I’ll set MWP and ask Sam to confirm the fix when he has a chance….

View Comment

sam-maloney commented on issue flux-framework/flux-pmix#130.

To add a couple of quick tests running flux pmi:…

View Comment

garlick open issue flux-framework/flux-core#7720.

content: flux kvs put --sync can hang under certain error conditions

Problem: as noted in #7702 , the content cache can get stuck flushing out dirty blobs under certain conditions:…View Comment

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

I’ve had this on my “to cleanup” list for a long time, but as @grondo says above, what is the best/easiest solution. Using Claude Opus tried to get a gauge on how disruptive a change would be using a number of the suggested paths above:…

View Comment

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

In a meeting this was actually described as not a real requirement. Rather than try to guess at what solution is really desired here, let’s close this and later open a different issue with clear goals….

View Comment

jeremylt commented on issue CEED/libCEED#1987.

Note - merging main into your branch instead of rebasing means I’d recommend we squash-merge this PR…

View Comment

hppritcha open issue open-mpi/ompi#14145.

ABI: Code Duplication: c_header.py Re-implements Domain Knowledge from ompi_bindings

## Code Duplication: c_header.py Re-implements Domain Knowledge from ompi_bindings…View Comment

BradWhitlock closed issue llnl/axom#1689.

Centralize logic related to units and conversion

We have logic in Klee, in the Quest Open Cascade reader and in the shaping tutorial related to units and conversions between them….View Comment

hppritcha commented on issue hpsfoundation/tac#93.

@jwillenbring …

View Comment

grondo commented on issue flux-framework/rfc#530.

Required by mergify:…

View Comment

jameshcorbett commented on issue flux-framework/flux-multi-cluster-utilities#29.

While working on this, I ran into another issue, which was that I can’t seem to update the jobspec in the jobtap plugin to have attributes.system.exec.test.override=1 . I’ve been working around this by setting that attribute directly on the jobspec at submission time. @grondo suggested making this edit in flux-core to track down the issue:…

View Comment

sam-maloney commented on issue flux-framework/flux-core#7677.

I would immediately think that target should only ever be 0 or 1, as otherwise the request would skip over intermediate instances, which feels like a violation of the hierarchical model. Certainly for a shrink/partial release, those resources would have to be removed from the resource set of each instance in the hierarchy in any case, and then you have the more philosophical question of what gives a lower level application/instance the right to determine what its parent/ancestor instances do with their resources. I suppose a user might reasonably want a way to indicate that an application is releasing resources which are no longer needed by its own local instance for further workflow steps, but that would be different from the target proposed here, as the shrink would still need to be dealt with by the local instance first, it would just be guaranteed to be immediately followed by an equivalent job_manager.dyn_alloc_request from the local instance to its immediate parent. …

View Comment

cmoussa1 commented on issue flux-framework/flux-accounting#896.

Thanks @jameshcorbett! That is a good question you brought up. This segregation between child banks and users is intentional and is not allowed behavior for a hierarchy in flux-accounting. So, no, banks and users cannot exist under the same parent bank, so I think we should be okay here….

View Comment

jeremylt commented on issue 4C-multiphysics/4C#2012.

Ah, this was a missing piece …

View Comment

becker33 open issue spack/spack-tutorial#572.

Add docker to container image

We now use docker in the binary caching section, but we never updated the image to include it….View Comment

imguoguo commented on issue sipeed/picoclaw#2251.

@loafoe Hi! Since there’s been no activity after the earlier reminder, I’m closing this Grafana Alertmanager channel PR for now to keep the queue tidy. The work looked solid, so if you’d like to pick it back up, feel free to reopen anytime and we’ll gladly continue the review….

View Comment

tzanio commented on issue mfem/mfem#5397.

Merged in next for testing……

View Comment

chu11 commented on issue flux-framework/rfc#528.

> One point that might need clarification: can MODEL_VERSION contain whitespace? …

View Comment

wihobbs commented on issue flux-framework/flux-core#7716.

Thanks for calling my attention to annotations, which do seem like the right approach. The RFC doesn’t stipulate what happens to a job’s annotations after the job enters the CLEAN state, unless the job fails (they are discarded). Do they persist in the KVS? Or is the way to reference a past job’s annotations through the eventlog?…

View Comment

sam-maloney commented on issue flux-framework/flux-accounting#885.

@cmoussa1 I haven’t actually run a build since, but once v0.59.0 releases I will rebuild my RPMs and report back here on the outcome!…

View Comment

jedbrown commented on issue rsmpi/rsmpi#224.

Thank you! Sorry about the delay….

View Comment

jedbrown commented on issue openjournals/joss-reviews#9333.

The MPI reference @mpi1994standard does not appear in the bibtex file. You might be intending to cite @mpi50. The Ringler 2013 paper above does have a DOI, but is not cited. If it’s not intended to be cited, then the check above can be considered a false positive….

View Comment

jandrej commented on issue mfem/mfem#5350.

> This is an interesting PR but I think it requires some discussion with the MFEM team at large. One of the basic tenets of the finite element method is that there is one mesh which is subdivided into elements on which we represent our fields. This PR relaxes this requirement for the special case where one mesh is a sub-mesh of another. Another alternative would be to compute bilinear forms on the primary and sub-mesh separately and combine these separate operators into a block system using coupling operators to define the mapping between finite element spaces. …

View Comment

balos1 commented on issue llnl/sundials#966.

@copilot apply the changes in the diff produced by the failing litgen_check…

View Comment

markcmiller86 commented on issue llnl/Silo#535.

Working on it. Just fixing a bug in DBCp() when copying between drivers …

View Comment

cyrush commented on issue visit-dav/visit#21047.

```…

View Comment

cjvogl commented on issue pnnl/SPAECIES#52.

@quantheory I’ve rebased this branch off main that has #49 merged in….

View Comment

v-dobrev commented on issue mfem/mfem#5334.

The diffs in “Files Changed” still show some changes that were already merged in master through PR #5330 – I suspect merging master here will fix that….

View Comment

bgunnar5 commented on issue llnl/mada-tools#13.

Closing this as #15 will include these files….

View Comment

cyrush commented on issue llnl/conduit#1642.

This is not a good change, the ownership semantics have to do with how the schema tree is owned, and a simple swap will not work….

View Comment

tzanio commented on issue mfem/mfem#5393.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch….

View Comment

v-dobrev commented on issue mfem/mfem#5259.

Note: I used a rebase + squash to merge the last two commits into next (ignoring the last merge of master into this branch)….

View Comment

adrienbernede commented on issue llnl/RAJA#2045.

@johnbowen42 OK fixed !…

View Comment