Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'call') [v1.17.0] #20582

Closed
viceice opened this issue Aug 1, 2022 · 4 comments
Closed

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'call') [v1.17.0] #20582

viceice opened this issue Aug 1, 2022 · 4 comments
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@viceice
Copy link
Contributor

viceice commented Aug 1, 2022

Description

The following error occurs in browser console after upgrade from v1.16.9 on PR and issue details pages

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'call')
    at jt (index.js?v=95cfeb8746010d271b9adf778c18dbad:7:127920)
    at ./node_modules/easymde/src/js/easymde.js (easymde.js:9:43063)
    at jt (index.js?v=95cfeb8746010d271b9adf778c18dbad:7:127920)
    at jt.t (index.js?v=95cfeb8746010d271b9adf778c18dbad:7:128283)

Gitea Version

1.17.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

image

Git Version

2.36.2

Operating System

Linux

How are you running Gitea?

offical docker image

Database

PostgreSQL
@viceice
Copy link
Contributor Author

viceice commented Aug 1, 2022

image
Happens when clicking on edit button 😕

@viceice
Copy link
Contributor Author

viceice commented Aug 1, 2022

OK. seems to be browser cache related 😞

Leaving open if anybody else stumbles on it

@wxiaoguang
Copy link
Contributor

That's a long standing problem but no progress yet.

@noerw noerw added type/question Issue needs no code to be fixed, only a description on how to fix it yourself. and removed type/bug labels Aug 1, 2022
@silverwind
Copy link
Member

Don't need to keep this open really

@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@silverwind @viceice @wxiaoguang @noerw