-
-
Notifications
You must be signed in to change notification settings - Fork 302
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
update ace to v1.2.9; fix ts build; #93
Conversation
Thanks @filipsch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it LGTM in general. It's not related with this PR but there is a minor that I commented on.
ext/searchbox.js
Outdated
this.editor = editor; | ||
}; | ||
|
||
this.setSession = function(e) { | ||
debugger |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that seems weird, it's introduced with https://github.com/ajaxorg/ace/pull/3329/files#diff-2b1fc8367171d51dd3148748a50accb2R88 on Ace repo 23 days ago. maybe we should let them know first fix there and merge after the change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
created a PR for that ajaxorg/ace#3358 fyi.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK let's wait for that to go through and then run the upgrade again.
Don't want to pull anything in that introduces an obvious bug from the upstream code base.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's merged on upstream, if @filipsch can update the code we are good to go I believe 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I'll have to wait for ajaxorg to make a new release of ace, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah better since we don't want to depend on an unreleased version.
…hub.com/sevin7676/Ace.Tern/tree/master/ace-builds/src-noconflict to be available for brace "build/update" proces - hack update script to include ext-tern.js and worker-tern.js to the build - include update script fix from thlorenz#93
When will you merge this request? As |
@gokmen noticed that the people from ace merged in a bug (a |
Is there a link to an issue requesting a new ace release that someone could provide? FWIW, I'd be OK with using Ace 1.2.8 even with the debugger statement, especially considering there are bugs that impact my downstream users fixed in 1.2.8. To my knowledge, the From another POV, if brace upgrades to 1.2.8, then more people can experience any issue that this causes and then check in with upstream to get it fixed / released. |
Ace 1.2.9 has been released! Now with one less debugger statement 😺 |
@shepmaster I'll update the PR then to depend on v1.2.9, and see if the builds still work. |
Done, but my new commit and push to the |
Huh; I see the same behavior. Maybe it's just some GitHub slowness? Edit — Yeah "We are investigating reports of elevated error rates." 11 minutes ago Edit2 — I see it now! 🎉 |
@shepmaster Okay cool; we're ready then. @gokmen can this be merged in now, and can a new release be made at the same time? Thanks! |
it's good to go for me 👍, on you @thlorenz |
@thlorenz ping! |
Sorry, just seeing this now. LGTM @filipsch made you collaborator. Please merge to master following this guide. Thanks. Obviously @gokmen if you see this first and want to merge, fine by me. Just ping me when done and I'll publish a new minor to npm. |
@thlorenz done! Ping me when new version is released and published; thanks! |
@filipsch getting test errors (did you run I have 10/10 tests failing. If we cannot solve this today we need to revert the commits from master. |
OK, confirmed that before these commits everything works fine.
|
@thlorenz will look into it before EOD. |
OK I force pushed to master, reverting the commits (hoping no one else but the two of us updated from master at this point). Sorry to do this, but I feel this is better to have reverted these and now we can calmly figure out why things broke. |
@thlorenz completely understand; I should have run the test scripts before; my bad. |
No problem (we caught it in time). Probably best to open another PR with the changes as I cannot reopen this one. |
@shepmaster I know you can do that, but that adds extra commits. |
Is this still going to happen? I was looking forward to the update. |
@LeviRosol it's still on my todo list, but I'm pretty swamped at my daytime job currently. When doing this PR, I didn't dive into the |
no worries. I assumed as much. If I can find some time I'll try to lend a hand. |
aceTag
tov1.2.8
build/update-ts.js
to follow new structure ofDefinitivelyTyped
repo.