{@literal @} retains {} when inside nested code components [276955543]

In Progress

Bug

Status Update

No update yet.

Description

as...@google.com

created issue #1

Apr 4, 2023 08:51PM

<pre> {@code 
   {@literal @}Override
}

is rendered as {@}Override

The work around is to remove the nested code tags. <pre> is preferred over @code

Comments

na...@google.com <na...@google.com> #2Apr 24, 2023 04:43PM

Assigned to as...@google.com.

This should be fixed upstream. Let's file a bug over there (if one does not exist already).

as...@google.com <as...@google.com> Apr 25, 2023 02:19PM

Reassigned to bu...@google.com.

bu...@google.com <bu...@google.com> #3Apr 25, 2023 02:19PM

Reassigned to as...@google.com.

Nothing was specified to wait for and there are no blocking bugs or pending CLs. For usage information see go/bugjuggler.

as...@google.com <as...@google.com> #4Apr 25, 2023 02:19PM

Reassigned to bu...@google.com.

Bugjuggler: https://github.com/Kotlin/dokka/issues/2982

bu...@google.com <bu...@google.com> #5Apr 25, 2023 02:19PM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com.

bu...@google.com <bu...@google.com> #6May 17, 2023 01:00PM

Assigned to as...@google.com.

I've seen too many errors and am giving up, sorry.

I should wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com but encountered:
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TIMEOUT
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TOO_MANY_PENDING
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": context deadline exceeded

as...@google.com <as...@google.com> #7Jun 7, 2023 04:13PM

Reassigned to bu...@google.com.

Bugjuggler: https://github.com/Kotlin/dokka/issues/2982

bu...@google.com <bu...@google.com> #8Jun 7, 2023 04:13PM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com.

bu...@google.com <bu...@google.com> #9Jun 10, 2023 04:42AM

Assigned to as...@google.com.

I've seen too many errors and am giving up, sorry.

I should wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com but encountered:
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TIMEOUT
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TOO_MANY_PENDING

as...@google.com <as...@google.com> #10Jun 13, 2023 06:11PM

Reassigned to bu...@google.com.

Bugjuggler: https://github.com/Kotlin/dokka/issues/2982

bu...@google.com <bu...@google.com> #11Jun 13, 2023 06:12PM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com.

bu...@google.com <bu...@google.com> #12Jun 14, 2023 12:39AM

Assigned to as...@google.com.

I've seen too many errors and am giving up, sorry.

I should wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com but encountered:
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_SCHEDULE_TIME_OVER_DEADLINE
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TIMEOUT
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TOO_MANY_PENDING

as...@google.com <as...@google.com> #13Jun 26, 2023 04:51PM

Reassigned to bu...@google.com.

Bugjuggler: https://github.com/Kotlin/dokka/issues/2982

bu...@google.com <bu...@google.com> #14Jun 26, 2023 04:52PM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com.

bu...@google.com <bu...@google.com> #15Jun 29, 2023 02:05AM

Assigned to as...@google.com.

I've seen too many errors and am giving up, sorry.

I should wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com but encountered:
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TIMEOUT
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TOO_MANY_PENDING
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_SCHEDULE_TIME_OVER_DEADLINE

as...@google.com <as...@google.com> Jul 31, 2023 05:08PM

Reassigned to bu...@google.com.

bu...@google.com <bu...@google.com> #16Jul 31, 2023 05:08PM

Reassigned to as...@google.com.

Nothing was specified to wait for and there are no blocking bugs or pending CLs. For usage information see go/bugjuggler.

as...@google.com <as...@google.com> #17Jul 31, 2023 05:08PM

Reassigned to bu...@google.com.

Bugjuggler: https://github.com/Kotlin/dokka/issues/2982

bu...@google.com <bu...@google.com> #18Jul 31, 2023 05:09PM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com.

bu...@google.com <bu...@google.com> #19Dec 9, 2023 10:28AM

Assigned to as...@google.com.

I've seen too many errors and am giving up, sorry.

I should wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com but encountered:
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TIMEOUT
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TOO_MANY_PENDING

as...@google.com <as...@google.com> #20Mar 28, 2024 05:21PM

Reassigned to bu...@google.com.

Bugjuggler: https://github.com/Kotlin/dokka/issues/2982

bu...@google.com <bu...@google.com> #21Mar 28, 2024 05:21PM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com.

bu...@google.com <bu...@google.com> #22May 29, 2024 01:43PM

Assigned to as...@google.com.

I've seen too many errors and am giving up, sorry.

I should wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com but encountered:
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TIMEOUT
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TOO_MANY_PENDING
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_SCHEDULE_TIME_OVER_DEADLINE

as...@google.com <as...@google.com> #23May 29, 2024 01:44PM

Reassigned to bu...@google.com.

Bugjuggler: https://github.com/Kotlin/dokka/issues/2982

bu...@google.com <bu...@google.com> #24May 29, 2024 01:44PM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com.

Some errors occurred during initial polling, but I will retry for a bit longer before I give up as they might be transient.
I should wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com but encountered:
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TIMEOUT

bu...@google.com <bu...@google.com> #25May 30, 2024 09:33AM

Assigned to as...@google.com.

I've seen too many errors and am giving up, sorry.

I should wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com but encountered:
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TOO_MANY_PENDING
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_SCHEDULE_TIME_OVER_DEADLINE
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TIMEOUT

as...@google.com <as...@google.com> #26May 30, 2024 06:01PM

Reassigned to bu...@google.com.

Bugjuggler: https://github.com/Kotlin/dokka/issues/2982

bu...@google.com <bu...@google.com> #27May 30, 2024 06:01PM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com.

bu...@google.com <bu...@google.com> #28Sep 24, 2024 03:02PM

Assigned to as...@google.com.

I've seen too many errors and am giving up, sorry.

I should wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com but encountered:
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TIMEOUT
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/2982": harpoon URL rejected REJECTED_FC_TOO_MANY_PENDING

as...@google.com <as...@google.com> #29Feb 25, 2025 02:31AM

Reassigned to bu...@google.com.

Bugjuggler: https://github.com/Kotlin/dokka/issues/2982

bu...@google.com <bu...@google.com> #30Feb 25, 2025 02:31AM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait for

https://github.com/Kotlin/dokka/issues/2982 to be closed and then assign the bug to asfalcone@google.com.

Issue 276955543

Description

Issue summary

Comments

na...@google.com <na...@google.com> #2Apr 24, 2023 04:43PM

as...@google.com <as...@google.com> Apr 25, 2023 02:19PM

bu...@google.com <bu...@google.com> #3Apr 25, 2023 02:19PM

as...@google.com <as...@google.com> #4Apr 25, 2023 02:19PM

bu...@google.com <bu...@google.com> #5Apr 25, 2023 02:19PM

bu...@google.com <bu...@google.com> #6May 17, 2023 01:00PM

as...@google.com <as...@google.com> #7Jun 7, 2023 04:13PM

bu...@google.com <bu...@google.com> #8Jun 7, 2023 04:13PM

bu...@google.com <bu...@google.com> #9Jun 10, 2023 04:42AM

as...@google.com <as...@google.com> #10Jun 13, 2023 06:11PM

bu...@google.com <bu...@google.com> #11Jun 13, 2023 06:12PM

bu...@google.com <bu...@google.com> #12Jun 14, 2023 12:39AM

as...@google.com <as...@google.com> #13Jun 26, 2023 04:51PM

bu...@google.com <bu...@google.com> #14Jun 26, 2023 04:52PM

bu...@google.com <bu...@google.com> #15Jun 29, 2023 02:05AM

as...@google.com <as...@google.com> Jul 31, 2023 05:08PM

bu...@google.com <bu...@google.com> #16Jul 31, 2023 05:08PM

as...@google.com <as...@google.com> #17Jul 31, 2023 05:08PM

bu...@google.com <bu...@google.com> #18Jul 31, 2023 05:09PM

bu...@google.com <bu...@google.com> #19Dec 9, 2023 10:28AM

as...@google.com <as...@google.com> #20Mar 28, 2024 05:21PM

bu...@google.com <bu...@google.com> #21Mar 28, 2024 05:21PM

bu...@google.com <bu...@google.com> #22May 29, 2024 01:43PM

as...@google.com <as...@google.com> #23May 29, 2024 01:44PM

bu...@google.com <bu...@google.com> #24May 29, 2024 01:44PM

bu...@google.com <bu...@google.com> #25May 30, 2024 09:33AM

as...@google.com <as...@google.com> #26May 30, 2024 06:01PM

bu...@google.com <bu...@google.com> #27May 30, 2024 06:01PM

bu...@google.com <bu...@google.com> #28Sep 24, 2024 03:02PM

as...@google.com <as...@google.com> #29Feb 25, 2025 02:31AM

bu...@google.com <bu...@google.com> #30Feb 25, 2025 02:31AM

Add comment

Issue metadata