-
Notifications
You must be signed in to change notification settings - Fork 77
Change default port #26
Comments
Can you use the starknet-devnet --port 5001 or starknet-devnet -p 5001 Or is it just a matter of convenience? |
I do use it personally. |
@janek26 I don't understand. Does your program run |
@FabijanC Macos has a system service called ControlCe that uses port 5000 but the devnet doesn't error out properly when it uses that port. I don't know how this works - it looks like it's running fine but only handles a subset of the requests. It would be nice if the default port wasn't one used by Macos and that it would fail gracefully in this condition. For now just moving the port would save a lot of frustration, it took me a while to realise what was going on. |
@JorikSchellekens |
@FabijanC |
I've opened some prs for it which could wait until another breaking change comes along. |
@ccarnino You said you'd like to be pinged on MacOS issues, did you also experience this issue with an occupied port? I'm asking because I'm not sure if all mac users are experiencing this. E.g. the CI/CD pipeline |
I personally have not experienced this problem, unless I was trying to run another devnet in another terminal by mistake. @JorikSchellekens @janek26 what kind of issues or how do you realise that devnet is failing behind the scenes because of this issue? |
@ccarnino this is a monterey specific issue |
None of the tests on https://github.com/Shard-Labs/starknet-hardhat-example would run. The following is the result of running the tests:
Meanwhile the server reports a single successful post:
|
I am on Monterey too. And I have the And no my test don't throw that error. |
Try to use python 3.9. I had problems with 3.7 |
This is the guide I use to startup my dev environment https://github.com/ccarnino/starknet-hardhat-typescript-example |
me and my colleagues at argent had this issue aswell. |
@JorikSchellekens Update us when you can, from what I've seen this should be fairly simple in Python with resources being a part of the standard library. |
Hey guys,
great work! While integrating this with Argent X we notices port 5000 is often already in use and the devnet doesn't check that and starts anyways (but doesn't work)
After a quick google search it seems like port 5000 is often used by the system on MacOS
would it be possible to change the default port to something less used?
Cheers, Janek
The text was updated successfully, but these errors were encountered: