Merge methods for randomizing state variables in canonicalCaseMap

In the canonicalCaseMap.py script there is an option to chose the simulated state randomly and there is often a desire to use identical sets of randomly selected values over multiple runs. This is currently accomplished in two ways:

By passing the defineRandom variable which contains a set of random values generated in runRetrievalSimulation.py and then passed up the stack through setupConCaseYAML() to conCaseDefinitions().
By using a constant seed for the random generator at the top of the script (rnd.default_rng(seed=33)).

We should pick just one approach and reduce the redundancy.

Also, approach (1) was created by Greema and then merged into the Main branch by @ReedEspinosa as part of commit cb3fbdd/


relm4::app::RelmApp::run_async catches cli args which causes panic

As title says, the relm4::app::RelmApp::run_async function catches the arguments, I pass to my application.
I've migrated my app from relm4 version 0.5 to 0.9, and noticed that change in behavior.
While I was running the app like this, and everything worked perfectly well:
fn main() {
    let args = Args::parse();
    // Keep the guard alive till the end of the function, since logging depends on this.
    let _guard = init_logging(&args.log_level);

    let app = relm4::RelmApp::new(APP_ID);
    app.run_async::<Greeter>(GreeterInit {
        config_path: args.config,
        css_path: args.style,
        demo: args.demo,
    });
}

After migration, this code still works... sometimes. However, after addition of --demo argument to application, it's been noted, that app fails to run with error:
Unknown option --demo

Even though clap read args correctly.
It seems like the call to gio::application::ApplicationExtManual::run in a relm4::app::RelmApp::run_async function forces the attempt to parse the arguments:
    fn run(&self) -> ExitCode {
        self.run_with_args(&std::env::args().collect::<Vec<_>>())
    }

which fails, since gio doesn't know about my app's arguments, but parses them, gets some demo and kills itself.
In relm4's 0.5 version, the relm4::app::RelmApp::run_async function just called gio's run_with_args function, and it didn't trigger arguments search, which worked perfectly well.
So, for now, as a dirty hack, I'm starting my application by initializing the empty args vector:
    app.with_args(vec![]).run_async::<Greeter>(GreeterInit {
        config_path: args.config,
        css_path: args.style,
        demo: args.demo,
    });

But it doesn't seem to me like a right thing to do

Sorry for responding so late, I somehow missed the notification.

So, for now, as a dirty hack, I'm starting my application by initializing the empty args vector

This has been the recommended approach. Relm4 hasn't tried to change the default behavior of gio in this case, so that's how things work currently.
That said, it makes more sense to me to make this more explicit. If you just build an app, add clap and parse CLI options, you should not run into problems by default. So I propose the following API:

If you don't do anything special, gio won't receive any CLI args (so no "dirty hack" is necessary anymore).
If you want to pass specific args to gio, it's going to be the same as it is now.
If you want to pass all args to gio (which is currently the default), you can use a with_default_args() method in the app builder.

That's how it used to be and I think this is the best approach.


fixes TreeMap.of(Comparator, KVKV) signature

Current coverage is 97.10% (diff: 100%)

Merging #1690 into master will not change coverage

@@             master      #1690   diff @@
==========================================
  Files            89         89
  Lines         11243      11243
  Methods           0          0
  Messages          0          0
  Branches       1886       1886
==========================================
  Hits          10918      10918
  Misses          181        181
  Partials        144        144

Powered by Codecov. Last update 541afa8...a274a51

Thank you! I will pull it in despite of Sputnik remarks. We need to tweak the Sputnik config later...


Would be nice when updating multiple boards to not have to press "ok" between each board updating

When there are multiple boards connected the update process requires that the user clicks OK after every successful (or not successful) update.

[x] Multiple boards update process is initiated by user during start up
[x] Multiple boards are update in one row without any user interaction
[x] After a successful update a message is displayed
[x] After an unsuccessful update a message is displayed indicating which board had a problem
[x] A single board can be updated from the Board Settings Menu
[x] Localization if needed

we noticed that a timeout can still occur when avrdude is not terminating and then the upload process would get stuck.


Neural Morphology for Translation Lookup

See https://github.com/lilt/core/issues/412 for experimental results.


docs: add development docs

cc @baparham

I think it's worth highlighting that we like to check a patch by building the binaries as well, since sometimes the patches don't build even if they apply cleanly

I think it's worth highlighting that we like to check a patch by building the binaries as well, since sometimes the patches don't build even if they apply cleanly

Do you mean this?
https://github.com/yao-pkg/pkg-fetch/blob/549db84226b6a4987f684d4af254560205c523a8/lib/bin.ts#L54-L57


chore: cleanup yarn.lock to bump browserslist

closes #1590
No more confusing stdout (for now)

CI is ok, just failed on the coveralls step. I will make that not fail builds today.


Add support to mute unneeded Artisan commands from summary

I guess this closes #5

Great job so far!

Thank you! Adjusted those things. Should I somehow squash those commits now?

Don't worry about the commit messages, at the end we squash them.

@nunomaduro can you please review the changes and let me know if there's anything else to be done? Thanks!

Thanks!


[WIP] Added initial GitHub issue search feature

When fastlane ends with an error (both crashes and user error) it will now automatically search for relevant GitHub issues using the GitHub search API. This should reduce the number of incoming issues.
User Error: Found 1 issue

User Error: Found more issues

On fastlane crashes (never happens obviously)

Thanks @orta for working on the initial gem 👍
Depends on https://github.com/orta/gh-issues-inspector/pull/7
CocoaPods sibling PR: https://github.com/CocoaPods/CocoaPods/pull/5421

Coverage decreased (-0.002%) to 66.888% when pulling 4168191e393444430ff6c708c8a6c6308f719756 on issue-search into 551b0eea99171caf1190c9f536d814aa75c1ccba on master.

This is 💯 !! Just a couple small questions and 👍

Sorry @ohwutup, forgot to add [WIP] to the title

Coverage decreased (-0.008%) to 66.882% when pulling ac961b3a82b977eecb0a33b00d9e0f5d60313b14 on issue-search into 551b0eea99171caf1190c9f536d814aa75c1ccba on master.

Coverage decreased (-0.01%) to 66.878% when pulling 8bf5e233de523644fddbfee49abf960df2f63df4 on issue-search into 551b0eea99171caf1190c9f536d814aa75c1ccba on master.

Coverage decreased (-0.02%) to 66.872% when pulling d0b65d6496529578bc86f3117afb72c8f2a752d4 on issue-search into 551b0eea99171caf1190c9f536d814aa75c1ccba on master.

👍


Add link to Swift.org documentation in UserManual.md

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves #NNNNN, fix apple/llvm-project#MMMMM.

@swift-ci please smoke test.

@swift-ci please smoke test macOS platform


feat: add form elements design tokens

Summary | Résumé
Adding new (and temporary) tokens for the form elements colours as well as the form font-family.

Closing PR in favour of new tokens.


(librecad) Switch to using new GitHub API helper

Description
This pull request updates the automatic updater to make use of our new GitHub API helper to get the releases available.
This allows this package to once again be pushed to Chocolatey Community Repository.
Additionally, a small change to include the already pushed versions of 2.1 and 2.0 has been added, without having these added and if we need to create a fix version we would first need to add these manually or explicitly set the version to use.
fixes #2194
Motivation and Context
To make the automatic updater work again.
How Has this Been Tested?

Run .\update_all.ps1 librecad
Verify a package was created for 2.2.0
Run .\update_all.ps1 librecad -ForcedPackages librecad\2.1
Verify a fix version for version 2.1.3 was created

Screenshot (if appropriate, usually isn't needed):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] I have updated the package description and it is less than 4000 characters.
[x] All files are up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment (only update.ps1 is affected here, so install/uninstall has not been checked).
[x] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review


Update scodec-core to 1.11.3

Updates org.scodec:scodec-core from 1.11.2 to 1.11.3.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a nice day!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [{ groupId = "org.scodec", artifactId = "scodec-core" }]

Need to fix this https://travis-ci.org/laserdisc-io/laserdisc/jobs/500535410#L539 before bumping


Default to latest ECS-Optimized AMI

Default to latest ECS-Optimized AMI
Added ECSAMI parameter which defaults to latest ECS-Optimized AMI
Removed legacy AMI Mappings
Pull Request #88
Thanks @mrichman for the pointer :)

You're welcome!

Closing as duplicate of #61


Add possibility to change node drain duration

Add possibility to change duration of node drain
litmus chaos test. This is needed for CNFs with
longer startup/shutdown.
Additionally, fix litmus waiter code and timeout module. Slight refactor of LitmusManager module.
Refs: #2098
How has this been tested:

[ ] Covered by existing integration testing
[ ] Added integration testing to cover
[ ] Verified all A/C passes

[ ] develop
[ ] master
[ ] tag/other branch

[ ] Test environment

[ ] Shared Packet K8s cluster
[ ] New Packet K8s cluster
[ ] Kind cluster

[ ] Have not tested

Types of changes:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

Checklist:
Documentation

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] No updates required.

Code Review

[ ] Does the test handle fatal exceptions, ie. rescue block

Issue

[ ] Tasks in issue are checked off


Link for (bank reconciliation import file technical layout definitions and..) fails with "ERR_CONNECTION_CLOSED"

Hi, the link for "Below are examples of the advanced bank reconciliation import file technical layout definitions and three related bank statement example files: https://mbs.microsoft.com/customersource/northamerica/AX/learning/documentation/how-to-articles/exofbankstfotechlayouts"
fails with ERR_CONNECTION_CLOSED in chrome, firefox and IE

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

ID: e05abef3-f815-21a0-eedb-e67901e5bf99
Version Independent ID: c4556269-06f3-177a-7da7-1de63eea835b
Content: Set up the advanced bank reconciliation import process - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/financials/cash-bank-management/set-up-advanced-bank-reconciliation-import-process.md
Service: dynamics-ax-applications
GitHub Login: @ShylaThompson
Microsoft Alias: saraschi

@gaggaz12, thanks for making us aware of this issue.
@ShylaThompson, can you please fix the link?

@gaggaz12 the link works now. CustomerSource went through maintenance last week, which was likely why the link was broken for you. Please try again.


Swift 3 update

Hey, great little library. Any idea if / when a compatible swift 3 will be released? The lw/swift-3 branch doesn't work for me.

Same question here! @LoganWright will you be finishing up lw/swift-3? I tried to use that branch in my project but there still seems to be issues with syntax. If not, any pointers as to what we should use as a replacement would be awesome!

@thedistricts @KileyCaravella I have not been maintaining this library for some time. Unfortunately, there are some very complex and nuanced json things that need to be done and I don't know the whole spec as well so haven't been able to dig in and update. I was mostly just keeping things up to date in here. I'd recommend looking into Jay which won't crash on obscure emoji.


Add sponsor team pictograms and use in detail pages

[ ] Add the pictograms from the two zip files in https://github.com/carbon-design-system/carbon-platform/issues/284 to the platform icon Sketch file and icon package
[ ] Add pictograms to each team in /data/teams.js
[ ] Render sponsor pictogram instead of icon in the library detail page and asset detail page

Hey team! Please add your planning poker estimate with ZenHub @alisonjoseph @francinelucca

I added the new pictograms to the Sketch file: https://ibm.ent.box.com/file/887827201496
This could probably be dropped to a small sizing.


Add rules_jvm_external 6.0

We should be bumping the compatibility level for this release

We should be bumping the compatibility level for this release

Could you describe the nature of the incompatibility? Based just on the release notes for 6.0 it doesn't look like the Bzlmod API meaningfully changed.

We dropped support for jetifier. This will change the output of the generated build files which some rulesets (such as contrib_rules_jvm) have "frozen" into their own repos as zip files. Without this, we risk causing those projects to resolve a version of rules_jvm_external that will cause their builds to break.

Luckily I think that the current versions of contrib_rules_jvm don't actually use their frozen deps with Bzlmod, they always fetch them with coursier. I discovered this with @illicitonion. If that's indeed the case and thus no modules in the BCR would be broken by this change, I would personally recommend not bumping the compatibility level, which would cause churn for all downstream projects adopting a new version.

If you think it's safe, I'll patch things to remove the compat level change.

I can test this later today.

Tested this with a project that also uses contrib_rules_jvm, everything worked as expected. There don't appear to be any other potential usages for this in the BCR, which means that this breaking change can only end up breaking end users - which would be unconditionally broken if we bumped the compatibility_level.

This doesn't seem to work with Bazel 6.4.0.
ERROR: https://bcr.bazel.build/modules/rules_jvm_external/6.0/MODULE.bazel:65:13: name 'use_repo_rule' is not defined

@shs96c You could add a bazel_compatibility attribute to the module call to give users a better error message. This is one of the very few changes we could even make to the existing version 6.0.

I can add that for the next release.


software_spec: fix bottle domain fallback handling

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

If we are using a non-GHCR HOMEBREW_BOTTLE_DOMAIN, then we can't use the download strategy mirror system as the URLs etc will all be different.
Instead we have to catch the error and reconstruct the URL before sending another fetch.

Review period will end on 2021-04-16 at 17:08:32 UTC.

Review period skipped due to critical label.

Thanks, @Bo98.


Integrate UpdaterTest from parse-composer

We remove the UpdaterTest from parse-composer to simplify the dependencies graph. Lets add it to drupal-packagist again.
Related PR: drupal-composer/drupal-parse-composer#10

Duplicate of #12


Implement visualize!

resolve #58
visualize!(axis3, obj3) add obj3 to the plot object of axis3

Can you add docstring to newly added functions and then add reference here.

Codecov Report

Merging #59 (438c4ff) into master (fb78320) will decrease coverage by 1.06%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #59      +/-   ##
==========================================
- Coverage   85.49%   84.42%   -1.07%
==========================================
  Files          21       21
  Lines        1027     1040      +13
==========================================
  Hits          878      878
- Misses        149      162      +13

Impacted Files
Coverage Δ

src/visualize.jl
0.00% <0.00%> (ø)

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 fb78320...438c4ff. Read the comment docs.

LGTM. Thanks @terasakisatoshi

This is great!

@DhairyaLGandhi  No, didn't had tests for visualize also. Any way we can include tests for plotting functions?

I would see Makies test suite and try to modify it to our use case.


Crash on Unknown Device Type

I found a crash due to unknown device types.
I have the Siren Alarm, Key Fob and Gate Sensors that were causing a type error to be thrown and eventually homebridge crashes. If I create entries for the unsupported devices and select hide from HomeKit then the errors stop and the server can start.
I've added some logs, but even with verbose it isn't horribly useful. Additionally, we can probably do some work to get you the data you need to add these devices.

Here are some logs ...
[8/9/2022, 3:50:57 PM] Homebridge v1.5.0 (HAP v0.10.2) (Homebridge 2E75) is running on port 51089.
[8/9/2022, 3:50:57 PM] [Sonos] listening on http://<IP_ADDRESS>:38171/notify
[8/9/2022, 3:50:57 PM] [Sonos] hardware: x64
[8/9/2022, 3:50:57 PM] [Sonos] os: Fedora Linux 36 (Server Edition)
[8/9/2022, 3:50:57 PM] [Sonos] restored 1 accessories from cache
[8/9/2022, 3:50:58 PM] [Sonos] closed http://<IP_ADDRESS>:38171/notify
[8/9/2022, 3:50:58 PM] [Sonos] listening on http://<IP_ADDRESS>:38171/notify
[8/9/2022, 3:50:58 PM] [Sonos] found 1 households
[8/9/2022, 3:50:58 PM] [Sonos] Sonos_waguiZ5EVj6BaqwBKYRIyOwwsC: RINCON_7828CAA54E7401400 [<IP_ADDRESS>]: associated S2 zoneplayer
[8/9/2022, 3:50:58 PM] [YoLink] Access Token expires in 7200 seconds. We will refresh on requests after 6480 seconds
[8/9/2022, 3:50:58 PM] [YoLink] Starting heartbeat to force access token refresh every 6840 seconds
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getHomeId
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceList
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Dining Room Motion Sensor(d88b4c0200024a1d)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Dining Room Motion Sensor (d88b4c0200024a1d) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Front Door Motion Sensor(d88b4c02000249d2)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Front Door Motion Sensor (d88b4c02000249d2) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Garage Freezer Thermostat(d88b4c020005c67a)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Garage Freezer Thermostat (d88b4c020005c67a) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Garage Motion Sensor(d88b4c020002f248)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Garage Motion Sensor (d88b4c020002f248) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Guest Bath Leak Sensor(d88b4c0200052887)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Guest Bath Leak Sensor (d88b4c0200052887) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Guest Bath Leak Sensor 2(d88b4c02000682c4)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Guest Bath Leak Sensor 2 (d88b4c02000682c4) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Guest Bath Leak Sensor 3(d88b4c0200068297)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Guest Bath Leak Sensor 3 (d88b4c0200068297) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Hot Water Tank Leak Sensor(d88b4c02000682c9)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Hot Water Tank Leak Sensor (d88b4c02000682c9) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Kitchen Freezer Thermostat(d88b4c0200055501)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Kitchen Freezer Thermostat (d88b4c0200055501) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Kitchen Leak Sensor(d88b4c0200053460)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Kitchen Leak Sensor (d88b4c0200053460) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Kitchen Motion Sensor(d88b4c020002f130)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Kitchen Motion Sensor (d88b4c020002f130) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Living Room Motion Sensor(d88b4c02000248bd)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Living Room Motion Sensor (d88b4c02000248bd) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Master Bath Sink(d88b4c0200053451)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Master Bath Sink (d88b4c0200053451) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Master Bath Toilet Leak Sensor(d88b4c020005286d)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Master Bath Toilet Leak Sensor (d88b4c020005286d) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Restroom Leak Sensor(d88b4c0200053c34)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Restroom Leak Sensor (d88b4c0200053c34) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Restroom Sink Leak(d88b4c02000533c1)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Restroom Sink Leak (d88b4c02000533c1) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: Utility Room Motion Sensor(d88b4c020002efe4)
[8/9/2022, 3:50:58 PM] [YoLink] Data refresh timer for Utility Room Motion Sensor (d88b4c020002efe4) fired
[8/9/2022, 3:50:58 PM] [YoLink] Restoring accessory from cache: YoLink Fob(d88b4c0100038868)
[8/9/2022, 3:50:58 PM] TypeError: Cannot read properties of undefined (reading 'warn')
at new YoLinkPlatformAccessory (/usr/lib/node_modules/homebridge-yolink/src/platformAccessory.ts:58:16)
at YoLinkHomebridgePlatform.discoverDevices (/usr/lib/node_modules/homebridge-yolink/src/platform.ts:175:25)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Dining Room Motion Sensor (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Dining Room Motion Sensor' (d88b4c0200024a1d)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Front Door Motion Sensor (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Front Door Motion Sensor' (d88b4c02000249d2)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Garage Freezer Thermostat (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Garage Freezer Thermostat' (d88b4c020005c67a)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Garage Motion Sensor (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Garage Motion Sensor' (d88b4c020002f248)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Guest Bath Leak Sensor (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Guest Bath Leak Sensor' (d88b4c0200052887)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Guest Bath Leak Sensor 2 (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Guest Bath Leak Sensor 2' (d88b4c02000682c4)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Guest Bath Leak Sensor 3 (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Guest Bath Leak Sensor 3' (d88b4c0200068297)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Hot Water Tank Leak Sensor (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Hot Water Tank Leak Sensor' (d88b4c02000682c9)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Kitchen Freezer Thermostat (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Kitchen Freezer Thermostat' (d88b4c0200055501)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Kitchen Leak Sensor (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Kitchen Leak Sensor' (d88b4c0200053460)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Kitchen Motion Sensor (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Kitchen Motion Sensor' (d88b4c020002f130)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Living Room Motion Sensor (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Living Room Motion Sensor' (d88b4c02000248bd)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Master Bath Sink (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Master Bath Sink' (d88b4c0200053451)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Master Bath Toilet Leak Sensor (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Master Bath Toilet Leak Sensor' (d88b4c020005286d)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Restroom Leak Sensor (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Restroom Leak Sensor' (d88b4c0200053c34)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Restroom Sink Leak (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Restroom Sink Leak' (d88b4c02000533c1)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState for Utility Room Motion Sensor (refresh after 14500 seconds)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getDeviceState for 'Utility Room Motion Sensor' (d88b4c020002efe4)
[8/9/2022, 3:50:58 PM] [YoLink] YoLinkAPI.getAccessToken
[8/9/2022, 3:50:58 PM] Got SIGTERM, shutting down Homebridge...
[8/9/2022, 3:50:58 PM] [Sonos] closed http://<IP_ADDRESS>:38171/notify
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState received data for Front Door Motion Sensor (d88b4c02000249d2)
[8/9/2022, 3:50:58 PM] [YoLink] Device state for Front Door Motion Sensor (d88b4c02000249d2) is: normal
[8/9/2022, 3:50:58 PM] [YoLink] Set data refresh timer for Front Door Motion Sensor (d88b4c02000249d2) to run in 14500 seconds
[8/9/2022, 3:50:58 PM] [YoLink] checkDeviceState received data for Garage Motion Sensor (d88b4c020002f248)

Thanks for reporting the bug.  Crash is bad, I had intended to gracefully report when an unknown device was found, clearly I don't have it right yet.
Can you turn on debug please (in the UI select ... menu at top right, then homebridge settings, and turn on debug mode) then (without hiding any device) capture for me the debug statements for each of the devices that start with "SENDING:" and "RECEIVED:" this will tell me what YoLink is sending back for each device and with that I can start to add support for them.
Thanks
David.

I know how to handle this in python and raise the error rather then let TypeError bubble up, but I can't offer much 'good' help in js.
I have scrubbed the log. I'm a little worried about the response back. Worst case, I may need to enable each failing device and get you a new log for each one.
here is a map of the unknown devices to keep things sane.
Name: Front Gate
EUI: d88b4c010003e4d9
Model: YS7707-UC
Type: Door Sensor
Name: Side Gate
EUI: d88b4c0100043de0
Model: YS7707-UC
Type: Door Sensor
Name: YoLink Fob
Type: YoLink Fob
EUI: d88b4c0100038868
Model: YS3604-UC
Name: Siren Alarm
Type: Siren Alarm
EUI: d88b4c010003b80d
Model: YS7103-UC
homebridge.log

Okay, so I see why it crashed, my fault.  Let me push a fix for that so it doesn't crash.  Then I can work with you on adding support for those new devices.

I have (hopefully) fixed the crash in version 1.0.7 that I just published.  Please install that.  I have also opened three new issues to track adding support for the door sensor, siren and key fob.  Please add into those issues the details I need to implement support... specifically the logs that give me the SENDING and RECEIVED data, plus any MQTT messages that are received, I need those too (pressing a button on your key fob should generate a MQTT message), triggering a gate open/close should also generate message, etc.

Will do.. I will even generate a siren alarm as much as it pains me.

Here is the log after removing devices and restarting.
Somehow, only my last update went through.  I will generate the events in the next log.
Build is working.
homebridge.log

Thanks for the log.  There is enough here for me to get the skeleton in place to support these devices.  Please wait a few days for that, I'll get back to you when I'm ready for next test.


Due to db session timeout (1h), create short db session for long process (import/copy study, import output)

To close because there is another more recent issue on the subject.


DXGI_ERROR_DEVICE_REMOVED Error

hello, i have a problem. I don't know if anyone has had this problem. I have a Vega8, the drivers are all installed correctly but it is giving the error DXGI_ERROR_DEVICE_REMOVED when I try to run the following script.
import tensorflow.compat.v1 as tf
tf.enable_eager_execution (tf.ConfigProto (log_device_placement = True))
print (tf.add ([1.0, 2.0], [3.0, 4.0]))

I've already followed the instructions on the link https://aka.ms/tfdmltimeout but it doesn't work.
2021-03-31 11: 29: 36.810513: I tensorflow / stream_executor / platform / default / dso_loader.cc: 98] Successfully opened dynamic library C: \ Users \ d.belgd \ Miniconda3 \ envs \ directml2 \ lib \ site-packages \ tensorflow_core \ python / directml.bdb07c797e1e1af1b4a42d21c67ce5494d73991459.dll
2021-03-31 11: 29: 36.917148: I tensorflow / core / common_runtime / dml / dml_device_cache.cc: 126] DirectML device enumeration: found 1 compatible adapters.
[PhysicalDevice (name = '/ physical_device: DML: 0', device_type = 'DML')]
2021-03-31 11: 29: 36.920996: I tensorflow / core / platform / cpu_feature_guard.cc: 142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2021-03-31 11: 29: 36.925428: I tensorflow / core / common_runtime / dml / dml_device_cache.cc: 109] DirectML: creating device on adapter 0 (AMD Radeon (TM) Vega 8 Graphics)
2021-03-31 11: 29: 37.129830: And tensorflow / core / common_runtime / dml / dml_heap_allocator.cc: 53] The DirectML device has encountered an unrecoverable error (DXGI_ERROR_DEVICE_REMOVED). This is most often caused by a timeout occurring on t the GPU. Please visit https://aka.ms/tfdmltimeout for more information and troubleshooting steps.
2021-03-31 11: 29: 37.136448: F tensorflow / core / common_runtime / dml / dml_heap_allocator.cc: 53] HRESULT failed with 0x887a0005: hr

I think this is the problem when I try to run
python detect_video.py --video data/grca-trainmix_1280x720.mp4 --trace --max_frames 10 --headless

WARNING:tensorflow:From detect_video.py:39: The name tf.keras.backend.get_session is deprecated. Please use tf.compat.v1.keras.backend.get_session instead.

W0331 13:51:28.546197  3820 module_wrapper.py:139] From detect_video.py:39: The name tf.keras.backend.get_session is deprecated. Please use tf.compat.v1.keras.backend.get_session instead.

2021-03-31 13:51:28.806023: I tensorflow/stream_executor/platform/default/dso_loader.cc:98] Successfully opened dynamic library C:\Users\d.belgd\Miniconda3\envs\directml2\lib\site-packages\tensorflow_core\python/directml.bdb07c797e1af1b4a42d21c67ce5494d73991459.dll
2021-03-31 13:51:28.933164: I tensorflow/core/common_runtime/dml/dml_device_cache.cc:126] DirectML device enumeration: found 1 compatible adapters.
2021-03-31 13:51:28.936741: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2021-03-31 13:51:28.940855: I tensorflow/core/common_runtime/dml/dml_device_cache.cc:109] DirectML: creating device on adapter 0 (AMD Radeon(TM) Vega 8 Graphics)
WARNING:tensorflow:From detect_video.py:46: The name tf.RunOptions is deprecated. Please use tf.compat.v1.RunOptions instead.

W0331 13:51:29.155223  3820 module_wrapper.py:139] From detect_video.py:46: The name tf.RunOptions is deprecated. Please use tf.compat.v1.RunOptions instead.

WARNING:tensorflow:From C:\Users\d.belgd\Miniconda3\envs\directml2\lib\site-packages\tensorflow_core\python\ops\resource_variable_ops.py:1630: calling BaseResourceVariable.__init__ (from tensorflow.python.ops.resource_variable_ops) with constraint is deprecated and will be removed in a future version.
Instructions for updating:
If using Keras pass *_constraint arguments to layers.
W0331 13:51:29.190702  3820 deprecation.py:506] From C:\Users\d.belgd\Miniconda3\envs\directml2\lib\site-packages\tensorflow_core\python\ops\resource_variable_ops.py:1630: calling BaseResourceVariable.__init__ (from tensorflow.python.ops.resource_variable_ops) with constraint is deprecated and will be removed in a future version.
Instructions for updating:
If using Keras pass *_constraint arguments to layers.
Traceback (most recent call last):
  File "detect_video.py", line 148, in <module>
    app.run(main)
  File "C:\Users\d.belgd\Miniconda3\envs\directml2\lib\site-packages\absl\app.py", line 303, in run
    _run_main(main, args)
  File "C:\Users\d.belgd\Miniconda3\envs\directml2\lib\site-packages\absl\app.py", line 251, in _run_main
    sys.exit(main(argv))
  File "detect_video.py", line 65, in main
    yolo.load_weights(FLAGS.weights)
  File "C:\Users\d.belgd\Miniconda3\envs\directml2\lib\site-packages\tensorflow_core\python\keras\engine\training.py", line 182, in load_weights
    return super(Model, self).load_weights(filepath, by_name)
  File "C:\Users\d.belgd\Miniconda3\envs\directml2\lib\site-packages\tensorflow_core\python\keras\engine\network.py", line 1339, in load_weights
    pywrap_tensorflow.NewCheckpointReader(filepath)
  File "C:\Users\d.belgd\Miniconda3\envs\directml2\lib\site-packages\tensorflow_core\python\pywrap_tensorflow_internal.py", line 877, in NewCheckpointReader
    return CheckpointReader(compat.as_bytes(filepattern))
  File "C:\Users\d.belgd\Miniconda3\envs\directml2\lib\site-packages\tensorflow_core\python\pywrap_tensorflow_internal.py", line 889, in __init__
    this = _pywrap_tensorflow_internal.new_CheckpointReader(filename)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Unsuccessful TensorSliceReader constructor: Failed to get matching files on ./checkpoints/yolov3.tf: Not found: FindFirstFile failed for: ./checkpoints : The system cannot find the path specified.
; No such process

Good to hear, and thanks for the dxdiag! I'll open a bug internally to see if we can improve this experience so it's not necessary to set an environment variable.

One more thing to add - if you're still seeing the error with the yolov3 sample, don't forget to run setup.py first before trying detect_video.py, because it looks like it's having trouble finding the checkpoint file. :)

@jstoecker really with the memory allocation it worked, now one thing I saw, was that detect-video.py is using shared memory and not dedicated memory. Do you know that directml supports access to dedicated memory? I ask this because the detection of the objects is very slow

In short: yes, DirectML supports access to dedicated memory!
DirectML itself doesn't allocate memory for GPU resources: that's up to the application/framework using it, such as TensorFlow-DirectML (TFDML) in this case. TFDML has a number of allocators for different purposes, but the bulk of the memory (to store the tensors used in GPU calculations) will be backed by subregions of a so-called default heap. Default heaps reflect different memory pools based on the GPU architecture (UMA or NUMA/discrete).
Your Radeon Vega 8 is an integrated GPU, so the 2GB of dedicated memory you see isn't physical VRAM but rather reserved system memory. In other words, your system actually has 8GB of RAM, but the integrated GPU is claiming 2GB of it for exclusive access. This blog explains some of the differences between dedicated and shared memory, how they are reported in task manager, and some differences between discrete and integrated GPUs in this respect.
Integrated GPUs are, unfortunately, not going to be particularly fast in machine learning. It's worth pointing out that we haven't really optimized TFDML for integrated GPUs (e.g. we could avoid some memory copies since default-heap resources will always live in the "L0" memory pool); however, it's unlikely that you'll see huge performance gains over the CPU without using a more powerful discrete GPU.


[feat]: enable host aliases in common chart

What this PR does:

Adds option to  Adding entries to Pod /etc/hosts with HostAliases

Notes for Reviewer:
Checklist:

[ ] Pull Request title in format [chart]: Changed Something
[ ] Updated documentation in the  README.md.gotmpl file and executed helm-docs
[ ] Chart Version bumped
[ ] All commits are signed-off

Please pay attention to the Checklist in this PR.
Also in my opinion this is a feature bump and not a bugfix bump of the helm chart.


Merge methylation calling from different runs!

Dear Jared,
would it be possible to merge read.fa (nanopolish extract) from different runs? I would like to run nanopolish call-methylation with the merged file. If yes, it would be great if you could recommend me the best way to merge *.fa file!
Thanks in advance!
Hai

Sorry I missed this issue. You can merge runs by simply cating the fasta files together.
Jared

Thanks Jared, I'll try!
Hai


Custom LifecycleHook Pods not deleted & Task phase not updated

Checklist

[x] Double-checked my configuration.
[x] Tested using the latest version.
[x] Used the Emissary executor.

Summary
Tasks phases from Custom LifecycleHook's at a workflow level are not being updated after completion. This results in the phase being stuck in 'Pending' & the hook pod not being deleted when the workflow has the following spec
  podGC:
    strategy: OnPodCompletion

Workflow details:
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  annotations:
    workflows.argoproj.io/pod-name-format: v1
  creationTimestamp: "2022-04-01T10:27:26Z"
  generateName: lifecycle-hook-tmpl-level-
  generation: 4
  labels:
    workflows.argoproj.io/completed: "true"
    workflows.argoproj.io/phase: Failed
    workflows.argoproj.io/resubmitted-from-workflow: lifecycle-hook-tmpl-level-nddnn
    workflows.argoproj.io/workflow-archiving-status: Archived
  name: lifecycle-hook-tmpl-level-dq5bd
  namespace: argo
  resourceVersion: "334749933"
  uid: 01acc8ce-7075-48e1-b0a1-3995bcd18a94
spec:
  arguments: {}
  entrypoint: main
  hooks:
    failed:
      arguments: {}
      expression: workflow.status == "Failed"
      template: echo-save
  nodeSelector:
    nodeGroup: argo
  podGC:
    strategy: OnPodCompletion
  serviceAccountName: argo-workflows
  templates:
  - inputs: {}
    metadata: {}
    name: main
    outputs: {}
    steps:
    - - arguments: {}
        name: step-1
        template: echo-save
    - - arguments: {}
        name: step2
        template: echo
  - container:
      args:
      - echoss "it was heads"
      command:
      - sh
      - -c
      image: alpine:3.6
      name: ""
      resources: {}
    inputs: {}
    metadata: {}
    name: echo
    outputs: {}
  - container:
      args:
      - echo "it was heads"
      command:
      - sh
      - -c
      image: alpine:3.6
      name: ""
      resources: {}
    inputs: {}
    metadata: {}
    name: echo-save
    outputs: {}
  - http:
      url: https://raw.githubusercontent.com/argoproj/argo-workflows/4e450e250168e6b4d51a126b784e90b11a0162bc/pkg/apis/workflow/v1alpha1/generated.swagger.json
    inputs: {}
    metadata: {}
    name: http
    outputs: {}
  tolerations:
  - effect: NoSchedule
    key: nodeGroup
    value: argo
status:
  artifactRepositoryRef:
    artifactRepository:
      *
    default: true
  conditions:
  - status: "False"
    type: PodRunning
  - status: "True"
    type: Completed
  finishedAt: "2022-04-01T10:27:46Z"
  message: child 'lifecycle-hook-tmpl-level-dq5bd-2503513326' failed
  nodes:
    lifecycle-hook-tmpl-level-dq5bd:
      children:
      - lifecycle-hook-tmpl-level-dq5bd-2217863861
      - lifecycle-hook-tmpl-level-dq5bd-3701634578
      displayName: lifecycle-hook-tmpl-level-dq5bd
      finishedAt: "2022-04-01T10:27:46Z"
      id: lifecycle-hook-tmpl-level-dq5bd
      message: child 'lifecycle-hook-tmpl-level-dq5bd-2503513326' failed
      name: lifecycle-hook-tmpl-level-dq5bd
      outboundNodes:
      - lifecycle-hook-tmpl-level-dq5bd-2503513326
      phase: Failed
      progress: 1/3
      resourcesDuration:
        cpu: 5
        memory: 5
      startedAt: "2022-04-01T10:27:26Z"
      templateName: main
      templateScope: local/lifecycle-hook-tmpl-level-dq5bd
      type: Steps
    lifecycle-hook-tmpl-level-dq5bd-798385017:
      boundaryID: lifecycle-hook-tmpl-level-dq5bd
      children:
      - lifecycle-hook-tmpl-level-dq5bd-2150900480
      displayName: step-1
      finishedAt: "2022-04-01T10:27:30Z"
      hostNodeName: *
      id: lifecycle-hook-tmpl-level-dq5bd-798385017
      name: lifecycle-hook-tmpl-level-dq5bd[0[].step-1
      outputs:
        artifacts:
        - name: main-logs
          s3:
            key: *
        exitCode: "0"
      phase: Succeeded
      progress: 1/1
      resourcesDuration:
        cpu: 3
        memory: 3
      startedAt: "2022-04-01T10:27:26Z"
      templateName: echo-save
      templateScope: local/lifecycle-hook-tmpl-level-dq5bd
      type: Pod
    lifecycle-hook-tmpl-level-dq5bd-2150900480:
      boundaryID: lifecycle-hook-tmpl-level-dq5bd
      children:
      - lifecycle-hook-tmpl-level-dq5bd-2503513326
      displayName: '[1[]'
      finishedAt: "2022-04-01T10:27:46Z"
      id: lifecycle-hook-tmpl-level-dq5bd-2150900480
      message: child 'lifecycle-hook-tmpl-level-dq5bd-2503513326' failed
      name: lifecycle-hook-tmpl-level-dq5bd[1[]
      phase: Failed
      progress: 0/1
      resourcesDuration:
        cpu: 2
        memory: 2
      startedAt: "2022-04-01T10:27:36Z"
      templateScope: local/lifecycle-hook-tmpl-level-dq5bd
      type: StepGroup
    lifecycle-hook-tmpl-level-dq5bd-2217863861:
      boundaryID: lifecycle-hook-tmpl-level-dq5bd
      children:
      - lifecycle-hook-tmpl-level-dq5bd-798385017
      displayName: '[0[]'
      finishedAt: "2022-04-01T10:27:36Z"
      id: lifecycle-hook-tmpl-level-dq5bd-2217863861
      name: lifecycle-hook-tmpl-level-dq5bd[0[]
      phase: Succeeded
      progress: 1/2
      resourcesDuration:
        cpu: 5
        memory: 5
      startedAt: "2022-04-01T10:27:26Z"
      templateScope: local/lifecycle-hook-tmpl-level-dq5bd
      type: StepGroup
    lifecycle-hook-tmpl-level-dq5bd-2503513326:
      boundaryID: lifecycle-hook-tmpl-level-dq5bd
      displayName: step2
      finishedAt: "2022-04-01T10:27:40Z"
      hostNodeName:*
      id: lifecycle-hook-tmpl-level-dq5bd-2503513326
      message: Error (exit code 127)
      name: lifecycle-hook-tmpl-level-dq5bd[1[].step2
      outputs:
        artifacts:
        - name: main-logs
          s3:
            key: *
        exitCode: "127"
      phase: Failed
      progress: 0/1
      resourcesDuration:
        cpu: 2
        memory: 2
      startedAt: "2022-04-01T10:27:36Z"
      templateName: echo
      templateScope: local/lifecycle-hook-tmpl-level-dq5bd
      type: Pod
    lifecycle-hook-tmpl-level-dq5bd-3701634578:
      displayName: lifecycle-hook-tmpl-level-dq5bd.hooks.failed
      finishedAt: null
      id: lifecycle-hook-tmpl-level-dq5bd-3701634578
      name: lifecycle-hook-tmpl-level-dq5bd.hooks.failed
      phase: Pending
      progress: 0/1
      startedAt: "2022-04-01T10:27:46Z"
      templateName: echo-save
      templateScope: local/lifecycle-hook-tmpl-level-dq5bd
      type: Pod
  phase: Failed
  progress: 1/3
  resourcesDuration:
    cpu: 5
    memory: 5
  startedAt: "2022-04-01T10:27:26Z"

What happened/what you expected to happen?
 Give it a 👍. We prioritise the issues with the most 👍.

Hi @sarabala1979 could you please confirm if this is a bug and being worked on?
Can then remove stale label

@sarabala1979 the podGC issue was resolved with #8452.
However lifecycle hooks run from a workflow level, get stuck in 'Pending', even after they have completed.
Should I close this issues and create a new one specific to the 'Pending status'. Its currently causing issues when trying to retry a failed workflow.

PodGC resolved by #8448. However hook phased not updated. Created a more specific issue: #8529


From PyPIC to xfields

Scope

We want to concentrate in one package (Xfields) single-particle and particle-in-cell interactions involving the gradient of a scalar potential (space-charge, beam-beam, e-cloud, etc.)

Foreseen applications:

Frozen space-charge (needs to run fully single-particle, i.e. within the kernel when on GPU):

Interpolated 3D (saved 3D potential on grid, as for the e-cloud)
Modulated 2D:

Transverse can be Bassetti-Erskine or a saved 2D map (interpolated)
Longitudinal profile can be analytical for interpolated from an array

PIC space-charge (collective, needs all particles):

3D Poisson solver (FFT)

2.5D Poisson solver (FFT, or any PyPIC FD solver, with chamber geometry)
Modulated 2D:

Transverse soft-gaussian or 2D PIC (FFT, or any PyPIC FD solver, with chamber geometry)
Longitudinal profile can be analytical for interpolated from an array

Weak-strong beam-beam (needs to run fully single-particle, i.e. within the kernel when on GPU):

6D Classical Hirata approach

6D Interpolated (just an hypothesis, can we generalize to an arbitrary 3D potential map for the strong beam (using cubic interp)? Might be useful for crab waste?)
4D - Classical Bassetti-Erskine approach
4D - With interpolated map

Strong-strong beam-beam (collective, needs all particles):

6D PIC - See COMBI

6D Soft-gaussian - See COMBI
4D PIC - See COMBI
4D Soft-gaussian - See COMBI

e-cloud incoherent (needs to run fully single-particle, i.e. within the kernel when on GPU):

Interpolated 3D map

e-cloud coherent and buildup (collective, needs all particles):

2D (slicing handled by PyECLOUD)

Electron lens ?
Wire?

Equations
Physics manual being compiled here:
https://github.com/giadarol/PyPIC/tree/reorganize/doc
GPU implementation

Available only where needed
Same class for cpu and gpu (choice based on context)

Required interpolators

For longitudinal part of frozen space charge

Linear 1D, with derivative
Cubic 1D, with derivative

For transverse part of frozen space charge and beam-beam, non-gaussian transverse profile:

Linear 2D, with derivatives
Cubic 2D, with derivatives

For 3D space charge and e-cloud:

Linear 3D, with derivatives
Cubic 3D, with derivatives

Ask Martin about Cubic Spline interpolation!

Requirements from GPU infrastructure

Possibility to inject a beam element with arbitrary code (possibly complex -> multiple functions and files).
Possibility to store data in the device memory when on GPU which is retrievable by the element but shared among elements.

Questions:

Could we conceive passing a user-defined function for the longitudinal part of the space-charge? (The user might need to allocate also data...)
In legacy codes (sixtrack, sixtracklib) we have the possibility of including the effect of linear coupling of the strong beam. Should we keep this possibility (we never used it nor tested it in the past). If yes should we have it also for space-charge?

For now in bb simulations it is always switched off. We should introduce a check in the mask on the local coupling at the bb interactions.

Should we have an origin?

Things to me remembered

Sorted version -> we discontinue
Should we return the cell indeces of the particles?
To me there is a mistake in the pysixtrack spacecharge: $\chi$ should not be there (NOT TRUE!, check the definition of p_x in sixtracklib), there should be $beta_0$ and not $\beta$ at the denominator.
We might want to rescale grid dimension to reuse the same solver
For soft gaussians you might want to decide if updating the centroid or not

For implementation fo p2m

You can take it from here

On GPU Implementation
Atomicadd in opencl https://streamhpc.com/blog/2016-02-09/atomic-operations-for-floats-in-opencl-improved/

Need to use an extension for the 64 bit version: https://www.khronos.org/registry/OpenCL/specs/2.2/html/OpenCL_Ext.html

fft in cupy https://docs.cupy.dev/en/stable/reference/fft.html#

To use fft plans in cupy have a look here

fft in pyopenc https://github.com/geggo/gpyfft

Obsolete


how to execute the example python script ?

tried
python    example_syslog_server.py   --bind-path 514
do not see any error ; also did not see any output

That would start it up binding to a UNIX domain socket with the path of ./514; that may or may not be what you want. The example script doesn't listen on TCP ports, but you should be able to modify it for your own use-case pretty straightforwardly.
It only prints something out of a message is received.

thanks @Roguelazer
Sorry could not follow the steps required to build and test the parser.
should I do python setup.py that did not work as well . could not find in ReadMe. Please point me to the docs

In fact I changed to some other port (above 10000) and tried with valid syslog message passed on to the port, that did not work as well.

@Roguelazer  does these steps seem right?
#1
 python    example_syslog_server.py   --bind-path  10003
#2
echo "<31>1 2017-11-24T05:14:15.000008-07:00 <IP_ADDRESS> mypid 8888 - - Test syslogparser" | nc localhost  10003

As I said, the --bind-path argument is not a port, it's a filesystem path at which a stream-mode unix domain socket will be created.
Here's a session of me setting it up and using it:
$ python -m virtualenv env
New python executable in /Users/jbrown/pg/syslog-rfc5424-parser/env/bin/python2.7
Also creating executable in /Users/jbrown/pg/syslog-rfc5424-parser/env/bin/python
Installing setuptools, pip, wheel...
done.
$ env/bin/pip install .
Looking in indexes: https://pypi.org/simple, https://pyshop.easypo.net/simple/
Processing /Users/jbrown/pg/syslog-rfc5424-parser
Collecting pyparsing>=2.0 (from syslog-rfc5424-parser==0.1.3)
  Using cached https://files.pythonhosted.org/packages/71/e8/6777f6624681c8b9701a8a0a5654f3eb56919a01a78e12bf3c73f5a3c714/pyparsing-2.3.0-py2.py3-none-any.whl
Collecting enum34 (from syslog-rfc5424-parser==0.1.3)
  Using cached https://files.pythonhosted.org/packages/c5/db/e56e6b4bbac7c4a06de1c50de6fe1ef3810018ae11732a50f15f62c7d050/enum34-1.1.6-py2-none-any.whl
Building wheels for collected packages: syslog-rfc5424-parser
  Running setup.py bdist_wheel for syslog-rfc5424-parser ... done
  Stored in directory: /Users/jbrown/Library/Caches/pip/wheels/21/e8/63/0fba71019ab56ceb789ded5206b28f2eef0522f47048f8da88
Successfully built syslog-rfc5424-parser
Installing collected packages: pyparsing, enum34, syslog-rfc5424-parser
Successfully installed enum34-1.1.6 pyparsing-2.3.0 syslog-rfc5424-parser-0.1.3
$ env/bin/python example_syslog_server.py  --bind-path example_path

from another shell (in the same directory), I ran
$ echo "<31>1 2017-11-24T05:14:15.000008-07:00 <IP_ADDRESS> mypid 8888 - - Test syslogparser" | socat - ./example_path

That resulted in the first shell printing out the following:
{"procid": 8888, "severity": "debug", "appname": "mypid", "timestamp": "2017-11-24T05:14:15.000008-07:00", "hostname": "<IP_ADDRESS>", "facility": "daemon", "version": 1, "msgid": null, "msg": "Test syslogparser\n", "sd": {}}

Thanks @Roguelazer ! worked fine, finally ... i have a syslog file that I need to parse ..any suggestion where to start
previous errors
sudo env/bin/python example_syslog_server.py  --bind-path /home/myself/a.txt
without sudo fails with permission issue
without filename at the end fails with "directory" error
echo "<31>1 2017-11-24T05:14:15.000008-07:00 <IP_ADDRESS> mypid 8888 - - Test syslogparser" | socat -  /home/myself/a.txt
error received as
2018/11/28 15:28:37 socat[13202] E connect(5, AF=1 "/home/myself/a.txt", 23): Permission denied

instead of the test python script, will use read file and use  SyslogMessage.parse(messageLine)

thankyou @Roguelazer  worked fine reading from file


Filtering

Hi Nil,
I've been working up a filtering scheme that uses RQL in the filter request parameter to populate the eloquent query with where clauses.  For example, the request string could contain something like the following:
filter=and(or(and(like(name,b*),ne(name,bob),like(name,a)),eq(size,10))
There are other ways of expressing this using RQL, but this will do for an example.
The implementation I've thrown together is using the xiag-ag/rql-parser (https://github.com/xiag-ag/rql-parser)  to parse the content of the filter parameter passed on in the request string and then uses a class I've added named EloquentNodeVisitor to add where clauses to the eloquent query builder.
My implementation does kind of break your approach to handling the filter parameter (based, I assume on the recommendation on the jsonapi website) since I want to have a single RQL filter rather than a filter per field. Since the current implementation of your json-api package exposes the filter through the Request->getFilters and this always returns an array it posed an issue with obtaining the RQL and still getting correctly formed links in the response.  As a workaround the JsonApiController now converts the result from getFilters to a string or a null - it might be better to change this in the json-api package instead but I didn't know whether this approach made sense to you so I've just hacked it for now.
One final note - RQL supports a "not" logical operator but I couldn't figure out any way to map it to the Eloquent query builder so it will be rejected at this stage.
Let me know if you want anything further clarified.
Symon.

Apologies - this was premature.  Will resubmit later.


meson could be bumped from 0.44.0 to 0.46.0

Issue description
meson is on version 0.44.0 in nixpkgs. There already is a version 0.46.0.
Sadly there is a bug in meson 0.44.0 , which hinders me from packaging with it (the problem is with https://github.com/sardemff7/eventd, I have a workaround, but it's not nice). That bug is already fixed in meson 0.44.1. It would be nice if someone came around for a version bump.
Sadly that will probably trigger a lot of package rebuilding …

We have meson 0.45.1 in nixos-unstable.
Feel free to open a pull request with 0.46.0. Usually, trying to build just a few dependent packages (e.g. systemd, json-glib, colord, appstream-glib) should be enough.

Oh, sorry. I failed to pull before checking. 0.45.1 suffices for me. Thank you!


Outline of validation function

I think that's everything - thanks, some good spots in there :)
Now just to go through and define validation rules for 100+ sensors :laughing:

Awesome, looks good to me!

@FozzieUK - it'd be great if you could sense check the validation rules I've applied here please?!

:shipit: from me, perhaps with the LAN validations as well?

I'll merge this then throw up the LAN validations in another PR - suggest we leave this at beta for a while and see if anyone reports anything odd?

Warnings/errors bubble up to here - but it's a bit of a mess...

I'm running the latest beta, all looks good with the Aux validations so far apart from Grid Consumption Total (register 11082), in my case it's a large negative I assume it's because I make use of low tariff to charge 18kwh of batteries and discharge throughout the day.

Oh interesting! We might need to tweak that sensor then... How does that relate to your feed-in total sensor?
@nathanmarlor it would be useful to log the entity id I think...

I'm running the latest beta, all looks good with the Aux validations so far apart from Grid Consumption Total (register 11082), in my case it's a large negative I assume it's because I make use of low tariff to charge 18kwh of batteries and discharge throughout the day.

I knew there'd be on with a huge system which broke things :) I'll fix it later on today.

I had a feeling this might be the case.

Well that was easier than expected - introduced the option to set sensors as signed/unsigned.

Ok, loaded up and looking good - i'm back at grid consumption total of 4686.2 kwh, confirmed at the inverter panel :)

Looks like none of them have overflowed 16 bits yet. Can you remember to take a look when one of them passes 6,554 kwh?

@canton7 ok, will do :+1:
Now the BMS Watthours is unsigned and is positive I can see the problem, it's scale is 0.1 - it shouldn't be.
I've modified my install with the scale removed and it's climbing upwards in 1 watt increments - i've knocked up a quick and dirty battery_watt_rate sensor which lets me measure the approx battery watt changes and it looks to be correct.
I'll check it over a much longer period and report back to confirm.

Looks like none of them have overflowed 16 bits yet. Can you remember to take a look when one of them passes 6,554 kwh?

It'll be a while but I'm sure it'll be obvious :+1:

I know the charge times isn't complete yet but as its validation related thought i'd mention it in case there is something useful here - I noticed these errors last night after changing my charge times.
The charge times set were Force/Grid on period 1 00:30-04:30, period 2 both off time 00:00-00:00
Data string sent to foxess_modbus write register service:-
Register:  41001
Friendly name: ""
Data: '1, 30, 1054, 0, 0, 0'
2023-03-31 21:41:54.256 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 546, in async_update_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 600, in _async_write_ha_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 565, in _stringify_state
if (state := self.state) is None:
File "/usr/src/homeassistant/homeassistant/components/binary_sensor/init.py", line 211, in state
if (is_on := self.is_on) is None:
File "/config/custom_components/foxess_modbus/entities/modbus_charge_period_sensors.py", line 203, in is_on
or not self._validate(rules, start_time)
File "/config/custom_components/foxess_modbus/entities/modbus_entity_mixin.py", line 85, in _validate
if not rule.validate(processed):
File "/config/custom_components/foxess_modbus/entities/validation.py", line 59, in validate
hours, minutes = ((data & 0xFF00) >> 8, data & 0xFF)
TypeError: unsupported operand type(s) for &: 'str' and 'int'
2023-03-31 21:41:54.263 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 546, in async_update_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 600, in _async_write_ha_state
state = self._stringify_state(available)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 565, in _stringify_state
if (state := self.state) is None:
File "/usr/src/homeassistant/homeassistant/components/binary_sensor/init.py", line 211, in state
if (is_on := self.is_on) is None:
File "/config/custom_components/foxess_modbus/entities/modbus_charge_period_sensors.py", line 203, in is_on
or not self._validate(rules, start_time)
File "/config/custom_components/foxess_modbus/entities/modbus_entity_mixin.py", line 85, in _validate
if not rule.validate(processed):
File "/config/custom_components/foxess_modbus/entities/validation.py", line 59, in validate
hours, minutes = ((data & 0xFF00) >> 8, data & 0xFF)
TypeError: unsupported operand type(s) for &: 'str' and 'int'
Despite the error the charge times were updated normally 👍

Ah. That's a bug, thanks.


Implement Animations for various transitions

Implement animated transitions for various actions such as

When a user clicks on add note/todo button and moves to the next screen where he fills the details of that note/todo.
Initially when the user opens the app the already saved notes/todo should have a descent and simple entry animation.

Can you please assign this to me?

Assigned :)

Thank you

Hello sir , i will add slide in slide out animation for actions please check the video below:
https://user-images.githubusercontent.com/52368582/193450428-a6920ad2-8771-427b-af76-87fb50d646e8.mp4

Looks good, please add appropriate animation when the Note is saved. Also can u add a descent entry animation for already saved notes?

Yes,looking for animation to fit for entry animation

When can I expect a PR for this task? Any ETA?

By today EOD currently looking for better transition thats why not giving till now

Hello sir,Good evening
here is a small video of entry animation,all note to add note animation
https://user-images.githubusercontent.com/52368582/193611197-ec37eac0-744e-4d92-857e-9ae128ef929c.mp4

Animations looks cool, go ahead :)

Sir its final like the entry animation and add note button click to add fragment animation and recyclerview item click to add fragment animation
Somewhere i need to add any animation?

Yup animations look good, just make sure that the animation resource files which you'll add should not be too big in size.

its size around 600B

Go forward.


scoring scheme documentation confusing

[X] I have read through the manual page (man fzf)
[X] I have the latest version of fzf
[X] I have searched through the existing issues

Info

OS

[ ] Linux
[X] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[ ] zsh
[X] fish

Problem / Steps to reproduce
The man page for scheme says this
      --scheme=SCHEME
              Choose scoring scheme tailored for different types of input.

              default  Generic scoring scheme designed to work well with any type of input
              path     Scoring scheme for paths (additional bonus point only after path separator)
              history  Scoring scheme for command history (no additional bonus points).
                       Sets --tiebreak=index as well.

It is confusing for someone who hasn't read fzf source code. It leaves me with these questions

what are "additional bonus points"? There are no further mentions of it in the manpage
if history has no additional bonus points, then how is that different from "default" which has no mention of bonus points so presumably doesn't use them?
when it says "bonus point only after path separator", is it only the last path separator or all path separators?
why is giving bonus points after path separator good for dealing with paths?
why is the history scheme good for searching command history?

I've already read https://github.com/junegunn/fzf/issues/2909 and https://github.com/junegunn/fzf/issues/2930 and am still not confident I know the answers...
If I may ask a second question, would you recommend using --scheme=history for searching command history and git log? I'm guessing yes for command history and no for git log? Context: https://github.com/PatrickF1/fzf.fish/pull/302
Btw, once I understand it, I'm happy to PR in the documentation updates if you'd like. Being an OSS author myself, I know how time consuming and difficult writing documentation is.

I agree that the current documentation is incomplete, but yet at the same time, I'd like to hide implementation details that few will (want to) understand by not mentioning stuff like 'bonus point'.
If you want to know more about the algorithm, the best resource is the top comment section of https://github.com/junegunn/fzf/blob/master/src/algo/algo.go
A matching character at a special position, such as at a word boundary or after a non-alphanumeric character, etc, is given a bonus point. The bonus point was the same regardless of the type of the special position, but 0.32.0 changed that.
https://github.com/junegunn/fzf/releases/0.32.0

Different bonus points to different categories of word boundaries

It seemed like a good idea, but soon after the version was released, I and some other users realized the new algorithm didn't work great for the command history. When you search for a command, you're likely looking for a more recent command.
...
100 git log gradle
...
1000 ./gradle test

The query gr will match both items. Prior to 0.32.0, ./gradle test will be the result with the highest score, okay that's great, but the new algorithm of 0.32.0 prefers git log gradle because gr after space gets a higher bonus point than gr after /, which is usually not desirable.
That's why I had to add --scheme.

If I may ask a second question, would you recommend using --scheme=history for searching command history and git log? I'm guessing yes for command history and no for git log?

You'll have to experiment with the options to see which gives better results, but I think --scheme=history makes sense in that case because the chronological ordering is more important and you don't want old and new commits to be mixed in the list.

Thanks for your response!

I agree that the current documentation is incomplete, but yet at the same time, I'd like to hide implementation details that few will (want to) understand by not mentioning stuff like 'bonus point'.

You make a great point and I agree. In that case, maybe just provide the same level of detail that you just did in your response. Both too little detail and too much detail is bad in man pages, and I think what you just wrote was the wrote amount of detail.

You'll have to experiment with the options to see which gives better results, but I think --scheme=history makes sense in that case because the chronological ordering is more important and you don't want old and new commits to be mixed in the list.

Thanks I'll test both. But to clarify, you are saying that you think --scheme=history might be good if I want to avoid mixing old and new commits?

Nvm, I re-read your comment and I see that you were saying that --scheme=history is probably a good idea for git log. I read the source code and it makes sense to me as well. Anyway, when I was reading https://github.com/junegunn/fzf/commit/6fb41a202a97ad3f2437f6e5aee8890268560412, I was surprised that this line has since been removed:
No additional bonus points are given so that we give more weight to the chronological ordering.

IMO, it's valuable. I would advice adding it back.

Anyway, when I was reading 6fb41a2, I was surprised that this line has since been removed:

The line is still there, in CHANGELOG.
Anyway, what do you think about this?
diff --git a/man/man1/fzf.1 b/man/man1/fzf.1
index dc21832..5e93f50 100644
--- a/man/man1/fzf.1
+++ b/man/man1/fzf.1
@@ -57,9 +57,9 @@ Choose scoring scheme tailored for different types of input.
 .br
 .BR default "  Generic scoring scheme designed to work well with any type of input"
 .br
-.BR path "     Scoring scheme for paths (additional bonus point only after path separator)
+.BR path "     Scoring scheme for file paths
 .br
-.BR history "  Scoring scheme for command history (no additional bonus points).
+.BR history "  Scoring scheme for command history (or any list where chronological ordering is important).
          Sets \fB--tiebreak=index\fR as well.
 .br
 .TP

That's much better! If I may offer an even better doc, I'd do
Scoring scheme well suited for file paths

and
Scoring scheme well suited for command history or any input where chronological ordering is important

Thanks! Pushed to master.


Washing machine icon doesn't turn yellow when on

I'm using the washing machine in a "Picture elements Card configuration" dashboard. All devices turn yellow when on.
For example, in the picture below you can see that the ceiling light and piano are on:

However, the washing machine icon doesn't turn yellow when it's on.

If i look into the entity it'll show me it's on, but the icon won't turn yellow.
I'm using the entity: sensor.washing_machine .  In the yaml it looks like so:
  - type: state-icon     entity: sensor.washing_machine     style:       top: 72%       left: 22%       font-size: 6px
Can this be fixed?

What kind of entities this card require to become "yellow"? If it need a binary sensor, you should define a binary sensor helper based on washing machine sensor and this should solve the issue. In any case this is not related to this integration but to the card you are using.


Added Rancher Deployment components in Rancher docs

Solved #429

Hi @martyav & @btat
I've removed the screenshots that you mentioned and thus added the all-in-one kubectl command which will showcase all the resources that are being deployed by rancher!


Add 8ball, new status

I've (finally) created and finished an 8ball command, as well as added a new Watching status.

Nice way of doing the 8ball response picks. Couldn't have done it better myself. lol


Issue with i2c_slave_receive procedure when I2C VIP used as Master and Slave in a Test Harness

Following instances are used in a Test Harness, no additional instantiations done. This plaform is created to check Master and Slave behaviors of the I2C VIP.
i1_i2c_vvc: entity bitvis_vip_i2c.i2c_vvc
generic map(
GC_MASTER_MODE  => true,
GC_INSTANCE_IDX   => 1,
GC_I2C_CONFIG                            => C_I2C_BFM_CONFIG_DEFAULT,  -- Behavior specification for BFM
GC_CMD_QUEUE_COUNT_MAX                   => 1000,
GC_CMD_QUEUE_COUNT_THRESHOLD             => 950,
GC_CMD_QUEUE_COUNT_THRESHOLD_SEVERITY    => warning,
GC_RESULT_QUEUE_COUNT_MAX                => 1000,
GC_RESULT_QUEUE_COUNT_THRESHOLD          => 950,
GC_RESULT_QUEUE_COUNT_THRESHOLD_SEVERITY => warning
)
port map(
i2c_vvc_if        =>  i2c_vvc_if
);
i2_i2c_vvc: entity bitvis_vip_i2c.i2c_vvc
generic map(
GC_MASTER_MODE  => false,
GC_INSTANCE_IDX   => 2,
GC_I2C_CONFIG                            => C_I2C_BFM_CONFIG_DEFAULT,  -- Behavior specification for BFM
GC_CMD_QUEUE_COUNT_MAX                   => 1000,
GC_CMD_QUEUE_COUNT_THRESHOLD             => 950,
GC_CMD_QUEUE_COUNT_THRESHOLD_SEVERITY    => warning,
GC_RESULT_QUEUE_COUNT_MAX                => 1000,
GC_RESULT_QUEUE_COUNT_THRESHOLD          => 950,
GC_RESULT_QUEUE_COUNT_THRESHOLD_SEVERITY => warning
)
port map(
i2c_vvc_if        =>  i2c_vvc_if
);
In a testbench used following two commands
i2c_slave_receive(I2C_VVCT, 2, 1, "One byte from master to slave");
i2c_master_transmit(I2C_VVCT,1,C_FPGA_DEVICE_ID,  x"AA", "I2C TX", FALSE);
Following is the error GOT when the Master is about to generate stop condition. When debugged @ low level, found i2c_slave_receive procedure checking the timeout 20ns check before Master is able to assert STOP condition.
UVVM: ***  FAILURE #1  ***
UVVM:        178240 ns   I2C_VVC,2
UVVM:                    await_value(std_logic 1, 0 ns, 20 ns) => Failed. Timed out after 20 ns. 'One byte from master to slave'  [1]
Let me know if there is any mistake in the usage.

Hi,
Thank you for using UVVM!
Is it possible for you to supply your code? And what version of UVVM are you using?
Br,
Marius

Following is the Version Details.
This project uses the following versions:
uvvm_vvc_framework, version v2.0.4
uvvm_util, version v2.0.4
bitvis_vip_sbi, version v2.0.4
bitvis_vip_uart, version v2.0.3
bitvis_uart, version v1.0.3
bitvis_irqc, version v1.0.3
bitvis_vip_axilite, version v2.0.5
bitvis_vip_axistream, version v3.0.2
bitvis_vip_avalon_mm, version v2.0.5
bitvis_vip_i2c, version v2.0.3
bitvis_vip_spi, version v2.0.1
The TB and TH code is already there in the previous.
library IEEE;
use IEEE.std_logic_1164.all;
use IEEE.numeric_std.all;
library uvvm_util;
context	uvvm_util.uvvm_util_context;
library uvvm_vvc_framework;
use uvvm_vvc_framework.ti_vvc_framework_support_pkg.all;
--use work.i2c_bfm_pkg.all;
use work.timing_const_pkg.all;
library bitvis_vip_i2c;
library bitvis_i2c;
use	bitvis_vip_i2c.i2c_bfm_pkg.all;
use	bitvis_vip_i2c.vvc_methods_pkg.all;
-- Test harness entity
entity i2c_vvc_th is
end entity;
-- Test harness architecture
architecture struct of i2c_vvc_th is
-- I2C VVC signals
signal  i2c_vvc_if    : bitvis_vip_i2c.i2c_bfm_pkg.t_i2c_if;
--signal  i2c_vvc_if    : t_i2c_if;
begin

-- Instantiate the concurrent procedure that initializes UVVM
i_ti_uvvm_engine : entity uvvm_vvc_framework.ti_uvvm_engine;

-- I2C VVC
i1_i2c_vvc: entity bitvis_vip_i2c.i2c_vvc
generic map(
GC_MASTER_MODE  => true,
GC_INSTANCE_IDX   => 1,
GC_I2C_CONFIG                            => C_I2C_BFM_CONFIG_DEFAULT,  -- Behavior specification for BFM
GC_CMD_QUEUE_COUNT_MAX                   => 1000,
GC_CMD_QUEUE_COUNT_THRESHOLD             => 950,
GC_CMD_QUEUE_COUNT_THRESHOLD_SEVERITY    => warning,
GC_RESULT_QUEUE_COUNT_MAX                => 1000,
GC_RESULT_QUEUE_COUNT_THRESHOLD          => 950,
GC_RESULT_QUEUE_COUNT_THRESHOLD_SEVERITY => warning
)
port map(
i2c_vvc_if        =>  i2c_vvc_if
);
i2_i2c_vvc: entity bitvis_vip_i2c.i2c_vvc
generic map(
GC_MASTER_MODE  => false,
GC_INSTANCE_IDX   => 2,
GC_I2C_CONFIG                            => C_I2C_BFM_CONFIG_DEFAULT,  -- Behavior specification for BFM
GC_CMD_QUEUE_COUNT_MAX                   => 1000,
GC_CMD_QUEUE_COUNT_THRESHOLD             => 950,
GC_CMD_QUEUE_COUNT_THRESHOLD_SEVERITY    => warning,
GC_RESULT_QUEUE_COUNT_MAX                => 1000,
GC_RESULT_QUEUE_COUNT_THRESHOLD          => 950,
GC_RESULT_QUEUE_COUNT_THRESHOLD_SEVERITY => warning
)
port map(
i2c_vvc_if        =>  i2c_vvc_if
);
i2c_vvc_if.sda<= 'H';
i2c_vvc_if.scl<= 'H';
end struct;
library IEEE;
use IEEE.std_logic_1164.all;
use IEEE.numeric_std.all;
library uvvm_util;
context uvvm_util.uvvm_util_context;
library uvvm_vvc_framework;
use uvvm_vvc_framework.ti_vvc_framework_support_pkg.all;
library bitvis_vip_i2c;
use bitvis_vip_i2c.vvc_methods_pkg.all;
use bitvis_vip_i2c.td_vvc_framework_common_methods_pkg.all;
use bitvis_vip_i2c.i2c_bfm_pkg.all;
use work.timing_const_pkg.all;
-- Test bench entity
entity i2c_vvc_tb is
end entity;
-- Test bench architecture
architecture func of i2c_vvc_tb is
constant RELEASE_LINE_AFTER_TRANSFER : boolean:= FALSE;
constant C_SLAVE_ADDR         : unsigned(6 downto 0) := "1010000";
constant C_SCOPE              : string  := C_TB_SCOPE_DEFAULT;
-- Clock and bit period settings
constant C_CLK_PERIOD : time := 60.098 ns; -- 16.368 MHz
constant C_CLOCK_PERIOD : time := 1000 ns; --1MHZ
constant C_BIT_PERIOD         : time := 16 * C_CLK_PERIOD;
constant C_FPGA_DEVICE_ID     : unsigned(9 downto 0) :="0001010000";
-- Log overload procedure for simplification
procedure log(
msg   : string) is
begin
log(ID_SEQUENCER, msg, C_SCOPE);
end;
begin

-- Instantiate test harness, containing DUT and Executors
i_test_harness : entity work.i2c_vvc_th;

-- PROCESS: p_main
p_main: process
variable v_cmd_idx : natural; -- Command index for the last read
variable v_byte_array : bitvis_vip_i2c.vvc_cmd_pkg.t_vvc_result;
begin
-- Wait for UVVM to finish initialization
await_uvvm_initialization(VOID);

-- Print the configuration to the log
report_global_ctrl(VOID);
report_msg_id_panel(VOID);

enable_log_msg(ALL_MESSAGES);
--disable_log_msg(ALL_MESSAGES);
enable_log_msg(ID_LOG_HDR);
enable_log_msg(ID_SEQUENCER);
enable_log_msg(ID_UVVM_SEND_CMD);

--disable_log_msg(I2C_VVCT, 1, ALL_MESSAGES);
--enable_log_msg(I2C_VVCT, 1, ID_BFM);

log(ID_LOG_HDR, "Starting simulation of TB for I2C using VVCs", C_SCOPE);
------------------------------------------------------------

log("Wait 10 clock period for reset to be turned off");
wait for (10 * C_CLK_PERIOD); -- for reset to be turned off

log(ID_LOG_HDR, "Configure I2C VVC 1", C_SCOPE);
------------------------------------------------------------

-- shared_i2c_vvc_config(1).inter_bfm_delay.delay_in_time := 10 ms; --check if to add;
shared_i2c_vvc_config(1).bfm_config.i2c_bit_time              :=  10*C_BIT_PERIOD;
shared_i2c_vvc_config(1).bfm_config.slave_mode_address        := C_FPGA_DEVICE_ID;
shared_i2c_vvc_config(1).bfm_config.enable_10_bits_addressing := false;
--shared_i2c_vvc_config(2).inter_bfm_delay.delay_in_time := 10 ms; --check if to add;
shared_i2c_vvc_config(2).bfm_config.i2c_bit_time              :=  10*C_BIT_PERIOD;
shared_i2c_vvc_config(2).bfm_config.slave_mode_address        := C_FPGA_DEVICE_ID;
shared_i2c_vvc_config(2).bfm_config.enable_10_bits_addressing := false;
log(ID_LOG_HDR, "Check simple receive", C_SCOPE);
------------------------------------------------------------
-- In this test case the UART VVC (TX channel) is instructed to send the data x"AA" to the DUT.
-- This data should be received and stored to a RX buffer by the DUT. After the UART VVC has completed
-- the transmission, the SBI VVC is instructed to check read and check (sbi_check) the C_ADDR_RX_DATA
-- register, and verify that it is in fact x"AA" that the DUT received. The test sequencer will continue
-- when the SBI VVC is done checking the C_ADDR_RX_DATA register.

i2c_slave_receive(I2C_VVCT, 2, 1, "One byte from master to slave");

i2c_master_transmit(I2C_VVCT,1,C_FPGA_DEVICE_ID, x"AA", "I2C TX", FALSE);

wait for 50 ns;  -- margin
-----------------------------------------------------------------------------
-- Ending the simulation
-----------------------------------------------------------------------------

wait for 4000 ns;             -- to allow some time for completion
report_alert_counters(FINAL); -- Report final counters and print conclusion for simulation (Success/Fail)
log(ID_LOG_HDR, "SIMULATION COMPLETED", C_SCOPE);
-- Finish the simulation

std.env.stop;
--wait;  -- to stop completely
end process p_main;
end func;

Am 11.07.2017 11:46 vorm. schrieb "AHHarish"<EMAIL_ADDRESS>
Following instances are used in a Test Harness, no additional
instantiations done. This plaform is created to check Master and Slave
behaviors of the I2C VIP.
i1_i2c_vvc: entity bitvis_vip_i2c.i2c_vvc
generic map(
GC_MASTER_MODE => true,
GC_INSTANCE_IDX => 1,
GC_I2C_CONFIG => C_I2C_BFM_CONFIG_DEFAULT, -- Behavior specification for
BFM
GC_CMD_QUEUE_COUNT_MAX => 1000,
GC_CMD_QUEUE_COUNT_THRESHOLD => 950,
GC_CMD_QUEUE_COUNT_THRESHOLD_SEVERITY => warning,
GC_RESULT_QUEUE_COUNT_MAX => 1000,
GC_RESULT_QUEUE_COUNT_THRESHOLD => 950,
GC_RESULT_QUEUE_COUNT_THRESHOLD_SEVERITY => warning
)
port map(
i2c_vvc_if => i2c_vvc_if
);
i2_i2c_vvc: entity bitvis_vip_i2c.i2c_vvc
generic map(
GC_MASTER_MODE => false,
GC_INSTANCE_IDX => 2,
GC_I2C_CONFIG => C_I2C_BFM_CONFIG_DEFAULT, -- Behavior specification for
BFM
GC_CMD_QUEUE_COUNT_MAX => 1000,
GC_CMD_QUEUE_COUNT_THRESHOLD => 950,
GC_CMD_QUEUE_COUNT_THRESHOLD_SEVERITY => warning,
GC_RESULT_QUEUE_COUNT_MAX => 1000,
GC_RESULT_QUEUE_COUNT_THRESHOLD => 950,
GC_RESULT_QUEUE_COUNT_THRESHOLD_SEVERITY => warning
)
port map(
i2c_vvc_if => i2c_vvc_if
);
In a testbench used following two commands
i2c_slave_receive(I2C_VVCT, 2, 1, "One byte from master to slave");
i2c_master_transmit(I2C_VVCT,1,C_FPGA_DEVICE_ID, x"AA", "I2C TX", FALSE);
Following is the error GOT when the Master is about to generate stop
condition. When debugged @ low level, found i2c_slave_receive procedure
checking the timeout 20ns check before Master is able to assert STOP
condition.
UVVM: *** FAILURE #1 https://github.com/UVVM/UVVM_All/issues/1 ***
UVVM: 178240 ns I2C_VVC,2
UVVM: await_value(std_logic 1, 0 ns, 20 ns) => Failed. Timed out after 20
ns. 'One byte from master to slave' [1]
Let me know if there is any mistake in the usage.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/UVVM/UVVM_All/issues/23, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACe00j4xShBfTKFgsJAIXQkykDOr8hMEks5sM0SJgaJpZM4OT_GI
.

Hi @AHHarish
I've tested your design using bitvis_vip_i2c v2.0.5, uvvm_util v2.1.1 and uvvm_vvc_framework v2.0.7 releases, and the TB runs fine:
i2c_vvc_tb:
`library IEEE;
use IEEE.std_logic_1164.all;
use IEEE.numeric_std.all;
library uvvm_util;
context uvvm_util.uvvm_util_context;
library uvvm_vvc_framework;
use uvvm_vvc_framework.ti_vvc_framework_support_pkg.all;
library bitvis_vip_i2c;
use bitvis_vip_i2c.vvc_methods_pkg.all;
use bitvis_vip_i2c.vvc_cmd_pkg.all;
use bitvis_vip_i2c.td_vvc_framework_common_methods_pkg.all;
use bitvis_vip_i2c.td_target_support_pkg.all;
use bitvis_vip_i2c.i2c_bfm_pkg.all;
--use work.timing_const_pkg.all;
-- Test bench entity
entity i2c_vvc_tb is
end entity;
-- Test bench architecture
architecture func of i2c_vvc_tb is
--constant RELEASE_LINE_AFTER_TRANSFER : boolean              := false;
constant C_SLAVE_ADDR                : unsigned(6 downto 0) := "1010000";
constant C_SCOPE                     : string               := C_TB_SCOPE_DEFAULT;
-- Clock and bit period settings
constant C_CLK_PERIOD   : time := 60.098 ns;  -- 16.368 MHz
constant C_CLOCK_PERIOD : time := 1000 ns;    --1MHZ
constant C_BIT_PERIOD     : time                 := 16 * C_CLK_PERIOD;
constant C_FPGA_DEVICE_ID : unsigned(9 downto 0) := "0001010000";
-- Log overload procedure for simplification
procedure log(
msg : string) is
begin
log(ID_SEQUENCER, msg, C_SCOPE);
end;
begin
-- Instantiate test harness, containing DUT and Executors
i_test_harness : entity work.i2c_vvc_th;
-- PROCESS: p_main
p_main : process
variable v_cmd_idx    : natural;    -- Command index for the last read
variable v_byte_array : bitvis_vip_i2c.vvc_cmd_pkg.t_vvc_result;
begin
-- Wait for UVVM to finish initialization
await_uvvm_initialization(VOID);
-- Print the configuration to the log
report_global_ctrl(VOID);
report_msg_id_panel(VOID);
enable_log_msg(ALL_MESSAGES);

--disable_log_msg(ALL_MESSAGES);
enable_log_msg(ID_LOG_HDR);
enable_log_msg(ID_SEQUENCER);
enable_log_msg(ID_UVVM_SEND_CMD);
--disable_log_msg(I2C_VVCT, 1, ALL_MESSAGES);
--enable_log_msg(I2C_VVCT, 1, ID_BFM);
log(ID_LOG_HDR, "Starting simulation of TB for I2C using VVCs", C_SCOPE);

log("Wait 10 clock period for reset to be turned off");
wait for (10 * C_CLK_PERIOD);       -- for reset to be turned off

log(ID_LOG_HDR, "Configure I2C VVC 1", C_SCOPE);

-- shared_i2c_vvc_config(1).inter_bfm_delay.delay_in_time := 10 ms; --check if to add;
shared_i2c_vvc_config(1).bfm_config.i2c_bit_time              := 10*C_BIT_PERIOD;
shared_i2c_vvc_config(1).bfm_config.slave_mode_address        := C_FPGA_DEVICE_ID;
shared_i2c_vvc_config(1).bfm_config.enable_10_bits_addressing := false;
--shared_i2c_vvc_config(2).inter_bfm_delay.delay_in_time := 10 ms; --check if to add;
shared_i2c_vvc_config(2).bfm_config.i2c_bit_time              := 10*C_BIT_PERIOD;
shared_i2c_vvc_config(2).bfm_config.slave_mode_address        := C_FPGA_DEVICE_ID;
shared_i2c_vvc_config(2).bfm_config.enable_10_bits_addressing := false;
log(ID_LOG_HDR, "Check simple receive", C_SCOPE);

-- In this test case the UART VVC (TX channel) is instructed to send the data x"AA" to the DUT.
-- This data should be received and stored to a RX buffer by the DUT. After the UART VVC has completed
-- the transmission, the SBI VVC is instructed to check read and check (sbi_check) the C_ADDR_RX_DATA
-- register, and verify that it is in fact x"AA" that the DUT received. The test sequencer will continue
-- when the SBI VVC is done checking the C_ADDR_RX_DATA register.
i2c_slave_receive(I2C_VVCT, 2, 1, "One byte from master to slave");

--i2c_master_transmit(I2C_VVCT, 1, C_FPGA_DEVICE_ID, x"AA", "I2C TX", false);
i2c_master_transmit(I2C_VVCT, 1, C_FPGA_DEVICE_ID, x"AA", "I2C TX");

wait for 50 ns;                     -- margin

-- Ending the simulation
wait for 4000 ns;                   -- to allow some time for completion
report_alert_counters(FINAL);  -- Report final counters and print conclusion for simulation (Success/Fail)
log(ID_LOG_HDR, "SIMULATION COMPLETED", C_SCOPE);

-- Finish the simulation
std.env.stop;

--wait; -- to stop completely
end process p_main;
end func;
`

Hi @AHHarish
I've tested your TB with our latest release. The simulation run fine with minor modifications:
i2c_vvc_tb.vhd
library bitvis_vip_i2c;
use bitvis_vip_i2c.vvc_methods_pkg.all;
use bitvis_vip_i2c.vvc_cmd_pkg.all;  -- ADDED
use bitvis_vip_i2c.td_vvc_framework_common_methods_pkg.all;
use bitvis_vip_i2c.td_target_support_pkg.all; -- ADDED
use bitvis_vip_i2c.i2c_bfm_pkg.all;
.......
--constant RELEASE_LINE_AFTER_TRANSFER : boolean              := false;  -- REMOVED
.......
i2c_master_transmit(I2C_VVCT, 1, C_FPGA_DEVICE_ID, x"AA", "I2C TX"); -- CHANGED

i2c_vvc_th.vhd
library bitvis_vip_i2c;
--library bitvis_i2c;  -- REMOVED
use bitvis_vip_i2c.i2c_bfm_pkg.all;
use bitvis_vip_i2c.vvc_methods_pkg.all;

Best regards,
Marius

Hi Marius,
Please consider adding additional command as give below after the i2c_master_transmit command. Still it fails. Use the same setup what you have described.
i2c_slave_receive(I2C_VVCT, 2, 1, "One byte from master to slave");
i2c_master_transmit(I2C_VVCT, 1, C_FPGA_DEVICE_ID, x"AA", "I2C TX"); -- CHANGED by Marius
await_completion(I2C_VVCT,1,100 * 10*C_BIT_PERIOD); -- ADDED by AHHarish
Regards,
AHHarish


KAFKA-14881: Update UserScramCredentialRecord for SCRAM ZK to KRaft migration

Replace saltedPassword with serverKey and StoredKey in UserScramCredentialRecord.
Bump IBP record version for SCRAM support to IBP_3_5_IV2.
Update latest IBP record version to IBP_3_5_IV2
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Thanks for this, @pprovenzano . Seems like a relatively straightforward change. However, you need to give a reason why we should do this. I think the reason here is for compatibility with SCRAM credentials migrated from ZK, right?
The comments in UserScramCredentialRecord.json for StoredKey and ServerKey are very unhelpful. They just repeat the name fo the field. If I understand correctly the meanings should be something like: StoredKey: used by the server to verify the client's identity and ServerKey: used by the server to prove its identity to the client ?
It seems that ScramControlManager.toRecord is no longer used; can we remove it?
Can we have a ScramCredentialDataTest that tests ScramCredentialData.toRecord / ScramCredentialData.fromRecord ?

Thanks for this, @pprovenzano . Seems like a relatively straightforward change. However, you need to give a reason why we should do this. I think the reason here is for compatibility with SCRAM credentials migrated from ZK, right? (This should be in the change description)
The current comments in UserScramCredentialRecord.json for StoredKey and ServerKey are not helpful. They just repeat the name of the field. If I understand correctly the meanings should be something like: StoredKey: used by the server to verify the client's identity and ServerKey: used by the server to prove its identity to the client ?
It seems that ScramControlManager.toRecord is no longer used; can we remove it?
Can we have a ScramCredentialDataTest that tests ScramCredentialData.toRecord / ScramCredentialData.fromRecord ?

Thank you for the review. I've updated the PR with all of your suggestions.

Should I move ScramCredentialData.java from metadata/src/main/java/org/apache/kafka/image to metadata/src/main/java/org/apache/kafka/metadata ?

Should I move ScramCredentialData.java from metadata/src/main/java/org/apache/kafka/image to metadata/src/main/java/org/apache/kafka/metadata ?

yes, please.


useNakedDomain option added

This time it definitely works as I expected.
Ref #293
Close #192

The domain component has this feature already built in?

@barrysteyn But serverless-next.js component doesn't expose that feature.

@danielcondemarin Hey, please review this PR.

@danielcondemarin could you confirm if we still need this? we are about to deploy a V2 of our app to a naked domain which uses this plugin, we don't have a way to test if it works as we don't have a spare domain to test on it as the V1 of our app uses it.

Hey @endigo thanks for adding this. What exactly would I use in my config to have naked domain AND www subdomain point to my application?

Actually this already works for me:
myWhackyApp:
  component: serverless-next.js
  inputs:
    domain: "mydomain.com"

@owlas It creates an only naked domain. Then you can redirect www to the naked one.

Sorry but can someone please show how to use the naked domain option. Currently I get two aliases created in Route53 for www and non www with both pointing to cloudfront. This causes them to be seen as two different sites which is affecting my SEO

@owboateng Unfortunately, this PR is not merged yet.
You can create custom Cloudfront distribution which redirects to the other one.
When you deploy your web to AWS using serverless command it will fail because of a duplicated record of Cloudfront, but it'll work fine.
I tried to solve this issue with this PR.
Thanks

@endigo Thanks for the quick response. Any one here knows when this PR will be integrated? Thanks

do you mind adding a test and fixing the conflicts. I'll test this out after.

I'd like to handle this differently. Closing but I'll be addressing it in #465


Add mdformat to .pre-commit-config.yaml

Apply mdformat on README.md
Add mdformat to .pre-commit-config.yaml

This would change some of the numbered items. 1. 2. 3. all turned to 1.1.1.

Yes, that is expected, isn't it? So writers could add or deleted items without the need to renumber the rest, because numbering is the work of markdown renderer.


[ABI] Use generic environment to handle mangled generic keypath types.

Always use mangled type names to represent type metadata in keypath patterns.
For generic types, use the generic environment to pull substituted types
from the instantiation arguments.
Finishes the type metadata part of rdar://problem/38038799.

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge


fix(installer): Backport installer fix to develop [DEV-1826]

Task linked: DEV-1826 Fix Cosmovisor binary permissions in interactive installer


initial tiles route

Acceptance criteria:

[ ] A /tiles route which accepts x, y, z path parameters and collection concept id and datetime query parameters and returns a tile by querying CMR
[ ] Demonstrated working for cmr datasets in /stac/collections/*-cmr.json
[ ] Automated tests

Pseudo code:
xr_extensions = ('.hdf', '.nc', '.h5', '.hdf5', '.nc4')

# GET /tiles/0/0/0.png?collection_concept_id=C000...&datetime=2000-01-01
def tile(x, y, z, collection_concept_id, datetime):
    results = earthaccess.search_data(
        concept_id=collection_concept_id,
        temporal=(datetime),
        count=1
    )
    granule_link = results[0].data_links()[0]
    if granule_link.endswith(extensions):
        # A place for the CMR reader to takeover?
        data = earthaccess.open(granule_link)
    elif granule_link.endswith('.tif'):
        data = rasterio.open(granule_link)
    # continue with tiling the data...

Closing as completed


Import GetUserProfileDirectoryW from winapi

Thanks @retep998

r=me

@bors: r+

@bors: r+

:pushpin: Commit ffafe9a has been approved by alexcrichton

:hourglass: Testing commit ffafe9a with merge 70a507c...

Gah bors always seems to get confused, I'm gonna close this to move it along, will reopen hopefully once https://github.com/rust-lang-nursery/multirust-rs/pull/130 merges