helvede.net is one of the many independent Mastodon servers you can use to participate in the fediverse.
Velkommen til Helvede, fediversets hotteste instance! Vi er en queerfeministisk server, der shitposter i den 9. cirkel. Welcome to Hell, We’re a DK-based queerfeminist server. Read our server rules!

Server stats:

158
active users

#issue

0 posts0 participants0 posts today
Continued thread

So it does look like the TypeScript language server has a limit of 4MB source size where it disables type checking (and actually shows an erroneous error stating that exports that exist in the file do not exist) for files that are imported but not open in the current workspace/session.

Still not sure if this is documented anywhere or not (haven’t been able to find it, if it is).

99.99999% of the time, unless you’re doing niche stuff like I am, you won’t run into this.

Workaround: should you have such a large file, e.g., with a large generated object, try and refactor to split it up into multiple files and rejoin it a separate file. The actual object size/memory usage isn’t the issue, it’s the file size.

github.com/typescript-language

I ran into an issue while creating and exporting a constant object that holds component versions of the ~1,500 icons in the Phorsphor icons library and I’ve created the simple reproduction below: D...
GitHubServer fails on import when exported object constant has too many entries/is too large · Issue #951 · typescript-language-server/typescript-language-serverBy aral
#TypeScript#max#lines

More #Etsy stupidity. Every time I have a #problem with Etsy, I contact their #support (with great difficulty), and after re-explaining things a few times to the drones who are just pasting irrelevant #canned responses into their replies, I finally get across to them that there is an #issue their #FAQs don't address.

At which point they cannot solve it. Of course. But it seems like they *also* give me a new #problem without a #solution.

Previously, on "What #Stupidity Has Etsy Committed This Week?", for those who didn't see my last post in this series:

1/x

I am having some kind of iCloud problem that's driving me insane. If anyone has ideas, please share them.

A few days ago I sent an image through Messages on iOS to a group and got a "Not Delivered" marker next to it. Tried a few times -- same. I can click and send as SMS, and it goes through. I then noticed this same behavior happening on my Mac.

According to my phone, I am logged into my iCloud account. I then noticed an alert in Settings on iOS saying to "Update Apple ID Settings." So, I go to do so and see (image attached):

-- -- -- --
Update Apple ID Settings
Some account services required you to sign in again.

[Continue]
-- -- -- --

When I click continue, the waiting glyph spins for 2-3 seconds and then stops -- nothing happens. Over and over. Rebooting the phone (and on last reboot it picked up the latest iOS update) made no difference.

( Also I see my iCloud backup has not run in 2 weeks and I got a warning - so I clicked "Backup Now," which rebooted the phone... )

I then went to logout of iCloud and received a series of "enter password to logout of" this or that service, then finally warned about all data on the phone being deleted in so doing, choose what I want to retain, etc.

Christ.

Is there another path here other than the monumental event of logging out of iCloud with all the ramifications that come with?

Extremely aggravating. Thanks, anyone.

Replied in thread
It's all song and dance, to me. A pull request is analagous to @'ing you here and saying "Please pull this! Here's what's wrong!" Filing an issue is analagous to @'ing you here and saying "Here's what's wrong! Please pull this!" Github et. al. just dress it up as something fancy, to make you think you'll need to use their centralized website in order to effectively work together.

That said, given the assumption that you're going to do everything through Github, an Issue is probably better than a Pull Request, just because it goes onto their list of issues webpage. (Which here, is analagous to using a tag like #issue)