fix: make sure visits
include "recent" and "ever" keys for db init 🔥
#4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I tried to deploy to AFRO staging and I got a
KeyError
saying that thevisits
object had norecent
key.I do not understand this plugin well enough to know why this scenario would occur; however, as I needed to deploy I have introduced this 🔥 hot fix 🔥
Important: this may not be the correct fix so I have assigned @ntwalibas so that he can properly investigate this
relates fjelltopp/ckanext-who-afro#89
relates fjelltopp/who-afro-ckan#
Dependency Changes
See who-afro-ckan and specifically fjelltopp/who-afro-ckan#
Testing
Local dev environment and staging deployed through Azure Pipelines now work.
Checklist