Angular Universal: Schema validation failed with the following errors:   Data path "" should NOT have additional properties(index).

Bug Report or Feature Request (mark with an x)
- [x ] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [x ] build
- [x ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

Node v10.5.0
NPM v6.1.0
Angular CLI: 6.0.8
Node: 10.5.0
OS: win32 x64
Angular: 6.0.6
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
Package                           Version
@angular-devkit/architect         0.6.8
@angular-devkit/build-angular     0.6.8
@angular-devkit/build-optimizer   0.6.8
@angular-devkit/core              0.6.8
@angular-devkit/schematics        0.6.8
@angular/cli                      6.0.8
@angular/platform-server          6.1.4
@ngtools/webpack                  6.0.8
@schematics/angular               0.6.8
@schematics/update                0.6.8
rxjs                              6.2.1
typescript                        2.7.2
webpack                           4.8.3
Repro steps

ng serve or npm run build:ssr
The log given by the failure

Schema validation failed with the following errors:
Data path "" should NOT have additional properties(index).
npm ERR! code ELIFECYCLE
Desired functionality

No errors.
Mention any other details that might be useful

I am trying to implement Angular Universal, I have followed this article
https://angular.io/guide/universal
I did go through other articles with similar problems, all of them say to downgrade npm package versions to 0.6.3. I currently run the latest cli, hence opening this issue. Please let me know if additional details are needed

Can you try if the problem was solved in the lastest @angular/cli and @angular-devkit/<package> changes? Ie 6.1.4 and 0.7.4 respectively.
Otherwise if the problem persists, Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

Can you try to upgrade @angular-devkit/build-angular to 0.7.x? As this issue might have been resolved in another release?

after updating to the latest version it got fixed. hence closing this issue. Thanks a lot for the help!

Create a fresh ng project using latest angular-cli and compare angular.json with your project's angular.json.
You might be able to figure our the issue.


Move code blocks via the Outline panel

Would like the ability to move blocks of code using the Outline panel.

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Make it easier to store other types of link disambiguating information in the path hierarchy

Bug/issue #, if applicable:
Summary
This is a small refactor to change how the path hierarchy internally stores its disambiguated elements, changing the implementation from nested dictionaries per name collision per node to small lists per name collision per node.
The benefit of a small list is that new disambiguating information can be added without increasing the depth of the nested dictionaries at each node.
Dependencies
None.
Testing
Nothing in particular.
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

~[ ] Added tests~
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

In the local benchmark I ran just now, this change shows no measurable difference in build time but a possible small improvement in memory usage
┌──────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Metric                                   │ Change          │ main (f0a3d7a1)      │ current (15305e58)   │
├──────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Duration for 'bundle-registration'       │ -0.7118%¹       │ 2.521 sec            │ 2.503 sec            │
│ Duration for 'convert-total-time'        │ no change²      │ 5.04 sec             │ 4.958 sec            │
│ Duration for 'documentation-processing'  │ no change³      │ 2.379 sec            │ 2.316 sec            │
│ Duration for 'finalize-navigation-index' │ no change⁴      │ 0.062 sec            │ 0.062 sec            │
│ Peak memory footprint                    │ -0.9491%⁵       │ 537.7 MB             │ 532.6 MB             │
│ Data subdirectory size                   │ no change       │ 168.5 MB             │ 168.5 MB             │
│ Index subdirectory size                  │ no change       │ 1.5 MB               │ 1.5 MB               │
│ Total DocC archive size                  │ no change       │ 196.5 MB             │ 196.5 MB             │
│ Topic Anchor Checksum                    │ no change       │ 9ca210cb9901eb38d157 │ 9ca210cb9901eb38d157 │
│ Topic Graph Checksum                     │ no change       │ 311f4d32005c9bd7dd72 │ 311f4d32005c9bd7dd72 │
└──────────────────────────────────────────────────────────────────────────────────────────────────────────┘

 1: There's a statistically significant difference between the two benchmark measurements.
    The values are different enough that the most probable explanation is that they're random samples from two different data sets.
    t-statistic : +2.572          degrees of freedom : 28       95% confidence critical value : +2.042

 2: No statistically significant difference.
    The values are similar enough that the most probable explanation is that they're random samples from the same data set.
    t-statistic : +1.297          degrees of freedom : 28       95% confidence critical value : +2.042

 3: No statistically significant difference.
    The values are similar enough that the most probable explanation is that they're random samples from the same data set.
    t-statistic : +0.990          degrees of freedom : 28       95% confidence critical value : +2.042

 4: No statistically significant difference.
    The values are similar enough that the most probable explanation is that they're random samples from the same data set.
    t-statistic : +1.103          degrees of freedom : 28       95% confidence critical value : +2.042

 5: There's a statistically significant difference between the two benchmark measurements.
    The values are different enough that the most probable explanation is that they're random samples from two different data sets.
    t-statistic : +5.870          degrees of freedom : 28       95% confidence critical value : +2.042

@swift-ci please test

@swift-ci please test


forge-std is not available in chisel

Component
Chisel
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
No response
What command(s) is the bug in?
No response
Operating System
None
Describe the bug
Right now it is impossible to use forge-std remapping in chisel.
Welcome to Chisel! Type `!help` to show available commands.
➜ import "forge-std/Test.sol";
Compiler errors:
Error (6275): Source "forge-std/Test.sol" not found: File not found. Searched the following locations: "".
 --> ReplContract.sol:6:1:
  |
6 | import "forge-std/Test.sol";
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The same error occurs when trying to import project contracts which are using forge-std (tests, for example).
The error reason is following function:
https://github.com/foundry-rs/foundry/blob/c78a811a8af95fb1e029427583a07b2ca3a3fa51/chisel/src/session_source.rs#L312-L333
On line 331 it explicitly excludes forge-std remapping from list of remappings getting passed into solc

I would like to take this @gakonst any direction for this...

hmm I can't remember why I added the note -.-
I believe I retroactively added support for running chisel inside a forge project
But the note hints at this already

NOTE(mattsse): perhaps the better solution is to not add the Vm.sol

we should not do this if forge is already in the project tree
@klkvr do you want to try this?

Yep, I will take this then

https://github.com/foundry-rs/foundry/blob/master/testdata/cheats/Cheats.sol
Is there a reason why interface here is named Cheats and not Vm? The same naming is used in all tests.

it used to be called cheats,
we just haven't renamed this universally in tests to Vm
would accept a PR for this


Search does not work.

Atom: 0.211.0
Chrome: 43.0.2357.125
Fedora: 22
Kernel: 4.0.5-300.fc22.x86_64
When I enable the plugin vim-mode and type "shift+7" nothing happens.
I'd expect it to open the little search Windows but it does nothing.
Any Idea what this could trouble?
I tried to turn off all plugins and themes to be sure but the result was the same.

Hi, just to check - would shift+7 normally produce a slash (/) on your keyboard?

It looks like you're using a non-US keyboard layout. Those do not play nicely with vim-mode (or Atom in general) unless you use the keyboard localization package.
Shift-7 gets registered as & since that's what it represents on a US keyboard layout.

 Running on a lenovo x1 3rd gen.
Yes a shift+7 does produce a /.
To test, I changed my keyboard layout to english (US) layout.
So then I pressed the / button that would be - on my keyboard.
That worked very well.
But I don't intend to use english keyboard for every day use.
Can I somehow help you guys with this task?

This is a bug in Chromium/Blink, so unless you want to fix that, your best shot would be to use the keyboard-localization package I mentioned.

Installing https://atom.io/packages/keyboard-localization actually solves the problem.
Thank you @jazzpi

Looks solved closing.


GUACAMOLE-1020: Implement extension to enable additional restrictions

I've taken a run at implementing a decorating extension that allows users, groups, connections, and connection groups, to be restricted beyond the defaults provided by the base Guacamole implementation:

Restrict the times at which users can log in based on a "Day of the Week" schedule. This is implemented using both an "Allow at certain times" field, which, if present, will restrict the user to logins only during those times, and a "Deny at certain times" field, which, if present, will block the user from logging in during the specified times. This is implemented at both the individual user level, as well as a setting that can be applied to a group and will impact all the members of that group.

Restrict the hosts from which users can log in, based on hostname, IP address, or CIDR notation. I've attempted to implement both IPv4 and IPv6 restrictions. Hostnames will be reverse-queried to resolve to IPs, and then they are checked against the user's login IP, if it's available.

Restrict the times at which connections and/or connection groups (of the Balancing variety) can be accessed, in the same "Day of the Week" schedule.

Restrict the hosts from which connections and/or connection groups (of the Balancing variety) can be accessed, using hostname, IP address, and/or CIDR range.

Had you considered allowing the weekday or time parts of the restrictions to be left out, rather than requiring both? It looks like most of the code would already be pretty close to supporting that.
I think it could be pretty handy - for example:
An admin might prefer to add rule a that a user can access a connection from 9:00 to 17:00 every day, and also add a couple of rules that the user cannot access the connection on Saturday or Sunday.
As opposed to right now it looks like they'd have to add 5 rules, one for each day of the week, and if they wanted to change the hours, they'd have to change all 5 of the rules.

Had you considered allowing either the weekday or time parts of the restrictions to be left out, rather than requiring both? It looks like most of the code would already be pretty close to supporting that.

I had thought about it, but not quite so thorougly.

An admin might prefer to add rule a that a user can access a connection from 9:00 to 17:00 every day, and also add a couple of rules that the user cannot access the connection on Saturday or Sunday.

This should be pretty easy to do - I could add a RegEx/parsing rule that looks for an * to create a rule for every day. I could also look for values like "WD" for Week Day and "WE" for Week End.

As opposed to right now it looks like they'd have to add 5 rules, one for each day of the week, and if they wanted to change the hours, they'd have to change all 5 of the rules.

Yep, that could be quite cumbersome.

If this is hard to implement, I'm fine with leaving it as a future enhancement,

Nah, I'll take a run at it, I think it should be pretty easy. Thanks for the suggestion!

@jmuehlner I've taken a run at implementing what I think you were getting at with the multi-day options.

I also tweaked it so that 1) date is always stored in UTC in the database, and 2) the front-end form sticks with the user's timezone for the field itself, then translates to UTC when storing in the backend.

This is all looking pretty reasonable to me - @mike-jumper thoughts?

@mike-jumper Ping...

:wave: Sorry about that. I'll take a look over this later today.

@mike-jumper or @jmuehlner, anything else that needs tweaking on this one?

Hi, is there any chance of having this merged with the release of the version 1.6.0, as it is not in the milestone? Thank you for your work.

@Toumassa Yes, I would think we would target it for 1.6.0. I've updated the Jira issue accordingly.

I can try and come up with something if there's no time, but would it be possible to display somewhere ther active time restrictions for a connection? I imagine maybe an icon  next to the connection group and hovering over it could display the time restrictions.

@mike-jumper Ping.

I've made a few updates to it, while waiting for reviews - I implemented a Restrictable interface to make some of the methods common to anything that can be restricted, and reworked some of the code around that.

@jmuehlner : I think I've addressed all the issues...without breaking things...but I need to test. Anything else jumps out, let me know.

I've put this back into draft mode for the moment - tracking down a couple of final things that aren't working as expected. Hopefully resolved tonight/tomorrow.

LGTM, but it looks like there's an outstanding change request by @mike-jumper

I'm not seeing any unresolved issues, but I'll scroll through it again and make sure, and wait for Mike's approval.

LGTM, but it looks like there's an outstanding change request by @mike-jumper

I'm not seeing any unresolved issues, but I'll scroll through it again and make sure, and wait for Mike's approval.

Ah, looks like it was just the comment:

Initial partial review - I'm about 50% done reading through the full set of changes.

LGTM, but it looks like there's an outstanding change request by @mike-jumper

I'm not seeing any unresolved issues, but I'll scroll through it again and make sure, and wait for Mike's approval.

Ah, looks like it was just the comment:

Initial partial review - I'm about 50% done reading through the full set of changes.

Heh - nice. :)
I'll read through things now.

LGTM, but it looks like there's an outstanding change request by @mike-jumper

I'm not seeing any unresolved issues, but I'll scroll through it again and make sure, and wait for Mike's approval.

Ah, looks like it was just the comment:

Initial partial review - I'm about 50% done reading through the full set of changes.

Heh - nice. :)
I'll read through things now.

@mike-jumper any objections if I merge this? Did you stil have more you wanted to read through?


Refactor to Rename Quest Module To OpenSRP

IMPORTANT: Where possible all PRs must be linked to a Github issue
Quest Module Rename To OpenSRP
Engineer Checklist

[x] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[x] I have added any strings visible on UI components to the strings.xml file
[x] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[x] I have built and run the FHIRCore app to verify my change fixes the issue and/or does not break the app
[x] I have checked that this PR does NOT introduce breaking changes that require an update to Content and/or Configs? If it does add a sample here or a link to exactly what changes need to be made to the content.

Code Reviewer Checklist

[ ] I have verified Unit tests have been written for any new feature(s) and edge cases
[ ] I have verified any strings visible on UI components are in the strings.xml file
[ ] I have verifed the CHANGELOG.md file has any notable changes to the codebase
[ ] I have verified the solution has been implemented in a configurable and generic way for reuseable components
[ ] I have built and run the FHIRCore app to verify the change fixes the issue and/or does not break the app

Marking this as Draft until we resolve on the base package name we want for the product. Do we still want to have Fhircore in the signature? cc @pld
Right now with this refactor it looks like this:

Generic OpenSRP APK - org.smartregister.fhircore.opensrp
eCBIS APK - org.smartregister.fhircore.opensrp.ecbis
ZEIR APK - org.smartregister.fhircore.opensrp.zeir

Marking this as Draft until we resolve on the base package name we want for the product. Do we still want to have Fhircore in the signature? cc @pld
Right now with this refactor it looks like this:

Generic OpenSRP APK - org.smartregister.fhircore.opensrp
eCBIS APK - org.smartregister.fhircore.opensrp.ecbis
ZEIR APK - org.smartregister.fhircore.opensrp.zeir

Note: Once the APK is distributed manually or on Playstore we can't change it unless we force all user to perform a fresh install via a different link

I think we miscommunicated here, let's talk before we make any further changes to be sure we're on the same page.
The main change I was interested in is the name of the APK that we generate as the generic APK, calling that OpenSRP vs Quest. For the internal code package names, I don't have a strong opinion on what that's called, I'm fine keeping it as it is in current main.

The main change I was interested in is the name of the APK that we generate as the generic APK, calling that OpenSRP vs Quest. For the internal code package names, I don't have a strong opinion on what that's called, I'm fine keeping it as it is in current main.

I agree with @pld here. I do not think the renaming of the internal packages is really necessary. The quest app can be renamed via it's flavor. Different apps can override the name as desired including the app Id.The app Id and versions are required for use in Playstore and typically the users aren't aware of them.

The main change I was interested in is the name of the APK that we generate as the generic APK, calling that OpenSRP vs Quest. For the internal code package names, I don't have a strong opinion on what that's called, I'm fine keeping it as it is in current main.

I agree with @pld here. I do not think the renaming of the internal packages is really necessary. The quest app can be renamed via it's flavor. Different apps can override the name as desired including the app Id.The app Id and versions are required for use in Playstore and typically the users aren't aware of them.

On Playstore the app id is not entirely transparent to the users, e.g. in the link where one downloads the Uber or Whatsapp apps you do get signature therein - https://play.google.com/store/apps/details?id=com.ubercab and https://play.google.com/store/apps/details?id=com.whatsapp respectively. It is somewhat just a branding nuance though.

so in our case wouldn't you get org.smartregister?

so in our case wouldn't you get org.smartregister?

At the moment for generic quest we get org.smartregister.fhircore.quest but this PR changes that to org.smartregister.fhircore.opensrp
If our conclusion is to remove the fhircore part then it will be org.smartregister.opensrp with the other flavors appending their unique project specific suffix e.g. org.smartregister.opensrp.ecbis.
We could also have it be org.smartregister.ecbis but we'd loose the opensrp

Ok I see that's a good justification to change, apologies, I didn't realize this. The below approach you suggested makes sense to me.

If our conclusion is to remove the fhircore part then it will be org.smartregister.opensrp with the other flavors appending their unique project specific suffix e.g. org.smartregister.opensrp.ecbis.

:+1: LGTM

Yeah sure let's wait on the new pr until we can chat about package strategy a final time

On Jun 8, 2023, at 07:32, Elly Kitoto @.***> wrote:

👍 LGTM
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.


Add dispose method to SSPCLient

Property 'dispose' is missing in type 'SSPClient'.

Is there something that does not get disposed and should when calling disconnect or shutdown?

The dispose function is working as of now. Hence closing the issue.


Adding packages libxml2,libxslt, zlib1g-dev

It seems that there is a breaking change in the latest version of lxml (5.0.0), which now requires libxml2 and libxslt. Unfortunately, these packages are not available in Python 3.8 and Python 3.9, causing a failure. I am adding these libxml2,libxslt, zlib1g-dev as temp fix, any user with python3.8, 3.9  tries to install amazon provider they will encounter this issue.
For permanent solutions:-

we can add these packages in airflow repo
Pin lxml version==4.9.4 in redshift_connector till it get resolved in lxml

It looks like there was an issue with the lxml wheel, as mentioned here. Initially, our job attempted to build from source because the wheel was not available, resulting in the problem. However, the wheel issue has now been fixed, and it started working fine again without any further intervention. I will close the PR as its not needed now


Unable to load kernel driver (The referenced account is currently disabled and may not be logged on to)

Brief description of your issue

Just after the update this message poped up
Steps to reproduce (optional)

Update to version 3.1.24183.0 Canary.
Run System Informer as admin.

Environment (optional)
- System Informer version 3.1.24183.0 (24696944) x64.
- Windows 11 Pro x64, 23H2, 10.0.22631
- Windows Kernel 10.0.22621.3810

Known issue with the build tools run through the release pipeline, I know where the problem is - fixing now.

3.1.24184.1 - Help > Check for updates - 👍


Attempt to force Meteor version into semver

[x] needs testing

Closes #128

Worth a shot.  Curious what formats this will support, and what will break.

There is an issue with this approach if Meteor releases a version with a string in one of the 1st three positions (eg: 1.5.beta, 2-alpha)

Could we check if the `patch

Could we check if the patch is numeric, else, truncate to minor?

What is this code actually trying to accomplish?
Seems like this is verifying that a specific version is supported on Modulus so.. does the check really need to be infinitely flexible?

Was just looking into parsing to integer, I think that can work:
> parseInt('2-alpha', 10)
2
> parseInt('beta', 10)
NaN

Just need to convert NaN to 0 I think

@fiveisprime are you suggesting a whitelist lookup instead? We'd have to update for every release, and every user would need to update to deploy, right?

updated with attempt to parseInt and included test.

My be redundant, but another test with the version being 2 or x. Besides that, 👍

LGTM

added some failing non-server tests and included more options recommended by @harlanj

👍

I think we publish this as 6.2.1 and next on npm, let @flean and @hassanasad try it out

Could always have them $ npm install -g onmodulus/modulus-cli#bug/meteor-version to test

I think #132 needs to be in that patch as well, since it was introduced in v6.2.0

Is this deployed to npm? I tried downloading the latest, and also modulus@next. Also tried with #bug/meteor-version but looks like that branch doesnt exist anymore. @fiveisprime @jackboberg

This is in the master branch. Just update to pull from master @timmyg

@harlanj ah sweet, looks like its working now. Do you know if there is any way to force a version on Codeship? (at least i can deploy now, just have to do it manually)

I'm not sure on how to do that. I haven't done any Codeship integrations. If you want to hop in our irc I can try to help you more there.

@harlanj cool, will hop in there in a bit - thanks for the help!

What's next step?I updated Modulus on npm. Now?

You can get this update by npm i -g modulus@next. However, our build image doesn't yet support Meteor using node@4. We have an open issue that addresses this on our meteor build image, but in the meantime, there are other work arounds.

:+1:

Does this work yet? Haven't tried and I'd like to save myself the grief if it doesn't


[Bug]: SoloCam S220: Changing alarm mode kills homebridge

Setup:
Running Homebridge on Docker on Raspi 4B

Homebridge 1.7.0
Node.js v18.18.2
homebridge-eufy-security v2.2.21

I had running homebridge with eufy security plugin quite smoothly with a Homebase 2 and two EufyCam 2C Pro (only used as motion sensors) added. Everything worked fine, including alarm mode switching for homebase.
Now I added two new Eufy Solocam S220 ("Haustür" and "Terrasse") to my account/guest account and added them to the eufy homebridge plugin.
First of all - the cameras are not recognized as cameras in the config UI:

However, the station is displayed as alarm system in my iOS Home app, so homekit integration seems to work for alarm station. But: After switching the alarm mode for one of the Solocams, homebridge encounters an error and restarts, see error message below.
This is strange since the S220 is listed under supported devices: https://bropat.github.io/eufy-security-client/#/supported_devices
Device Type
Station (Supported)
Plugin Version
v2.0.x (Supported)
HomeBridge Version
v1.6.x (Supported)
NodeJS Version
v18 (Supported)
Operating System
Docker (UnSupported)
Relevant log output
[12/20/2023, 10:52:00]	[EufySecurity]	ERROR	Haustür handleSecuritySystemCurrentStateGets: Wrong return value
[12/20/2023, 10:52:00]	[EufySecurity]	ERROR	Haustür handleSecuritySystemTargetStateGet: Wrong return value
[12/20/2023, 10:52:00]	[EufySecurity]	ERROR	Terrasse handleSecuritySystemTargetStateGet: Wrong return value
[12/20/2023, 10:52:00]	[EufySecurity]	ERROR	Terrasse handleSecuritySystemCurrentStateGets: Wrong return value
[12/20/2023, 10:52:09]	[EufySecurity]	ERROR	Haustür handleSecuritySystemTargetStateGet: true
[12/20/2023, 10:52:10 AM] [deCONZ] Smart plug 1 Consumption: Total Consumption: set to 0.35 kWh (from 0 kWh)
[12/20/2023, 10:52:10 AM] [deCONZ] Smart plug 1 Consumption: Total Consumption: set to 0 kWh (from 0.35 kWh)
[12/20/2023, 10:52:14]	[EufySecurity]	ERROR	Haustür alarm could not be reset: NotSupportedError: This functionality is not implemented or supported
[12/20/2023, 10:52:18]	[EufySecurity]	ERROR	Haustür handleSecuritySystemTargetStateGet: true
[12/20/2023, 10:52:20]	[EufySecurity]	ERROR	Haustür alarm could not be reset: NotSupportedError: This functionality is not implemented or supported
[12/20/2023, 10:52:22]	[EufySecurity]	INFO	Haustür Request to change station guard mode to: AWAY_ARM(1)
[12/20/2023, 10:52:22 AM] NotSupportedError: This functionality is not implemented or supported
    at Station.setGuardMode (/homebridge/node_modules/homebridge-eufy-security/node_modules/eufy-security-client/src/http/station.ts:689:19)
    at StationAccessory.handleSecuritySystemTargetStateSet (/homebridge/node_modules/homebridge-eufy-security/src/plugin/accessories/StationAccessory.ts:350:19)
    at setValue (/homebridge/node_modules/homebridge-eufy-security/src/plugin/accessories/StationAccessory.ts:99:33)
    at SecuritySystemTargetState.setHandler (/homebridge/node_modules/homebridge-eufy-security/src/plugin/accessories/BaseAccessory.ts:161:25)
    at SecuritySystemTargetState.<anonymous> (/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2547:42)
    at step (/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:195:27)
    at Object.next (/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:176:57)
    at /homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:169:75
    at new Promise (<anonymous>)
    at Object.__awaiter (/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:165:16)
[12/20/2023, 10:52:22 AM] Got SIGTERM, shutting down Homebridge...
[12/20/2023, 10:52:22]	[EufySecurity]	INFO	Finished shutdown!
[12/20/2023, 10:52:24 AM] [deCONZ] Phoscon-GW: websocket connection to ws://<IP_ADDRESS>:443 closed
[12/20/2023, 10:52:27]	[EufySecurity]	WARN	Haustür Changing guard mode to AWAY_ARM(1) did not complete. Retry...'
[12/20/2023, 10:52:27 AM] NotSupportedError: This functionality is not implemented or supported
    at Station.setGuardMode (/homebridge/node_modules/homebridge-eufy-security/node_modules/eufy-security-client/src/http/station.ts:689:19)
    at Timeout._onTimeout (/homebridge/node_modules/homebridge-eufy-security/src/plugin/accessories/StationAccessory.ts:359:21)
    at listOnTimeout (node:internal/timers:569:17)
    at processTimers (node:internal/timers:512:7)
[12/20/2023, 10:52:27 AM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[12/20/2023, 10:52:32 AM] [HB Supervisor] Restarting Homebridge...

config
{
            "platform": "EufySecurity",
            "ignoreStations": [],
            "ignoreDevices": [],
            "cleanCache": true,
            "username": "xxx",
            "password": "xxx",
            "country": "DE",
            "deviceName": "",
            "cameras": [
                {
                    "serialNumber": "T8142T7xxx26",
                    "enableCamera": false,
                    "enableButton": false,
                    "motionButton": false,
                    "talkback": false,
                    "videoConfig": {
                        "audio": false,
                        "audioSampleRate": 0
                    }
                },
                {
                    "serialNumber": "T8142T7xxx68",
                    "videoConfig": {
                        "audio": false,
                        "audioSampleRate": 0
                    },
                    "talkback": false,
                    "enableButton": false,
                    "motionButton": false,
                    "enableCamera": false
                },
                {
                    "serialNumber": "T8134P2xxx1E",
                    "rtsp": false,
                    "talkback": false
                },
                {
                    "serialNumber": "T8134P2xxx15",
                    "rtsp": false,
                    "talkback": false
                }
            ],
            "stations": [
                {
                    "hkHome": 1,
                    "hkAway": 0,
                    "serialNumber": "T8134P2xxx1E",
                    "hkNight": 3,
                    "hkOff": 63
                },
                {
                    "hkHome": 1,
                    "hkAway": 0,
                    "serialNumber": "T8134Pxxx15",
                    "hkNight": 3,
                    "hkOff": 63
                }
            ]
        }

Anyone an idea? Problem still exists.


Add retry in yf.download to avoid random data not found

Describe the problem
we typically save all tickers in a list and then download in yf
`python
tickers=pd.read_excel('tickers.xlsx').to_list()
stock_data_close = pd.DataFrame(yf.download(tickers, start=start_date, end=end_date)['Adj Close'])
stock_data_open = pd.DataFrame(yf.download(tickers, start=start_date, end=end_date)['Open'])
stock_data_high = pd.DataFrame(yf.download(tickers, start=start_date, end=end_date)['High'])
stock_data_low = pd.DataFrame(yf.download(tickers, start=start_date, end=end_date)['Low'])
`
but sometimes the ticker not getting results are randomly like this, does not always the same
[100%**]  1630 of 1630 completed
27 Failed downloads:

OXY: No data found for this date range, symbol may be delisted
HD: No data found for this date range, symbol may be delisted
GATX: No data found for this date range, symbol may be delisted
RACE: No data found for this date range, symbol may be delisted
FIS: No data found for this date range, symbol may be delisted
BTU: No data found for this date range, symbol may be delisted
ALV: No data found for this date range, symbol may be delisted
TW: No data found for this date range, symbol may be delisted
VSH: No data found for this date range, symbol may be delisted
WPP: No data found for this date range, symbol may be delisted
Describe the solution
Add multiple retry for a specific ticker if it is not able to download
stock_data_low = pd.DataFrame(yf.download(tickers, start=start_date, end=end_date,retry=5)['Low'])
Means for any failed download in a specific ticker, retry for 5 times.
Additional context

Some considerations:

may need to delay retries e.g. 2 seconds
consider that Yahoo returning nothing because that symbol didn't trade / doesn't exist
I hope obvious: only retry symbols that failed

Some considerations:

may need to delay retries e.g. 2 seconds
consider that Yahoo returning nothing because that symbol didn't trade / doesn't exist
I hope obvious: only retry symbols that failed

I tried to download single chart in a for loop, comparing to download from a list.
It seems most failed download are finished after retry only one more time, and delay is not necessary.
5 tries would be the best if no delay applied and skipped almost instantly
The code I wrote is using if condition on the dataframe
like
for i in range(5):
if df.empty==True:
continue
else:
break

Is this fixed in latest release 0.2.17?

Is this fixed in latest release 0.2.17?

not yet, I have tried myself, but my coding skills isn't good enough and failed. Let's see if other people can work on

@XJTLUmedia ... you use PIP upgrade. Don't overthink it.

Ok, then no, it didn't fix


Intermittent serial port issue - no data is written.

Great library!  Thanks for building this for the community.  I'm using this in a project and am running into a very strange issue.  We have a windows service running on a 64bit Windows 10 Enterprise machine that maintains an open SerialPortStream connection to a peripheral.    The method call does not fail and no errors are returned.  I've turned on diagnostic tracing for the SerialPortStream library and can see when it switches from writing data to failing to do so.  I have attached a sample log below.  Any ideas?  Your insight is greatly appreciated.
LogSample.txt
Just a note, I do not have a command timeout set on this SerialPortStream.

Interesting case and thank you for the logs. What serial device are you using?
The last working case looks like:
IO.Ports.SerialPortStream Verbose: 0 : COM5: SerialThread: DoWriteEvent: WriteFile(996, 48220016, 8, ...) == False
    DateTime=2018-02-04T17:42:21.8490340Z
IO.Ports.SerialPortStream Verbose: 0 : COM5: SerialThread: ProcessWaitCommEvent: EV_TXEMPTY
    DateTime=2018-02-04T17:42:21.8490340Z
IO.Ports.SerialPortStream Verbose: 0 : COM5: CommEvent: EV_TXEMPTY
    DateTime=2018-02-04T17:42:21.8490340Z
IO.Ports.SerialPortStream Verbose: 0 : COM5: SerialThread: ProcessWriteEvent: 8 bytes
    DateTime=2018-02-04T17:42:21.8490340Z
IO.Ports.SerialPortStream Verbose: 0 : COM5: SerialThread: ProcessWriteEvent: TX-BUFFER empty
    DateTime=2018-02-04T17:42:21.8490340Z

The failing case however is
IO.Ports.SerialPortStream Verbose: 0 : COM5: SerialThread: DoWriteEvent: WriteFile(996, 48220024, 8, ...) == False
    DateTime=2018-02-04T17:42:28.6656425Z
IO.Ports.SerialPortStream Verbose: 0 : COM5: SerialThread: ProcessWriteEvent: 0 bytes
    DateTime=2018-02-04T17:42:29.1657180Z

It tells me that Windows didn't immediately complete the request (OK, this happens everywhere), but there is no indication that the driver from Windows actually sent the data.
Do you have hardware flow control active?
It looks like the Windows serial driver itself goes into a timeout:
result = UnsafeNativeMethods.GetOverlappedResult(m_ComPortHandle, ref writeOverlapped, out bytes, true);
if (!result) {
  ...
} else {
  ProcessWriteEvent(bytes);
}

So Windows is saying that the write is finished (result was true), however no bytes were sent (bytes=0 shown in logs), and we don't see the COMM_EVENT indicating TX_EMPTY.
If you're using a 16550A chipset (really ancient, probably not), I'd check if you have flow control active.
If you are using a USB chipset, can you try different drivers (note, not always the newest is the best, as I found out with some)? I've found FTDI to be the most reliable. Check the USB cables for quality (some long cables, cheap hubs cause problems). Try exchanging the USB/SER adapter if you have better luck.
My tests have included running for days automatic tests sending via the serial port using FTDI on testing external embedded devices.

Thanks for the info!  We're using an industrial computer by a company called Qotom.  We have sent an email to them to which chipset their using, but I don't think it's a the 16550A.
We do not have hardware flow control active.    We're connecting from this Qotom computer to another embedded single board computer from Eurotech.  These devices are just communicating with a simple 3 line (TX,RX,GND) serial cable, very low-tech.
I too have been running the tests for days (weeks actually) and have had no issues in our lab, only in production.   :)
Is there a way to get the actual count of bytes written without modifying your library too much?  That way if I see zero bytes written a few times in a row I can try some alternative handling while we're trying to get to the root cause.  The issue seems to be resolved when we restart our windows service.
Thanks again for the help.  I will post again when I have more info from the PC manufacturer or I find a resolution.

You could check the property BytesToWrite. If the value doesn't decrease between two reads then data isn't being sent. The BytesToWrite checks how much data is still in the memory buffer that hasn't been successfully sent plus any data that the serial driver itself reports as being present. The property will call UnsafeNativeMethods.ClearCommError(m_ComPortHandle, out cErr, out comStat); which may have the side effect also of clearing any (unreported) errors in the serial driver. Give it a try!
If it's an embedded device, I would expect that it would be a 16550A compatible directly built in to Intel's LPC bus. You can certainly check to see what drivers are installed. For example, I see my 16550A on my laptop (it's old) is:

(General Tab) on Intel(R) ICH8M-E LPC Interface Controller - 2811
(Resources Tab) I/O Range 03F8-03FF; IRQ 04

But yours is a COM5 and unlikely to be a 16550A (that would be a COM1 or COM2, perhaps COM3 or COm4 with IRQ sharing).

Thanks for the continued assistance. We finally got it to fail in our lab this morning after running for 5 days.  We also managed to get a software serial port monitor by Eltima hooked up to it while it was in the failed state.  We took a snapshot when it was in a failed state:

and when it was in a working state:

Looks like its getting a STATUS_TIMEOUT during the IRP_MJ_WRITE call.  It seems like the buffer is filling as you mentioned - if you notice the data length is 84488 during the write period. For whatever reason, the buffer didn't fill up beyond this amount upon subsequent calls to the IRP_MJ_WRITE calls.
We are still working with the hardware manufacturer to understand what we can do on the hardware side.    I will post more info as I get it.  Hopefully this will help anyone having a similar issue.

The Eltima logs certainly match the logs in the SerialPortStream. I saw the same, that eventually we just get the Write is finished with zero bytes. The 84488 is what is in the local buffer which it attempts to write. The assumption in code is that if it's too big, the driver should only send a partial amount and say how much it actually wrote.
I remember when designing the original code, PL2303 chipsets had problems sending too much data.
You could limit the size of the writes to something lower such as 4096 bytes by modifying the function CommOverlappedIo.cs::DoWriteEvent (line 747).
However, in the original logs you sent, you were only sending about 8 bytes every few seconds, so it suggests that the serial port wasn't sending data for probably 20 minutes or so.

Assuming this is a driver issue, no feedback for some time. Closing


Feature Request: Rust Support

I've been working on integrating a Rust project with a large multi-language repository, and we're successfully building Rust binaries via rules_rust and cargo raze. However, we have not been able to get the projects working within CLion or Intellij IDEA, I think in part because the plugin does not yet support it.
Is Rust support something that the Intellij plugin authors would be open to? I am happy to dedicate time to making this come to fruition, if it is desired. Roughly speaking, what would it take to get this working?

@jin there seems to already be support for go, cpp, dart, javascript, python, scala, kotlin and java.
What is the process for adding a new language? Barring scala which wix added support for, each of the existing languages are used internally within Google. I presume one concern is who would be on the hook for supporting the language support after the initial implementation

Currently, we don't have bandwidth or domain expertise to support new languages like Rust, and there isn't a process to add a new language yet. It's possible to work on a fork of this project to add Rust support, but until the details are ironed out, we cannot support this yet.
One of the things that's high on my list to do is to implement a pluggable framework so that rule owners / domain experts (e.g. rules_rust) can integrate with this plugin without having to extend the core IntelliJ plugin, similar to how Starlark has provided Bazel core with extensibility.

Any updates on this? Will this be scoped out or prioritized in/for 2021?

By the way, could someone link an example of a project that uses Bazel with Rust?

https://github.com/bazelbuild/rules_rust/tree/master/examples has a couple of samples.
I can build a repo that mimics the common components used in internal monorepos using bazel if it might help.
And here you can find an example of crates where cargo raze was used to generate build files:
https://github.com/bazelbuild/rules_rust/tree/master/bindgen/raze/remote

Currently, we don't have bandwidth or domain expertise to support new languages like Rust, and there isn't a process to add a new language yet. It's possible to work on a fork of this project to add Rust support, but until the details are ironed out, we cannot support this yet.

Is forking this project still seen as the best way to getting Rust support added given the current state of the project?
Would you accept a PR to add direct Rust support now? Or...

One of the things that's high on my list to do is to implement a pluggable framework so that rule owners / domain experts (e.g. rules_rust) can integrate with this plugin without having to extend the core IntelliJ plugin, similar to how Starlark has provided Bazel core with extensibility.

...is this completely blocked on implementing such a pluggable framework?

I've opened a PR which integrates with the IntelliJ Rust plugin to deliver Rust support.

#3222

It depends on https://github.com/intellij-rust/intellij-rust/pull/8491. I've uploaded an example project, and demo of the plugin's capabilities, at https://github.com/vaticle/bazel-intellij-rust-example
https://user-images.githubusercontent.com/14253102/151391801-a7551fcb-0322-4ed5-adc1-f11784a3b106.mov
The PR's architecture is suboptimal, looking for some insider knowledge to bring it to production grade.


720p messages in ingest container

I'm having trouble telling whether this is an obs issue or what is being reported in my ingest container, but it only ever reports a 720p stream.
If I change the stream size in obs, it will load the image smaller in the webpage, so I think it is sending a smaller stream, but no matter what, the console always says 720P. I was trying to confirm that I could get 1080P.

I can confirm that this is an FTL issue however you are able to send whatever size video you want. It will always report 720p


Improve benchmark setup

I needed to find something lightweight to do to get my mind off the Cholesky issues, so here we are 😄

Add -profile flag to run just a single iteration without warmup (with profiler hook enabled)
Add -profiler_hook flag (nvtx,roctx,tau,vtune,auto,debug)
Add -input flag to provide either JSON or a filename
Add test framework comparing the benchmark output against a reference
Refactor benchmarks to use a common framework for handling JSON etc.
Replace RapidJSON by nlohmann_json

The distributed benchmarks are tested now as well. The -profile flag is meant as a shortcut, if users are interested in the difference between hot and cold calls, they can still see the individual generate and apply calls in the timeline by controlling repetitions themselves. We could consider adding ranges to the timer iterations if repetitions > 1?

I feel like this PR mixes quite a few things, which could stand as their own PR. I think splitting this up into 3 PRs

CLI changes (-profile, -input, ...)
test framework
JSON changes
would make each part simpler to review. If that is too inconvenient, I would suggest to at least extract the test framework changes.

should this use #1387 as the base branch?


Empty canvas on Web, no errors.

Using eframe-template, building with trunk. I've upgraded my script, and while working on Native it stopped showing anything on Web, just blank canvas. Ids are aligned.
 I've done the following:

added wasm to chrono:

chrono = { version = "0.4.23", features = ["wasmbind"] }

The error line moved a function further (next wbindgen had an error as well it seems). This occured a couple of times. Whenever I "fixed" (it works on Native so...) or rather "done something" - the error line moved forward.
For example  adding
use eframe::wasm_bindgen::{self, prelude::*};
Solved one binding and the error wbindgen line progressed.
I've tried various things:

tried removing blocks of code for adding fonts (no result)
tried removing ChaChaPoly and uses (no change)
ensured the usage of include_bytes!() everywhere where something could be loaded

Eventually fixing all those binding errors. But the canvas on Web still empty.
I am suspecting the instantiation and usage of ehttp are the problem? EDIT: It's not. Commented out all ehttp lines and got error with this func instead __wbg_getTime_58b0bdbebd4ef11d. Maybe chrono issue? EDIT: Commented out all chrono lines, the issue persists, same thing, blank canvas. With both modules commented out, same thing.
This is my Cargo.toml :
[dependencies]
egui = "0.20.0"
eframe = { version = "0.20.0", default-features = false, features = [
    "accesskit",
    "glow",
    "persistence"
]}

# You only need serde if you want app persistence:
serde = { version = "1", features = ["derive"] }
ethers = "1.0.1"
tokio = "1.22.0"
chrono = { version = "0.4.23", features = ["wasmbind"] }
eyre = "0.6.8"
chacha20poly1305 = "0.10.1"
serde_json = "1.0.88"
anyhow = "1.0.66"
image = "0.24.5"
egui_extras = "0.20.0"
ehttp = "0.2.0"
poll-promise = { version = "0.2.0", features = ["web"] }
url = "2.3.1"
regex = "1.7.0"

# native:
[target.'cfg(not(target_arch = "wasm32"))'.dependencies]
tracing-subscriber = "0.3"

# web:
[target.'cfg(target_arch = "wasm32")'.dependencies]
console_error_panic_hook = "0.1.6"
tracing-wasm = "0.2"
wasm-bindgen-futures = "0.4"

[profile.release]
opt-level = 2 # fast and small wasm

# Optimize all dependencies even in debug builds:
[profile.dev.package."*"]
opt-level = 2

[patch.crates-io]

I don't know what it can be. I haven't added much in terms of new modules to the script I've previously used. I think only chrono (or more functions of chrono) and the ehttp mechanics. Content is largely modified though, especially moving Grid to Table and so on. I've also started using some other extras, maybe there's a problem with those? Also, the current version is 0.20.0 and previous that worked was 0.19.0

I just spent some time tracking down a similar issue, for me it was caused by <!DOCTYPE html> in the index.html I was using for testing. Removing that fixed the issue.

I just spent some time tracking down a similar issue, for me it was caused by <!DOCTYPE html> in the index.html I was using for testing. Removing that fixed the issue.

I've done that just now and still am getting Uncaught (in promise) LinkError: WebAssembly.instantiate(): Import #6 module="wbg" function="__wbg_fetch_9a5cb9d8a96004d0" error: function import requires a callable
but thanks a lot any help effort is appreciated. Could you describe your issue?
I'm most interested whether my ehttp usage needs different bindings, because I can't figure out how to decorate main with #[wasm_bindgen], or how to export the start_web() function to a different function, since I can't pass in necessary arguments into the initiator function anyways.

but thanks a lot any help effort is appreciated. Could you describe your issue?

Completely white screen, no console errors. After commenting out most parts of the code, removing basically all dependencies, the only relevant difference I could find when comparing to the custom_3d_three-d example was the DOCTYPE, and that was it.

does someone know, why would adding <!DOCTYPE html> break the app?

After commenting out most parts of the code, removing basically all dependencies, the only relevant difference I could find when comparing to the custom_3d_three-d example was the DOCTYPE, and that was it

When did you first discover you were a Chad?
I checked up with a similar approach and there must be a serious bug somewhere. I've commented out every single thing. My code is now:
use eframe::{egui};
use egui::{Context,CentralPanel};
struct MyApp{}
impl Default for MyApp{
    fn default() -> Self { MyApp{}}
}
#[cfg(target_arch = "wasm32")]
pub fn main(){
    let mut options = eframe::WebOptions::default();
    eframe::start_web(
        "MATCHING ID",
        options,
        Box::new(|cc| Box::new(MyApp::default()
    )),
    );
}

impl eframe::App for MyApp {
    fn update(&mut self, ctx: &Context, cframe: &mut eframe::Frame) {
        CentralPanel::default().show(ctx, |ui| {
ui.label("ookokokokokokokokokokokokokokokokokokokokokokokokokokkookokokokokokokokokokokokokokokokokokokokokokokokokokkookokokokokokokokokokokokokokokokokokokokokokokokokokk");
          });
    }
}

And this thing will show blank canvas with Trunk [of course with browser inspector shows same default 300x150 empty sized box]. I'm lost.  For me removing <!DOCTYPE html> does nothing =(
And as always, Native works flawlessly..

comparing to the custom_3d_three-d example

correct me if I'm wrong but isn't the example purely native with just a html file added?
I think we should compare against the eframe example for web since it's for web.
As I said, my script is simplified eframe example, it's just one main file and the rest is the trunk boilerplate. I believe somewhere in 0.20.0 must have occured a bug? I actually had no clue that the above won't run on web currently. It wasn't like that previously. Some update somewhere must have messed it up then.

I got my app to work just by making new eframe-template and pasting my code as non-invasively as I could into it, later changing one by one the labels from template egui to my app and such, but this is weird that the above simplified version wouldn't work at all

I've been coming up against this myself while trying to run the example with almost any minimal changes. I tried removing <!DOCTYPE html> and found this helped, but things would break again after another change. Curiously I noticed in the served HTML that <!DOCTYPE html> was always appearing, regardless of whether i had removed if from the source or not, even after a complete clean and rebuild. From this I suspected trunk itself could be the issue. I packaged the files with trunk build but instead served them with a quick rocket server rather than trunk serve. Surprisingly, the UI now appeared and didn't break after making changes to the source. Additionally, <!DOCTYPE html> was now absent from the served html, matching my source.
Based on this, I think the issue could be to do with trunk, or some part of that process, but I don't have time to investigate further just at the moment.

I am having a very similar issue and have found no help or workarounds anywhere.

Encountered the same issue.
Following this comment in index.html:
    <!--Register Service Worker. this will cache the wasm / js scripts for offline use (for PWA functionality). -->
    <!-- Force refresh (Ctrl + F5) to load the latest files instead of cached files  -->

I hard refreshed http://<IP_ADDRESS>:8080/ (cmd+shift+R on chrome+mac) and it solved the problem locally.
However on the deployed site I still get a blank page, with the following error message on the console:
Uncaught TypeError: Failed to resolve module specifier "json-unix-time/json_unix_time-d2a6ab87fd2df4a7.js". Relative references must start with either "/", "./", or "../".

Did you manage to solve this? I'm experiencing the same problem with eframe_template
here is a test on github-pages:
https://aboualiaa.github.io/eframte-test/

I have the same problem - just swapped out glow with wgpu in the eframe_template built with trunk, and getting a gray blank canvas.

Sadly I haven't :( I guess sticking with older versions of egui until this is resolved is the simplest workaround...


I love this!

Hi, not an issue, just grateful. :) I've been looking for a nice TexTage-equivalent for DDR for a while now, and this is it! Thank you so much.

Thanks! Glad you find it useful!


Make the router's touch points configurable

Host and path based routing, whether for external (ingress) or internal
purposes is largely the same.  So instead of continuing to tack on more
annotations and configuration items to this router, this commit makes
the touch points configurable so you can use the same code base to run
under multiple different roles.
We also renamed the following configuration/runtime items:

The ingress secret name is now routing (by default but is configurable)
The publicPaths annotation is now routingPaths (by default but is configurable)
The trafficHosts annotation is now routingHosts (by default but is configurable)
The X-INGRESS-API-KEY header is now X-ROUTING-API-KEY (by default but is configurable)

See: #11
Subtask (renaming configuration annotations) link: https://github.com/30x/k8s-pods-ingress/issues/11#issuecomment-217002450
Subtask (making the touch points configurable) link: https://github.com/30x/k8s-pods-ingress/issues/11#issuecomment-216591635

lgtm


Restrict height of the view with the goals

When running :CornelisLoad on a file with a lot of goals, like https://github.com/martinescardo/HoTTEST-Summer-School/blob/main/Agda/Exercises/01-Exercises.lagda.md the view with the goals fills my entire window. Is it possible to restrict it to be smaller? How can this be done?
Edit: I just saw it is related to #60

Fixed in 37c04e36dd35dbca13bdada79276470bba6adddf


Rescue more errors and raise ConnectionError

These are some more errors that could occur when requesting HTML:
OpenSSL::SSL::SSLError
Errno::ETIMEDOUT
Errno::EHOSTUNREACH
Errno::ENETUNREACH
Errno::ECONNRESET
Net::OpenTimeout
SocketError
So we rescue them and raise Funky::ConnectionError

Coverage remained the same at 100.0% when pulling a570c665e2960358985c30615985e30aee220c44 on more_server_errors into 2a454d7169253083c059297170004018cc162b53 on master.

works for me

Coverage remained the same at 100.0% when pulling 87bccccb2367eba37aa3316607f90397310cfc16 on more_server_errors into 2a454d7169253083c059297170004018cc162b53 on master.

Great!

Coverage remained the same at 100.0% when pulling 87bccccb2367eba37aa3316607f90397310cfc16 on more_server_errors into 2a454d7169253083c059297170004018cc162b53 on master.


Hover Display Not Aligning with Mouse Position

Hello! Hopefully this will be an easy fix, but I can't seem to get the mouse to align with the bisect-x. Wondering if anyone else is having this issue?
Layerchart Version - 0.44.0
Svelte Version - 4.2.7
Tailwindcss Version - 3.4.9
Hover cursor over chart in this reproducible sample code shows your cursor to the right of the datapoints not allowing to overlap by about 16px. This makes it so I can't hover over the last datapoint.

Here's the Svelte REPL: https://svelte.dev/repl/bb4ac8dd5e0f48d9a37249392dcf01b3?version=4.2.19

What am I missing?
Thanks!
AskDavis

Hey @AskDavis 👋, thanks for checking out LayerChart.
I see you are using scaleBand() with bisect-x and time series (date) data.   Instead of scaleBand(), I would recommend scaleTime() or scaleUtc() and convert the date strings '2023-01-05' to Date instances, either by updating the data...
const investmentData = [
    { date: new Date('2023-01-05'), value: 5000 },
    { date: new Date('2023-01-06'), value: Math.floor(Math.random() * (8500 - 5000)) + 5000 },
    ...
  ];

processing the data...
const investmentData = [
    { date: '2023-01-05', value: 5000 },
    { date: '2023-01-06', value: Math.floor(Math.random() * (8500 - 5000)) + 5000 },
    ...
  ].map(d => ({ ...d, date: new Date(d.date) }));

or change the x accessor from
<Chart x="date" ...>

to
<Chart x={d => d.date} ...>

Note: in the upcoming Simplified Charts PR, LineChart will smartly switch between scaleLinear() and scaleTime() based on the data type of x.
Hope that gets you going.

that fixed it! amazing! thank you so much! I really love LayerChart!! amazing work and can't thank you enough :)

that fixed it! amazing! thank you so much! I really love LayerChart!! amazing work and can't thank you enough :)

You're very welcome, and glad you're enjoying it 😃.  The new simplified charts will help provider a better onboarding experience (and just generally simplifier)


Unable to install 1.22.2 upgrade

vscode-inno-updater.log
Issue Type: Bug
VSCode 1.22.1 had been running for a few hours / days. Was notified of an upgrade so clicked Update Now. It then proceeded to say that it was installing in the background. I then waited and clicked on "Update Now" when it said it had finished.
The window closed and then a dialog appeared saying I needed to re-install Visual Studio code as it couldn't upgrade.
 Did it tell you to send us a log file?

No I didn't know I needed to screenshot - assumed it would be in the log file. It did ask me to file an issue and gave me the log file name to upload.
I repeated the attempt to upgrade shortly afterwards and it crashed with a runtime exception and it also mentioned that a setup was already running. In the end I had to kill all the processes, including setup processes before trying again. That time it then worked.

Oh I just saw the log file atop the issue, sorry! That is enough yeah.

/duplicate #47815


Some information is incorrect/out of date

I am guessing a lot is out of date or incorrect, but I'm using VS Code, and there's no options further under "New", just "New File" and "New Window". I didn't bother finishing reading your article because I'm looking for the information I need, not doing free debugging for Microsoft (which I'm guessing it gets a lot of, but could use more badly).
Good day.
Mike

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d7d9f53c-6ece-ea3c-9a51-9edd0efeebe3
Version Independent ID: 9c927a8e-3ebd-0c8a-76cc-9b1c980b98a3
Content: Create projects & solutions - Visual Studio (Windows)
Content Source: docs/ide/creating-solutions-and-projects.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @TerryGLee
Microsoft Alias: tglee

@mkstarr This article is for Visual Studio, not VS Code.  You can find VS Code docs here: https://code.visualstudio.com/docs
If you have specific feedback about Visual Studio documentation, please let us know.
Have a good day.


update sqlmodel plus other dependencies

Codecov Report

Merging #38 (5b953ec) into main (58a6302) will decrease coverage by 1.77%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #38      +/-   ##
==========================================
- Coverage   89.42%   87.65%   -1.78%
==========================================
  Files           6        6
  Lines         331      324       -7
==========================================
- Hits          296      284      -12
- Misses         35       40       +5

Impacted Files
Coverage Δ

steam2sqlite/models.py
100.00% <ø> (ø)

steam2sqlite/navigator.py
68.00% <0.00%> (-20.00%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 58a6302...5b953ec. Read the comment docs.


WIP/RFC: Add GitHub actions CI config

Overview
GitHub actions offers a lot of potential for our monorepo, for a variety of reasons including but not limited to:

Some projects like PD and LL in the monorepo are relatively isolated from other projects and don't rely on the other projects' builds
The App needs to be built on Windows, macOS, and Linux
Deploys are inconsistent project to project and sometimes rely on scripts run from dev's computers
Our inter-job dependencies are more complex than Travis really allows for
Triggering workflows on a variety of GH events opens a lot of doors in terms of simplifying and automating releases and changelogs

GitHub Actions Workflow Syntax docs
Changelog

At the moment, this config is a proof of concept that replicates large chunks of our existing CI config that is current split across TravisCI and Appveyor

Review requests
See this all working live here: https://github.com/mcous/opentrons/actions
Any and all comments welcome! There's a good chance this specific PR is never merged, even if we do decide to switch to GH actions. Some of my own observations:

Feels a little slower than Travis
Multi-OS (mac, windows, Linux) seems to work pretty well
Much more expressive job dependency syntax for serialization and parallelization of sub-tasks (“jobs”) is cool
Cannot restart "jobs" individually; must restart the whole "workflow"

Risk assessment
N/A

Latest CI run in my fork: https://github.com/mcous/opentrons/actions/runs/196581941

The PR was an effective exploration and we'll likely be moving forward on a GH actions switchover for the monorepo. It'll be more split up that the monoconfiguration in this PR, so closing it and keeping the branch around as a helper for the actual PR(s) that do the switch


chore: Helm chart option to set POD container name

Fixes https://github.com/aws/karpenter-provider-aws/issues/7383
Description
Helm chart option to set POD container name.
Several of our observability tools rely on POD container name and "controller" is too much generic.
This change adds this option to values.yaml:
controller:
  # -- Distinguishing container name (containerName: karpenter-controller).
  containerName: controller

How was this change tested?
Using "helm template" to check it defaults to current setting (controller) and allows defining a new container name.
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
142 unchanged lines in 17 files lost coverage.
Overall coverage decreased (-17.3%) to 65.122%

Files with Coverage Reduction
New Missed Lines
%

pkg/providers/instancetype/instancetype.go
1
95.98%

pkg/test/options.go
1
93.33%

pkg/test/nodeclass.go
1
98.98%

pkg/test/environment.go
2
96.06%

pkg/providers/instancetype/types.go
3
96.67%

pkg/controllers/controllers.go
4
0.0%

pkg/providers/amifamily/ami.go
5
94.44%

pkg/controllers/nodeclass/hash/controller.go
5
70.49%

pkg/operator/options/options.go
6
74.29%

pkg/controllers/nodeclass/termination/controller.go
6
59.68%

Totals

Change from base Build<PHONE_NUMBER>7:
-17.3%

Covered Lines:
5732

Relevant Lines:
8802

💛  - Coveralls

this breaks when setting a different container name, fix: https://github.com/aws/karpenter-provider-aws/pull/7533


Error: 500 can't lock file

Hi,
does anyone had similar error? Any solution for that?

Error: 500 can't lock file '/var/lock/qemu-server/lock-104.conf' - got timeout

  on vm-gitlab.tf line 2, in resource "proxmox_vm_qemu" "gitlab":
   2: resource "proxmox_vm_qemu" "gitlab" {

Error: 500 can't lock file '/var/lock/qemu-server/lock-103.conf' - got timeout

  on vm-squid.tf line 2, in resource "proxmox_vm_qemu" "squid":
   2: resource "proxmox_vm_qemu" "squid" {

yup im getting that same error

Same error here. Anyone make any progress working through this one?

In my case setting parallelism to 1 solve the case. I suspect that (maybe only for me) the problem is related with disk performance. When I am creating 2-3 machines parallel it is a problem, when I create them one by one - everything works. Maybe this is related with my proxmox configuration - I have Dell Laptop with 1TB disk - this is my playground ;-)

I have the same issue with only 1 vm at a time.I have try the parameter clone_wait but even if I put 3600 it still stop at 5m10 with a timeout.
I know that my disks maybe slow but the provider should respect the timeout parameter.
Or maybe there is something else to set in terraform for this timeout...not sure. First time I try this.
Thanks

Hitting the same. I think it's an issue in proxmox where it's trying to assign multiple VMs the same ID. I'm imagining something like:
terraform starts creating vm1, requests next "free" ID from Proxmox. gets 100.
terraform starts creating vm2, requests next "free" ID from Proxmox. gets 100.
terraform starts creating vm1, proxmox's internal counter sets the next free ID to 101.
terraform tries to create vm2 with ID 100, Proxmox errors.
Would be cool to set a VM ID manually, to avoid this.

I didn't notice such behavior - it rather looked like I had 3 instances with 3 different ID but "extracting" template to VM was a problem like bottleneck with disk transfer which caused timeout. Maybe as you wrote problem is located with proxmox itself, not in a plugin...

Same error here, with only a single VM.
I'm going to create a smaller cloud-init template and try that but it would be awesome if there was another way.

Any progress / workarounds for this? Having the same issue.

@stefanvangastel   Are you attempting to clone a large VM disk here?   Looks like there are a few ideas in this ticket on what the issue could be, and so I'm curious if this due to something on the proxmox end taking longer than the code currently waits for.

A 12 gb disk. Though I try to create multiple (3) vm’s at a time. The error also seems random

Hm, I can't (yet) reproduce this on my end.   When you try running a terraform apply, can you look at the task list in proxmox?  I'm wondering if the clone is still in progress when we attempt to post the VM config.  If the clone is still occurring and terraform tries to apply a configuration update, I would expect a lock error like was posted above to happen.   If you set the clone_wait attribute in your proxmox_vm_qemu resource higher than the default of 15 seconds (say 120 seconds), does that make a difference?

I will try to do that. The lock error does occur. I’ll post my results
later
Op vr 6 nov. 2020 om 03:01 schreef Doran Smestad<EMAIL_ADDRESS>
Hm, I can't (yet) reproduce this on my end. When you try running a
terraform apply, can you look at the task list in proxmox? I'm wondering if
the clone is still in progress when we attempt to post the VM config. If
the clone is still occurring and terraform tries to apply a configuration
update, I would expect a lock error like was posted above to happen. If you
set the clone_wait attribute in your proxmox_vm_qemu resource higher than
the default of 15 seconds (say 120 seconds), does that make a difference?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Telmate/terraform-provider-proxmox/issues/173#issuecomment-722760888,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS34EXNWJ33G7HRVWP33UDSONKJHANCNFSM4NDNLMCQ
.

Aha!  Okay, I was able to reproduce this.  Looks like @rpelissi  was on the right path in suggesting the timeout parameter is not being honored somewhere.  I dropped the timeout to 5 seconds in my testing but I had to clone a massive enough VM to cause the lock error to occur after 5 minutes of waiting for the clone to finish.  I'll dive in here and update when I think I've found a solution.  In the meanwhile I do believe the clone_wait attribute should be a valid workaround.

Is this going to be fixed? This problem is still relevant

I think this is the same race condition than mentioned here (closed): #23
I'm running into this or vm conflict that are created with same id in some cases.
In my case I'm using ( 5-10) partial clones created alltogether that are really quick to spawn, that might help to reproduce the bug...
I had to forcefully use fixed vmids to solve the issue or use pm_parallel = 1

In fact this is more likely related to a lock on proxmox ve side that will prevent further operations...
cf (https://forum.proxmox.com/threads/concurrent-cloning-of-vm.97549/#post-422157)
I solved it by adding a delay for vm creation using the official time sync "hack"
https://registry.terraform.io/providers/hashicorp/time/latest/docs/resources/sleep
In my case 1s delays were  enough to prevent error 500!

this might be a proxmox VE issue in fact...

hammering proxmox with too many operations will cause a lot of problem, but lowering parallelism would fix 99% of the problems of lockfile and/or storage, the faster the system, the  higher the parallelism count!
I see a lot of people that thinks their system is an AWS datacenter, but it is not!

I am running into this issue creating 2 VM's with the same template. Setting the parallelism to 1 fixes the problem.
Naturally runs slower, but it goes through.

I'm having this problem on version = "3.0.1-rc3" creating container templates. I even specify the vmid. How do i slow down the container creation to avoid this error?

I just ran into the same problem using v3.0.1-rc4. I was creating multiple VMs in parallel cloning the same template.
I can confirm setting pm_parallel = 1 in the provider config fixes the problem.
pm_parallel defaults to 4. I guess it's probably a good idea to change these default as a bunch of other users will run right away into that problem.


Show different IDE's for project files inside the directory

What feature or improvement do you think would benefit Files?
Currently, when you have a folder open that has a git repository inside it shows in the bottom left to open it with visual studio.

First I find it odd, that it even suggest Visual Studio as an option down there as I don't have Visual Studio installed on my system.

If I click it, because I wondered it opened my Rider, which I totally like. So it somehow found my Rider installation and opened the solution.

it maybe also just tried to open it with the app, that is set as default for .sln files

Requirements
I would love if it says Rider (or any other IDE that is set as default for .sln files) instead of Visual Studio, as the statement to it is misleading and wrong in my opinion. Because it would make it better because of the following reasons:

It's misleading as it doesn't open Visual Studio at all
It would make more sense to show the actual IDE it will try to open.

If it's not possible at all to implement it a different name would be more fitting for example. Open in IDE etc. etc. pretty generic and overall fitting name.
Files Version
<IP_ADDRESS>
Windows Version
OS Build: 22621.521
Experience: 1000.22634.1000.0
Comments
No response

I was actually looking at the pull request of the implementation and it looks indeed like it, that it will use the default app for .sln files.
I don't know how much has changed since it, as I can't seem to find it in the current main branch.
https://github.com/ferrariofilippo/Files/blob/57b6240258310231ad28e414c839094a141758cb/src/Files.App/Actions/Open/OpenInVSAction.cs#L40

@Founntain the current branch only shows for VS Code. We're tracking support for changing/adding IDEs in #12857.


Mutation running twice

When we make a mutation. In the Console panel and then we go to "Schema or Explore" or another.
And then we go back to the Console. Ratel performs a new mutation. Duplicating the data.

I believe this got fixed with the history / panels redesign. Queries would run twice in the old layout but not in the new.
@MichelDiz can you please check whether this is still happening with the mutations you have?

I've Just tested on https://play.dgraph.io/ and seems to be solved.
Thanks Paul!

Fixed. Writing an e2e test to make sure this issue doesn't resurface again


When I build a project supporting DJL in Android Studio, I encounter the following error. How can I resolve it?

Description
When I build a project supporting DJL in Android Studio, I encounter the following error. How can I resolve it?
`Could not resolve all files for configuration ':app:debugRuntimeClasspath'.

Could not find ai.djl.android:core:0.26.0.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/ai/djl/android/core/0.26.0/core-0.26.0.pom
- https://repo.maven.apache.org/maven2/ai/djl/android/core/0.26.0/core-0.26.0.pom
Required by:
project :app
Could not find ai.djl.android:pytorch-native:0.26.0.
`

"When I enter the specified path, I find that it does not have version 0.26.0."

I published 0.26.0 for android. Please try it again

I published 0.26.0 for android. Please try it again

Thank you,It work


[SPARK-34469][K8S] Ignore RegisterExecutor when SparkContext is stopped

What changes were proposed in this pull request?
This PR aims to make KubernetesClusterSchedulerBackend ignore RegisterExecutor message when SparkContext is stopped already.
Why are the changes needed?
If SparkDriver is terminated, the executors will be removed by K8s automatically.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the newly added test case.

Test build #135255 has started for PR 31587 at commit b2a34f8.

Test build #135255 has finished for PR 31587 at commit b2a34f8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135255/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39835/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39835/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/39835/

Thank you, @viirya !

This is backported to branch-3.1 to fix a bug situation when the late arrival executor pods causes a delay of SparkContext.stop.


The program doesn't recognize installed frameworks.

From the link, I downloaded SDK which included the necessary runtimes however program always prompts me to get it.

try open cmd and run dotnet --list-sdks and dotnet --list-runtimes and show results

[cid:78d015dd-7fbb-481d-8311-7a225c6bd717]
Here you go, thank you.

Gönderen: Johan Hellgren @.>
Gönderildi: 9 Mart 2023 Perşembe 01:26
Kime: isJuhn/KAMI @.>
Bilgi: UberZer0 @.>; Author @.>
Konu: Re: [isJuhn/KAMI] The program doesn't recognize installed frameworks. (Issue #76)
try open cmd and run dotnet --list-sdks and dotnet --list-runtimes and show results
—
Reply to this email directly, view it on GitHubhttps://github.com/isJuhn/KAMI/issues/76#issuecomment-1460962287, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHY4LJWVPJVJNRHDV7KISE3W3EBR5ANCNFSM6AAAAAAVTEMJDQ.
You are receiving this because you authored the thread.Message ID: @.***>

Here you go, I think sending it by mail somehow made it worse.

I guess maybe latest release is still on .net 6 (we have no automatic release pipeline) try downloading the artifacts for the top result in the Actions tab. Or build from source. Or install .net 6.

That one worked, thank you.