Beta Test / Technical

[RonSouthworth]

Originally Posted by rgleason

Canne and I have been working on CI: Appveyor/Travis process to automatically build windows, mac and linux and push to new Github Release. We have used help and files from Sean and Nereus32.

CI: Push 'build' to Git Release
(This document is a WIP.)

The work being done on automation is fantastic guys.

With the automation in place it will alleviate a lot of distraction for all the developers and team, and especially for you Rick !


What are you going to do with the free time I wonder

[rgleason]

The opencpn.org server and consequently the OpenCPN Manual are having problems. I hope Bdbcat can get her going again. Jon Gough and I have noticed this over the last 24-48 hours.

[rgleason]

Originally Posted by RonSouthworth

The work being done on automation is fantastic guys.

With the automation in place it will alleviate a lot of distraction for all the developers and team, and especially for you Rick !
What are you going to do with the free time I wonder

Ron, I am just a humble 'packager' for Windows really. It is the programmers we depend upon the most, ...and I am hoping that Leamas and Pavel's Package Manager will someday help us all complete this task more easily.
However for a temporary good solution, Petri's guidance was essential, and Jon Gough has managed to make almost all the necessary 'packages' after a big effort. Check out his most recent ODraw version 1.6.4 'Release' Directory for packages pushed from Appveyor and Travis.I need to tackle the Travis certificate and push next as Petri [Canne] has shown is possible in his Dashboard-Tactics plugin. Then finish configuring a plugin for Leamas.Free time? --Sail! and stop working on the boat a little. Hope you are feeling better!

[Douwe Fokkema]

The released version of radar_pi has an issue with the official OpenCPN 5.0.0 release. The problem occurs on Mac with Mojave 10.14.4. The radar windows (PPI windows) don't function, they are frozen, not refreshed.

When I compile O 5.0.0 on the Mac myself, all is fine. I assume that the travis build for Mac is not fully compatible with Mojave. This seems to be addressed in the recent commits on master: Switch macOS travis build to Mojave + Xcode 10.2.
It would be nice if this version could be tagged as pre-release and made available to Mojave users.


Douwe Fokkema

[nohal]

Originally Posted by Douwe Fokkema

The released version of radar_pi has an issue with the official OpenCPN 5.0.0 release. The problem occurs on Mac with Mojave 10.14.4. The radar windows (PPI windows) don't function, they are frozen, not refreshed.

When I compile O 5.0.0 on the Mac myself, all is fine. I assume that the travis build for Mac is not fully compatible with Mojave. This seems to be addressed in the recent commits on master: Switch macOS travis build to Mojave + Xcode 10.2.
It would be nice if this version could be tagged as pre-release and made available to Mojave users.


Douwe Fokkema

Douwe...

Not all is gold that shines... We can't simply use these CI builds without fixing at least these two:
- The macOS bug with GL canvases introduced by the latest Mojave update (a trivial patch to wxWidgets has to be included)
- DMG lost the decorations and icon placement since the switch to Mojave builder on travis. I so far have no explanation for why the script is not working correctly there as it does with "identical" configuration locally.

Pavel

[rgleason]

From discussion on the Tactics thread, by Canne and Stevead. Out of curiosity:
Saw this comment by Steven "do splines in real time ...." followed by suggestions for timestamps. For more detail please read Canne and Stevead posts above and below this.

How hard would it be to make O's version of nmea0183 able to make timestamps visible and invisible with some kind of a trigger?

1. The default would be invisible to maintain compatibility.

How hard would it be to make O's version of nmea0183 able to insert timestamps at various points?

1. When received.
2. Other times to be determined.

What source for the timestamp?

1. GPS?
2. Computer?

So now the real question, What are "splines"?

[rgleason]

I will no longer be able to provide support to users because I cannot access the manual due to DNS issues or IP blocking at the opencpn.org nameservers.

[fgd3]

Any idea how long you will be unable to access the manual? I seem to be able to reach it with no difficulty.


Fabbian

[rgleason]

Originally Posted by fgd3

Any idea how long you will be unable to access the manual? I seem to be able to reach it with no difficulty. Fabbian

No idea, Fabbian, it's been almost a month now. IP's are not resolving properly to the nameservers, from 5 computers and 2 cell phones. Bdbcat has been very helpful and sent an email that really clarified the problem.

Using website traceroute opencpn.org and [192.138.189.133] resolve to the nameservers, but from my laptop and other machines, it does not seem to resolve properly to [192.138.189.133].

What magic would cause this? I am starting to think that I need to talk with the isp.

[rgleason]

Oh Joy, Bdbcat advised that it is fixed. I can now access opencpn.org. Thank you Dave!

[Moo]

Originally Posted by rgleason

No idea, Fabbian, it's been almost a month now. IP's are not resolving properly to the nameservers, from 5 computers and 2 cell phones. Bdbcat has been very helpful and sent an email that really clarified the problem.

Using website traceroute opencpn.org and [192.138.189.133] resolve to the nameservers, but from my laptop and other machines, it does not seem to resolve properly to [192.138.189.133].

What magic would cause this? I am starting to think that I need to talk with the isp.

Dunno what the problem was Rick but that address doesn't look like a public IP address so not surprised that you can't reach it directly, there is some kind of port forwarding going on I guess.

[CarCode]

Originally Posted by Moo

Dunno what the problem was Rick but that address doesn't look like a public IP address so not surprised that you can't reach it directly, there is some kind of port forwarding going on I guess.

This is the traceroute result from here (Greece) to opencpn.org:


traceroute to opencpn.org (192.138.189.133), 64 hops max, 72 byte packets
1 192.168.10.20 (192.168.10.20) 4.904 ms 1.268 ms 1.161 ms
2 192.168.1.254 (192.168.1.254) 3.365 ms 4.978 ms 3.378 ms
3 62.169.255.246 (62.169.255.246) 12.868 ms 7.753 ms 8.365 ms
4 62.169.247.245 (62.169.247.245) 10.533 ms 13.863 ms 10.290 ms
5 62.169.247.237 (62.169.247.237) 56.724 ms 16.679 ms 17.043 ms
6 * 62.169.252.230 (62.169.252.230) 34.089 ms 16.104 ms
7 tengig-0-1-0-6.br02.ath01.pccwbtn.net (63.218.173.153) 17.583 ms 16.462 ms 21.624 ms
8 63-218-232-41.static.pccwglobal.net (63.218.232.41) 65.236 ms 69.797 ms 71.316 ms
9 63-218-233-38.static.pccwglobal.net (63.218.233.38) 70.695 ms 65.278 ms 66.188 ms
10 ae-0-11.bar1.raleigh1.level3.net (4.69.137.177) 164.362 ms 163.148 ms 166.277 ms
11 * * *
12 * * *
13 110.3.225.104.ptr.anycast.net (104.225.3.110) 183.399 ms 165.013 ms 166.844 ms
14 webaccountserver-rev-dns (192.138.189.133) 158.471 ms 167.823 ms 159.412 ms

[CarinaPDX]

Originally Posted by Moo

Dunno what the problem was Rick but that address doesn't look like a public IP address so not surprised that you can't reach it directly, there is some kind of port forwarding going on I guess.

That is a public address. The private block you are thinking of is 192.168.xxx.xxx, not 192.138.xxx.xxx or 192.xxx.xxx.xxx It took me awhile before that got ingrained...


Greg

[rgleason]

Moo, At first I thought the same thing. Yes CarinaPDX 192.168 is private.
Carcode, thanks for the tracert (windows), yours lands in the same place as mine now, I believe:
14 webaccountserver-rev-dns (192.138.189.133) 158.471 ms 167.823 ms 159.412 ms
and that is correct. And it is still working this morning!
I believe, it was caused by some glitch in the website, and suddenly I could no longer access the site. My IP was blocked. First time this ever happened. Bdbcat fixed it with the provider (Our router IP was blacklisted).

[rgleason]

Dave, Pavel Shouldn't the plugin preferences page show the Version major.minor.patch so users beta testers, troubleshooters and programmers can know what is being used?