Handle auth

Hi :)
From what I see, the auth that's defined in RPCContext is parsed but not checked, meaning that any user on a client machine has full access to the data, which might be a security issue.
Is it possible to add that functionality?
Alternatively, exposing the auth (or the context) to the different methods in the NFSFileSystem so that implementers can be responsible for the checks is also a possibility.
Thanks,
Liran

since this is is meant entirely for localhost operation, acting like a FUSE mount, I didn't see significant needs for auth. Perhaps if its a mount running on a multi-user environment? It is possible to implement, but there is a decent amount of work in other parts as well as handle the auth correctly I think.

Can I know more about your needs here and what you need auth for?

I'm working on a central server that will host the nfs service, the data is stored on a custom storage backend so this project suits the needs pretty well.
Clients connect to it when they need to access the files.
The clients may have other services running so limiting access can be nice although not a deal breaker.
I made a few changes to see if I can expose the context to the NFSFileSystem implementation (using tokio::task::LocalKey) so auth may be handled by it. As a proof of concept it works.

Got it. Happy to accept any improvements!


jQuery Template Bug - & instead of $

https://github.com/bridgedotnet/Frameworks/blob/master/jQuery2/Ajax/HelperFunctions.cs
Hi I have reproduced an issue I am seeing using the Param function in jQuery
http://live.bridge.net/#9f62a426ea8b07d33d53
var url = &.param(parameters);
instead of
var url = $.param(parameters);

https://github.com/bridgedotnet/Frameworks/pull/31

This is most likely related to bridgedotnet/Bridge#796.

It looks like a straight forward case of the wrong text inside the Template Attribute
[Template("&.param({0})")]

The pull request (#31) has been merged. The fix will go to the next Bridge.jQuery release - 2.9.0.


libp2p-next

Supersedes https://github.com/paritytech/substrate/pull/5066. This PR upgrades substrate to libp2p-0.17. The following are the main libp2p changes which are visible in substrate:

Adapt to https://github.com/libp2p/rust-libp2p/pull/1440 and https://github.com/libp2p/rust-libp2p/pull/1519.
Adapt to https://github.com/libp2p/rust-libp2p/pull/1472.
Adapt to https://github.com/libp2p/rust-libp2p/pull/1467.

https://github.com/libp2p/rust-libp2p/pull/1440 and https://github.com/libp2p/rust-libp2p/pull/1519
Overview
As described in the libp2p PRs, the underlying changes are primarily in libp2p-core. Realistically, a second connection to the same peer only occurs if two peers connect to each other "at the same time". As a side-effect, existing connections are also no longer closed in favour of new ones, which addresses https://github.com/paritytech/substrate/issues/4272.
Details

The enabled/disabled status is the same across all connections, as decided by the peerset manager.
send_packet and write_notification always send all data over the same connection to preserve the ordering provided by the transport, as long as that connection is open. If it closes, a second open connection may take over, if one exists, but that case should be no different than a single connection failing and being re-established in terms of potential reordering and dropped messages. Messages can be received on any connection and thus two peers which happened to connect to each other simultaneously may each a different connection for sending data.
The behaviour reports GenericProtoOut::CustomProtocolOpen when the first connection reports NotifsHandlerOut::Open.
The behaviour reports GenericProtoOut::CustomProtocolClosed when the last connection reports NotifsHandlerOut::Closed.

In this way, the number of actual established connections to the peer is an implementation detail of the network behaviours. As mentioned before, in practice and at the time of this writing, there may be at most two connections to a peer and only as a result of simultaneous dialing. The network service even configures a hard limit of 2 connections per peer. However, the implementation in principle accommodates for any number of connections.
Noteworthy
During intermediate testing with the (by default disabled) integration tests test_consensus, test_sync and test_connectivity it was revealed that when run in release mode these tests were very often failing, with the common symptom that the last node to start in a round of testing would often see no other peers (i.e. empty DHT routing table) and thus make no progress while all the others keep on running, causing the tests to time out waiting for the problematic peer to reach a certain state. The tests are mainly using add_reserved_peer on the network to initialise the topology, however, add_reserved_peer ultimately results in a call to add_known_peer on the DiscoveryBehaviour which did not actually add that address to the Kademlia routing table, though it adds it to the user_defined peers which, when passed in the constructor of the behaviour, are added to the Kademlia routing table. I thus changed add_known_peer to also add the given address to the Kademlia routing table and that resolved the issues with these integration tests and the test_connectivity test seems to run notably faster (release mode). My current guess is that the tests were so far unknowingly relying on a timing assumption w.r.t. the initial discovery / connection setup and DHT queries in order for all peers to find each other, in particular when simultaneous connections attempts are in play, as often happens in release mode. Ultimately, the change of letting add_known_peer add the given address to the Kademlia routing table may be a patch worth extracting separately, because it does look like an oversight to me.
https://github.com/libp2p/rust-libp2p/pull/1472
Insubstantial changes to adapt to the new APIs.
https://github.com/libp2p/rust-libp2p/pull/1467
Insubstantial changes to add now necessary feature flags where there is a dependency on libp2p with default-features = false.

CC @tomaka, @twittner, @mxinden - Feel free to review at your leisure. This is obviously not mergeable until the next libp2p release but you may already want to skim the PR description.

I opened https://github.com/paritytech/polkadot/pull/963, which should fix the Polkadot compilation.

Would you mind merging master, so that we can test Polkadot with it?

Would you mind merging master, so that we can test Polkadot with it?

Just did so. For what it is worth, I already ran polkadot with it a few weeks ago, just to check that https://github.com/paritytech/substrate/issues/4272 is resolved with these changes, which seemed to be the case.

Deployed both on my Google Cloud instance (with incoming connections) around 3pm and on kusama-validator-ew4-0 around 5pm.
There are a couple warnings (notably about reserved nodes getting disconnected), but that was already the case before. In particular, comparing the logs before and after this PR, the rate of all warnings seem exactly the same.
In Grafana everything seems normal as well. The number of GrandPa notifications emitted has increased, but that is expected due to #5520.
So everything looks good to me so far. I suggest to take a look tomorrow morning again and if there's nothing weird happening, we merge this.

Well, the test is kind of inconclusive.
It seems that Parity's logs server has crashed during the night, and my Google Cloud node stopped shortly after I posted the previous message without me realizing :man_facepalming:  (probably because I closed the SSH connection, forgetting that this would close the node (I'm not a devops)).
On Grafana, however, everything looks normal.

I'd still be in favour of merging.
@twittner?

Needs a merge/rebase over master.

I think the test is failing because of the unused import warning.

warning: unused import: channel::mpsc
--> client/network/src/service.rs:39:27
|
39 | use futures::{prelude::*, channel::mpsc};
|                           ^^^^^^^^^^^^^
|


Add tap, tapLeft and tapBoth to Either

Handy functions commonly used for logging.

Hey @spebbe any chance you can have a look at this?


SSR prefetching (hydration/dehydration) with NextJS and client side routing to the same route.

Describe the bug
Not sure if this is a bug or if I'm doing something incorrectly but when using SSR hydration/dehydration prefetching based on the docs, the first request will set initial data for a query correctly, but when routing to the same route but with a different param the cache isn't updated with the new prefetched value.
To Reproduce
Steps to reproduce the behavior:

Go to https://ctwew.sse.codesandbox.io/set1
Open up the dev tools and see that the data returned from getServerSideProps and the data displayed is the same.
Click on toggle set, this will perform a client side route change and will call getServeSideProps as an api call.
You will notice that the data onscreen will still have "dataSet: set1", the url will be "/set2". However if you check the console you will see that the data contains "dataSet: set2"

Expected behavior
I would expect the data from getServerSideProps to update the cache and the components using the data to be rerendered with the correct values.
Screenshots
https://codesandbox.io/s/amazing-paper-ctwew?file=/pages/[dataSet].js
Data returned from getServerSideProps on the initial page load.

Data returned from getServerSideProps on the route change.

Desktop (please complete the following information):

OS: macOs
Browser: chrome
Version: 2.13.1

Additional context
I did notice the force option for the prefetch query options and have tried it with "force: true" but that didn't work either.

@Ephem might know more about this while I noodle on it.

@callumbooth Great writeup, and wow you found this quickly, I realized it myself only a few hours ago. I'll explain the cause it in detail when I'm at a computer.
@tannerlinsley This is the updatedAt-thing I mentioned on Discord.
I do have a fix in mind, will try to find the time to implement it asap.

Awseome!

Okay, so the slightly longer version/explanation of this is that there are two prerequisites for this to happen:

Query with same key gets fetched twice
The second fetch comes in through a hydrate

So to be clear, if that example had the url in the query-key, the first toggle would succeed (because the key with /set2 is different from 1), but on the second toggle back to one any more recent data from the server would not enter the cache. I'm pretty sure this is what that reproduction was meant to show, but I want to make this part clear for anyone reading along.
What the above means is in essence that this mainly effects Next.js getServerSideProps.
The reason for the bug is that when hydration was first started to be implemented, we didn't hydrate updatedAt or base any staleness etc on that. This meant that the only safe thing to do was to never hydrate any queries that were already in the cache, since we didn't know if queries coming in via a hydate contained newer data or not. When this changed and updatedAt became a thing, I kind of forgot that this was a problem we had in the first place and forgot to implement it. 😬
So the fix is to make the default behavior that when hydrating, we look at updatedAt and if the data in the query that is being hydrated is newer, we overwrite the existing query in the cache.

:tada: This issue has been resolved in version 2.15.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

I can confirm the issue is fixed, thanks for pushing a solution so quickly.


Fix/run lit action pkp base

WHAT

Fixes errors when attempting to sign with pkp's through the pkp-base implementations from attempting to use both auth sigs and session sigs when invoking executeJS which now only allows on of the two authentication options.

Testing

Tested with email sms session signatures where it was observed to successful sign a message with a provided session sigs for authentication context.

See here for more context on the bug

@sarahzdev @joshLong145 need review on new changes:
https://github.com/LIT-Protocol/js-sdk/pull/125/commits/10b367db3bba0c194bca956ce88db7af09102ee8
https://github.com/LIT-Protocol/js-sdk/pull/125/commits/10b367db3bba0c194bca956ce88db7af09102ee8

@sarahzdev @joshLong145 need review on new changes:
10b367d
3556092

These look good on my end.


Write unit tests for CGPoint+Extension.swift

Add unit tests
Description

write unit tests for CGPoint+Extension.swift
clean up formatting on CGPoint+Extension.swift

Motivation and Context
There are virtually no unit tests for this framework. Having unit tests in place will make adding and altering code to the codebase exponentially easier.
How Has This Been Tested?

No breaking changes, just unit tests.

The net result will be dramatically more maintainable code where developers can refactor without fear.
Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Non-functional change (Updating Documentation, CI automation, etc..)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

Thank you! Unit tests are indeed very important and this will be a great help soon when CI will be set up for this project.


release 0.2.0

alpha channel is kept to force the migration to the new version of the operator.

/label docs-approved
/label px-approved
No docs impact as the OLM channel didn't change.

/retest

/lgtm

/label cherry-pick-approved

/label qe-approved


micrortps_bridge: uorb multi-topics don't work

Currently, uorb multi-topics (e.g. optical_flow_raw, vehicle_vision_position, etc.) don't work with the micrortps_bridge.
https://github.com/PX4/Firmware/blob/master/src/modules/micrortps_bridge/CMakeLists.txt
related to https://github.com/PX4/Firmware/pull/8495. But I guess we need to fix it anyways.
@dagar I saw you've worked on it. Is that something you could look into?

I'm not that familiar with FastRTPS itself, but at a glance it doesn't look like the concept of multi-topics exists. I think we'll need to treat them like individual topics (sensor_accel_0, sensor_accel_1, etc), but it could be done automatically.
The manually maintained message ids (https://github.com/PX4/Firmware/blob/master/msg/tools/uorb_rtps_message_ids.py#L5) are already a problem. So the entire thing needs to be considered.
Should we discuss this on the messaging working group call?

Should we discuss this on the messaging working group call?

Sure. When's that?

It's on Thursday, although I've never attended.
https://dev.px4.io/en/contribute/#calendar
The big overall issue that's not at all clear to me is how we need to handle message versioning and ids when you start using them outside of Firmware.

@santiago3dr can we please keep this open? This is something that still needs to be tackled.

@TSC21 I believe you'll need to explicitly handle the instances as separate topics.

@TSC21 I believe you'll need to explicitly handle the instances as separate topics.

Yes I know. Just didn't have time to implement this yet.

Solution in https://github.com/PX4/Firmware/pull/12137

Solved already.


fix(ScriptjsLoader): Fix setState warning

Make the callback from scriptjs a no-op when unmounting the component.
There was a corner case where the component would be unmounted while scriptjs was doing its thing. The callback would then call setState, thus triggering a warning from React.

Released v5.1.1


Support mTLS when connecting to docker registry

Description
Is it possible to support a Docker registry that is hosted behind a mTLS endpoint? My webbrowser does use my certificate towards this artifactory instance to do the mTLS auth.
Commandline I'm not sure if this can be resolved outside of the cosign binary, but it might make sense to add support for mTLS authentication.
See here the output on a cosign command. Most probably as this artifactory instance requires an mTLS certificate.
$ COSIGN_DOCKER_MEDIA_TYPES=1 cosign verify-attestation --key cosign.pub docker.artifactory.my-enterprise.com/my-example-image@sha256:f720336cb5dbdd42994c4283b7c377b5e45f25371cb57aeadd9bcae5b1ca914c

Error: Get "https://docker.artifactory.my-enterprise.com/v2/": remote error: tls: handshake failure
main.go:46: error during command execution: Get "https://docker.artifactory.my-enterprise.com/v2/": remote error: tls: handshake failure

Do you have any examples of other CLIs that do this right?

Nope I don't. I actually do realize mostly the workaround is to go via VPN which does not require mTLS in our case. I do realize now not many CLIs might be supporting this, but I can imagine the demand for this might increase. Take for example the ease of mTLS using spiffe and spire nowadays.
I assume support via a config file should be best to not bloat the CLI with a whole bunch of new options. E.g. to read the certificate from the OS credentials store.

Found this: https://smallstep.com/hello-mtls/doc/client/curl
Might be a lead on how this could be supported.

Also found here a tutorial walking through an implementation. Would be happy to contribute, we just need to agree on a way to pass the client cert/ca for the mTLS connection.

I was evaluating (and sadly have to pass on) cosign, when I encountered this mTLS limitation.  I was encouraged in the slack channel to register my request for this feature.
On the CLI, it might've been noted that curl has solutions for this already...clearly cosign would need to disambiguate between the registry ca/cert/key and the signature ca/cert/key - but I can see ways to do this.
Thanks, folks.


Import cycles; unhandled returned promises; misc

Using this bug to document misc nit-picky things I found in the typescript code that I thought I could clean up:
At the moment, cdn/elements/dialog.ts imports from cdn/utils.ts which imports cyclicly from cdn/elements/dialogs.ts.
The same cyclic import situation exists between cdn/utils/ts and:

cdn/elements/menus.ts
cdn/elements/pages.ts
cdn/elements/snackbars.ts

Even though vite / typescript / etc handle cyclic imports, its generally not recommended for various reasons (from our friend chatgpt):

Cyclic imports in TypeScript (or any programming language) are generally not recommended due to several potential issues that can arise, affecting both the functionality and maintainability of your codebase. Here’s why:

Unpredictable Behavior

•	Initialization Order Issues: When two or more modules depend on each other, the order in which these modules are initialized can become unpredictable. This can lead to situations where one module tries to access another module that hasn’t been fully initialized yet, leading to undefined values or runtime errors.
•	Incomplete Module Imports: In a cyclic dependency, when Module A imports Module B, and Module B imports Module A, one of these modules may not be fully loaded when the other tries to use it. This can cause incomplete or incorrect behavior in your application.

Maintenance Complexity

•	Harder to Understand: Cyclic dependencies create a web of interdependencies that can be difficult to understand and debug. It can be challenging to track down where issues are coming from, especially in a large codebase.
•	Tight Coupling: Cyclic dependencies often indicate that your modules are too tightly coupled. This makes the code harder to maintain and refactor, as changes in one module can ripple through the cycle, leading to unexpected side effects.

Code Smell

•	Design Flaw Indicator: Cyclic dependencies often point to a flaw in the design of your application. Typically, it suggests that your modules are not sufficiently decoupled, and your application architecture might benefit from a refactor to better separate concerns.

Tooling and Compilation Issues

•	Compilation Errors: TypeScript and other transpilers or bundlers can sometimes struggle with cyclic dependencies, leading to compilation errors or warnings. While TypeScript’s module system can handle many cases, it’s not always reliable, especially as the complexity of the cycles increases.
•	Circular Dependency Warnings: Many tools, like Webpack or Rollup, will warn about circular dependencies, indicating that the code may not behave as expected.

Increased Cognitive Load

•	Difficult Debugging: Debugging cyclic dependencies is more complex because of the intertwined nature of the modules. Developers need to consider multiple modules simultaneously, which increases cognitive load.
•	Unexpected Changes: Refactoring or making changes in one module can have unexpected side effects on others due to the cyclic nature of the imports, making even minor changes risky.
How to Avoid Cyclic Imports

Refactor Code: Break down large modules into smaller, more focused modules with well-defined responsibilities. This can help to reduce or eliminate the need for cyclic dependencies.
Use Dependency Injection: Instead of importing a module directly, consider passing dependencies as parameters to functions or constructors. This can help decouple the modules.
Use Interfaces or Abstract Classes: Sometimes, introducing an interface or abstract class can help break the cycle by reducing direct dependencies between concrete implementations.
Reorganize Module Structure: Sometimes simply reorganizing where modules are located can help avoid cyclic dependencies. Group related modules together in a way that reduces interdependence.

In summary, cyclic imports in TypeScript are not recommended because they can lead to unpredictable behavior, make the code harder to understand and maintain, indicate design flaws, and cause issues with tooling and compilation. It’s generally better to refactor your code to avoid these kinds of dependencies.

All we need to do is move the run() function out of cdn/utils.ts and put it into cdn/beer.ts file, and the cyclic imports problem gets resolved.
In cdn/beer.ts in the function onClickElement() we see the call to the run() function. The function returns a Promise object that is not handled by the caller such as by adding a chained .then() call to the return value of run(). It can become difficult to understand to the person reading this code about whether .then() is missing because the original author of that function forgot it, or whether he/she intentionally omitted it. One way to make this clear to the reader is by simply adding a void in front of the run(...) method call indicating that not handling the returned Promise is an intentional decision. This issue is found in a few different places in the code.

Merged, thanks!


With support for .Net 3.1 ending tin 6 months, can it be migrated to .Net 6 (LTS)

.Net Core 3.1 (LTS) goes end of life on the 13th of December 2022.
To maintain support, can this project please be upgraded to .NET 6 (LTS)

Thanks @GitTorre, apologies, I hadn't spotted the net6 branch. Any ETA on when it will be ready?

Thanks @GitTorre, apologies, I hadn't spotted the net6 branch. Any ETA on when it will be ready?

No need to apologize and the branch was local until yesterday.. It's a great question! As to when it will ship, I'm hoping in the next few weeks as it will be part of the 3.2.x wave of releases (3.2.1, specifically) and there is more work to do in a few areas (unrelated to .net runtime versions). Do note that the net6.0 versions of FO and CO require SF runtime version 9.0 and higher.

Thanks @GitTorre, that explains how I missed it when I looked at the branches! That's great that your aiming for the next few weeks. Thankfully, we're already in the process of upgrading our estate to 9.0.

Thanks @GitTorre, that explains how I missed it when I looked at the branches! That's great that your aiming for the next few weeks. Thankfully, we're already in the process of upgrading our estate to 9.0.

I reserve the right to define what "a few" means :)
The plan is:
Release 3.2.0 which targets SF runtime 8.x and .netcoreapp3.1
Release 3.2.1 which targets SF runtime 9.x and .net6
Once 3.1 is obsolete, folks will need to move to .net6 and so that means SF runtime 9.x and FO 3.2.1+.
3.2.0 will be the last version of FO that targets .net core 3.1. So, folks can stay on that until they upgrade to SF runtime 9.x.
Sounds like a good plan?
...Charles

Hi Charles (@GitTorre),
That sounds like a reasonable plan to me.
Looking forward to them arriving in a "few" weeks.
Best,
Stephen


CFQUERYPARAM_REQ false positive: String in SQL Server XML function

...
UPDATE
					Something
				SET
					taskXML.modify('insert #additionalMember#
									   as last into (/task)[1]')
				WHERE
					tID = <cfqueryparam value="#arguments.something.tID#" cfsqltype="cf_sql_integer">
					AND taskUUID = <cfqueryparam value="#arguments.something.tUUID#" cfsqltype="cf_sql_varchar">
...

Reports on the taskXML.modify (taskXML is a column from a preceeding IF EXISTS ( SELECT... ))

@TheRealAgentK ,  can you expand on this one a bit please.   I get a single CFQUERYPARAM_REQ because of #additionalMember# as I would expect.

Will try to create and then push an isolated test case in dev.

Ah, scratch that - I see what you mean now. Yes, that is a valid one because .modify() actually acts like an update on that XML blurb. It's another one that's not fixable with CFQUERYPARAM though and would benefit from the more fine-grained ignoring in SQL.

Thank you.

this is also triggered when the case of the  and  tags don't match, which is only stylistically messy but still valid

Hey @zspitzer - can you provide a (couple of) test samples for us?

here's a simple test case (attached too)
<cfset user_id=1>
<CFquery name="users" datasource="dsn">
SELECT 	user
FROM 	users
where 	user_id = <CFqueryparam value="#user_id#" cfsqltype="CF_SQL_NUMERIC">
</CFquery>
java -jar .\CFLint-1.2.0-all.jar -folder . -stdout -text
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
Issue
Severity:WARNING
Message code:CFQUERYPARAM_REQ
File: queryparam_req.cfm
Column:0
Line:5
Message:<cfquery> should use <cfqueryparam/> for variable 'user_id'.
Variable:'user_id' in function:
Expression:<CFquery name="users" datasource="dsn">
SELECT  user
FROM    users
where   user_id = <CFqueryparam value="#user_id#" cfsqltype="CF_SQL_NUMERIC">
</CFquery>
Total files:1
Total lines:7
Issue counts:1
CFQUERYPARAM_REQ:1
Total issues:1
Total warnings:1
queryparam_req.cfm.txt

done #380


TaskCanceled exception

On your bitbucket.org page you had an issue open where internal exception "TaskCanceled" was being triggered sometimes. I'm currently experiencing that issue with some formulations of queries. Is that issue still being tracked/worked on?

I'm having this problem as well. I have a web application,and I'm using a singleton instance for all requests (should be thread safe), but when i perform simultaneous transactional requests, I get this exception.
I've tried creating several instances per request, but it seems transaction management is local to each client, so transaction nesting doesn't work, as different clients will try to commit different transactions.

This is basically always a timeout. Do you know that those queries are actually capable of finishing within a reasonable period?

Yeah. I basically ran into two scenarios, when I perform several queries using transactions:

If I use only one instance for all web requests, when I try to perform two transactional operations simultaneously, there's a very high probabilty that one of them will hang and eventually throw a TransactionAborted exception. At first I thought this could be a deadlock at the database level, but if I use a new instance per request the problem goes away. However, in my code, I found that in some situations more than one GraphClient instance would get injected, which led me to the next problem...
If I use several GraphClient instances along a web request, I get an exception at line 104 in CypherExecutionPolicy.cs (no "Location" key found). I did some digging around and it seemed to me the different instances were trying to commit different transactions. Although I haven't been able to pinpoint what's happening exactly, I suspect the problem lies in the TransactionManager.

My solution to overcome this right now is to make sure only one GraphClient instance is injected per request at all times. There's a chance I'm overlooking something in my code which could be causing these issues, but since I get these behaviours depending only on the way I inject GraphClient instances, I'm led to believe there's some problem in transaction management.
Cheers, and keep up the good work

Hi I'll have a look, but I'm away until Monday, if you have a replicatable example that'd be great!
-----Original Message-----
From: "pedrocristinamyadlab"<EMAIL_ADDRESS>Sent: 09/10/2015 10:30
To: "Readify/Neo4jClient"<EMAIL_ADDRESS>Subject: Re: [Neo4jClient] TaskCanceled exception (#70)
Yeah. I basically ran into two scenarios, when I perform several queries using transactions:
If I use only one instance for all web requests, when I try to perform two transactional operations simultaneously, there's a very high probabilty that one of them will hang and eventually throw a TransactionAborted exception. At first I thought this could be a deadlock at the database level, but if I use a new instance per request the problem goes away. However, in my code, I found that in some situations more than one GraphClient instance would get injected, which led me to the next problem...
If I use several GraphClient instances along a web request, I get an exception at line 104 in CypherExecutionPolicy.cs (no "Location" key found). I did some digging around and it seemed to me the different instances were trying to commit different transactions. Although I haven't been able to pinpoint what's happening exactly, I suspect the problem lies in the TransactionManager.
My solution to overcome this right now is to make sure only one GraphClient instance is injected per request at all times. There's a chance I'm overlooking something in my code which could be causing these issues, but since I get these behaviours depending only on the way I inject GraphClient instances, I'm led to believe there's some problem in transaction management.
Cheers, and keep up the good work
—
Reply to this email directly or view it on GitHub.


Can't get the same MAE/OBO score as  in the paper

Thanks you for your great work and  dataset.
I have tried to reproduce the results with the default code using  pretrain weight to test. And I also tried  to transform .mp4 to .npz with tools.video2npz and  uncommented the L131 and used the dataset.RepCountA_Loader. It did improve the performance a lot, but still can't get  the same performance shown in your paper (MAE:0.44 OBO:0.29).
I finally got the test result in RepCountA with MAE:0.582 and OBO:0.284.  And I tried  to retrain the model and got the same result (MAE:0.582 OBO:0.284). It  seems to be the same as in this  issue.
My code is
import os
from dataset.RepCountA_Loader import MyData
from models.TransRAC import TransferModel
from testing.test_looping import test_loop

N_GPU = 1
device_ids = [i for i in range(N_GPU)]
os.environ["CUDA_VISIBLE_DEVICES"] = "0"
root_path = r'/mnt/disk_2/xiangwei/LLSP/videos'
test_video_dir = 'test'
test_label_dir = 'test.csv'
config = './configs/recognition/swin/swin_tiny_patch244_window877_kinetics400_1k.py'
checkpoint = './pretrained/swin_tiny_patch244_window877_kinetics400_1k.pth'
lastckpt = '/mnt/disk_1/xiangwei/TransRAC-main/transrac_ckpt_pytorch_171.pt'
NUM_FRAME = 64
SCALES = [1,4,8]
test_dataset = MyData(root_path, test_video_dir, test_label_dir, num_frame=NUM_FRAME)
my_model = TransferModel(config=config, checkpoint=checkpoint, num_frames=NUM_FRAME, scales=SCALES, OPEN=False)
NUM_EPOCHS = 1

test_loop(NUM_EPOCHS, my_model, test_dataset, lastckpt=lastckpt)

I have the same problem with you and even the result is similar (MAE:0.582 OBO:0.282)
my torch version is 1.7.0+cu110, I'm not sure if it's the problem

Could you get the same test result by loading our ckpt as #18 shown?

I have loaded your ckpt and run test.py. And it can't get the same test result

I have loaded your ckpt and run test.py. And it can't get the same test result ↳

Sorry for your question.  Refer to #18, #29, and #43.  I think you could check the input data.

Thank you for suggestion,  but i can't figure out what' wrong with input data, i have already uncommented L131  to transform mp4 to npz as #29, #43 mentioned, and loaded your ckpt as #18 suggested. Those suggetions did  work. They help me to improve my result from roughly  MAE:0.68 to  (MAE:0.582 and OBD:0.284) now, but it still can't get the same result. My colleagues ran your code on diffierent mechines, and they also can’t get the same result.

Sorry, I have no idea what went wrong in this case. The author of #43 has told me he solved the reproduce issue by uncommenting L131 as #29 and #18. Because it's the first time some researchers can not reproduce the result after following #43. I cloned this repo again and followed the [install.md]. (https://github.com/SvipRepetitionCounting/TransRAC/blob/main/install.md) to test all the code and found no bugs In the last month.
I think the step of processing data, mp4 to npz, may be the key to the problem.  And we have no test about whether the different torch versions cause trouble. ( I think it won't. XD)
Because we can not reproduce your bugs, we may not be able to provide further assistance with these bugs.

I followed all the aforementioned settings and still get MAE: 0.582 and OBO： 0.283. (pytorch 1.7.0, mmcv1.4.0, mmcv_full1.7.1 cuda 10.1), and I tested with two different machines, also repeated downloading the dataset and preprocessing the MP4 to npz, but still got the same results.
And here is one of the error I met: RuntimeError: round_vml_cpu not implemented for 'Long' because of the round function in "count = torch.sum(target, dim=1).round().to(device)", line 38 in test_lopping.py. I found that one of the video has groundtruth of 0, and if I ignore the round function for that video, I got the result as mentioned above.

This problem seems lies in cuda.  I updated the cuda version from 11.4 to 11.6 and installed pytorch 1.12.1 as well as mmaction2 , then it produced a similar result with the paper.  But I can't figure out the reason and there is still a very small margin to the paper

Glad to see you have solved it.
Closed as no update.

I followed all the aforementioned settings and still get MAE: 0.582 and OBO： 0.283. (pytorch 1.7.0, mmcv1.4.0, mmcv_full1.7.1 cuda 10.1), and I tested with two different machines, also repeated downloading the dataset and preprocessing the MP4 to npz, but still got the same results.
And here is one of the error I met: RuntimeError: round_vml_cpu not implemented for 'Long' because of the round function in "count = torch.sum(target, dim=1).round().to(device)", line 38 in test_lopping.py. I found that one of the video has groundtruth of 0, and if I ignore the round function for that video, I got the result as mentioned above.

This problem seems lies in cuda. I updated the cuda version from 11.4 to 11.6 and installed pytorch 1.12.1 as well as mmaction2 , then it produced a similar result with the paper. But I can't figure out the reason and there is still a very small margin to the paper

I have tried this version but still I got MAE=0.5826 and OBO=0.2829. Could you please share with us what is the result you get? Thanks a lot in advance!


Monitoring

Federico!! Muy fan tuyo @fgimenez !
Great collection of ansible / terraform codes. It is really amazing. I am using part of it, so thanks a million!
Is there any plan to include some monitoring?  Prometheus or similar
I cant find it.
Regards

Federico!! Muy fan tuyo @fgimenez !

Vaya muchas gracias!! :D

Is there any plan to include some monitoring? Prometheus or similar

Monitoring is indeed a central concern for us. The approach we have taken so far is taking advantage of the current instrumentation of substrate-based applications which sends data to instances of substrate-telemetry https://github.com/paritytech/substrate-telemetry We have developed a Prometheus exporter https://github.com/w3f/substrate-telemetry-exporter that can be attached to a substrate-telemetry backend so that it can be scraped.
We also have already defined some alerts to get information about the status of the network https://github.com/w3f/substrate-telemetry-chart/blob/master/charts/substrate-telemetry/templates/alertrules.yaml but the information that we get currently from the exporter is pretty generic and won't be useful at all for knowing how the validators are performing. So the idea is to change the exporter to be configurable to get information about a concrete validator, and then define a set of alertrules for this data.
So, as I see it nothing should be changed in this repo, now that we can configure the telemetry endpoint to be used by the validators we are good. We have started the work on the other two repos to make these validators more observable. closing this issue now, feel free to reopen if you think that it should be handled in a different way :)


Can't see application window

Describe the bug
I install lens(macOS) application. But Lens application window doesn't appear.
To Reproduce
Steps to reproduce the behavior:

I downloaded https://github.com/lensapp/lens/releases/tag/v4.1.3 > Lens-4.1.3.dmg
and installed and launched application
But Lens window did not appear

Expected behavior
A clear and concise description of what you expected to happen.
window does not appear even clicked application.
Screenshots

Environment (please complete the following information):

Lens Version: 4.1.3
OS: mac OS

Installation method (e.g. snap or AppImage in Linux): https://github.com/lensapp/lens/releases/tag/v4.1.3 > dmg

same as or similar to #2195

@jim-docker
I also have info: APP:ACTIVATE {"hasVisibleWindows":false} log.
Therefore I also reinstall lens as homebrew.
Thank you for your help :) I resolve this issue.


Implement modem

This is still a work in progress, definitely needs some cleaning at the least but it is working.

To do this I needed to be able to mock a firebase object. Per our recent discussions this may become much easier with the refactorings we were talking about but this impl will work for now.
Also needed to break out an http client object to keep all the esp8266 from compiling to build a Firebase.
I also needed to be able to build and run locally outside of the arduino framework, as such I have added some dummies and a link to the arduino-mock repository to make this possible.

The FirebaseSerialHost example is working and I have tested it with the huzzah module. We are still missing the advanced versions of all commands.
I wouldn't mind checking in the simple version though and making a smaller PR for the advanced versions. This one is getting a little large.

This PR is being abandoned, it is in a hopeless tailspin of rebasing that I cannot pull it out of. See https://github.com/googlesamples/firebase-arduino/pull/83 and https://github.com/googlesamples/firebase-arduino/pull/84


bug(OverlayContainer): Dropdown not rendering after adding custom theme and also adding the class to the CDK OverlayContainer

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
I've created a custom theme and followed the documentation steps for adding and it works fine.
I'm also trying to get the overlays styled for Dropdowns, etc. and IIUC the way to go about that is to add the custom theme class to the class list of the overlay container.
I've done that like this:
    this.overlayContainer.getContainerElement().classList.add('my-theme')
    console.log(this.overlayContainer.getContainerElement().classList)

The console.log statement does show that it has been added.
However it is not showing up in the application when served, and so the dropdown is not rendering.
Reproduction
Steps to reproduce:
1.git clone git@github.com:fireflysemantics/angular-theming-test.git
2. cd  angular-theming-test
3. npm i
4. ng serve -o
Since it uses SCSS I had to create a new repository for it.
Expected Behavior
The dropdown should render.
Actual Behavior
The my-theme class should render in the overlay container.


regexp.MustCompile() performance

Heya,
Looking though the code today I noticed that the calls to regexp.MustCompile() are inline.
Compiling the regular expressions represents a significant cost of a match, this is why the compile and match/replace calls are seperated in Go.
Moving the compile step up into the package scope (so they are run once on init) will result in a performance benefit, especially for functions like getRenderInput which are called often.

Hi, thanks for your comment. This is actually my first go project, so I appreciate your feedback! I wonder if the go compiler does some optimization here if you use MustCompile with a static string? But nevertheless, I think it is better practice to move them into the package scope. I will see how I handle the replacement expressions in the address formatter. Will probably do that next weekend. Thanks again.

Hi Timon, I think in your case maybe it's not such a big deal but there wouldn't be any optimisations for using a static string.
What's going on under the hood is that the string 'pattern' is being converted into a non-deterministic finite state automata, and possibly simplified into a deterministic automata. This all requires parsing the pattern string and converting it to a graph type structure in memory which allows very fast lookups, in your case the automaton would likely be small and reasonable fast to build. It's still a good best-practise to call Compile() only once.
All the best
-P

https://github.com/timonmasberg/address-formatter/commit/cfdd1690fcfd05ea409e64118d7cd846477a0694


Fix some broken links

I still need to fix the following broken links:
On source page path = /networks/join-testnet:
-> linking to ../osmosis-core/osmosisd.md (resolved as: /osmosis-core/osmosisd.md)

On source page path = /osmosis-core:
-> linking to /osmosis-core/guides/structure/transaction

On source page path = /osmosis-core/modules/spec-gamm:
-> linking to ./client/docs/create-lbp-pool.md (resolved as: /osmosis-core/modules/client/docs/create-lbp-pool.md)
-> linking to ./client/docs/create-pool.md (resolved as: /osmosis-core/modules/client/docs/create-pool.md)

On source page path = /osmosis-core/modules/spec-superfluid:
-> linking to 07_proposals.md (resolved as: /osmosis-core/modules/07_proposals.md)
-> linking to 03_messages.md (resolved as: /osmosis-core/modules/03_messages.md)
-> linking to 04_epoch.md (resolved as: /osmosis-core/modules/04_epoch.md)
-> linking to 06_hooks.md (resolved as: /osmosis-core/modules/06_hooks.md)

On source page path = /osmosis-core/osmosisd:
-> linking to ../network/join-testnet (resolved as: /network/join-testnet)
-> linking to ../network/join-mainnet (resolved as: /network/join-mainnet)

On source page path = /osmosis-core/relaying/ibc-relayers-list:
-> linking to discord.silknodes.io (resolved as: /osmosis-core/relaying/discord.silknodes.io)

On source page path = /overview/getting-started:
-> linking to ../wallets/keplr/README.md (resolved as: /wallets/keplr/README.md)
-> linking to ../terminology.md (resolved as: /terminology.md)
-> linking to ../terminology.md#slippage (resolved as: /terminology.md)
-> linking to ../terminology.md#fees (resolved as: /terminology.md)

On source page path = /overview/integrate/registration:
-> linking to info.osmosis.zone (resolved as: /overview/integrate/info.osmosis.zone)
-> linking to coingecko.com (resolved as: /overview/integrate/coingecko.com)

On source page path = /overview/osmo:
-> linking to ../osmosis-core/modules/spec-superfluid.md (resolved as: /osmosis-core/modules/spec-superfluid.md)

Hi @daniel-farina  kindly visit the official COSMOS page to start a chat with an agent on a live chat support to report this for review and for further assistance via LIVE CHAT


feature: modify dfdaemon port validate method, allow to expose more p…

Ⅰ. Describe what this PR did
modify dfdaemon port validate method, allow to expose more port to listen.
Ⅱ. Does this pull request to fix one issue?

NONE
Ⅴ. Special notes for reviews
Here is a case:
We have a private docker registry, named https://docker.pt.komey.com.
and we want to make our user to None care about the registry address,
So we'd like to config our DNS（docker.pt.komey.com） record for a specific region to <IP_ADDRESS> and expose dfdaemon on 443 port. Which may make our users have No feeling about the difference between the regions which didn't deploy dragonfly.

Thanks for your contributes!
Could you please combine your 3 commits into one?


Custom color - instead of blue

Great library.
How can I use another color for the drop, instead of blue?

Thank you!
dependencies {
  compile 'com.github.recruit-lifestyle:WaveSwipeRefreshLayout:1.2'
}

If you added version1.2, you can use WaveSwipeRefreshLayout#setWaveColor method!

Awesome, thank you.

How do you set the color of rotating arrow?

can you make it like I can use colors with alpha? (in setWaveColor switch mPaint.setColor to setARGB)

@hatpick
dependencies {
  compile 'com.github.recruit-lifestyle:WaveSwipeRefreshLayout:1.4'
}

If you added version1.4, you can use WaveSwipeRefreshLayout#setWaveARGBColor method!

Thanks,

This works perfectly! But is there a way to change the Arrow color?

use setColorSchemeColors(color)


⚠ Bofrost.de has degraded performance

In 7abf9d7, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1066 ms

Resolved: Bofrost.de performance has improved in b8351f5 after 6 minutes.


Restructure the lib/ folder

I renamed page.dart to page_widget.dart to reflect that it's the home of the PageWidget.  I propose we keep all of our Widget classes in the widgets/ folder.  That would mean the following changes -

Move ParameterWidget (and _ActiveParameterWidget) out of entry.dart and into widgets/parameter_widget.dart
Move CommentEntryWidget into widgets/comment_entry_widget.dart
Move page_widget.dart into widgets/page_widget.dart
Move PageEntry / ParameterEntry / CommentEntry into their own files outside of widgets/

Does this sound reasonable to everyone?

I'm going to move ahead on this before starting on Iteration 5 stories!

Completed with PR #44.


Can't import wallet

Hi I have an wallet addres for which I haave both mnemonic and private key, that was generated using solong some time ago. Tried to import it to sollet.io as they suggested but none of derivation method gives me exactly this addres. I can acces this wallet on old device... But would be cool if there was possibility to import from private key. For sure I need to transfer fundds from this wallet to any other, more secure but I wanted to let you know more people may have issue like this one.

Do you know the derivation path used by solong? Can you still import it into their wallet?


primary_reads_enabled doesn't behave as expected when pool_mode = "session"

Describe the bug
When primary_reads_enabled = false and  pool_mode = "session" if a psql client connects to the primary node (via pgcat) on first connection, it ignores primary_reads_enabled = false. i.e. select queries are always sent from the primary node and never the replica.
To Reproduce
[pools.simple_db]
pool_mode = "session"
default_role = "replica"
query_parser_enabled = true
primary_reads_enabled = false
sharding_function = "pg_bigint_hash"

[pools.simple_db.shards.0]
servers = [
    [ "<IP_ADDRESS>", 5432, "primary" ],
    [ "localhost", 5431, "replica" ]
]

Expected behavior
One would expect that the inserts go to the primary while the selects go to the replicas.

Yeah it appears that the when primary_reads_enabled = false and pool_mode = "session". The behaviour is not as expected. primary_reads_enabled = false seems to be completely ignored.

Try pool_mode = "transaction". In session mode, the client is bound to the first server it talks to for the duration of the client connection.

Yes, pool_mode = "transaction" works. But my ticket is describing that was that pool_mode = "session" doesn't work. If its bound to the first server for the duration of the connection, it could cause writes to occur (and fail) on the replicas. We've seen this happen before as well. i.e. when pool_mode = "session" pgGat sometimes tries to write to the replica, which then fails because our replicas are read only. This doesn't seem like the desired behaviour.

Hello @levkk and team, how are you?
We would really appreciate having this functionality in session mode, as we greatly value PgCat's performance concerning pool control. We have many legacy applications that, unfortunately, only work in session mode, and we need to handle write and read balancing/routing. Currently, with the way things are, the Primary node is heavily overloaded and exceeding the connection limit.
Therefore, we are interested in funding the development of this session mode functionality with write and read routing in PgCat. If you find it relevant, I am available to discuss it further.
We would also like this functionality to be made available to the community under the current PgCat license.
Thank you, and I look forward to your response.
Best regards,
Rodrigo Tornis


multi role - introduce NOBLE_MULTI_ROLE flag for ignoring peripheral role commands

See #377
Patch 6701fc61c5c0f44b948d90f12013ea464baffc80 introduced default functionality in noble to send error responses for commands meant for peripheral roles. This is problematic for use with bleno, as all commands that bleno is meant to receive will send back REQ_NOT_SUPPORTED.
The introduction of the NOBLE_MULTI_ROLE flag will prevent this functionality, as well as provide a flag for all future multi role patches to be placed under.
Bryce

@popasquat89 thanks!
Should bleno auto-set NOBLE_MULTI_ROLE internally?

I'm trying to think of any scenarios where you would use both bleno and
noble and not want to enable that flag. The only one I can think of is if
you specified the BLENO_HCI_DEVICE_ID different from the
NOBLE_HCI_DEVICE_ID. Would it make sense in this case for the new flag to
be disabled?
Do we add a flag in bleno to disable the default functionality of enabling
the multi role flag in noble?
I think it might be best to let the developer decide to enable the flag.
Bryce
On Sun, Apr 17, 2016 at 7:46 PM, Sandeep Mistry<EMAIL_ADDRESS>wrote:

@popasquat89 https://github.com/popasquat89 thanks!
Should bleno auto-set NOBLE_MULTI_ROLE internally?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/sandeepmistry/noble/pull/379#issuecomment-211140763

@popasquat89 thanks!

I think it might be best to let the developer decide to enable the flag.

Sounds good, let's stick with this for now


Uncaught TypeError: e is undefined when selecting Keepright-problems

URL
No response
How to reproduce the issue?
Try to tick "Keepright problems". Then window freezes and parts of app are not clickable anymore. I had chinese languange pack for firefox installed but not anymore.
Screenshot(s) or anything else?
The console shows the error appearing when ticking Keepright Problems and a warning (?) I get when hovering the map

This is how window freezes, which doesn't dissapear after unselecting Keepright-problems:

Which iD Editor versions do you see the issue on?
Released version at openstreetmap.org/edit
Which browsers are you seeing this problem on?
Firefox

Appears also on Edge, happens without chinese language pack as well.
Page has to be reloaded to run again.
Working with KeepRight is not possible with this bug.

This might be a duplicate of #8963, check to see if this issue is still present when using https://ideditor.netlify.app/ (includes unreleased features)
Note that the version of iD on openstreetmap.org/edit is using the latest release which doesn't include any of the unreleased features listed in the changelog

The version on osm.org just got updated to v2.21.0. KeepRight seems to be working now:

Yes, I can confirm it's working


Change Admin Dashboard View and Correct Reports problems

Change Admin Dashboard View and Correct Reports problems

Dashboard View done...
Reports correction in progress

Reports are done...


Updated websocket examples

Also can you change all the models to the turbo models when appropriate

TODOs before merging
// TODO: handle timeout between server and elevenlabs
// TODO: handle timeout between client and server
// TODO: get it working for the normal output format (mp3_44100)
// TODO: handle saying that it's the last input
Also note to self:

[ ] restructure to /incoming/node
[ ] remove the code which isn't node-express and vanilla JS for now until properly validated


[FEATURE] Single page that just redirects

For example, https://jessewei.dev/teaching/act/guide should just redirect to the guide.

But it should still show up here


Change Certificates.Configuration to a Sources package

https://github.com/aspnet/Hosting/pull/1095

Would like to confirm whether cross-compilation is required for Microsoft.AspNetCore.

https://github.com/aspnet/KestrelHttpServer/pull/1878 moved config code to Kestrel


chore: Update dependencies

And suppress new validator warnings

Duplicate of #5382? which is waiting on #5385 to be merged first.

I just merged #5385. #5382 has conflicts now.

Some changes are redundant with #5382, but this one picks up more updates and also updates vnu.jar.

@NGPixel once all the DePaul bits are in, let me know and I'll rebase this against the new main

#5382 merged.


annotation in radar charts

I have a radar chart created with radar charts and i have created 14 radial lines and i am seeing ticks values in the first radial like [0,50,100] now i want to show different different labels and ticks in each radial. I am attaching a image also that of what type i want to show the chart please help me out i have posted the same querty in chart js official account but didn't got any helpful response and after research i found out that this can help me out but i read on website that annotation can't be applied on radar charts so if possible tell the way to make it out

@satyammishra0 well, the annotation plugin, as you have read on website, doesn't support radar charts and mainly radial scale.
Having a look to the picture, I think we could try to use the datalabels plugin: https://chartjs-plugin-datalabels.netlify.app/

ok can you help me out more with it in figuring how we can do so ?

I tried that too but in that also I don't think we can customize the radials values of the ticks as used in the image i have provided

@satyammishra0 let me close it. But feel free to reopen if you needed.


[Config] Define BOOST_HANA_CONFIG_CLANG for apple clang

Hi!
I had trouble building the library with the version of clang that came with Xcode, and it came down to the configuration thinking I was using GCC. Using __apple_build_version__ to map to the proper clang build version fixed the problems. See https://gist.github.com/yamaya/2924292 for version reference.
Thank you!
Alex.

Can you please show me your clang++ --version? Mine completely fails to build Hana (compilation errors and then ICEs when I fix the compilation errors).
Here's my clang++ --version:
> clang++ --version
Apple LLVM version 6.0 (clang-600.0.57) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin13.4.0
Thread model: posix

Thanks for taking a look.
Here is my clang++ --version (I updated Xcode on OS X Yosemite):
> clang++ --version
Apple LLVM version 6.1.0 (clang-602.0.53) (based on LLVM 3.6.0svn)
Target: x86_64-apple-darwin14.3.0
Thread model: posix

Note that I actually had to also specify a path for libc++ when running cmake:
cmake .. -DCMAKE_CXX_COMPILER=/usr/bin/clang -DLIBCXX_ROOT=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/

I'm on Mavericks with Xcode 6.2, and I can tell that the associated Clang isn't able to compile Hana. However, it works on your Xcode 6.3.2 (the latest on Yosemite). Based on the Xcode/Clang version record you linked above, it would be nice to know whether Xcode 6.3 and 6.3.1 are able to compile Hana too, which would give us the minimal required version of Xcode.

I tweaked your PR in 66c0b70; do you agree with my approach? Also, could you please build 66c0b70 with your Xcode just to make sure it actually works. Of course, I'll get my hands on a more recent version of Xcode to make sure it works on the long term, but for now I don't have that.

It looks good to me, and everything compiles. Thank you! :smiley:

Thanks for the feedback and the PR! This issue will be closed automatically when I merge the changes to master, which I will do as soon as https://travis-ci.org/ldionne/hana/builds/64145010 passes. Thanks!


How to train on keypoints?

❓ Questions and Help
When I try to run:
python tools/train_net.py --config-file "configs/e2e_keypoint_rcnn_R_50_FPN_1x.yaml" SOLVER.IMS_PER_BATCH 2 SOLVER.BASE_LR 0.0025 SOLVER.MAX_ITER 720000 SOLVER.STEPS "(480000, 640000)" TEST.IMS_PER_BATCH 1
I get this error:
size mismatch for roi_heads.box.predictor.cls_score.weight: copying a param with shape torch.Size([81, 1024]) from checkpoint, the shape in current model is torch.Size([2, 1024]).
Is this because the pre-trained model is made for localization with 81 classes? What would be the best way to get around this without having the proper pre-trained model?
Thanks!

Hi,
You are probably running the training job in the same directory as where there is an already existing checkpoint from a previous run (from detection on 81 classes).
Can you change the OUTPUT_DIR from the keypoint config to point to a different folder?

Thanks! I had forgotten to change it.

@renebidart  @fmassa hi, I train on single GPU. What would be the best max_iters or parameters to train on keypoints?
maybe like:
SOLVER.IMS_PER_BATCH:2
SOLVER.BASE_LR: 0.0025
SOLVER.MAX_ITER: 720000
SOLVER.STEPS: (480000, 640000)
TEST.IMS_PER_BATCH: 1


New release

Hello!
I noticed there was no new release after https://github.com/mailslurper/mailslurper/pull/134. Could you please publish a new release? Thanks!

New release: https://github.com/mailslurper/mailslurper/releases/tag/release-1.15.0


AGNOS updater: add download speed indicator

fixes #24119

Thanks for the PR, but #24119 also involves showing the download speed in the UI. You're welcome to finish this up and re-open, but no guarantees we'll merge it. We tend to prefer doing updater work ourselves, since most of the work is in validating it.


New daily docker

Thank you for submitting this pull request

changes daily-build-master-docker-images in dailyBuilds master from free style job to pipeline job
hard coded values in pipelines were replaced by variables

ToDo: once the new nodes with Rhel7 and all requested docker configuration are created
the label def AGENT_DOCKER_LABEL= "kieci-02-docker" should be replaced by the recent machine.
Same for def artifactsPath="/home/docker/kie-artifacts/$kieVersion" - since the path will be /home/jenkins./..

How to retest a PR or trigger a specific build:

* a pull request please add comment: Jenkins retest this

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

ok to test
why is this requested from @mbiarnes who should be the admin?

jenkins retest this

Build finished. 39 tests run, 0 skipped, 0 failed.


sphinx-toolbox: updating version

After starting get the error:
Could not import extension sphinx_toolbox.confval (exception: No module named 'cachecontrol')
Couldn't find why it is happening but figure out that the new version fixed that.

Docs for f4c29404170aca1931c9bb31f12eb9675a1aa50e are browesable at: https://ci.foundries.io/projects/fio-docs/builds/915/docs/artifacts/html/index.html


Error with kubectl

This command: kubectl create clusterrolebinding kubernetes-dashboard --clusterrole=cluster-admin --serviceaccount=kube-system:kubernetes-dashboard
Results in this error: Unable to connect to the server: dial tcp <IP_ADDRESS>:8080: connectex: No connection could be made because the target machine actively refused it.

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

ID: 2ba1dad2-9792-2a7b-cdb6-68da0524cff3
Version Independent ID: 42736112-f6db-d241-e89b-48fd2c35ceb7
Content: Manage an Azure Kubernetes Service cluster with the web dashboard
Content Source: articles/aks/kubernetes-dashboard.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

Thanks for the question. We are currently investigating and will update you shortly.

You need to run get-credentials before creating the binding..Did you run the command?
az aks get-credentials --resource-group  --name

that fixed it! thanks!

Thanks, @mv3008 for helping out.
Thanks @brianharwell for the update.
We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


Setting width="100%" on mj-image in full-width mj-seciton gets 100px as output.

Given this code:
<mj-section full-width="full-width">
    <mj-section padding="0">
        <mj-image width="100%" src="image.jpg" />
    </mj-section>
</mj-section>

The output is as followed:

Click to show HTML output
 ```html

```

As you can see, the width set on the <td> and <img> tags is set to 100px instead of 100%.
This holds true for any other percentage, as every percentage value is converted to a px value.

Hi,
mj-image should be in a mj-column even for a single column layout. That's why the image width is broken


Is SciPy website under any maintenance? Can't open it since yesterday!

Already being tracked here: https://github.com/numpy/numpy/issues/8779.

Just wonder if there is any mirror website to access the old version?

The Internet Archive has a snapshot of the 0.18.1 documentation: http://web.archive.org/web/20161216070200/https://docs.scipy.org/doc/scipy/reference/


DROID MR.

@BertAnthonyRochester Could you provide us with the URL of the MS Doc that you were following, if any?

@BertAnthonyRochester Could you provide us with the URL of the MS Doc that you were following, if any?

@BertAnthonyRochester We will now proceed to close this thread, but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@BertAnthonyRochester We will now proceed to close this thread, but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


Add maglnet/composer-require-checker in CI

Problem Statement
https://github.com/getsentry/sentry-symfony/issues/714#issuecomment-1525083220:

Btw, sentry/sentry has the same issue in GuzzleTracingMiddleware.

Solution Brainstorm
@cleptric we should avoid similar issues in the future by adding https://packagist.org/packages/maglnet/composer-require-checker in CI
Originally posted by @Jean85 in https://github.com/getsentry/sentry-symfony/issues/714#issuecomment-1523646872
We can also use https://packagist.org/packages/irstea/composer-require-checker-shim if we don't want to pollute our dependencies.

Same as https://github.com/getsentry/sentry-symfony/issues/716

The GuzzleTracingMiddleware class is not used by this package and it was provided mostly as an example for the tracing feature itself. I don't think we should require a package used by it if the class itself is optional.

With 4.0 I think we're good here.


Source code fails to compile on Arch Linux x86-64 due to TII Dialog function error

The same failure to compile happens with both the beta release in the AUR and the latest main branch code from GitHub. The relevant console output is below:
[ 98%] Linking CXX executable AbracaDABra
/usr/bin/ld: CMakeFiles/AbracaDABra.dir/tii/tiidialog.cpp.o: in function `TIIDialog::reset()':
tiidialog.cpp:(.text+0x5d7c): undefined reference to `QCPGraph::setData(QList<double> const&, QList<double> const&, bool)'
/usr/bin/ld: tiidialog.cpp:(.text+0x5e3b): undefined reference to `QCPGraph::setData(QList<double> const&, QList<double> const&, bool)'
collect2: error: ld returned 1 exit status
make[2]: *** [gui/CMakeFiles/AbracaDABra.dir/build.make:1626: gui/AbracaDABra] Error 1
make[1]: *** [CMakeFiles/Makefile2:305: gui/CMakeFiles/AbracaDABra.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

I assume it is because you have installed qcustomplot but not qcustomplot-qt6 from AUR. Either both must be installed or none, I do not know how to deal with this limitation :-(

Installing qcustomplot-qt6 did allow it to compile. It seems an odd limitation but I guess moving it from optdepends to depends in the PKGBUILD will ensure that qcustomplot-qt6 is installed so no-one else has the same issue. Thank you for your prompt help.

Yes, I will probably do it. Thanks for your feedback, I will close this issue.


Update trace4cats-opentelemetry-jaeger-exporter, ... to 0.14.1

About this PR
📦 Updates

io.janstenpickle:trace4cats-opentelemetry-jaeger-exporter
io.janstenpickle:trace4cats-opentelemetry-otlp-grpc-exporter
io.janstenpickle:trace4cats-opentelemetry-otlp-http-exporter

from 0.14.0 to 0.14.1
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (0.14.0).
You might want to review and update them manually.
docs/components.md
docs/examples.md
docs/migrating.md
docs/sampling.md
project/Dependencies.scala

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

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

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

Superseded by #221.


helm 3 support

Hi
This tool so promising to convert helm charts to regular Kubernetes native yaml files without using helm in some cases. I tried to use this tool today but getting below error. is this works for helm 3?
helm convert --destination mongodb --name mongodb stable/mongodb
Error: Couldn't load repositories file (/Users/skotaru/.helm/repository/repositories.yaml).
You might need to run helm init (or helm init --client-only if tiller is already installed)

Hi @kotarusv, could you try doing the conversion using Docker: https://github.com/ContainerSolutions/helm-convert/issues/25#issuecomment-697404204

@etiennetremel this helped me :-)
on the other topic, I had to login to docker container and add custom helm repo


V1.2.0

#24

Codecov Report

Merging #26 (d6b24c8) into main (fb77dd5) will decrease coverage by 0.21%.
Report is 2 commits behind head on main.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main      #26      +/-   ##
==========================================
- Coverage   99.59%   99.38%   -0.21%
==========================================
  Files          67       69       +2
  Lines        1221     1292      +71
  Branches      196      212      +16
==========================================
+ Hits         1216     1284      +68
- Misses          5        8       +3

Files Changed
Coverage Δ

src/astro/FunctionalAstrolabe.ts
98.78% <ø> (-1.22%)
:arrow_down:

src/astro/FunctionalPalace.ts
100.00% <ø> (ø)

src/astro/FunctionalSurpalaces.ts
100.00% <ø> (ø)

src/astro/analyzer.ts
97.10% <ø> (+0.22%)
:arrow_up:

src/astro/astro.ts
100.00% <ø> (ø)

src/star/FunctionalStar.ts
93.75% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


How to generate TOTP using Date in milliseconds?

Hi,
I've tried all the totp libraries but when I convert seconds into milliseconds the TOTP doesnt generate the same OTP within time period. Im converting into milliseconds by mutliplying with 1000. I believe the length of secret data changes when converting to milliseconds. Is there anything special need to be changed.

Many more details needed. I have no idea what' you're doing.

TOTP should not be using milliseconds. The factor should be secondsSince1970 / step where step is the time period the authentication parties have agreed to (usually 30).

Yeah. Question was never clarified, so closing this.


cannot run bandit on codes in a folder using *.py

Describe the bug
Not sure if it's a bug, but I can run bandit on each file in a folder, however when I try to use /folder/*.py, it says

Files skipped (1):
*.py (Invalid argument)

How should I fix this? I'm on Anaconda (latest version) on Windows 10.

By default Bandit scans directories for *.py.  So there is no need to enter *.py part of  /folder/


How to use rocThrust and OpenMP in the same time

I followed the example https://github.com/ROCm-Developer-Tools/HIP-Examples/tree/master/openmp-helloworld and built it successfully with hipcc. But when I tried to add rocthrust containers in the source file, errors occurred.
I have also tried to build this example with only rocthrust and it works fine.
My environment:

ROCm 3.9
CMake 3.16.5

Error messages:
In file included from openmp_helloworld.cpp:25:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/device_vector.h:25:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/vector_base.h:29:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/contiguous_storage.h:240:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/contiguous_storage.inl:23:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/allocator/default_construct_range.h:35:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/allocator/default_construct_range.inl:22:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/uninitialized_fill.h:274:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/uninitialized_fill.inl:26:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/system/detail/adl/uninitialized_fill.h:44:
/public/opt/rocm/rocm-3.9.1/include/thrust/system/hip/detail/uninitialized_fill.h:62:13: error: no matching function for call to 'operator new'
            ::new(static_cast<void*>(&out)) value_type(value);
            ^~
/public/opt/rocm/rocm-3.9.1/include/thrust/system/hip/detail/parallel_for.h:66:17: note: in instantiation of function template specialization 'thrust::hip_rocprim::__uninitialized_fill::functor<thrust::device_ptr<int>, int>::operator()<unsigned long>' requested here
                f(tile_base + idx);
                ^
/public/opt/rocm/rocm-3.9.1/include/thrust/system/hip/detail/parallel_for.h:95:44: note: in instantiation of function template specialization 'thrust::hip_rocprim::__parallel_for::kernel<256, 1, thrust::hip_rocprim::__uninitialized_fill::functor<thrust::device_ptr<int>, int>, unsigned long>' requested here        hipLaunchKernelGGL(HIP_KERNEL_NAME(kernel<block_size, items_per_thread, F, Size>),
                                           ^
/public/opt/rocm/rocm-3.9.1/include/thrust/system/hip/detail/parallel_for.h:131:50: note: in instantiation of function template specialization 'thrust::hip_rocprim::__parallel_for::parallel_for<thrust::hip_rocprim::__uninitialized_fill::functor<thrust::device_ptr<int>, int>, unsigned long>' requested here            hipError_t  status = __parallel_for::parallel_for(count, f, stream);
                                                 ^
/public/opt/rocm/rocm-3.9.1/include/thrust/system/hip/detail/parallel_for.h:119:12: note: in instantiation of member function 'thrust::hip_rocprim::parallel_for(execution_policy<thrust::hip_rocprim::tag> &, thrust::hip_rocprim::__uninitialized_fill::functor<thrust::device_ptr<int>, int>, unsigned long)::workaround::par' requested here
    struct workaround
           ^
/public/opt/rocm/rocm-3.9.1/include/thrust/system/hip/detail/uninitialized_fill.h:76:18: note: in instantiation of function template specialization 'thrust::hip_rocprim::parallel_for<thrust::hip_rocprim::tag, thrust::hip_rocprim::__uninitialized_fill::functor<thrust::device_ptr<int>, int>, unsigned long>' requested here
    hip_rocprim::parallel_for(policy, functor_t(first, x), count);
                 ^
/public/opt/rocm/rocm-3.9.1/include/thrust/detail/uninitialized_fill.inl:54:10: note: (skipping 3 contexts in backtrace; use -ftemplate-backtrace-limit=0 to see all)
  return uninitialized_fill_n(thrust::detail::derived_cast(thrust::detail::strip_const(exec)), first, n, x);
         ^
/public/opt/rocm/rocm-3.9.1/include/thrust/detail/contiguous_storage.inl:251:3: note: in instantiation of function template specialization 'thrust::detail::default_construct_range<thrust::device_allocator<int>, thrust::device_ptr<int>, unsigned long>' requested here
  default_construct_range(m_allocator, first.base(), n);
  ^
/public/opt/rocm/rocm-3.9.1/include/thrust/detail/vector_base.inl:220:15: note: in instantiation of member function 'thrust::detail::contiguous_storage<int, thrust::device_allocator<int>>::default_construct_n' requested here
    m_storage.default_construct_n(begin(), size());
              ^
/public/opt/rocm/rocm-3.9.1/include/thrust/detail/vector_base.inl:65:3: note: in instantiation of member function 'thrust::detail::vector_base<int, thrust::device_allocator<int>>::default_init' requested here
  default_init(n);
  ^
/public/opt/rocm/rocm-3.9.1/include/thrust/device_vector.h:95:8: note: in instantiation of member function 'thrust::detail::vector_base<int, thrust::device_allocator<int>>::vector_base' requested here
      :Parent(n) {}
       ^
openmp_helloworld.cpp:41:32: note: in instantiation of member function 'thrust::device_vector<int, thrust::device_allocator<int>>::device_vector' requested here
    thrust::device_vector<int> v(10);
                               ^
/public/opt/devtoolset-7/root/usr/include/c++/7/new:134:7: note: candidate function not viable: call to __host__ function from __device__ function
void* operator new(std::size_t, const std::nothrow_t&) _GLIBCXX_USE_NOEXCEPT
      ^
/public/opt/devtoolset-7/root/usr/include/c++/7/new:168:14: note: candidate function not viable: call to __host__ function from __device__ function
inline void* operator new(std::size_t, void* __p) _GLIBCXX_USE_NOEXCEPT
             ^
/public/opt/devtoolset-7/root/usr/include/c++/7/new:120:7: note: candidate function not viable: requires 1 argument, but 2 were provided
void* operator new(std::size_t) _GLIBCXX_THROW (std::bad_alloc)
      ^
note: candidate function not viable: requires 1 argument, but 2 were provided
In file included from openmp_helloworld.cpp:25:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/device_vector.h:25:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/vector_base.h:29:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/contiguous_storage.h:240:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/contiguous_storage.inl:22:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/allocator/copy_construct_range.h:46:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/allocator/copy_construct_range.inl:21:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/copy.h:90:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/copy.inl:21:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/system/detail/generic/copy.h:58:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/system/detail/generic/copy.inl:23:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/transform.h:724:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/transform.inl:25:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/system/detail/generic/transform.h:105:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/system/detail/generic/transform.inl:19:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/for_each.h:279:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/detail/for_each.inl:27:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/system/detail/adl/for_each.h:44:
In file included from /public/opt/rocm/rocm-3.9.1/include/thrust/system/hip/detail/for_each.h:35:
/public/opt/rocm/rocm-3.9.1/include/thrust/system/hip/detail/parallel_for.h:141:17: error: no matching function for call to object of type 'thrust::hip_rocprim::__uninitialized_fill::functor<thrust::device_ptr<int>, int>'
                f(idx);
                ^
/public/opt/rocm/rocm-3.9.1/include/thrust/system/hip/detail/parallel_for.h:119:12: note: in instantiation of member function 'thrust::hip_rocprim::parallel_for(execution_policy<thrust::hip_rocprim::tag> &, thrust::hip_rocprim::__uninitialized_fill::functor<thrust::device_ptr<int>, int>, unsigned long)::workaround::seq' requested here
    struct workaround
           ^
/public/opt/rocm/rocm-3.9.1/include/thrust/system/hip/detail/uninitialized_fill.h:76:18: note: in instantiation of function template specialization 'thrust::hip_rocprim::parallel_for<thrust::hip_rocprim::tag, thrust::hip_rocprim::__uninitialized_fill::functor<thrust::device_ptr<int>, int>, unsigned long>' requested here
    hip_rocprim::parallel_for(policy, functor_t(first, x), count);
                 ^
/public/opt/rocm/rocm-3.9.1/include/thrust/detail/uninitialized_fill.inl:54:10: note: in instantiation of function template specialization 'thrust::hip_rocprim::uninitialized_fill_n<thrust::hip_rocprim::tag, thrust::device_ptr<int>, unsigned long, int>' requested here
  return uninitialized_fill_n(thrust::detail::derived_cast(thrust::detail::strip_const(exec)), first, n, x);
         ^
/public/opt/rocm/rocm-3.9.1/include/thrust/detail/allocator/default_construct_range.inl:94:11: note: in instantiation of function template specialization 'thrust::uninitialized_fill_n<thrust::hip_rocprim::tag, thrust::device_ptr<int>, unsigned long, int>' requested here
  thrust::uninitialized_fill_n(allocator_system<Allocator>::get(a), p, n, typename pointer_element<Pointer>::type());
          ^
/public/opt/rocm/rocm-3.9.1/include/thrust/detail/allocator/default_construct_range.inl:105:35: note: in instantiation of function template specialization 'thrust::detail::allocator_traits_detail::default_construct_range<thrust::device_allocator<int>, thrust::device_ptr<int>, unsigned long>' requested here
  return allocator_traits_detail::default_construct_range(a,p,n);
                                  ^
/public/opt/rocm/rocm-3.9.1/include/thrust/detail/contiguous_storage.inl:251:3: note: in instantiation of function template specialization 'thrust::detail::default_construct_range<thrust::device_allocator<int>, thrust::device_ptr<int>, unsigned long>' requested here
  default_construct_range(m_allocator, first.base(), n);
  ^
/public/opt/rocm/rocm-3.9.1/include/thrust/detail/vector_base.inl:220:15: note: in instantiation of member function 'thrust::detail::contiguous_storage<int, thrust::device_allocator<int>>::default_construct_n' requested here
    m_storage.default_construct_n(begin(), size());
              ^
/public/opt/rocm/rocm-3.9.1/include/thrust/detail/vector_base.inl:65:3: note: in instantiation of member function 'thrust::detail::vector_base<int, thrust::device_allocator<int>>::default_init' requested here
  default_init(n);
  ^
/public/opt/rocm/rocm-3.9.1/include/thrust/device_vector.h:95:8: note: in instantiation of member function 'thrust::detail::vector_base<int, thrust::device_allocator<int>>::vector_base' requested here
      :Parent(n) {}
       ^
openmp_helloworld.cpp:41:32: note: in instantiation of member function 'thrust::device_vector<int, thrust::device_allocator<int>>::device_vector' requested here
    thrust::device_vector<int> v(10);
                               ^
/public/opt/rocm/rocm-3.9.1/include/thrust/system/hip/detail/uninitialized_fill.h:58:41: note: candidate template ignored: substitution failure [with Size = unsigned long]
        void THRUST_HIP_DEVICE_FUNCTION operator()(Size idx)
                                        ^
2 errors generated when compiling for host.

openmp_helloworld.cpp:
// HIP header
#include <hip/hip_runtime.h>
#include <thrust/device_vector.h>

//OpenMP header
#include <omp.h>

#include <stdio.h>
#include <stdlib.h>

__global__
void hip_helloworld(unsigned omp_id)
{
    printf("Hello World... from HIP thread = %u\n", omp_id);
}

int main(int argc, char* argv[])
{
    thrust::device_vector<int> v(10);

    // No errors
    //thrust::device_vector<int> v;

    // Beginning of parallel region
    #pragma omp parallel
    {
        auto tid = omp_get_thread_num();
        printf("Hello World... from OMP thread = %d\n", tid);

        hipLaunchKernelGGL(hip_helloworld, dim3(1), dim3(1), 0, 0, tid);
    }
    // Ending of parallel region

    hipLaunchKernelGGL(hip_helloworld, dim3(1), dim3(1), 0, 0, /*id=*/ 0);
    hipStreamSynchronize(0);

    printf("PASSED!\n");
    return 0;
}

Commands:
hipcc -xhip -fopenmp=libomp openmp_helloworld.cpp

CMake gives the same error. This is my cmake file:
project(openmp_helloworld)

cmake_minimum_required(VERSION 3.16)

# Search for rocm in common locations
if(NOT DEFINED ROCM_PATH)
    if(DEFINED ENV{ROCM_PATH})
        set(ROCM_PATH $ENV{ROCM_PATH} CACHE PATH "ROCm path")
    elseif(DEFINED ENV{HIP_PATH})
        set(ROCM_PATH "$ENV{HIP_PATH}/.." CACHE PATH "ROCm path")
    else()
        set(ROCM_PATH "/opt/rocm" CACHE PATH "ROCm path")
    endif()
endif()

set(HIP_PATH "${ROCM_PATH}/hip" CACHE PATH "HIP path")

list(APPEND CMAKE_PREFIX_PATH ${ROCM_PATH} ${HIP_PATH})
find_package(hip REQUIRED)
find_package(rocprim REQUIRED CONFIG)
find_package(rocthrust REQUIRED CONFIG)

# Find OpenMP
find_package(OpenMP REQUIRED)

# Source files
set(CPP_SOURCES ${CMAKE_SOURCE_DIR}/openmp_helloworld.cpp)

# Preparing the executable
add_executable(test_openmp_helloworld ${CPP_SOURCES})
target_link_libraries(test_openmp_helloworld
    PRIVATE hip::device
            roc::rocthrust
            OpenMP::OpenMP_CXX
)

Any updates for this issue, I meet the same issue in my project.

Any updates for this issue, I meet the same issue in my project.

@joye @alephpiece  I reached this problem and checking the test code.

I could build the test project with the following command:
hipcc -xhip -fopenmp=libomp -I/opt/rocm/include/ openmp_helloworld.cpp

rocm 4.3 Ubuntu 18.04.5 LTS

I could build the test file with the following command:
hipcc -xhip -fopenmp=libomp -I/opt/rocm/include/ openmp_helloworld.cpp

rocm 4.3 Ubuntu 18.04.5 LTS

Tested with my CMakelists.txt too. Buildable runable.
@joye @alephpiece Is the problem still appear at rocm 4.3?

I could build the test file with the following command:
hipcc -xhip -fopenmp=libomp -I/opt/rocm/include/ openmp_helloworld.cpp

rocm 4.3 Ubuntu 18.04.5 LTS

Tested with my CMakelists.txt too. Buildable runable.
@joye @alephpiece Is the problem still appear at rocm 4.3?

Hi neon60:
Which commit ID fix the issue?

I could build the test file with the following command:
hipcc -xhip -fopenmp=libomp -I/opt/rocm/include/ openmp_helloworld.cpp

rocm 4.3 Ubuntu 18.04.5 LTS

Tested with my CMakelists.txt too. Buildable runable.
@joye @alephpiece Is the problem still appear at rocm 4.3?

Hi neon60: Which commit ID fix the issue?

@hanjiemicro I could not reproduce the issue. So I could not give you a specific Commit ID. Is the issues still exist at your side?

It pops up in centos7 os.

It popped up in centos7/rocm-4.0.x branch

It popped up in centos7/rocm-4.0.x branch

@hanjiemicro Ok. I will check on centos images. For me on rocm 4.3 Ubuntu 18.04.5 LTS the issue did not appeared.

Closing issue due to inactivity


Rust: modify sorted set command types to RESP3

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

please push your rounds as a separate commit instead of squashing.

Oh sorry I missed that message.


Add changelog, increase version, fix error message and update devDependencies

Since I don't see any functional impact, I merge it without review.


[ExpansionPanel] add override PaperProps

Add override PaperProps for remove in some case elevation, "Divider" in ::before.
Summary 💡
Add ability to override PaperProps for ExpansionPanel
Examples 🌈

Motivation 🔦
It is logical that there should be the ability to change the behavior of the component on which the current component is based.

Could you share what you're trying to achieve?

@eps1lon I am trying to achieve a normal appearance.
In Drawer I have a component for displaying connected displays. Upon disclosure, there will be full display information.
Because Drawer has a shadow and the panel has a shadow, it looks awful. I am trying to achieve a flat display

@popuguytheparrot What's wrong with one of these two options?

<ExpansionPanel elevation={0}>
The customization demo in https://material-ui.com/components/expansion-panels/#customized-expansion-panels

@oliviertassinari on API page i didnt see this prop

Make sense, it requires to dive a bit:

Now, your problem is related to a potential solution I had in mind to kill the /api/ pages. sencha might have the beginning of a solution: https://docs.sencha.com/extreact/6.6.0/modern/Ext.carousel.Carousel.html#configs, not the interactive api explorer with an Inherited checkbox.

This comes up fairly often.
I thought about this quite often and so far I think the best solution is to make apparent props display by default and then make it expandable. Though this requires quite a bit of infra work.

@eps1lon Agree, there is potential here!

Closing for #18288


Int 324 wrapper

Summary
This adds a wrapper that allows the certificates and keys to be passed in as strings instead of files
PR - Merge Checklist:

[ ] CR'd
[ ] Version updated (version #)
[ ] CHANGELOG updated
[ ] README updated or N/A
[ ] [Jenkins build passes](link the passing build here)
[ ] Dependencies satisfied N/A
[ ] Acceptance criteria verified by QE
[ ] Fully tested and approved by QE

Dependencies:

[ ] N/A

Risks:
This library uses xmlsec1 as a shell command.  This could have performance issues.
Rollback:
N/A - prerelease

lgtm


Document update request on IKE Phase 2 parameters

Under IKE Phase 2 (Quick Mode) parameters section, SA Lifetime (Bytes) for RouteBased should be updated as 102,400,000 KB instead of a dash. Additionaly, it would be helpful to expose expected re-key cycle depends on the role(as initator or as responder) of Azure.

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

ID: 779fbece-f67b-28ef-143e-f58ecfa29b1d
Version Independent ID: fe532684-022f-9006-9179-c534fd923171
Content: Azure VPN Gateway: About VPN devices for connections
Content Source: articles/vpn-gateway/vpn-gateway-about-vpn-devices.md
Service: vpn-gateway
GitHub Login: @yushwang
Microsoft Alias: yushwang

@bedro96 , For route based gateway SA lifetime in terms of KB is optional. You can set it in your On-Premises ends, Azure honors it but Azure doesn't send SA lifetime in KB as proposal.
@yushwang , can you comment on this ?

Thank you for you dedication to our documentation.
Unfortunately, we have been unable to review this issue in a timely manner. We sincerely apologize for the delayed response. We are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close


Errors in Visual Studio editor

Hi. I noticed that Visual Studio shows in editor a lot of errors but it compiles fine. I don't have this problem with other projects. Reinstalling VS, WDK etc. doesn't give any results. Is it a problem with the whole project or my setup? I'm using the newest VS 2017 Community and the newest WDK

Hi! Yes, unfortunatelly, I have the same problem and had to "resolve" it via Tools -> Options -> Text Editor -> C/C++ -> Advanced -> [Intellisense] Disable Squiggles. My go-to explanation would be that it's because C++ is not supported by Microsoft in Windows Driver development, but that's rather lame. Maybe discrepancies in include paths? I have to admit I didn't investigate this issue deep enough yet, so if by any chance you or someone happens to resolve it before I do, don't hesitate to share how did you achieve that. :)

Although, judging by squiggles under noexcept keywords, it really looks like when Visual Studio project's toolset is set to WindowsKernelModeDriver*, it all breaks. Like it couldn't uderstand it should parse C++17 code.

I know that @tandasat had some C++ code compiling in the driver with HyperPlatform at one point, although I'm not sure if he had the same squiggle issue. Might be worth looking at though.

I do not think I had the same issue in HyperPlatform, probably because I did not use much C++ specific constructs, and also did not use any of C++17 specific things.
I did had the same issue in the other project though. In my case, removing all noexcept essentially addressed the issue (also, probably because codebase was more like C++03), but if you are using STL headers that's not possible to do.

I've filled bug to VS Developer Community: https://developercommunity.visualstudio.com/content/problem/321040/intellisense-cannot-understand-c17-when-platform-t.html

same problem!

Resolved in recent VS2019 updated.


[Testing Purpose Only] Test Case / Test Execution

Exploring Test - Round 1

[x] Login through steem

[x] Create a new game

[x] Create a new post

[x] Audit a game - approve

[x] Audit a game - reject

[x] Play a game

[x] Vote a game

[x] Comment a game

[x] Update the game

[x] Report a game

[x] Audit a game - approve for a reported game

[x] Audit a game - reject for a reported game

[x] Check game list by category - public

[x] Check game list by roles - private

[x] Check policy links

[x] Check social media links

[x] Promote a game by admin

[x] De-promote a game by admin

[x] Assign Auditor by admin

[x] Unassign Auditor by admin

1st Round testing done, and find issue:
#201
#202
#203
#204
#205

Exploring Test - Round 2

[] Login through steem

[] Create a new game

[] Create a new post

[] Audit a game - approve

[] Audit a game - reject

[] Play a game

[] Vote a game

[] Comment a game

[] Update the game

[] Report a game

[] Audit a game - approve for a reported game

[] Audit a game - reject for a reported game

[] Check game list by category - public

[] Check game list by roles - private

[] Check policy links

[] Check social media links

[] Promote a game by admin

[] De-promote a game by admin

[] Assign Auditor by admin

[] Unassign Auditor by admin


Ian Linkletter & Proctorio

https://ca.gofundme.com/f/stand-against-proctorio
Business Insider: https://www.businessinsider.com/proctorio-silencing-critics-fueling-student-protests-against-surveilalnce-edtech-schools-2020-10
Deutschlandfunk (German Public Radio): https://www.deutschlandfunk.de/hochschulen-in-der-corona-pandemie-online-ueberwachung-soll.684.de.html?dram:article_id=486757
Inside Higher Ed: https://www.insidehighered.com/quicktakes/2020/10/20/ed-tech-specialist-fights-proctorio-lawsuit
Teen Vogue: https://www.teenvogue.com/story/exam-surveillance-tools-remote-learning
The Ubyssey: https://www.ubyssey.ca/news/linkletter-responds-to-proctorio-lawsuit/
Vancouver Sun: https://vancouversun.com/news/ubc-employee-being-sued-by-u-s-software-company-files-anti-slapp-application
The Verge: https://www.theverge.com/2020/10/22/21526792/proctorio-online-test-proctoring-lawsuit-universities-students-coronavirus
Vice: https://www.vice.com/en/article/7k9zjy/an-exam-surveillance-company-is-trying-to-silence-critics-with-lawsuits

https://www.eff.org/deeplinks/2021/02/student-surveillance-vendor-proctorio-files-slapp-lawsuit-silence-critic


NPC SyncDirection .authority is false

see also: https://github.com/MirrorNetworking/Mirror/pull/3495
repro:

Tanks demo
drag Tank into scene, name it SceneTank
add log message:

        void Start()
        {
            Debug.LogWarning($"{name} hasAuthority={hasAuthority} isOwned={isOwned} authority={authority}");
        }

it works properly for the player's tanks.
for the NPC in the scene, it's always false.
even though server owns it.

fix incoming:

@miwarnec Why is it still not fixed in release version?


[DSL] Language extension - arrays

We should be able to define arrays/lists of objects (e.g. for instantiating multiple monsters in a room).
Estimated work requirements

extend grammar

array definition
array member access

include arrays in type system
include arrays in DSLInterpreter
include in semantic analysis

#Time:6

Wie in https://github.com/Programmiermethoden/Dungeon/pull/693 in der Beschreibung zu Multiple Choice Aufgaben erläutert, sollten Arrays leer sein können.


media-src is not included in the contentSecurityPolicy default

Hi, I keep getting error regarding media-src not explicitly set. The documentation shows that media-src is not included in the contentSecurityPolicy default. Can you please include this? Thanks.

Yup, we should definitely get this added! Thanks, @april-ctrlspire! 😁


Don't show index-pattern creation form once created when viewing surrounding docs

Description
Currently once the index pattern gets created, the state is not getting updated correctly due to which if the user returns to the finding flyout and clicks view surrounding documents button again, we don't find the indexPatternId for the pattern just created and end up asking user to create the index-pattern again but since the pattern already exists the creation fails silently and user gets stuck.
The change in this PR ensures we re-render the flyout with the new state after index pattern creation so that the next surrounding doc button click directly opens the discover window
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Passing UTs:


64 automatic dark mode for pictures

I implemented the \picDark command from the SPL slides. It can be used to include images using \pic but automatically inverting them in dark mode (white gets inverted to a dark gray that matches the slide background).
This therefore closes issue #64.

Demo file misses the case of "-dark" files.

@tthuem I updated the example in the demo slides accordingly. It now mentions the option to use "-dark" files in the explanation.

Fine with me. You might want to squash all commits into a single commit.


Deploy dockerised playground

q4:

[x] install dockerised playground
[x] update monit check

proxy:

[x] configure proxypass https://test.metafacture.org/playground/ to q4
[x] add q4 as a member to balancer in hot standby

q3:

[x] archive current install
[x] install docker + docker compose
[x] install dockerised playground
[x] update monit check

proxy:

[x] set q4 as main balancermember, q3 + q1 in hot standby

q1

[x] archive current install
[x] install docker + docker compose
[x] install dockerised playground
[x] update monit check

@dr0i @fsteeg all instances are now running with Docker.