packages icon indicating copy to clipboard operation
packages copied to clipboard

There was no response when building

Open x751685875 opened this issue 4 years ago • 9 comments

Hello developer, when everything is set up, you click build, but there has been no response, and there has been no response for a long time Mac version: 11.1 Mac configuration: MacBook Pro (15-inch, 2018) / 2.2 GHz 6 Intel Core i7 / 16 GB 2400 MHz DDR4 / Radeon Pro 555X 4 GB image

x751685875 avatar Jan 29 '21 13:01 x751685875

I'm really worried, but I'm not sure what caused no response. Today, I re installed the MAC system. After the re installation, I conducted a test and succeeded. However, when I built it again, it still had no response, And then there was no success. @packagesdev

x751685875 avatar Jan 29 '21 13:01 x751685875

Do note that the response may be delayed, they're not the most active on github

TheTechRobo avatar Jan 29 '21 13:01 TheTechRobo

I'm really worried, but I'm not sure what caused no response. Today, I re installed the MAC system. After the re installation, I conducted a test and succeeded. However, when I built it again, it still had no response, And then there was no success. @packagesdev

I also have this problem. Have you solved it?

kingfulee avatar Feb 20 '21 08:02 kingfulee

This looks like an issue whose origin is difficult to track. This might be related to the launchd daemon having been disabled for instance.

For the record, contacting me via [email protected] is better if you're reporting an issue that blocks you because I don't check the github issues page on a regular basis.

packagesdev avatar Mar 06 '21 09:03 packagesdev

Offtopic but:

For the record, contacting me via [email protected] is better if you're reporting an issue that blocks you because I don't check the github issues page on a regular basis.

You could set up github notifications to be sent to that address. :thinking:

TheTechRobo avatar Mar 06 '21 14:03 TheTechRobo

I will look into this notification thing.

Regarding the issue, it's quite possible that the launchd plist for Packages has been disabled.

Running the following command in Terminal.app may solve the issue:

/usr/bin/sudo /bin/launchctl load -w /Library/LaunchDaemons/fr.whitebox.packages.build.dispatcher.plist

packagesdev avatar Mar 07 '21 17:03 packagesdev

I will look into this notification thing.

Regarding the issue, it's quite possible that the launchd plist for Packages has been disabled.

Running the following command in Terminal.app may solve the issue:

/usr/bin/sudo /bin/launchctl load -w /Library/LaunchDaemons/fr.whitebox.packages.build.dispatcher.plist

I also have this problem. I tried this method, but it didn't work

Jinyueyue7 avatar Mar 25 '21 03:03 Jinyueyue7

I will look into this notification thing. Regarding the issue, it's quite possible that the launchd plist for Packages has been disabled. Running the following command in Terminal.app may solve the issue: /usr/bin/sudo /bin/launchctl load -w /Library/LaunchDaemons/fr.whitebox.packages.build.dispatcher.plist

I also have this problem. I tried this method, but it didn't work

I successfully solved the problem. I restarted the computer and rerun the command: sudo launchctl load -w /Library/LaunchDaemons/fr.whitebox.packages.build.dispatcher.plist

Jinyueyue7 avatar Mar 26 '21 07:03 Jinyueyue7

Perfect solution to my problem.

Netskao avatar Apr 14 '21 07:04 Netskao