Open Source Heartbeat: Open Source Heartbeat

Open Source Heartbeat

vsoch commented on issue flux-framework/flux-python#18.

@trws @grondo @garlick looking for your advice! In testing building for Mac, I found that flux core and flux security need something called pipe2. …

View Comment

trws commented on issue flux-framework/flux-python#17.

It is, we actually use one on flux-core now if you want to snag some configs from over there….

View Comment

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

https://teams.microsoft.com/l/message/19:f2ed7be3682d40d1b8e038744e500a09@thread.skype/1756487055813?tenantId=a722dec9-ae4e-4ae3-9d75-fd66e2680a63&groupId=70162982-9587-4bcc-ad53-20178c76fe11&parentMessageId=1756487055813&teamName=VisIt&channelName=General&createdTime=1756487055813…

View Comment

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

Main issue was confusion about the the scalar range of the tensor plot….

View Comment

cjvogl commented on issue mfem/mfem#5001.

Noting a good idea from @kmittal2 in a Slack conversation: …

View Comment

grondo commented on issue flux-framework/flux-python#17.

And I guess CI will check if the build still works :laughing: …

View Comment

tpatki open issue flux-framework/flux-power-monitor#11.

Support CPU-only and GPU-only builds of Variorum when parsing

Similar to what we did in the LDMS Variorum plugin code, check if power_node_watts exists, and aggregate only GPU/APU data from Variorum based on what is available. …View Comment

chu11 open issue flux-framework/flux-core#7054.

t0100-modprobe.t: hanging

The t0100-modprobe.t test seems to be hanging for me on corona (RHEL8) on this test….View Comment

tpatki commented on issue flux-framework/flux-core#6873.

> Also, I wonder if we can find another way to pass in the instance URI, since embedding it in the dependency URI might cause parsing problem later on (like ambiguity about which scheme an appended ?option=value belongs to)? …

View Comment

imguoguo commented on issue RadxaOS-SDK/rsdk#87.

adrienbernede commented on issue LLNL/radiuss-spack-configs#142.

@rhornung67 I guess you need the branch to live a little longer….

View Comment

CamStan commented on issue LLNL/UnifyFS#821.

> Have you had a chance to figure out why the CI builds are not running? …

View Comment

markcmiller86 closed issue LLNL/Silo#448.

Add DBSetEvalNameschemes()

Add this global/file level property to alter behavior of DBGetMultiXXX object calls. By default, if a multiblock object is nameschemed, callers of DBGetMultiXXX objects will get only the nameschemes and then have to work with those to do further reads….View Comment

adayton1 commented on issue LLNL/CHAI#328.

CHAI is used successfully on Windows, though in a CPU-only configuration. It uses CMake as its build system, which is supported on Windows, so the build process should be very similar. You might have to select a specific generator (e.g. cmake -G “Visual Studio 17 2022” -A x64) to generate a visual studio solution file, for example. Or supposedly, in visual studio there is built in support for CMake projects (see https://learn.microsoft.com/en-us/cpp/build/cmake-projects-in-visual-studio?view=msvc-170). Other generators are listed here if you don’t use visual studio: https://cmake.org/cmake/help/latest/manual/cmake-generators.7.html. …

View Comment

jedbrown commented on issue pyOpenSci/software-peer-review#331.

> We’re not a journal and people aren’t submitting papers but code….

View Comment

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

hmmm not sure what’s going on with NVIDIA openshmem test….

View Comment

cmoussa1 commented on issue flux-framework/flux-core#7047.

Thanks @chu11! Going to set MWP here…

View Comment

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

There was a little “override branch protections” selection that I used without going to settings. Which I needed in the powerman PR because a couple of our CI runners were using obsolete github runners and would never run. …

View Comment

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

Thanks @wihobbs! Setting MWP here…

View Comment

garlick open issue chaos/powerman#214.

github: ubuntu-20.04 runner is deprecated

Problem: CI is broken right now because we’re using ubuntu-20.04 which is now deprecatedView Comment

adayton1 commented on issue LLNL/Umpire#997.

I haven’t seen this before….

View Comment

cyrush open issue Alpine-DAV/ascent#1613.

multi node ascent furnace test

add standard test we can use for strong and weak scaling across platforms….View Comment

tgamblin commented on issue spack/spack#51266.

Should we try to get rid of the local imports after this PR, since they’re basically a sign of where circular imports used to be? I feel like we should use this to think about what the proper layering should be….

View Comment

hppritcha commented on issue mpi-forum/mpi-issues#1004.

Fine with me. In this case I’d like to find an approach which limits API growth. For the ‘c’ interfaces could we use a more generic approach for treating the handle - like with MPI_T_PVAR_HANDLE_ALLOC? Also if there were some way to just say no to f90, then for f08 we could use polymorphism. I haven’t thought much about the copy/delete callbacks though….

View Comment

jandrej commented on issue mfem/mfem#4994.

I skimmed through the changes and felt a little confused. Are you aware of the dFEM interface? See here for an example. dFEM covers a broad spectrum of functionality of automatic differentiation capabilities and I’m not sure why there is effort in recreating this functionality in different parts of MFEM. …

View Comment

wihobbs commented on issue flux-framework/flux-accounting#714.

Thanks @cmoussa1!…

View Comment

tpatki commented on issue Olympus-HPC/Mneme#43.

Closing to create a branch to trigger Gitlab CI….

View Comment

cmelone commented on issue LLNL/hubcast#137.

unlinking this from #121 since we still need to add bot functionality for the gitlab client…

View Comment

JustinPrivitera open issue LLNL/conduit#1464.

silo data is too large

pdb data for testing nameschemes is gigantic. We should find or make a simpler example for testing….View Comment

alecbcs commented on issue spack/spack-tutorial#491.

Looks good to me :)…

View Comment

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

> Can you add more defensive checks, and at least print the exception? In particular GitHub API requests may fail. …

View Comment

samuelkgutierrez open issue hpc/quo-vadis#415.

Add Developer Build Option

View Comment

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

For some reason when I tried again yesterday the checks passed in the TOSS 4 builder, so the package is out there. TOSS 5 still failed though….

View Comment

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

With that, setting MWP….

View Comment

bgunnar5 commented on issue LLNL/merlin#549.

Bypassing the review process here as this is a combination of PRs that have already been reviewed….

View Comment

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

@grondo, is this still something you want to consider? happened to pop up in a search today…

View Comment

benzwick open issue coendevente/SlicerNNInteractive#61.

Add `uv run` usage example to documentation

Currently, the README shows how to install and run the server with:…View Comment

cbritopacheco commented on issue cbritopacheco/rodin#121.

@copilot I have fixed the syntax error and the test. Please finish it. Also most of these are just basic functionality tests which should be categorized as unit tests and moved to tests/unit/ under their respective path and file. So please separate the unit tests from the manufactured tests (which actually are solutions to test against and not class functionality). Also add a few more more manufactured tests….

View Comment

tzanio commented on issue mfem/web#335.

deployed as of 1084806

View Comment

tzanio commented on issue mfem/mfem#4907.

Re-merged in next for testing……

View Comment

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

Just a thought on documentation work that could be relevant to this……

View Comment

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

Merged in next for testing……

View Comment

tzanio commented on issue mfem/mfem#4906.

Re-merged in next for testing……

View Comment

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

:+1: for removal…

View Comment

markcmiller86 commented on issue LLNL/Silo#453.

In 33e4935ff83aec904541d3d56281bfa7cde13721, I added tests that emulate the issue reported by Lila. …

View Comment

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

@haampie if you can follow up in another PR with those pkg name modifications I’m happy to review :)…

View Comment

tgamblin closed issue spack/spack#4062.

Spack Clone to `/` (Docker)

I was wondering, while provisioning a docker image, if spack bootstrap / is actually something being considered as good practice / possible workflow. I could imagine so. …View Comment

balos1 commented on issue spack/spack#51281.

CC @steven-roberts…

View Comment

jedbrown commented on issue rust-lang/rfcs#3847.

Similar proposal: https://github.com/rust-lang/compiler-team/issues/907 …

View Comment

vsoch commented on issue pydicom/deid#286.

I think this would be a fantastic development for the project. We can introduce changes (that are breaking) as long as it is clear / versioned with an appropriate bump. I can give feedback and review at each step - let me know on issues / PRs when the time comes….

View Comment

jeremylt commented on issue openjournals/joss-reviews#8388.

@editorialbot generate pdf…

View Comment

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

flux-cancel(1) is a reference to the manual page in section 1, a common practice in documentation and error messages to refer the user to the correct documentation. (i.e. man 1 flux-cancel). Perhaps in this case it would be clearer if the message was?…

View Comment

chu11 open issue flux-framework/flux-core#7028.

eventlogger: set reactor when creating future

while playing around with an old branch trying to fix #6910 had a test fail with this unexpected exception from job-execView Comment

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

@chu11 or @grondo can you check that I did the completions right? I’ve never messed with them before, and are unfamiliar with how they work….

View Comment

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

Want to check if it is in the bash completions as well?…

View Comment

markcmiller86 commented on issue betterscientificsoftware/bssw.io#2251.

Ok, sorry for bad link in previous comment. Go here, https://github.com/markcmiller86/markdown-collab/blob/main/ExperiencesIntegratingMOABAndVisIt.md….

View Comment

balos1 commented on issue LLNL/sundials#752.

Thanks for sharing your workaround @mottelet. …

View Comment

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

braid case might be a subtle color difference (not that that helps too much with the underlying mystery) …

View Comment

tgamblin commented on issue hpsfoundation/tac#35.

> If the “Align with the mission of the HPSF” requirement is enough to prompt others to scrutinize the dependency licenses, then I’m happy to close this pull request without merging. …

View Comment

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

The same test fails in the TOSS4 build farm, although the failure was in test case #3 rather than #4. I didn’t see a segfault message, but it’s possible I just missed it….

View Comment

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

@mergifyio requeue…

View Comment

garlick commented on issue flux-framework/flux-coral2#397.

Thanks! MPW now….

View Comment

wihobbs commented on issue flux-framework/flux-coral2#402.

It’s helpful to remember, if the node can be returned to service immediately, to raise a fatal exception on the job but exit 0 in the prolog (this is useful, for instance, if a user requests more storage than we cap them at):…

View Comment

chu11 commented on issue chu11/freeipmi-mirror#76.

ipmitool’s output can be different as it intereprets data differently. some ideas…

View Comment

gardner48 commented on issue LLNL/sundials#728.

> @gardner48 Looks like the extended precision test for cvsRoberts_FSA_dns_constraints_-sensi_stg1_t.c is failing because a line number is in the output file (due to an error message, see sundials-codes/answers#60) , and the line number changed. We should probably just disable that test with extended precision since it fails. …

View Comment

adayton1 commented on issue LLNL/camp#184.

> D’oh! Yes, good catch. Thank you. …

View Comment

artv3 commented on issue LLNL/RAJA#1866.

@LLNL/raja-core , what do you guys think of updating the CHANGELOG within each PR? I think it may help us keep track of new features as they come in – instead of when we are making the release candidate. …

View Comment

jeremylt commented on issue CEED/libCEED#1891.

oh, our vector access protected us accidentally here…

View Comment

becker33 commented on issue spack/spack#51140.

It’s not done as a post-concretization step, the specs from the dev specs are imposed in the solver itself. Then there’s also a post-concretization step that ensures the dev_path variant is present, but it doesn’t worry about the rest of the spec….

View Comment

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

Thanks for checking this stuff out in its early state @dalcinl. some of the above functions have been implemented but are sitting in various states in PRs. some of these should be defined - like MPI_Wtick and the aint related functions so i’ll see what’s going on. As for the fromint/toint that seems like an excellent project for a AI LLM. I’ll see what can be done there. …

View Comment

grondo commented on issue flux-framework/flux-coral2#383.

No objection here. …

View Comment

jameshcorbett commented on issue flux-framework/flux-accounting#735.

go off king …

View Comment

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

I was able to reproduce this in my docker container following your set of instructions above. After the first job, subsequently submitted jobs get rejected with a Queue not valid for user error message. For flux-accounting, this seems to be a particular issue when default queues are configured, e.g….

View Comment

bgunnar5 closed issue LLNL/merlin#533.

Ability to Filter Database Queries

Since the new merlin query-workers command will now communicate with Merlin’s database, we need a way for this command to query the database with filters. We should add filter support for both merlin database get all-* and merlin database delete all-* commands. See #524….View Comment

dylan-copeland commented on issue LLNL/libROM#316.

@dreamer2368 An example using this PR is in file src/rom_handler.cpp of https://github.com/LLNL/scaleupROM/pull/60 …

View Comment

cyrush commented on issue spack/spack-packages#1218.

@adamjstewart It looks like it it is trying to build with a newer umpire than ascent 0.8.0 supports. …

View Comment

cmoussa1 commented on issue flux-framework/flux-coral2#394.

Yes I can. Here goes nothing!…

View Comment

cyrush commented on issue LLNL/conduit#1459.

@abhishek1297 glad you were able to work it out, we can add that method to the C-API. Thanks for the feedback!…

View Comment

emily-howell commented on issue Alpine-DAV/ascent#431.

@cyrush Also, you mentioned wanting to compile with 64bit IDs and then use caliper to observe any performance changes. Is there a specific analysis you were hoping to see? I was just doing some runs of different areas of the test suite with caliper reports to see any notable changes….

View Comment

becker33 commented on issue spack/spack-packages#1254.

@hfp this might be of interest to you….

View Comment

dylan-copeland commented on issue mfem/mfem#3807.

> @dylan-copeland did you make the changes you planned here (after mfem/data#12 was merged)? …

View Comment

cbritopacheco commented on issue cbritopacheco/rodin#119.

Merging even though not finished….

View Comment

tzanio commented on issue mfem/mfem#4980.

Merged in next for testing……

View Comment

vsoch commented on issue google/dranet#151.

Thank you @keithmattix much appreciated. Enjoy the holiday!…

View Comment

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

@tepperly, the PR will be merged by the editor (@pazner in this case, as seen in the table added to the first post) when there are at least 2 approvals from people in the Reviewers team and after some additional testing (run nightly) in the next branch. The procedure is documented in CONTRIBUTING.md: https://github.com/mfem/mfem/blob/master/CONTRIBUTING.md#pull-requests – we try to follow it closely but it’s not set in stone. …

View Comment

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

I added testing and removed the WIP. I am not hard over on merging this as is, but wanted the option to be available….

View Comment

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

> I wonder though if we could just create bad treeobjs directly instead of laboriously modifying good ones? Could even have some prepared JSON in test data files. Just a thought. This is fine for now. …

View Comment

markcmiller86 commented on issue betterscientificsoftware/bssw.io#2251.

> Agreed! Are you back from your break, @markcmiller86 ? …

View Comment

tgamblin commented on issue spack/spack#51246.

This is very nice for #51137, where we start showing conditional deps in spack info. …

View Comment

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

This one is mostly good too but currently has no testing….

View Comment

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

Yes, sorry. I dropped the ball on this one. Rebased and will hit the button….

View Comment

grondo commented on issue flux-framework/flux-python#16.

Oh, I see you answered in the email thread. Thanks!…

View Comment

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

This does seem more user-friendly!…

View Comment

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

Thanks @jameshcorbett! Setting MWP here…

View Comment

cmelone commented on issue cmelone/hubcast-test#3.

@lc-hubcast restart failed jobs…

View Comment

becker33 commented on issue spack/spack#51190.

Looks like the tests need to be updated for the changed method name, but otherwise LGTM…

View Comment

jeremylt commented on issue openjournals/joss-reviews#8388.

Ratel just will error if misconfigured. That’s to hard baked into the PETSc error and options handling….

View Comment

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

Yeah, the options are extensible, akin to a programming language, and -help is used to show everything that can be specified in the current expansion. You can’t get to the entire expansion without running. It would be possible (at substantial cross-cutting effort and maintainability impact) to make a system that shows the useful options in a simulation, but even that would be unable to deal with solution-dependent logic (e.g., solve an auxiliary problem, enter an optimization loop, and/or write output only if the solution satisfies a numeric criteria). The decision to make -help comprehensive and extensible was made (by the PETSc team) long ago and responsive to community needs. We could bikeshed over a different name, but this is widely used and accepted in the PETSc community and we consider it a feature that Ratel be readily usable by people familiar with configuring PETSc solvers via run-time options (which you can liken to a domain-specific programming language)….

View Comment

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

jenkins ci runs make distcheck…

View Comment

samuelkgutierrez open issue hpc/quo-vadis#411.

qv_scope_create() is broken with QV_SCOPE_FLAG_NO_SMT

I’m looking into a solution. I’ve found the problem, but a potential solution may involve maintaining multiple topologies. That is, if we detect the use of QV_SCOPE_FLAG_NO_SMT, we can restrict the topology, but then we can’t use that one for other scopes without the SMT flag….View Comment