start of work to add spack#275
Conversation
I am debugging a nil pointer reference and have commented out the other modules until then Signed-off-by: vsoch <vsoch@users.noreply.github.com>
|
Hey @nishakm ! Can you please set my expectation for when someone will be able to review this? Is there something else I need to do? Thank you! |
Sorry for the late reply! At this time, we're trying to re-evaluate the parser model. So I can't give feedback for this right now. If you want to contribute any ideas, please join our community meetings on Wednesdays at 11am-12pm PT. |
|
So contributing to this project requires attending an in person meeting? Time is precious these days and that's a high bar. :/ I can engage here and contribute a lot in terms of code, but I think my preference is for asynchronous communication. Imagine how it would be if we had to devote a meeting hour every week to every OSS project we want to contribute to? Not enough hours in the day! So please keep me in the loop. I will not be able to attend the meetings but I'm available on these channels. |
That's not what I meant :). Attending the meetings are always optional, and meeting minutes and decisions are recorded here: https://hackmd.io/EQ0DwvvgRnOl2uzPiTYQcw. The parser model is currently broken and the community (which is just 2 people right now) is currently in discussion on how to address it and move forward. I will definitely keep you in the loop! |
|
Ok sounds good! Thanks. |
Hey @nishakm ! I am working on adding spack, and this is a WIP!
I got pretty far today but hit a nil pointer reference and wanted to ask if you had any insights to this error?
At first glance it looks to be an issue with the checksum String() but I tried changing to use bytes, removing it, and nothing has changed so (before I go out for my run) I thought it might be more useful to open this for discussion and help!
Note that I am debugging the nil pointer reference and have commented out the other modules until then so I can easily run and see the spack error, and I haven't cleaned up the code yet. Also note that we can discuss the design - spack is typically installed to one root so instead of looking for it somehow in the PWD I look for spack on the path, and if it's found, we parse installed packages. Also ignore the
make dockercommand - that was just for my local testing (and I'll be removing it!)This has been super fun to work on today - I hope I can help more after this too!
Signed-off-by: vsoch vsoch@users.noreply.github.com