From: Ammar Faizi <[email protected]>
To: Muhammad Rizki <[email protected]>
Cc: Alviro Iskandar Setiawan <[email protected]>,
Irvan Malik Azantha <[email protected]>,
Memet Zx <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Subject: Re: [PATCH v1 0/1] Fix getFixedRandomColor() function
Date: Wed, 27 Sep 2023 18:31:33 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 9/27/23 6:09 PM, Muhammad Rizki wrote:
> This series contains fixes:
> - Fix getFixedRandomColor() to fix logic Tailwind class name selection.
>
> Please give it a test, thanks!
I did:
- git apply your patch
- npm run build
- Clear browser cache
- Look at https://www.gnuweeb.org/
It still shows white font color. Looking at the console, it throws these errors:
lockdown-run.js:17 Lockdown failed: TypeError: At intrinsics.Object.groupBy expected boolean not function
at isAllowedPropertyValue (lockdown-install.js:1:53384)
at isAllowedProperty (lockdown-install.js:1:53807)
at visitProperties (lockdown-install.js:1:55095)
at isAllowedPropertyValue (lockdown-install.js:1:53041)
at isAllowedProperty (lockdown-install.js:1:53807)
at visitProperties (lockdown-install.js:1:55095)
at lockdown-install.js:1:55523
at repairIntrinsics (lockdown-install.js:1:144597)
at lockdown-install.js:1:145462
at lockdown-run.js:4:3
(anonymous) @ lockdown-run.js:17
lockdown-more.js:99 Protecting intrinsics failed: ReferenceError: harden is not defined
at lockdown-more.js:69:13
at Set.forEach (<anonymous>)
at protectIntrinsics (lockdown-more.js:44:22)
at lockdown-more.js:97:5
(anonymous) @ lockdown-more.js:99
--
Ammar Faizi
next prev parent reply other threads:[~2023-09-27 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 11:09 [PATCH v1 0/1] Fix getFixedRandomColor() function Muhammad Rizki
2023-09-27 11:09 ` [PATCH v1 1/1] fix(page): fix " Muhammad Rizki
2023-09-27 11:31 ` Ammar Faizi [this message]
2023-09-27 12:28 ` [PATCH v1 0/1] Fix " Muhammad Rizki
2023-09-27 12:34 ` Ammar Faizi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox