discourse/spec/fixtures
Alan Guo Xiang Tan d9a7779811
DEV: Fix flaky core backend spec (#22650)
Why this change?

The user id in a fixture file was hardcoded to 666. Once we've
fabricated enough user objects until the sequence for `User#id` reaches
666, the specs in vanilla_body_parser_spec.rb will fail.

What is the fix here?

This commit increases the user id to a large integer which we will
likely never hit in the next 10-20 years.
2023-07-18 07:01:19 +08:00
..
backups FIX: Backups should use relative paths for local uploads 2020-08-21 15:22:28 +02:00
csv FEATURE: Add support for case-sensitive Watched Words (#17445) 2022-08-02 10:06:03 +02:00
db DEV: Allow DROP NOT NULL in pre-deploy migrations (#20775) 2023-03-22 14:43:32 +00:00
emails FIX: improve mailman email parsing (#21627) 2023-05-19 10:33:48 +02:00
encodings
feed FIX: Select best link from Atom feed (#15663) 2022-01-21 17:54:18 +02:00
i18n FIX: Missing translation when translation override contained a %{key} (#16625) 2022-05-04 17:35:22 +02:00
images DEV: Fix png optimization test flakyness (#19535) 2022-12-20 16:05:14 -03:00
json DEV: Fix flaky core backend spec (#22650) 2023-07-18 07:01:19 +08:00
md A11Y: Set role=presentation if alt attr is missing (#18546) 2022-10-12 14:07:37 +03:00
media
mmdb
multisite
onebox FEATURE: Basic support for threads.net onebox (#22471) 2023-07-06 16:02:49 -03:00
pdf
plugins FEATURE: Serve RTL versions of admin and plugins CSS bundles for RTL locales (#21876) 2023-06-01 05:27:11 +03:00
scss
site_settings
theme_settings FIX: Use the default value correctly for theme settings of type uploads (#20541) 2023-03-06 11:41:47 +03:00
themes
woff2