The devDependency @types/node was updated from 11.13.6 to 11.13.7.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
Medium	5.0	WS-2019-0032	#15

Your Greenkeeper Bot 🌴

The devDependency ts-node was updated from 8.0.3 to 8.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ts-node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ WhiteSource Security Check: The Security Check found 2 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
Medium	5.0	[WS-2019-0032]( "Go to CVE Details")	#15
Medium	5.0	[WS-2019-0047]( "Go to CVE Details")	#19

Your Greenkeeper Bot 🌴

See: window.AmbientLightSensor and https://github.com/Exelord/dark-mode/blob/ce9e9a80c46caa619dbd641018a2c3ce561375ef/lib/sensors/ambient-light.js

The Touch Bar entries conflict with other extensions and custom Touch Bar functionality.

Hi,

VSCodium currently only supports installing extensions from open-vsx.org. Therefore it would be awesome if you could publish your extension there as well :)

The process of how to publish there is described here.

Thank you!

I noticed that sometimes Sundial is called 3 times(!!!) because two vscode events are triggered and when the vscode.interval is at zero. We could reset the interval everytime a event is triggered and should consider refactoring the events and look for some better alternatives to not trigger it that often

To reduce the bundled size, replace moment.js lib with dayjs

Is your feature request related to a problem? Please describe.

Whenever I manually switch to some other theme, immediately the extensions switches back to the Sundial Day/Night Theme. But for some files I really like to switch the Color Theme, because the syntax highlighting is more appropriate.

Describe the solution you'd like

I would like to be able to switch manually the Color Theme without Sundial automatically switching the theme until the next theme switching event (when the extensions switches to the Day/Night theme). For example if I switch manually the theme at 3pm, I want it to stay so until 6 pm when the Sundial dark theme kicks in.

Describe alternatives you've considered

I tried removing all event in the sundial.windowEvent and sundial.workspaceEvents, but it didn't work.

"sundial.windowEvents": [],
"sundial.workspaceEvents": []

Is it possible to turn off the auto-selection between night and day themes?

I want to manually switch the theme so that whenever I open the vscode, just the previous theme is used.

The extension settings sync prevents Sundial to perform API request to the geolocation API somehow. I'm already investigating this

The devDependency webpack-build-notifier was updated from 0.1.31 to 0.1.32.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack-build-notifier is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
Medium	5.0	[WS-2019-0032]( "Go to CVE Details")	#15

Your Greenkeeper Bot 🌴

I'm using the extension Bracket Pair Colorizer to color pairs of brackets in the editor. The problem is that colors that work well at night don't work well during daytime. These colors can be changed by modifying the file settings.json.

I think a good feature would be to add a new option for sundial in which you can specify lines to add/remove to the settings.json file depending of the time of the day.

Is your feature request related to a problem? Please describe.

The extension currently floods the Debug Console with non-error messages. This is quite frustrating when I try to debug problems with my own extensions or VSCode.

Describe the solution you'd like

Other extensions print this kind of information on the Output card e.g.:

Hey, great extension made me finally switch to vsc from atom ;)

How can I set it up, that I have a fixed (no day/night change) theme of my choice for the terminal in vsc?

Thank you for being part of the Open VSX community by adding your extensions to the Open VSX Registry. Please note that the service was recently transferred to the Eclipse Foundation and urgent action on your part is needed so we can continue to list your extensions. To ensure uninterrupted service, please sign the Eclipse Publisher Agreement on or before January 8, 2021. If not signed by that date, your extensions will be delisted and will no longer appear on the site nor be available via the API. If you sign at a later date, your extensions will then be re-activated. The signing process is explained in the Wiki (steps 1 and 2).

Please also note that all extensions MUST have a license in order to be listed.

More details are in these recent blog posts:
https://blogs.eclipse.org/post/brian-king/open-vsx-registry-under-new-management
https://blogs.eclipse.org/post/brian-king/new-era-open-vsx-registry

Today, there’s growing momentum around open source tools and technologies that support Visual Studio (VS) Code extensions. Leading global organizations are adopting these tools and technologies. This momentum has spurred demand for a marketplace without restrictions and limitations. Thanks for joining us on this journey as we continue to build the Open VSX community. We look forward to continued innovation from you in 2021!

Describe the bug

When the option Auto locale is active and a VPN connection is also active the extension throws an exception.
This forces the extension to set the wrong theme and we have disabled the option Auto locale and entered manual coordinates or time for proper behavior.
At first it seemed like this could be solved by not using a VPN to establish a connection and use the one on cache, given the error description. After trying that approach the error persists.

To Reproduce

Steps to reproduce the behavior:

1. Open VS Code
2. Go to extension settings
3. Enable 'Auto locale'
4. Connect to a VPN location
5. There should be a notification/pop up displaying an error

Expected behavior

No error notification and configured theme displayed according to geo-location.

Screenshots

Desktop (please complete the following information):

• OS: Windows 11 21H2 build 22000.434
• VS Code: 1.63.2
• Sundial: 2.6.2

WS-2019-0047 - Medium Severity Vulnerability

Vulnerable Library - tar-2.2.1.tgz

tar for node

Library home page: http://registry.npmjs.org/tar/-/tar-2.2.1.tgz

Path to dependency file: /package.json

Path to vulnerable library: /tmp/git/vscode-sundial/node_modules/tar/package.json

Dependency Hierarchy:

• vscode-1.1.30.tgz (Root Library)
  • gulp-untar-0.0.7.tgz
    • ❌ tar-2.2.1.tgz (Vulnerable Library)

Found in HEAD commit: b80ef33c3acce6d426c425738b353cb9a345d9d8

Vulnerability Details

Versions of node-tar prior to 4.4.2 are vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink will overwrite the system's file with the contents of the extracted file.

Publish Date: 2019-04-05

URL: WS-2019-0047

CVSS 2 Score Details (5.0)

Base Score Metrics not available

Suggested Fix

Type: Upgrade version

Origin: https://www.npmjs.com/advisories/803

Release Date: 2019-04-05

Fix Resolution: 4.4.2

Step up your Open Source Security Game with WhiteSource here

Describe the solution you'd like

It'd be nice if you can set list of light and dark themes and every time it switches it picks a random one

Describe alternatives you've considered

You'd have to change it manually otherwise

Additional context

Add any other context or screenshots about the feature request here.

The devDependency webpack-cli was updated from 3.3.0 to 3.3.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack-cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
Medium	5.0	WS-2019-0032	#15

Your Greenkeeper Bot 🌴

This is an amazing plugin (especially since VSCode don't support Mojave's native dark mode..). I live up in the cold north, and the time of daylight changes quite fast, so manually editing when it is supposed to change form light to dark would almost require me to do it everyday if I wanted it to be in sync with the sunlight outside.

Would it be possible, perhaps, to have the function to change to dark when the sun sets rather than at a predefined time? There is a nice little programme that does this for the OS, https://nightowl.kramser.xyz, and f.lux and the native night shift have been doing it since long.

Hey everyone. Your extension looks nice, but it's a shame that it's mac-only.

Read the bottom of this comment:
microsoft/vscode#61519 (comment)

There is a JavaScript query, supported by V8/Electron (VSCode's GUI engine), which tells you whether dark mode is enabled or disabled on the system.

So you can rip out all the ugly macOS-specific code and replace it with this. :-)

The devDependency webpack was updated from 4.29.6 to 4.30.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ WhiteSource Security Check: The Security Check found 2 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
Medium	5.0	[WS-2019-0032]( "Go to CVE Details")	#15
Medium	5.0	[WS-2019-0047]( "Go to CVE Details")	#19

Your Greenkeeper Bot 🌴

The devDependency @types/got was updated from 9.4.3 to 9.4.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/got is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
Medium	5.0	WS-2019-0032	#15

Your Greenkeeper Bot 🌴

Describe the bug

When `"sundial.systemTheme" is enabled, there is a noticeable lag when switching between editors.

To Reproduce

Steps to reproduce the behavior:

1. Open VSCode from iTerm2 (i.e. using code .)
2. Set "sundial.systemTheme: true" in settings
3. Create a new split (cmd+\).
4. Quickly switch focus repeatedly using "cmd+1" and "cmd+2"

Expected behavior

No noticeable lag.

Desktop (please complete the following information):

• OS: [e.g. macOS 10.14.5]
• VS Code [e.g. 1.3.5]
• iTerm2 Build 3.3.20190124-nightly

The devDependency @types/got was updated from 9.4.2 to 9.4.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/got is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
Medium	5.0	WS-2019-0032	#15

Your Greenkeeper Bot 🌴

OK, not quite a "feature request", but I found your extension completely by luck, because if one searches "auto night mode" in the extensions, this doesn't appear in the vscode's results, or at least not in the top ~20 ones or so(I don't usually go deep down).

I don't know how, but maybe you could add some keywords or something like that so that it gets brought up when people search for it? I just want the people to find this and help their eyes. :)
(Thank you very much for this extension).

https://code.visualstudio.com/api/working-with-extensions/bundling-extension

Describe the bug

No theme change after sunset. (haven't tested sunrise)

I verified that window.autoDetectColorScheme is not checked (default). I enabled the extension before sunset, but it is now 50 minutes past sunset and no theme change. Are there logs somewhere I can look at?

Desktop (please complete the following information):

Version: 1.52.1 (user setup)
Commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523
Date: 2020-12-16T16:34:46.910Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19042

Here are my settings for Sundial v2.3.0:

    "workbench.preferredDarkColorTheme": "Cobalt2",
    "sundial.nightVariable": 20,
    "sundial.latitude": "47.6",
    "sundial.longitude": "-122.3"

Would be great if somehow Sundial could change the theme without an internet connection and throws an info message in the console that the connection is down.

WS-2019-0034 - Medium Severity Vulnerability

Vulnerable Library - js-yaml-3.12.2.tgz

YAML 1.2 parser and serializer

path: /tmp/git/vscode-sundial/node_modules/js-yaml/package.json

Library home page: https://registry.npmjs.org/js-yaml/-/js-yaml-3.12.2.tgz

Dependency Hierarchy:

• tslint-5.14.0.tgz (Root Library)
  • ❌ js-yaml-3.12.2.tgz (Vulnerable Library)

Found in HEAD commit: bc0c4634e02c47558d6e0204dfa10707b0cae370

Vulnerability Details

Versions js-yaml prior to 3.13.0 are vulnerable to Denial of Service. By parsing a carefully-crafted YAML file, the node process stalls and may exhaust system resources leading to a Denial of Service.

Publish Date: 2019-03-31

URL: WS-2019-0034

CVSS 2 Score Details (5.0)

Base Score Metrics not available

Suggested Fix

Type: Upgrade version

Origin: https://www.npmjs.com/advisories/788

Release Date: 2019-03-31

Fix Resolution: 3.13.0

Step up your Open Source Security Game with WhiteSource here

Seems its not longer working with autoLocale:

[Extension Host] rejected promise not handled within 1 second: TypeError: Cannot read property 'globalState' of undefined
t.log @ console.ts:134
$logExtensionHostMessage @ mainThreadConsole.ts:39
_doInvokeHandler @ rpcProtocol.ts:390
_invokeHandler @ rpcProtocol.ts:375
_receiveRequest @ rpcProtocol.ts:295
_receiveOneMessage @ rpcProtocol.ts:225
_protocol.onMessage.e @ rpcProtocol.ts:100
fire @ event.ts:584
r @ ipc.net.ts:295
e @ ipc.net.ts:302
fire @ event.ts:584
o @ ipc.net.ts:103
_socketDataListener.e @ ipc.net.ts:132
emit @ events.js:182
addChunk @ _stream_readable.js:279
readableAddChunk @ _stream_readable.js:264
Readable.push @ _stream_readable.js:219
onread @ net.js:636
console.ts:134 [Extension Host] stack trace: TypeError: Cannot read property 'globalState' of undefined
	at Sundial.<anonymous> (/Users/marvinheilemann/.vscode/extensions/muuvmuuv.vscode-sundial-1.2.1/out/sundial.js:96:47)
	at Generator.next (<anonymous>)
	at fulfilled (/Users/marvinheilemann/.vscode/extensions/muuvmuuv.vscode-sundial-1.2.1/out/sundial.js:4:58)
t.log @ console.ts:134
$logExtensionHostMessage @ mainThreadConsole.ts:39
_doInvokeHandler @ rpcProtocol.ts:390
_invokeHandler @ rpcProtocol.ts:375
_receiveRequest @ rpcProtocol.ts:295
_receiveOneMessage @ rpcProtocol.ts:225
_protocol.onMessage.e @ rpcProtocol.ts:100
fire @ event.ts:584
r @ ipc.net.ts:295
e @ ipc.net.ts:302
fire @ event.ts:584
o @ ipc.net.ts:103
_socketDataListener.e @ ipc.net.ts:132
emit @ events.js:182
addChunk @ _stream_readable.js:279
readableAddChunk @ _stream_readable.js:264
Readable.push @ _stream_readable.js:219
onread @ net.js:636
mainThreadExtensionService.ts:49 [[object Object]]Cannot read property 'globalState' of undefined
$onExtensionRuntimeError @ mainThreadExtensionService.ts:49
_doInvokeHandler @ rpcProtocol.ts:390
_invokeHandler @ rpcProtocol.ts:375
_receiveRequest @ rpcProtocol.ts:295
_receiveOneMessage @ rpcProtocol.ts:225
_protocol.onMessage.e @ rpcProtocol.ts:100
fire @ event.ts:584
r @ ipc.net.ts:295
e @ ipc.net.ts:302
fire @ event.ts:584
o @ ipc.net.ts:103
_socketDataListener.e @ ipc.net.ts:132
emit @ events.js:182
addChunk @ _stream_readable.js:279
readableAddChunk @ _stream_readable.js:264
Readable.push @ _stream_readable.js:219
onread @ net.js:636
mainThreadExtensionService.ts:50 TypeError: Cannot read property 'globalState' of undefined
	at Sundial.<anonymous> (/Users/marvinheilemann/.vscode/extensions/muuvmuuv.vscode-sundial-1.2.1/out/sundial.js:96)
	at Generator.next (<anonymous>)
	at fulfilled (/Users/marvinheilemann/.vscode/extensions/muuvmuuv.vscode-sundial-1.2.1/out/sundial.js:4)

See: src/extension.ts#L34

Would be nice to have some automated tests before every publish.

I don't have much experience in this with VS Code, so I hope someone will contribute or help me to get in the right direction. Especially with things like; tell VS Code it's in the night now

In my case I would like to have an option to set a variable where I can say that the theme should change one hour before sunset.

  "sundial.dayVariable": 40,
  "sundial.nightVariable": -30,

in minutes

I found that there is no related setting of sundial.systemTheme before. Thank you.

Describe the bug

I have continuous pop-up errors when I am working in VSCode, as your extension unsuccessfully tries to reach some server for the automatic geo-location.

To Reproduce

Go offline, wake up the computer from sleep, do not connect to wifi, and have enabled automatic geolocation for this extension.

Expected behavior

It should remember the data from the last sync with the geolocation server, if the data is for example older than 10 days (think about holidays), it should have a fallback option to the manual time settings.

Screenshots

If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• MS Windows 10 1903 Build 18362
• VS Code 1.40.2

https://codeclimate.com/github/muuvmuuv/vscode-sundial/issues

Themes are not auto-updating.

The themes are not auto-updating and there is the following error message on the settings pane:

Setting has invalid type, expected "string". Fix in JSON..

Some other functionality appears to work, namely that I can use ctrl+cmd+t to switch btw light and dark themes.

To Reproduce

Steps to reproduce the behavior:

1. Install theme
2. Go to Settings (cmd+,)
3. See errors

Expected behavior

1. The themes auto-switch.
2. The error messages don't appear.

Screenshots

Here's the screenshot of the Settings pane, including the error messages:

Desktop (please complete the following information):

• OS: macOS 10.15.4
• VS Code:

Version: 1.45.0
Commit: d69a79b73808559a91206d73d7717ff5f798f23c
Date: 2020-05-07T15:57:33.467Z
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.4.0

• Sundial: 2.3.0

Is your feature request related to a problem? Please describe.

Because I'm going to implement this feature natively to VS Code, this isn't longer needed in Sundial.

Describe the solution you'd like

Remove it from Sundial core and add a hint that any other feature in Sundial would need the options in Code colorThemeAutoSwitch to be off (or whatever the option will be named in release)

Describe alternatives you've considered

None

Additional context

• Depends on: microsoft/vscode#61519

See: https://github.com/Exelord/dark-mode/blob/ce9e9a80c46caa619dbd641018a2c3ce561375ef/lib/sensors/system-theme.js

The devDependency @types/node was updated from 11.13.0 to 11.13.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ WhiteSource Security Check: The Security Check found 2 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
Medium	5.0	[WS-2019-0032]( "Go to CVE Details")	#15
Medium	5.0	[WS-2019-0047]( "Go to CVE Details")	#19

Your Greenkeeper Bot 🌴

The devDependency @types/node was updated from 11.13.5 to 11.13.6.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
Medium	5.0	WS-2019-0032	#15

Your Greenkeeper Bot 🌴

Describe the bug
See this please:

According to my timezone, it must turn on the light theme, but the dark theme is applied.

To Reproduce
Well, yesterday it worked correctly, but today it got my day/night wrong (at least apparently).

Expected behavior
Light theme must be on. Am I doing anything wrong?

Desktop (please complete the following information):

• OS: [e.g. macOS 10.14.4] Windows 10
• VS Code: [e.g. 1.33.1] 1.60.2
• Sundial: [e.g. 1.16.0] 2.6.0

The devDependency @types/inquirer was updated from 6.0.0 to 6.0.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/inquirer is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
Medium	5.0	WS-2019-0032	#15

Your Greenkeeper Bot 🌴

WS-2019-0032 - Medium Severity Vulnerability

Vulnerable Library - js-yaml-3.12.2.tgz

YAML 1.2 parser and serializer

path: /tmp/git/vscode-sundial/node_modules/js-yaml/package.json

Library home page: https://registry.npmjs.org/js-yaml/-/js-yaml-3.12.2.tgz

Dependency Hierarchy:

• tslint-5.14.0.tgz (Root Library)
  • ❌ js-yaml-3.12.2.tgz (Vulnerable Library)

Found in HEAD commit: 3922198e39bbe653c4faa646ab26b0f11600cad0

Vulnerability Details

Versions js-yaml prior to 3.13.0 are vulnerable to Denial of Service. By parsing a carefully-crafted YAML file, the node process stalls and may exhaust system resources leading to a Denial of Service.

Publish Date: 2019-03-26

URL: WS-2019-0032

CVSS 2 Score Details (5.0)

Base Score Metrics not available

Suggested Fix

Type: Upgrade version

Origin: https://www.npmjs.com/advisories/788/versions

Release Date: 2019-03-26

Fix Resolution: 3.13.0

Step up your Open Source Security Game with WhiteSource here

The devDependency @types/node was updated from 11.11.8 to 11.12.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
Medium	5.0	[WS-2019-0032]( "Go to CVE Details")	#15

Your Greenkeeper Bot 🌴

The devDependency @types/webpack was updated from 4.4.26 to 4.4.27.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ WhiteSource Security Check: The Security Check found 1 vulnerabilities.

Severity	CVSS Score	CVE	GitHub Issue
Medium	5.0	[WS-2019-0032]( "Go to CVE Details")	#15

Your Greenkeeper Bot 🌴