add CRF tutorial

Description
Brief Description of the PR:
add a tutorial for CRF Layer
To Reviewers:
Here is the candidate feature list for this tutorial:

[Done] Replace faked training data with real training data:

Pros: make the tutorial more practicable
Cons: Add many codes for data processing, make it longer and less concentration.

[Done] Add additional custom training step base approach (co-exists with current custom training loop based approach):

Pros: User have more choose of programming style
Cons: Add some (not much) codes, make it longer and less concentration.

What do you think?
Fixes # (issue)
Type of change

[ ] Bug fix
[x] New Tutorial
[ ] Updated or additional documentation
[ ] Additional Testing
[ ] New Activation and the changes conform to the activation contribution guidelines
[ ] New Callback and the changes conform to the callback contribution guidelines
[ ] New Image addition and the changes conform to the image op contribution guidelines
[ ] New Layer and the changes conform to the layer contribution guidelines
[ ] New Loss and the changes conform to the loss contribution guidelines
[ ] New Metric and the changes conform to the metric contribution guidelines
[ ] New Optimizer and the changes conform to the optimizer contribution guidelines
[ ] New RNN Cell and the changes conform to the rnn contribution guidelines
[ ] New Seq2seq addition and the changes conform to the seq2seq contribution guidelines
[ ] New Text addition and the changes conform to the text op contribution guidelines

Checklist:

[ ] I've properly formatted my code according to the guidelines

[ ] By running Black + Flake8
[ ] By running pre-commit hooks

[ ] This PR addresses an already submitted issue for TensorFlow Addons
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] This PR contains modifications to C++ custom-ops

How Has This Been Tested?
If you're adding a bugfix or new feature please describe the tests that you ran to verify your changes:
*

Update: I am working on update this tutorial with real training data.

Update: all the planed features are implemented. it still needs some polish but it's ready for technical review.

When #2555 is merged, I will update this tutorial accrodingly.

@howl-anderson Can you join in the official forum?
We have some user looking for CRF support:
https://discuss.tensorflow.org/t/how-to-implement-and-use-a-linear-chain-crf-in-tensorflow/4742/

@bhack Sure, I will handle this. Thank you!

Update: since #2555 is merged, I will update this tutorial soon.

@seanpmorgan Please take a look

@MarkDaoust Please take a look

Thank you for your contribution. We sincerely apologize for any delay in reviewing, but TensorFlow Addons is transitioning to a minimal maintenance and release mode. New features will not be added to this repository. For more information, please see our public messaging on this decision:
TensorFlow Addons Wind Down
Please consider sending feature requests / contributions to other repositories in the TF community with a similar charters to TFA:
Keras
Keras-CV
Keras-NLP


project for synthesis

Description
Hi,

Can you please provide a link to some more IPs or projects which I can use to do full ASIC flow and do some optimization for my learning.
Can you please let me know which open source tool is similar to ModelSim because i also want to see simulation result before synthesis ?

Thank you
Suggested Solution
No response
Additional Context
No response

https://github.com/The-OpenROAD-Project/OpenROAD-flow-scripts has various designs you can run
https://www.veripool.org/verilator/


feat(marketplace): use catalogApi to fetch marketplace plugins

Hey, I just made a Pull Request!
Changes:

used catalog API to fetch all the plugins and pluginLists.
removed the MarketplaceClient which invokes catalog-backend API to get the data.
removed marketplace-backend plugin.
removed redundant type declarations infavor of Entityfrom @backstage/types
cleanup old metadata files.

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or Updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)

I have installed RBAC backend and denied catalog.entity permission, marketplace plugin entities are not loaded where as in my other PR marketplace plugins entities are displayed even if you restrict catalog.entitypermission because it uses backend service to fetch the entities.
with this PR :

with the backend implementation PR:

Catalog list
Marketplace

closing this PR in favour of backend plugin to fetch from catalog-backend.


Update byte-buddy, byte-buddy-agent to 1.14.10

About this PR
📦 Updates

net.bytebuddy:byte-buddy
net.bytebuddy:byte-buddy-agent

from 1.14.2 to 1.14.10
Usage
✅ Please merge!
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 me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (1.14.2).
You might want to review and update them manually.
website/yarn.lock

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "net.bytebuddy" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "net.bytebuddy" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #773.


Update Arr.php

Making array_pluck / Arr::pluck safer for malformed data where the key could be absent in one of the arrays.

This doesn't work.
1) SupportCollectionTest::testGetListValueWithAccessors
Failed asserting that two arrays are equal.
--- Expected
+++ Actual
@@ @@
 Array (
-    0 => 'foo'
-    1 => 'bar'
 )


Separators are not supported, despite docs saying they are

There's an example for separators, but this feature does not exist in 4.0.0. Am I missing something?

PagedListView.separated
Still exists in version 4.0.0 just like in the example.
What issue are you experiencing?

False alarm. It wasn't working, because I missed the .separated( part of the example.
Feel free to close the ticket. (I'm not sure if you want it marked as "completed" or "not planned".

False alarm. It wasn't working, because I missed the .separated( part of the example.
Feel free to close the ticket. (I'm not sure if you want it marked as "completed" or "not planned".

does it work or not? because i cant seem to get it to work

It works for me. (I recommend copy-pasting the example and tweaking it to make sure you don't miss something.)


tfsec inconsistent results for a pair of buckets

Describe the bug
When trying to apply tfsec to terraform code containing a pair of buckets that use terraform-aws-modules/s3-bucket/aws, I am seeing intermittent failures. On my main codebase it occurs more frequently.
The intermittent failure is a report stating
[aws-s3-enable-bucket-logging][MEDIUM] Resource 'module.s3_bucket_1:aws_s3_bucket.this[0]' does not have logging enabled.

See https://asciinema.org/a/9ygsuHdWwENmiVy4rXNJpGRfj for a demo that uses the code below.
To Reproduce
$ terraform --version
Terraform v1.0.4
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v3.54.0

$ tfsec --version
0.58.4

Create file main.tf:
terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 3.0"
    }
  }
}

provider "aws" {
  region = "eu-west-2"
}

resource "aws_kms_key" "objects" {
  description             = "KMS key is used to encrypt bucket objects"
  deletion_window_in_days = 7
  enable_key_rotation     = true
}

module "s3_bucket_logs" {
  source               = "terraform-aws-modules/s3-bucket/aws"
  version              = "~> 1.0"
  acl                  = "log-delivery-write"
  bucket               = "my-s3-bucket-logs"
  attach_public_policy = true
  force_destroy        = true

  block_public_acls       = true
  block_public_policy     = true
  ignore_public_acls      = true
  restrict_public_buckets = true

  server_side_encryption_configuration = {
    rule = {
      apply_server_side_encryption_by_default = {
        # Can't use KMS on logs bucket
        sse_algorithm = "AES256"
      }
    }
  }

  versioning = {
    enabled = true
  }
}

module "s3_bucket_1" {
  source = "terraform-aws-modules/s3-bucket/aws"

  bucket = "my-s3-bucket-1"
  acl    = "private"

  attach_public_policy    = true
  block_public_acls       = true
  block_public_policy     = true
  ignore_public_acls      = true
  restrict_public_buckets = true

  logging = {
    target_bucket = module.s3_bucket_logs.this_s3_bucket_id
    target_prefix = "log/"
  }

  server_side_encryption_configuration = {
    rule = {
      apply_server_side_encryption_by_default = {
        kms_master_key_id = aws_kms_key.objects.arn
        sse_algorithm     = "aws:kms"
      }
    }
  }

  versioning = {
    enabled = true
  }
}

To iterate through multiple runs, checking for the results, run:
$ for i in `seq 1 10`; do terraform init 2>&1 > /dev/null && tfsec --no-color . | egrep "potential problems|^  \[|No problems detected"; done

Expected behavior
Checks should pass and pass consistently.
Screenshots
See https://asciinema.org/a/9ygsuHdWwENmiVy4rXNJpGRfj
Desktop (please complete the following information):

OS: Ubuntu 21.04

Additional context
None

@dhallam I'm pretty sure this isn't the issue, but can you confirm if this is a typo
target_bucket = module.s3_bucket_logs.this_s3_bucket_id

I think it should be a this.s3_bucket_id?
target_bucket = module.s3_bucket_logs.this.s3_bucket_id

Hi @owenrumney. That's interesting - good spot. We're still using the v1 of the module (1.25.0) where the output prefix was this_ (was removed in https://github.com/terraform-aws-modules/terraform-aws-s3-bucket/pull/88). However, I notice that I hadn't specified the version of s3_bucket_1 so it was pulling the latest (2.7.0). The s3_bucket_logs is pinned to v1 so the terraform in the sample is valid, albeit running a different version of the terraform-aws-s3-module for each bucket.
Re-running with both s3_bucket_1 and s3_bucket_logs pinned to ~> 1.0, I consistently get
[aws-s3-enable-bucket-logging][MEDIUM] Resource 'module.s3_bucket_1:aws_s3_bucket.this[0]' does not have logging enabled.

If I pin both to ~> 2.0 and update to target_bucket = module.s3_bucket_logs.s3_bucket_id, I consistently get
[aws-s3-enable-bucket-logging][MEDIUM] Resource 'module.s3_bucket_1:aws_s3_bucket.this[0]' does not have logging enabled.

If I pin s3_bucket_1 to ~> 2.0 so that it's explicit and leave s3_bucket_logs pinned to ~> 1.0, I see the inconsistent results as reported in this issue.
So I think there are two issues:

Why are we getting aws-s3-enable-bucket-logging on a bucket that has logging enabled when using the terraform-aws-s3-bucket module?
What is the cause of the inconsistency when the two modules use different versions of terraform-aws-s3-bucket?

Thanks for this - I'll take a look at 1. I think the reason for 2 is a dedup issue, will try to work that out too

@dhallam Please could you test this with the latest release and let us know here if it's still an issue? I believe this should be fixed now with the reworking of our results handling for modules.


No content present in events and hiring page

Hello
There is no content present in events page and hiring page
Just footer is present
I would like to add it
Pls assign me

I think its fixed now

Do you have any specific that I could solve

Do you have any specific issue that I could solve

Some logic things are remaining such as adding members to club and displaying the club (when clicked on view club btn) with their members.
Can you try working on them.

Yes I can work on displaying the club with their members.


[BUG] .net 6 upgrade - .runtimeconfig.dev.json is no longer available in build output

Describe the bug
I've upgraded an service fabric actor solution (previous .net5.0) to .net6.0, and I'm unable to build the solution.
The following error occurs in the ouput window:

C:\Users{username}.nuget\packages\microsoft.servicefabric.actors\5.2.1235\build\netcoreapp2.0\Microsoft.ServiceFabric.Actors.targets(19,5): error MSB3030: Could not copy the file "C:\Dev{...}{...}\src{...}\bin\Debug\net6.0\win7-x64\{...}.runtimeconfig.dev.json" because it was not found.

Area/Component:
SDK
To Reproduce

Start from a solution with a .net5.0 project with an Actor
Change the TFM to .net6.0
Build or Run
Build fails with error:

C:\Users{username}.nuget\packages\microsoft.servicefabric.actors\5.2.1235\build\netcoreapp2.0\Microsoft.ServiceFabric.Actors.targets(19,5): error MSB3030: Could not copy the file "C:\Dev{...}{...}\src{...}\bin\Debug\net6.0\win7-x64\{...}.runtimeconfig.dev.json" because it was not found.

Expected behavior
Successful build.
Observed  behavior:
When comparing to output folder for .net6.0 vs .net5.0. The .net5.0 folder contains a file: {...}.runtimeconfig.dev.json
The 6.0 folder doesn't contain this file.
The error occurs in the build targets file on this line:
<Copy SourceFiles="$(TargetDir)\$(AssemblyName).runtimeconfig.dev.json" DestinationFiles="$(FabActUtilWorkingDir)\FabActUtil.runtimeconfig.dev.json" SkipUnchangedFiles="true" />
Screenshots
n/a
Service Fabric Runtime Version:
Nuget packages

Microsoft.VisualStudio.Azure.Fabric.MSBuild 1.7.6
Microsoft.ServiceFabric.Actors 5.2.1235

Environment:

Windows 10 21H1 (OS Build 19043.1288)
Visual studio 2022 Professional (Version 17.0.0)
Microsoft Azure Service Fabric: 8.2.1235.9590
Microsoft Azure Service Fabric SDK: 5.2.1235.9590

If this is a regression, which version did it regress from? n/a
Additional context
Building the individual *.csproj files works, building the *.sfproj doesn't.
Related change in .net sdk  https://github.com/dotnet/sdk/issues/16818

Assignees: /cc @microsoft/service-fabric-triage

The fix maybe as simple as changing:
<Copy SourceFiles="$(TargetDir)\$(AssemblyName).runtimeconfig.dev.json" DestinationFiles="$(FabActUtilWorkingDir)\FabActUtil.runtimeconfig.dev.json" SkipUnchangedFiles="true" />
To
<Copy SourceFiles="$(TargetDir)\$(AssemblyName).runtimeconfig.dev.json" DestinationFiles="$(FabActUtilWorkingDir)\FabActUtil.runtimeconfig.dev.json" SkipUnchangedFiles="true"  Condition="Exists('$(TargetDir)\$(AssemblyName).runtimeconfig.dev.json')"  />

Fix is merged to develop


nanoc guard no longer works with nanoc version 4.11.13

It looks like Guard nanoc is accessing a method in nanoc that has been renamed. Downgrading to nanoc version 4.11.12 fixes the problem.
Steps to reproduce

Use Nanoc  4.11.13, guard-nanoc 2.1.6 and guard 2.16.1
bundle exec guard

Expected behavior
Guard Nanoc starts
Actual behavior
It fails to start
Crash log
ERROR - Guard::Nanoc failed to achieve its <start>, exception was:
> [#3d60f37ee03b] NoMethodError: undefined method `load_command_at' for Nanoc::CLI:Module
> [#3d60f37ee03b] Did you mean?  load_commands_at
<snip>
Guard::Nanoc has just been fired

Happens to me, too. Same error. Also fixed by downgrading to 4.11.12

I fixed this issue, but forgot to release guard-nanoc with the fix! A fix is coming up shortly.

Upgrade to guard-nanoc 2.1.7, and the problem should be gone.


Website: full table needs multi-page

For the full table now we can have many more sources, need to display multiple pages, can try and use https://datatables.net/ or do a custom callback on page as is.

Old development route. We can now just use a searchbar with wrappers, similar to ONC


Use tabler-icons for brand icons

See https://github.com/lucide-icons/lucide/issues/670 for more details
I initially considered using the svelte simple-icons package since it's what they recommend but it didn't have any type declarations so it was basically unusable with typescript, which is why I decided to use tabler-icons instead (https://tabler.io/icons)
Eventually, this could even replace lucide-svelte if needed but I think that's not important for now.

@Discusser


Anonymous login does not let you find and enter scenes

Describe the bug
Anonymous login brings you into a scene selection screen that is disabled:

Expected behavior
Should be able to select and enter a public scene.
Screenshots

Duplicate of https://github.com/conix-center/arena-account/issues/53?

This is clientside actually, conix-center/arena-account#53 looks fixed where the list isnt empty anymore.
Moving to arena-account because all this html/js is in that repo


Running canopy tests in FSI.exe

Mr. Goat,
Canopy is freaking fantastic! I ran into some trouble, though, while trying to execute some commands in the F# interactive console. For some reason, whenever I try to run:
element "some-selector"
fsi reports the following error:
error FS0074: The type referenced through 'OpenQA.Selenium.IWebElement' is defined in an assembly that is not referenced. You must add a reference to assembly 'WebDriver'.
I'm pretty sure I loaded the reference to WebDriver.dll using the #r "/packages/Selenium.WebDriver.2.35.0/lib/net40/WebDriver.dll" command.
Have you encountered this issue before?
PS Forgive me. I intended to label this as a question -- not an issue -- but I'm not sure how to add the label.

I had the same issue (with latest canopy) and I think it was due to order of referencing the dlls. The following works:
open System
open System.IO

//------------------------------------------
// Step 0. Get the package bootstrap. This is standard F# boiler plate for scripts that also get packages.

let packagesDir = __SOURCE_DIRECTORY__ + "/script-packages"
Directory.CreateDirectory(packagesDir)
Environment.CurrentDirectory <- packagesDir

if not (File.Exists "paket.exe") then
    let url = "https://github.com/fsprojects/Paket/releases/download/1.2.0/paket.bootstrapper.exe" in use wc = new System.Net.WebClient() in let tmp = Path.GetTempFileName() in wc.DownloadFile(url, tmp); File.Move(tmp,"paket.bootstrapper.exe"); System.Diagnostics.Process.Start("paket.bootstrapper.exe") |> ignore;;

//------------------------------------------
// Step 1. Resolve and install the Canopy package and the Chrome web driver
// You can add any additional packages you like to this step.
#r "script-packages/paket.exe"

Paket.Dependencies.Install """
    source https://nuget.org/api/v2
    nuget Canopy
    nuget Selenium.Support
    nuget Selenium.WebDriver.ChromeDriver
""";;

//------------------------------------------
// Step 2. Reference the canopy framework libraries and configure chrome
#r @"script-packages/packages/Newtonsoft.Json/lib/net40/Newtonsoft.Json.dll"
#r @"script-packages/packages/Selenium.WebDriver/lib/net40/WebDriver.dll"
#r @"script-packages/packages/Selenium.Support/lib/net40/WebDriver.Support.dll"
#r @"script-packages/packages/canopy/lib/canopy.dll"
#r @"script-packages/packages/SizSelCsZzz/lib/SizSelCsZzz.dll"
open canopy
open runner

canopy.configuration.chromeDir <- Path.Combine(packagesDir, @"packages\Selenium.WebDriver.ChromeDriver\driver")

//------------------------------------------
// Step 3. Open Chrome and go to Dynamics NAV page

let root = "http://localhost:8081/DynamicsNAV80/WebClient/"

start chrome

url root

Thanks @forki !

I tried the script, had to add 'nuget Newtonsoft.Json' to the Paket.Dependencies.Install section, and then it was sweet.
Thanks @forki too :)

This may help too: https://github.com/amirrajan/canopy-repl/blob/master/CanopyRepl.fsx

@forki's script still works, but as noted above you need to add Newtonsoft.Json AND SizSelCssZzz to the paket dependencies now


open ai key were is it

were is the open ai i key------
┌──(user1㉿user1)-[~/nuclei-cve-gpt]
└─$ ncvegpt CVE-2022-0349
2024/02/09 18:45:49 set OPENAI_KEY environment variable

sorry were to add it***

the output is telling you what to do.. set OPENAI_KEY environment variable.
I don't know which OS it is running on... search on google how to set env variables on Linux/windows/macOS/whatever
Note that This is an ongoing experiment. as written in the readme

i did i did man, i did all of that, i even figure out how to set the env var. it still doesnt work man. im on kali

$> ncvegpt CVE-2023-27301
2024/02/11 10:09:04 set OPENAI_KEY environment variable

export OPENAI_KEY=test

$> ncvegpt CVE-2023-27301
2024/02/11 10:09:32 ChatCompletionStream error: error, status code: 401, message: Incorrect API key provided: test. You can find your API key at https://platform.openai.com/account/api-keys

this is for linux, all clear?


update the variables used in page titles

Currently, our page titles are always <H1> - R3 Documentation. It would be more useful to include the product version of the content.
For example, currently, if a user searches Google for a Corda-related term, there is nothing to indicate what version of Corda the results relate to. This will become more important after Corda 5 is released.

Preview built here: https://paul.preview.docs.r3.com/


Create locator for asset fails when EndTime is set - Error from MKIO API "Streaming Locator load failed."

Trying to create a locator for an asset with a endtime set 2 hours ahead (Utc.Now + 2 Hours) and the Api fails with:

Code used to create locator is as follows:
 var newLocatorProps = new MK.IO.Models.StreamingLocatorProperties  {      AssetName = assetname,      StartTime = DateTime.UtcNow,      EndTime = DateTime.UtcNow.AddHours(2),      StreamingPolicyName = "Predefined_ClearStreamingOnly"  };  var newLocator = await client.StreamingLocators.CreateAsync(Guid.NewGuid().ToString(), newLocatorProps);
If endtime is removed then to operation completes successfully.
Version used 1.2.1 with Asp.Net 8 website. Based in UK so dd/mm/yyyy date format, shouldn't matter but you never know!

Good catch! I fixed it https://github.com/xpouyat/MK.IO/commit/9ced27c4ded9e30cf2ba4733117c915d0502b430
A new release (1.2.2) should be available in a few minutes on Nugget.

Awesome. Thanks for the quick fix. Can confirm it works as expected with 1.2.2.


Switch to google-api-python-client instead of using deprecated google-apitools

Imported from Jira BEAM-9823. Original Jira may contain additional context.
Reported by: tvalentyn.

.take-issue

.close-issue
https://github.com/apache/beam/issues/19073 is more recent and general and will be resolved using Python Client for Cloud Storage API instead.


customize: friendly_name

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.36.0
Component/platform:
Core
Description of problem:
The notifications shown in  does not use the friendly_name specified in customize:
Expected:
Name specified using customize: should be used
Problem-relevant configuration.yaml entries and steps to reproduce:
customize:
switch.neo_coolcam_power_plug_12a_switch_2_0:
friendly_name: Test
The friendly_name is shown on the card.

Are you indenting correctly?
homeassistant:
  customize:
    light.blah:
      friendly_name: test

Yes.. It's working on other places but not in toasters

Markus Thiel
<EMAIL_ADDRESS>0704530353
On 17 Jan 2017, 21:31 +0100, andrey-git<EMAIL_ADDRESS>wrote:

Are you indenting correctly?
homeassistant: customize: light.blah: friendly_name: test
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/home-assistant/home-assistant/issues/5388#issuecomment-273290629), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAkhvyE7rrGAcLsEd17gubHhFluubiEJks5rTSUsgaJpZM4LlY6k).

Do you mean the little bottom-right popup/toast that says the entity name that was turned on/off etc?

Bottom left yes

Markus Thiel
<EMAIL_ADDRESS>0704530353
On 17 Jan 2017, 22:11 +0100, happyleavesaoc<EMAIL_ADDRESS>wrote:

Do you mean the little bottom-right popup/toast that says the entity name that was turned on/off etc?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub (https://github.com/home-assistant/home-assistant/issues/5388#issuecomment-273300777), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAkhv99-A419qCeiHUPI_rrwsc4KiQyMks5rTS6QgaJpZM4LlY6k).

That is correct. It has always been this way, so I have labeled this as an enhancement request for the frontend.


Fixed a typo

:- )

Thank you for opening PR! I am happy to merge it!
configurationNames is also should be modified, but I am happy to do it.


Filemode support, and binary issue

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Proper frontend testing

[ ] https://kentcdodds.com/blog/common-mistakes-with-react-testing-library
[ ] https://github.com/testing-library/eslint-plugin-testing-library

https://github.com/takefumi-yoshii/nextjs-testing-strategy-2022.git


Error when using browser_domain

When trying to use
fake_header = FakeHttpHeader(browser_domain = 'de')
print(fake_header)

it returns
TypeError: __init__() got an unexpected keyword argument 'browser_domain'
using latest version from PyPi
It should be domain_name  then it's working - Typo in code or readme?
Thanks for this awesome work! Really helps :-)

Thanks for the kind words. It is indeed a typo in the readme file. :-)


python: log experiment with html

Would tqdm auto work for this in a better way?

Would tqdm auto work for this in a better way?

haven't used before, would it?


Lowercased SourceLocation

Hello,
is there a particular reason to have the SourceLocation lowercased?
In particular in these two situations:
https://github.com/hbuckle/puppet-powershellmodule/blob/a91a6d4f378e6c7ad8bc4dfc0f817ee59509c8f1/lib/puppet/type/psrepository.rb#L30
and
https://github.com/hbuckle/puppet-powershellmodule/blob/a91a6d4f378e6c7ad8bc4dfc0f817ee59509c8f1/lib/puppet/provider/psrepository/powershellcore.rb#L73
Since I think most of the webserver out there doesn't rewrite urls (e.g. Nexus Sonatype doesn't do it), I was wondering if removing these parameter alteration would be a thing.

Hi - this is just an internal thing to make it easier to compare strings. Although URLs aren't case sensitive, Puppet is so if the casing were different Puppet would think it needed to be changed. It should have no effect on actually interacting with repos.

It does affect the interaction with repos, this code for example doesn't work with the lowercase:
psrepository { 'PSGalleryProxy':     ensure              => present,     source_location     => 'http://mylocalnexus/repository/PowerShellGallery_proxy/',     installation_policy => 'untrusted',     provider            => 'windowspowershell',   }
Since a call to "http://mylocalnexus/repository/PowerShellGallery_proxy/" returns 200, a call to "http://mylocalnexus/repository/powershellgallery_proxy/" returns 404 hence the Set-PSRepository command returns malformed URL

Ah ok, I didn't know that some servers treated the URL as case sensitive. I should be able to update this to remove the lower casing.

I've got minimal modification in my current workspace, if you want I'll make a pull request :)

2.0.0 makes source location case sensitive


Bump framework to onboard role v2 group mgt related improvements

Description
Bring the framework changes onboarded from https://github.com/wso2/carbon-identity-framework/pull/5462

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7751951567

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7751951567
Status: success


Debugging Hangs when default terminal app doesn't exist

To test: Set Terminal.External.LinuxExec to an app that doesn't exist.
Start debugging with external terminal (I used the C++ extension and set externalConsole to true).
Expected:
Failure response for RunInTerminal command.
Actual:
No Response from VS Code's debugadapter protocol.
UI looks like it is waiting for debugging to start.

@weinand This is becoming a bigger issue especially in the VS Code remote scenario as it doesn't fail with a good message to the user. Can we prioritize this to be fixed?

@pieandcakes this issue had been partially addressed in VS Code but it still needs some work on the extension side. Please see https://github.com/microsoft/vscode-remote/issues/734.

@weinand Apparently when trying to find https://github.com/microsoft/vscode-remote I get a 404 so I can't see that issue.

@pieandcakes I've fixed the broken link...

Thanks. I look forward to testing it.

Heads up I am still seeing situations where you get the "hang" with externalConsole=false (the internal console) but the external console works fine. This is on 1.35.0-insider 2019-05-17 on Real Linux Ubuntu to Real Linux Ubuntu with Remote SSH, but I saw the behavior last December-February too without inviting Remote to the party. Unfortunately it is really hard to give definitive repro steps to get in that state, because there are so many moving parts. And I know that doesn't help you. I am hoping that whatever error UX is forthcoming might shed some light. Mentioning it because if I've hit it you'll probably hear from someone else eventually too.


Add a cache decorator

Current Situation
We currently don't have any multiprocessing compatible way to cache component renders, similar to Django's cached_page decorator.
Proposed Actions
Create a caching decorator. The API might look something like this....
def cache_component(timeout, *, cache=None):
    """The cache is keyed by the component's dotted path."""
    ...
    return decorator

@cache_component(60 * 15, cache=REACTPY_CACHE)
@component
def example():
   ...

Closing this since it is not technologically possible to maintain interactivity while also catching renders.


Add new deployment via Ansible

This PR reworks the way ccc repo is installed and deployed using Ansible playbook and collections

Reopen to test github actions until upstream merge


Fix window tests for Spark-3.4

This PR fixes window tests for Spark-3.4 by catching the correct Exception
fixes #6988
Signed-off-by: Raza Jafri<EMAIL_ADDRESS>

build


[Formatter] Fix (?) leading/trailing newline

4d9adf2e47a0bf121f294293fea25441f22f7c79 introduced a leading new line to the formatter, which is slightly annoying upon formatting a file.
I'm a bit afraid of touching that diff's comment logic, so I used the catch-all solution of trimming the final input (then appending a newline).
This also has the effect of adding a newline to some existing tests which don't end with one. I think this is desired? If not, I can replace trim with a trim_leading or something.
@jordwalke @yunxing

@yunxing @jordwalke merging this because I'm OCD-ing over the missing/extra lines at places. Retrospective comments welcome!


change dead text to X is dead

About the PR
noob trap into thinking someone cant be revived by saying soul departed
probably shamelessly stolen from nyano idk
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
no cl no fun

Not even "She doesn't appear to be breathing", my soul. Also we need deathgasping

John Doe whispers with a last dying breath, "jane doe syndie"


Dockerhub build: "not found"

Are you experiencing an issue with...

[X] shields.io
[ ] My own instance
[ ] gh-badges NPM package

:beetle: Description
The badge https://img.shields.io/docker/build/rivethealth/aws-saml shows "repo not found", despite the existence of the repo: https://hub.docker.com/r/rivethealth/aws-saml

Try using the cloud build badge. The badge at the ../docker/build/..  is more of a legacy badge to support "older" repositories that were created prior to docker's launch of the "new" docker hub (back in 2018)
https://img.shields.io/docker/cloud/build/rivethealth/aws-saml

I assume that's working for you @pauldraper, so going to close this. Feel free to re-open if needed


Upgrading to Julia 1.x

I'm opening this issue to begin a conversation about upgrading BayesianDataFusion.jl to be compatible with the most recent version of Julia, 1.x. We've begun upgrading the package on a fork and have succeeded in bringing most it up to date.
I have a few questions for you:
Meta-level questions

Are you interested in being included in discussions about the upgrade as it proceeds?
Once the upgraded version is feature complete, would you consider a pull request to this repository?

Substantive questions

The current implementation allows multithreaded sampling only when there is 1 featureless relation: https://github.com/jaak-s/BayesianDataFusion.jl/blob/7c9b3de22cd61f03913e79058bea86bf01acb7b4/src/macau.jl#L64
Why? Is it impossible in principle to run Macau across multiple threads or machines when there is more than one relation or a relation with features? Or is this rather a limitation of the implementation as it stands?
test/sparse_csr.jl tests a function named sparse_csr that casts a matrix of type SparseMatrixCSC to type SparseMatrixCSR. However, SparseMatrixCSR matrices are not used anywhere in the codebase except in tests. Is this a vestige of previous development? Is there any reason why it cannot be removed entirely?
macau_blocked.jl appears to be a stub that is not used anywhere in the code. Can it be safely removed?
macau_hmc.jl, macau_sgd.jl, and macau_vb.jl appear to implement Hamiltonian Monte Carlo, Stochastic Gradient Descent, and Variational Bayes variants of Macau. However, only the HMC variant has tests. Are all three functional? Are there any limitations? (Specifically, can they be used to fit any model that macau.jl can fit?)

Meta

I'm happy to help this upgrade process.
Yes, pull request to this repository would be welcome!

Details

There is no limitation from Macau. I think the reason was that I implemented parallel version only for a special case of a single relation.
Yes, you can remove it. It is not currently used, if we need it in the future we can bring it back again.
macau_blocked.jl can be removed.
I quickly scanned the code and macau_hmc.jl, macau_sgd.jl and macau_vb.jl all solve only the special case of a single matrix without side information, i.e., the standard BPMF. So I don't mind retiring these files as they are not required for the main functionality of the package.

Regarding parallelism, do you have a sense of how much effort would be required to implement parallelism for the general multi-relational plus side-information case?

Actually, I think the effort might not be too large at all (unless I've forgotten something).
Basically, the algorithm is the same when sampling the latent matrix of one entity, each row can be sampled independently. Thus, one can parallelize over rows. The complexity in the multiple relation case is that for each row one needs to access data from more than one relation. But otherwise the parallelization strategy is the same.


MAINT: remove deprecated np.random.random_integers

See numpy/numpy#6931.
The replacement with np.random.randint is pretty straightforward.

LGTM. I didn't even know about random_integers and this simplifies all the code that uses it.

@@            master   #5792   diff @@
======================================
  Files          235     235
  Stmts        43257   43282    +25
  Branches      8152    8155     +3
  Methods          0       0
======================================
+ Hit          33639   33664    +25
  Partial       2591    2591
  Missed        7027    7027

Review entire Coverage Diff as of 53fbfd9

Powered by Codecov. Updated on successful CI builds.

LGTM too. Thanks CJ, Lars.


0.1: Avoid eagerly running executors when waiting for FutureResult or Option

(I would make a 0.3 PR as well but I would appreciate some pointers as to where to look in the code for FutureResult, Option and Either)

TBH I'm not sure why the buffer_unordered::works test is stalling. Locally it passes instantly.

That's not ideal for cases like this. A trait BlockOn that is implemented by default for all futures but can be overridden in the case of "already resolved" futures would be useful.

Using Future::wait is often times incorrect, and thus it is deprecated. While the optimizations here seem neat, these futures don't actually do much when calling wait anyways. There is a fresh_task_id() call, a TLS access, and then poll. It doesn't "spin up an executor".
For those reason, I'd lean towards leaving this out, leaving it uncomplicated, and encouraging more people to not call Future::wait.

@seanmonstar I see, I didn't realize wait was deprecated. Thanks for the feedback.
Perhaps the general idea of this PR would be something more in the vein of lazily initializing the thread-local executor when polling. Perhaps only doing the fresh_task_id work when task::current is actually called.


Add SCSS to source

So I continued building on #882 and came up with this.
It's mostly done, some colors needs SCSS variables but I did not put any time into that at this moment.
I have added the ability to change the global selector in SCSS, but there is not support in the Vue setup of course. That might need some looking into.
Other than that I made a fork of the latest master, removed the inline CSS and added a subfolder for SCSS with variables and a style.scss.
Please have a look and report back if you find anything broken, missing etc. I have compared the generated CSS with the old one and it seems I managed to get everything right. Might need to double-check some colors though.
Edit:
A big plus with using a global classname setting is that we can avoing clashes with other libs added. I also added the classname var to the keyframe so that it is prefixed.

I should add that I see no reason to add the .scss files to the /dist folder. Most NPM-packages that includes the /src folder points devs to using /src/scss/ of they need to use the SCSS in their pipeline.

As the src-Folder is in the package I agree with not copying over the SCSS file(s). However, and this is unrelated to the current problem, I generally vote for small packages and not distributing all source files.
Anyhow, as this is a much newer and cleaner approach to #882, should we close the latter?

Hi, thanks for your hard work.
Is this going to land someday?
It would be great to have SCSS variables instead of a lot CSS overrides.

I am no longer using either the library or Vue. So this is abandoned from my end. Feel free to pick up where I left though.


disable external keyboard support in the wallet app

The wallet shouldn't support any third party keyboards such as Gboard or say SwiftKey for security purposes. The external keyboards should not be supported in the app due to the fact that they can potentially expose the secret keys of the wallet.
At the moment if user has the GBoard installed then some controllers like (wallet restore) where user sees keyboards allow user to switch to the custom keyboards. We need to disable that.

@rafaelekol The usage of non-native External Keyboard Allowed in some cases
At the moment the keyboard check happens when user transtions to "secret key input" screen. If the selected keyboard meets the criteria then no alert will be shown on transition. However, if the user changes/selects the keyboard while remaining on the "secret key input" screen no alert will be shown and user is able to user the selected keyboard to input secret key.
Reproduceable on Samsung A6 device, build 0.1.1 (499). Likely to appear on most of other Android devices as well.


Document Proxy Env Vars

Issue #, if available:
Follows https://github.com/aws/eks-anywhere/pull/2849
Description of changes:
This change documents support for using EKS-Anywhere behind a Proxy via environment variables.
Previously, only commands using a cluster config file could use a proxy.
Now, you can use a proxy for any command by setting the documented environment variables.
Additionally, I added documentation that to successfully use a proxy you will need to update your docker daemon's configuration as described in docker's own documentation.
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approved

/approve

/lgtm

/lgtm

/cherrypick release-0.11


Model weights for crnn trained on special characters and space along with English alphabets?

Has anyone successfully trained a model to recognize special characters and spaces. If so could you please share the model weights.
Thank you

Hope will help you https://github.com/Sierkinhane/crnn_chinese_characters_rec


Testing a package

Specs

Leon version: 1.0.0-beta.3
OS (or browser) version: Firefox
Node.js version: 10.16.0
Complete "npm run check" output: Hooray! Leon can run correctly
(if using Docker) Complete "npm run docker:check" output: nope
(optional) Leon package version:

Expected Behavior
I've written this package but leon is able to recognize only the first expression set even if I ask him something different that should match other expression sets. So I tried to momentarly remove the first expression set and see what would happen. This is the result, but it's not very informative to me.
Actual Behavior
.: NER :.

➡ Searching for entities...
(node:69002) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'entities' of undefined
    at Promise (/Users/federico/Dropbox/GitHub/leon/server/dist/core/ner.js:57:49)
    at new Promise (<anonymous>)
    at Ner.extractActionEntities (/Users/federico/Dropbox/GitHub/leon/server/dist/core/ner.js:37:12)
    at Nlu.process (/Users/federico/Dropbox/GitHub/leon/server/dist/core/nlu.js:159:37)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:69002) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)

How Do We Reproduce?
You might need the package...
Extra (like a sample repo to reproduce the issue, etc.)

Hello @Imperator26,
Thanks for opening that issue and for creating a new package if I understood correctly.
Could you please give more context? What's the package for? What are you doing exactly (commands, etc.) to get this error?

Yes I'm working on a simplier weather package myself. You can check it out at my fork

Well done! I've tried your fork and it's working pretty well.
Now regarding your concern, could you please provide me the expressions file that is causing that error and also tell me what sentences are you giving to Leon?

@louistiti If you try to ask him "When is the sun going to rise in London?" it doesn't work. He answers like I asked "What's the weather like in London?". I tried npm run train expressionsmultiple times, but that did't work. So I tried to momentarely remove the expression "What's the weather like in", but I get the error above.

It looks good here :thinking:
I'm on this commit.

It looks good here 🤔
I'm on this commit.
Maybe try to git pull and reinstall the project, several changes have been made since your fork.

Interesting... I'll try that

It works I'll make a PR

PR #108


The revert of EOF detection change in libssl for 1.1.1

Checklist

[x] documentation is added or updated

I think we should not remove things from the public headers.

I think we should not remove things from the public headers.

If we do 1.1.1f release ASAP I think it should not be a problem in this case. Especially that the presence of SSL_R_UNEXPECTED_EOF_WHILE_READING define can be used in applications to check the proper EOF handling in the OpenSSL 3.0.

If you think we should keep the BIO_FLAGS_IN_EOF I would be OK with that, but then we need to drop the revert of all the BIO changes. So please tell me what do you prefer.

I see no issue keeping BIO_FLAGS_IN_EOF...  but it could be perceived as an added feature...

I see no issue keeping BIO_FLAGS_IN_EOF... but it could be perceived as an added feature...

Or a bug that it wasn't there in the first place?

Maybe in case we get the unexpected EOF, we should just simulate
the old behaviour?

Maybe in case we get the unexpected EOF, we should just simulate the old behaviour?

That's what the revert of the changes in libssl does.

I see no issue keeping BIO_FLAGS_IN_EOF... but it could be perceived as an added feature...

We already did this for 1.1.1e because it was needed for the proper EOF handling, so I do not see an issue if we just keep it.

So I've changed the PR to revert only the libssl changes.

I wonder if s_client can detect the unexpected EOF, and if we
should still let it return an error.

So I think the answer to that is, just it can detect it, it now
prints this "Success" error message. I think we should turn that
into a proper error message.

So I think the answer to that is, just it can detect it, it now prints this "Success" error message. I think we should turn that into a proper error message.

That should be a different PR.

Merged to 1.1.1 as 0cd2ee64bffcdece599c3e4b5fac3830a55dc0fa and 30d190caf311d534867df97e26b552e628cb7d85


Update websocket tests to solid-0.1 draft?

Should the websockets tests follow the draft at https://github.com/solid/solid-spec/blob/master/api-websockets.md?

Done


style: change request page

Thanks for submitting a PR! Please check the boxes below:

[x] I have run pre-commit to check linting
[x] I have added information to docs/ if required so people know about the feature!
[x] I have filled in the "Changes" section below?
[x] I have filled in the "How did you test this code" section below?
[x] I have used a Conventional Commit title for this Pull Request

Changes
Currently the alignment of approvers is incorrect as well as the spacing being off compared to other pages.
Before:

After:

How did you test this code?

View CR page, tested at different device widths

We don't have style as accepted prefix for PR names, please add it or change this PR name.


Artifacts at x16 upscale

I dont think these black lines were present at x4 upscale but at x16 they are present at first I thought it was because some pixels were transparent at the mask layer but even with changing to solid black it persists.

Those lines might be from some sort of math error. What field is this from. Could you list a few steps to help reproduce the problem? I haven't looked at this on a bit so might be hard for me to figure it out right away

I tried x16 upscale on a different field with animations and there was no black lines, its elview2 heres the link to the files
https://www.dropbox.com/scl/fo/no84fb6lk3j2us9nta2do/APLOuZbXX8pMnsY2-cKO8EA?rlkey=wfocy7z3gt2tqmdxir01gxhh9&st=zh9nlmtx&dl=0

I just spent 2 days getting things to compile again. lol. now is Christmas. There were some new bugs surfaced. I'm gonna try to knock out the bugs and hopefully get to this before the end of my Christmas break.

I do wonder how you generated these. I'm gonna try to output some my self and upscale them, and compare.

I dont think these black lines were present at x4 upscale but at x16 they are present at first I thought it was because some pixels were transparent at the mask layer but even with changing to solid black it persists.

This screen shot from in game?

I did notice your pack is missing these elview2_0_1, elview2_0_6, elview2_0_7
those extra images are generated when some tiles are overlapping. Though I dunno if the game can read them yet.

might not be causing your issue though

so I upscaled that one image 16X and made all the non transparent pixels red. and overlaid your image and you can see the red showing through. I think this means that your missing some data in those pixels.

I always deleted those extra layers because I thought they caused issues with animations? Maybe not? So I redid the layers again with original upscaled and it seems fixed now.

But sometimes the blocky layers can cause problems such as this one if I try editing the texture in its swizzled state it becomes black, whats the best way to smooth the edges out?

I managed to fix it by editing the layers before swizzling, then I had to add on areas that was cut off by the swizzle process thanks its all fixed now

i see ya figured that out.

I managed to fix it by editing the layers before swizzling, then I had to add on areas that was cut off by the swizzle process thanks its all fixed now

Blockiness is caused by the 16x16 tiles being blown up. it's less of an issue where the overlapping pixels don't have characters walking behind them. Just gotta make sure the two tiles the game sees still touch in the end. :)


⭐FEAT: Make the Readme well organized and easy to read

TODO :

In the main Readme file , look for ways to make the Readme more concise or better looking.
The markup language used doesnt look well organized and same throughout

Hey @ArslanYM, can I try my hand at this?

@AshwanthramKL please do🫱🏻🫲🏼🫱🏻🫲🏼


Update common-field-properties-legacy.md

Updating the Searchable property to reflect that it only affects "Edit Filters" but not "Edit Columns" in UCI, which is the intended behavior per PM.

@igorantunesms - What fields aren't displayed when the Searchable option isn't selected?


feat(localize): updated translation from Crowdin

:tada: This PR is included in version 3.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Loadbalancer IP (MetalLB) not changeable anymore in Rancher 2.6 (GUI)

Last week I have started studying Rancher 2.6 and I really like it.
Things are running great except one:
Situation:

Rancher 2.6 ist installed and a new custom RKE-clsuter has been set up successfully
MetalLB with configmap is installed (with IP range) - automatic assignment of IPs is working well and as expected.

Problem:
In Rancher 2.5.9 (in the old GUI) while editing the deployment related loadbalncer service there was still an option "loadbalancer IP" available which I could easily fill in and change the loadbalancer IP (if needed) e.g. from <IP_ADDRESS> to <IP_ADDRESS> as long as it is part of the IP-range which I configured in MetalLB.
If you have an idea or approach how to handle this in Rancher v2.6 your help is very much appreciated! 😃
Many thanks in advance.

@maveice Could you please provide a set of steps that you use in the 2.5.9 to set the load balancer IP. When you say "Old GUI", I assume you mean the Cluster Manager UI?

@nwmac - yes, "Old GUI" means "Cluster Manager UI" (in 2.5.9).
Steps:

Pls. go to project "Default", then to the tab "Load Balancing"
Edit one of the loadbalancing services
At the bottom of the right hand side there is an option "Show advanced options" - click it
Please look for the field/box which is headlined "Load Balancer IP": You can insert your desired MetalLB IP there (as long as it is in the defined range)

Please let me know, if there are any further questions.

My checks PASSED
Reproduction Environment:

Rancher version: v2.6.0
Rancher cluster type: single-node docker install
Docker version: 20.10
Downstream cluster type: n/a
Downstream K8s version: n/a
Reproduction steps:

Explore a cluster. Go to Service Discovery -> Services -> Create.
Create a Load Balancer
On the Create LoadBalancer form, click on "IP Addresses" and notice there is no field for Load Balancer IP any longer:

Validation Environment:

Rancher version: v2.6-head 931a0f09d pulled at 11/1/21 ~1:15pm Arizona time
Rancher cluster type: single-node docker install
Docker version: 20.10
Downstream cluster type: n/a (does not matter)
Downstream K8s version: n/a (does not matter)
Validation steps:

Explore a cluster. Go to Service Discovery -> Services -> Create.
Create a Load Balancer
On the Create LoadBalancer form, click on "IP Addresses". Notice the Load Balancer IP field now exists :)
Successfully created a Load Balancer. Ensured the request/response to/from the server appeared correct.

Confirmed that the services POST request had content loadBalancerIP and was set to "<IP_ADDRESS>" in the spec. The response looks normal.
Edited this service (the lb entry). Confirmed in the UI I still see my Load Balancer IP address. I modified this to "<IP_ADDRESS>" and saved. A PUT request for test (the name of my service) was sent successfully with the modified loadBalancerIP in the spec. This response also looks normal.
Additional Info:
I do not have a suitable means to set up a custom cluster with MetalLB in a reasonable amount of time to test this with such a setup/scenario; however, considering this was just a frontend change my validation of the field and confirmation that edits (PUT requests) works as expected should be sufficient.


Hex-Bin-Dec-converter not working

Describe the bug
No prompt appearing when we click on  Hex-Bin-Dec-converter inside Tools
To Reproduce
Steps to reproduce the behavior:

Go to 'Simulator
Click on 'tools'
Then Click to 'Hex-Bin-Dec-converter'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Old UI:

Screenshots
New UI:

Device Information [optional]:

OS: [e.g. Windows 10]
Browser [e.g. chrome]

Are you working on this issue? (Yes/No)
No

it's working in my case

@Rajat-S-Patel  its not working on beta   https://beta.circuitverse.org/simulator can you  try this URL

yes, It's not working on beta

@satu0king  can you take a look please

@satu0king can you take a look please

Yes it has not been migrated, we just need to migrate the code.

Fixed


Fix/do not retrive nulls

The get_parameter_data method of the DataSet currently retrieves everything in each result column of the SQLite result table, including NULLs. This PR suggests to change that behaviour to only fetch the non-NULL values. The filtering is conditioned on the top-level parameter's values.
Changes proposed in this pull request:

introduce a new sqlite function to retrieve N+1 columns of data, filtered conditioned on one of the columns being non-NULL
make get_parameter_data use that
add two tests for scenarios where NULLs are present in the result table

@QCoDeS/core
EDIT: This is needed before I can proceed with #1477

@QCoDeS/core I think the latest push addresses all concerns. Do you agree?


Rebase

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: iuriimattos:x: iuriimattos2You have signed the CLA already but the status is still pending? Let us recheck it.


gulp packaging is failing

I'm guessing that there are missing steps. For one thing, actually running "gulp pack:linux{32|64}:deb" fails badly. Running "gulp 'pack:linux64:deb'" seems to succeed, but ultimately fails to produce a .deb.
Installing fpm wasn't described, so I tried "npm install -g fpm". That appeared to work, but the gulp packaging failed with "/bin/sh: 1: fpm: not found". After running "npm install fpm" in the F-M-D source directory and trying again, packaging appears to run to completion, but produces no output.
localhost Facebook-Messenger-Desktop [0]# gulp 'pack:linux64:deb'
[01:18:49] Requiring external module coffee-script/register
[01:18:50] Using gulpfile /usr/src/Facebook-Messenger-Desktop/gulpfile.coffee
[01:18:50] Starting 'build:linux64'...
[01:18:50] Using v0.12.2
[01:18:50] Create cache folder in /usr/src/Facebook-Messenger-Desktop/cache/0.12.2
[01:18:50] Using cache for: linux64
[01:18:50] Create release folder in /usr/src/Facebook-Messenger-Desktop/build/Messenger/linux64
[01:18:50] Zipping app.html
[01:18:50] Zipping package.json
[01:18:50] Zipping app.js
[01:18:50] Zipping images/icon.png
[01:18:50] Zipping images/icon_menubar.tiff
[01:18:50] Zipping images/icon_menubar_alert.tiff
[01:18:50] Zipping images/icon_tray.png
[01:18:50] Zipping images/icon_tray_alert.png
[01:18:50] Zipping images/loading.gif
[01:18:50] Zipping components/dispatcher.js
[01:18:50] Zipping components/menus.js
[01:18:50] Zipping components/notification.js
[01:18:50] Zipping components/settings.js
[01:18:50] Zipping components/platform.js
[01:18:50] Zipping components/themer.js
[01:18:50] Zipping components/updater.js
[01:18:51] Zipping components/window-behaviour.js
[01:18:51] Zipping components/utils.js
[01:18:51] Zipping styles/app.css
[01:18:51] Zipping styles/auto-hide.css
[01:18:51] Zipping themes/dark.css
[01:18:51] Zipping styles/base.css
[01:18:51] Zipping themes/default.css
[01:18:51] Zipping themes/mosaic.css
[01:18:51] all done!
[01:18:51] Finished 'build:linux64' after 957 ms
[01:18:51] Starting 'pack:linux64:deb'...
1.5.3
[01:18:52] Finished 'pack:linux64:deb' after 1.22 s

I'm guessing that fpm isn't being invoked correctly, but I have no idea how to do it. I'm not even slightly familiar with node.js, and I'd just like this to work.

To install fpm I actually add to install a lot of garbage. Mainly:
apt-get install ruby-dev gcc make
yum install ruby-devel gcc
That make it work (at least for me) but you will also have the full ruby development stack...

@Sytten , I had all of these packages installed when the gulp packaging failed. I build a lot of tools by hand, so I've got most of the GNU toolchain installed and quite a lot of -dev packages installed on this particular machine.

Well I don't really know what to tell you, it works on my end...
This guy had problems too.
https://github.com/Sytten/Facebook-Messenger-Desktop/pull/8#issuecomment-168816898

You mentioned a new app? That's starting to seem like a better solution...

Yep I didnt follow the news related to it for a while, better check on the gitter of the original dev...


Add optional meta data parameter to Agent

Ideally it could also be used with AgentList.from_csv() -- need a way to specify the CSV columns that should be treated as meta data though.

Or, there could be another feature for selecting traits that you want to turn into meta data, and vice versa.

Add "include" and "exclude" parameters to the constructor that will be optional lists where the strings have to correspond to trait fields.


tutorial

@B2o5T Love it, and for all npm or yarn install blocks use <PackageInstall /> component because it has tabs for npm yarn or pnpm + it has copy button

This is currently blocked by https://github.com/the-guild-org/the-guild-docs/issues/510, I added the task to replace the install instructions to https://github.com/dotansimha/graphql-yoga/issues/916

@n1ru4l let's merge it and continue with the advanced one


Fix the timelock.py test in scalable rendering mode.

Description
The hybrid/timelock.py test was hanging when running in scalable,parallel,icet mode. I looked at the test and there were some tests that were not run when in that mode with the comment that those tests caused a crash in scalable,parallel,icet mode. I added an SetTimeSliderState call to the conditional code and the tests were successfully skipped and the test ran to completion.
Here is the output without the change.
Saving window 2...
VisIt: Message - Saving window 2...
Saved /usr/WS1/visit/test_trunk/build/test/output2/current/hybrid/timelock/timelock_16.png
VisIt: Message - Saved /usr/WS1/visit/test_trunk/build/test/output2/current/hybrid/timelock/timelock_16.png
    Test case 'timelock_16' PASSED
Executing pipeline.
0% done: Starting execution (0% of stage 1/17)
0% done: Reading from Flash File Format (0% of stage 1/17)
5% done: Reading from Flash File Format (0% of stage 2/17)
5% done: Waiting for all processors to finish I/O (0% of stage 2/17)
11% done: Waiting for all processors to finish I/O (100% of stage 2/17)
11% done: Waiting for all processors to finish I/O (0% of stage 3/17)
11% done: Handling missing data values (0% of stage 3/17)
17% done: Handling missing data values (100% of stage 3/17)
17% done: Handling missing data values (0% of stage 4/17)
17% done: Creating expressions (0% of stage 4/17)
23% done: Creating expressions (100% of stage 4/17)
23% done: Creating expressions (0% of stage 5/17)
23% done: Handling missing data values (0% of stage 5/17)
29% done: Handling missing data values (100% of stage 5/17)
29% done: Handling missing data values (0% of stage 6/17)
29% done: Preparing pipeline (0% of stage 6/17)
35% done: Preparing pipeline (100% of stage 6/17)
35% done: Preparing pipeline (0% of stage 7/17)
35% done: Preparing pipeline (0% of stage 7/17)
41% done: Preparing pipeline (0% of stage 8/17)
41% done: Cleans up duplicate points from a poly line (0% of stage 8/17)
47% done: Cleans up duplicate points from a poly line (0% of stage 9/17)
47% done: Finding visible triangles (0% of stage 9/17)
47% done: Calculating external faces (0% of stage 9/17)
52% done: Calculating external faces (100% of stage 9/17)
52% done: Calculating external faces (0% of stage 10/17)
52% done: Removing ghost cells (0% of stage 10/17)
58% done: Removing ghost cells (0% of stage 11/17)
64% done: Finding visible triangles (0% of stage 12/17)
64% done: Removing unneeded points (0% of stage 12/17)
70% done: Removing unneeded points (100% of stage 12/17)
70% done: Removing unneeded points (0% of stage 13/17)
70% done: Calculating normals (0% of stage 13/17)
76% done: Calculating normals (0% of stage 14/17)
76% done: Compacting data tree (0% of stage 14/17)
82% done: Compacting data tree (100% of stage 14/17)
82% done: Compacting data tree (0% of stage 15/17)
82% done: Calculating Actual Extents. (0% of stage 15/17)
88% done: Calculating Actual Extents. (100% of stage 15/17)
88% done: Calculating Actual Extents. (0% of stage 16/17)
88% done: Synchronizing (0% of stage 16/17)
94% done: Synchronizing (100% of stage 16/17)
94% done: Synchronizing (100% of stage 16/17)
Reading engine output.
free(): corrupted unsorted chunks

Loguru caught a signal: SIGABRT

Here is the output with the SetTimeSliderState added to the conditional logic.
Saving window 2...
VisIt: Message - Saving window 2...
Saved /usr/WS1/visit/test_trunk/build/test/output2/current/hybrid/timelock/timelock_16.png
VisIt: Message - Saved /usr/WS1/visit/test_trunk/build/test/output2/current/hybrid/timelock/timelock_16.png
    Test case 'timelock_16' PASSED
VisIt: Message - Window 2 was deleted.
VisIt: Message - VisIt closed "localhost:/usr/WS1/visit/test_trunk/build/testdata/pdb_test_data/dbA00.pdb".
    BEGIN SECTION: Make sure replacing into a time-locked window updates the database correlation.
Executing pipeline.
0% done: Starting execution (0% of stage 1/17)
0% done: Reading from Silo File Format (0% of stage 1/17)
0% done: Reading from Silo File Format (0% of stage 1/17)
5% done: Reading from Silo File Format (0% of stage 2/17)
5% done: Waiting for all processors to finish I/O (0% of stage 2/17)
11% done: Waiting for all processors to finish I/O (100% of stage 2/17)
11% done: Waiting for all processors to finish I/O (0% of stage 3/17)
11% done: Handling missing data values (0% of stage 3/17)
17% done: Handling missing data values (100% of stage 3/17)
17% done: Handling missing data values (0% of stage 4/17)
17% done: Creating expressions (0% of stage 4/17)
23% done: Creating expressions (0% of stage 5/17)
23% done: Handling missing data values (0% of stage 5/17)
29% done: Handling missing data values (100% of stage 5/17)
29% done: Handling missing data values (0% of stage 6/17)
29% done: Preparing pipeline (0% of stage 6/17)
35% done: Preparing pipeline (100% of stage 6/17)
35% done: Preparing pipeline (0% of stage 7/17)
35% done: Preparing pipeline (0% of stage 7/17)
41% done: Preparing pipeline (0% of stage 8/17)
41% done: Cleans up duplicate points from a poly line (0% of stage 8/17)
47% done: Cleans up duplicate points from a poly line (0% of stage 9/17)
47% done: Finding visible triangles (0% of stage 9/17)
47% done: Calculating external faces (0% of stage 9/17)
52% done: Calculating external faces (100% of stage 9/17)
52% done: Calculating external faces (0% of stage 10/17)
52% done: Removing ghost cells (0% of stage 10/17)
58% done: Removing ghost cells (100% of stage 10/17)
58% done: Removing ghost cells (0% of stage 11/17)
64% done: Finding visible triangles (0% of stage 12/17)
64% done: Removing unneeded points (0% of stage 12/17)
70% done: Removing unneeded points (100% of stage 12/17)
70% done: Removing unneeded points (0% of stage 13/17)
70% done: Calculating normals (0% of stage 13/17)
76% done: Calculating normals (100% of stage 13/17)
76% done: Calculating normals (0% of stage 14/17)
76% done: Compacting data tree (0% of stage 14/17)
82% done: Compacting data tree (100% of stage 14/17)
82% done: Compacting data tree (0% of stage 15/17)
82% done: Calculating Actual Extents. (0% of stage 15/17)
88% done: Calculating Actual Extents. (100% of stage 15/17)
88% done: Calculating Actual Extents. (0% of stage 16/17)
88% done: Synchronizing (0% of stage 16/17)
94% done: Synchronizing (100% of stage 16/17)
94% done: Synchronizing (100% of stage 16/17)
Reading engine output.
Rendering window 1...
VisIt: Message - Rendering window 1...
Scalable Rendering.
0% done: Starting execution (0% of stage 1/4)
0% done: Synchronizing (0% of stage 1/4)
25% done: Synchronizing (100% of stage 1/4)
Reading engine output.
Saving window 1...
VisIt: Message - Saving window 1...
Saved /usr/WS1/visit/test_trunk/build/test/output2/current/hybrid/timelock/timelock_21.png
VisIt: Message - Saved /usr/WS1/visit/test_trunk/build/test/output2/current/hybrid/timelock/timelock_21.png
    Test case 'timelock_21' PASSED

Type of change

[X] Bug fix~~

How Has This Been Tested?
I ran the test in scalable,parallel,icet mode without the change and verified that it hung and then ran it again with the change and it ran to completion.
Reminders:

Please follow the style guidelines of this project.
Please perform a self-review of your code before submitting a PR and asking others to review it.
Please assign reviewers (see VisIt's PR procedures for more information).

Checklist:

[X] I have commented my code where applicable.~~
[ ] I have updated the release notes.
[ ] I have made corresponding changes to the documentation.
[ ] I have added debugging support to my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[X] I have confirmed new and existing unit tests pass locally with my changes.~~
[ ] I have added new baselines for any new tests to the repo.
[ ] I have NOT made any changes to protocol or public interfaces in an RC branch.

Since this test and its crash are mentioned in #19037, do you think it should be elevated to its own ticket?  Just wondering if it would get the attention I believe it needs that way.


Support for Craft v4?

Do you plan to provide a new release with support for Craft v4?

Yes, I'll try to look into it in the next few days.
Thanks for bringing it up!

It should be working now!
Could you test it and tell if everything's ok?

Thanks, will test it next week and provide feedback!

I did some quick testing and ran into a couple of issues:

The new {{%crafthcaptcha_logs}} table wasn't created when upgrading from version 1.2.0 to 2.0.0 as part of the overall Craft v4 upgrade. I'm not sure if this is my fault as I just followed the Craft upgrade guide and had manually changed all of the various plugin versions in composer.json. I went ahead re-installed the plugin which created the appropriate table.

The verify($data) method always returns an false even though the captcha is successfully solved. I debugged the code and it appears as part of commit 9436e515 that you now check that the hostname property matches the current request's hostname. This doesn't work on my local environment (likely because it resolves to localhost) and the hCaptcha documentation recommends not checking or relying on that property:
https://docs.hcaptcha.com/#verify-the-user-response-server-side

Please also note that the hostname field is derived from the user's browser, and should not be used for authentication of any kind; it is primarily useful as a statistical metric. Additionally, in the event that your site experiences unusually high challenge traffic, the hostname field may be returned as "not-provided" rather than the usual value; all other fields will return their normal values.

I would remove that check or make it optional through a config.

Assuming that's fixed, it looks like everything should work.

Thank you for this detailed feedback, awesome!
On the first point, I need to verify and understand how Craft handles migrations but it should not impact the validation of the captcha.
For the second point, I just removed the check on the hostname for now, as recommended in the hcaptcha documentation.
I'll close this issue, feel free to reopen if you find something else!


Customer Account documentation

We need to have documentation for the customer account, I would suggest keeping the documentation in the current repo in Wiki section.

https://github.com/majidkarimizadeh/leaseweb-go-sdk/wiki/Customer-Account


Tests fail on Jenkins as of 139b75e2c185a74d6b79990763c70ad3d806ec7b

Currently the nd4j Jenkins job runs with -DskipTests because the tests fail. I am not sure what the problem is - is it the tests, or the way the Jenkins is set up (or maybe how libnd4j is built?). Please have a look: https://<IP_ADDRESS>/job/nd4j/14/console

All tests passing now.


New supported inverter (CHINT)

Hi!
just migrated from home_assistant_solarman!
My inverter is supported, It's a CHINT, a 6KW hybrid inverter, and i also have the chint-provided PDF file with the MODBUS mappings, where should i upload it to?
i manually wrote the fllowing yaml, which seems to be working quite nicely:
requests:
  - start: 0x1001
    end: 0x104C
    mb_functioncode: 0x03

  - start: 0x1080
    end: 0x1092
    mb_functioncode: 0x03

  - start: 0x1300
    end: 0x1362
    mb_functioncode: 0x03

  - start: 0x1A44
    end: 0x01A46
    mb_functioncode: 0x03

# Battery: 0x2000 - 0x2013

parameters:
 - group: info
   items:
    - name: "Rated Voltage"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1A44]
      icon: 'mdi:solar-power'
    - name: "Rated Frequency"
      class: "frequency"
      state_class: "measurement"
      uom: "Hz"
      scale: 0.01
      rule: 1
      registers: [0x1A45]
      icon: 'mdi:solar-power'
    - name: "Rated Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 1
      rule: 1
      registers: [0x1A46]
      icon: 'mdi:solar-power'

 - group: solar
   items:
    - name: "Phase A Voltage"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1001]
      icon: 'mdi:solar-power'
    - name: "Phase A Current"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 1
      registers: [0x1002]
      icon: 'mdi:solar-power'
    - name: "Phase A Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x1003]
      icon: 'mdi:solar-power'
    - name: "Phase A Frequency"
      class: "power"
      state_class: "measurement"
      uom: "Hz"
      scale: 0.01
      rule: 1
      registers: [0x1005]
      icon: 'mdi:solar-power'

    - name: "Phase B Voltage"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1006]
      icon: 'mdi:solar-power'
    - name: "Phase B Current"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 1
      registers: [0x1007]
      icon: 'mdi:solar-power'
    - name: "Phase B Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x1008]
      icon: 'mdi:solar-power'
    - name: "Phase B Frequency"
      class: "power"
      state_class: "measurement"
      uom: "Hz"
      scale: 0.01
      rule: 1
      registers: [0x100A]
      icon: 'mdi:solar-power'

    - name: "Phase C Voltage"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x100B]
      icon: 'mdi:solar-power'
    - name: "Phase C Current"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 1
      registers: [0x100C]
      icon: 'mdi:solar-power'
    - name: "Phase C Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x100D]
      icon: 'mdi:solar-power'
    - name: "Phase C Frequency"
      class: "power"
      state_class: "measurement"
      uom: "Hz"
      scale: 0.01
      rule: 1
      registers: [0x100F]
      icon: 'mdi:solar-power'

    - name: "PV1 Voltage"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1010]
      icon: 'mdi:solar-power'
    - name: "PV1 Current"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 1
      registers: [0x1011]
      icon: 'mdi:solar-power'
    - name: "MPPT1 Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 3
      registers: [0x1012]
      icon: 'mdi:solar-power'

    - name: "PV2 Voltage"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1014]
      icon: 'mdi:solar-power'
    - name: "PV2 Current"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 1
      registers: [0x1015]
      icon: 'mdi:solar-power'
    - name: "MPPT2 Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 3
      registers: [0x1016]
      icon: 'mdi:solar-power'

    - name: "PV3 Voltage"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1018]
      icon: 'mdi:solar-power'
    - name: "PV3 Current"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 1
      registers: [0x1019]
      icon: 'mdi:solar-power'
    - name: "MPPT3 Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 3
      registers: [0x101A]
      icon: 'mdi:solar-power'

    - name: "Inner Temperature"
      class: "temperature"
      state_class: "measurement"
      uom: "C"
      scale: 1
      rule: 2
      registers: [0x101C]
      icon: 'mdi:solar-power'

    - name: "Total Energy"
      class: "energy"
      state_class: "measurement"
      uom: "kwh"
      scale: 1
      rule: 3
      registers: [0x1021]
      icon: 'mdi:solar-power'

    - name: "Total Generation Time"
      class: "time"
      state_class: "measurement"
      uom: "h"
      scale: 1
      rule: 3
      registers: [0x1023]
      icon: 'mdi:solar-power'

    - name: "Today Energy"
      class: "energy"
      state_class: "measurement"
      uom: "wh"
      scale: 1
      rule: 3
      registers: [0x1027]
      icon: 'mdi:solar-power'

    - name: "Active Power"
      class: "power"
      state_class: "measurement"
      uom: "Var"
      scale: 0.1
      rule: 4
      registers: [0x1037]
      icon: 'mdi:solar-power'

    - name: "Reactive Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x1039]
      icon: 'mdi:solar-power'

    - name: "Today Peak Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x103B]
      icon: 'mdi:solar-power'

    - name: "Power Factor"
      class: "time"
      state_class: "measurement"
      uom: ""
      scale: 0.001
      rule: 2
      registers: [0x103D]
      icon: 'mdi:solar-power'

    - name: "PV4 Voltage"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x103E]
      icon: 'mdi:solar-power'
    - name: "PV4 Current"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 1
      registers: [0x103F]
      icon: 'mdi:solar-power'
    - name: "MPPT4 Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 3
      registers: [0x1040]
      icon: 'mdi:solar-power'

    - name: "PV totally input power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 3
      registers: [0x1048]
      icon: 'mdi:solar-power'

# Decimals of total energy ( 0x104C )

    - name: "PV5 Voltage"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1080]
      icon: 'mdi:solar-power'
    - name: "PV5 Current"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 1
      registers: [0x1081]
      icon: 'mdi:solar-power'
    - name: "MPPT5 Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 3
      registers: [0x1082]
      icon: 'mdi:solar-power'

    - name: "PV6 Voltage"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1084]
      icon: 'mdi:solar-power'
    - name: "PV6 Current"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 1
      registers: [0x1085]
      icon: 'mdi:solar-power'
    - name: "MPPT6 Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 3
      registers: [0x1086]
      icon: 'mdi:solar-power'

    - name: "PV7 Voltage"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1088]
      icon: 'mdi:solar-power'
    - name: "PV7 Current"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 1
      registers: [0x1089]
      icon: 'mdi:solar-power'
    - name: "MPPT7 Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 3
      registers: [0x108A]
      icon: 'mdi:solar-power'

    - name: "PV8 Voltage"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x108C]
      icon: 'mdi:solar-power'
    - name: "PV8 Current"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 1
      registers: [0x108D]
      icon: 'mdi:solar-power'
    - name: "MPPT8 Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 3
      registers: [0x108E]
      icon: 'mdi:solar-power'

    - name: "PV9 Voltage"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1090]
      icon: 'mdi:solar-power'
    - name: "PV9 Current"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 1
      registers: [0x1091]
      icon: 'mdi:solar-power'
    - name: "MPPT9 Power"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 3
      registers: [0x1092]
      icon: 'mdi:solar-power'

    - name: "Phase R watt of grid"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x1300]
      icon: 'mdi:solar-power'
    - name: "Phase S watt of grid"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x1302]
      icon: 'mdi:solar-power'
    - name: "Phase T watt of grid"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x1304]
      icon: 'mdi:solar-power'

    - name: "Accumulated energy of positive"
      class: "energy"
      state_class: "measurement"
      uom: "Wh"
      scale: 10
      rule: 3
      registers: [0x1306]
      icon: 'mdi:solar-power'
    - name: "Accumulated energy of negative"
      class: "energy"
      state_class: "measurement"
      uom: "Wh"
      scale: 10
      rule: 3
      registers: [0x1308]
      icon: 'mdi:solar-power'

    - name: "Phase R watt of load"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x130A]
      icon: 'mdi:solar-power'
    - name: "Phase S watt of load"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x130C]
      icon: 'mdi:solar-power'
    - name: "Phase T watt of load"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x130E]
      icon: 'mdi:solar-power'

    - name: "Accumulated energy of load"
      class: "energy"
      state_class: "measurement"
      uom: "Wh"
      scale: 10
      rule: 3
      registers: [0x1310]
      icon: 'mdi:solar-power'

    - name: "L1-N phase voltage of grid"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x131A]
      icon: 'mdi:solar-power'
    - name: "L2-N phase voltage of grid"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x131B]
      icon: 'mdi:solar-power'
    - name: "L3-N phase voltage of grid"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x131C]
      icon: 'mdi:solar-power'

    - name: "L1 current of grid"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 4
      registers: [0x131D]
      icon: 'mdi:solar-power'
    - name: "L2 current of grid"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 4
      registers: [0x131F]
      icon: 'mdi:solar-power'
    - name: "L3 current of grid"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 4
      registers: [0x1321]
      icon: 'mdi:solar-power'

    - name: "L1-N phase voltage of load"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1323]
      icon: 'mdi:solar-power'
    - name: "L2-N phase voltage of load"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1324]
      icon: 'mdi:solar-power'
    - name: "L3-N phase voltage of load"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1325]
      icon: 'mdi:solar-power'

    - name: "L1 current of load"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 4
      registers: [0x1326]
      icon: 'mdi:solar-power'
    - name: "L2 current of load"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 4
      registers: [0x1328]
      icon: 'mdi:solar-power'
    - name: "L3 current of load"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 4
      registers: [0x132A]
      icon: 'mdi:solar-power'

    - name: "Total import Energy"
      class: "energy"
      state_class: "measurement"
      uom: "Wh"
      scale: 10
      rule: 3
      registers: [0x1332]
      icon: 'mdi:solar-power'
    - name: "Total export Energy"
      class: "energy"
      state_class: "measurement"
      uom: "Wh"
      scale: 10
      rule: 3
      registers: [0x1334]
      icon: 'mdi:solar-power'
    - name: "Total load Energy"
      class: "energy"
      state_class: "measurement"
      uom: "Wh"
      scale: 10
      rule: 3
      registers: [0x1336]
      icon: 'mdi:solar-power'

    - name: "Frequency of grid"
      class: "power"
      state_class: "measurement"
      uom: "Hz"
      scale: 0.01
      rule: 1
      registers: [0x1338]
      icon: 'mdi:solar-power'

    - name: "Phase R Voltage of EPS"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1350]
      icon: 'mdi:solar-power'
    - name: "Phase R current of EPS"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 4
      registers: [0x1351]
      icon: 'mdi:solar-power'
    - name: "Phase R watt of EPS"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x1353]
      icon: 'mdi:solar-power'

    - name: "Frequency of EPS"
      class: "power"
      state_class: "measurement"
      uom: "Hz"
      scale: 0.01
      rule: 1
      registers: [0x1355]
      icon: 'mdi:solar-power'

    - name: "Phase S Voltage of EPS"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x1356]
      icon: 'mdi:solar-power'
    - name: "Phase S current of EPS"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 4
      registers: [0x1357]
      icon: 'mdi:solar-power'
    - name: "Phase S watt of EPS"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x1359]
      icon: 'mdi:solar-power'

    - name: "Phase T Voltage of EPS"
      class: "voltage"
      state_class: "measurement"
      uom: "V"
      scale: 0.1
      rule: 1
      registers: [0x135B]
      icon: 'mdi:solar-power'
    - name: "Phase T current of EPS"
      class: "current"
      state_class: "measurement"
      uom: "A"
      scale: 0.01
      rule: 4
      registers: [0x135C]
      icon: 'mdi:solar-power'
    - name: "Phase T watt of EPS"
      class: "power"
      state_class: "measurement"
      uom: "W"
      scale: 0.1
      rule: 4
      registers: [0x135E]
      icon: 'mdi:solar-power'

    - name: "Daily energy to EPS"
      class: "energy"
      state_class: "measurement"
      uom: "Wh"
      scale: 10
      rule: 3
      registers: [0x1360]
      icon: 'mdi:solar-power'
    - name: "Accumulated energy to EPS"
      class: "energy"
      state_class: "measurement"
      uom: "Wh"
      scale: 10
      rule: 3
      registers: [0x1362]
      icon: 'mdi:solar-power'

# Battery SOC ... Battery acucmultaed discharge energy ... from 0x2000 to 0x2013

Now, it's pretty unclear to me HOW to integrate this to HA energy dashboard?
Some of those values are populated, others are always 0, but i am not knowledgeable enugh to understand what to do now?

Now, it's pretty unclear to me HOW to integrate this to HA energy dashboard?

Add the Total sensors to energy dashboard and it should work.

Device added to the list of Supported Devices

Beautiful!
Thanks!

Great work and congratulations for another supported device 👍

Is that a typo in your config file?
Frequencyr instead of Frequency?

Pretty sure its a typo ...

Since the file is going to be renamed anyway, maybe @davidrapan can directly fix it too

Yeah I already noticed that. 😉


Error when preprocess test dataset

When I use the command "python lib/core/data_preprocessor.py --cfg configs/kitti/3dssd/3dssd.yaml --split testing --img_list test", I got the following error.
AttributeError: 'KittiDataset' object has no attribute 'mixup_db_class'
With debugging, I found that mixup_db_class only will be activated by  ['train', 'val', 'trainval'] modes. So May I ask for how to fix this and what is the intension of using mixup_db_class?  Code reading is painful, please help out.

I have the same issue.

I have solved the problem to add
if self.img_list in ['train', 'val', 'trainval']:
before
mixup_label_dict = dict([(cls, []) for cls in self.mixup_db_class])


Front end documentation

Document all front end code. Add comments

Work split up :
Raji - User Service, Login, Movie Review, Navbar, Profile, TRM, E2E tests.
Manoj - Signup, Home, Movies Watched, Search Results, Unit tests.

Completed documentation for User Service, Login, Movie Review, Navbar, Profile, TRM, E2E tests.

Manoj, ETA on this, please?

Completed the documentation for Signup, Home, Movies Watched, Search Results.
Will close once review is done and merged onto /master

Documentation for Signup, Home, Movies Watched, Search Results done by Manoj.
Manoj is working on documenting unit tests.

Ready for review

Requested changes on review.

Done. Merged to master.


Homepage Demo Video

Story
No response
Description
For 1.0 Release, we are revamping the website (see https://github.com/flowforge/website/issues/184) to ensure clear messaging around what FlowForge is and offers as a product. As part of this, we need a 1-2 minute video demo'ing FlowForge and it's capabilities.

Open Questions for this video:

What do we demo?

Focus on FF already being installed (or demo'ing FF Managed)
Show how easy it is to setup a project and build/deploy a flow to a device

Thinking showing a device deployment is better as covers more functionality, but still shows the Project > Snapshot > Deploy pipeline

@joepavitt as discussed I think this would really benefit from Nick being on the video as a talking head.

Yep - agreed. @knolleary will assign to you, as we've discussed this too. @robmarcer can you share the draft story you recorded please?

Alternative Design. Think I prefer my original plan.

My plan was to start from the point of a user who is already signed up and a member of a team - so we can get to the 'create a node-red project easily' bit much quicker.

Login
Create project
Open Node-RED - create a simple flow that includes logging regularly to console.
In platform show other views of the project, include logs that should the flow console output
Register a device, download its credentials file, assign it to the project
In terminal - run device agent
In platform, create a snapshot, set as target
In terminal - show the flow console output

Need a good wrap up as well.

wrap up should be clear CTAs, something like:

"If you want to play with FlowForge for free, you can head to Github and install our open-source version. Alternatively, you can head to our own managed instance (linked in the description) and get started straight away."

I am cautious of showing off console/terminal for a platform that is meant to be low-code - can we keep this browser-constrained?

Target time of 2 mins (max)


Document the supported TLS versions in HTTPRequest

See #42857.

Thanks!

Cherry-picked for 3.2.4.


Is it possible to reuse a step's output for other two steps (avoid reruning the shared step)

For example,
@Step.register("share")
class Share(Step):
    CACHEABLE = False
    def run(self):
        ...

@Step.register("a")
class StepA(Step):
    def run(self, foo):
        ...

@Step.register("b")
class StepB(Step):
    def run(self, foo):
        ...

And the config file
steps: {
    share: {type: "share"},
    A: {type: "a", foo: {type:"ref", ref:"share"}},
    B: {type: "b", foo: {type:"ref", ref:"share"}},
}

Currently, it seems that both StepA and StepB will run the step Share. i.e. the step Share will be executed twice, once for A and once for B. Currently is it possible to just run step Share once and use the result for both StepA and StepB? I don't want to make step Share cacheable.

I just wonder if it is possible....
Just reply me with a "no" if it is not possible...

@Boltzmachine Currently, you have set CACHEABLE = False for Share step. If you set it to True, it will cache the output, and the step will be run only once.


Update doc on migrations

Add note about using different assemblies for the database and startup.

This information would've been very useful to our team if it was mentioned here, and would've saved us a lot of time and head scratching.

Thank you @niklasholm.


Hackaton100219

New features:

Checking presence of empty spaces at end of column names and column entry names - close #13
Check if all files exist when running petablint.py. Only if all files exist, the data format checking will be executed. TO DO: execute individual file checking.

Codecov Report

Merging #50 into master will decrease coverage by 0.85%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master      #50      +/-   ##
==========================================
- Coverage   65.98%   65.13%   -0.86%
==========================================
  Files           4        4
  Lines         391      413      +22
  Branches       75       83       +8
==========================================
+ Hits          258      269      +11
- Misses        124      135      +11
  Partials        9        9

Impacted Files
Coverage Δ

petab/core.py
73.72% <100%> (+0.29%)
:arrow_up:

petab/lint.py
46.66% <42.1%> (-0.75%)
:arrow_down:

Continue to review full report at Codecov.

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


Fix URL in README.md

Issue
https://gravitee.atlassian.net/browse/APIM-XXX
Description
Fix bad presentation of URL in README file.
Additional context

Thanks @mamayadi! 🚀

@gaetanmaisse You welcome


Adding --help-env, --help-xoptions and --help-all.

Introduced in 3.11 for describing the environment variables, the implementation options and the showing all information at the same time.

Rather than managing help messages manually, can we update it like the documents using rustpython-doc crate?

Not sure, we might add some additional xopts since those are implementation dependent (we also already add our own env variable in RUSTPYTHONPATH).
I think these are a one time thing so automating it might be too much (with docs, it was the whole stdlib that constantly might get updated so the rustpython-doc crate made a lot of sense to create).

but I don't think this is such a good first issue anymore, I'll try and re-structure the cli argument parsing to make it easier to generate these.