Q: how to generate a/index.html ?

I have:
.
`-- src
    |-- a
    |   `-- index.html
    |-- b
    |   `-- index.html
    `-- index.html

I would like to produce:
.
`-- out
    |-- a
    |   `-- index.html
    |-- b
    |   `-- index.html
    `-- index.html

so that /a/ and /b/ will be valid URLs. Right now, Ivy wants to generate:
.
`-- src
    |-- a.html
    |-- b.html
    `-- index.html

Is there a way to force the desired behavior (so that old URLs won't break)?

Hi Greg. Ivy does indeed have a very-lightly documented option for generating directory-style URLs. If you add
extension = "/"

to your config.py file, that should do the trick.

Thank you - that's worked. On a similar note, is there a way to prevent generation of an index.html file for a node entirely? For example, if I have:
src
|-- advice
|   |-- findability.html
|   `-- safety.html
|-- bibliography.html
|-- index.html
`-- project.html

and I don't want either advice.html or advice/index.html in the output, can I achieve that? If I don't have src/advice/index.html, I get the error message:
Error: Ivy cannot locate a template file for the node: '@root/advice//'.

There's a build_node filter here that you can use as a switch to decide if a node should be written to disk.
You could write a little extension that checks the node's metadata for some kind of disable flag, e.g.
@ivy.filters.register('build_node')
def build_filter(enable_build: bool, node: Node):
    if node.get('disable'):
        return False
    return True

I have no idea where the template error is coming from though, Ivy should be perfectly happy with a node directory with no index file inside it.

I've actually gone ahead and added support for a disable flag directly to Ivy in version 6.1.0 as I think it's a generally useful feature.

thanks - I'll see if I can figure out why not having an index.whatever file in a directory is causing conniptions.

Definitely let me know if you can track that issue down any further!

I think we figured this one out :)
The template error was happening because Ivy always looks in the last resort for a template file called node.*. Your theme didn't have a template with this name.


Nuget Package update

Hi there. I really love this library.
I'm using the 1.1.0 Nuget Package version and it doesn't seem to include the Interface for DocumentDbRepository yet. Any plans to update the Nuget package? Thanks a lot!

Hi @neil445,
Glad you love it :) Package updated to 1.2.0.

Hi Crokus, isn't time to update the nuget package? I sound like I'm asking too much now. haha.
Thanks.


Add swedish translation

Solves #11

Will fix during the day

I have now changed to name of the file. Amended my commit to keep the history clean.

Still looking for someone to review this. This will most likely get merged sooner or later. 👍

Thanks!


Entity system rewrite required

The Entity system in UMod needs to be re-wrote in order to allow Lua to connect to the UModCharacter and to EntityBase/WeaponBase.

I'm advancing on that. Now Entities can be created and you can set model for the first time through Lua (you couldn't do that without that rewrite). And normaly UModCharacter can be passed to Lua as an Entity* however, that is not finished, I'm still searching a viable and fast way to cast from any compatible AActor* to Entity*.

The preprocessor allowed me to accomplish that !


ConfigureRhd2164.Rhd2164AmplifierDataFormat should be removed

I'm questing the utility of exposing the chip setting that allows the user the select offset binary or twos-complement representations of RHD2164 data:
https://github.com/neurogears/onix-refactor/blob/f42fb50cfc9d845e806eecc74564b9b79c453418/OpenEphys.Onix/OpenEphys.Onix/ConfigureRhd2164.cs#L19
Reasons against this:

NPX data is represented as offset binary and this has motivated the default format for all spike sorters
The user typically does not care about this distinction. If they do, the care about some integer sample representation for efficient saving versus a floating point representation in SI units. This distinction is properly captured in the AnalogInput way of doing things. where the AnalogInput data streaming node can either passthrough ushorts or perform a conversion to represent samples as voltages.

In fact, this is a bug -- Rhd2164Data assums offset binary.
https://github.com/neurogears/onix-refactor/blob/f42fb50cfc9d845e806eecc74564b9b79c453418/OpenEphys.Onix/OpenEphys.Onix/Rhd2164Data.cs#L44

Addressed in #151


Fix sqlserver accept issue.

Direct casting visitor to SQLServerASTVisitor may throw 'cannot cast exception', we need to first determine whether it can be cast and then cast.

Codecov Report
Attention: Patch coverage is 52.38095% with 10 lines in your changes missing coverage. Please review.

Project coverage is 59.03%. Comparing base (ec01eae) to head (c07f756).
Report is 62 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #6058      +/-   ##
============================================
- Coverage     59.04%   59.03%   -0.01%
- Complexity    28413    28534     +121
============================================
  Files          1354     1375      +21
  Lines        129742   130332     +590
  Branches      24471    24346     -125
============================================
+ Hits          76600    76947     +347
- Misses        43568    43637      +69
- Partials       9574     9748     +174

Files
Coverage Δ

...sql/dialect/sqlserver/ast/SQLServerObjectImpl.java
100.00% <ø> (ø)

...sqlserver/ast/stmt/SQLServerRollbackStatement.java
92.30% <ø> (+6.59%)
:arrow_up:

...uid/sql/dialect/sqlserver/ast/SQLServerOutput.java
38.70% <66.66%> (+2.99%)
:arrow_up:

.../dialect/sqlserver/ast/SQLServerStatementImpl.java
80.00% <50.00%> (-20.00%)
:arrow_down:

.../druid/sql/dialect/sqlserver/ast/SQLServerTop.java
61.11% <66.66%> (+4.44%)
:arrow_up:

...lserver/ast/expr/SQLServerObjectReferenceExpr.java
21.21% <66.66%> (-2.60%)
:arrow_down:

...ect/sqlserver/ast/stmt/SQLServerExecStatement.java
68.96% <66.66%> (-7.96%)
:arrow_down:

...t/sqlserver/ast/stmt/SQLServerInsertStatement.java
67.64% <50.00%> (-2.05%)
:arrow_down:

...t/sqlserver/ast/stmt/SQLServerUpdateStatement.java
87.50% <50.00%> (-3.81%)
:arrow_down:

...uid/sql/dialect/sqlserver/ast/SQLServerObject.java
0.00% <0.00%> (ø)

... and 105 files with indirect coverage changes

Continue to review full report in Codecov by Sentry.

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


[bug] "Generate builder" and "Run sigstore/cosign-installer" steps failing with error updating to TUF remote mirror: invalid key

The "Generate builder" and "Run sigstore/cosign-installer" steps have started failing for my workflows.  This used to work fine, not sure if it is just an intermittent error or something more fundamental:
Here's a build that worked 18 hours ago but is failing now (i.e. without any code changes): https://github.com/jkreileder/cf-ips-to-hcloud-fw/actions/runs/8339143012 (corresponding workflow)

Generate builder error:

Verifying artifact slsa-generator-container-linux-amd64: FAILED: error retrieving Rekor public keys: updating local metadata and targets: error updating to TUF remote mirror: invalid key
remote status:{
	"mirror": "https://tuf-repo-cdn.sigstore.dev/",
	"metadata": {
		"root.json": {
			"version": 9,
			"len": 6766,
			"expiration": "12 Sep 24 06:53 UTC",
			"error": ""
		},
		"snapshot.json": {
			"version": 132,
			"len": 2302,
			"expiration": "09 Apr 24 16:16 UTC",
			"error": ""
		},
		"targets.json": {
			"version": 9,
			"len": 5478,
			"expiration": "12 Sep 24 06:13 UTC",
			"error": ""
		},
		"timestamp.json": {
			"version": 169,
			"len": 723,
			"expiration": "26 Mar 24 16:16 UTC",
			"error": ""
		}
	}
}

FAILED: SLSA verification failed: error retrieving Rekor public keys: updating local metadata and targets: error updating to TUF remote mirror: invalid key
remote status:{
	"mirror": "https://tuf-repo-cdn.sigstore.dev/",
	"metadata": {
		"root.json": {
			"version": 9,
			"len": 6766,
			"expiration": "12 Sep 24 06:53 UTC",
			"error": ""
		},
		"snapshot.json": {
			"version": 132,
			"len": 2302,
			"expiration": "09 Apr 24 16:16 UTC",
			"error": ""
		},
		"targets.json": {
			"version": 9,
			"len": 5478,
			"expiration": "12 Sep 24 06:13 UTC",
			"error": ""
		},
		"timestamp.json": {
			"version": 169,
			"len": 723,
			"expiration": "26 Mar 24 16:16 UTC",
			"error": ""
		}
	}
}
Error: Process completed with exit code 6.

Run sigstore/cosign-installer@6e04d228eb30da1757ee4e1dd75a0ec73a653e06 error:

Error: getting ctlog public keys: updating local metadata and targets: error updating to TUF remote mirror: invalid key
remote status:{
	"mirror": "https://tuf-repo-cdn.sigstore.dev/",
	"metadata": {
		"root.json": {
			"version": 9,
			"len": 6766,
			"expiration": "12 Sep 24 06:53 UTC",
			"error": ""
		},
		"snapshot.json": {
			"version": 132,
			"len": 2302,
			"expiration": "09 Apr 24 16:16 UTC",
			"error": ""
		},
		"targets.json": {
			"version": 9,
			"len": 5478,
			"expiration": "12 Sep 24 06:13 UTC",
			"error": ""
		},
		"timestamp.json": {
			"version": 169,
			"len": 723,
			"expiration": "26 Mar 24 16:16 UTC",
			"error": ""
		}
	}
}
main.go:74: error during command execution: getting ctlog public keys: updating local metadata and targets: error updating to TUF remote mirror: invalid key
remote status:{
	"mirror": "https://tuf-repo-cdn.sigstore.dev/",
	"metadata": {
		"root.json": {
			"version": 9,
			"len": 6766,
			"expiration": "12 Sep 24 06:53 UTC",
			"error": ""
		},
		"snapshot.json": {
			"version": 132,
			"len": 2302,
			"expiration": "09 Apr 24 16:16 UTC",
			"error": ""
		},
		"targets.json": {
			"version": 9,
			"len": 5478,
			"expiration": "12 Sep 24 06:13 UTC",
			"error": ""
		},
		"timestamp.json": {
			"version": 169,
			"len": 723,
			"expiration": "26 Mar 24 16:16 UTC",
			"error": ""
		}
	}
}
Error: Process completed with exit code 1.

Started seeing the same just now.

+1 Seeing this across all our builds in the last 2 hours... this is holding up our release candidate...

‼ @ianlewis @laurentsimon please advise! This is breaking all our build pipelines, and talking with folks their pipelines are also dead in the water ‼

@laurentsimon @ianlewis You just need to bump Cosign to at least v2.2.0, latest is v2.2.3.

@haydentherapper Cosign in SLSA Verifier needs to be updated to the latest version as well.

haydentherapper Cosign in SLSA Verifier needs to be updated to the latest version as well.

According to the announcement, v2.2.0 should support a new TUF Trust root.

I see. The version of slsa-verifier used by the latest slsa-github-generator is old.
https://github.com/slsa-framework/slsa-github-generator/blob/07e64b653f10a80b6510f4568f685f8b7b9ea830/.github/actions/generate-builder/action.yml#L95
https://github.com/slsa-framework/slsa-verifier/blob/c9abffe4d2ab2ffa0b2ea9b2582b84164f390adc/go.mod#L21

@laurentsimon @ianlewis
I'm sorry to bother you, but could you release a new version of slsa-github-generator to solve this issue?

Hi, yes let's do that. I think we need to revert a few breaking PRs we made recently in the slsa-github-generator. slsa-verifier should be ready to be released. @ramonpetgrave64 could you send PRs to temporarily revert the few breaking PRs we made recently?

Note: slsa-verifier's latest version uses cosign 2.2.0 https://github.com/slsa-framework/slsa-verifier/blob/v2.4.1/go.mod so need not be updated.

I see this is closed, but v1.9.0 is marked as the latest release... in the release notes update, it says:

error updating to TUF remote mirror: invalid
This will occur only when generating provenance with all builders and generators.
Affected versions: all versions up and including v1.9.0

Can this bug be reopened until a release occurs? Or is there a way to work around this, or can we use the generator at main?

Generator at main won't pass verification. We need to cut the release. @kpk47 is working on it

Thank you @laurentsimon for being so responsive on this issue; I understand the commit auto-closed the bug. It's helpful to have something to follow. Good luck and thank you for your hard work securing software supply chains.

Release is available v1.10.0 https://github.com/slsa-framework/slsa-github-generator/releases/tag/v1.10.0

I upgraded to v1.10.0 and that fixed generation of new provenance files, but I'm wondering: Is there a way to make old versions of slsa-verifier still work? From what I can tell, this change appears to make all old provenances unverifiable which seems like a significant problem.

@ddworken We have faced the same issue. This is a really good point.
@haydentherapper @bobcallaway What is the Sigstore/Cosign solution for revoked root keys and in general how does Sigstore provide backward compatibility with old versions of certificates, and therefore verifying existing legitimate provenances that were signed with revoked keys?

The latest version of slsa-verifier is still is able to verify old provenances.

Hmm, it appears as though this isn't the case. My project uses SLSA for releases and secure updates. I have daily tests running on Github Actions and it went from passing to failing in line with this bug:

You can see the test failure here. I also confirmed that this appears to apply to the main slsa-verifier binary, so you can reproduce this yourself by:
# From inside of the slsa-verifier git repo
# Check out the old version of slsa-verifier
git checkout v1.3.2
# Download a file and an old attestation
wget https://github.com/ddworken/hishtory/releases/download/v0.277/hishtory-linux-amd64
wget https://github.com/ddworken/hishtory/releases/download/v0.277/hishtory-linux-amd64.intoto.jsonl
# Run slsa-verifier
go run ./cli/slsa-verifier -artifact-path hishtory-linux-amd64 -provenance hishtory-linux-amd64.intoto.jsonl -source github.com/ddworken/hishtory

This fails with the output:

slsa-verifier output
Getting rekor entry error error verifying tlog entry: updating local metadata and targets: error updating to TUF remote mirror: invalid key
remote status:{
	"mirror": "https://sigstore-tuf-root.storage.googleapis.com",
	"metadata": {
		"root.json": {
			"version": 9,
			"len": 6766,
			"expiration": "12 Sep 24 06:53 UTC",
			"error": ""
		},
		"snapshot.json": {
			"version": 132,
			"len": 2302,
			"expiration": "09 Apr 24 16:16 UTC",
			"error": ""
		},
		"targets.json": {
			"version": 9,
			"len": 5478,
			"expiration": "12 Sep 24 06:13 UTC",
			"error": ""
		},
		"timestamp.json": {
			"version": 170,
			"len": 721,
			"expiration": "29 Mar 24 16:08 UTC",
			"error": ""
		}
	}
}: unable to fetch Rekor public keys from TUF repository, trying Redis search index to find entries by subject digest
FAILED: SLSA verification failed: could not find a matching valid signature entry: got unexpected errors updating local metadata and targets: error updating to TUF remote mirror: invalid key
remote status:{
	"mirror": "https://sigstore-tuf-root.storage.googleapis.com",
	"metadata": {
		"root.json": {
			"version": 9,
			"len": 6766,
			"expiration": "12 Sep 24 06:53 UTC",
			"error": ""
		},
		"snapshot.json": {
			"version": 132,
			"len": 2302,
			"expiration": "09 Apr 24 16:16 UTC",
			"error": ""
		},
		"targets.json": {
			"version": 9,
			"len": 5478,
			"expiration": "12 Sep 24 06:13 UTC",
			"error": ""
		},
		"timestamp.json": {
			"version": 170,
			"len": 721,
			"expiration": "29 Mar 24 16:08 UTC",
			"error": ""
		}
	}
}: unable to fetch Rekor public keys from TUF repository: verifying tlog entry 24296fb24b8ad77a614df024f5e997739525746b275409b28df6a6b7285c7128f4f8e429a5cb1e42, updating local metadata and targets: error updating to TUF remote mirror: invalid key
remote status:{
	"mirror": "https://sigstore-tuf-root.storage.googleapis.com",
	"metadata": {
		"root.json": {
			"version": 9,
			"len": 6766,
			"expiration": "12 Sep 24 06:53 UTC",
			"error": ""
		},
		"snapshot.json": {
			"version": 132,
			"len": 2302,
			"expiration": "09 Apr 24 16:16 UTC",
			"error": ""
		},
		"targets.json": {
			"version": 9,
			"len": 5478,
			"expiration": "12 Sep 24 06:13 UTC",
			"error": ""
		},
		"timestamp.json": {
			"version": 170,
			"len": 721,
			"expiration": "29 Mar 24 16:08 UTC",
			"error": ""
		}
	}
}: unable to fetch Rekor public keys from TUF repository: verifying tlog entry 24296fb24b8ad77af7d9a9a7dbb2e7c25c5d46e41770969259f3d72fd20f0016bd5b1a54229bcbba
exit status 2

So it seems to me that slsa-verifier is now failing to verify attestations that used to pass.

Why do you need to use an old version of slsa-verifier?

This is because my project embeds slsa-verifier in order to provide secure updates.

Probably unrelated to this issue but what is the Sigstore/Cosign solution for revoked root keys and in general how does Sigstore provide backward compatibility with old versions of certificates, and therefore verifying existing legitimate provenances that were signed with revoked keys?

@behnazh-w Supporting validity windows was the motivation behind the design of the trust root spec. For each root of trust, a validity time period is specified. If a compromise were to occur, rather than revoking the root material entirely and assuming we can determine the window when compromise occurred, the root material would simply be specified as valid only up to the compromise.
All clients but Cosign support ingesting the roots of trust in this format currently. Cosign will be updated to read it soon.

So it seems to me that slsa-verifier is now failing to verify attestations that used to pass. It is true that the latest version of slsa-verifier is able to verify old attestations, but this doesn't seem to help anyone who is stuck with an old version of slsa-verifier.

You're correct. The TUF root updates need an update of slsa-verifier to v2.4.1. We could backport the fixes, but it would still require you to update your slsa-verifier version.

Got it, thanks for confirming! I'm wondering: Is this class of breakage something you expect to continue to need to happen with slsa-verifier? If so, it seems like this may be an important caveat to document (maybe under the "Known Isssues" heading) since having a previously working verifier continue to work seems like a reasonable expectation.

We don't expect this to happen. @haydentherapper can comment on the specifics of cosign.


Default battery Vcut = 0 while Feature Unreleased

The newest PySAM has features from patch and develop, including the battery's voltage cutoff. If Vcut = 0, then the old battery behavior is reproduced and this is what the current SAM GUI does. However, the Vcut default is not 0 given the new defaults, and so in PySAM, these non-zero Vcuts will produce results that are different from SAM. This has effects on the battery system variables during dispatch, and in some tests have shown large power differences for certain timesteps.
While this Vcut feature is still unreleased,  cmod_battery and cmod_batterystateful should set Vcut to 0 if it's not provided (as in the case of a case being exported from the current SAM release, which doesn't contain Vcut) so that the behavior is the same as in the released SAM.
Need to update PySAM v2.2.1

Closing because cmod_battery already has Vcut = 0 as a default when the value is not provided. BatteryStateful is not accessible from SAM so there isn't the consideration of results needing to match.


Fix container exec

Closes https://github.com/Azure/azure-cli/issues/5926

View a preview at https://prompt.ws/r/Azure/azure-cli/5927
This is an experimental preview for @microsoft users.

Would like @samkreter to review before merging.


epic: Complete InCluster Networking

TL;DR
Extend the limited In Cluster Network support provided in PR kcp-dev/kcp#1708, in order to add:

Support for Syncing from multiple User Workspaces from given Syncer
NetworkPolicy-based protection of the accesses to the CoreDNS services installed for each user orkspace

Progress tracking #
EPIC detailed issues and overall progress can be tracked with the following project view
Work Items

[x] kcp-dev/kcp#1987
[x] kcp-dev/kcp#1988
[ ] kcp-dev/contrib-tmc#80
[ ] kcp-dev/kcp#1531

@davidfestal @sttts I was having a look through the codebase to get an understanding of how #1531 might be solved by creating a NetworkPolicy in each namespace. One that would "lock down by default between workspaces, but allow namespace comm for the same workspace"
Some related discusssion in slack here https://kubernetes.slack.com/archives/C021U8WSAFK/p1667469578560679
A few thoughts:

Is there a precedence in the code where some resource(s) are created in each namespace? I can see a kcp-default-token secret and kcp-root-ca.crt configmap whos name gets transformed when syncing, which leads to another question
Would the NetworkPolicy be created by kcp in the upstream namespace, and synced to the downstream namespace(s), with transforms to ensure appropriate restrictions? Or would the NetworkPolicy be a 'special case' like Namespaces where they aren't synced, but instead created and managed in the downstream namespace(s) only?

My instinct is to create a default NetworkPolicy in every namespace that gets transformed when synced downstream.

@davidfestal @sttts I was having a look through the codebase to get an understanding of how #1531 might be solved by creating a NetworkPolicy in each namespace. One that would "lock down by default between workspaces, but allow namespace comm for the same workspace"
Some related discusssion in slack here https://kubernetes.slack.com/archives/C021U8WSAFK/p1667469578560679
A few thoughts:

Is there a precedence in the code where some resource(s) are created in each namespace? I can see a kcp-default-token secret and kcp-root-ca.crt configmap whos name gets transformed when syncing, which leads to another question
Would the NetworkPolicy be created by kcp in the upstream namespace, and synced to the downstream namespace(s), with transforms to ensure appropriate restrictions? Or would the NetworkPolicy be a 'special case' like Namespaces where they aren't synced, but instead created and managed in the downstream namespace(s) only?

My instinct is to create a default NetworkPolicy in every namespace that gets transformed when synced downstream.

Here is the current take on this (still need to formalize it in an issue / EPIC):

short term:

The syncer would create namespaced NetworkPolicies to ensure a strong network isolation of namespaces originating from different KCP workspaces (no syncing required here, since the policies restrict all traffix between those namespaces
User-provided NetworkPolicies (provided in KCP and synced to physical cluster namespaces) are NOT supported (merging both is not realistic, after thinking about it and trying to do so)

mid/long term:

Use Admin Network Policies to isolation of namespaces originating from different KCP workspaces
Allow namespaced NetworkPolicies to be defined at the KCP level, and synced + transformed by the Syncer to enforce communication rules between namespaces inside the KCP workspace boundaries

We did not contemplate enabling the use-case when communications would be allowed between namespaces of  originating from different KCP workspaces

/transfer-issue contrib-tmc


Navigating table columns with up/down arrow key skips random columns

System information:

Ubuntu Linux 21.04
Version <IP_ADDRESS>106012023
uuid-ossp; plpgsql;

Connection specification:

PostgreSQL 12
Postgres
Local database

Describe the problem you're observing:
Navigating table columns with up/down arrow key skips random columns.
I could not discover a pattern in the "jumps", neither types nor length name.
Jumps are stable.
Steps to reproduce, if exist:

Create a table with reasonable amount of columns with various names/types.
Open ER Diagram of table.
Select random column with mouse click.
Traverse up and down through column names with arrow keys.

Thank you for the report. This is reproduceble, so we will see if anything can be done.

Verified


slightly improved some parser error messages

This changes a very confusing error message reported by Kristian in issue 732 to a slightly less bad one...

Nice @sydow! :D


Button and LED mapping not included in .json file for KW24D

Working thought the example with the KW24D, I am able to get the device to connect to an IP address, but I have no way of verifying that communication is made between multiple devices, as mbed_app.json does not have the buttons/LEDs mapped yet.

Thanks for catching this issue.  Try adding this to the target_overrides section of mbed_app.json.  It should work.  Make sure this is set to true also "enable-led-control-example": true,
    "KW24D": {
        "LED": "LED1",
        "BUTTON": "SW1"
    }

If that works, you can make a pull request to add it.
I just made a similar pull request for another platform.
https://github.com/ARMmbed/mbed-os-example-mesh-minimal/pull/99

Thanks Mac.  I added that code to mbed_app.json, and successfully communicated between KW24D in thread mode.  I will make a pull request now to add those changes.

Merged in.
Thanks for providing the pin-names and testing this.


Minor format, grammar and typographic changes

Nothing too important.

I corrected one of these issues in 8d5d71310792eec3cf4a83e321e90320538f69c3.
The README.md is generated from the POD6 in lib/IO/Glob.pm6, so I made the changes there rather than applying your PR.
I have no opinion as to whether the addition of the "of" preposition makes the abstract more readable or not.
Cheers.

OK, fair enough. Your module, your rules. :+1:


Update spacy dependency from 1.7 to 1.8

Need to investigate the change log to see what is different (https://github.com/explosion/spaCy/releases/).
update NER fine tuning (there is some new docs on that: https://spacy.io/docs/usage/training-ner)

waiting for explosion/spaCy#999

The fix was pushed it seems https://github.com/explosion/spaCy/commit/d2436dc17be25b0f3ad220212c542e66c44bb512. Let me know if I could be of any help.

After updating to 1.8.1, when I launch the command :
python -m rasa_nlu.server -c config_spacy.json --server_model_dirs=./model_YYYYMMDD-HHMMSS
I'm still getting this error :
ERROR:root:Failed to load model './model_20170426-104959'. Error: 1 Traceback (most recent call last):   File "rasa_nlu/data_router.py", line 84, in __create_model_store     interpreter = Interpreter.load(metadata, self.config, self.component_builder)   File "rasa_nlu/model.py", line 245, in load     component = component_builder.load_component(component_name, context, model_config, meta)   File "rasa_nlu/components.py", line 234, in load_component     component = registry.load_component_by_name(component_name, context, model_config)   File "rasa_nlu/registry.py", line 89, in load_component_by_name     return load_component(component_clz, context, config)   File "rasa_nlu/components.py", line 27, in load_component     return component_clz.load(*load_args)   File "rasa_nlu/extractors/spacy_entity_extractor.py", line 103, in load     ner = EntityRecognizer.load(pathlib.Path(ner_dir), spacy_nlp.vocab)   File "spacy/syntax/parser.pyx", line 154, in spacy.syntax.parser.Parser.load (spacy/syntax/parser.cpp:6999)     self = cls(vocab, TransitionSystem=TransitionSystem, model=None, **cfg)   File "spacy/syntax/parser.pyx", line 177, in spacy.syntax.parser.Parser.__init__ (spacy/syntax/parser.cpp:7370)     cfg['actions'] = TransitionSystem.get_actions(**cfg)   File "spacy/syntax/ner.pyx", line 71, in spacy.syntax.ner.BiluoPushDown.get_actions (spacy/syntax/ner.cpp:3906)     actions[action].append(entity_type) KeyError: 1 INFO:root:Started http server on port 5000

I've updated the spacy dependency to 1.8.2 in the requirements. Nevertheless, it is still possible to use 1.7 (since we removed the NER training there is no issue with the changes from 1.7 to 1.8 anymore).


Visual script node ' set_albedo ' doesn't work . .

Godot version
Godot 4.0 . .
System information
Windows 10 . .
Issue description
Just a quick bug ??
In Godot 3.4, this works . . .

It changes an albedo, on a simple mesh . . . In Godot 4, this causes an error . . .

I tried connecting both ports, from the 'get_material', either way, an error, something about 'index' . .
So, I'm not sure, does this make sense . . I guess, should one start reporting bugs now, I've been reporting a ton, and, feel a bit tired, and, want to take a break, and, perhaps only report when Godot 4 is near, to RC, just, very tired, though, the engine rocks, of thinking of new things, and, making 'noob' suggestions, I know now most of them were not that useful, in the sense, engine pros, coders knew better, wanted to say thanks, for help / explanations . . :'-)) . .
Not sure, do you want reports for visual script atm, I've been wondering if the system might be under review, or, big re-factor, and, these things are right now just supposed to be there . .
Anyway, hoping for some advice, 1. when do you want to start getting bug reports for Godot 4, not even sure it's a bug, there's an error, etc . . . 2. Is it not required atm, because of some big coding changes, and, 3. How many bug reports do you want / ie., how much will you find yourself, sort-of, how important is it that the Godot community does this, not sure, do you know about these bugs, I guess, those are some questions, so I know when to report bugs, and, how much :-)) . .
Thanks, engine is getting good, Godot 4 is good improvement, over-all it's 9 / 10 +, however, now some things that worked in Godot 3, stopped working, etc . .
Steps to reproduce
The above code doesn't work, in Godot 4, not sure it's a bug . .
Anyway, looking forward to see what happens in visual script, also, bec. I have used visual shaders, and, it has helped me learn how coding systems work / make demos/prototypes, :-OO . . . 10 / 10 feature, for beginners, learning, and, making something fast, hope you could make it better, in a cool way . . . .
Minimal reproduction project
No response

You're trying to get a material from a box that doesn't exist, as you're trying to ask for a null instance of BoxMesh to pass its Material.
Also, you should pass the material and not the box instance (which is currently null) to set the albedo property.

Uhhh, well, I just got the ' get_material ', from the inspector, and, tried to connect it, it worked in Godot 3, and, still does . .
The ' set_albedo ' is also just from the inspector . .
Ok, made it work . .

Also had to use the ' get_mesh ', and, add that to the ' get_material ' . .
It's an amazing system, wow, is it complex, 10.2 / 10 . . :-)) . .

Closing, as this isn't a bug.


updated README and removed things

@cantbewong see updates for paths here

Also removed files that aren't needed


Fix warnings from Clippy

Recently released Rust 1.51 includes new Clippy with new warnings:
error: name `GetPublicKeyForID` contains a capitalized acronym
   --> src/wrappers/themis/rust/tests/secure_session.rs:663:6
    |
663 | type GetPublicKeyForID = Box<dyn FnMut(&[u8]) -> Option<EcdsaPublicKey>>;
    |      ^^^^^^^^^^^^^^^^^ help: consider making the acronym lowercase, except the initial letter: `GetPublicKeyForId`
    |
    = note: `-D clippy::upper-case-acronyms` implied by `-D warnings`
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#upper_case_acronyms

error: aborting due to previous error

Shut up, Clippy, I name my types however I want to!
I mean, yes, sure, O Wise Stationery, I will immediately rename the entity as prescribed and will refrain from such practice any further.
Checklist

[X] Change is covered by automated tests
[X] The coding guidelines are followed

@ilammy can you please cherry pick there changes to stable?

@vixentael,

@ilammy can you please cherry pick there changes to stable?

Done: #794


Documenting --requirements-file precedence and requirements.txt

Closes https://github.com/arkq/flake8-requirements/issues/80

Please bump patch version here as well: https://github.com/arkq/flake8-requirements/blob/master/src/flake8_requirements/checker.py#L23  I will make a new release.

@arkq done, thanks!


Dev

Update into main from dev to release rc from main right after.

Do not merge until the pending notion issue is fixed and confirmed 🙌🏼


Data sync is not happening between nodes deployed on different machines

I have boot node and node 1 deployed on one machine as block maker and voter and relevant invoking tm2.conf file looks like -

url = "http://<IP_ADDRESS>:9000/"
port = 9000
socketPath = "qdata/tm2.ipc"
otherNodeUrls = []
publicKeyPath = "keys/tm2.pub"
privateKeyPath = "keys/tm2.key"
archivalPublicKeyPath = "keys/tm2a.pub"
archivalPrivateKeyPath = "keys/tm2a.key"
storagePath = "qdata/constellation2"

and node3 deployed on another machine which is ONLY voter and uses tm5.conf which config looks like -
url = "http://<IP_ADDRESS>:9000/"
port = 9000
socketPath = "qdata/tm5.ipc"
otherNodeUrls = ["http://<IP_ADDRESS>:9000/"]
publicKeyPath = "keys/tm5.pub"
privateKeyPath = "keys/tm5.key"
archivalPublicKeyPath = "keys/tm5a.pub"
archivalPrivateKeyPath = "keys/tm5a.key"
storagePath = "qdata/constellation5"

both the nodes constellations logs show no errors. In the  constellation log for node 1 the log is displayed as -

nohup: appending output to 'nohup.out'
2017 Sep-03 05:24:32216663 [INFO] Constellation initializing using config file tm2.conf
2017 Sep-03 05:24:32217548 [INFO] Log level is LevelDebug
2017 Sep-03 05:24:32217620 [INFO] Utilizing 2 core(s)
2017 Sep-03 05:24:32220587 [INFO] Constructing Enclave using keypairs (keys/tm2.pub, keys/tm2.key) (keys/tm2a.pub, keys/tm2a.key)
2017 Sep-03 05:24:32220802 [INFO] Initializing storage qdata/constellation2
2017 Sep-03 05:24:32276282 [INFO] Internal API listening on qdata/tm2.ipc
2017 Sep-03 05:24:32276271 [INFO] External API listening on port 9000
2017 Sep-03 05:24:32276219 [INFO] Node started
2017 Sep-03 05:24:38344272 [DEBUG] Request from : ApiUpcheck; Response: ApiUpcheckR
2017 Sep-03 05:25:09751069 [DEBUG] Request from <IP_ADDRESS>:49940: ApiPartyInfo (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]}); Response: ApiPartyInfoR (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]})
2017 Sep-03 05:29:35051830 [DEBUG] Request from <IP_ADDRESS>:48254: ApiPartyInfo (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]}); Response: ApiPartyInfoR (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]})
2017 Sep-03 05:30:09760130 [DEBUG] Request from <IP_ADDRESS>:50490: ApiPartyInfo (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]}); Response: ApiPartyInfoR (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]})
2017 Sep-03 05:34:37725427 [DEBUG] Request from <IP_ADDRESS>:49104: ApiPartyInfo (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]}); Response: ApiPartyInfoR (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]})
2017 Sep-03 05:35:09798877 [DEBUG] Request from <IP_ADDRESS>:51044: ApiPartyInfo (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]}); Response: ApiPartyInfoR (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]})
2017 Sep-03 05:39:40398721 [DEBUG] Request from <IP_ADDRESS>:49964: ApiPartyInfo (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]}); Response: ApiPartyInfoR (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]})
2017 Sep-03 05:40:09837242 [DEBUG] Request from <IP_ADDRESS>:51600: ApiPartyInfo (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]}); Response: ApiPartyInfoR (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]})
2017 Sep-03 05:44:42984722 [DEBUG] Request from <IP_ADDRESS>:50820: ApiPartyInfo (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]}); Response: ApiPartyInfoR (PartyInfo {piUrl = "http://<IP_ADDRESS>:9000/", piRcpts = fromList [("QfeDAys9MPDs2XHExtc84jKGHxZg/aj52DTh0vtA3Xc=","http://<IP_ADDRESS>:9000/"),("R56gy4dn24YOjwyesTczYa8m5xhP6hF2uTMCju/1xkY=","http://<IP_ADDRESS>:9000/")], piParties = fromList ["http://<IP_ADDRESS>:9000/"]})

and node 3 constellation log shown as -
nohup: appending output to 'nohup.out'
2017 Sep-03 05:25:09524816 [INFO] Constellation initializing using config file tm5.conf
2017 Sep-03 05:25:09528401 [INFO] Log level is LevelDebug
2017 Sep-03 05:25:09528491 [INFO] Utilizing 2 core(s)
2017 Sep-03 05:25:09528924 [INFO] Constructing Enclave using keypairs (keys/tm5.pub, keys/tm5.key) (keys/tm5a.pub, keys/tm5a.key)
2017 Sep-03 05:25:09529209 [INFO] Initializing storage qdata/constellation5
2017 Sep-03 05:25:09606851 [INFO] External API listening on port 9000
2017 Sep-03 05:25:09606862 [INFO] Internal API listening on qdata/tm5.ipc
2017 Sep-03 05:25:09606804 [INFO] Node started
~

So the problem here is, I am able to deploy contract and add data using contract functions in node 1, however pointing to node3 and calling the same function on contract address of node 1 gives me back null. Transactions are not synced between the nodes I guess ?. And here I am performing public transaction so all the participating should be able to see and read the data? but thats not happening in node 3 case, can somebody please help me resolve this.
cute pic -
https://www.instagram.com/p/BYGgz26BuZA/?hl=en&taken-by=utamaruru

Uh, so adding peers manually from the geth console got both the nodes to identify each other, but shouldnt that happen automatically. I have configured my nodes on private vpn

@sivachaitanya did you point node 3 to the bootnode too? Please reopen if you are experiencing an issue with the latest Quorum release.


add label support for volume response

I don't see the reason to add the builder- and constructor annotations to the Subnet class so please describe why you would add them. Also, please remove the unused import lombok.Singular in VolumeResponse.

@pellepelster push


Allow the user to reset input actions for all controller types.

Overview
Users can now reset the input actions for all controller types. The UI has also been updated to streamline this new functionality
Old UI

New UI

Changes

Fixes: #7521

This is awesome!!

/azp run


Pull Request for Adding the Code of Conduct

I have completed the Code of Conduct. I am hoping someone can review this and accept the pull request.

Looks good to me! I checked it with Tiffany's requirements and it has all the requirements!


Prompting with vague segmentation mask

Hi,
I tried prompting the model with a vague segmentation mask that I obtained from another model. The prompt isn’t very accurate, but it at least covers the object of interest. I expected SAM2 to refine the mask more precisely, but the results are not better.
Here is the mask prompt:

And result from SAM:

There are small patches scattered on the right side, and the left side of the mask is completely off.
What could be the reason?  Does SAM2 always need a point/box to refine the masks?

One thing you could try is transforming the segmentation mask to a bounding box and using that as input to sam2:
torchvision.ops.masks_to_boxes

This behavior is not surprising because the mask prompt here spans multiple objects. Prompts are expected to correspond to one object (or a part or sub-part of an object) but not multiple objects.
Can you try prompting with mask prompts corresponding to one object?

how did you use masks as input to sam2?


IdentifierGenerator is not working ideally

Right now, identifierGenerator works like this:
https://github.com/medusa-ui/medusa/blob/bc39079f701396439deac7b9309209dba5970c2e/src/main/java/io/getmedusa/medusa/core/util/IdentifierGenerator.java#L5-L16
And that's potentially a little dangerous.
Imagine scenario:
You have two iterations on the same content, as such:
[$foreach $items-bought]

Medusa

[$end]

[$foreach $items-bought]

Medusa

[$end]

The ID would only hash the content, so it would generate the same for both iterations - causing confusion and invalid HTML (id needs to be unique).
But at the same time I need to make sure that no matter how many refreshes you do, it always generates the same ID (otherwise the ConditionalRegistry or IterationRegistry does not have the right reference -> you get a situation where things work until you refresh).
Not sure what the best solution for this is.

Possible fix in PR #40
Changes:

IterationTag: use m-id instead of id for the template
websocket.js: loop through each template-element with an m-id

example page: http://localhost:8080/history


Fewer Literal Filepaths

Ammended all full literal resource path strings in CharacterFile and ModFile to make use of helper functions
Added character path helper function to create a path to the /char/ resources directory

very based, thanks for making these adjustments


experimental: remove \n from AutoGPT feedback_tool exit check

Thank you for contributing to LangChain!

[x] PR title: "package: description"

Where "package" is whichever of langchain, community, core, experimental, etc. is being modified. Use "docs: ..."  for template changes, "infra: ..." for CI changes.
Example: "community: add foobar LLM"

[x] PR message:

Description: I wanted to run the HumanInputRun tool for human-in-the-loop feedback during execution of the AutoGPT agent, but found that inputing 'q' or 'stop' did not work, because the check adds a newline to the feedback and so we wind up with, e.g.: >>> feedback = "\nq"
 >>> feedback in {"q", "stop"}
 False

Issue: I couldn't find one.
Dependencies: None
Twitter handle: if your PR gets announced, and you'd like a mention, we'll gladly shout you out! ... sure, it's @michaeljschock

[x] Lint and test: Run make format, make lint and make test from the root of the package(s) you've modified. See contribution guidelines for more: https://python.langchain.com/docs/contributing/

Additional guidelines:

Make sure optional dependencies are imported within a function.
Please do not add dependencies to pyproject.toml files (even optional ones) unless they are required for unit tests.
Most PRs should not touch more than one package.
Changes should be backwards compatible.
If you are adding something to community, do not re-import it in langchain.

If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, hwchase17.

@baskaryan, @efriis, @eyurtsev, @hwchase17 - okay to merge this change?


Typescript support

Hi there! Thanks for the extension, it's cool!
Can Typescript support be added to it? You know, typescript is a JS superset, mostly compatible, at least function calls and declarations are mostly the same.
I tried to change this line but with no success:
https://github.com/lannonbr/vscode-js-annotations/blob/a1167ef476741ef59a4fc503e0cfa6ab7cde49e1/src/extension.ts#L42
I am not familiar with VSCode extensions apparently :smiley:

I am interested in adding Typescript support. I currently use Esprima to find function calls within the code, and I am not sure if it will parse TS files, but I will dig into it and try finding a solution so this supports Typescript in an upcoming release.

Oh. I guess Esprima is not able to do that. Well, unfortunately I have no time to help you in this, but at least I can suggest you very good tool if you are interested https://github.com/dsherret/ts-simple-ast. Used it, for similar purpose.

It looks like recast may work given I can switch the underlying parser to also include a TS parser

Cool. I didn't even know it existed. Thanks for the response! Good luck.

And with a little bit of work, I just pushed up v0.3.0 and it is all set. Typescript function calls will now get annotations the same way as JS.
Closing.

Wow. That's amazing. Not bad, not bad :astonished:


Reformat Code on proto file introduces newlines at 8192 char intervals

When a proto file larger than 8192 chars has Reformat Code run, newlines are introduced after each 8192 chars.
This does not happen to the file when buf format is run on the same file.
This obviously can break the syntax of the proto file in various ways, which subsequently breaks protoc compilation and future buf format executions.
In the latter case, there's an additional issue that a Reformat Code run on a file with invalid syntax fails and clears the IntelliJ editor buffer.
(e.g. buf format would report a Failure: filename.proto:245:8: syntax error)
It looks like the output of buf format is being read from stdout and joined with separating newlines at https://github.com/bufbuild/intellij-buf/blob/main/src/main/kotlin/build/buf/intellij/formatter/BufFormatterService.kt#L66 , when in this case it should probably just be concatenated verbatim without separators.

Thank you @timw for the report - this will be fixed in the v0.3.1 version of the plugin, which should be published through the JetBrains marketplace in the next few days.


support multiple tax rates per invoice

fix #6
Adds support for multiple tax rates per invoice.
No changes required in the API, but Invoice.tax_rate is now obsolete. I left it in because you asked for backwards compatibility, so we don't throw an error if trying to set it. Now, numerical tax information is taken from the line_items, Invoice.tax_amount is still used for validation and for TaxTotalAmount
tax_category and tax_reason are still taken from the invoice:

German 7% and 19% are both the standard category and I don't currently see a case where one (but not another in the same invoice) line item would have a different category
tax_reason is simply not used by us. It could also go into the line_item object, but then we'd have to send it for each line_item - meh

Also, feel free to suggest better syntax, I'm much more of a Rails than pure Ruby person so if you don't like something by all means let's change it :)

actually don't review yet please, I have found a potential issue that needs fixing; will update

@halfbyte it now works as expected even if there are line_items with quantity > 1, adjusted spec too.


Profile Page

Basic Information
Make a profile page displaying a user's... well, profile. Place in /components/profile.tsx. Maybe break this down into smaller components and make an issue for each of them?

[ ] #123

Closed as of https://github.com/codersforcauses/penni/pull/117.

Sorry. Thats my bad


Update full_code.py

Add sess.close() in the end.

Thank you again for the update.
I decide to close the pull request, and help you can understand my decision.
Regards,
Morvan
On 25 October 2016 at 19:18, JamesRaynor<EMAIL_ADDRESS>wrote:

Add sess.close() in the end.
You can view, comment on, or merge this pull request online at:
https://github.com/MorvanZhou/tutorials/pull/18
Commit Summary

Update full_code.py

File Changes

M tensorflowTUT/tf11_build_network/full_code.py
https://github.com/MorvanZhou/tutorials/pull/18/files#diff-0 (2)

Patch Links:

https://github.com/MorvanZhou/tutorials/pull/18.patch
https://github.com/MorvanZhou/tutorials/pull/18.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MorvanZhou/tutorials/pull/18, or mute the thread
https://github.com/notifications/unsubscribe-auth/ASgmNKRisWBLVki4ltEhHexmyMgpbekWks5q3btXgaJpZM4Kfr4S
.

No worries~
谢谢你的教程~
On Wed, Oct 26, 2016 at 3:14 AM, Morvan<EMAIL_ADDRESS>wrote:

Thank you again for the update.
I decide to close the pull request, and help you can understand my
decision.
Regards,
Morvan
On 25 October 2016 at 19:18, JamesRaynor<EMAIL_ADDRESS>wrote:

Add sess.close() in the end.
You can view, comment on, or merge this pull request online at:
https://github.com/MorvanZhou/tutorials/pull/18
Commit Summary

Update full_code.py

File Changes

M tensorflowTUT/tf11_build_network/full_code.py
https://github.com/MorvanZhou/tutorials/pull/18/files#diff-0 (2)

Patch Links:

https://github.com/MorvanZhou/tutorials/pull/18.patch
https://github.com/MorvanZhou/tutorials/pull/18.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MorvanZhou/tutorials/pull/18, or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ASgmNKRisWBLVki4ltEhHexmyMgpbekWks5q3btXgaJpZM4Kfr4S>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MorvanZhou/tutorials/pull/18#issuecomment-256116442,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APLu6WSvlac9TIV3UFoWtVMBRZ6BkWGqks5q3kbxgaJpZM4Kfr4S
.


Use dependency injection or similar for HTTPMessage class

In a lot of cases software using this library will want to control the messages being sent from this library in a specific way. An easy way of achieving that (following DataConnector) is by using DI allowing us to override the HTTPMessage class and add logic or use different curl libraries.

@xow @spvickers I have an idea on how to support this in a backward-compatible way. Feedback?

@jeremeamia thanks! You might want to create it as a pull request so we can easily view it, comment on it and (in Stephen's case) merge it.

Yep, planning on it. Just wanted to see if it was something that would satisfy your needs first. In a similar boat as you. I'm exploring the use of this library to replace some of our custom LTI code, but would like to use Guzzle as the client.

Definitely would do what we need and solve this issue! Since this affected both of us, sounds like the solution will be useful in a lot of different cases.

Hi folks, I've been working on cleaning up this library for a while now over at https://github.com/franzliedke/lti. Using Guzzle is part of that.
Sorry for the shameless plug, but I'd surely appreciate some collaboration. :)

Sorry late to the conversation.  I do not like the HTTPMessage particularly and had been wondering about using another module instead, for example, guzzlehttp/guzzle.  But is your suggestion to enable the package to have users insert their own preferred library for this?  If so, is there a standard interface for such libraries which we could use to enable this to be possible?

@franzliedke That's a lot of changes! I haven't looked in detail, but is there any reason forking it? It would be great if improvements could be contributed upstream so we can all benefit.
@spvickers I like just having functions for what the library does and we can manually use whatever library we need. But true if there's a standard interface that would be useful to follow.

@franzliedke your library you reference at https://github.com/franzliedke/lti appears to be based on the ceLTIc project library.  This repository represents a siginificant rewrite of that library with the inclusion of support for LTI 2.  Your comments on what needs to change in this one to meet your needs would be appreciated.

@xow so if we agreed an interface you could write your own class using your own choice of HTTP library?

@spvickers I will, however, mine will be just moodle's curl wrapper so it won't do anyone else much good unfortunately

@xow @spvickers When I started this rewrite (more than a year ago), I believe this project did not exist yet and I was looking for a Composer library.
As for decoupling HTTP sending from concrete implementations, that's what PSR-7 is for, and that's what I built into my fork.

@franzliedke I appreciate your project pre-dates the release of this library, but I am concerned that your shameless plug for others to collaborate in your repository could be a backward step unless you have also added in LTI 2 support.  IMS welcomes contributions and suggestions which make this library better able to support the needs of users and decoupling HTTP is certainly high up on my list.  I had already started looking at guzzlehttp/guzzle so am pleased to see this is one you have found useful.

@spvickers I'm beginning to think that I only want to implement the low-level basics for sending / receiving LTI messages. I will leave the rest (implementing the logic for a tool provider) up to you - maybe you can even build on top of my library when it's done.

This will reduce the complexity on both sides.

@xow @spvickers Have a look at #12

Thanks for the pull request; we are looking at doing something in this area and will review your proposal.


Assignment 1

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Included Assignment answers
What did you learn from the changes you have made?
Python coding and how to extract data from dataset
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
No
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Writing these codes was quit challenging
How were these changes tested?
on VSCode
A reference to a related issue in your repository (if applicable)
The internet
Checklist

[- ] I can confirm that my changes are working as intended

You have unfortunately made a pull request to the wrong repo. You shouldn't be making a pull request to UofT-DSI/applying_statistical_concepts, but rather your own forked applying_statistical_concepts repo. Please read the instructions on your onboarding Assignment Submission Guide more carefully.


feat: add Mikescher/better-docker-ps

Mikescher/better-docker-ps: Because docker ps is annoying and does not fit my monitor/terminal width
$ aqua g -i Mikescher/better-docker-ps

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well.
Please confirm if this package works well yourself as much as possible.
Command and output
$ dops --help
better-docker-ps

Usage:
  dops [OPTIONS]                     List docker container

Options (default):
  -h, --help                         Show this screen.
  --version                          Show version.
  --all , -a                         Show all containers (default shows just running)
  --filter <ftr>, -f <ftr>           Filter output based on conditions provided
  --format <fmt>                     Pretty-print containers using a Go template
  --last , -n                        Show n last created containers (includes all states)
  --latest , -l                      Show the latest created container (includes all states)
  --no-trunc                         Don't truncate output (eg ContainerIDs, Sha256 Image references, commandline)
  --quiet , -q                       Only display container IDs
  --size , -s                        Display total file sizes

Options (extra | do not exist in `docker ps`):
  --silent                           Do not print any output
  --timezone                         Specify the timezone for date outputs
  --color <true|false>               Enable/Disable terminal color output
  --no-color                         Disable terminal color output
  --socket <filepath>                Specify the docker socket location (Default: /var/run/docker.sock)
  --timeformat <go-time-fmt>         Specify the datetime output format (golang syntax)
  --no-header                        Do not print the table header
  --simple-header                    Do not print the lines under the header
  --format <fmt>                     You can specify multiple formats and the first one that fits your terminal widt will be used
  --watch <interval>                 Automatically refresh output periodically (interval is optional, default: 2s)

Available --format keys (default):
  {{.ID}}                            Container ID
  {{.Image}}                         Image ID
  {{.Command}}                       Quoted command
  {{.CreatedAt}}                     Time when the container was created.
  {{.RunningFor}}                    Elapsed time since the container was started.
  {{.Ports}}                         Published ports. ([!] differs from docker CLI, these are only the published ports)
  {{.State}}                         Container status
  {{.Status}}                        Container status with details
  {{.Size}}                          Container disk size.
  {{.Names}}                         Container names.
  {{.Labels}}                        All labels assigned to the container.
  {{.Label}}                         [!] Unsupported
  {{.Mounts}}                        Names of the volumes mounted in this container.
  {{.Networks}}                      Names of the networks attached to this container.

Available --format keys (extra | do not exist in `docker ps`):
  {{.ImageName}                      Image ID (without tag and registry)
  {{.ImageTag}, {{.Tag}              Image Tag
  {{.ImageRegistry}, {{.Registry}    Image Registry
  {{.ShortCommand}                   Command without arguments
  {{.LabelKeys}                      All labels assigned to the container (keys only)
  {{.ShortPublishedPorts}}           Published ports, shorter output than {{.Ports}}
  {{.LongPublishedPorts}}            Published ports, full output with IP
  {{.ExposedPorts}}                  Exposed ports
  {{.NotPublishedPorts}}             Exposed but not published ports
  {{.PublishedPorts}}                Published ports
  {{.PublicPorts}}                   Only the public part of published ports
  {{.IP}                             Internal IP Address

Thank you!

LGTM.
Please update aqua to v2.17.0 or newer because we improved aqua generate-registry command.
https://github.com/aquaproj/aqua/releases/tag/v2.17.0

v4.84.0 is out 🎉
https://github.com/aquaproj/aqua-registry/releases/tag/v4.84.0


NGINX tries to serve static files then falls back to 404

We shouldn't do this since we will use client-side redirects


refactor: Use CSS instead of JavaScript to align chart elements in dashboards

Closes #1442
This PR swaps JS logic to keep chart elements in sync in the two columns of the Tall dashboard layout for CSS subgrid, which is both simpler and more performant.
As we have a nested layout and elements we want to align are not direct descendants of the grid layout that contains them (unavoidable due to e.g. drag and drop functionality), some of the container elements now use the contents display to make them "invisible" to the grid itself.

Thanks! We don't, I briefly tried to add one but had some problems with local GQL server not being accessible from Storybook. Maybe this could be a part of #1439?


pass a prompt in from stdin for inference

it code as it mostly already handles a prompt from stdin, this cleans it up to skip the prompter if it's included in the prompt txt file

I noticed that you have a prompter arg, but did not use it. Was there a reason?


Illegal Instruction Message

I am able to compile Flexbar but receive the following message when running:
18 Illegal instruction     (core dumped)
Here is my syntax:
flexbar \
  -r path/to/reads/fastq \
  -b path/to/barcodes/fasta \
  -bt LTAIL  \

It seems like the install was successful:
RUN apt-get update  && apt-get install -y libtbb2 libtbb-dev
RUN mkdir -p /opt/flexbar/tmp && cd /opt/flexbar/tmp \
  && wget https://github.com/seqan/flexbar/archive/v3.3.0.tar.gz \
  && wget https://github.com/seqan/seqan/releases/download/seqan-v2.4.0/seqan-library-2.4.0.tar.xz
  && tar xzf v3.3.0.tar.gz \
  && tar xJf seqan-library-2.4.0.tar.xz \
  && mv seqan-library-2.4.0/include flexbar-3.3.0 \
  && cd flexbar-3.3.0  \
  && cmake .  && make  \
  && cp flexbar /opt/flexbar/  \
  && cd /  \
  && rm -rf /opt/flexbar/tmp

ENV LD_LIBRARY_PATH "/opt/flexbar/:$LD_LIBRARY_PATH"

-- The C compiler identification is GNU 7.3.0
-- The CXX compiler identification is GNU 7.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test COMPILER_SUPPORTS_CXX14
-- Performing Test COMPILER_SUPPORTS_CXX14 - Success
-- Flexbar 64 bit architecture
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11")
-- Found BZip2: /usr/lib/x86_64-linux-gnu/libbz2.so (found version "1.0.6")
-- Looking for BZ2_bzCompressInit
-- Looking for BZ2_bzCompressInit - found
-- Configuring done
-- Generating done
-- Build files have been written to: /opt/flexbar/tmp/flexbar-3.3.0

Same issue with 3.4.0. Any tips appreciated.

This message indicates that you compiled Flexbar on a system that supports an instruction set like for example AVX that is not available on the system you run Flexbar on. So, I would propose to compile Flexbar on the machine you run it on and get the error. Flexbar should then also work on machines that support more instruction sets.
Kind regards,
Johannes


Remove test string from speed plugin code

The plugin was adding 'test' to the control bar. found the issue, just sharing back. thanks!

ahh, i see this is a dup of #1412


Refactored MqttService

UbiMqttProvider will be refactored and the MqttService constructor can then be finished

Codecov Report

Merging #11 into master will decrease coverage by 2%.
The diff coverage is 61.9%.

@@             Coverage Diff              @@
##             master      #11      +/-   ##
============================================
- Coverage     44.62%   42.62%   -2.01%
  Complexity       53       53
============================================
  Files             9        9
  Lines           242      244       +2
  Branches         14       14
============================================
- Hits            108      104       -4
- Misses          127      132       +5
- Partials          7        8       +1

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/fi/helsinki/btls/domain/Beacon.java
90% <100%> (+0.52%)
8 <0> (ø)
:arrow_down:

...in/java/fi/helsinki/btls/services/MqttService.java
60.86% <60%> (-12.47%)
8 <6> (ø)

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 cf4b685...2431190. Read the comment docs.


Token generation without a 'blessed' account

Is it possible to generate a valid token without a farmbot.io account?
I realize this project is fully F/OSS (which is amazing, great job!) so both sides can be changed as I see fit (no token validation, no token reading at all, etc) but that would probably make upgrading quite difficult.

@Phrohdoh Do you mean to ask if it is possible to have a single user setup? The current software was built from the ground up to support multiple accounts on one server, so that is probably outside of the architecture of this project.
That being said, it is an OSS project. If you wish to have a personal server for your own use, the deployment instructions are up-to-date and you could easily stand one up on a VPS or bare metal server on a LAN or behind a firewall.
What kind of use case did you have in mind?

The instructions mention cURL-ing https://my.farmbot.io/api/tokens to generate an API token.
Is this something that would exist on my own instance if I were to self-host this?
I'd like to host the software (server and web app) myself keeping all of my data on my own hardware, at least for the time being.
I do not think I will need any more than a single user (as long as a user can manage N FarmBots).

@Phrohdoh That is correct. For instance: If you were running the server on your laptop, you would just curl to http://localhost:3000/api/tokens instead of our server. The server running on your laptop would be identical to the one running on my.farmbot.io.
As for the user stuff, you could just create one account and keep the server behind a firewall to prevent outsiders from registering for an account.

Great, thanks for the information!
Unrelated to this issue but, is there an IRC channel (on freenode?) or gitter or anything similar for instant communication? Or is the forum the primary and only means of community communication?

@Phrohdoh We don't have one at the moment. Unfortunately, the Gitter chat was eating up a lot of our time on duplicate questions that had already been answered on the forum, so we eventually shut it down in favor of the message board. #farmbot on Freenode is a thing, but none of the core uses it.
Github issues and the forum are the best place to get support for now.


Autostart: Start hidden is not working

Describe the bug
My setting has autostart enabled in the Windows startup setting, and I turned on the start hidden function within the program setting. Still, every time I restart Windows, local send is opened as an active window on the desktop.
To reproduce

Go to 'Setting'
Click on 'Auto Start: start hidden'
Set the option to 'On'
It simply doesn't work

Expected behavior
Only the tray icon will appear on my taskbar every time I boot up Windows, without the main window pops up
Screenshots

Desktop (please complete the following information)
Windows 10 22H2
Version: 19045.2846
Smartphone (please complete the following information)
No response
Additional context
No response

I'm having this problem too!
System: Win10 22H2 19045.3448
AppVersion: Version: 1.11.1 (35)
But I don't have this problem on my Win11 computer.
I hope this issue is resolved soon.

Facing same issue.
Edition	Windows 10 Pro
Version	22H2
OS build	19045.3758
Localsend: 1.13.1 (42)

also facing the same issue on windows 10

@mizzunet autostart is already there, it autostrats but it doesnt start hidden\minimized

Having the same problem on windows 10

https://github.com/localsend/localsend/issues/464#issuecomment-1875180027 solved the issue for me, thanks @mizzunet

Spectacular app, Thanks to the Developer(s)!
But this bug needed to be fixed. I managed to start minimized in the Windows 11 tray through a command line in a bat placed in the Windows start folder. But even so, the app icon appears on the taskbar but minimized, so I leave the icon in a place that doesn't bother me until I close it to the tray. The bat line is this:
start /min "" "C:\Users\YOURUSERNAME\AppData\Local\Programs\LocalSend\localsend_app.exe"
But creating a simple shortcut in this folder and setting it to start minimized also has the same effect.
I believe this is easy to resolve in the app.

Hello!
About this problem, I created a free installer that adds a small executable to launch the LocalSend application hidden in the Windowsw system tray. An uninstaller will be available to remove this add-in from your system whenever you want:
https://rapidshare.io/Tfw/Hide_LocalSend_V.1.0.exe
All rights of the local app LocalSend belong to its respective developer.
I hope I helped someone! God Blesses!

Hide LocalSend
For those who are also facing this problem, where LocalSend does not start with the window hidden in Windows, I created a installer for myself and my friends whit a small 2mb application called "Hide LocalSend" that started in Windows through a simple link in the start menu. It does not change any registry lines and does not alter the original LocalSend installation in any way.
You can download it from this link and share it with anyone you want:
https://fastupload.io/4bedfbf0cdcd17b6
This is the script used to create de small app in SciTE:
Local $sUserName = @UserName
Local $sAppFolder = "C:\Users\" & $sUserName & "\AppData\Local\Programs\LocalSend\localsend_app.exe"
Run($sAppFolder, "", @SW_HIDE)
Sleep(1000)
Exit

The application I created is completely free and is not for sale. It was created with simple compilers, it is clean in Windows Defender. It can be uninstalled at any time with the native Windows uninstaller. If it doesn't work for you, please let me know so I can remove the sharing link. If it works, I'm happy to help, until this problem is resolved in future verion of LocalSend app.
God bless all.

At first, I couldn't find the reg key. After a while, I discovered that the LocalSend version installed was A UWP one, so I uninstalled it, and installed a regular executable, then I found the reg key and modified it based on @mizzunet instructions.

I was actually only able to fix this using the comment from @cr0eax in https://github.com/localsend/localsend/issues/1293#issuecomment-2105144960_ mentioning you have to add quotes in regedit:

Currently autorun registry key value looks like this: C:\Program Files\LocalSend\localsend_app.exe autostart When auto started by windows I can see that "autostart" argument is missing from command line. After changing registry value to following, problem is fixed. "C:\Program Files\LocalSend\localsend_app.exe" autostart So, bug caused by space in the path.
I see multiple opened issues about this problem. Hope it finally gets fixed now. #687 #1231 #464


bug: NESTED DEPLOYS FAIL: When using the scaffold's frontend to call a contract function which deploys another contract, it fails.

Is there an existing issue for this?

[X] I have looked through the existing issues

Which method was used to setup Scaffold-ETH 2 ?
git clone
Current Behavior
I have contract A that has function deploy() that deploys contract B. When using the frontend to call that smart contract function, I suspect that the nonce handling is not optimal, as a normal script calling the function works.
The exact error is:   Nonce too high. Expected nonce to be 4 but got 6. Note that transactions can't be queued when automining.
Expected Behavior
There should not be any reverts when calling a function that works also with a script.
Steps To Reproduce
Deploy contract A which has a function that deploys another contract. Use the scaffold's frontend to interact with your deploy() function. It should show JSON-RPC error on the frontend, and "Nonce too high. Expected nonce to be 4 but got 6. Note that transactions can't be queued when automining." similar error on the terminal which you are running yarn chain.
Anything else?
No response

Hey could you please provide a minimal SE-2 repo with the contracts you are using, or at least could you please pass the contracts so that it's easy to reproduce on our system locally

I believe this could be related to an issue with MetaMask rather than SE-2.
I don't know exactly how to reproduce it, but it is possible for MetaMask to think that you are operating at the incorrect nonce when spinning up a local chain. This is a MetaMask issue, but you can temporarily fix the issue by going to the MetaMask extension -> Settings -> Advanced -> Press "Clear Activity Tab Data". Then spin up a local chain again. You should be able to interact properly with the smart contracts again.

Closing this for now 🙌


VLAZ: Watch bomdn.com

VLAZ requests the watch of the watch_keyword bomdn\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

bomdn\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


handle_starr_data expects all seasons to have a statistics key

Error:
Traceback (most recent call last):
  File "/home/ronald/userScripts/modules/poster_renamerr.py", line 642, in main
    results = handle_starr_data(app, server_name, instance_type, include_episode=False)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/ronald/userScripts/util/utility.py", line 574, in handle_starr_data
    'season_pack': season['statistics']['episodeCount'] == season['statistics']['totalEpisodeCount'],
                   ~~~~~~^^^^^^^^^^^^^^
KeyError: 'statistics'

Looks like this section of code causes it:
https://github.com/Drazzilb08/daps/blob/c86f81fec8c3974b2ced1c768e270186c0dbb814/util/utility.py#L571-L577
I did some fairly basic debugging on my end (since my Python is not so great) to make it print out the season_data for each series it iterates over in the Sonarr instance which is causing the above error.
Mysterious Disappearances
{'nextAiring': '2024-05-08T13:30:00Z', 'previousAiring': '2024-05-01T13:30:00Z', 'episodeFileCount': 4, 'episodeCount': 4, 'totalEpisodeCount': 12, 'sizeOnDisk':<PHONE_NUMBER>, 'releaseGroups
--------
Stardust Telepath
{'episodeFileCount': 0, 'episodeCount': 0, 'totalEpisodeCount': 12, 'sizeOnDisk': 0, 'releaseGroups': [], 'percentOfEpisodes': 0}
--------
BARTENDER: Glass of God
{'episodeFileCount': 0, 'episodeCount': 0, 'totalEpisodeCount': 12, 'sizeOnDisk': 0, 'releaseGroups': [], 'percentOfEpisodes': 0}
--------
Kamichu!
None
{'episodeFileCount': 16, 'episodeCount': 16, 'totalEpisodeCount': 16, 'sizeOnDisk':<PHONE_NUMBER>, 'releaseGroups': ['Judgment'], 'percentOfEpisodes': 100}

In my case one of the series causing an error seems to be Kamichu! which seems to be lacking a statisctics key for Season 0 (Specials).

I can see that this series has an entry for Specials but no episodes in there, so a bit of an edge case.
No clue how to update the code elegantly to handle this, maybe by using dict.get instead of just grabbing the statistics key? In my debugging modifications this got it to print out None instead of getting a KeyError

Updated dev branch, can you please test this to see if this is fixed.

Just pulled the dev docker image down, getting a slightly different error:
Finished running sync_gdrive

An error occurred:
Traceback (most recent call last):
  File "/app/modules/poster_renamerr.py", line 642, in main
    results = handle_starr_data(app, server_name, instance_type, include_episode=False)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/util/utility.py", line 580, in handle_starr_data
    'season_has_episodes': season['statistics']['episodeCount'] > 0,
                           ~~~~~~^^^^^^^^^^^^^^
KeyError: 'statistics'

https://github.com/Drazzilb08/daps/commit/8b90f7394501e83209cacb13251aa72e35761fd7#diff-67b18f147213369955c00b435674927a17a57eb8e897cc69a9fa20b19a613ebfR580 I think this line might be the culprit?
In any case, thanks for taking a look!

I think you're 100% correct, please update and try again. Lemme know if the error persists.

Looks good now, I can see kometa setting up posters for shows in that sonarr instance.
Thanks for the help!

No worries. Glad this is fixed. Closing the issue.


use sepearte clientset for election

Signed-off-by: Ruiming Xie<EMAIL_ADDRESS>
What type of PR is this?
kind/enhancement
What this PR does / why we need it:
use sepearte clientset for leader election.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Codecov Report

Merging #389 (bf00490) into main (8be5c67) will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #389      +/-   ##
==========================================
+ Coverage   11.69%   11.72%   +0.02%
==========================================
  Files          56       56
  Lines        6120     6134      +14
==========================================
+ Hits          716      719       +3
- Misses       5354     5366      +12
+ Partials       50       49       -1

Impacted Files
Coverage Δ

...m/clusternet/clusternet/pkg/scheduler/scheduler.go
4.41% <0.00%> (-0.05%)
:arrow_down:

...ithub.com/clusternet/clusternet/pkg/agent/agent.go
1.77% <0.00%> (-0.04%)
:arrow_down:

...rc/github.com/clusternet/clusternet/pkg/hub/hub.go
2.80% <0.00%> (-0.04%)
:arrow_down:

...ernet/clusternet/pkg/hub/apiserver/shadow/utils.go
100.00% <0.00%> (+10.71%)
:arrow_up:

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 8be5c67...bf00490. Read the comment docs.


CDPS-832: Migration and Sync should not create null history for other fields

Codecov Report
Attention: Patch coverage is 90.47619% with 4 lines in your changes missing coverage. Please review.

Project coverage is 83.74%. Comparing base (79f8876) to head (d60321b).
Report is 1 commits behind head on main.

Files
Patch %
Lines

...gital/hmpps/prisonperson/jpa/PhysicalAttributes.kt
89.18%
0 Missing and 4 partials :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##               main      #64      +/-   ##
============================================
+ Coverage     83.53%   83.74%   +0.21%
- Complexity      385      386       +1
============================================
  Files            59       59
  Lines          1160     1175      +15
  Branches        113      113
============================================
+ Hits            969      984      +15
  Misses          119      119
  Partials         72       72

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Abandon scratch orgs with status of 'Deleted'

Do not commit scratch orgs with status of 'Deleted' to the pool
Add scratch org info status field to org details

Codecov Report

Merging #634 (b57b3dc) into develop (34780b4) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head b57b3dc differs from pull request most recent head c9c6205. Consider uploading reports for the commit c9c6205 to get more accurate results

@@           Coverage Diff            @@
##           develop     #634   +/-   ##
========================================
  Coverage    64.53%   64.53%
========================================
  Files           43       43
  Lines         1421     1421
  Branches       240      240
========================================
  Hits           917      917
  Misses         504      504

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 34780b4...c9c6205. Read the comment docs.


Better support for inputs and multiple classes.

textual doesn't have a very good way of getting input as of now. the only way to do it is by using an on_key event and testing for the enter key to end the input. while this works, it ends up getting very limited and being a headache to work with (especially with async).
for example, we have 2 classes, and one needs to get input:
class MyApp(App):
    async def on_load(self, event: events.Load) -> None:
        self.text = ""
        self.some_class: Optional["SomeClass"]

    async def on_key(self, event: events.Key) -> None:
        key: str = event.key

        if key == "enter":
            await self.some_class.finish_input(self.text)
        self.text += key

class SomeClass:
    def start(self) -> None:
        self.app = MyApp()
        self.app.run() # thread is blocked here, so we dont even get to the code below

        self.app.some_class = self
        ... # some other stuff here

    async def finish_input(self, text: str) -> None:
        ... # do something with the text
        await send_to_some_other_function(text)

since textual blocks the thread with run(), theres not a very good way to send things down to another class (at least when the textual app isn't the main class).
even if we could, trying to synchronize the app and the function waiting for the input would be practically impossible.
something i've also noticed while working with textual, is that it's a pain to work with when the app isn't the main class or being called from other async functions.
for example, when we have a class that starts textual on its own from an async function, a RuntimeError is generated by asyncio
class Client:
    async def start(self) -> None:
        ... # some other async stuff
        MyApp.run() # this generates an error due to run() creating a new event loop

when the textual class isn't being run from the main thread, you cannot start it at all with run().
however, there is a workaround to this, which is to await App.process_messages(), but this still blocks the thread so it would be pretty much pointless.
please implement better support for both of these.

I see you're 13, and clearly very smart to be coding at this level, but its best not to make assertions about how the API works when you're asking the guy who wrote it.
Regarding key events. It's not just the App that can receive them. If you call the focus() method on a custom widget, it will receive key events also. If you are implementing a widget, this is probably what you should do.
Your second "question" may be moot if you follow the advice above, but it isn't a Textual issue. If you want to run something else in parallel  with Textual, you can launch a task, which may be awaited. If you want that task to be able to respond to input, you will need to implement some way of communicating the key with that task. Textual uses a queue to do this, you could implement something similar.
Hope that helps.

ah, thought i was missing something. thank you


Syntax error when running in Eagle 9.6.2

I have a syntax error on line 94 when running in Eagle 9.6.2 on the board here.
It seems like the error is in this line: void AddPolyShape(UL_POLYSHAPE P, int L, int indent). But nothing jumps up to me as to what might be wrong here...
Anything I can do on my side to help?

Maybe it's because I'm not using the eagle branch, but I can't find it! Has it been pushed?

My mistake, I forgot to push the eagle branch - sorry about that!  Should be set now.

Ah thanks, I just pulled and updated.
It seems like I now run into #3 ... I have an error with Invalid layer while accessing 'dx[1]'. Has #6 been merged into the eagle branch?

Give it another try.  Since my above comment, I went ahead and rebased the eagle branch onto main and made the necessary changes to make polygons work in Eagle.  So, now the eagle branch is fully caught up with the fixes and features in main (including text, nets, etc).
Let me know if it works for you (or not!)

Same error still, but different line now (317): Invalid layer while accessing 'dx[1]'. I have weird cutout on my board, could this be the reason?
The board is available here if you want to try yourself to help debugging!
If there is anything I can do to help, please let me know!

This was an interesting one, thanks for sharing the file.  Turns out that there was a latent bug related to #3, and the workaround put in place for that was (not surprisingly) not a real fix.  Your file helped expose the underlying issue, so that is now properly fixed.
Now your board processes without an error, however there are one or more other issues that I'm trying to understand.

The GND pour render covers the entire board rather than having cutouts - this doesn't happen if I process the same BRD through Fusion instead, so it seems to be something unique to Polygons in Eagle.

Okay, I've solved the above issues.

In Eagle, if you haven't ratsnested then the polygon pours (copper) render as whatever outline you drew for the pour, i.e. without conforming to the board outline or clearance for other traces/vias/etc.  So, I added a line to force a ratsnest prior to processing.
Only nets which have copper (traces and/or vias) get included in the netlist now

There's one more little issue your board has exposed, which is that InteractiveHtmlBom doesn't support curved traces - since KiCad doesn't support them, there isn't a provision in the data structures to accommodate such a thing.  For now I've simply disabled processing curved traces (they just won't show up), but a real fix will require a change to InteractiveHtmlBom.  I'll submit an issue there (and a PR, if I can figure out how to solve it)

Hey,
Thanks for all that! All because of me! I'm glad this is working now! Even if the curved traces aren't showing, it's still a great tool!
Let me know if there is anything I can do to help!

InteractiveHtmlBom issue: https://github.com/openscopeproject/InteractiveHtmlBom/issues/229
On my fork, I've got this working already so it should be just a matter of time (working with the developer) to get this incorporated in ibom main.
Pull request in process: https://github.com/openscopeproject/InteractiveHtmlBom/pull/230

Awesome, thanks for your work!

The InteractiveHtmlBom changes have been merged, so the curved traces on your board should work now.  I'll leave this issue open until I've had the chance to go back and verify it.

Hey, I've just tested and apart from an upstream problem with python3.9 (that I've raised), it looks like everything is working perfectly!
Thanks a lot for this work!


ng-uncheckable directive for hybrid ui.bootstrap.buttons

The keyword uncheckable allows for hybrid checkbox-radio buttons.
It would be helpful if this keyword could be set via a directive ng-uncheckable, similar to ngChecked.
(I am new to Angular and don't understand how the ngChecked directive works yet. Otherwise I would simply copy and modify it.)

        Left
        Middle
        Right

Can you provide a use case or a demo for this?

My app has a highly interdependent model and the hybrid-mode fits my needs perfectly.
But in my case, the hybrid-mode depends on the current state of the model. The same group of radio buttons may switched to hybrid mode, and at other times not.

Without the hybrid-mode, I would need to add a Default-button with the value of nothing to allow the user to completely deselect a group of radio buttons.

With hybrid-mode, the user is able to complete deselect a group of radio buttons. Without the need of a Default-button.

In some cases the software selects/activates only one radio button and disables the other ratio buttons of the radio button group. Problem: With hybrid-mode enabled, the user would be able to de-select this one, computed choice. And thus, modify the model, even if it is forbidden.

I could work around thus, by disabling this one, computed choice. Thus, hindering the user to click the radio button. But in fact, this button has not the logical state of disabled but of selected. It is a valid choice and should not be displayed as disabled.

Generally speaking, I feel that Angular should allow for changing all (or most) aspects of the the UI interactively.

Maybe we could call it uib-uncheckable - I'm open to this feature. Would you like to try your hand at a PR implementing this directive along with the relevant tests?


Surpressing multiple brs

In your code you remove 'unnecessary empty lines':
// remove unnecessary empty lines
$output = preg_replace("/\n\n\n*/im", "\n\n", $output);

This actually leads to the removal of intended empty lines (at least in my case). It would be great to have some configuration for things like this. Should I submit a PR for this?
Just to give you an example:
Hello

 lets test this

 Cheers!

is converted to
Hello

lets test this

Cheers!

But I would expect:
Hello

lets test this

Cheers!

I'm actually fine with your example!
As long as something like that continues to work:
Hello

lets test this

Cheers!

should turn into
Hello lets test this

Cheers!

PR welcome! I don't think you need to make it an option.

Include this.
Hello  lets test this  Cheers!

I put in a PR a few days ago to address this:
https://github.com/soundasleep/html2text/pull/75

Same here, it would be great that multiple "br" like start

end works


ui issue in button in cms pages  in mobile view

Bagisto Version

[ ] master branch

Steps To Reproduce

go to cms pages in admin panel

try to edit cms page

Actual Result

@deepaksinghgusain227 please lookout the issue


Feature request: Define HTTP header other than DNT to exclude Ajax calls

Unfortunately, most browsers nowadays set the HTTP DNT header, so the data-do-not-trackattribute cannot be used. I'd love to be able to define an additional custom HTTP header to disable tracking for Ajax calls.
Use case: We have a documentation website, and an app that pulls part of the documentation per Ajax to display it as online help. It would be great to add a header like X-My-DNT to the Ajax requests for these pages so Umami can distinguish Ajax calls from actual user accesses. Please note that the app often displays the same content as users would see if they used the documentation site themselves, so not adding the script is not an option for these pages.
For example, add a data-http-dnt="X-My-DNT" attribute to the script tag for these pages. This leaves the definition of the custom header to the developer (here: X-My-DNT), and Ajax calls can transmit that header.

Sorry, a Network Changed error caused this to be posted twice.


Be able to delete a record's value

Would be awesome if you guys could implement a way to remove a record's value. E.g.:
var record = client.record.get('user/jwanglof')
console.log(record.get());

Console log:
{
    firstname: 'Johan',
    surname: 'Wanglof',
    pets: [
        {pet_id: 'roger_the_rabbit'},
        {pet_id: 'max_the_cat'},
        {pet_id: 'rosa_the_cow'}
    ]
}

Lets say that max_the_cat dies (sorry for being gruesome) and I want to remove it from the pets-list. It would be sweet if I could do a delete on just that record by index (or index-name perhaps?):
record.delete('pets[1]');

Agreed, this feature sounds really useful! We have added it onto our roadmap and will implement it soon. Will keep this thread updated with progress and release date.

What's the status on this feature? =)

Just started looking at this, sorry for the long delay.
I'm considering having this done via .set( path, undefined )
A bit keen to keep delete ( which is a very final action ) and record modification separate.
Also, what kind of callback would you expect? If Bob is subscribed to pets.1 and John removed it would Bob expect to get undefined back and react accordingly?
Following example is just a brain dump of what issues might arise from that API being used with an Array.
petOwner = ds.record.getRecord( 'petOwner ' );

//Bob

function petDetailsChanged( pet ) {
    if( typeof pet === "undefined" ) {
      // pet died =(
      // must now unsubscribe and cleanup, and take into account pets[ 2 ] might now be pets[ 1 ]
   } else {
      //pet status has changed! ( and is still totally alive )
   }
}

petOwner.subscribe( 'pets.1', petDetailsChanged );
petOwner.subscribe( 'pets.2', petDetailsChanged);

//John
petOwner.set( "pets.1", undefined );

@jwanglof  @WolframHempel Thoughts?

My initial thought is that the dump seems to make sense, I can talk to my CTO tomorrow and see if he has any thoughts as well.
But, it makes sense that the developer, and not the API, needs to take care when a record is being changed in any way imo, but the API probably needs to make sure that the array is in a correct order so that index 1 isn't undefined when there is an index 2 (this shouldn't be a problem with JavaScript though).
One thing to think about when creating the document for this feature is that this must be really clear so the developers knows how to handle with this =)
And it seems smart to keep delete and record modification separate for sure.

Closing as duplicate of #119


Click on navigation bar item does not trigger navigation (scroll down)

Describe the bug
When a navigation item on a page with a navigation bar is clicked then the scrolling down to the page's section referenced by the navigation item does only start for a short moment but then stops. It only succeeds fully when the same navigation item is clicked again.
The next issue concerns clicking on 'MEHR ERFAHREN' once the downwards navigation has succeeded (currently, by clicking again on 'Auto Abo abschließen'): If one tries to click on the leftest 'MEHR ERFAHREN' button like as follows
await click('MEHR ERFAHREN', {}, below('Premium-Paket'));

then the button is scrolled into view and you get this error: "Error: Element matching text "MEHR ERFAHREN" is covered by other element".
If one adds await hover('MEHR ERFAHREN'); before the above mentioned click, then the click succeeds, no error message.
To Reproduce
const { openBrowser, goto, click, closeBrowser } = require('taiko');
(async () => {
    try {
        await openBrowser({headless: false});
        await goto('vwfs.de/autoabo.html');
        await click('Ja, ich willige ein');
        await click('Auto Abo abschließen');
    } catch (error) {
        console.error(error);
    } finally {
        await closeBrowser();
    }
})();

Expected behavior
1st issue expected behavior: After the click on 'Auto Abo abschließen' the page should be scrolled down to where the navigation item is referencing to.
2nd issue expected behavior: The above mentioned click on 'MEHR ERFAHREN' should lead for the right element to be found, scrolled into view and be clicked instead of throwing the above mentioned error message.

Versions:

Taiko: 1.0.23
MacOS Catalina: 10.15.6 (19G2021)
Node.js: v14.7.0

Additional context
It appears that the scrolling issue is related to the size of the browser window. Running the same test with a lower browser window height, for example, seems to make the scrolling (after the click on 'Auto Abo abschließen') work. But it still seems to be relatively brittle.

I could that when we try to click Auto Abo abschließen for the first time the page is scrolled once the coordinates to click is calculated and hence Taiko is clicking on wrong coordinates. Seems like highlighting element on action is causing the scroll, trying to find why that is happening.


Added a option to click the task tile to open a box with all the details #73

Related Issue
Closes #73
Type of Change
Put x inside the square bracket to specify what type of change your PR is:

[x] New Feature

Description of Change
Clicking the List tile opens a box with all information of task and an option to delete the task.
Implementation Details
Create a New widget named task box.
Demo

@Sanat-Jha  Try making it responsive. When I rotate the screen to Landscape,  there is a bottom overflow

@Akshit517 Overflow fixed.


Docker volume reverted to very old version after reboot

I am running 3 photon 2 cluster and using vsphere docker volumes. It seems, that docker volume used by our mariadb data volume has reverted to several months old version. I tried to copy 2 days old vmdk file from backupd from equallogic and still seems to contain old files. How is this possible?
Is there any tool to show files in vsphere docker volume vmdk?
I was using few months old version (latest) tried to update to new latest.

@aleskinen thanks for the logs and the details I'll review and update.