achaiah

I see the same problem. Heartbeats stop being published after a reconnect. I have also confirmed that the above solution works but it's definitely a bug in the implementation.

Actually, this only solves the problem if the stomp server does not restart. Upon reboot, even with the 'z-default' name, the server stops receiving heartbeats.

I can't run the frontend either... so much for a full-stack example :( ``` * What went wrong: Execution failed for task ':frontend:npm-preunpack'. > javax/xml/bind/DatatypeConverter * Try: Run with --stacktrace...

Yes, that worked. Thanks. Apparently the frontend cannot be built with jdk9. To build with jdk8 you can specify the following option: `./gradlew -Dorg.gradle.java.home=your-jdk8-home frontend:run`

+1 Thanks for considering supporting Python 3. I'm sure you're aware that the original EOL for python 2 was set to 2015. It has been extended to 2020 but basically...

Yes, it's not totally as trivial as just stuffing everything into nn.DataParallel but it's not terribly difficult either. I've done it in the past in my custom code but would...

@jph00 you may want to examine your code to make sure you're working with the same GPU. The parallelization using nn.DataParallel seems to work for me if I leave out...

I can get around the issue by simply commenting out the lines that store regularization and constraints loss in `batch_logs` but it's obviously not ideal. Not sure what the real...

I added a pull request partially addressing the multi-GPU issues: https://github.com/ncullen93/torchsample/pull/40

It's actually not too hard to write some boilerplate code to get a fine-tuning setup up and running or if you need something more solid you can use one of...