I feel like it's 10.15 where Apple really started doubling down on their
"notarization" service? I haven't updated anything to it because it breaks (by
design) a number of things I regularly use, so it would be hard to say, but
that has to be frustrating for developers who can't be constantly on
On Thursday, April 9, 2020 at 1:01:31 PM UTC+2, Tanmay Das wrote:
>
> Running the executable: `./helloworld`
>
Maybe there's a log entry for your program specifically in Console (the GUI
collecting macOS logs), or in one of the system logs.
If this is somehow related to GateKeeper, you could tr
Unable to reproduce the issue on MacOS Mojave 10.14.6, though I tried with
gusto.
On Thu, Apr 9, 2020 at 4:32 AM Tanmay Das wrote:
> Thanks, everyone for your valuable comments. I think Brain is right. It
> might be an OS-related issue. I really like how active this group is. I
> look forward to
Thanks, everyone for your valuable comments. I think Brain is right. It
might be an OS-related issue. I really like how active this group is. I
look forward to coming back with more topics in the future. Stay Home. Stay
Safe.
On Wednesday, April 8, 2020 at 10:17:36 PM UTC+6, Tanmay Das wrote:
>
>
> Therefore, I think it must be some issue with macOS being told to run an
> executable it hasn't seen before, making a network connection.
>
You are probably right.
> If you run it once successfully, and then remove the network connection,
> does it run again OK?
It does.
On Thursday, Ap
On Thursday, 9 April 2020 12:01:31 UTC+1, Tanmay Das wrote:
>
> Running the executable: `./helloworld`
>
>
OK, then clearly it's not an issue with finding our downloading
dependencies: these will all have been resolved by the time the binary has
been compiled and linked.
Therefore, I think it mu
Running the executable: `./helloworld`
Also note that, before building the executable, I tried running with `go
run`, which of course, failed. I can't even say "Failed" because the go
compiler was not throwing any error like *Hey, since I need to download
some dependencies even though your prog
On Thursday, 9 April 2020 06:15:22 UTC+1, Tanmay Das wrote:
> I also forgot to mention one thing. I was able to build the program using
> go build. Even the executable was there. It just didn't run until I
> connected to internet.
>
>
When you say "it just didn't run", do you mean with "go run .
Hmm, it makes sense. Still, there should be some caching mechanism. If the
internet connection can't be established, load the dep from the cache.
On Thursday, April 9, 2020 at 1:14:33 PM UTC+6, Volker Dobler wrote:
>
> On Wednesday, 8 April 2020 18:17:36 UTC+2, Tanmay Das wrote:
>>
>> Is this beh
On Wednesday, 8 April 2020 18:17:36 UTC+2, Tanmay Das wrote:
>
> Is this behavior expected? If it is, why did the go authors make such a
> decision? I mean making the internet connectivity a dependency for the
> execution of a program sounds counter-productive to me, honestly. :(
>
Well, go run
No. OS X 10.15.3
On Thursday, April 9, 2020 at 11:40:51 AM UTC+6, Tamás Gulácsi wrote:
>
> Is it in Windows? Any antivirus may be involved?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails
Is it in Windows? Any antivirus may be involved?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion
I also forgot to mention one thing. I was able to build the program using
go build. Even the executable was there. It just didn't run until I
connected to internet.
On Wednesday, April 8, 2020 at 10:17:36 PM UTC+6, Tanmay Das wrote:
>
> Hey Gophers,
> My very first post here.
>
> Today I faced a
13 matches
Mail list logo
