The karma-spec-reporter npm package is a Karma plugin which tells Karma to
print the name of each spec (e.g. test case). This is extremely useful
as a maintainer to be able to visually inspect the CI logs and confirm
that we are actually running JS tests and not just giving
false-positives.
We are stuck on an ancient Karma version (0.13.22, lastest is 6.x),
which seems to be incompatible with the latest karma-spec-reporter version
(0.0.36). Since upgrading karma-spec-reporter, spec name printing has
failed with:
02 12 2024 20:59:28.164:WARN [plugin]: Error during loading "karma-spec-reporter" plugin:
Cannot read properties of undefined (reading 'LOG_PRIORITIES')
Downgrading to karma-spec-reporter@0.0.20 eliminates this error and
restoring spec name printing to our JS CI logs.
The Studio Maintenance app had two features:
* "Force Course Publish", which literally doesn't do anything. All it
does is tell you what version *would* be seen by users *if* the course
were to be published--no publishing actually occurs via this feature.
* "Announcements", which writes to the announcements_announcement
database table, but doesn't actually display anywhere.
Having these pages in the platform is actively misleading and creates a
maintenance burden for edx-platform developers, so we remove them.
Note that this commit does not include a migration for the announcements
Django app. So, announcements_announcement table will not be deleted.
Given the small expected size of any past-authored announcements, we are
not worried about leaving them in the database perpetually.
Unclear if there was a change in the focal repositories
or if there was an issue with something else. The noble
repositories don't support 7.0, so we're stuck here
until we upgrade to 8.0.
Operators Note: In newer versions of ubuntu the MD4 hashing algorithm
is disabled by default. To enable it the openssl config needs to be
updated in a manner similar to what's being done here. Alternatively,
you can set the `FEATURES['ENABLE_BLAKE2B_HASHING']` setting to `True`
which will switch to a newer hashing algorithm where MD4 was previously
used.
Because this hashing is being used as a part of the edx-platform caching
mechanism, this will effectively clear the cache for the items that use
this hash. The will impact any items where the cache key might have been
too big to store in memcache so it's hard to predict exactly which items
will be impacted.
BREAKING CHANGE: See the operator note above for more details as this
may break for users transitioning from Ubuntu 20.04 to newer versions.
This is no longer installed by default on ubuntu and so we have to
either manually install it or just run the relevant commands in the
container here it's already available. This lets us do some of the test
setup in a more robust way.
This code does not have any dependencies that are specific to any specific
version of ubuntu. So instead of testing on a specific version and then needing
to do work to keep the versions up-to-date, we switch to the ubuntu-latest
target which should be sufficient for testing purposes.
This work is being done as a part of https://github.com/openedx/platform-roadmap/issues/377
closes https://github.com/openedx/edx-platform/issues/35314
The .github/workflows/add-remove-label-on-comment.yml workflow is missing or needs an update to stay in
sync with the current standard for this workflow as defined in the
`.github` repo of the `openedx` GitHub org.
We haven't quite dropped Py3.8 support yet, so we can't use these workflows if
they're compiling with 3.11:
* upgrade-one-python-dependency (upgrading a single, targeted dep)
* compile-python-requirements (recompiling all deps without upgrading)
So, we "downgrade" those workflows to use 3.8, for now. We should revert this
commit when we drop 3.8 support.
Note: The upgrade-python-requirements.yml workflow is still using 3.8, so this
commit will update the other workflows to match that one.
* feat: temporarily prevent renovate from updating this package
Minor (and therefore presumed-safe by renovate) version updates caused
an exception on some deprecated code. Marking this package as not-safe
for renovate until that code is removed, which will happen quite soon.
see external (2U) ticket REV-4067 for details. cc @julianajlk
FIXES: APER-3502
* feat: adding a comment
attempting to add a comment explaining the ignored dependency
Co-authored-by: Kyle McCormick <kyle@axim.org>
---------
Co-authored-by: Kyle McCormick <kyle@axim.org>
When a shard of unit-tests.yml fails, we want the `success` job to be
maked "Failed" (not "Skipped"). That's because "Failed" blocks the PR
from merging, whereas "Skipped" does not. This change ensures that
`success` always runs to completion rather than being cancelled as soon
as a unit test shard fails or is cancelled.
From https://github.com/marketplace/actions/alls-green#options:
> Important: For this to work properly, it is a must to have the job always run,
> otherwise GitHub will make it skipped when any of the dependencies fail. In
> some contexts, skipped is interpreted as success which may lead to undersired,
> unobvious and even dangerous (as in security breach "dangerous") side-effects.
Closes https://github.com/openedx/edx-platform/issues/34789
Update the renovate config in edx-platform to match the standard config
in most of our other frontend repos, with the exception of 1 settings:
Given the size of edx-platform I want to limit the number of concurrent
renovate PRs to a very small number so that we don't overwhelm our CI
resources. If we find that it would be useful to get more PRs at a
time, we can change this setting in the future.
We've also removed the `rebaseStalePRs` settings since that would be
extra costly on edx-platform for now.
