Back to changelog

vAMSYS 5.2.1

We are pleased to share the latest updates featuring several improvements and fixes within the vAMSYS ecosystem.

What a busy day! 24 code pushes today to production to solve some of the issues discovered on 5.2 launch. Code changes are very disruptive - for the ~5 minutes it takes for them to go live the CPU use explodes, vAMSYS.io gets unhappy and will sometimes throw errors or timeouts, our Pegasus servers will also be upset and take just a bit longer to store those position reports. All in all, our fast pace with pushing out fixes contributed a little to the overall headache experienced by our servers. Moving on - unless it’s an emergency - we will do a much better job in batching the updates so it’s a bit easier for everyone.

Overall, it went way better than expected without too many dramas or offline period.

PIREP Processing Issues

One thing which we could not really test in 5.2 Beta is how the newly created PIREPs are handled - this caused empty landing rates and autoreject issues. Behind the scenes it was caused by:

  • Unusual timestamp formatting coming from users - hh.mm.ss instead of the usual hh:mm:ss

  • PIREPs getting processed faster than the Position Reports get updated. One of the new features in 5.2 is touchdown evaluation - for that to work, we need the position reports stored and assigned to the PIREP. The way we scheduled the tasks meant PIREP processing started before position reports got assigned to PIREP.

Pegasus Server high load

Pegasus servers experienced a surge in CPU use which caused some issues with logging in and getting Airport and Stand data.

We’ve moved some of the tasks outside of our 3 servers responsible for Pegasus and this has stabilized the situation. We will be exploring in days and weeks to come to further optimize this.

Other Fixes:

  • Pegasus had issues looking up SimBrief Alias (we no longer store aliases as of 5.2) via SimBrief API

  • Error in our ‘Error 500’ error page, where it would not produce error ID to share

  • Restored erroneusly deleted loadfactor calculator from Orwell

  • Fixed Navigraph User account linking - it was refering to beta when it no longer exists

  • Re-enabled Discord account linking - forgot to do so prior to 5.2 launch

  • Fixed recurrent activity job - it was looking at the old Events

  • Fixed VA Staff seeing Pilot Registration Review page in Orwell when they were not supposed to

  • Fixed an error which would occur when logging out whilst in Orwell

  • Fixed route importer wrongly lowercasing route tags

  • Lots and Lots n+1 query and lazy loading improvements and fixes

  • Fixed Ruiting edit in Orwell where it would try to null out wrong column

  • Fixed View Booking page for users with SimBrief dispatches from 5.0

  • Fixed SimBrief Airline - ICAO setting in SimBrief Integration in Orwell was not being applied

  • Fixed an issue with creating a Fleet in Orwell

  • Fixed an issue with editing Activity in Orwell when it is Route based

  • Fixed an issue of not being able to select activity when creating a Badge rewarding activity participation

  • Fixed internal remarks not being applied on Route on creation or edit

  • Fixed containers assigned to route not displaying correctly in Orwell

Things to Look Forward to

There are still some gremlins lurking - we will keep resolving bugs as they crop up. Keep making reports in Featurebase so we can fix them!

Once the initial bug squashing is complete, we have a list of highly requested Improvements to add - we will be dedicating some time for that before moving on to 5.3.

Don't miss the next one

Subscribe and we'll email you when we ship.

Unsubscribe anytime.