Travis builds are currently erroring due to an issue in Cask about typescript.el HOT 5 CLOSED

That sucks, but I guess there's not much we can do about it. Apart from waiting it out, right?

Good thing bringing it to our attention though, otherwise this could quite easily become a point of confusion :)

from typescript.el.

Yeah, I wanted folks to be aware of the issue. Luckily, the Cask issue report I linked to was already filed. Otherwise, I would have been at a loss to figure out what's going on.

When I run into problems like this one, and I already have a good amount of knowledge about the piece of software that is failing, I try to fix it myself, but the extent of my knowledge of Cask is minuscule, and I cannot at the moment justify the time expense of becoming proficient enough with Cask to solve this problem, so I'm certainly going to wait it out.

from typescript.el.

It seems fixed now.

from typescript.el.

@lddubeau still this issue is not resolved cask/cask#420

from typescript.el.

@anildigital I closed this issue because I was no longer getting errors on Travis when running the tests for this project. There could be any number of reasons the Cask issue is still open: they forgot to close it, a change occurred that did not completely take care of the problem, though it was enough to fix the issue for this project, etc. Ultimately though, if our tests suite works, then there's no problem for us, and nothing to fix.

Did you run this project's test suite and got an error again? If yes, then please comment with a link to the Travis session's log.

from typescript.el.