To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please cDescriDescribe the bug
A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See eDescribe the bug
A clear and concise description of what the bug is and what you expected to happen.

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:
iOS Device:
unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
rror
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:
iOS DDescribe the bug
A clear and concise description of what the bug is and what you expected to happen.

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:
iOS Device:
unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
evice:

unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[ ] this issue is present on the latest version of unc0ver

Logs
If applicDescribe the bug
A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:
iOS Device:
unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
able, add logs or error messages here.
be the bug**
A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:
iOS Device:
unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
omplete the following information):**

iOS Version:
iOS Device:
unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.Describe the bug
A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:
iOS Device:
unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restoreDescribe the bug
A clear and concise description of what the bug is and what you expected to happen.

To Reproduce
Steps to reproduce the behavior:

GDescribe the bug
A clear and concise description of what the bug is and what you expected to happen.

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:
iOS Device:
unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
o to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:
iOS Device:
unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is preDescribe the bug
A clear and concise description of what the bug is and what you expected to happen.

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:
iOS Device:
unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
sent after a rootfs restore

[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or erroDescribe the bug
A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:
iOS Device:
unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
r messages here.

[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.

Hom

Jghxus

Sygg

VUYVCGUHJB

\//
/..
''/

Jdidj

qwerasdfzxcvtgbyhnujmik,ol.p;/[']=-09876543136527726767627672676276726762767267267676726726726767676672672672676277276726726763763767647567676176276763767676467765676767675766766666777776666777788889999101001010100

what the FUCK!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!????????????????????????????????????????????

You mad bro?

qwerasdfzxcvtgbyhnujmik,ol.p;/[']=-09876543136527726767627672676276726762767267267676726726726767676672672672676277276726726763763767647567676176276763767676467765676767675766766666777776666777788889999101001010100

what the FUCK!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!????????????????????????????????????????????

Describe the bug
A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'

Click on '....'

Scroll down to '....'

See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please cDescriDescribe the bug
A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'

Click on '....'

Scroll down to '....'

See eDescribe the bug

A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'

Click on '....'

Scroll down to '....'

See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:

iOS Device:

unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce

[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled

[ ] this issue is present after a rootfs restore

[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
rror
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:

iOS DDescribe the bug

A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'

Click on '....'

Scroll down to '....'

See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:

iOS Device:

unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce

[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled

[ ] this issue is present after a rootfs restore

[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
evice:

unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce

[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled

[ ] this issue is present after a rootfs restore

[ ] this issue is present on the latest version of unc0ver

Logs
If applicDescribe the bug
A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'

Click on '....'

Scroll down to '....'

See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:

iOS Device:

unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce

[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled

[ ] this issue is present after a rootfs restore

[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
able, add logs or error messages here.
be the bug**
A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'

Click on '....'

Scroll down to '....'

See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:

iOS Device:

unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce

[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled

[ ] this issue is present after a rootfs restore

[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
omplete the following information):**

iOS Version:

iOS Device:

unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce

[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled

[ ] this issue is present after a rootfs restore

[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.Describe the bug
A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'

Click on '....'

Scroll down to '....'

See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:

iOS Device:

unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce

[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled

[ ] this issue is present after a rootfs restoreDescribe the bug

A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

GDescribe the bug

A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'

Click on '....'

Scroll down to '....'

See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:

iOS Device:

unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce

[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled

[ ] this issue is present after a rootfs restore

[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
o to '...'

Click on '....'

Scroll down to '....'

See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:

iOS Device:

unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce

[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled

[ ] this issue is preDescribe the bug

A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'

Click on '....'

Scroll down to '....'

See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:

iOS Device:

unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce

[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled

[ ] this issue is present after a rootfs restore

[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
sent after a rootfs restore

[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or erroDescribe the bug
A clear and concise description of what the bug is and what you expected to happen.
To Reproduce
Steps to reproduce the behavior:

Go to '...'

Click on '....'

Scroll down to '....'

See error

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version:

iOS Device:

unc0ver Version:

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce

[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled

[ ] this issue is present after a rootfs restore

[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
r messages here.

[ ] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.

Still mad?

You know this is actually starting to become entertaining.


Request for support for python 3.10 and 3.11

Requesting the devs to add support for python 3.10 and 3.11 as python’s latest release is python 3.12 and most other libraries have moved on python 3.10 and 3.11

Is there any progress on this issue? I have seen a commit that seems relative to newer python support. (commit e3b7cd)
While an installation attempt on Python 3.11 with boost-cpp library, an error and an warning messages occur.
Error:
include/boost/timer.hpp:25:1: note: ‘#pragma message: This header is deprecated. Use the facilities in <boost/timer/timer.hpp> instead.’
         25 | BOOST_HEADER_DEPRECATED( "the facilities in <boost/timer/timer.hpp>" )

Warning:
include/boost/math/tools/config.hpp:23:6: warning: #warning "The minimum language standard to use Boost.Math will be C++14 starting in July 2023 (Boost 1.82 release)" [-Wcpp]
         23 | #    warning "The minimum language standard to use Boost.Math will be C++14 starting in July 2023 (Boost 1.82 release)"

library versions:

boost-cpp: 1.84.0
python: 3.11.8
gcc: 12.2.0
vina(desired): lastest(1.2.5)

Downgrading boost-cpp from 1.84 to 1.81, this package can be successfully installed. This issue seems can be closed.

Is there any progress on this issue? I have seen a commit that seems relative to newer python support. (commit e3b7cd) While an installation attempt on Python 3.11 with boost-cpp library, an error and an warning messages occur. Error:
include/boost/timer.hpp:25:1: note: ‘#pragma message: This header is deprecated. Use the facilities in <boost/timer/timer.hpp> instead.’
         25 | BOOST_HEADER_DEPRECATED( "the facilities in <boost/timer/timer.hpp>" )

Warning:
include/boost/math/tools/config.hpp:23:6: warning: #warning "The minimum language standard to use Boost.Math will be C++14 starting in July 2023 (Boost 1.82 release)" [-Wcpp]
         23 | #    warning "The minimum language standard to use Boost.Math will be C++14 starting in July 2023 (Boost 1.82 release)"

library versions:

boost-cpp: 1.84.0
python: 3.11.8
gcc: 12.2.0
vina(desired): lastest(1.2.5)

support for boost-cpp >= 1.82 is requested in this PR


Create Default HashId instance only, if needed

Currently, on every boot, the "Default" HashId Instance is created on every boot. This is expensive, and in most use cases unneccessary, as this default is seldomly used, as far as I understand.
Further, when using an environment without Math-libraries for composer install (for example the Composer container), the php artisan package:discovery command will fail, resulting in abortion of package discovery.
This change will delay the creation of the "Default" instance until it's required for the first time.

To reproduce the error, you can use:
docker run -it --entrypoint ash composer -c "composer create-project laravel/laravel . && composer require veelasky/laravel-hashid"
Which will result in:


Kernel Panic - Centos 7.2 3.10.0 - with devicemapper LVM thinpool ext4

Output of docker version:
Client:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 21:23:11 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.5.4
 Git commit:   b9f10c9
 Built:        Wed Jun  1 21:23:11 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 178
 Running: 5
 Paused: 0
 Stopped: 173
Images: 8
Server Version: 1.11.2
Storage Driver: devicemapper
 Pool Name: vg01-docker--pool
 Pool Blocksize: 524.3 kB
 Base Device Size: 274.9 GB
 Backing Filesystem: ext4
 Data file:
 Metadata file:
 Data Space Used: 1.655 TB
 Data Space Total: 5.63 TB
 Data Space Available: 3.976 TB
 Metadata Space Used: 119.7 MB
 Metadata Space Total: 16.98 GB
 Metadata Space Available: 16.86 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Library Version: 1.02.107-RHEL7 (2015-12-01)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 3.10.0-327.13.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 32
Total Memory: 251.6 GiB
Name: XXXXXXXXXXX
ID: AISM:7SDV:XXJ2:Z22V:LPV7:VQNL:XOWS:6J65:WRGX:SB2H:P4YT:VL7K
Docker Root Dir: /grid/0/docker
Debug mode (client): false
Debug mode (server): false
Username: XXXXXX
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Additional environment details (AWS, VirtualBox, physical, etc.):
CentOS Linux release 7.2.1511 (Core)
3.10.0-327.13.1.el7.x86_64
Physical
Issue:
We are encountering sporadic kernel panics on roughly one node per day out of ~100.
  LV          VG   Attr       LSize Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  docker-pool vg01 twi-aot--- 5.12t             29.40  0.71

Our workload is similar to a Jenkins workload, QE testing, but the containers are not cleaned up on exit to allow for additional debugging. As found in the output, we have about 175 stopped containers on this node that recently panic'd, in case this might be a factor.
In looking at the changelog for the latest available 3.10 kernel on Centos 7.2, I don't see any fixes that appear related, so I'm hesitant to just roll out a kernel upgrade in hopes it fixes it. I've been unable to locate similar panics in my searching.
Has anyone encountered this or a similar panic before and have thoughts on root cause/next steps? Happy to provide any additional details as requested.

I haven't seen this reported, but given that docker doesn't install kernel modules, this is unlikely a bug in the docker codebase.
ping @rhvgoyal anything familiar in this?

possibly related to this? https://lkml.org/lkml/2013/10/31/385

Can you try latest centos kernel and see if this issue is already fixed or not.

We ended up moving to xfs for the filesystem and no additional panics have occurred.
However, a colleague reached out to some kernel devs he knows and the consensus is that the panics are related to the LSI megaraid driver. Several panics have been fixed in versions newer than what we are running, including SCGCQ00827403, which very much sounds like the panic we are seeing.
We can close this for now, but hopefully the above will prove useful for others.


(GH-198) Use the PuppetFile Resolver for validation

~Builds on #200~
Fixes #198
The new Puppetfile Resolver gem needs to be revendored, and its dependency
Molonillo. This will be used to Puppetfile module dependency resoltion.
Previously the Puppetfile validator only performed basic validation checks.
This commit updates the validation to now include doing a full module
dependency resolution based on the validation routines in Puppetfile-Resolver.
This commit also removes the R10K Puppetfile parsing and uses the parser
available in the Puppetfile-Resolver.
By default the resolver is enabled, but can be disabled by setting:
puppet.validate.resolvePuppetfiles: false

[x] Add a setting to disable puppetfile resoltion
[x] resolve_puppetfile should come from settings
[x] module_path should come from settings
[x] More tests in the the validation_provider_spec for puppetfile?

Blocked by #200

Still more to look at.  Manual testing with VSCode is failing :-(

Figured it out. Will push commits later.

It was caused by https://github.com/lingua-pupuli/puppetfile-resolver/issues/2 . Puppetfile-resolver 0.0.3 has the fix and is vendored now.

@jpogran  This is back up for review

There is a minor race condition, but that needs a separate ticket.  Currently, validation can be initiated BEFORE workspace settings have been sent from the client.  Therefore the resolver can be called once even though puppet.validate.resolvePuppetfiles is set to false.


Allow build URL to use an environment variable

Description
Pretty self explanatory! p.s. Thanks for adding the build hook feature.
Related issues

Thanks for adding this!


Unknown configuration setting warning.

VSCode Version: 1.29.1
OS Version: Windows 7 64b

Steps to Reproduce:

Working on a regular React project, nothing too fancy. I updated the files associations in order to get the matching icon for the .js files.
After opening the settings.json file (from the preferences menu, not directly) I get a couple of warnings stating: Unknown configuration setting. Removing the changes in the settings file, doesn't clear the warning.

Does this issue occur when all extensions are disabled?: Yes
Here are a couple of captures:

Location was renamed: "workbench.panel.defaultLocation": "bottom",
Suggest was renamed: "typescript.suggest.insertParametersForFunctionCalls": true,

Ok, but the settings in the screenshots are the default settings. I never changed either of those.
Curious if VSCode auto-update does updates those properties?

@rhernandog I cannot reproduce this.. Can you please provide me a minimal steps to repro this issue?

Well, beyond what I already described, there is no other way this happens.
I open VSCode, then I open the settings, then I click on files -> files associations. After the json file opens, the warnings appear.
I made a capture of it:
https://youtu.be/J9ZAd6M4HpQ
As I said before, I never touched the two settings being marked by VSCode as warnings. All I've done in the past months was to change from the system installer to the user installer. The extensions are the same. Again, I think that it could be something about the auto update. I don't recall if I installed version 1.27 or 1.28 when I made the switch to the user installer.
I wish I could provide more details, but unfortunately that is all I'm doing to get this warnings and is actually not breaking the software, everything works as expected.
Thanks for the answers and dedication to this.
Best,
Rodrigo.

I cannot figure out what in the world happened to "typescript.suggest.insertParametersForFunctionCalls". Did the auto complete function parenthesis move to another name again?"

@rhernandog It seems you had some settings which got renamed.
@isidorn @mjbvz Was not there migration when these settings got renamed

Yes, the setting was marked as deprecated for at least one release cycle with a message that pointed users to the new setting. After that, I deleted the deprecated setting a few iterations back because I did not want it showing up any more in the settings ui or settings json. Not sure if there's a better way to handle this

Same as @mjbvz I believe
The setting was depricated for a milestone and than removed.

@rhernandog Please remove that setting from your settings file as it is deprecated and removed.

@sandy081 so what is the replacement?

@mjbvz @isidorn I suppose above comment is meant for you.

@SovietFrontier replacement for "workbench.panel.location": "bottom" is ``workbench.panel.defaultLocation": "bottom"`

What about "typescript.suggest.insertParametersForFunctionCalls": true?


Update log4j to 2.17 to address CVE-2021-45105.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45105

Closing PR as 2.17 is vulnerable. Please update to 2.17.1


refactor: use fetch instead of axios

Replaced axios with fetch. For some strange reason there are errors about axios like the one below
index.js:227 Uncaught (in promise) Error: import_axios.default.post is not a function
    at UploadManager.<anonymous> (index.js:227:1)
    at Generator.next (<anonymous>)
    at index.js:63:1
    at new Promise (<anonymous>)
    at __async (index.js:47:1)
    at UploadManager.startDeployment (index.js:216:1)
    at UploadManager.<anonymous> (index.js:185:1)
    at Generator.next (<anonymous>)
    at index.js:63:1
    at new Promise (<anonymous>)

Thanks for pointing that out. Didn't know that older Node versions does not
include fetch. I have opened a ticket on the spheron discord channel
already. Hopefully I get help from there
On Mon, Mar 20, 2023 at 11:58 AM shomix @.***> wrote:

Hey @havidtech https://github.com/havidtech the PR looks good all in
all. 😄
Just that this fix wont work for all cases. The fetch library is not
supported for all Node environments ( the new version do include it, but
the older ones do not ), so the package wont work for Node projects.
Can you provide an example repo to reproduce the issue the description?
Also what node version are you using?
And on which environment are you using the SDK? Browser/Node?
—
Reply to this email directly, view it on GitHub
https://github.com/spheronFdn/sdk/pull/81#issuecomment-1476015061, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASEX5QCPYJ63G4PP75Q5RG3W5AZ4ZANCNFSM6AAAAAAWAOBMT4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Closing this PR as it seems like the PR is stale for 2 weeks and the issue has been handled separately


Apple Watch complication

According to the WatchKit Programming Guide, Apple recommends that all Watch apps include a complication, even if that complication only acts as a button to launch the app.
Besides that, I think a good action for the complication (at least for me 😅) would be to open the app directly in the input screen.

That would be awesome. I'll gladly provide the assets. 😄

🎉

Are we using Stack or Simple? I feel like Stack could be nice if we provide the latest input.
(https://developer.apple.com/watchos/human-interface-guidelines/app-architecture/complications/)

I honestly don't have a strong opinion on this one. For me, simple would be more than enough, but I guess it wouldn't harm to have the latest input shown.

I have mixed feelings about being able to look my weight all the time. I'm worried about let the user anxious.

Although would be interesting if the stack showed the time since the last measure.

Yeah, it's a good point. I'm not sure if showing last time would be clear enough for the person to understand what is it about. Maybe we can start with something real simple, haha.

Let's do the simple then (yay!).

Alright! I'll make sure to provide assets. 😄


Find next vs Find Next

see attached screen shot
the terminal lower-cases "next" and "pervious" while the editor upper-cases them (which I believe is correct)

Verified but there is still a few outliers


The special casing of OnOff client clusters should likely be removed in preference to event entities

Currently there is a special logic at https://github.com/zigpy/zha/blob/9fe83455574b8aa3f29cb5e722f3b312e6615f79/zha/application/discovery.py#L449 that converts a OnOff output (client) cluster into a virtual server cluster through a handler. It will generate attribute updates based on the commands generated by the client cluster.
I assume this logic stems from before we had event entities in home assistant and was some type of attempt to create a binary_input like entity from an OnOff client cluster.
We should add support for event entities for output clusters, and drop this rather confusing special logic for OnOff clusters.

Any sort of virtual clusters need to go, in my opinion. They were created to re-use the existing cluster handlers to create entities. With the ZHA library allowing direct entity creation, we need to start replacing virtual clusters with those.

In this case it's not virtual clusters, it's a virtual entity linked to a handler. The clusters are real here.

The attributes on the cluster is virtual thou.


Feature/creation-load

In this PR I worked on the following:

Add a module to write and read from file
Refactor add_item() in the label class

Please resolve the conflict before merging.


Broken links in crypto/ec/ec_mult.c comments

The comments state this code implements the wNAF-based interleaving multi-exponentiation method described in http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/moeller.html#multiexp, but this link is broken. Possibly it refers to:
Möller, B. (2001, August). Algorithms for multi-exponentiation. In International Workshop on Selected Areas in Cryptography (pp. 165-180). Springer Berlin Heidelberg.
http://link.springer.com/chapter/10.1007%2F3-540-45537-X_13
http://www.bmoeller.de/pdf/TI-01-08.multiexp.pdf

ping @levitte :)

comment updated on all release branches.