Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2023-08-29

Channels

#calva
<
2023-08-29
>
punit-naik07:08:43

I am not able to connect to an external nrepl port using calva. When I try to do it, it connects to some random port. Any ideas?

pez07:08:01

Not really… Can you describe the steps you take to reproduce this?

punit-naik07:08:32

1. Click on the REPL icon in the bottom bar 2. Select the option Connect to a running REPL, not in your project 3. Select Generic At this point it should have given me an option of passing a port, but it connects directly to some random port.

pez07:08:43

Could it be that it still finds an nrepl port file in the workspace root and connects to that?

punit-naik07:08:07

I have not started any other repl.

pez07:08:28

There can still be an nrepl port file there. 😃

punit-naik07:08:28

Oh okay, my bad. I cleared that file and now I can connect, thanks!

pez07:08:41

You are welcome! Please file an issue about this. I don’t think we should be using that port file when you connecting to an external repl.

punit-naik07:08:59

okay sure

🙏 2
punit-naik07:08:21

Is there any documentation as to how to file a new issue?

pez07:08:52

No, we don’t have any rules or procedures around that. Just click the New Issue button at Github and type. Including the steps to reproduce is always helpful.

✔️ 2
pez07:08:16

There are mainly two categories of audiences of an issue: 1. Anyone who wants to help to fix it 2. Calva users that want to know what the issue is about The two audiences basically need the same things: • A clear title framing the issue • A description adding context and detailing it a bit • Steps to reproduce (this is a great way to add context and detail) When writing the issue it is probably best to read it from the perspective of someone who wants to help with fixing it. Having said all that, we in the Calva Team will ask for information we are lacking. It is more important that the issue gets filed than that is in any way perfectly authored. 😃 This is why we don’t have a template or procedures. We want the friction of helping us documenting issues to be as small as it possibly can be.

✔️ 4
💯 6
Dustin Getz10:08:03

stu halloway has a great gist about how to write a good issue that i can never seem to find when i need it

👀 2
pez07:08:16

There are mainly two categories of audiences of an issue: 1. Anyone who wants to help to fix it 2. Calva users that want to know what the issue is about The two audiences basically need the same things: • A clear title framing the issue • A description adding context and detailing it a bit • Steps to reproduce (this is a great way to add context and detail) When writing the issue it is probably best to read it from the perspective of someone who wants to help with fixing it. Having said all that, we in the Calva Team will ask for information we are lacking. It is more important that the issue gets filed than that is in any way perfectly authored. 😃 This is why we don’t have a template or procedures. We want the friction of helping us documenting issues to be as small as it possibly can be.

✔️ 4
💯 6
pez15:08:11

Dear Calva friends: Here’s a dev build of a version of Calva that will print server process output to the REPL window. • https://output.circle-artifacts.com/output/job/c39cb214-96f5-4b91-9857-44921b945139/artifacts/0/tmp/artifacts/calva-2.0.388-2300-subscribe-stdout-47382319.vsix It will be optional and default to enabled, following CIDER’s lead. • Here’s the issue it fixes: https://github.com/BetterThanTomorrow/calva/issues/2300 • Docs: https://deploy-preview-2302--calva-docs.netlify.app/output/#repl-process-output-stdout-and-stderr Thanks in advance for help testing this! 🙏 ❤️ calva Thanks to @dustingetz, and @dpsutton and others for help in reproducing and fixing.

👏 4