-
Notifications
You must be signed in to change notification settings - Fork 34
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
log each event id we process from onclusive #1864
Merged
petrjasek
merged 2 commits into
superdesk:hotfix/2.6.3
from
petrjasek:fix-onclusive-add-logging
Oct 13, 2023
Merged
log each event id we process from onclusive #1864
petrjasek
merged 2 commits into
superdesk:hotfix/2.6.3
from
petrjasek:fix-onclusive-add-logging
Oct 13, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
so we can check logs in case some event is missing CPCN-380
MarkLark86
approved these changes
Oct 13, 2023
@petrjasek Might need to update the superdesk-core requirement to v2.6.5: https://github.com/petrjasek/superdesk-planning/blob/fix-onclusive-add-logging/server/requirements.txt#L22 (due to PyYAML issues https://github.com/petrjasek/superdesk-planning/blob/fix-onclusive-add-logging/server/requirements.txt#L22) |
MarkLark86
added a commit
that referenced
this pull request
Oct 24, 2023
* [SDAAP-64] Fix null location crash in notifications (#1773) * [SDESK-6873] fix: Backport moment-timezone upgrade * fix(client): Change moment import to moment-timezone * fix lint errors * [SDNTB-804] feature: Add priority to Events, Planning and Coverages (#1772) * ui: PlanningAPI updates * api: Add priority to ContentProfiles * ui: Add priority to ContentProfiles * api/ui: Add priority to search * ui: Default values * ui: fix unit tests * api: Add behave tests for search * fix: Getting profiles by ID not working when using system default profiles * change limit when calling onclusive api (#1783) * change limit when calling onclusive api use 1000 instead of 100 to do less pagination, also fetch some extra items to avoid possible gaps. SDCP-684 * fix date filtering for all day events (#1782) * fix date filtering for all day events when making a query also do a query for all_day events using only date part of the given date, but it must be first converted to local time using client timezone so it will the date user sees in the UI. also tweak the way the all_day events are assigned to dates in the UI based on newsroom code. SDCP-682 * avoid dynamic mapping for event calendars (#1784) SDESK-6876 * [SDNTB-804] fix(ui): Load ContentProfiles using its name not _id (#1785) * fix onclusive ingest (#1786) - keep timestamp for next run based on current start - look for timezone not only using name but also offset - increase buffer when getting updates (not clear if the timestamps should be utc or local, so add some extra time - for events with no end time set it to start time and not some fake end time which might make it go visible on a next day SDCP-688 SDCP-690 * check all timezones when parsing onclusive (#1787) SDCP-688 * fix events not visible in the UI (#1790) mostly related to events with `no_end_time` flag which have same end timestamp as start one. SDCP-680 * there was an error in timezone detection (#1792) when the event started during the hour when there was daylight savings switch for a timezone, so rather work with utc date. SDCP-688 * fix event date not visible in preview (#1791) * fix event date not visible in preview that was the case for events with no end time and same timezone as local one for user. SDCP-690 * add missing end date for multi day events with no end time * Fix : Some events ingested from Onclusive do not contain the complete location info [SDCP-692] (#1794) * fix : Some events ingested from Onclusive do not contain the complete location info [SDCP-692] * update testcases * parse location.location field * fix black * update logic * set language for onclusive events based on product (#1796) SDCP-696 * fix timestamps from onclusive (#1797) those are currently using London timezone, not utc. * use languages with -CA for onclusive events (#1798) so it's consistent with manually created events SDCP-696 * use /date api for initial import from onclusive (#1801) use `/date` api instead of `/between` and log imported events into a text file so we can check that if needed. SDCP-699 * [SDESK-6829] fix(ingest_rule): Skip autopost action if item is already posted (#1802) Multiple posts will still occur if a Calendar or Agenda is to be added in the ingest rule (due to the separation of ingest, and executing routing rules) * fix server requirements (#1804) * fix server requirements * fix e2e core server version * release 2.6.2 * [SDESK-6972] fix(api): Allow Event dates.tz to have a null value (#1816) * fix(api): Allow dates.tz to have a null value * Add tests * Update UIF (#1851) * fix switch label param (#1855) * update server requirements * log each event id we process from onclusive (#1864) so we can check logs in case some event is missing CPCN-380 * fix missed conflict in package.json * fix: add default values to util functions * add missing import * fix merge issues * fix default planning language value * fix(e2e): Select tree popover from body not dom parent * fix(unit tests): Store utcnow before checking versionposted --------- Co-authored-by: Andrew Marwood <[email protected]> Co-authored-by: Petr Jašek <[email protected]> Co-authored-by: devketanpro <[email protected]> Co-authored-by: Konstantin Markov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
so we can check logs in case some event is missing
CPCN-380