Skip to content

bug: Moving comment threads fails due to an assertion error #2649

Closed
@ryanbreen

Description

Steps To Reproduce

Using a develop build, create a comment thread and attempt to move it.

Expected behavior

You should be able to reposition comment threads without error.

Actual behavior

You should be able to reposition comment threads without error.

Screenshots or video

image

image

Desktop (please complete the following information)

No response

Smartphone (please complete the following information)

No response

Environment (please complete the following information)

No response

Frontend Stack Trace

Error: Assert failed: (gpt/point? position)
    at Object.app$common$types$shape_tree$frame_id_by_position [as frame_id_by_position] (shape_tree.cljc:204:3)
    at Object.eval [as potok$core$WatchEvent$watch$arity$3] (comments.cljs:126:29)
    at Object.potok$core$watch [as watch] (core.cljs:31:11)
    at process_watch (core.cljs:178:26)
    at Object.process_event [as next] (core.cljs:207:17)
    at ConsumerObserver.next (Subscriber.js:114:33)
    at Subscriber._next (Subscriber.js:81:26)
    at Subscriber.next (Subscriber.js:52:18)
    at eval (Subject.js:70:34)
    at exports.errorContext (errorContext.js:23:9)

Backend Stack Trace

No response

Additional context

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions