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.

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

3 Firefox Javascript errors: (1) "info is null" /minified/pad.js line 2493 ; (2) syntax error /socket.io/1/xhr-polling/ "1" (3) syntax error /jserror "OK" #252

Closed
Wikinaut opened this issue Nov 30, 2011 · 14 comments
Assignees
Labels
Milestone

Comments

@Wikinaut
Copy link
Contributor

In Firefox there's are these error messages:

(1)
Error: info is null
Source: http://beta.etherpad.org/minified/pad.js
Zeile: 2493

(2)
Error: Syntax error
Quelldatei: http://beta.etherpad.org/socket.io/1/xhr-polling/1490956074432109169?t=1322639214850
Line: 1, Column: 1
Source:
1

(3)
Syntax error line 1
beta.etherpad.org/jserror
OK

@Wikinaut
Copy link
Contributor Author

Wikinaut commented Dec 1, 2011

Can someone with Firefox confirm my observations regarding the Javascript errors ?

@crash-dive
Copy link

Firefox does the same for me. It seems to be caused only when the property "grayedOut" is being set. However I have never come across that property before so I do not know what it does.

The error is not just in FF, I opened Chrome and looked and info is null when grayedOut is being set there as well, it is just no error is thrown to the console.

@Pita
Copy link
Contributor

Pita commented Dec 4, 2011

@ja-jo what is grayedOut?

@crash-dive
Copy link

Sorry should have given a little more info, I will do my best but I am still not 100% on how all the editor works.

The error Wikinaut is talking abouts comes during initialisation of the info object in pad.js. This object is created on line 2403 by calling the Ace2Editor function and is then used by a lot of functions via closure scoping.

However on line 1301 the function padeditor.disable calls editor.setProperty (grayedOut", true) this function then in turn calls info.ace_setProperty found on line 2493 (note we have now hit the info object). However this is done before the function Ace2Editor is called, meaing that info has not been set and therefore a null error is thrown to the console.

I hope that helps explain a little better what is going on.

@ghost ghost assigned Pita and JohnMcLear Dec 4, 2011
@JohnMcLear
Copy link
Member

Looking into this as my next job.

@JohnMcLear
Copy link
Member

Quick fix for the "info" error
https://github.com/johnyma22/etherpad-lite/commit/0810915f2c708b54b93dda0ab5364242679a4aef &
https://github.com/johnyma22/etherpad-lite/commit/2038659ac71a9053b2e3ffbe3d336ce7de93df44

Looking at the Syntax error next, note, can't replicate this error, I think Pita might of fixed this one. So if @Pita merges the two commits above it should stop you seeing any errors.

Someone should probably look to see why the setProperty stuff is firing too early though, I don't know my way around that process to help.

@Wikinaut
Copy link
Contributor Author

Wikinaut commented Dec 7, 2011

The info error (1) is unfortunately still present (the other errors (2) and (3) in my list disappeared). (Firefox)

Fehler: info is null
Quelldatei: https://pad.opteryx.org/minified/pad.js
Zeile: 2497

@JohnMcLear
Copy link
Member

I can confirm this is still an issue

@marcelklehr
Copy link
Contributor

I'm using FF10 and see no errors on the console...

@Wikinaut
Copy link
Contributor Author

this is an old report. Will checkout with the latest revision and then probably close this issue, depending on my observations.

@Wikinaut
Copy link
Contributor Author

Yes, still one error.

Error: illegal character
Source: https://pad.server.com/minified/pad.js Line 1

This file starts that way:

require.define({"/pad.js": (function (require, exports, module) {/**

  • This code is mostly from the old Etherpad. Please help us to comment this code.
  • This helps other people to understand this code better and helps them to improve it.
  • TL;DR COMMENTS ON THIS FILE ARE HIGHLY APPRECIATED
    */

@Wikinaut
Copy link
Contributor Author

perhaps the comment should be placed outside the require.define

@cweider
Copy link
Contributor

cweider commented Feb 16, 2012

@Wikinaut, what happens if the comment is removed? The line number may not be reliable, IIRC, errors that occur when the editor iframe is written can be very misleading. Also, while this is a problem, I’m guessing it’s unrelated to this issue, separate ticket?

@JohnMcLear
Copy link
Member

Do we have a reliable way to consistently reproduce this bug?

muxator added a commit that referenced this issue Oct 20, 2019
This upgrade should be backward compatible, but still suffers form major
vulnerabilities in its https-proxy-agent transitive dependency (see
https://www.npmjs.com/advisories/1184).

Changelog:
- https://github.com/npm/cli/releases

6.12.0 (2019-10-08):
    Now npm ci runs prepare scripts for git dependencies, and respects the
    --no-optional argument. Warnings for engine mismatches are printed again.
    Various other fixes and cleanups.

    BUG FIXES
    890b245dc #252 ci: add dirPacker to options (@claudiahdz)
    f3299acd0 #257 npm.community#4792 warn message on engine mismatch
                   (@ruyadorno)
    bbc92fb8f #259 npm.community#10288 Fix figgyPudding error in npm token
                   (@benblank)
    70f54dcb5 #241 doctor: Make OK more consistent (@gemal)

    FEATURES
    ed993a29c #249 Add CI environment variables to user-agent (@isaacs)
    f6b0459a4 #248 Add option to save package-lock without formatting Adds a new
                   config --format-package-lock, which defaults to true.
                   (@bl00mber)

DEPENDENCIES
    0ca063c5d [email protected]:
        fix: filter functions and undefined out of makeEnv (@isaacs)
    5df6b0ea2 [email protected]:
        fix: pack git directories properly (@claudiahdz)
        respect no-optional argument (@cruzdanilo)
    7e04f728c [email protected]
    5c380e5a3 [email protected] (@isaacs)
    62f2ca692 [email protected] (@isaacs)
    0ff0ea47a [email protected] (@isaacs)
    f46edae94 [email protected] (@isaacs)

TESTING
    44a2b036b #262 fix root-ownership race conditions in meta-test (@isaacs)

6.11.3 (2019-09-03):
    Fix npm ci regressions and npm outdated depth.

    BUG FIXES
    235ed1d28 #239 Don't override user specified depth in outdated. Restores
                   ability to update packages using --depth as suggested by npm audit. (@G-Rath)
    1fafb5151 #242 npm.community#9586 Revert "install: do not descend into
                   directory deps' child modules" (@isaacs)
    cebf542e6 #243 npm.community#9720 ci: pass appropriate configs for file/dir
                   modes (@isaacs)

    DEPENDENCIES
    e5fbb7ed1 [email protected] (@claudiahdz)
    23ce65616 [email protected] (@claudiahdz)

6.11.2 (2019-08-22):
    Fix a recent Windows regression, and two long-standing Windows bugs. Also,
    get CI running on Windows, so these things are less likely in the future.

    DEPENDENCIES
    9778a1b87 [email protected]: Fix regression where shims fail to preserve exit
              code (@isaacs)
    bf93e91d8 [email protected]: Properly handle git+file: urls on Windows
              when a drive letter is included. (@isaacs)

    BUGFIXES
    6cc4cc66f escape args properly on Windows Bash Despite being bash, Node.js
              running on windows git mingw bash still executes child processes
              using cmd.exe. As a result, arguments in this environment need to
              be escaped in the style of cmd.exe, not bash. (@isaacs)

    TESTS
    291aba7b8 make tests pass on Windows (@isaacs)
    fea3a023a travis: run tests on Windows as well (@isaacs)

6.11.1 (2019-08-20):
    Fix a regression for windows command shim syntax.

    37db29647 [email protected] (@isaacs)

v6.11.0 (2019-08-20):
    A few meaty bugfixes, and introducing peerDependenciesMeta.

    FEATURES
    a12341088 #224 Implements peerDependenciesMeta (@arcanis)
    2f3b79bba #234 add new forbidden 403 error code (@claudiahdz)

    BUGFIXES
    24acc9fc8 and 45772af0d #217 npm.community#8863 npm.community#9327 do not
              descend into directory deps' child modules, fix shrinkwrap files
              that inappropriately list child nodes of symlink packages (@isaacs
              and @salomvary)
    50cfe113d #229 fixed typo in semver doc (@gall0ws)
    e8fb2a1bd #231 Fix spelling mistakes in CHANGELOG-3.md (@XhmikosR)
    769d2e057 npm/uid-number#7 Better error on invalid --user/--group configs.
              This addresses the issue when people fail to install binary
              packages on Docker and other environments where there is no
              'nobody' user. (@isaacs)
    8b43c9624 nodejs/node#28987 npm.community#6032 npm.community#6658
              npm.community#6069 npm.community#9323 Fix the regression where
              random config values in a .npmrc file are not passed to lifecycle
              scripts, breaking build processes which rely on them. (@isaacs)
    8b85eaa47 save files with inferred ownership rather than relying on SUDO_UID
              and SUDO_GID. (@isaacs)
    b7f6e5f02 Infer ownership of shrinkwrap files (@isaacs)
    54b095d77 #235 Add spec to dist-tag remove function (@theberbie)

    DEPENDENCIES
    dc8f9e52f [email protected]: Infer the ownership of all unpacked files in
              node_modules, so that we never have user-owned files in root-owned
              folders, or root-owned files in user-owned folders. (@isaacs)
    bb33940c3 [email protected]:
        9c93ac3 #2 npm#3380 Handle environment variables properly (@basbossink)
        2d277f8 #25 #36 #35 Fix 'no shebang' case by always providing $basedir
                in shell script (@igorklopov)
        adaf20b #26 Fix $* causing an error when arguments contain parentheses
                (@satazor)
        49f0c13 #30 Fix paths for MSYS/MINGW bash (@dscho)
        51a8af3 #34 Add proper support for PowerShell (@ExE-Boss)
        4c37e04 #10 Work around quoted batch file names (@isaacs)
    a4e279544 [email protected] (@isaacs):
        fail properly if uid-number raises an error
    7086a1809 [email protected] (@isaacs)
    8845141f9 [email protected] (@isaacs)
    51c028215 [email protected] (@isaacs)
    534a5548c [email protected] (@isaacs)
    3038f2fd5 [email protected] (@isaacs)
    a609a1648 [email protected] (@isaacs)
    f0346f754 [email protected] (@isaacs)
    ca9c615c8 [email protected] (@isaacs)
    b417affbf [email protected] (@isaacs)

    TESTS
    b6df0913c #228 Proper handing of /usr/bin/node lifecycle-path test (@olivr70)
    aaf98e88c [email protected] (@isaacs)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants