Automatic error report from arnavs/HealthSimulations.jl

Repo: arnavs/HealthSimulations.jl
Run URL: https://github.com/arnavs/HealthSimulations.jl/actions/runs/45997280
Image ID: sha256:23e996c42a17dc7bd314e5d992cdec375a581bf6e2e49af9917aae167d328b3f
Stacktrace:
Traceback (most recent call last):
  File "/root/tagbot/action/__main__.py", line 48, in <module>
    versions = repo.new_versions()
  File "/root/tagbot/action/repo.py", line 186, in new_versions
    current = self._versions()
  File "/root/tagbot/action/repo.py", line 157, in _versions
    root = self._registry_path
  File "/root/tagbot/action/repo.py", line 77, in _registry_path
    uuid = self._project("uuid")
  File "/root/tagbot/action/repo.py", line 68, in _project
    return str(self.__project[k])
KeyError: 'uuid'

[err]

Probably duplicate error:
Repo: oxinabox/ipynb2Literate.jl
Run URL: https://github.com/oxinabox/ipynb2Literate.jl/actions/runs/46001132
Image ID: sha256:23e996c42a17dc7bd314e5d992cdec375a581bf6e2e49af9917aae167d328b3f
Stacktrace:
Traceback (most recent call last):
  File "/root/tagbot/action/__main__.py", line 48, in <module>
    versions = repo.new_versions()
  File "/root/tagbot/action/repo.py", line 186, in new_versions
    current = self._versions()
  File "/root/tagbot/action/repo.py", line 157, in _versions
    root = self._registry_path
  File "/root/tagbot/action/repo.py", line 77, in _registry_path
    uuid = self._project("uuid")
  File "/root/tagbot/action/repo.py", line 68, in _project
    return str(self.__project[k])
KeyError: 'uuid'

@christopher-dG You should probably just skip if the Project.toml file has no uuid.

Already done, see #75 (in the future these issues won't be opened more than once)


How can i get modifications in DBCorePutRequest which exist in updating hook ?

You need to compute them by first calling next DBCoreTable.getMany({trans, keys}) to inspect what is currently on the given keys. You could have a look at how the CRUD hooks middleware does it in hooks-middleware.ts.
DBCore API is a bit more verbose than the CRUD hooks but you also gain more control operations and you are able to things that is not possible using the hooks.
Note however that the hooks will continue to be maintained so if you're fine with them, keep using them. In a future major release, the hooks middleware may be moved into a helper library, but my promise is to keep it maintained no matter if they are put in a helper library or in the core library.


[9.x] Adds class discoverer Discover

What?
Introduces a class specialized in discovering files as PHP Classes. Rework of the DiscoverEvents, but generalized.
use Illuminate\Filesystem\Discover;

$events = Discover::inside('Events')->all();

The main idea is to detach the discover mechanism so other services or packages can also discover files from within a path, like Policies. As with the DiscoverEvents, it only collects instantiable classes.
use Illuminate\Filesystem\Discover;
use ReflectionClass;

$policies = Discover::inside('Policies')
    ->all()
    ->filter(function (ReflectionClass $policy) {
        return str_ends_with($policy->name, 'Policy');
    });

It receives an Application instance, so it can be mocked and tested.
It's multi-tenancy friendly, as it supports changing the root dir and root namespace.
Can be set to recursive.
Returns a Collection, so further filters can be applied over it.

use Illuminate\Filesystem\Discover;

// Find all classes in `/www/projects/laravel/myProject/Components`.
$policies = Discover::inside('Components')
    ->recursively()
    ->atNamespace('myProject', 'Project\\')
    ->all()

Why?
Basically, centralize the discovery of Classes. This can be done for Policies, Events and what not. May be Components can benefit from this approach as a way to cache them.
BC?
None, is only additive. May be in next version we could get rid of DiscoverEvents and whatever the Gate does to find Policies (it doesn't work recursively last time I checked).

PS: Should I PR this to master instead?

I’ll take that as a PR too master.
Italo Baeza C.

El 22-03-2022, a la(s) 13:44, Taylor Otwell @.***> escribió:

Closed #41616.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.


Add AS3 build tool submodule

This is probably the best library for it.

@6100m Thanks for this, one small problem, this library doesn't appear to generate an SWF...

I noticed that too actually, apparently you code the SWF directly with flappy?

@6100m Hmm, we need an SWF statically generated somehow.

Yeah, I'll find a different library, one sec :)

@zurgeg Found a library that can create a SWF file and read and write data to it :)

In turn, this library SHOULD be able to generate it :)

We should create another repository for the SWF's source. This should not be dynamically generated.

In my opinion, we should build the SWF using this, but store it statically in a different repo.

I don't think it would be too good to create a monorepo for all related source, especially as that may get tricky when v770/v512 are implemented. #7's approach of serving the SWF from here seems best, but source should be elsewhere.


fix(esl-scrollbar): remove unnecessary width

Issue: https://github.com/exadel-inc/esl/issues/1197

:tada: This PR is included in version 4.0.0-beta.18 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Building Experimental Light Client for Teku

PR Description
Currently in the process of building the Light Client Experimental Server infrastructure into Teku as suggested by @benjaminion here: https://github.com/ConsenSys/teku/issues/4230
If the code is too early in the process to merge as a pull request, I'll be working on this for the next 3-4 months so I can open a new pull request once more logic has been developed.

@ajsutton Hi Adrian, I'm about to resume building the light-client. I've successfully implemented a ./gradlew spotlessApply build to the Teku client, but it still has compilation issues in regards to the dependencies...
And as far as testing my light-client build, all the compilation issues will have to be resolved first right?
Because I tried a mass ./gradlew implementation to resolve the compilation issues but ran into Build failures at 40%... Are y'all running into Build failures with the ./gradlew implementation?

And as far as testing my light-client build, all the compilation issues will have to be resolved first right?

Yep, if we can't compile cleanly we pretty much can't do anything.

Because I tried a mass ./gradlew implementation to resolve the compilation issues but ran into Build failures at 40%... Are y'all running into Build failures with the ./gradlew implementation?

We're not having any issues with building.  CI runs that process on every PR and every merge to master so we always know it works.  I'd have to see the errors your getting from gradle to know why it's having issues but you'd expect it to fail if there are compilation problems.
You can do just the compile step with:
./gradlew compileJava compileTestJava compileJmhJava compileIntegrationTestJava compileAcceptanceTestJava

which may make it easier to track down the compilation issue at least.

You can do just the compile step with:
./gradlew compileJava compileTestJava compileJmhJava compileIntegrationTestJava compileAcceptanceTestJava

which may make it easier to track down the compilation issue at least.

Thanks, will try that.
If I continue running into any compilation errors I'll try resolving them by myself first (in order to sharpen my problem solving skills) for a few hours and open an issue or get back to you if I need further help.
Thanks again AJ.

Update:
Good News: I got the gradle build compiler up to 99% executed.
Bad News: Build failing at 99%.
Will return tomorrow to see if I can successfully complete the build.

@ajsutton
When I run ./gradlew spotlessApply & ./gradlew distTar installDist it completes successfully at 100%, but when I run ./gradlew, it fails at 99%.
I narrowed it down and its failing at these points:
Eth2P2PNetworkOptionsTest > helpDisplaysDefaultNetwork() FAILED
   java.lang.AssertionError at Eth2P2PNetworkOptionsTest.java:134

tech.pegasys.teku.cli.options.LoggingOptionsTest
tech.pegasys.teku.cli.subcommand
I wonder maybe if I need to reinstall my gradle? I've already deleted and re-pulled the teku repo into my local folder.
Will continue chipping away at this issue.

Eth2P2PNetworkOptionsTest > helpDisplaysDefaultNetwork() FAILED
   java.lang.AssertionError at Eth2P2PNetworkOptionsTest.java:134

It should provide a URL to a HTML page that will give more detail on why those tests failed.  It's probably teku/build/reports/tests/test/index.html that you want to open but the gradle output will have it as a full URL that will definitely be right.

Yup, checked that html page, that's how I narrowed down the errors to these classes:
tech.pegasys.teku.cli.options.LoggingOptionsTest
tech.pegasys.teku.cli.subcommand
I'll continue chipping away at this issue... I'm hoping I can start building (and testing) at least some of the light client API (without some of the dependencies running).
I'll figure out something.

The HTML should provide complete details of the failure (including a stack trace).  If you can share that I can help identify what's failing. It may be the test makes some assumption about the system which isn't true in your case and the test just needs fixing.

Unsure if this is what you need, but within the tech.pegasys.teku.cli.options package, Eth2P2PNetworkOptionsTest class, the helpDisplaysDefaultNetwork() failure results are showing:
java.lang.AssertionError:
Expecting:
 <"
?[1mteku?[21m?[0m [OPTIONS] [COMMAND]

Description:

Run the Teku beacon chain client and validator

Options:
  ?[33m-c?[39m?[0m, ?[33m--config-file?[39m?[0m=?[3m<FILENAM?[23m?[0m?[3mE>?[23m?[0m
                             Path/filename of the yaml config file (default:
                               none)
      ?[33m--data-beacon-path?[39m?[0m=?[3m<FI?[23m?[0m?[3mLENAME>?[23m?[0m
                             Path to beacon node data
                               Default: <data-base-path>/beacon
      ?[33m--data-path, --data-ba?[39m?[0m?[33mse-path?[39m?[0m=?[3m<FILENAME>?[23m?[0m
                             Path to the base directory for storage
                               Default: C:\Users\Jeyak\AppData\Local\teku
      ?[33m--data-storage-archive?[39m?[0m?[33m-frequency?[39m?[0m=?[3m<FREQUENCY>?[23m?[0m
                             Sets the frequency, in slots, at which to store
                               finalized states to disk. This option is ignored
                               if --data-storage-mode is set to PRUNE
                               Default: 2048
      ?[33m--data-storage-mode?[39m?[0m=?[3m<S?[23m?[0m?[3mTORAGE_MODE>?[23m?[0m
                             Sets the strategy for handling historical chain
                               data.  (Valid values: ARCHIVE, PRUNE)
                               Default: PRUNE
      ?[33m--data-storage-non-can?[39m?[0m?[33monical-blocks-enabled?[39m?[0m[=?[3m<BOOLEAN>?[23m?[0m]
                             Store non-canonical blocks
                               Default: false
      ?[33m--data-validator-path?[39m?[0m=?[3m<FILENAME>?[23m?[0m
                             Path to validator client data
                               Default: <data-base-path>/validator
      ?[33m--eth1-deposit-contrac?[39m?[0m?[33mt-address?[39m?[0m=?[3m<ADDRESS>?[23m?[0m
                             Contract address for the deposit contract. Only
                               required when creating a custom network.
      ?[33m--eth1-deposit-contrac?[39m?[0m?[33mt-max-request-size?[39m?[0m=?[3m<INTEGER>?[23m?[0m
                             Maximum number of blocks to request deposit
                               contract event logs for in a single request.
                               Default: 10000
      ?[33m--eth1-endpoint, --eth?[39m?[0m?[33m1-endpoints?[39m?[0m=?[3m<NETWORK>?[23m?[0m[,?[3m<NETWORK>?[23m?[0m...]...
                             URLs for Eth1 nodes.
                               Default: []
  ?[33m-h?[39m?[0m, ?[33m--help?[39m?[0m                 Show this help message and exit.
      ?[33m--initial-state?[39m?[0m=?[3m<STRIN?[23m?[0m?[3mG>?[23m?[0m
                             The initial state. This value should be a file or
                               URL pointing to an SSZ-encoded finalized
                               checkpoint state.
  ?[33m-l?[39m?[0m, ?[33m--logging?[39m?[0m=?[3m<LOG VERBOSI?[23m?[0m?[3mTY LEVEL>?[23m?[0m
                             Logging verbosity levels: OFF, FATAL, ERROR, WARN,
                               INFO, DEBUG, TRACE, ALL (default: INFO).
      ?[33m--log-color-enabled?[39m?[0m[=?[3m<?[23m?[0m?[3mBOOLEAN>?[23m?[0m]
                             Whether Status and Event log messages include a
                               console color display code
                               Default: true
      ?[33m--log-destination?[39m?[0m=?[3m<LOG?[23m?[0m?[3m_DESTINATION>?[23m?[0m
                             Whether a logger is added for the console, the log
                               file, or both (Valid values: BOTH, CONSOLE,
                               DEFAULT_BOTH, FILE)
                               Default: DEFAULT_BOTH
      ?[33m--log-file?[39m?[0m=?[3m<FILENAME>?[23m?[0m  Path containing the location (relative or
                               absolute) and the log filename. If not set will
                               default to <data-path>/logs/teku.log
      ?[33m--log-file-name-patter?[39m?[0m?[33mn?[39m?[0m=?[3m<REGEX>?[23m?[0m
                             Pattern for the filename to apply to rolled over
                               log files. If not set will default to
                               <data-path>/logs/teku_%d{yyyy-MM-dd}.log
      ?[33m--log-include-events-e?[39m?[0m?[33mnabled?[39m?[0m[=?[3m<BOOLEAN>?[23m?[0m]
                             Whether frequent update events are logged (e.g.
                               every slot and epoch event)
                               Default: true
      ?[33m--log-include-validato?[39m?[0m?[33mr-duties-enabled?[39m?[0m[=?[3m<BOOLEAN>?[23m?[0m]
                             Whether events are logged when validators perform
                               duties
                               Default: true
      ?[33m--metrics-categories?[39m?[0m[=?[3m<METRICS_CATEGORY>?[23m?[0m[,?[3m<METRICS_CATEGORY>?[23m?[0m...]...]
                             Metric categories to enable
                               Default: [JVM, PROCESS, BEACON, DISCOVERY,
                               EVENTBUS, EXECUTOR, LIBP2P, NETWORK, STORAGE,
                               STORAGE_HOT_DB, STORAGE_FINALIZED_DB,
                               REMOTE_VALIDATOR, VALIDATOR,
                               VALIDATOR_PERFORMANCE]
      ?[33m--metrics-enabled?[39m?[0m[=?[3m<BO?[23m?[0m?[3mOLEAN>?[23m?[0m]
                             Enables metrics collection via Prometheus
                               Default: false
      ?[33m--metrics-host-allowli?[39m?[0m?[33mst?[39m?[0m[=?[3m<hostname>?[23m?[0m[,?[3m<hostname>?[23m?[0m...]...]
                             Comma-separated list of hostnames to allow, or *
                               to allow any host
                               Default: [<IP_ADDRESS>, localhost]
      ?[33m--metrics-interface?[39m?[0m=?[3m<N?[23m?[0m?[3mETWORK>?[23m?[0m
                             Metrics network interface to expose metrics for
                               Prometheus
                               Default: <IP_ADDRESS>
      ?[33m--metrics-port?[39m?[0m=?[3m<INTEGE?[23m?[0m?[3mR>?[23m?[0m
                             Metrics port to expose metrics for Prometheus
                               Default: 8008
  ?[33m-n?[39m?[0m, ?[33m--network?[39m?[0m=?[3m<NETWORK>?[23m?[0m    Represents which network to use.
                               Default: mainnet
      ?[33m--p2p-advertised-ip?[39m?[0m=?[3m<N?[23m?[0m?[3mETWORK>?[23m?[0m
                             P2P advertised IP (Default: <IP_ADDRESS>)
      ?[33m--p2p-advertised-port?[39m?[0m=?[3m<INTEGER>?[23m?[0m
                             P2P advertised port. The default is the port
                               specified in --p2p-port
      ?[33m--p2p-advertised-udp-p?[39m?[0m?[33mort?[39m?[0m=?[3m<INTEGER>?[23m?[0m
                             Advertised UDP port to external peers. The default
                               is the port specified in --p2p-advertised-port
      ?[33m--p2p-discovery-bootno?[39m?[0m?[33mdes?[39m?[0m[=?[3m<enr:-...>?[23m?[0m[,?[3m<enr:-...>?[23m?[0m...]...]
                             List of ENRs of the bootnodes
      ?[33m--p2p-discovery-enable?[39m?[0m?[33md?[39m?[0m[=?[3m<BOOLEAN>?[23m?[0m]
                             Enables discv5 discovery
                               Default: true
      ?[33m--p2p-enabled?[39m?[0m[=?[3m<BOOLEA?[23m?[0m?[3mN>?[23m?[0m]
                             Enables P2P
                               Default: true
      ?[33m--p2p-interface?[39m?[0m=?[3m<NETWO?[23m?[0m?[3mRK>?[23m?[0m
                             P2P network interface
                               Default: <IP_ADDRESS>
      ?[33m--p2p-nat-method?[39m?[0m=?[3m<natM?[23m?[0m?[3method>?[23m?[0m
                             Specify the NAT circumvention method to be used,
                               possible values are UPNP, NONE. NONE will
                               require manual router configuration.
                               Default: NONE
      ?[33m--p2p-peer-lower-bound?[39m?[0m=?[3m<INTEGER>?[23m?[0m
                             Lower bound on the target number of peers
                               Default: 64
      ?[33m--p2p-peer-upper-bound?[39m?[0m=?[3m<INTEGER>?[23m?[0m
                             Upper bound on the target number of peers
                               Default: 74
      ?[33m--p2p-port?[39m?[0m=?[3m<INTEGER>?[23m?[0m   P2P port
                               Default: 9000
      ?[33m--p2p-private-key-file?[39m?[0m=?[3m<FILENAME>?[23m?[0m
                             This node's private key file. If not specified,
                               uses or generates a key which is stored within
                               the <beacon-data-dir>.
      ?[33m--p2p-static-peers?[39m?[0m[=?[3m<P?[23m?[0m?[3mEER_ADDRESSES>?[23m?[0m[,?[3m<PEER_ADDRESSES>?[23m?[0m...]...]
                             Static peers
                               Default: []
      ?[33m--p2p-subscribe-all-su?[39m?[0m?[33mbnets-enabled?[39m?[0m[=?[3m<BOOLEAN>?[23m?[0m]
                               Default: false
      ?[33m--p2p-udp-port?[39m?[0m=?[3m<INTEGE?[23m?[0m?[3mR>?[23m?[0m
                             UDP port used for discovery. The default is the
                               port specified in --p2p-port
      ?[33m--rest-api-cors-origin?[39m?[0m?[33ms?[39m?[0m[=?[3m<origin>?[23m?[0m[,?[3m<origin>?[23m?[0m...]...]
                             Comma separated list of origins to allow, or * to
                               allow any origin
                               Default: []
      ?[33m--rest-api-docs-enable?[39m?[0m?[33md?[39m?[0m[=?[3m<BOOLEAN>?[23m?[0m]
                             Enable swagger-docs and swagger-ui endpoints
                               Default: false
      ?[33m--rest-api-enabled?[39m?[0m[=?[3m<B?[23m?[0m?[3mOOLEAN>?[23m?[0m]
                             Enables Beacon Rest API
                               Default: false
      ?[33m--rest-api-host-allowl?[39m?[0m?[33mist?[39m?[0m[=?[3m<hostname>?[23m?[0m[,?[3m<hostname>?[23m?[0m...]...]
                             Comma-separated list of hostnames to allow, or *
                               to allow any host
                               Default: [<IP_ADDRESS>, localhost]
      ?[33m--rest-api-interface?[39m?[0m=?[3m<?[23m?[0m?[3mNETWORK>?[23m?[0m
                             Interface of Beacon Rest API
                               Default: <IP_ADDRESS>
      ?[33m--rest-api-port?[39m?[0m=?[3m<INTEG?[23m?[0m?[3mER>?[23m?[0m
                             Port number of Beacon Rest API
                               Default: 5051
  ?[33m-V?[39m?[0m, ?[33m--version?[39m?[0m              Print version information and exit.
      ?[33m--validator-keys?[39m?[0m=?[3m<KEY_?[23m?[0m?[3mDIR>:<PASS_DIR> | <KEY_FILE>:<PASS_FILE>?[23m?[0m[,?[3m<KEY_DIR>:?[23m?[0m
     ?[3m   <PASS_DIR> | <KEY_FI?[23m?[0m?[3mLE>:<PASS_FILE>?[23m?[0m...]...
                             <KEY_DIR>:<PASS_DIR> will find <KEY_DIR>/**.json,
                               and expect to find <PASS_DIR>/**.txt.
                             <KEY_FILE>:<PASS_FILE> will expect that the file
                               <KEY_FILE> exists, and the file containing the
                               password for it is <PASS_FILE>.
                             The path separator is operating system dependent,
                               and should be ';' in windows rather than ':'.
                               Default: []
      ?[33m--validators-early-att?[39m?[0m?[33mestations-enabled?[39m?[0m[=?[3m<BOOLEAN>?[23m?[0m]
                             Generate attestations as soon as a block is known,
                               rather than delaying until the attestation is due
                               Default: true
      ?[33m--validators-external-?[39m?[0m?[33msigner-keystore?[39m?[0m=?[3m<FILE>?[23m?[0m
                             Keystore (PKCS12/JKS) to use for TLS mutual
                               authentication with external signer
      ?[33m--validators-external-?[39m?[0m?[33msigner-keystore-password-file?[39m?[0m=?[3m<FILE>?[23m?[0m
                             Password file to decrypt keystore (PKCS12/JKS)
                               that will be used for TLS mutual authentication
                               with external signer
      ?[33m--validators-external-?[39m?[0m?[33msigner-public-keys?[39m?[0m[=?[3m<STRINGS>?[23m?[0m[,?[3m<STRINGS>?[23m?[0m...]...]
                             The list of external signer public keys, or a URL
                               to load the keys from
                               Default: []
      ?[33m--validators-external-?[39m?[0m?[33msigner-slashing-protection-enabled?[39m?[0m[=?[3m<BOOLEAN>?[23m?[0m]
                             Enable internal slashing protection for external
                               signers
                               Default: true
      ?[33m--validators-external-?[39m?[0m?[33msigner-timeout?[39m?[0m=?[3m<INTEGER>?[23m?[0m
                             Timeout (in milliseconds) for the external signing
                               service
                               Default: 5000
      ?[33m--validators-external-?[39m?[0m?[33msigner-truststore?[39m?[0m=?[3m<FILE>?[23m?[0m
                             Keystore (PKCS12/JKS) to trust external signer's
                               self-signed certificate
      ?[33m--validators-external-?[39m?[0m?[33msigner-truststore-password-file?[39m?[0m=?[3m<FILE>?[23m?[0m
                             Password file to decrypt keystore (PKCS12/JKS)
                               that will be used to trust external signer's
                               self-signed certificate
      ?[33m--validators-external-?[39m?[0m?[33msigner-url?[39m?[0m=?[3m<NETWORK>?[23m?[0m
                             URL for the external signing service
      ?[33m--validators-graffiti?[39m?[0m=?[3m<GRAFFITI STRING>?[23m?[0m
                             Graffiti value to include during block creation.
                               Value gets converted to bytes and padded to
                               Bytes32.
      ?[33m--validators-graffiti-?[39m?[0m?[33mfile?[39m?[0m=?[3m<GRAFFITI FILE>?[23m?[0m
                             File to load graffiti value to include during
                               block creation. Value gets converted to bytes
                               and padded to Bytes32. Takes precedence over
                               --validators-graffiti. If the file can not be
                               read, the --validators-graffiti value is used as
                               a fallback.
      ?[33m--validators-keystore-?[39m?[0m?[33mlocking-enabled?[39m?[0m=?[3m<BOOLEAN>?[23m?[0m
                             Enable locking validator keystore files
                               Default: true
      ?[33m--validators-performan?[39m?[0m?[33mce-tracking-mode?[39m?[0m=?[3m<TRACKING_MODE>?[23m?[0m
                             Set strategy for handling performance tracking.
                               Valid values: LOGGING, METRICS, ALL, NONE
                               Default: ALL
      ?[33m--ws-checkpoint?[39m?[0m=?[3m<STRIN?[23m?[0m?[3mG>?[23m?[0m
                             A recent checkpoint within the weak subjectivity
                               period. Should be a string containing
                               <BLOCK_ROOT>:<EPOCH_NUMBER> or a URL containing
                               the field ws_checkpoint with the same
                               information.
Commands:
  ?[1mhelp?[21m?[0m                  Displays help information about the specified command
  ?[1madmin?[21m?[0m                 Holds advanced tools for node admins
  ?[1mtransition?[21m?[0m            Manually run state transitions
  ?[1mpeer?[21m?[0m                  Commands for LibP2P PeerID
  ?[1mgenesis?[21m?[0m               Commands for generating genesis state
  ?[1mslashing-protection?[21m?[0m   Manage local slashing protection data used by the
                          validator client.
  ?[1mmigrate-database?[21m?[0m      Migrate the database to a specified version.
  ?[1mdebug-tools?[21m?[0m           Utilities for debugging issues
  ?[1mvalidator-client?[21m?[0m, ?[1mvc?[21m?[0m  Run a Validator Client that connects to a remote Beacon
                          Node
  ?[1mvoluntary-exit?[21m?[0m        Create and sign a voluntary exit for a specified
                          validator.

Teku is licensed under the Apache License 2.0
">
to contain:
 <"-n, --network=<NETWORK>    Represents which network to use.
                               Default: mainnet">
	at tech.pegasys.teku.cli.options.Eth2P2PNetworkOptionsTest.helpDisplaysDefaultNetwork(Eth2P2PNetworkOptionsTest.java:134)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:686)
	at org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
	at org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
	at org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
	at org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
	at org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:84)
	at org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
	at org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
	at org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
	at org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
	at org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
	at org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
	at org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:104)
	at org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:98)
	at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$6(TestMethodTestDescriptor.java:212)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:208)
	at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:137)
	at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:71)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$5(NodeTestTask.java:135)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$7(NodeTestTask.java:125)
	at org.junit.platform.engine.support.hierarchical.Node.around(Node.java:135)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:123)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:122)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:80)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
	at org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.invokeAll(SameThreadHierarchicalTestExecutorService.java:38)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$5(NodeTestTask.java:139)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$7(NodeTestTask.java:125)
	at org.junit.platform.engine.support.hierarchical.Node.around(Node.java:135)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:123)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:122)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:80)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
	at org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.invokeAll(SameThreadHierarchicalTestExecutorService.java:38)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$5(NodeTestTask.java:139)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$7(NodeTestTask.java:125)
	at org.junit.platform.engine.support.hierarchical.Node.around(Node.java:135)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:123)
	at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:122)
	at org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:80)
	at org.junit.platform.engine.support.hierarchical.SameThreadHierarchicalTestExecutorService.submit(SameThreadHierarchicalTestExecutorService.java:32)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor.execute(HierarchicalTestExecutor.java:57)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestEngine.execute(HierarchicalTestEngine.java:51)
	at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:108)
	at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:88)
	at org.junit.platform.launcher.core.EngineExecutionOrchestrator.lambda$execute$0(EngineExecutionOrchestrator.java:54)
	at org.junit.platform.launcher.core.EngineExecutionOrchestrator.withInterceptedStreams(EngineExecutionOrchestrator.java:67)
	at org.junit.platform.launcher.core.EngineExecutionOrchestrator.execute(EngineExecutionOrchestrator.java:52)
	at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:96)
	at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:75)
	at org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.processAllTestClasses(JUnitPlatformTestClassProcessor.java:99)
	at org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor$CollectAllTestClassesExecutor.access$000(JUnitPlatformTestClassProcessor.java:79)
	at org.gradle.api.internal.tasks.testing.junitplatform.JUnitPlatformTestClassProcessor.stop(JUnitPlatformTestClassProcessor.java:75)
	at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.stop(SuiteTestClassProcessor.java:61)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36)
	at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
	at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33)
	at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94)
	at com.sun.proxy.$Proxy2.stop(Unknown Source)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker$3.run(TestWorker.java:193)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.executeAndMaintainThreadName(TestWorker.java:129)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.execute(TestWorker.java:100)
	at org.gradle.api.internal.tasks.testing.worker.TestWorker.execute(TestWorker.java:60)
	at org.gradle.process.internal.worker.child.ActionExecutionWorker.execute(ActionExecutionWorker.java:56)
	at org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:133)
	at org.gradle.process.internal.worker.child.SystemApplicationClassLoaderWorker.call(SystemApplicationClassLoaderWorker.java:71)
	at worker.org.gradle.process.internal.worker.GradleWorkerMain.run(GradleWorkerMain.java:69)
	at worker.org.gradle.process.internal.worker.GradleWorkerMain.main(GradleWorkerMain.java:74)

I'm reading through all this and it seems like some variables/commands need to be changed within this class (at least according to the failed test results) [currently perusing through all this].

ah that's interesting.  It looks like colour output has somehow wound up enabled when the test prints the help text so it then isn't finding the expected string (because the actual string has a bunch of control characters in it to set the colours). I'm not sure why that's happening - it obviously thinks it's attached to a console in your setup whereas it usually doesn't.

I'm suspecting its the terminal I'm using (Gitbash), I'll try using my Ubuntu terminal and get back with the results.

@jeyakatsa Give it a try with the changes in https://github.com/ConsenSys/teku/pull/4578 - it hopefully overrides PicoCLI's console detection to force colours to be disabled which should get the test to pass for you.

@ajsutton that resolved it. The Gradle build completed successfully, but there are still dependency import issues when opening the client through Eclipse. Can I at least build some of the Light Client Api infrastructure while some of the Teku dependencies are in red?

Just an FYI (I've started building the PublicKey Getters and Setters into the Light Client infrastructure). Will be opening a pull request once I test the said and possibly other functionalities against Gradle. Thanks again Aj!


Script Page: Some expression sheets like hologram romani are weirdly aligned and ended up being cut out

https://apps.atlasacademy.io/db/NA/script/9130030110

This change broke chara fade in of normal servants. I'm unsure why the offset is used differently.
Partially reverted in https://github.com/atlasacademy/apps/commit/4fd74dbd8cecea6d4dc9d22d888b560f4f32c3b4
https://apps.atlasacademy.io/db/JP/script/0300121941
https://apps.atlasacademy.io/db/JP/script/0300121751
https://apps.atlasacademy.io/db/JP/script/0300120110

Rasputin and Kadoc should be shifted down by 50 here https://apps.atlasacademy.io/db/NA/script/0300121941


Tutorial

Change Summary
Tutorial showing xWRF usage.
Related issue number

Closes #69

Checklist

[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable

@andersy005 Can you advise me on how to properly integrate the jupyter notebooks into the docs?

@andersy005 Can you advise me on how to properly integrate the jupyter notebooks into the docs?

@lpilz, since we are already using markdown for docs, i would recommend using myst + jupytext combo to author the notebooks as well. here's an example of a notebook in a myst markdown format: https://raw.githubusercontent.com/intake/intake-esm/main/docs/source/tutorials/index.md
here's a pointer to the docs as well: https://myst-nb.readthedocs.io/en/latest/use/markdown.html
feel free to ping whenever you need any feedback and/or clarification

Exception occurred:
  File "/home/docs/checkouts/readthedocs.org/user_builds/xwrf/conda/72/lib/python3.9/site-packages/jupyter_client/kernelspec.py", line 294, in get_kernel_spec
    raise NoSuchKernel(kernel_name)
jupyter_client.kernelspec.NoSuchKernel: No such kernel named xwrf-dev

I've had trouble with writing a notebook using nb_conda_kernels making the RTD build fail. If you resave the notebook with just "Python3 (ipykernel)" (i.e.choose the base kernel because the RTD build will need to use that after activating the environment), the build should move forward.

@lpilz:  This is looking great!  Thanks for doing this!
Some comments:

I'm wondering if we should reference the non-code name of the project as simply xWRF, instead of xWRF (i.e., without the back-ticks).  My thinking here is that back-ticks should be used for the name of actual code.  For example, the package that you import would be xwrf, but the "English name" of the package is xWRF.  (Does that make sense?  I'm open to other suggestions.)

It appears that the xarray HTML reprs do not play well with dark mode iin the furo Sphinx theme.  Some of the text is rendering with too little contrast to visually see in dark mode, but it displays beautifully with light mode.  I don't think this a problem for xWRF to solve, but it is something that needs further investigation and a new issue in the right place needs to be made (or a PR, if we can figure out how to fix it).  (Note that there are lots of dark-mode display problems that have come up:   https://github.com/pydata/xarray/issues/4024, https://github.com/pydata/xarray/pull/4036, https://github.com/pydata/xarray/issues/4161, and others, I'm sure.)

@lpilz:  I believe I have developed a "hack" to fix the xarray HTML repr display issues.  It turns out the that Xarray HTML repr includes/ships CSS that assumes that any theme changes will be contained in the html element's theme attribute.  But the Sphinx Furo theme assumes that the body element will have a data-theme attribute containing the theme (dark or light or auto).  So, I added some custom javascript to force the html[theme] attribute to match the body[data-theme] attribute.

I'm not sure what the proper fix for this is...whether it should go in the Furo theme or in Xarray to specifically deal with the Furo theme.

BTW, this fix works on Chrome, and I haven't verified with other browsers.

BTW, this fix works on Chrome, and I haven't verified with other browsers.

unfortunately, this is still not functional on non-chromium based browsers

Safari

Firefox

@kmpaul

I'm wondering if we should reference the non-code name of the project as simply xWRF, instead of xWRF
I also put some thought into that and decided to preliminarily go with the backticked version simply because of capitalization issues at the start of sentences. However, I agree that it adds a level of highlight that is maybe too much. I'll change it and we can just see if we like it like that.

@kmpaul Thanks for your work on the styling issue. Unfortuately, I don't have a lot of experience with front end engineering, so I won't be able to help a lot on this. But if there is something I can do nonetheless - don't hesitate to delegate.

In my opinion, we should document the styling issue in a separate issue and address it at a later time

@andersy005:  I think that's fine.  Yes.  I realized that my fix might be browser limited...but I wasn't expecting it to be that limited.  Since it displays fine with the light theme of Furo, which is always an option, let's not let the styling issue hold up this PR.

See #73

Incidentally, I implemented the "proper fix" for this in Xarray yesterday (see https://github.com/pydata/xarray/issues/6500 and https://github.com/pydata/xarray/issues/6501).  So, after the next release of Xarray, we won't need this hacky fix anyway.

Well...  So, I know we said we'd fix this in another PR, but it turns out the fix was really easy.  It shouldn't have worked on Chrome, either, but it turns out Chrome is a little more forgiving about assigning values to const variables.  So, I just fixed it.

thank you 🙏, @kmpaul! the fix looks great

Thanks, @andersy005! I'm appreciate that.

I concur, nice work. Thanks a lot @kmpaul :)

@lpilz, you are welcome!  Glad I could help!


v0.4.8

Clear cookies when error occurs on login.

Coverage decreased (-0.2%) to 92.562% when pulling caa347da1d3e3ae7fef6ed01c3ae860907316dba on develop into c0a08d3572ddb048cef70c717676477498c62086 on master.


What's the purpose of sessionLock variable in dataservice.js?

Hey, I'm rebuilding this project in Ionic/Angular5 and I'm wondering what the sessionLock variable is for in this file:
https://github.com/mesh0000/poolui/blob/master/app/utils/dataservice.js

seems to me it is to not allow being logged in one tab if you logged out in another...
but I would consider writing or using some other session handling , as there is a known bug of unknown (for me at least) origin - if you not log out from session and open the app after longer time, it shows you're logged in but you cannot set any new values


What about lucid icons pack for qwik?

Can you do it? Lucid icons are awesome, the total number is enormous though, must be a lot of work 🤔

It could probably be done fairly easily -- I'll bear it in mind for the future.  But I created this carbon-icons-qwik library because I'm in the process of implementing Carbon Design System components for Qwik.


Runtime upgrade is failing with new cli

Expected Behavior

Upgrade should pass
Actual Behavior
Upgrade fails with dapr-operator in crashloopbackoff
Steps to Reproduce the Problem

Install previous stable version of cli
Install previous stable version of runtime
Upgrade CLI to use latest RC
Try upgrading dapr with latest_cli upgrade -k --runtime-version 1.12.0-rc.3

Release Note

RELEASE NOTE:

Not able to reproduce this with 1.11 CLI or 1.12 RC CLI.

Closing this, as now I am not able to repro this on my local kind cluster.


Problem: Block height in event stream is string.

Solution: Change block height to integer.
Fixes #2166

Ok, I forgot to refresh the page so it only displayed to me the comments uptil 'request changes' so I made a those tiny fixes. Nevertheless the changes are very small.

Okay. I'll change the description of this PR to say that it also fixes that other issue.


Change ssl certificate without dropping connections

Hi , I am using uWebSockets.js with socketio and I was searching for way to update ssl certificate when ssl renews without restarting server. Like its done with httpserver. I can use filewatcher to know if certificate is renewed, can you please tell how to change in uWebSockets.js.
httpServer.setSecureContext(
{
  key: fs.readFileSync(settings.PRIVKEY),
  cert: fs.readFileSync(settings.FULLCHAIN)
});

const { SSLApp } = require("uWebSockets.js");
const { Server } = require("socket.io");

const app = new SSLApp({
  key_file_name: "keys/server_key.pem",
  cert_file_name: "keys/server_cert.pem",
});
const io = new Server({ transports: ["websocket"] });
io.attachApp(app);

You can use the SNI feature for this.


Quality difference between two HTML examples, no way to display/hide triangles easily.

I note that using the threeMeshIntersectExample.html style for drawing/rendering/viewing seems more chunky and less smooth than the renderings that geometry.html.
Also I couldn't tell how to turn on the triangle lines (they seem to add some definition for what I am doing now) in the threeMeshIntersectExample.html and likewise I couldn't tell how to turn them off using the geometry.html style. It would be nice to have a check box for this.

The mesh intersection example now shows clear lines. geometry.html is now out of date.


Update what-are-teams-live-events.md

Typo

@cichur PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

Hi @dstrome Wondering if you can help with this PR? Thanks.


gir-rs: unstable-2021-05-05 -> unstable-2021-11-21

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@ofborg eval

Looks good to me, thank you!


update download instructions for firewall

install_github("gregorbj/VisionEval/sources/framework/visioneval") needs additional instructions for folks working within a proxy server (like ODOT).  See SWIM documentation and also below:
library(httr)
set_config(use_proxy(url="proxynew.odot.state.or.us", port=8080))
set_config( config( ssl_verifypeer = 0L ) )

also updated getting started text based on comments from @jrawbits


Update PDP docs to account for new --no-engine client option

In 5.2, we are releasing a --no-engine option for Prisma Client. In addition, the correct engine to use will be inferred from the connection string (prisma:// is routed to PDP, postgres:// is routed to a library engine, etc)
We should update our PDP documentation to show that --accelerate and --data-proxy are no longer needed, but --no-engine can help reduce deployed app size.

Closing as it already exists.


Series methods isnull and notnull

Fulfils enhancement #203: isnull and notnull methods for series (especially for use with columns in dataframes).
I've also slipped in a couple of other small tweaks - fixing a bug with writing series CSV, and adding trove classifiers to indicate Python 3 compatibility.

Thanks Thomas-- just merged this in.


Update to fix change in awesome spawn internal call

working with AwesomeSpawn.launch is tricky, but easiest to mock
the return results from an external command
/cc @himdel @Fryguy

thanks! looks like it should fix it, but can't reproduce locally :(

Why is the code testing against launch?  That's a private method.  I would expect it to stub run or run!.


Linking devices from Home Assistant

Is your feature request related to a problem? Please describe.
I would like to handle linking (and unlinking) devices from Home Assistant and also see if devices are linked to each other in Home Assistant. One of the benefits with having a heat control system is the ability for wall thermostats to control the radiator thermostats depending on the measured temperature in the room. I do not believe there is any option for that but please let me know if I have missed some option for setting links.
Describe the solution you'd like
A service in Home Assistant for each of the methods; addLink and removeLink or a combined service for the two where the action could be specified as a param. Perhaps also an attribute like "children" and "parent" to see a list of linked devices for a specific device. This would probably have to include a getLinks method in Pyhomematic.
Describe alternatives you've considered
The set_temperature for a RTV could be set based on the current temperature measured by the wall thermostat. The problem with this approach would be that the control algorithms that Homematic uses when a link has been established would be lost and that it could be troublesome keep track of all devices and controls in the automation.
The link could of course be set on the CCU but then it can not be used in automations and there would be no information in Home Assistant that the link is established. There is also the aspect of trying to use the CCU as little as possible to only having to use Home Assistant for heat control.
I would definitely help out/do the implementation if it is decided that it is a requested feature!

Are you aware, that you get the linked devices into Home Assistant by adding an additional interface? It's mentioned here.
Would look something like that:
homematic:
  interfaces:
    groups:
      host: <IP_ADDRESS>
      port: 9292
      path: /groups

The climate entities you get are the virtual thermostat groups you see in the CCU.
The process of linking the devices won't be integrated into Home Assistant for sure. Doing that with service calls is way to complicated, whereas it's just a few clicks on the CCU (or other GUI for Homegear / hassio). I'm always open for adding new features that help with automating. But the topic your talking about is setting up the infrastructure. You only do that once. As soon as it's configured you never touch it again. And you probably won't ever add or remove links on the fly within automations. So even though for theoretical completeness it might make sense, it's not worth the effort in my opinion. It can be done already, just not in the same UI. But that's the same with a lot of other products.

Alright, I did not know about the group option so I will try that for getting the linked devices, thanks.
When you say it's just a few clicks on other GUI you mention "hassio" what do you mean by that?
I do agree that it would not change often. I was planning on using it to auto link RTVs that are assigned to the same room as a WT using automation or the like in Home Assistant. But as you say perhaps it is to much work for such a thing.

When you say it's just a few clicks on other GUI you mention "hassio" what do you mean by that?

If you use hassio instead of a standalone installation, then there's an add-on which can use the rf-modules you can put on raspberry pies. In such a setup you don't need a CCU anymore because hassio acts as one. But to do administration you also need a configuration-program that handles pairing of devices etc.. So even in this case with deeper integration into Home Assistant we still rely on 3rd party software to set up the devices.
Your plan to use an automation would only make sense if you would move a device into different rooms from time to time. But besides having to (re)link devices whenever that happens, that would also always break automations that depend on these devices. A stable setup would be to have a dedicated thermostat for each relevant room and leave it there.

Alright yes I did try the setup with the rf-modules but it is not really a straight forward experience with the third party software so was thinking a Home Assistant/Pyhomematic integration could help out with that.
Yes that is true but it would make for the possibility to not interact with the ccu/third party software which would be nice.
Thanks for your responses and commenting on the issue!


Fix helm webhook ingress error: port name or number is required

Use the first exposed port for the service

can we please bump the chart number? I need this fix :)


provide @import solution for scss in readme

related to https://github.com/skakri/photoswipe-rails/issues/9  . Current solution in Readme is bit confusing if you use @bootstrap or other gems...

Also check #8


Fix the plurality naming issue for KeyVault

Since the auto-resolve solution will not be merged soon, here manually fix it to unblock GA

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.KeyVault

I think you might miss the change in another place, because I don't find the old plural enum is deleted.
I have double checked, this model is also used in ManagedHsmNetworkRuleSet.

Good catch, fixed


refactor: return an error in case response deserialization fails

This change is

Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Please upload report for BASE (main@fb92713). Learn more about missing BASE report.

Files
Patch %
Lines

crates/mempool_infra/src/component_client.rs
0.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #377   +/-   ##
=======================================
  Coverage        ?   80.74%
=======================================
  Files           ?       35
  Lines           ?     1620
  Branches        ?     1620
=======================================
  Hits            ?     1308
  Misses          ?      245
  Partials        ?       67

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


Nginx setting for user home's .kalite folder is not set

If not using ka-lite user, kalite will run with /home/user/.kalite and this needs to be defined in /etc/ka-lite/nginx.d/blah.conf
The consequence is that static files, videos etc. won't show.

You mean, if the user runs ka-lite as a different user than the one specified at install time (using the deb file)? For instance, if I install on the RPi and choose pi as the user at that time, do I need to do anything special? Or should I have specified a different user still to be the ka-lite useR?

It's related to what the user puts during the installation when prompted by debconf:

So you're saying it's an issue when I run as a different user than what I specified in that command prompt?

Yes, if you don't put ka-lite as the username, it will fail to serve static media.
If you want it to work for a different user, you need to put something in /etc/ka-lite/nginx.d/myprecious.conf - like so:
set $kalite_home /home/myuser/.kalite;

This line is included in the nginx config in /etc/nginx/sites-available/kalite.conf.

c4ec18d

Fixed in #295, verified that it works

Also, the 0.15.1-ubuntu2 with the fix is in https://launchpad.net/~learningequality/+archive/ubuntu/ka-lite-proposed/+packages


V1.8.1 patchset

Dev tests are passing. Carrying patches from v1.8.0.
@s-urbaniak @aaronlevy

Why is this being added to the image. A sidecar installs these plugins on hosts and those should be used. Can you provide the context?


Signing Server wrong OTP error message:

Getting this error when we enter incorrect OTP at the time of signing.

@Raheel1258 The model error isn't coming from the backend.

Facing same issue on Upgraded keeper app v 1.1.8(276) to 1.1.11(297)

Getting this error on Dev app sometimes.
Closing this issue for now.


[STORM-1122] Fix the format issue in Utils.java

Delete the abandoned comment "(defn xxx )" function,
fix a bunch of messed indention,
unify inconsistent space format,
expand "import java.io." and "import java.util." in the file header.

Nice, +1

+1

+1 nice to see it consistent.

We probably want to cherry-pick this to 0.10.x and maybe even 0.9.x.  Just so porting patches between them is not a pain.

I merge it into master and 0.10.x-branch, but not 0.9.x since we want to fade out 0.9.x.


mftraining error: Size > 0:Error:Assert failed:in file ../../../src/cutil/emalloc.cpp, line 32

Environment

Tesseract Version:

leptonica-1.78.0
 libgif 5.1.4 : libjpeg 8d (libjpeg-turbo 1.5.3) : libpng 1.6.34 : libtiff 4.0.9 : zlib 1.2.11 : libwebp 0.6.1 : libopenjp2 2.3.0
Found AVX2
Found AVX
Found FMA
Found SSE
Found libarchive 3.3.2 zlib/1.2.11 liblzma/5.2.3 bz2lib/1.0.6 liblz4/1.7.5
Found libcurl/7.59.0 OpenSSL/1.0.2o (WinSSL) zlib/1.2.11 WinIDN libssh2/1.7.0 nghttp2/1.31.0

Platform: Windows version 64bit

Current Behavior:
I followed one of many tutorials of tesseract (https://towardsdatascience.com/simple-ocr-with-tesseract-a4341e4564b6), and first I got the unicharset error, but after some time searching the solution, I finally moved on (from 0 shapes detected to 18 shapes detected).
But now when I do
mftraining -F font_properties.txt -U unicharset -O eng.test.exp0.tr

It shows the following error:
Read shape table shapetable of 18 shapes
Size > 0:Error:Assert failed:in file ../../../src/cutil/emalloc.cpp, line 32

I've seen that there is a similar previous issue
https://github.com/tesseract-ocr/tesseract/issues/1664
But in that issue the file of the error is different.
Expected Behavior:
Gives me the shapetable, so I'll be able to continue with the training (cntraning, renaming those 4 files and generate the traineddata and test it)
Here are the .tif and the files that I generated following the tutorial, if it is of any help.
files_used.zip

The included file eng.test.exp0.tr does not look like a .tr file. It seems to be a unicharset file.

The correct syntax should be
mftraining -F font_properties -U unicharset -O font_name.unicharset font_name.font.exp0.tr

As you already have destroyed the .tr file because of the wrong syntax, you should recreate that file.

Oh!
You are right, I was using the wrong syntax.
My bad and thank you for the answer ^^
I'm closing the issue

Hi, my syntax is all correct... but still im getting the following error when i run the mftraining command.

i've followed the normal training methods mentioned in the documentationlink
This is my first time posting a issue here, i dont know the procedure so pls Help me. Thank you.
This is all my files regarding the same. Link to files


Geometry (occupancy) Update?

Hello! Geometry (occupancy) is listed in "Coming soon," is there any update on this?
Thank you!

Hey,
The current development plan is:

Adding the Triplane fitting feature #14.
3inFusion experiments.
Geometry only (occupancy) experiments.


Not working with vue 3 and nuxt 3

I'm trying to add this in my nuxt 3 applications. But I'm facing a problem to add this. For this, I'm using version 0.4.8. If I try to install the latest version I got this error.

This is how I use it.
<script setup>
import JsonEditorVue from "json-editor-vue";

const value = ref('')

</script>

<template>
      <JsonEditorVue v-model="value" />
</template>

And this is the error I'm getting.

For Nuxt 3 usage see https://github.com/cloydlau/json-editor-vue#nuxt-3
For Nuxt 3 example see https://github.com/cloydlau/json-editor-vue/tree/main/demo/nuxt3
Please provide a codesandbox if none of above solves your problem, so I can locate it, thanks.


(FACT-1090) Query Ruby $LOAD_PATH when used

Facter 3.0 included a regression where running Facter in some Puppet
commands would not include the correct Ruby $LOAD_PATH, resulting in
missing facts. This happens because Facter caches the $LOAD_PATH when
initialized, and only resets it when Facter.reset is called.
Fix the regression by updating Facter to query $LOAD_PATH when facts
are loaded instead of caching on initialization.

CLA signed by all contributors.

@peterhuene got a little more complex, but I think this replicates Facter 2.x behavior.

I think I can add some tests that hack around with Ruby's $LOAD_PATH in Facts (that's going to be ugly). I'll see how it goes.


With popup on multiple editable celle per lines and columns

I have a cross table between dynamic columns and lines, each cells are editable with x-editable plugin.
When I click on a cell an additionnal div with the popup form is created, but not in the TD cell, juste at the same level. Here is the generated code in a screen.

What am I missing ? Is this a known problem ?

Ok should be closed, i just fix it.. It's not a bug, your editable selector has to be inside a TD (like A tag) and not be the TD.


common yaml functionality

Moved to https://github.com/LinuxForHealth/hl7v2-fhir-converter/pull/160


AsyncLazy with API call is being called twice across 4 components.

I am using AsyncLazy in a shared class between multiple blazor components, which all want the data OnInitializedAsync
As show in this blog I am replicating the structure of data caching
https://blog.stephencleary.com/2013/01/async-oop-3-properties.html
In API class
    API(){
            LazyVariable= new AsyncLazy<DTO>(async () =>
            {
                string url = $"url";
                var response =  await httpClient.GetFromJsonAsync<DTO>(url);
                AppState.var = response;
                return response;
            });
     }

I am in each component (4 rendering at same time) calling via
protected override async Task OnInitializedAsync()
{
api = new Api()
await api.LazyVariable
}

However, I see the API called twice across the 4 components

You're instantiating a new Api object which has the AsyncLazy<DTO> as an instance field. Either the Api instance needs to be shared, or the AsyncLazy<DTO> instance needs to be shared if you don't want it to run more than once.


Add support for importing raw textures (RGB16/24, RGBA16/32)

This updates modding.import_texture() to allow choosing raw 16/24 bit RGB or 16/32 bit RGBA as formats to import.
Tested all formats in-game and they all work as expected. DXT ends up looking better than 16 bit most of the time but is included for completeness sake.

Meant to do a rebase, not create a merge commit. I'll re-do it.


Amendment to remove mention of derivative catalogs

This is a small and straightforward amendment, that tightens security around the removal of artificial satellites. We do not plan on storing any identifications arising from the alert-vetting satellite cross-matching process, and so we can simply remove all mention of derivative catalogs and how to handle them.

Helmut and Ashley approved this change offline, so I will merge this PR and send them a copy of the new PDF.

Thanks all! Merging now.


Feature/fix unkeyed fields

What
Initially to fix unkeyed fields but includes the following changes:

Fix composite literal uses of unkeyed fields - it is safer to explicitly pair up keys to values instead of relying on the ordering of a struct.
Remove parallelisation of web endpoint unit tests - to prevent intermittent failures
Remove deprecated functions, methods and variables from api package
Include audit process in api check function for put version endpoint
Use log.ErrorCtx and log.InfoCtx when logging in dimension package
Set variable has_downloads to true when updating a version with
downloads occur and use this variable in the handler to prevent updates
to the edition or dataset resource.
Update unit tests

How to review
Check logical changes make sense and unit and acceptance tests pass.
Who can review
Anyone

Still got unkeyed fields in instance_external_test.go

Re. Still got unkeyed fields in instance_external_test.go - I have raised this in another PR to be fixed; so will not be doing it here


[CT-575] [Bug] 1.0.0 Cannot execute an empty query

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
dbt is errorring with cannot execute and empty query for a model that does have columns description in a schema.yml file, and having persist_docs: {columns: true} configured.
Database Error in model my_third_dbt_model (models/example/my_third_dbt_model.sql)
Expected Behavior
No response
Steps To Reproduce

dbt init
Create a third simple model with column description: e.g.: models/example/my_third_dbt_model.sql

select *
from {{ ref('my_second_dbt_model') }}

Add the documentation of newly created model to schema.sql: i.e: models/example/schema.sql

  - name: my_third_dbt_model
    description: "An additional starter dbt model"
    columns:
      - name: Id
        description: 'The primary key for this table'
        tests:
          - unique
          - not_null

Enable column-level docs persistence; i.e.: dbt_project.yml

models:
  ...
  +persist_docs:
    relation: true
    columns: true

Run dbt run and observe the error

Relevant log output
No response
Environment
- OS: MacOS
- Python: Python 3.9.9
- dbt: 1.0.0

What database are you using dbt with?
postgres
Additional Context
No response

Seems related to https://github.com/dbt-labs/dbt-core/issues/2439 but in reverse.

@Fouad-Kichauat Thanks for opening, and for the clear reproduction case!
This is due to the mismatched casing for your column name: Id in your .yml file, and yet id in your model (flowing through from my_first_dbt_model):
https://github.com/dbt-labs/dbt-core/blob/f633e9936f62702a59fa661d261caaff9cefbe92/core/dbt/include/starter_project/models/example/my_first_dbt_model.sql#L14
If you change your Id to id, the issue goes away.
Better error?
One straightforward change we could make: Check to ensure that
https://github.com/dbt-labs/dbt-core/blob/f633e9936f62702a59fa661d261caaff9cefbe92/core/dbt/include/global_project/macros/adapters/persist_docs.sql#L31
That would still result in the column comment not being persisted, but it would at least avoid the "can't execute an empty query" error. Instead, it would fail silently. Is that actually better...?
Case-insensitive comparison?
This just came up over on dbt-bigquery as well: https://github.com/dbt-labs/dbt-bigquery/issues/169
For databases that retain case-sensitive names, I think it's reasonable for dbt to expect users to match case as well. For instance, on Postgres, this is possible:
jerco=# create table dbt_jcohen.my_wonky_tbl as (select 1 as "id", 2 as "ID", 3 as "Id");
SELECT 1
jerco=# select * from dbt_jcohen.my_wonky_tbl;
 id | ID | Id
----+----+----
  1 |  2 |  3
(1 row)

We could add case-insensitive comparison logic here, but then how could we handle the case above?
Update docs
My inclination is to say, our best bet is to update the docs on persist_docs, to really drive home that column names must match across yaml + sql, with regard to their casing as well: https://docs.getdbt.com/reference/resource-configs/persist_docs

Is it possible to warn when the yml contains columns which are not created by the model sql file I wonder?

Good question! Some past conversations on that theme:

https://github.com/dbt-labs/dbt-core/issues/1438
https://github.com/dbt-labs/dbt-core/issues/1570
https://github.com/dbt-labs/dbt-core/issues/2191

@jtcohen6 Thank for the fast reply!
Using the prior example and matching the exact case of the source column solves the issue for the demo code.
But in our current project it does not. To better replicate the issue we are facing, following changes need to be made to the above mentioned demo:
models/example/schema.sql
models:
  - name: my_third_dbt_model
    description: "An additional starter dbt model"
    columns:
      - name: Id
        description: 'The primary key for this table'
        tests:
          - unique
          - not_null
      - name: SecondColumn

models/example/my_third_dbt_model.sql
select id as Id,
'test' as SecondColumn
from {{ ref('my_second_dbt_model') }}

It all depends on whether you're quoting the column name or not. In Postgres, column names are lowercased by default, but they retain case-sensitivity if they're quoted.
If you change your model to quote the column names, this should now work:
select id as "Id",
'test' as "SecondColumn"
from {{ ref('my_second_dbt_model') }}

models:
  - name: my_third_dbt_model
    description: "An additional starter dbt model"
    columns:
      - name: Id
        quote: true
        description: 'The primary key for this table'
        tests:
          - unique
          - not_null
      - name: SecondColumn
        quote: true
        description: 'Another column'

To be clear, I don't recommend this. It's all much simpler if you lowercase (and snake case) column names across the board:
models:
  - name: my_third_dbt_model
    description: "An additional starter dbt model"
    columns:
      - name: id
        description: 'The primary key for this table'
        tests:
          - unique
          - not_null
      - name: second_column

select id,
'test' as second_column
from {{ ref('my_second_dbt_model') }}

Thank you for the many clarifications!! We can close the issue now.


Tasks error

I think a bit of example code might have been left in the App Store version of the app, as in the logs I can see requests requesting (and failing) to go to example.com

Oops forgot to assign the bug tag to this one 😅

Hey @SoCuul, this is actually intentional.
I'm replacing the actual URL of the instance with example.com, so that when people share logs they don't leak their instance URL accidentally.
The reason this "error" pops up (as far as I know) is that when a view appears, it triggers a request to load some data. When the view disappears, the task that was launched for this is still active, and gets canceled by SwiftUI. The logging picks up these errors. I guess I should probably suppress these errors in the logs.

Maybe for clarity don't remove the logs, but just put something like censored-by-swiftpaperless instead of example.com

I'm working to suppress the cancellation errors as much as possible now, since they're not actually errors.
Other than that, I'll close this issue for now.


build: update fastapi version compatibility

Compatible with higher versions of Fastapis.

@drochetti Can you review it?

I would be interested in having this too

Thanks for the PR @Undertone0809 !
https://github.com/fal-ai/fal/pull/167 fixes this along the way.


construction/metadata to return actorID

construction/metadata endpoint needs to return everything that is needed to construct a transaction. We need to add destinationActorId to the response so that we can pass that in when construction transaction
https://github.com/Zondax/rosetta-filecoin-lib/blob/master/construction_api.go#L38

Ok, this should be easy, I'll add destinationActorId to the response inside the metadata map


refactor: Introduce - removes the improper dependency on the thread (part 2)

service was fully rewritten

Depends on https://github.com/hyperledger/aries-framework-go/pull/1252
Part of #1157
Signed-off-by: Andrii Soluk<EMAIL_ADDRESS>

@soluchok @troyronda @llorllale @fqutishat @Baha-sk May be these refactor need to be done in steps (may be API by API - supporting new/old simultaneously or something). I'm but skeptical of deleting the client and BDD test files as a whole and then adding it. It's hard to see what has changed. This refactoring looks similar to one we are having with KMS.

@soluchok maybe it would be better to disable files in this PR with a build constraint rather than deleting in this one and re-creating in the next one?


nothing provides cuda-command-line-tools-libnvtoolsext needed by tensorrt-6.0.1+1-r0.armv8a_tegra210

--> Starting dependency resolution
--> Finished dependency resolution
Error:
Problem: conflicting requests

nothing provides cuda-command-line-tools-libnvtoolsext needed by tensorrt-6.0.1+1-r0.armv8a_tegra210
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

ERROR: Logfile of failure stored in: /yow-lpggp31/prodigu/lts19-jetson-nano/build/tmp-glibc/work/jetson_nano_qspi_sd-wrs-linux/wrlinux-image-std-sato/1.0-r1/temp/log.do_rootfs.18906

I see in "../layers/meta-tegra/recipes-devtools/gie/tensorrt_6.0.1-1.bb"
`the dependency very clearly
RDEPENDS_${PN} += "libstdc++ cudnn cuda-cublas cuda-cudart cuda-command-line-tools-libnvtoolsext tegra-libraries libglvnd"
``

I am investigating

I found that the package is not being built:
prodrigu@yow-lpggp3:/yow-lpggp31/prodigu/lts19-jetson-nano/build/tmp-glibc/work/armv8a_tegra210-wrs-linux/cuda-command-line-tools/10.0.326-1-r0$ find . -name *.rpm
./deploy-rpms/armv8a_tegra210/cuda-command-line-tools-doc-10.0.326+1-r0.armv8a_tegra210.rpm
./deploy-rpms/armv8a_tegra210/cuda-command-line-tools-10.0.326+1-r0.armv8a_tegra210.rpm
./deploy-rpms/armv8a_tegra210/cuda-command-line-tools-libcupti-dev-10.0.326+1-r0.armv8a_tegra210.rpm
./deploy-rpms/armv8a_tegra210/cuda-command-line-tools-dev-10.0.326+1-r0.armv8a_tegra210.rpm
./deploy-rpms/armv8a_tegra210/cuda-command-line-tools-libcupti-10.0.326+1-r0.armv8a_tegra210.rpm
./deploy-rpms/armv8a_tegra210/cuda-command-line-tools-dbg-10.0.326+1-r0.armv8a_tegra210.rpm

Yeah, looks like another hard-coded /lib reference in the cuda-command-line-tools recipe, preventing the package from getting created.

I've also cherry-picked the fix into the zeus-l4t-r32.3.1 branch.


scriptRoot doesn't work (or documentation needs clarifying)

Describe the bug
No matter what I set scriptRoot config item too, download of scripts from ioBroker server puts them in top level project folder.
To Reproduce
Change scriptRoot to something. It is ignored.
Expected behavior
I have the following folder:
.../src/myProject
.../src/myProject/someJunk
.../src/myProject/someOtherJunk
.../src/myProject/ioBrokerScripts

I want to open folder .../src/myProject in vscode and browse around things. In that folder I have a .iobroker-config.json file. In that file I have the setting   "scriptRoot": "iobroker-scripts".
According to the documentation when I download from ioBroker the scripts should end up in .../src/myProject/ioBrokerScripts but instead, they end up in .../src/myProject. I have tried various folders but none seem to work - scripts always end up in top level folder.
Version information (please complete the following information):

Extension version: v0.13.1
VS Code version: 1.63.2
ioBroker admin version: v5.2.3
ioBroker nodejs version: v12.22.5
ioBroker javascript adapter version: 5.2.18

Thanks for the nice description of the bug. I will try to reproduce it, because it's working fine for me.
From your description it seems you've done everything correct. Would it be possible for you to share your .iobroker-config.json?
A config working for me looks like this:
{
  "ioBrokerUrl": "http://iobroker",
  "socketIoPort": 8081,
  "scriptRoot": "iobroker-scripts",
  "adminVersion": "admin5"
}

I was able to reproduce the bug. It never happened to me, because I've got all my scripts in sub directories and only scripts in the root directory were affected.
Please let me know if the just released version 0.13.2 fixes your problem.

Yup - that's better. Thank you for the quick response :smile:


No frames received on Ubuntu 22 for D435

librealsense
2.55.1 RELEASE

OS
Linux

Name
Intel RealSense D435

Serial Number
241222077177

Firmware Version
<IP_ADDRESS>

Advanced Mode
YES

Camera Locked
YES

Usb Type Descriptor
2.1

Product Line
D400

Asic Serial Number
241223121250

Firmware Update Id
241223121250

Dfu Device Path

Please provide a description of the problem
Hi, I followed the instruction to install sdk, but The viewer shows no frames received, no other errors.
And also I followed this link installed  dependencies

Hi @heyunwang1  Please try unplugging the micro-sized end of the USB cable from the side of the camera, reversing the connector's orientation and plugging it back into the camera (USB-C cables are two-way insertion at the micro-sized end).
Does doing so make any difference?

Hi, there are no differece
and also I try to use cheese to open

So the camera is detected and displayed in the side-panel of the RealSense Viewer but you receive No frames received when enabling streams?  Which stream is it (depth or RGB, or both) that displays this message, please?
Does the Viewer behave the same if you run it in sudo admin permissions mode with sudo realsense-viewer

It also shows No frames received for both with sudo realsense-viewer

Are you using the official 1 meter long USB cable supplied with the camera or a longer cable of your own choice?
If you are using the official cable, is the camera accessible with Cheese if you follow the procedure below:

Uninstall the SDK packages with this command:

dpkg -l | grep "realsense" | cut -d " " -f 3 | xargs sudo dpkg --purge
2.  Re-install the SDK from source code using the libuvc backend installation method at the link below.
https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md

Now the software can basically receive a picture in 20 seconds.
“20:01:19 [Error] /home/drt/librealsense_build/librealsense-master/src/uvc/uvc-streamer.cpp:105 - uvc streamer watchdog triggered on endpoint: 132”
“20:01:17 [Warn] /home/drt/librealsense_build/librealsense-master/src/libusb/messenger-libusb.cpp:42 - control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11”
“20:04:30 [Error] /home/drt/librealsense_build/librealsense-master/src/ds/ds-options.cpp:93 - Asic Temperature value is not valid!”
For cheese, it does not report an error, but its screen is black

The control_transfer returned warning indicates a communication problem between the camera and computer, typically with the USB system (a problem with the USB port or the USB cable).
The Asic Temperature value is not valid! message is not important.
Do you have a different USB port that you can try the camera in?

Thank you, I will buy a new cable tommorow

Case closed due to no further comments received.


[yaml] fix yaml label appending

Fix issue where user labels get overridden by manual 'yaml' label.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @robertwb

The lint error looks pre-existing.


SSM by region for outside GAMBLR (core) usage

This new helper function allows plotting functions such as ashm_multi_rainbow_plot and ashm_rainbow_plot to be run in stand-alone mode, i.e not relying on get_ssm_by_region to subset a MAF to regions of interest and by this, eliminating CORE GAMBLR functionality as a dependency for this package.

Are you planning to delete those functions that don't do anything? I suspect socketWrite and test_glue can both be dropped. There are possibly others

The socketWrite is used in the view_mutation_igv  and make_igv_snapshot functions of the utilities.R (which will probably become one of the GAMBLR.utils functions), but the test_glue can safely be dropped 💯


Feature/99 custom measure 2

Closes #99
Added functionality to create custom measure.

LGTM, as I said above, I think Measurements.scala can be much more improved, but I'm happy to do it here: #104 so that you can merge this one. I'll leave it up to you :)

I feel like we keep refactoring the same things over and over again. (And more to come - multi column support etc.) :)

LGTM, as I said above, I think Measurements.scala can be much more improved, but I'm happy to do it here: #104 so that you can merge this one. I'll leave it up to you :)

I feel like we keep refactoring the same things over and over again. (And more to come - multi column support etc.) :)

I agree, because some things are just changing and thus 'older' data model is not perfectly suitable anymore :D

I have removed outdated JaCoCo code coverage post as they were for another version of Scala - change in title.
So removed to avoid confusion.


Add NPM test scripts for different browser/OS environments

Description of the problem this pull request solves
A tool is only as good as its supported environments: we should be testing
Lyra in as many browsers as possible.
For development purposes, there are now two watch-mode karma script aliases:

npm run test:dev will spin up a karma watcher that runs tests in PhantomJS
npm run test:chrome will do the same but use a captured Chrome instance,
which can be useful for debugging purposes

For acceptance testing, we now have two platform-specific aliases that run
Karma against all the browsers that a developer might reasonably have installed
on their development OS of choice:

npm run test:osx runs PhantomJS, Chrome, Firefox, and Safari
npm run test:win runs PhantomJS, Chrome, Firefox, and IE

Functional test +1 for osx.  I have to update everything on my windows machine tho to functional test  npm run test:win

Just verified npm test:win in WIndows 10, and added custom launchers for IE9 and IE10 emulation modes (not sure how accurate they are). At present there is no official karma launcher for Edge.

Going to merge this and if anything weird comes up with win later, we can fix it


The code is not formatted, but the actual returned code is formatted. However, it is not displayed in a formatted way.

The code is not formatted, but the actual returned code is formatted. However, it is not displayed in a formatted way.

Hi, could you try upgrading the plugin to the latest version(2.0.0) and see if the problem still exists?

where i can get latest version(2.0.0) source code thank you

The source code for v2.0.0 isn't available at the moment.
The latest version can be found here.


Add rule "TODO" tags should be handled

Fixed in PR https://github.com/iwarapter/sonar-puppet/pull/25

PR Merged


Fix failing tests

@ludoo I think this one fixes the concurrency issue. I did a few tests and it seems to work. Can you give it a try locally?

This is nice. I'm now entirely sure the additional complexity is worth a 25% reduction in test runs (5m40 vs 7m40 for modules), but if you think it is, +1 from me.
We will then need to periodically: a) recheck all providers used across the repo and recompile a versions file, b) bump minimum versions in it. Not a big deal of course, so up to you.


[feat]: add support for microsoft rush monorepo

Feature description
Shadcn CLI does not support projects which are managed by @microsoft/rush mono repo.
Rush mono repo could be configured to use either npm, yarn or pnpm but it has its own way of managing dependencies
(i.e  npm install , yarn add or pnpm add are not used diectly.)
Problem:
Because Rush is managing the dependencies differently, regardless of the Rush package manager config, none of the following Shadcn CLI commands works:
npx shadcn@latest add button
# or
npx shadcn@latest add button
# or
pnpm dlx shadcn@latest add button

running Shadcn CLI to add a component will cause error at installing dependencies step:
using npm

using pnpm

Proposed Solution
Shadcn CLI to detect if project is managed by Rush, and use rush cli to install dependencies.
(Shadcn CLI currently supports npm, yarn, pnpm and bun )
Affected component/components
CLI
Additional Context
Additional details here...
Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues and PRs

I am not sure how features are prioritized , but I am going to open a pull request from my fork where I made this working with Rush.
I believe my changes could make it easier to add other package managers down the road, for instance https://github.com/shadcn-ui/ui/issues/5529.


C++ OpenTelemetry Plugin

Is your feature request related to a problem? Please describe.
There is an OpenCensus plugin that collects metrics and spans with internal gRPC APIs. Would the project be open to having a parallel OpenTelemetry plugin?
Describe the solution you'd like
An OpenTelemetry plugin similar to the OpenCensus one.
Describe alternatives you've considered
Building a plugin externally doesn't seem possible, given the required APIs are private.
Additional context
We maintain a framework that wraps gRPC C++, called Arrow Flight. Right now we provide OpenTelemetry support as a middleware in our layer (based on this example), but it some cases users need more insight into the performance of gRPC itself, which is a total black box right now.

Hi, we are preparing a roadmap for this. Please stay posted! :)

Is there any update on the roadmap?

It appears some of this was done in #33650. Are there plans for further work? Is the call tracer API meant for public use?

As noted at https://github.com/grpc/grpc-go/issues/6305, it was announced on 2023-05-01 that OpenCensus is being sunsetted and also that OpenTelemetry now has feature parity with it for C++. We would love to have some more information about the timeline for OTel support in gRPC C++. Thanks

It looks like the current implementation records metrics, but not spans. And it seems OpenCensus is still artificially hardcoded into ServerContextBase, so other implementations can't start a span and share it with the RPC handler.

It's been another 6 months. @yashykt is there any update for when OpenTelemetry support might happen, or if gRPC exposes enough hooks to do this ourselves? (The interceptor mechanism is insufficient since I don't see a way to pass a span from the interceptor to the RPC handler.)

Alternatively would you be open to an external PR for this @yashykt ?

Sorry for not posting an update here earlier!
The gRFC for OpenTelemetry metrics is available at https://github.com/grpc/proposal/blob/master/A66-otel-stats.md
This was implemented in gRPC C++ and has been available since 1.61.x

The gRFC for OpenTelemetry tracing is in progress in https://github.com/grpc/proposal/pull/389. Please take a look. It'll be finished in the coming quarters.
There are some additional metrics also being designed in https://github.com/grpc/proposal/pull/421 and https://github.com/grpc/proposal/pull/419. These might be of interest as well.

Thanks for the context.
It seems like plugins/call filters are able to propagate state to RPC handlers and/or guarantee that they run in the same thread as the RPC handler? (Since the OpenTelemetry current span is a thread local.)

It seems like plugins/call filters are able to propagate state to RPC handlers and/or guarantee that they run in the same thread as the RPC handler? (Since the OpenTelemetry current span is a thread local.)

Is your query around how gRPC will propagate contexts from the application to be used as the parent context for the RPCs? As far as I see it, there are two ways we can support this -

Explicitly provide a way to set the OpenTelemetry context. A similar thing was done for OpenCensus - https://github.com/grpc/grpc/blob/a19e01c4fd947ed5f4cc4a91412c4cbf029d2526/include/grpcpp/client_context.h#L373
Internally make sure that we propagate the parent OpenTelemetry context to the internal call tracers so that we preserve the parent context even when there is a thread hop.

Yes, or more specifically: how can we propagate state (like context) from an interceptor (or other mechanism that gets to run before/after every call) to the RPC handler itself?
I had seen that OpenCensus was privileged, if there is no way to do things like this besides modifying gRPC itself that is extremely unfortunate. (For instance, another thing we're trying to do is provide a session cookie, so we have to have some way of communicating the session from an interceptor to the RPC handler...hardcoding won't work since I doubt we'd be able to upstream that to gRPC.)

Yes, or more specifically: how can we propagate state (like context) from an interceptor (or other mechanism that gets to run before/after every call) to the RPC handler itself?

This has come up before in various contexts. We've thought of working on a context propagation mechanism that does not use metadata.
The C++ interception API is also going to go through an overhaul so maybe we can consider this @ctiller

That's great news! We've been struggling with a pile of hacks because of that and an interception API that is able to pass context to the RPC handler somehow (same as in Java and other gRPC implementations) would be much appreciated.


Azure Security Center - Update Security settings API version

All SDK Contribution checklist:
Swagger update PR - https://github.com/Azure/azure-rest-api-specs/pull/14374
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

Hi @m-nash,
Is there a way to only update a specific swagger update?
I did a small change in one API and I wish to update the SDK just for this one change, is it possible to do it?
thanks,
Gal


Software Versioning

As of now I dont have a system of numbered versions for the software. Luckily bidscoin provides an example on how to do this; I just have not had my mind around it. The versioning could actually be another target for the final gsoc deliverable (it is quite important, i hope is not hard to implement). Guess this would be version 0.1 of sovabids hehe.
Also, there is the idea of flagging bad versions, as @civier  proposed:

I don't know if you're familiar with fMRIprep, but it's the most popular software to do pre-processing of functional MRI data. In any case, it has a nice function that allows the developers to flag a bad version (i.e., a version that was distributed, but found to be problematic retrospectively), such that the users will see a warning message when trying to use it.

For example, conversion 20.2.1 was flagged, and when trying to use it, it displays the following:
You are using fMRIPrep-20.2.1, and a newer version of fMRIPrep is available: 20.2.3.
Please check out our documentation about how and when to upgrade:
https://fmriprep.readthedocs.io/en/latest/faq.html#upgrading
WARNING: Version 20.2.1 of fMRIPrep (current) has been FLAGGED
(reason: Functional outputs in standard space can be wrong depending on the original data's orientation headers - see https://github.com/nipreps/fmriprep/issues/2307).
That means some severe flaw was found in it and we strongly
discourage its usage.

I am a big fan of semantic versioning :) https://semver.org/
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards compatible manner, and
PATCH version when you make backwards compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Hmm so if currently lets say we are at sovabids 0.X.Y, when we launch the new rules file format it would be already sovabids 1.X.Y ? Im a bit scared of having a '1' already hehe

As per what the website says:

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes.

Maybe we should stay on the 0.X.Y for now, since it is quite experimental still. If the final GSoC is sovabids 0.1 , the implementation of the new rules file would be sovabids 0.2

I ended up using versioneer and to manage the semantic version one cause use git tags . Im still getting around the concept but as of now it works!
I decided to label the current version as a prerelease (alpha software). So I added an 'a' to the end
So in general what I understand is that I use git tag to comply to semantic versioning and versioneer manages the more detailed stuff through its system.
If you go to https://sovabids.readthedocs.io/en/latest/ you will see the version at the upper left corner.
Closing this, but if you have any feedback on this , let me know.


Updated requirements.txt for python module 2

Issue #, if available:
Description of changes:
requirements.txt was outdated leading to multiple errors when trying to run docker image.
The fix was to change version of flask to 1.1.4 and also to add markupsafe too.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Ping me if you have any questions or comments 😄