-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix metar response: Invalid field name(s) found: raw_text #79
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for the quick fix!
I would not consider this as fix without having more info... That parameter was used to limit returned data. Now it returns more data, that wont be used... |
@muktupavels has a good point. Regardless of the amount of data, I would estimate that |
The current server of AWC is TDS 1.3 (January 2010), which uses metar1_2.xsd. It should be available at the following URLs:
The 1st server doesn't accept
I have no objection to change the URI base of the request keeping the fields constraint to get only that element:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, this works as well
Big thank you for fast reaction to @rbuj |
The AWC SOAP WS is back with the same conditions in both URIs, ie no changes need to be made in the request. |
Apparently it's still necessary for getting the weather info from METAR database |
@rbuj |
I still think that moving to If we want to be more paranoid, we can do both and change to |
What is really bad - this fix is needed for all Ubuntu versions. What should we do if they change the URL again? |
Wrong, it is really bad that all Distros need this! |
I tried to write an e-mail to NOAA and AviationWeather about reverting their API changes. Will inform you on any reply. |
Thank you. |
Got answer from NOAA, they are currently running on their backup system. |
I'm the lead web developer at the Aviation Weather Center. I'm trying to get a handle on the change that cause the weather download to fail. I've noticed that our backup ADDS Dataserver is having troubles with the field specifier. I'm looking into that problem. It appears from the URLs listed above that datasever1_3 works but dataserver_current doesn't. That's good information. |
I'm not sure why the dataserver_current and dataserver1_3 are working differently. They're symlinks to the same Tomcat .war file. But they are different. I did notice that the war file on that server is older than we're using on the production server. But while it's operational, I can't change it to test this theory. The dataserver_current is the preferred link but we keep dataserver1_3 and dataserver1_3_0 active. The latter two work fine on the backup server. We will be on the backup server until probably next Monday or Tuesday. The server work at the Weather Service web farm will be going through this Friday. We might switch back on Friday but it's looking more like Monday. Here are direct links: We are in the process of upgrading our servers from Redhat 6 to 7. The new RH7 servers are: |
What's holding up merging this change in? There are two items "Pending" but if you look at the Details, they're green. |
@satoshi - the pipeline has nothing to do with it. If you read the thread, you will notice that there's still an issue in the API that we use to fetch weather data, and they are performing work on their servers that will extend possibly until Monday/Tuesday. |
@vkareh I read the thread and understand that the server work is still ongoing; however I thought this change would address the issue regardless.
I don't know what you're talking about. You said yourself "I still think that moving to dataserver1_3 might be a good idea" which this change would do. |
Nope, fixing all distros is a bad idea! If you can't wait a few day, you need to patch your installation for yourself. |
Tried it but it didn't work for me either. Guess because my libmateweather.so.1.6.9 has a different sha-256sum?
|
If you do Does |
We're in a transition period. This is probably a stop gap solution. It took
me a while to find this email list. So I'll use it in the future to give
you heads up on changes we make with the dataserver code.
Dan.
Web Developer
Aviation Weather Center NWS
…On Wed, Oct 18, 2023 at 4:56 AM Mike Ovchinnkov ***@***.***> wrote:
I confirm that method provided by @devietor <https://github.com/devietor>
is working. Tested on Linux Mint 21.2 Victoria x64, MATE 1.26.0
I've made a patch
<https://github.com/mate-desktop/libmateweather/files/13003210/patch.zip>
which can be applied to libmateweather.so.1.6.9 with SHA-256 sum
d3f66b2ff019991eaffe1c8d5ed984173971030f5fb6b0dd506216f105ea7690.
Download patch, unpack and execute bspatch
/usr/lib/x86_64-linux-gnu/libmateweather.so.1.6.9 ~/libmateweather.so.1.6.9
libmateweather.so.1.6.9.patch, then replace the library with file from
your home directory to sudo mv -f ~/libmateweather.so.1.6.9
/usr/lib/x86_64-linux-gnu/
—
Reply to this email directly, view it on GitHub
<#79 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFZNPHZWLSQZSVS72MO47Y3X76RT5AVCNFSM4NN43HIKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZWHAYDSOBSGM3A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks for the answer @pepa65 . It does not. I have the new server: I have tried reinstalling with 'sudo apt-get install --reinstall libmateweather1' but it didn't work either Here are the websites from 'strings libmateweather.so.1.6.9' :
|
You may try to use HEX editor such as |
But What does |
It should read https://www.aviationweather.gov/cgi-bin/data/dataserver.php I was able to fix the problem on my Ubuntu 22.04, libmateweather1:amd64 1.26.0-1 doing:
|
Why not recompiling your libmateweather package with given commits in our git? |
@N0rbert |
Thanks @raveit65. |
@devietor, please if possible provide server-side solution with redirect or
maybe symlink in server filesystem.
It is impossible to patch all mateweather packages on all distros for all
users.
|
So it would be another reason for making that URL a configurable parameter. |
It says
|
@colibris79 If you can confirm that your newly installed
It will replace the wrong URL with the right one. Edit: This will indeed work. The original lib file with your wrong URL has the exact sha256 sum that you reported. |
I have a tiny patchscript at https://good4.eu/plw that should be safe to use (it only replaces a non-functional URL -if it exists- with a functional one -- if the binary For quick application: (But you'll probably want to check out the 2-line code first!) |
Thank you so much! I can always reinstall or make a backup of the file. |
If you use the |
Reinstalled (again) and patched it with the 'sed' command and now is working again. I have no clue why first two times it didn't. Will keep your patchscript just in case. Thanks again |
My weather applet stopped working again, 2 or 3 days ago. Has the URL changed once again? |
Mine is working fine. |
Did you hotpatch the binary? If so, possibly your system had an upgrade/reinstall of the library, overriding your changes |
If your package manager is APT you can check the last installed packages with |
Thanks, it works in manjaro and archlinux as well ! |
No, there were no updates to libmateweather on my Ubuntu 22.04, still version 1.26.0-1. Just in case, I have reinstalled the package and hotpatched again. No success. |
Even with |
Old URI
https://aviationweather.gov/adds/dataserver_current/httpparam?dataSource=metars&requestType=retrieve&format=xml&hoursBeforeNow=3&mostRecent=true&stationString=LEDA&fields=raw_text
New URI
https://aviationweather.gov/adds/dataserver1_3/httpparam?dataSource=metars&requestType=retrieve&format=xml&hoursBeforeNow=3&mostRecent=true&stationString=LEDA&fields=raw_text
Test: Update weather info on mateweather-applet
msg->response_body->data
contains raw_text element nowCloses #80