dns: Drop the admin node after initial deployment (SOC-10636)

As it stands, the DNS barclamp is applied with only the admin node in
the dns-server role. As the first part of the proposal step, it adds the
first two nodes (for a total of 3 nodes) so we get multi-master DNS.
Filter out the lead node, which should drop the admin node from the
role.

There was a known issue around crowbar updating DNS and trying to use the new entries immediately after that.


BUG: misc: allow both cmin/cmax and low/high params in bytescale

Resolves issue #6552 where bytescaling an array using both cmin/cmax and low/high parameters resulted in an unexpected array.

Would be nice to close gh-6552, gh-4458 and gh-5305 all in one go here.

(This started out as a reply to Ralf's inline comment, but it got a little too long for an inline comment reply.)
If we ignore error-checking for the moment, it looks likes this function could almost be written as:
def bytescale(data, cmin=None, cmax=None, high=255, low=0):

    if cmin is None:
        cmin = data.min()
    if cmax is None:
        cmax = data.max()

    # Linear map from [cmin, cmax] to [low, high]
    scale = float(high - low) / (cmax - cmin)
    scaled_data = (scale * data) + low

    # Quantize the scaled data by rounding.
    scaled8bit = scaled_data.round().clip(0, 255).astype(np.uint8)  # XXX Probably not what we want!

    return scaled8bit

In the existing code (not this pull request), round is not used.  Instead, 0.4999 is added before the scaled data is truncated to integers.  That leads to behavior that I consider a bug:
In [48]: bytescale(np.array([5.0001]), cmax=10.0, cmin=0.0, high=1, low=0)
Out[48]: array([0], dtype=uint8)

In [49]: bytescale(np.array([5.001]), cmax=10.0, cmin=0.0, high=1, low=0)
Out[49]: array([1], dtype=uint8)

Under any reasonable convention for handling the points exactly on a quantization boundary, the above results should both be 1.
I suspect the intent of adding 0.4999 was to always round down.  In the boundary cases, np.round rounds to the nearest even value, which is probably not what we want:
In [67]: r = np.array([0.5, 1.5, 2.5, 3.5, 4.5, 5.5])

In [68]: r.round()
Out[68]: array([0.,  2.,  2.,  4.,  4.,  6.])

Suppose we do want to always round down.  The numpy round/around functions don't provide an option for that behavior.  We could change the constant 0.4999 to something even closer to 0.5, e.g.:
In [130]: d = 0.5 - 65*np.finfo(np.float64).eps

In [131]: r = np.array([0.5, 1.5, 2.5, 3.5, 4.5, 253.5, 254.5])

In [132]: (r + d).astype(np.uint8)
Out[132]: array([  0,   1,   2,   3,   4, 253, 254], dtype=uint8)

Or use np.where (or something equivalent, e.g. lazy_where):
In [156]: set_printoptions(formatter=dict(float=lambda t: "%6.2f" % t))

In [157]: x
Out[157]:
array([  0.00,   0.25,   0.50,   0.75,   1.00,   1.25,   1.50,   1.75,
         2.00, 254.00, 254.25, 254.50, 254.75, 255.00])

In [158]: np.where((x % 1) == 0.5, np.floor(x), np.round(x))
Out[158]:
array([  0.00,   0.00,   0.00,   1.00,   1.00,   1.00,   1.00,   2.00,
         2.00, 254.00, 254.00, 254.00, 255.00, 255.00])

I like the idea of using astype(uint8) instead of cast[uint8] since this would preserve ndarray subclasses (i.e. bytescale on a masked array would return a masked array). Right now, this isn't the case.
Regarding rounding, what's the rationale for wanting to round down? If we don't want to use numpy's round() function because it implements a 'bankers' rounding, why not add 0.5 and truncate to round up (rather than 0.4999 or some number closer to but still less than 0.5 to round down)?

Regarding rounding, what's the rationale for wanting to round down?

I don't know; my interpretation of the intent of adding 0.4999 instead of 0.5 is just a guess.  We're now dealing with the fallout of an undocumented magic constant.  Grrr.

... why not add 0.5 and truncate to round up ...

If we were starting from scratch, I think that would be a reasonable thing to do.  Perhaps it is a reasonable thing to do now, too.  It might cause some different results in some cases, but I think we can argue that many of those cases (e.g. the example I gave earlier) were actually incorrect, so we're fixing a bug.   But in an example such as bytescale(np.array([0, 0.5, 1]), low=0, high=1), the result changes from array([0, 0, 1]) to array([0, 1, 1]).  Can we justify that as the natural consequence of a bug fix?  As I write this, I'm leaning towards "Yes, we can", but it would be good to get the opinion of some other devs.

@WarrenWeckesser You also suggested clipping to (0, 255), rather than clipping to (low, high):

scaled8bit = scaled_data.round().clip(0, 255).astype(np.uint8)  # XXX Probably not what we want!

The initial implementation was clipping between (0, high), which I assumed was a mistake. In my mind, clipping between (low, high) seemed like the correct approach, and therefore I wrote a unittest to support that output.
But obviously clipping to (0, 255) yields different results. Which is preferred?
Clipping output to (low, high):
In [4]: bytescale(np.arange(10), cmin=3, cmax=6, low=100, high=200)
Out[4]: array([100, 100, 100, 100, 133, 167, 200, 200, 200, 200], dtype=uint8)

Clipping output to (0, 255):
In [4]: bytescale(np.arange(10), cmin=3, cmax=6, low=100, high=200)
Out[4]: array([  0,  33,  67, 100, 133, 167, 200, 233, 255, 255], dtype=uint8)

You also suggested clipping to (0, 255), rather than clipping to (low, high) ...

I didn't think too much about that aspect when I wrote the code.   Now I think clipping to (low, high) makes more sense.
By the way, there is currently a check for low <= high.  That could be extended to check for 0 <= low <= high <= 255.

I've added a few more changes, based on the comments provided above. Thanks for your feedback!

This looks good to me, and all the tests still pass.
There are some edges cases where this returns a different array.  In particular, this is evident in the modified test of bytescale(np.array([0, 1, 2])), which now returns [0, 128, 255] instead of [0, 127, 255].  I see this as a consequence of a bug fix, and not a backwards incompatibility--see my earlier comments.  There are probably one or two devs that are more conservative than me concerning backwards compatibility, so I'll hold off on merging this.

Changes look reasonable to me. Before merging would be good to check how this affects imsave (gh-4458 and gh-5305).

So I looked into #4458. The changes made in this PR have very little affect on imresize. The only affect would be due to the rounding changes made.
Some background on #4458: If 'mode' is not specified when calling misc.imresize', then misc.imresizecallsmisc.toimagewithmode=None. If 'misc.toimage is called with mode=None, it then calls misc.bytescale, which will output an 8bit image scaled to (0,255).
This PR doesn't change any of that logic. The only affect this PR should have on misc.imresize is slightly different pixel values due to the rounding change introduced here. This is evident on the different mean value of the output image when the input image is not 8bit (e.g. clock3 images below). I've replicated the example given in issue #4458 on both scipy 0.18.1 and this branch, using skimage.data.clock() instead of scipy.misc.lena():
imresize on scipy 0.18.1
In [1]: import scipy

In [2]: scipy.__version__
Out[2]: '0.18.1'

In [3]: from skimage import data

In [4]: clock = data.clock()

In [5]: def stats(img):
    ...:     print 'min', img.min()
    ...:     print 'mean', img.mean()
    ...:     print 'max', img.max()
    ...:     print 'shape', img.shape
    ...:     print 'dtype', img.dtype
    ...:

In [6]: clock2 = scipy.misc.imresize(clock.astype('uint8'), [1000, 1000])

In [7]: clock3 = scipy.misc.imresize(clock.astype('float32'), [1000, 1000])

In [8]: stats(clock)
min 99
mean<PHONE_NUMBER>33
max 247
shape (300, 400)
dtype uint8

In [9]: stats(clock2)
min 99
mean 146.398597
max 247
shape (1000, 1000)
dtype uint8

In [10]: stats(clock3)
min 0
mean 81.600154
max 254
shape (1000, 1000)
dtype uint8

In [11]:

imresize on misc.bytescale-lowhigh branch
In [1]: import scipy

In [2]: scipy.__version__
Out[2]: '0.19.0.dev0+09d22ca'

In [3]: from skimage import data

In [4]: clock = data.clock()

In [5]: def stats(img):
    ...:     print 'min', img.min()
    ...:     print 'mean', img.mean()
    ...:     print 'max', img.max()
    ...:     print 'shape', img.shape
    ...:     print 'dtype', img.dtype
    ...:

In [6]: clock2 = scipy.misc.imresize(clock.astype('uint8'), [1000, 1000])

In [7]: clock3 = scipy.misc.imresize(clock.astype('float32'), [1000, 1000])

In [8]: stats(clock)
min 99
mean<PHONE_NUMBER>33
max 247
shape (300, 400)
dtype uint8

In [9]: stats(clock2)
min 99
mean 146.398597
max 247
shape (1000, 1000)
dtype uint8

In [10]: stats(clock3)
min 0
mean 81.601141
max 254
shape (1000, 1000)
dtype uint8

In [11]:

Also note that the issue identified in #4458 can be easily overcome by simply providing an appropriate mode parameter when calling imresize:
In [20]: stats(scipy.misc.imresize(clock.astype('float32'), [1000, 1000], mode='F'))
min 99.345
mean 146.331
max 246.36
shape (1000, 1000)
dtype float32

We could probably make a change to misc.imresize to check the datatype of the input image and call toimage with the appropriate mode parameter set, but my preference would be to address that in a separate PR.

Regarding #5305, it's pretty much the same situation as #4458. As far as I can tell, this PR should have very little impact on imsave. The only difference would be a slight difference in values due to the changes in rounding.
The main issue with misc.imsave is that it calls misc.toimage' with default parameters. So saving a float32 array to an image with misc.imsavewill convert the input array down to an 8bit image and scale the data to (0,255). For PNG images, this may be appropriate, but there are many applications where a user would want their data saved as a float32 TIF image. This isn't possible withmisc.imsave`:
imsave using scipy 0.18.1
In [35]: stats(clock.astype('float32'))
min 99.0
mean 146.332
max 247.0
shape (300, 400)
dtype float32

In [36]: scipy.misc.imsave('/tmp/clock_float32.tif', clock.astype('float32'))

In [37]: clock_float32 = scipy.misc.imread('/tmp/clock_float32.tif')

In [38]: stats(clock_float32)
min 0
mean 81.542275
max 255
shape (300, 400)
dtype uint8

In [39]:

imsave using misc.bytescale-lowhigh
In [13]: stats(clock.astype('float32'))
min 99.0
mean 146.332
max 247.0
shape (300, 400)
dtype float32

In [14]: scipy.misc.imsave('/tmp/clock_float32.tif', clock.astype('float32'))

In [15]: clock_float32 = scipy.misc.imread('/tmp/clock_float32.tif')

In [16]: stats(clock_float32)
min 0
mean 81.5432666667
max 255
shape (300, 400)
dtype uint8

In [17]:

So again, this PR doesn't change the behavior of misc.imsave. It does very slightly change the value of some pixels due to the change in rounding though. My recommendation would be to address the imsave issues brought up in #5305 in a different PR. It should be a fairly easy change by providing an appropriate mode parameter to toimage.

We could probably make a change to misc.imresize to check the datatype of the input image and call toimage with the appropriate mode parameter set, but my preference would be to address that in a separate PR.

Agreed. Thanks for the detailed investigation @gdooper! You've pretty much figured out what's needed for those two issues, so if you'd be interested to send follow up PRs for those that would be great.
This is good to go, so merging. Thanks all!


Obfuscation problem for postgresql database dumps.

Fixes a problem I encountered while trying to obfuscate a postgresql database dump.
Postgresql ends batches of import data in its dumps with .  on a single line.
Currently however, the regular expression deciding to stop importing will also stop when it encounters lines that have a single dot as their last character.
This would be the case for a line that has as as its last column value some data ending in a dot.
This way, you might end up with a partially obfuscated dump.
The small fix will specifically look for the . occurence, which seems to work for me.

Apparently all builds are failing due to a failure in the ffaker module for ruby 1.9.3


Move index to src

Due to index.html being in dist, the auto-deploy script is failing (due to git conflicts as index gets modified for cache bust)

Will do once merged and deployed last version


OpenAd test times out on Travis

The make adAll step of the OpenAD test on Travis fairly regularly times out.
It looks like Travis has an inbuilt workaround for this: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received We just need to put travis_wait at the start of the line.
@christophernhill - opinions on this?

This was fixed by #279. Closing this issue.


Runtime permissions lost after >7 days, permissions need to be regranted

Steps to reproduce

Follow instructions documented in "Installation and setup" (https://github.com/GioBonvi/GoogleContactsEventsNotifier/blob/master/docs/install-and-setup.md).
Run the script. A pop-up box titled "Authorization required" appears. Bread text is "This project requires your permission to access your data". Press "Review permissions" and select account to use. You will face a page with the content "Google hasn’t verified this app. You’ve been given access to an app that’s currently being tested. You should only continue if you know the developer that invited you". Press "Continue" and "Allow". Script will run and produce output as intended.
More than a week later (Google Scripts seems to only keep logs for 7 days), but not more than a month later, step 2 above needs to be repeated for the script to keep running. The behaviour is reoccurring and does not stop after n times.

Expected behaviour
Permissions (step 2 above) should be given once and stay until revoked. While I understand that this is likely related to Google Apps Scripts as a service and not Google Contacts Events Notifier, if this is expected behaviour, it would be wise to include a note on it in the installation documentation.
Context

Version of the script: 5.1.4

Lastly, I want to extend a big thank you to the author and all contributors for their efforts - this is a great little script!

Same Problem!

I am not sure what is going on there. I was not able to reproduce this.
If anyone is willing to take a closer look, feel free!

Same problem, test execution works, run notifyStart - permissions granted, trigger is created, 7 days later no notifications anymore, trigger last executed on 1.04. Running notifyStart requires to grant permissions again, which should not happen as far as I understand

I have observed the execution for a week and today, exactly a week after activation, the script didn't run any more. Executing notifyStart brought me again to the consent screen where I had to grant all those permissions for the script :-(

I noticed, that my project status is test in google cloud platform, I've choosen "publish", let's see if it was it

That is a great find. Please keep us in the loop!

unfortunately, that didn't work, yesterday the script ran for the last time and today no more. I will keep googling :-(

As for now I was not able to reproduce the issue. I set up the script about a year ago (after the last update I applied) and didn't have to re-grant any permission after that.

try to create and assign a new project, I also had no issues for a long time until something broke and I've started to change things and finally created and assigned a new project instead of some default one

I've managed to make it work longer than a week. There is a possiblity to "release" a script (I don't know the exact english version of this button, it is in the top right corner, where versions are managed). So I created a "version" of the script, deleted the trigger for test version and created manually one for "released" version. Since then, it is running.

I've managed to make it work longer than a week. There is a possiblity to "release" a script (I don't know the exact english version of this button, it is in the top right corner, where versions are managed). So I created a "version" of the script, deleted the trigger for test version and created manually one for "released" version. Since then, it is running.

Thanks for the pointer, I am trying it out now. Hopefully iy works! :-)
For anyone else reading this, the "release" mentioned by chpasha is "Deploy" in English.


fix: Uppercase input labels on billing address screen

fix: Uppercase input labels on billing address screen
remove import

The type of this PR is: Bugfix

This PR resolves CX-1911
Description
Uppercase input labels on billing address screen.

Palette V2
Palette V3

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against 53f468ff5eda74b4d7e92e1bd38b5bfd9a10a5ab


Is there a way to initialize a random weight for

Hi! Thank you for the wonderful work of LLM inference.
For now, I am profiling the performance of each part of the code, but I do not care about the output. And the checkpoint loading takes too much time, so I wonder if is there a way to load empty ckpt or just initialize the model with random ones.

Hey @PannenetsF
Thanks a lot for trying this.
I think the benchmark might be better if you use this repo: https://github.com/bigcode-project/bigcode-inference-benchmark/
Thanks :)

Thanks for the response, I will try it out later! @mayank31398

closing this.


Change storage to IBM Cloud Object Storage

Looks like Notebooks on DSX are being pushed to use COS over Object Storage(Swift API)
to comply we'd have to change the cells under Enrichment is now COMPLETE! and replace the put_file function cell to:
cos = ibm_boto3.client(service_name='s3',
    ibm_api_key_id=credentials['IBM_API_KEY_ID'],
    ibm_service_instance_id=credentials['IAM_SERVICE_ID'],
    ibm_auth_endpoint=credentials['IBM_AUTH_ENDPOINT'],
    config=Config(signature_version='oauth'),
    endpoint_url=credentials['ENDPOINT'])

and the cell below to:
# Build the enriched file name from the original filename.
localfilename = 'enriched_' + credentials['FILE']

# Write a CSV file from the enriched pandas DataFrame.
df.to_csv(localfilename, index=False)

# Use the above put_file method with credentials to put the file in Object Storage.
cos.upload_file(localfilename, Bucket=credentials['BUCKET'],Key=localfilename)

Can leave both depending COS and OS(Swift API) and let user comment out either one.

thanks @tylernd27 we've been fixing these as we catch them in all our code patterns. fyi @scottdangelo since you've been fixing them


RFP-1: Goldmund Vanity Miner

A value-add improvement to an existing feature of the subkey utility to generate custom vanity address with mnemonics.
As the first RFP it brings with it a simple and clear goal with exact scope of work, SHA256 verified binaries for Windows and Linux with compilation guides and a user text for the wiki.

@iamexe This RFP seems overpriced. Wrapping existing Rust code in executable files should cost 0.8 XOR from my point of view.
Could you please explain why the estimation is so big?

@pgolovkin at current prices 0.8 XOR is 170$. If it were just compiling existing code into an executable I agree with your statement 100% but please note that there is no such existing rust code yet and there is no way for a user to trust any executable, this would be bad security practice as a bad actor could include an RPC call sending the 12 words of people to their server. The user guide is there to educate users that they should always verify such software and not just trust random executables or links. I am trying to think forward to future scenarios where users get scammed and how to prevent that by educating the community.
Also there is no option that I know of at the moment to mine a custom substrate account including mnemonics without writing additional code.
This is not the same functionality that is already present, it is new functionality.
A big part of the work is providing a compilation guide for users such that they can understand, compile, verify and thus trust the executables.
Additionally to users who already trust the binaries a user guide is also part of the work.
Additionally many users have no idea on how to use 'cmd' or 'terminal' applications or what it even means.
I want to create new functionality (mnemonic option when generating custom accounts for backup), make it as accessible (executables) and trustable (user guides educating normal users on how to use them correctly) for everyone (regular every day people).
If someone else wants to do all that for any other price, they are free to do so. I already spent a lot of time thinking about this in detail and writing the proposal and this comment so I would be happy with 1 XOR so far :)

I have no further interest in supporting this gate keeper, centralized, deceptive, socialist network.
You may close this "request" and may other people work for it if they so choose.
Atlas Shrugged.


"Supports Folia" can be selected regardless of what the plugin actually supports.

Is your feature request related to a problem?
"Supports Folia" is a completely user-determined tag which can be selected regardless of platform, meaning a velocity or waterfall only plugin could specify that it supports Folia when it doesn't.
Describe the solution you'd like.
Folia support is automatically detected by checking if there is a paper-plugin.yml file with folia-supported: true specified.
Describe alternatives you've considered.
Alternative is that it stays as is, which allows a project to mark "Supports Folia" misleadingly.
Other
No response

One possible consideration: what if a project has two release channels: one which supports folia, and one which does not?


Can't see vendetta settings anywhere, how to install plugins and themes?

The "you" section on the far right of the page list. It's in between "scan a qr code" and "billing settings"

I've installes VendettaXposed (Rooted), There's no vendetta settings for me too.


Fix handling of invalid utf-8 sequences in PyString::to_string_lossy

See discussion in #479 and #634.

Thanks!


aldeed:simple-schema - Constraints

Hi theosp
I like to update from tap:i18n  1.2.1 to tap:i18n 1.3.1
tap-i18n 1.3.1 is bound to  aldeed:simple-schema --> 0.7.0.
My project is currently on the latest version aldeed:simple-schema --> 1.3.0.
This leads to an update error:
=> Errors while adding packages:
While selecting package versions:
error: conflict: constraints on aldeed:simple-schema cannot all be satisfied.
Constraints come from:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Regards roman

I can take care of it only Sunday.
A pull request is welcomed.
-Daniel
On 16 Jan 2015 16:19, "roman"<EMAIL_ADDRESS>wrote:

Hi theosp
I like to update from tap:i18n 1.2.1 to tap:i18n 1.3.1
tap-i18n 1.3.1 is bound to aldeed:simple-schema --> 0.7.0.
My project is currently on the latest version aldeed:simple-schema -->
1.3.0.
This leads to an update error:
=> Errors while adding packages:
While selecting package versions:
error: conflict: constraints on aldeed:simple-schema cannot all be
satisfied.
Constraints come from:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Regards roman
—
Reply to this email directly or view it on GitHub
https://github.com/TAPevents/tap-i18n/issues/42.

Published v1.3.2 that uses simple-schema 1.3.0

Starring tap:i18n will be appreciated :)

done :-) thanks.

And how to use it in a schema? I tried what the guy said here: https://github.com/aldeed/meteor-autoform/issues/483 (last answer) but not work.
Thanks!

Ok I get this package working with https://github.com/aldeed/meteor-autoform:
Schema.signIn = new SimpleSchema({
    email: {
        type: String,
        regEx: SimpleSchema.RegEx.Email,
        label: function() {
            return TAPi18n.__('signin_form_input_email');
        },
    },
    password: {
        type: String,
        label: function() {
            return TAPi18n.__('signin_form_input_password');
        },
    }
});

Thanks again!

@jadsonlourenco ooh, nice catch! But it didn't work for me. What versions are you using?

Going further with @jadsonlourenco solution, I did the following in order to keep it more readable:
function __(key) {
    return TAPi18n.__.bind(TAPi18n, key);
}

So you can use it just like:
password: {
   type: String,
    label: __('signin_form_input_password')
}

Of course one can name it whatever they like


Remove unused column cache

This column cache is dead code, and triggers data races with certain
usage patterns. The performance is satisfactory without it, so rather
than add locking around an unused cache, it's easier to :scissors: it!

@markbates This is triggering the build failure with my other PR. Fixes the data race there.

@timraymond all the checks passed here, so i should merge it or not?

@markbates You can merge.


website is not loading

the map loads fine, but it doesn't show any data....
maybe you can bump the hardware a bit ? cache it.....
it was a nice overview

works ok now

Thank you, we have been increasing computational resource to keep it working


Removed .NET Core 3.1 and updated to .NET 6.0

Removed soon to be obsolete .NET Core 3.1 target framework
Support .NET 6.0 now instead
Fixed .NET code analysis errors
Cleaned dependencies in sample projects

@jonorossi Thank you for approving. I still need to fix a problem with the unit tests on .NET 6. Attempting to run them stops with the following error.
Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
Testhost process exited with error: Error:
  An assembly specified in the application dependencies manifest (Serilog.Sinks.MSSqlServer.Tests.deps.json) was not found:
    package: 'Azure.Core', version: '1.6.0'
    path: 'lib/netstandard2.0/Azure.Core.dll'
. Please check the diagnostic logs for more information.

Under investigation. ;)


First take on reflow

Not sure why this never got merged. 😞
Docs have move to rancher/elemental-docs and have a different structure meanwhile.


Partial Mode: IntelliSense not available for Typescript

Does this issue occur when all extensions are disabled? Yes

VS Code Version: 1.94.2, commit 384ff7382de
OS Version: Windows 22H2, WSL2 Ubuntu 22.04.5 LTS

I have the project open inside WSL in VSCode.
Steps to reproduce

Clone this project, which is a vscode extension under development.
Run npm install --save-dev
Go to extension.ts. Write vscode.window. and don't get nice IntelliSense.
In the status bar, TypeScript shows: Partial Mode — Project Wide IntelliSense not available.
The output from TypeScript is the same as in issue microsoft/vscode#191441 but without the last line

TSServer exited. Code: null. Signal: SIGTERM

When I manually restart the TSServer, I also get this line.
What I tried to fix this

Reload without extensions -> same problem.

Run npm clean-install and npm cache verify. Also manually deleted node_modules/ folder and ran npm install --save-dev again.

Check that built-in TypeScript/JavaScript is not disabled as described in issue microsoft/vscode#179589.

TypeScript Log. I added "typescript.tsserver.log": "verbose" to my settings.json, then visited the TypeScript file again. The log is as follows:

See full TypeScript log
Info 0    [17:52:28.235] Starting TS Server
Info 1    [17:52:28.237] Version: 5.6.3
Info 2    [17:52:28.237] Arguments: C:\Users\domin\AppData\Local\Programs\Microsoft VS Code\Code.exe c:\Users\domin\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\lib\tsserver.js --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName C:\Users\domin\AppData\Local\Temp\vscode-typescript\9dd41fe1d00c6981b53f\tscancellation-acc4ebec8c3b9042e090.tmp* --logVerbosity verbose --logFile c:\Users\domin\AppData\Roaming\Code\logs\20241022T174555\window2\exthost\vscode.typescript-language-features\tsserver-log-7sMOR4\tsserver.log --locale en --noGetErrOnBackgroundUpdate --canUseWatchEvents --validateDefaultNpmLocation --useNodeIpc
Info 3    [17:52:28.237] Platform: win32 NodeVersion: v20.16.0 CaseSensitive: false
Info 4    [17:52:28.237] ServerMode: undefined hasUnknownServerMode: undefined
Info 5    [17:52:28.245] Binding...
Info 6    [17:52:28.265] request:
    {
      "seq": 0,
      "type": "request",
      "command": "configure",
      "arguments": {
        "hostInfo": "vscode",
        "preferences": {
          "providePrefixAndSuffixTextForRename": true,
          "allowRenameOfImportPath": true,
          "includePackageJsonAutoImports": "auto",
          "excludeLibrarySymbolsInNavTo": true
        },
        "watchOptions": {}
      }
    }
Info 7    [17:52:28.265] Host information vscode
Info 8    [17:52:28.266] Host watch options changed to undefined, it will be take effect for next watches.
Info 9    [17:52:28.266] response:
    {"seq":0,"type":"response","command":"configure","request_seq":0,"success":true}
Perf 10   [17:52:28.266] 0::configure: async elapsed time (in milliseconds) 1.6583
Info 11   [17:52:28.267] request:
    {
      "seq": 1,
      "type": "request",
      "command": "compilerOptionsForInferredProjects",
      "arguments": {
        "options": {
          "module": "ESNext",
          "moduleResolution": "Bundler",
          "target": "ES2022",
          "jsx": "react",
          "allowImportingTsExtensions": true,
          "strictNullChecks": true,
          "strictFunctionTypes": true,
          "sourceMap": true,
          "allowJs": true,
          "allowSyntheticDefaultImports": true,
          "allowNonTsExtensions": true,
          "resolveJsonModule": true
        }
      }
    }
Perf 12   [17:52:28.267] 1::compilerOptionsForInferredProjects: elapsed time (in milliseconds) 0.4578
Info 13   [17:52:28.267] response:
    {"seq":0,"type":"response","command":"compilerOptionsForInferredProjects","request_seq":1,"success":true,"body":true}
Info 14   [17:52:28.267] request:
    {
      "seq": 2,
      "type": "request",
      "command": "updateOpen",
      "arguments": {
        "changedFiles": [],
        "closedFiles": [],
        "openFiles": [
          {
            "file": "^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts",
            "fileContent": "import * as vscode from 'vscode';\nimport { window } from 'vscode';\n\nconst PREVIEW_COMMAND = `\\x0C checkpoint_paste()`; // \\x0C is Ctrl + L\n\n/**\n * Whether the extension is currently executing a Manim command.\n * \n * Note that this is not capturing whether the `checkpoint_paste()` command is\n * still running. Instead, it only captures whether reading/writing to clipboard\n * is currently happening to prevent unpredictable behavior.\n * \n * We don't need to capture the state of `checkpoint_paste()` because users\n * might actually want to preview a cell (or another one) again from the start\n * even though the animation is still running. With the new VSCode terminal\n * shell integration, it will automatically send a `Ctrl + C` to the terminal\n * when a new command is sent, so the previous command will be interrupted.\n */\nlet isExecuting = false;\n\n/**\n * Interactively previews the given Manim code by means of the\n * `checkpoint_paste()` method from Manim.\n * \n * This workflow is described in [1] and was adapted from Sublime to VSCode by\n * means of this extension. The main features are discussed in [2]. A demo\n * is shown in the video \"How I animate 3Blue1Brown\" by Grant Sanderson [3],\n * with the workflow being showcased between 3:32 and 6:48.\n * \n * [1] https://github.com/3b1b/videos#workflow\n * [2] https://github.com/ManimCommunity/manim/discussions/3954#discussioncomment-10933720\n * [3] https://youtu.be/rbu7Zu5X1zI\n *\n * @param code The code to preview (e.g. from a Manim cell or from a custom selection).\n */\nexport async function previewCode(code: string): Promise<void> {\n    if (isExecuting) {\n        vscode.window.showInformationMessage('Please wait a few seconds, then try again.');\n        return;\n    }\n    isExecuting = true;\n\n    try {\n        const clipboardBuffer = await vscode.env.clipboard.readText();\n        await vscode.env.clipboard.writeText(code);\n\n        // Send command to interactive IPython shell\n        // See the new Terminal shell integration API (from VSCode release 1.93)\n        // https://code.visualstudio.com/updates/v1_93#_terminal-shell-integration-api\n        const terminal = vscode.window.activeTerminal || vscode.window.createTerminal();\n        if (terminal.shellIntegration) {\n            terminal.shellIntegration.executeCommand(PREVIEW_COMMAND);\n        } else {\n            terminal.sendText(PREVIEW_COMMAND);\n        }\n\n        // Restore original clipboard content\n        const timeout = vscode.workspace.getConfiguration(\"vscode-manim\").clipboardTimeout;\n        setTimeout(async () => {\n            await vscode.env.clipboard.writeText(clipboardBuffer);\n        }, timeout);\n    } catch (error) {\n        vscode.window.showErrorMessage(`Error: ${error}`);\n    } finally {\n        isExecuting = false;\n    }\n}\n",
            "scriptKindName": "TS"
          }
        ]
      }
    }
Info 15   [17:52:28.269] getConfigFileNameForFile:: File: ^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts ProjectRootPath: undefined:: Result: undefined
Info 16   [17:52:28.274] Starting updateGraphWorker: Project: /dev/null/inferredProject1*
Info 17   [17:52:28.321] DirectoryWatcher:: Added:: WatchInfo: c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules 1 undefined WatchType: node_modules for closed script infos and package.jsons affecting module specifier cache
Info 18   [17:52:28.322] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":1,"path":"c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules","recursive":true}}
Info 19   [17:52:28.322] Elapsed:: 0.6050999999999931ms DirectoryWatcher:: Added:: WatchInfo: c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules 1 undefined WatchType: node_modules for closed script infos and package.jsons affecting module specifier cache
Info 20   [17:52:28.329] DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs/Microsoft VS Code/node_modules 1 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 21   [17:52:28.329] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":2,"path":"C:/Users/domin/AppData/Local/Programs/Microsoft VS Code/node_modules","recursive":true}}
Info 22   [17:52:28.329] Elapsed:: 0.13769999999999527ms DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs/Microsoft VS Code/node_modules 1 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 23   [17:52:28.331] DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs/node_modules 1 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 24   [17:52:28.331] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":3,"path":"C:/Users/domin/AppData/Local/Programs/node_modules","recursive":true}}
Info 25   [17:52:28.331] Elapsed:: 0.15390000000002146ms DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs/node_modules 1 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 26   [17:52:28.332] DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/node_modules 1 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 27   [17:52:28.332] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":4,"path":"C:/Users/domin/AppData/Local/node_modules","recursive":true}}
Info 28   [17:52:28.333] Elapsed:: 0.14949999999998909ms DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/node_modules 1 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 29   [17:52:28.334] DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/node_modules 1 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 30   [17:52:28.334] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":5,"path":"C:/Users/domin/AppData/node_modules","recursive":true}}
Info 31   [17:52:28.334] Elapsed:: 0.26699999999993906ms DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/node_modules 1 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 32   [17:52:28.990] DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs/Microsoft VS Code/^ 1 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 33   [17:52:28.990] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":6,"path":"C:/Users/domin/AppData/Local/Programs/Microsoft VS Code/^","recursive":true,"ignoreUpdate":true}}
Info 34   [17:52:28.991] Elapsed:: 0.14400000000000546ms DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs/Microsoft VS Code/^ 1 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 35   [17:52:28.991] DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs 0 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 36   [17:52:28.991] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":7,"path":"C:/Users/domin/AppData/Local/Programs","recursive":false,"ignoreUpdate":true}}
Info 37   [17:52:28.991] Elapsed:: 0.08600000000001273ms DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs 0 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 38   [17:52:28.991] DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local 0 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 39   [17:52:28.991] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":8,"path":"C:/Users/domin/AppData/Local","recursive":false,"ignoreUpdate":true}}
Info 40   [17:52:28.991] Elapsed:: 0.06970000000001164ms DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local 0 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 41   [17:52:28.991] DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData 0 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 42   [17:52:28.991] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":9,"path":"C:/Users/domin/AppData","recursive":false,"ignoreUpdate":true}}
Info 43   [17:52:28.991] Elapsed:: 0.08690000000001419ms DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData 0 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 44   [17:52:28.999] DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs/Microsoft VS Code 0 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 45   [17:52:28.999] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":10,"path":"C:/Users/domin/AppData/Local/Programs/Microsoft VS Code","recursive":false,"ignoreUpdate":true}}
Info 46   [17:52:28.999] Elapsed:: 0.11110000000007858ms DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs/Microsoft VS Code 0 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
Info 47   [17:52:28.999] FileWatcher:: Added:: WatchInfo: c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/package.json 2000 undefined Project: /dev/null/inferredProject1* WatchType: File location affecting resolution
Info 48   [17:52:28.999] event:
    {"seq":0,"type":"event","event":"createFileWatcher","body":{"id":11,"path":"c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/package.json"}}
Info 49   [17:52:29.000] FileWatcher:: Added:: WatchInfo: C:\Users\domin\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\node_modules\typescript\package.json 2000 undefined Project: /dev/null/inferredProject1* WatchType: File location affecting resolution
Info 50   [17:52:29.000] event:
    {"seq":0,"type":"event","event":"createFileWatcher","body":{"id":12,"path":"C:\\Users\\domin\\AppData\\Local\\Programs\\Microsoft VS Code\\resources\\app\\extensions\\node_modules\\typescript\\package.json"}}
Info 51   [17:52:29.001] DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs/Microsoft VS Code/node_modules/@types 1 undefined Project: /dev/null/inferredProject1* WatchType: Type roots
Info 52   [17:52:29.001] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":13,"path":"C:/Users/domin/AppData/Local/Programs/Microsoft VS Code/node_modules/@types","recursive":true,"ignoreUpdate":true}}
Info 53   [17:52:29.001] Elapsed:: 0.05749999999989086ms DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs/Microsoft VS Code/node_modules/@types 1 undefined Project: /dev/null/inferredProject1* WatchType: Type roots
Info 54   [17:52:29.001] DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs/node_modules/@types 1 undefined Project: /dev/null/inferredProject1* WatchType: Type roots
Info 55   [17:52:29.001] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":14,"path":"C:/Users/domin/AppData/Local/Programs/node_modules/@types","recursive":true,"ignoreUpdate":true}}
Info 56   [17:52:29.001] Elapsed:: 0.04039999999986321ms DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/Programs/node_modules/@types 1 undefined Project: /dev/null/inferredProject1* WatchType: Type roots
Info 57   [17:52:29.001] DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/node_modules/@types 1 undefined Project: /dev/null/inferredProject1* WatchType: Type roots
Info 58   [17:52:29.001] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":15,"path":"C:/Users/domin/AppData/Local/node_modules/@types","recursive":true,"ignoreUpdate":true}}
Info 59   [17:52:29.001] Elapsed:: 0.040199999999913416ms DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/Local/node_modules/@types 1 undefined Project: /dev/null/inferredProject1* WatchType: Type roots
Info 60   [17:52:29.001] DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/node_modules/@types 1 undefined Project: /dev/null/inferredProject1* WatchType: Type roots
Info 61   [17:52:29.001] event:
    {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":16,"path":"C:/Users/domin/AppData/node_modules/@types","recursive":true,"ignoreUpdate":true}}
Info 62   [17:52:29.001] Elapsed:: 0.03099999999994907ms DirectoryWatcher:: Added:: WatchInfo: C:/Users/domin/AppData/node_modules/@types 1 undefined Project: /dev/null/inferredProject1* WatchType: Type roots
Info 63   [17:52:29.001] Finishing updateGraphWorker: Project: /dev/null/inferredProject1* projectStateVersion: 1 projectProgramVersion: 0 structureChanged: true structureIsReused:: Not Elapsed:<PHONE_NUMBER>000001ms
Info 64   [17:52:29.001] Project '/dev/null/inferredProject1*' (Inferred)
Info 65   [17:52:29.005] 	Files (64)
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es5.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2015.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2016.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2017.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2018.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2019.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2020.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2021.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2022.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.dom.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.dom.iterable.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.dom.asynciterable.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.webworker.importscripts.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.scripthost.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2015.core.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2015.collection.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2015.generator.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2015.iterable.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2015.promise.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2015.proxy.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2015.reflect.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2015.symbol.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2015.symbol.wellknown.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2016.array.include.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2016.intl.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2017.date.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2017.object.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2017.sharedmemory.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2017.string.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2017.intl.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2017.typedarrays.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2018.asyncgenerator.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2018.asynciterable.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2018.intl.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2018.promise.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2018.regexp.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2019.array.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2019.object.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2019.string.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2019.symbol.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2019.intl.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2020.bigint.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2020.date.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2020.promise.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2020.sharedmemory.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2020.string.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2020.symbol.wellknown.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2020.intl.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2020.number.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2021.promise.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2021.string.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2021.weakref.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2021.intl.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2022.array.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2022.error.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2022.intl.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2022.object.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2022.sharedmemory.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2022.string.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2022.regexp.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.decorators.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.decorators.legacy.d.ts
	c:/Users/domin/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/node_modules/typescript/lib/lib.es2022.full.d.ts
	^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts

	resources/app/extensions/node_modules/typescript/lib/lib.es5.d.ts
	  Library referenced via 'es5' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2015.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2015.d.ts
	  Library referenced via 'es2015' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2016.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2016.d.ts
	  Library referenced via 'es2016' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2017.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2017.d.ts
	  Library referenced via 'es2017' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2018.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2018.d.ts
	  Library referenced via 'es2018' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2019.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2019.d.ts
	  Library referenced via 'es2019' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2020.d.ts
	  Library referenced via 'es2020' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2021.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2021.d.ts
	  Library referenced via 'es2021' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2022.d.ts
	  Library referenced via 'es2022' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.full.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.dom.d.ts
	  Library referenced via 'dom' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.full.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.dom.iterable.d.ts
	  Library referenced via 'dom.iterable' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.full.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.dom.asynciterable.d.ts
	  Library referenced via 'dom.asynciterable' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.full.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.webworker.importscripts.d.ts
	  Library referenced via 'webworker.importscripts' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.full.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.scripthost.d.ts
	  Library referenced via 'scripthost' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.full.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2015.core.d.ts
	  Library referenced via 'es2015.core' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2015.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2015.collection.d.ts
	  Library referenced via 'es2015.collection' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2015.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2015.generator.d.ts
	  Library referenced via 'es2015.generator' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2015.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2015.iterable.d.ts
	  Library referenced via 'es2015.iterable' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2015.d.ts'
	  Library referenced via 'es2015.iterable' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2015.generator.d.ts'
	  Library referenced via 'es2015.iterable' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2018.asynciterable.d.ts'
	  Library referenced via 'es2015.iterable' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2019.object.d.ts'
	  Library referenced via 'es2015.iterable' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.symbol.wellknown.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2015.promise.d.ts
	  Library referenced via 'es2015.promise' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2015.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2015.proxy.d.ts
	  Library referenced via 'es2015.proxy' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2015.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2015.reflect.d.ts
	  Library referenced via 'es2015.reflect' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2015.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2015.symbol.d.ts
	  Library referenced via 'es2015.symbol' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2015.iterable.d.ts'
	  Library referenced via 'es2015.symbol' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2015.d.ts'
	  Library referenced via 'es2015.symbol' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2015.symbol.wellknown.d.ts'
	  Library referenced via 'es2015.symbol' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2017.sharedmemory.d.ts'
	  Library referenced via 'es2015.symbol' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2018.asynciterable.d.ts'
	  Library referenced via 'es2015.symbol' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.symbol.wellknown.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2015.symbol.wellknown.d.ts
	  Library referenced via 'es2015.symbol.wellknown' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2015.d.ts'
	  Library referenced via 'es2015.symbol.wellknown' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2017.sharedmemory.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2016.array.include.d.ts
	  Library referenced via 'es2016.array.include' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2016.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2016.intl.d.ts
	  Library referenced via 'es2016.intl' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2016.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2017.date.d.ts
	  Library referenced via 'es2017.date' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2017.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2017.object.d.ts
	  Library referenced via 'es2017.object' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2017.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2017.sharedmemory.d.ts
	  Library referenced via 'es2017.sharedmemory' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2017.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2017.string.d.ts
	  Library referenced via 'es2017.string' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2017.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2017.intl.d.ts
	  Library referenced via 'es2017.intl' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2017.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2017.typedarrays.d.ts
	  Library referenced via 'es2017.typedarrays' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2017.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2018.asyncgenerator.d.ts
	  Library referenced via 'es2018.asyncgenerator' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2018.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2018.asynciterable.d.ts
	  Library referenced via 'es2018.asynciterable' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2018.d.ts'
	  Library referenced via 'es2018.asynciterable' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2018.asyncgenerator.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2018.intl.d.ts
	  Library referenced via 'es2018.intl' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2018.d.ts'
	  Library referenced via 'es2018.intl' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.intl.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2018.promise.d.ts
	  Library referenced via 'es2018.promise' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2018.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2018.regexp.d.ts
	  Library referenced via 'es2018.regexp' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2018.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2019.array.d.ts
	  Library referenced via 'es2019.array' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2019.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2019.object.d.ts
	  Library referenced via 'es2019.object' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2019.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2019.string.d.ts
	  Library referenced via 'es2019.string' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2019.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2019.symbol.d.ts
	  Library referenced via 'es2019.symbol' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2019.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2019.intl.d.ts
	  Library referenced via 'es2019.intl' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2019.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2020.bigint.d.ts
	  Library referenced via 'es2020.bigint' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2020.date.d.ts
	  Library referenced via 'es2020.date' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2020.promise.d.ts
	  Library referenced via 'es2020.promise' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2020.sharedmemory.d.ts
	  Library referenced via 'es2020.sharedmemory' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2020.string.d.ts
	  Library referenced via 'es2020.string' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2020.symbol.wellknown.d.ts
	  Library referenced via 'es2020.symbol.wellknown' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.string.d.ts'
	  Library referenced via 'es2020.symbol.wellknown' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2020.intl.d.ts
	  Library referenced via 'es2020.intl' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.bigint.d.ts'
	  Library referenced via 'es2020.intl' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.date.d.ts'
	  Library referenced via 'es2020.intl' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.number.d.ts'
	  Library referenced via 'es2020.intl' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2020.number.d.ts
	  Library referenced via 'es2020.number' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2020.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2021.promise.d.ts
	  Library referenced via 'es2021.promise' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2021.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2021.string.d.ts
	  Library referenced via 'es2021.string' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2021.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2021.weakref.d.ts
	  Library referenced via 'es2021.weakref' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2021.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2021.intl.d.ts
	  Library referenced via 'es2021.intl' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2021.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2022.array.d.ts
	  Library referenced via 'es2022.array' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2022.error.d.ts
	  Library referenced via 'es2022.error' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2022.intl.d.ts
	  Library referenced via 'es2022.intl' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2022.object.d.ts
	  Library referenced via 'es2022.object' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2022.sharedmemory.d.ts
	  Library referenced via 'es2022.sharedmemory' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2022.string.d.ts
	  Library referenced via 'es2022.string' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2022.regexp.d.ts
	  Library referenced via 'es2022.regexp' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es2022.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.decorators.d.ts
	  Library referenced via 'decorators' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es5.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.decorators.legacy.d.ts
	  Library referenced via 'decorators.legacy' from file 'resources/app/extensions/node_modules/typescript/lib/lib.es5.d.ts'
	resources/app/extensions/node_modules/typescript/lib/lib.es2022.full.d.ts
	  Default library for target 'es2022'
	^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts
	  Root file specified for compilation

Info 66   [17:52:29.005] -----------------------------------------------
Info 67   [17:52:29.008] Project '/dev/null/inferredProject1*' (Inferred)
Info 67   [17:52:29.008] 	Files (64)

Info 67   [17:52:29.008] -----------------------------------------------
Info 67   [17:52:29.008] Open files:
Info 67   [17:52:29.008] 	FileName: ^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts ProjectRootPath: undefined
Info 67   [17:52:29.008] 		Projects: /dev/null/inferredProject1*
Perf 67   [17:52:29.008] 2::updateOpen: elapsed time (in milliseconds) 740.6395
Info 68   [17:52:29.008] response:
    {"seq":0,"type":"response","command":"updateOpen","request_seq":2,"success":true,"performanceData":{"updateGraphDurationMs":727.0486000000001},"body":true}
Info 69   [17:52:29.008] event:
    {"seq":0,"type":"event","event":"typingsInstallerPid","body":{"pid":7012}}
Info 70   [17:52:29.009] request:
    {
      "seq": 4,
      "type": "request",
      "command": "configure",
      "arguments": {
        "file": "^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts",
        "formatOptions": {
          "tabSize": 4,
          "indentSize": 4,
          "convertTabsToSpaces": true,
          "newLineCharacter": "\n",
          "insertSpaceAfterCommaDelimiter": true,
          "insertSpaceAfterConstructor": false,
          "insertSpaceAfterSemicolonInForStatements": true,
          "insertSpaceBeforeAndAfterBinaryOperators": true,
          "insertSpaceAfterKeywordsInControlFlowStatements": true,
          "insertSpaceAfterFunctionKeywordForAnonymousFunctions": true,
          "insertSpaceBeforeFunctionParenthesis": false,
          "insertSpaceAfterOpeningAndBeforeClosingNonemptyParenthesis": false,
          "insertSpaceAfterOpeningAndBeforeClosingNonemptyBrackets": false,
          "insertSpaceAfterOpeningAndBeforeClosingNonemptyBraces": true,
          "insertSpaceAfterOpeningAndBeforeClosingEmptyBraces": true,
          "insertSpaceAfterOpeningAndBeforeClosingTemplateStringBraces": false,
          "insertSpaceAfterOpeningAndBeforeClosingJsxExpressionBraces": false,
          "insertSpaceAfterTypeAssertion": false,
          "placeOpenBraceOnNewLineForFunctions": false,
          "placeOpenBraceOnNewLineForControlBlocks": false,
          "semicolons": "ignore",
          "indentSwitchCase": true
        },
        "preferences": {
          "quotePreference": "auto",
          "importModuleSpecifierEnding": "auto",
          "jsxAttributeCompletionStyle": "auto",
          "allowTextChangesInNewFiles": false,
          "providePrefixAndSuffixTextForRename": true,
          "allowRenameOfImportPath": true,
          "includeAutomaticOptionalChainCompletions": true,
          "provideRefactorNotApplicableReason": true,
          "generateReturnInDocTemplate": true,
          "includeCompletionsForImportStatements": true,
          "includeCompletionsWithSnippetText": true,
          "includeCompletionsWithClassMemberSnippets": true,
          "includeCompletionsWithObjectLiteralMethodSnippets": true,
          "autoImportFileExcludePatterns": [],
          "autoImportSpecifierExcludeRegexes": [],
          "preferTypeOnlyAutoImports": false,
          "useLabelDetailsInCompletionEntries": true,
          "allowIncompleteCompletions": true,
          "displayPartsForJSDoc": true,
          "disableLineTextInReferences": true,
          "interactiveInlayHints": true,
          "includeCompletionsForModuleExports": true,
          "includeInlayParameterNameHints": "none",
          "includeInlayParameterNameHintsWhenArgumentMatchesName": false,
          "includeInlayFunctionParameterTypeHints": false,
          "includeInlayVariableTypeHints": false,
          "includeInlayVariableTypeHintsWhenTypeMatchesName": false,
          "includeInlayPropertyDeclarationTypeHints": false,
          "includeInlayFunctionLikeReturnTypeHints": false,
          "includeInlayEnumMemberValueHints": false
        }
      }
    }
Info 71   [17:52:29.009] Host configuration update for file ^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts
Info 72   [17:52:29.009] response:
    {"seq":0,"type":"response","command":"configure","request_seq":4,"success":true}
Perf 73   [17:52:29.009] 4::configure: async elapsed time (in milliseconds) 0.3030
Info 74   [17:52:29.009] request:
    {
      "seq": 5,
      "type": "request",
      "command": "geterr",
      "arguments": {
        "delay": 0,
        "files": [
          {
            "file": "^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts",
            "ranges": [
              {
                "startLine": 1,
                "startOffset": 1,
                "endLine": 21,
                "endOffset": 4
              }
            ]
          }
        ]
      }
    }
Perf 75   [17:52:29.010] 5::geterr: async elapsed time (in milliseconds) 0.7549
Info 76   [17:52:29.022] event:
    {"seq":0,"type":"event","event":"syntaxDiag","body":{"file":"^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts","diagnostics":[]}}
Info 77   [17:52:29.053] event:
    {"seq":0,"type":"event","event":"semanticDiag","body":{"file":"^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts","diagnostics":[{"start":{"line":1,"offset":25},"end":{"line":1,"offset":33},"text":"Cannot find module 'vscode' or its corresponding type declarations.","code":2307,"category":"error"},{"start":{"line":2,"offset":24},"end":{"line":2,"offset":32},"text":"Cannot find module 'vscode' or its corresponding type declarations.","code":2307,"category":"error"}]}}
Info 78   [17:52:29.055] event:
    {"seq":0,"type":"event","event":"suggestionDiag","body":{"file":"^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts","diagnostics":[{"start":{"line":2,"offset":1},"end":{"line":2,"offset":33},"text":"'window' is declared but its value is never read.","code":6133,"category":"suggestion","reportsUnnecessary":true}]}}
Info 79   [17:52:29.055] event:
    {"seq":0,"type":"event","event":"requestCompleted","body":{"request_seq":5,"performanceData":{"diagnosticsDuration":[{"syntaxDiag":0.29919999999992797,"semanticDiag":29.1579999999999,"suggestionDiag":1.6519000000000688,"file":"^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts"}]}}}
Info 80   [17:52:31.442] request:
    {
      "seq": 6,
      "type": "request",
      "command": "definitionAndBoundSpan",
      "arguments": {
        "file": "^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts",
        "line": 22,
        "offset": 52
      }
    }
Perf 81   [17:52:31.444] 6::definitionAndBoundSpan: elapsed time (in milliseconds) 2.2628
Info 82   [17:52:31.444] response:
    {"seq":0,"type":"response","command":"definitionAndBoundSpan","request_seq":6,"success":true,"body":{"definitions":[]}}
Info 83   [17:52:32.732] request:
    {
      "seq": 7,
      "type": "request",
      "command": "documentHighlights",
      "arguments": {
        "file": "^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts",
        "line": 17,
        "offset": 50,
        "filesToSearch": [
          "^/vscode-remote/wsl+ubuntu/home/dominic/dev/vscode-manim/src/previewCode.ts"
        ]
      }
    }
Perf 84   [17:52:32.733] 7::documentHighlights: elapsed time (in milliseconds) 1.0080
Info 85   [17:52:32.733] response:
    {"seq":0,"type":"response","command":"documentHighlights","request_seq":7,"success":true,"body":[]}
[tsserver - Copy.log](https://github.com/user-attachments/files/17479293/tsserver.-.Copy.log)

Note that it probably cannot provide me IntelliSense due to
Cannot find module 'vscode' or its corresponding type declarations.

I'm also wondering about the Arguments:  line at the beginning of the log where it points to a tsserver.js in my app data (where VSCode is installed), and not inside WSL. But that might not mean anything since VSCode might load the server from anywhere.

I've also tried on a second machine (Windows 11 Version 23H2, WSL2 with Ubuntu 24.04.1 LTS) and there it's the same problem for the linked project.


Crash With Logistical Sorters and Personal Chests

In Mekanism 9.0.1, if you attach a Logistical Sorter to a Personal Chest, and also have a Logistical Transporter attached to the sorter, the game will crash as soon as you apply a filter.  It does not seem to happen if the sorter is attached to the bottom of the chest however.  Attaching an example crash log.
https://gist.github.com/Kaltazar/6225843136773f507e00d3b2ea6109b6

I believe this was fixed on the dev branch. you either have to wait for the release branch or build the dev branch yourself.

Yeah, fixed :)


Best way to pass custom parameters to a dzi tile source?

Let's say this is my tile source:
const tileSource = new OpenSeadragon.DziTileSource({
  width: 19200,
  height: 19200,
  tileSize: 1023,
  tileOverlap: 1,
  tilesUrl: "http://localhost:4000/dzi_test/",
  fileFormat: "jpeg"
});

How would I go about passing custom args to the server, like "brightness" or "channels", etc.?
Would I be able to attach custom args to every request (i.e. http://localhost:4000/dzi_test/12/1_0.jpeg?brightness=4&channels=blu,grn)
Alternatively, is there a way to pass custom headers with the request?
I realize there are many ways I could do this including using a custom tile source, but I am looking for the ideal/best way to accomplish this.
Thank you!

Forget it. I just discovered that any args passed to the .dzi file will automatically be passed to the tile image requests. Easy. Great feature!
So, tileSource = "http://localhost:4000/dzi_test/test.dzi?foo=bar" will request images like http://localhost:4000/dzi_test/test_files/...jpg?foo=bar
That's exactly what I need for this.

Excellent :)

🤘

Forget it. I just discovered that any args passed to the .dzi file will automatically be passed to the tile image requests. Easy. Great feature!
So, tileSource = "http://localhost:4000/dzi_test/test.dzi?foo=bar" will request images like http://localhost:4000/dzi_test/test_files/...jpg?foo=bar
That's exactly what I need for this.

I found change the parameters after initialization, this solution won’t work

I found change the parameters after initialization, this solution won’t work

I'm not sure what you mean by this. Can you give an example, or explain more fully?

sorry for that.
I mean that it's work not fine if I'll changed tileSource = "http://localhost:4000/dzi_test/test.dzi?foo=bar" to xxxi?foo=bar1
but, I found a way to change it
  changeMode(mode: string) {
    const url = (this.viewer as any).tileSources;
    const bounds = this.viewer.viewport.getBounds();

    this.viewer.close();
    (this.viewer as any).open(url);
    setTimeout(() => { // waiting for viewer opend
      (this.viewer as any).source.queryParams = [`?mode=${mode}`];
      this.viewer.viewport.fitBounds(bounds, true);
    }, 500);
  }


First pass at website front page accessibility

First pass at trying to improve the accessiblity of the homepage. Used a few different auditing tools and the voiceover tool in safari.
This one might warrant actual review as it includes alt text copy that I made up.
One thing that could be improved according to the auditing tools is the contrast on some of the text, like the blue on blue of the announcements bar, but I thought it must have already been encountered/resolved in the design phase so I left it for now.

Will update the copy in my next PR since this already landed


Hashcash intermittenly produces invalid proof of work error

Describe the bug
Valid proof of works generated by hashcash are reported as invalid
To Reproduce
resource = "01FNEEYJJMH1940N0X64THA51V"
1000.times do
  pow = Hashcash.generate(resource)
  Hashcash.valid?(pow, resource) || abort("Bug in `hashcash`")
end

Expected behavior
A generated hashcash stamp should be valid within the specified time window.

Arithmetic overflow (OverflowError)
         from src/hashcash/stamp.cr:21:16 in 'update_counter'
         from src/hashcash.cr:24:5 in 'generate'
         from src/hashcash.cr:16:3 in 'generate'
         from spec/hashcash_spec.cr:42:7 in '->'
         from /home/mia/.asdf/installs/crystal/1.3.2/share/crystal/src/primitives.cr:266:3 in 'internal_run'
         from /home/mia/.asdf/installs/crystal/1.3.2/share/crystal/src/spec/example.cr:33:16 in 'run'
         from /home/mia/.asdf/installs/crystal/1.3.2/share/crystal/src/spec/context.cr:18:23 in 'internal_run'
         from /home/mia/.asdf/installs/crystal/1.3.2/share/crystal/src/spec/context.cr:339:7 in 'run'
         from /home/mia/.asdf/installs/crystal/1.3.2/share/crystal/src/spec/context.cr:18:23 in 'internal_run'
         from /home/mia/.asdf/installs/crystal/1.3.2/share/crystal/src/spec/context.cr:156:7 in 'run'
         from /home/mia/.asdf/installs/crystal/1.3.2/share/crystal/src/spec/dsl.cr:220:7 in '->'
         from /home/mia/.asdf/installs/crystal/1.3.2/share/crystal/src/primitives.cr:266:3 in 'run'
         from /home/mia/.asdf/installs/crystal/1.3.2/share/crystal/src/crystal/main.cr:50:5 in 'exit'
         from /home/mia/.asdf/installs/crystal/1.3.2/share/crystal/src/crystal/main.cr:45:5 in 'main'
         from /home/mia/.asdf/installs/crystal/1.3.2/share/crystal/src/crystal/main.cr:127:3 in 'main'
         from /lib/x86_64-linux-gnu/libc.so.6 in '__libc_start_main'
         from /home/mia/.cache/crystal/crystal-run-spec.tmp in '_start'
         from ???

# src/hashcash/stamp.cr:21
def update_counter
  until check(Digest::SHA1.digest(self.to_s), bits)
    @counter += 1
  end
end

# src/hashcash/stamp.cr:21
def initialize(
  ...
  @counter : Int32 = rand(Int32::MAX)
)
end

@caspiano
Either of these will fix the problem (or make it much less likely to occur).
@counter : Int64 = rand(Int32::MAX).to_i64

or
@counter : Int32 = rand(Int32::MAX // 2)

Alternativly some kind of handling of the counter overflowing might be better, but I don't know what would be the correct way of handling it for hashcash.


Fixed failed Manifest Validation

Q
A

Bug fix?
yes

New feature?
no

New sample?
no

Related issues?
no

What's in this Pull Request?
Manifest Validation failed, fixed that by updating the validator engine in office-addin-manifest
Guidance
No additional guidance, to repro the issue run
npm run validate
before and after the change

@aafvstam looks great! Thanks!


Roll Engine from 9ce1e5c5c7e7 to 29d31f6e507c (60 revisions)

Roll Engine from 9ce1e5c5c7e7 to 29d31f6e507c (60 revisions)
https://github.com/flutter/engine/compare/9ce1e5c5c7e7...29d31f6e507c
2020-05-22<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from Kvwlr... to DzG49... (flutter/engine#18580)
2020-05-22<EMAIL_ADDRESS>Roll Skia from 80abb89c3632 to ec31488ace66 (1 revision) (flutter/engine#18579)
2020-05-22<EMAIL_ADDRESS>Roll Skia from da90c3765908 to 80abb89c3632 (4 revisions) (flutter/engine#18577)
2020-05-22<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from zNmv... to 99Z4... (flutter/engine#18576)
2020-05-22<EMAIL_ADDRESS>Roll Skia from 317dce5c81c0 to da90c3765908 (1 revision) (flutter/engine#18575)
2020-05-22<EMAIL_ADDRESS>Roll Dart SDK from 4ee57c08e0a6 to 65113fd73dec (3 revisions) (flutter/engine#18574)
2020-05-22<EMAIL_ADDRESS>Roll Skia from 67e21a19259b to 317dce5c81c0 (3 revisions) (flutter/engine#18573)
2020-05-22<EMAIL_ADDRESS>Update CanvasKit to 0.15.0 (flutter/engine#18570)
2020-05-21<EMAIL_ADDRESS>Roll Skia from 3d52abc84667 to 67e21a19259b (1 revision) (flutter/engine#18568)
2020-05-21<EMAIL_ADDRESS>Roll Dart SDK from 396b5fb7a97d to 4ee57c08e0a6 (6 revisions) (flutter/engine#18567)
2020-05-21<EMAIL_ADDRESS>Add fl_value_to_string (flutter/engine#18540)
2020-05-21<EMAIL_ADDRESS>Roll Skia from 1e63279156d6 to 3d52abc84667 (5 revisions) (flutter/engine#18566)
2020-05-21<EMAIL_ADDRESS>null-annotate semantics.dart (flutter/engine#18553)
2020-05-21<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from ciqRH... to Kvwlr... (flutter/engine#18565)
2020-05-21<EMAIL_ADDRESS>Roll Skia from b37105ea6cca to 1e63279156d6 (9 revisions) (flutter/engine#18564)
2020-05-21<EMAIL_ADDRESS>Implement WriteAtomically using write/fsync on all platforms, and enable (flutter/engine#18320)
2020-05-21<EMAIL_ADDRESS>Roll Dart SDK from ecce58c1e354 to 396b5fb7a97d (2 revisions) (flutter/engine#18560)
2020-05-21<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from RNByJ... to _zNmv... (flutter/engine#18558)
2020-05-21<EMAIL_ADDRESS>[profiling] Memory Profiling support for iOS (flutter/engine#18516)
2020-05-21<EMAIL_ADDRESS>Roll Skia from 22636205ce92 to b37105ea6cca (2 revisions) (flutter/engine#18557)
2020-05-21<EMAIL_ADDRESS>Roll Dart SDK from d551980ac9fc to ecce58c1e354 (2 revisions) (flutter/engine#18556)
2020-05-21<EMAIL_ADDRESS>Roll Dart SDK from bf7e9d13d730 to d551980ac9fc (6 revisions) (flutter/engine#18551)
2020-05-21<EMAIL_ADDRESS>Roll Skia from 4c0578632217 to 22636205ce92 (4 revisions) (flutter/engine#18550)
2020-05-21<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from ThMeW... to ciqRH... (flutter/engine#18549)
2020-05-21<EMAIL_ADDRESS>Roll Skia from 67ff541ac116 to 4c0578632217 (1 revision) (flutter/engine#18547)
2020-05-21<EMAIL_ADDRESS>Let run_tests.py just stream output (flutter/engine#18534)
2020-05-21<EMAIL_ADDRESS>Add FlKeyEventPlugin (flutter/engine#18313)
2020-05-21<EMAIL_ADDRESS>Add tests for StandardMethodCodec (flutter/engine#18521)
2020-05-21<EMAIL_ADDRESS>Roll Skia from f83baf230c69 to 67ff541ac116 (1 revision) (flutter/engine#18545)
2020-05-21<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from 3o9aQ... to RNByJ... (flutter/engine#18543)
2020-05-21<EMAIL_ADDRESS>fuchsia: Fix runtime_tests and shell_tests (flutter/engine#18492)
2020-05-21<EMAIL_ADDRESS>Roll Skia from d2dc8ddcdf5e to f83baf230c69 (2 revisions) (flutter/engine#18539)
2020-05-21<EMAIL_ADDRESS>Roll Dart SDK from 7aa8656d1dd8 to bf7e9d13d730 (21 revisions) (flutter/engine#18538)
2020-05-21<EMAIL_ADDRESS>Add FlMethodChannel, FlMethodCodec, FlStandardMethodCodec and FlJsonMethodCodec (flutter/engine#18220)
2020-05-20<EMAIL_ADDRESS>[web] Fix arc rendering when it starts a new sub path. (flutter/engine#18535)
2020-05-20<EMAIL_ADDRESS>Send platformResolvedLocale from iOS embedder (flutter/engine#18519)
2020-05-20<EMAIL_ADDRESS>System mouse cursor: macOS (flutter/engine#18131)
2020-05-20<EMAIL_ADDRESS>Roll Skia from 656ee7bc0fd2 to d2dc8ddcdf5e (2 revisions) (flutter/engine#18537)
2020-05-20<EMAIL_ADDRESS>Make FlBasicMessageChannelResponseHandle a GObject to detect unresponded and double responded messages. (flutter/engine#18514)
2020-05-20<EMAIL_ADDRESS>System mouse cursor: Web (flutter/engine#17718)
2020-05-20<EMAIL_ADDRESS>[web] Reuse ImageElement(s) across frames (flutter/engine#18437)
2020-05-20<EMAIL_ADDRESS>Roll Skia from 3e84312c0f4d to 656ee7bc0fd2 (8 revisions) (flutter/engine#18536)
2020-05-20<EMAIL_ADDRESS>Roll Dart SDK from d2ee73b2513c to 7aa8656d1dd8 (12 revisions) (flutter/engine#18533)
2020-05-20<EMAIL_ADDRESS>Fixes Semantic Object memory leak cause of wrong release call (flutter/engine#18107)
2020-05-20<EMAIL_ADDRESS>Set caches directory on Fuchsia (flutter/engine#18321)
2020-05-20<EMAIL_ADDRESS>[fuchsia] Remove SceneDisplayLag event on Fuchsia (flutter/engine#18515)
...

Commit queue failed; closing this roll.


Average Counter bug with Classic

That fixes the bug with IC2 Classic and the Average counter which would be with classic normaly a TotalConducted Counter.
Note: I did that on the githubpage so missing Imports are there... (2 Classes from Nuclearcontrol)

Try to add
import shedar.mods.ic2.nuclearcontrol.crossmod.ic2classic.IC2ClassicType

somewhere at the top to fix it (it's the only thing you need to import I think).
Lastly, it would be a good idea to turn "IC2NuclearControl.crossClassic.getClassicType() == IC2ClassicType.SPEIGER" into a boolean constant so it doesn't need to check every tick.

You do not need accept the pull request. It was anyway only planed to show how to solve it^^"

Go ahead and finish it off, my git setup for this mod is half broken anyway :P


storage: add mock tests for store struct

fixes #3306

@yichengq I have a few questions for you. The code looks pretty good. Just want to make sure we have the test coverage.

Have passed travis.
storage: coverage: 90.4% of statements
storage/backend: coverage: 85.9% of statements
The most of uncovered part in backend pkg is fatal and panic lines.

LGTM

BTW, I do not trust the line coverage. We need to improve logic coverage instead.

agree. This is also these tests targeting for. will keep improving.


[testing] enable get_queue for /onedal testing without dpctl support

Description
A valid value for queue is None (this is the default value for onedal class methods like 'fit' and 'predict').  Without a value, tests which parameterize via get_queue will be skipped as the list is empty.  This initializes the output with None if cpu is in the filter.  This is currently a silent fail in the sklearnex testing step on public CI (see last main run) where most tests are now skipped.  In some windows cases, only 1 test of 1000 will run without this change.

/intelci: run

/intelci: run

/intelci: run

/intelci: run

/intelci: run

/intelci: run

Nice work here, looks like 1279 skipped in main branch on public 3.11 sklearnex onedal step compared to just 18 with these changes

Is there any functional difference between using no queue and using dpctl CPU queue?

Is there any functional difference between using no queue and using dpctl CPU queue?

Nope! https://github.com/intel/scikit-learn-intelex/blob/main/sklearnex/_device_offload.py#L155 sets it and sends it back.


Broadcasting preview seems to be zoomed

On broadcasting preview screen, everything seems nearer to camera and zoomed in, while streaming this RTMP will display a wider view.
Please help.

I am also facing same issue did you find any solution. Please help me


Force ajax dataType to html

This fixes the "html.replace is not a function" error.
utility.storePageIn requires the 3rd parameter to be a jQuery or a string. But, on line ~452, the ajax success callback caller sometimes passes an XMLDocument object (instead of an HTML string) to the html parameter in the callback. This is passed to ulitity.storePageIn which expects a jQuery or a string.
This change forces the request result to be an HTML string, instead of the default auto-guessing.

Thank you for the contribution @Kalabasa


Change updateref order

When creating a mirrored configuration and using syncrepl and updateref params, the generated LDIF processed by ldapmodify  has the syncrepl change after the updaterefchange. That provokes the following error:
<olcUpdateRef> must appear after syncrepl or updatedn
This just changes the order which seems to solve the problem.
Tested with:
#slapd -V
@(#) $OpenLDAP: slapd  (Jan 16 2016 23:00:08) $
       	root@chimera:/tmp/buildd/openldap-2.4.40+dfsg/debian/build/servers/slapd

Thanks


Add support to manually initialize theme

Gantry admin needs to initialize selected theme in order to set the proper streams to load/save data.
This pull request adds a new function Themes::initTheme() allowing plug-ins to initialize theme manually. It also moves onThemeInitialized event into proper location to prevent theme being unset on the event call.

Looks good to me, merge when ready.


Assignment indentation after one line comment

Changes to fix #4502 issue - proper indentation when there is one-line comment after the =.
Actually #4502 is about two issues - indentation after one-line comment and extra space in the following line.  These two issues seemed to be related but it turned out that they are not.  I still submitted the fix for both in this PR, as each is relatively simple.
Note that although the expected output of #3851 test cases are modified, as discussed in #4502, no config option was added, assuming that the the previous indentation was a bug and not a feature.

Thanks for the PR! I gather that this achieves the goal of resolving the referenced issues, but it's another case where we're just trying to triage symptoms instead of the root cause of the core lhs/rhs utility functions not handling comments well.
A fairly short time ago, we introduced a new utility function rewrite_assign_rhs_with_comments that continues to support the paradigm of the lhs contents inclusively running up to the assignment operator, but actually supporting comments between the assignment operator and the start of the rhs.
The usage of that function was intentionally kept fairly minimal when it was added to keep that PR reasonable, but I think this is a great opportunity to use that "new" function here to address the root cause instead of continuing to battle side effects.
It's a preferable solution both from a code base perspective (encapsulation, reduced duplication) and from a runtime/execution perspective as it avoids first making formatting changes and then having to scan back through our own formatted result to try to figure out what to do next.
Would you be willing to try to implement this approach? I believe it should only require making a few tweaks to the rewrite function for locals to use rewrite_assign_rhs_with_comments instead of whatever rewrite-* and string concat is in there now

Made the change for using rewrite_assign_rhs_with_comments().  Seem to work o.k.
Had to create a span variable with initial value let mut comment_after_assign_span = base_span for the non = case - hope base_span is the right value but should be verified.

Thanks for the updates!


⚠ Adacta-fintech.com has degraded performance

In 7bcb32e, Adacta-fintech.com (https://www.adacta-fintech.com) experienced degraded performance:

HTTP code: 200
Response time: 1081 ms

Resolved: Adacta-fintech.com performance has improved in 79d6b89.


Allow Dispute Kits to unstake ineligible jurors

Problem
For the 1 Human 1 Vote Dispute Kit, it is possible that some large staked jurors might not be registered on Proof of Humanity. In such a case, they would end up being drawn often from the sortition tree but later filtered out. It is highly inefficient and costly.
Proposed solution
Some team members have suggested that KlerosCore should allow a DisputeKit to unstake such ineligible jurors as follow:
https://github.com/kleros/kleros-v2/blob/51ec1d2894560781371fa8ca97e2b5f08311bed3/contracts/src/arbitration/dispute-kits/DisputeKitSybilResistant.sol#L233-L241
https://github.com/kleros/kleros-v2/blob/51ec1d2894560781371fa8ca97e2b5f08311bed3/contracts/src/arbitration/KlerosCore.sol#L481-L487
Analysis
A) If there are 2 Dispute Kits with different eligibility criteria using the same subcourt
Then one Dispute Kit might decide to unstake a juror while this juror is still eligible in the other Dispute Kit. It would be unfair to the juror as he would miss some opportunities. There is no easy way to prevent that.
B) Should unstaking ineligible jurors take place in the usual Staking phase?

Yes because that's what phases are made for. But then the juror could re-stake immediately after.
No and by-pass the DelayedStakes to prevent the juror from re-staking immediately after, but this might still happen if it takes more than maxDrawingTime to draw and KlerosCore cycles through the phases. In addition it breaks the design of the phases and creates a new path for unstaking.

This issue should be viewed as an optimisation which benefits the bot operators. It does not benefit the end users with either better functionality or performance.
For now we are waiting for more clarity on the possibility of making the sortition sum tree more modular + the possibility of simplifying the phases in Kleros Core.

#137 has been implemented so we can revisit this.
Unstake ineligible jurors from court X:

only during Staking phase
and only if they are ineligible from all the DisputeKits allowed by the court in question.

Currently we cannot iterate through the dispute kits to implement this logic.
Worst case just unstake without checking all the DKs.

Easier to implement now after #1357


No horizontal scrollbar when trying to view long suggested changes in a pull request

Extension version:
VSCode Version: insiders.vscode.dev
OS:

Steps to Reproduce:

Open a pull request with suggested code changes with longer lines of text.
Resize the window and observe that the suggested changes text does not resize (other text such as description/comments resizes). I'm also unable to scroll horizontally (via mouse/keyboard) to view the rest of the suggested change.

Upstream issue: https://github.com/microsoft/vscode/issues/172363


Production: show more verbose error

Laravel Mix Version: 1.0.7
Node Version: 6.11.0
NPM Version: 3.10.10
OS: Ubuntu 16.04LTS

Description:
When there is a small non-breaking syntax error in a JS file, the production options shows an error without much information:
Whoops! We had trouble minifying "public/js/buy.js". Perhaps you need to use mix.babel() instead?

/home/jvalck/tickets-webapp/node_modules/laravel-mix/src/plugins/CustomTasksPlugin.js:66
                    throw e;
                    ^
SyntaxError: Unexpected token: name (image)
    at JS_Parse_Error.get (eval at <anonymous> (/home/jvalck/tickets-webapp/node_modules/uglify-js/tools/node.js:1:0), <anonymous>:86:23)

npm ERR! Linux 4.8.0-36-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "production"
npm ERR! node v6.11.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! @ production: `NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ production script 'NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the  package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/jvalck/tickets-webapp/npm-debug.log

This is the line in wabpack.mix.js:
mix.scripts([resourcesScriptDir+'buy.js'], 'public/js/buy.js');

It would be handy if the error message would be more verbose indicating on what line the script failed.
Steps To Reproduce:

Make a small JS-file with a non-breaking syntax error (so that npm run dev doesn't fail), for example an ES6 JS-file.
Run npm run production

Same here ...

Yeah!!! mix.babel() rules!

It would be nice to be informed which line broke the compilation

Thanks guys! I needed this info too. 👍

I'm getting the same error for one of my JS files, but we're already using babel() with that file.
mix
    ...
    .babel('resources/assets/js/news/comments.js', 'public/js/news/comments.js')
    ...
    ;

$ yarn run prod

Whoops! We had trouble minifying "public/js/news/comments.js". Perhaps you need to use mix.babel() instead?

Any idea what sort of issue comments.js could have that would break minification?

Thanks!  Nice!

I change mix.scripts([], '') to mix.babel([], '') then everything go ok~
Thanks! Nice!