[DSIP-74] optimize workflow-related displays and filters

Search before asking

[X] I had searched in the DSIP and found no similar DSIP.

Motivation
Workflow Timing：Currently the timer management does not show who created the timer task, so without executing the task it is not known who created it, is it necessary to show the creator and modifier options?
Workflow Definition：The current filters defined in the workflow are too simple, is it possible to add filters for status, timed status, and time?
These are my thoughts, let's see if you agree and I'll work on optimizing them if possible
Design Detail
Workflow Timing：

When creating timed options, it's easy to see who created and modified the
Workflow Definition：

This is not only limited to workflow name queries, but can also be customized based on status, etc.
Increase the user-friendliness better with the above tweaks
Compatibility, Deprecation, and Migration Plan
Compatibility with latest version.
Test Plan
Test by UT.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I'm +1 on Workflow Definition.
For Workflow Timing, Considering that there are many fields displayed on the page now, adding two more fields is not so necessary, which is not very friendly to users with smaller resolutions. It would be better if there could be a better solution for this piece.

I'm +1 on Workflow Definition.
For Workflow Timing, Considering that there are many fields displayed on the page now, adding two more fields is not so necessary, which is not very friendly to users with smaller resolutions. It would be better if there could be a better solution for this piece. For example, add a field option for the user to choose the display field. By default, we only show high priority fields.
This program can be a good solution to the problem of many fields, the user can customize the choice of fields to display, you can look at this moving picture

I'm +1 on Workflow Definition.
For Workflow Timing, Considering that there are many fields displayed on the page now, adding two more fields is not so necessary, which is not very friendly to users with smaller resolutions. It would be better if there could be a better solution for this piece. For example, add a field option for the user to choose the display field. By default, we only show high priority fields.

This program can be a good solution to the problem of many fields, the user can customize the choice of fields to display, you can look at this moving picture

This program can be a good solution to the problem of many fields, the user can customize the choice of fields to display, > you can look at this moving picture

Yes. That's what I mean.

This program can be a good solution to the problem of many fields, the user can customize the choice of fields to display, > you can look at this moving picture

Yes. That's what I mean.

For the optimization points I mentioned above, I make the following adjustments, see below

But for the column name dynamic display and hide (I am a front-end white, to achieve this for me a bit of a struggle), found that put in a bit out of place feeling, I feel that is not should be a single out of a pr, for the function of the field more than a little optimization of the unity of a little better, I would like to listen to your views?

But for the column name dynamic display and hide (I am a front-end white, to achieve this for me a bit of a struggle), found > that put in a bit out of place feeling, I feel that is not should be a single out of a pr, for the function of the field more than a > little optimization of the unity of a little better, I would like to listen to your views?

You can just achieve the Workflow Definition part of this issue. And The Workflow Timing part is waiting for other contributors to realize.

But for the column name dynamic display and hide (I am a front-end white, to achieve this for me a bit of a struggle), found > that put in a bit out of place feeling, I feel that is not should be a single out of a pr, for the function of the field more than a > little optimization of the unity of a little better, I would like to listen to your views?

You can just achieve the Workflow Definition part of this issue. And The Workflow Timing part is waiting for other contributors to realize.
I'm going to add status filtering and corresponding creator and modifier logic to the workflow timings, can the front-end not show them for now, or are they not necessary?

But for the column name dynamic display and hide (I am a front-end white, to achieve this for me a bit of a struggle), found > that put in a bit out of place feeling, I feel that is not should be a single out of a pr, for the function of the field more than a > little optimization of the unity of a little better, I would like to listen to your views?

You can just achieve the Workflow Definition part of this issue. And The Workflow Timing part is waiting for other contributors to realize.

I think it's a good idea to add this to these.

 I think it's a good idea to add this to these.

I think this is unnecessary especially in prod environment.

 I think it's a good idea to add this to these.

I think this is unnecessary especially in prod environment.

Okay, then in read more of the other comments, otherwise writing and not passing is the same as not writing at all😂

I've just described the adjustments, take a look, anything else you want to add? @SbloodyS @ruanwenjun


Problem Select

I was trying to make the layout more user friendly to accomodate the backend changes, but found a problem.
The bootstrap select is incorrectly themed, your version:

The original select bootstrap template adminlte that i want:

What changes can I do to make it right.

It's not incorrectly themed. It's theme used. Use CSS.


Update generated source code

Automated PR triggered by new code generation.
Update generated source code
Generated SDK source code using:

Generator version 3.30.0
Specification version 1.0.0-dev0.0.36
Automation (cloudant-sdks) version 1b682fd

This change is already merged with PR https://github.com/IBM/cloudant-python-sdk/pull/106


don't display all keys in left

OS
Windows
VERSION
1.5.2
ISSUE DESCRIPTION
no display all keys on diagram

display all keys by search

click load more button, or enable load all in setting

need update to new version(1.5.5), will have the switch


Make sure we validate simple syntax on service commands

We ignored errors for simple syntax in PortOpt (missed that in the previous migration of this code 🐻). This make sure we don't ignore nat.Parse errors.
Test has been migrate too (errors are not exactly the same as before though -_-).
/cc @thaJeztah @AkihiroSuda @icecrime @dnephin @mavenugo @aaronlehmann
🐸
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

@vdemeester need rebase, not sure if still actual

@LK4D4 rebased and yeah, still actual 👼

@vdemeester what do you think about @dnephin suggestion?

@LK4D4 I have to take care of it 👼 😝

ping @dnephin


Pipe "Rile: xxx" and similar thing into standard error stream?

Could you please consider printing meta information like Role: xxx  into stdnard error stream, so one can pipe : cat a | sgpt '....' | tee b ?
(of at least to make it via flag --meta-on-stderr  or disable via flag e.g. --silent ?)

Closing this issue due to its age and lack of similar reports/requests from other users.


Wrong block hash?

Not sure what's going on here, but i'm grabbing the last block from the db like so:
carp_mainnet=# SELECT * FROM "Block" ORDER BY "Block".id DESC LIMIT 1;
-[ RECORD 1 ]---------------------------------------------------------------
id      | 169013
era     | 0
hash    | \x869b30014807b9b158c8d24fb406deea93f39893169dc47c32a2cb6e6f642e2d
height  | 169012
epoch   | 7
slot    | 169043
payload | \x

As you can see here, it says the block hash is 869b30014807b9b158c8d24fb406deea93f39893169dc47c32a2cb6e6f642e2d. I looked up block 169012 on CardanoScan, but this is not the correct hash. The slot is however correct (169043).
Link for the block here on CardanoScan https://cardanoscan.io/block/169012
When I try to start Carp it gives the following error:
2024-03-03 13:27:18 Applying all pending migrations
2024-03-03 13:27:18 No pending migrations
2024-03-03 13:27:18 2024-03-03T18:27:18.127946Z  INFO carp: Starting Carp
2024-03-03 13:27:18 2024-03-03T18:27:18.128009Z  INFO carp: Execution plan execution_plans/default.toml
2024-03-03 13:27:18 2024-03-03T18:27:18.128140Z  INFO carp: Config file PathBuf { inner: "/app/config/indexer/oura_docker.mainnet.yml" }
2024-03-03 13:27:18 2024-03-03T18:27:18.134168Z  INFO carp::sources::oura_source: Starting sync at block #169043 (869b30014807b9b158c8d24fb406deea93f39893169dc47c32a2cb6e6f642e2d)
2024-03-03 13:27:18 2024-03-03T18:27:18.134187Z  INFO carp::sources::oura_source: Attempting to connect to node...
2024-03-03 13:27:18 2024-03-03T18:27:18.134434Z  INFO carp::sources::oura_source: Connection to node established
2024-03-03 13:27:18 2024-03-03T18:27:18.134648Z  INFO carp::engine: Starting to process blocks
2024-03-03 13:27:18 2024-03-03T18:27:18.136230Z ERROR oura::sources::n2c::run: N2C error: Can't find chain intersection point
2024-03-03 13:27:18 2024-03-03T18:27:18.136245Z  WARN oura::sources::n2c::run: unrecoverable error performing chainsync, will exit
2024-03-03 13:27:18 2024-03-03T18:27:18.136447Z ERROR carp: Processing loop finished with error, stopping engine error=Can't fetch oura event: RecvError
2024-03-03 13:27:18 2024-03-03T18:27:18.136491Z  INFO carp: Engine is stopped successfully

It crashes I assume because the block hash doesn't match what's in the Cardano Node?
Any ideas what might be going on here?

Hey @rooooooooob is this now resolved? Should I close this issue?

It's resolved in CML. I don't think carp has bumped the dependency version yet, it looks like it's still on CML 5.0.0. The fix is in 5.2.0. I believe that means that it might be fixed as "5.0.0" can use anything from that onwards but before 6.0.0, but it would depend which version is installed and used by cargo. I might be misunderstanding cargo's versioning behavior though. We should bump it in carp too. @ecioppettini


should we use web link to generate it?

@oshada97 I don't understand the purpose of this issue...Please open an issue with a correct format and description so I can help you.


wprecon: init at 1.6.3a

Motivation for this change
WordPress vulnerability recognition tool
https://github.com/blackbinn/wprecon
Related to #81418
This tool is licensed under License Zero Noncommercial Public License 2.0.1.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 120090 run on x86_64-linux 1

1 package built:

wprecon


Verify workarounds for ZMQ failure

Since this is a key part of local launch we want to be really careful with ZMQ. In the case of some type of ZMQ error we should be very explicit about how it can be worked around. Presumably by exiting the experiment or starting a local server. No explicit costing here, but an item to make sure that we check this before release.

We want to know whether ZMQ fails. So nothing to be done here. We have telemetry that will tell us where we're at.


Change to scrolling bar position

Right now our scrolling bar is taking the full height of vaadin-grid component. Can we make it not to overlap with header? As our header will never be transparent and it will be always fixed, we really do not have case were we would scroll it.
I do understand that this might become tricky issue.
See "Scrolling general" and "Scrollbar extends over header" parts on PDF at ticker #89

Change Notice signed, this way stay as wontfix.


re-run failed sql scripts after a failed migration?

I got a problem when sql scripts failed.
I cannot run the fixed sql scripts directly.
what I have to do now is I have to run repair command first. and then migrate.
but what  I want is that when i fix the scripts it can automatically run failed scrips without "repair command"
because the repair command will update all checksum value. if somebody update other sql scripts in the same time.
some bad thing will happen in production.

You could run validate to see if the expected scripts have a checksum mismatch. If everything looks as expected, then you can run repair without concern of incorrectly overwriting script checksums.
Does that help?

You could run validate to see if the expected scripts have a checksum mismatch.
the problem is if i check it manually it will lose the meaning of CI\CD
so I just think a  trick, i'm not sure if it work.
can i just add a callback before validate and use the callback to delete the failed record from flyway_sheme_history.
then everything i do fly migrate it will delelte the failed record and run the sql scripts without flyway repair

We've shipped a paid feature called cherry pick in Flyway 7 beta. It allows you to specify exact scripts to operate on. Currently it only supports migrate, but in light of this issue we've scheduled some work to add repair also. Keep an eye out for future releases.
In the meantime I think your workaround is a good option.


Fixed some wording, grouped access info together

Also includes what's in https://github.com/redhat-appstudio/infra-deployments/pull/718/

/unhold
I'm curious how this might work (or not)

/unhold

I'm curious if that unhold will make Tide merge this?

It did auto-merge.  Cool.


Update README with Firebase platform support info

Adding a section in the readme to point to the docs for a source of truth on firebase's platform support.

How about deleting the table on this page too?  The usage information is covered elsewhere.


How to uninstall lab properly

I'm wondering how to uninstall lab properly. There is a guide about this issue?

See README.md
Please remove config file.
The config file path is $HOME/.config/lab/config.yml.

Thank you, so removing the configuration file is enough or I should also remove the binary?

If you only want to delete the secret credential of the lab command, deleting the config file is sufficient.
If you want to delete the binary, type $ which lab on the command line to delete the displayed file.
This is a general linux/unix procedure.

thanks for your support!


Support for XmlPath syntax in Node

From<EMAIL_ADDRESS>on March 30, 2011 12:11:37
When having got a Node from XmlPath it should be possible to use XmlPath syntax from the Node.
E.g.
String href = node.get("link.@href");
One way to implement this would be to store the XmlPath (e.g. "x.y") in the Node object. When doing "node.get("link.@href")" we could just append the "link.@href" to the "x.y" (i.e. x.y.link.@href) and return the result.
Original issue: http://code.google.com/p/rest-assured/issues/detail?id=57

From<EMAIL_ADDRESS>on March 30, 2011 03:33:50
This should also apply to NodeChildren

From<EMAIL_ADDRESS>on November 13, 2013 23:01:25
Status: Fixed


Review prerequisites

Context
This is to review the list of requirements for Macs.
Some requirements are redundant, while others don't apply.
The section should say what the prerequisites enable the user to do.
Changes proposed in this pull request
The PR proposes removing the requirement:
"You must also have a GitHub account [external link] with access to alphagov at https://github.com/alphagov/paas-tech-docs."
The link does not make sense and there is no need for access to alphagov to use and contribute to the TDT. Also users don't even need a GitHub account if they just want to use the TDT.
Remove the requirement for a text editor since all laptops come with some form of text editor. If this is more of an on-boarding guide for people at GDS, we should make it clear and suggest getting Atom or some other editor.

If the TDT docs are intended as general documentation for using the tool, we should remove GDS-specific information. If it's intended to be an onboarding guide for GDS tech writers, then we can keep that information.


Refactoring

Pull created by bissquit at 2023-02-20T11:59:08Z

Not tested yet, continue working on it
Comment created by bissquit at 2023-02-20T12:00:27Z

Assignee is {'login': None}


Add "types" field to package.json "exports"

In TypeScript 4.7, the nodenext and node16 module resolution options were added to better support native ESM in Node.js. When the package.json "exports" field exists, however, they require a "types" field to exist within each entrypoint, or else types won't be resolved when using one of these module resolution options.
Currently, using this library with either of those settings throws the following TypeScript error:
error TS7016: Could not find a declaration file for module '@splinetool/react-spline'. <EMAIL_ADDRESS>implicitly has an 'any' type.
  Try `npm i --save-dev @types/splinetool__react-spline` if it exists or add a new declaration (.d.ts) file containing `declare module '@splinetool/react-spline';

This PR fixes this issue by adding the "types" field to "exports" for the "./" entrypoint. The same change is required for @splinetool/runtime, but I couldn't find a link to a repository where I could submit the change.

Hey @futurGH, could you share your setup? I've just tried using react-spline with Typescript 4.8.2 via create-react-app and it worked no problem.
Shouldn't it fallback to the root "types" field in package.json?

Thanks for looking into this @marcofugaro. You can find a better explanation of this issue than I'm capable of at microsoft/TypeScript#46334. Essentially, the top-level "types" field only applies when importing from "main". When you compile to native ESM and use "nodenext" or "node12" for TS' module resolution, it instead defaults to the "." import map, which requires its own "types" field, as TS won't look up the top-level "types" field if it's not looking at the "main" field as the entrypoint.

Right, thanks for linking to the conversation.

Thanks for merging this! I'd also appreciate if a similar change could be made to the @splinetool/runtime package; I don't believe the source for the package is public for me to submit a PR to?

@futurGH a new version of @splinetool/runtime with this fix will be published early next week


Email + Sendgrid

To help with Docker Deployments, I suggest switching to the REST API for Sendgrid, and just calling for the API Key, Interfacing with Sendgrid's API is pretty stupid easy
Most providers block all the ports you would use for the SMTP versions of sendgrid

I had envisioned the docker deployments using Gmail, or something else.  The config isn't that hard to modify, and it's primarily geared toward Heroku deployments (as stated in the README).  If you've found a way to easily modify the config to support both, please feel free to submit a PR, or document your process in the wiki.

Should be too bad, I'll brush up on my ruby


Update Dependencies

Updates dependencies to latest version
Fixes clippy issues
Fixes cargo build --no-default-features --features="alloc" issue (Vec was not imported)

Unfortunately, this does seem to break the encryption tests, although not the decryption ones, not sure what's up with that.

@bhgomes Hi! Thank you for the PR, I'll check it out.

@bhgomes This #11 should fix your issue. Alas, coverall.io is down the whole day, thus the build fails on the coverage check.
Is there any particular reason to upgrade cryptographic dependencies? I think it might cause the encryption test to fail (I suspect a difference in random seed generation).

Thanks for reviewing! The reason I wanted to upgrade was to try and get crates like zeroize and rand up to the latest versions to make cocoon compatible with other crates that use those two crates. rand is particularly necessary since cocoon exposes RngCore, CryptoRng, StdRng, and ThreadRng in its public API. Using the very old versions of the crypto crates didn't allow me to upgrade those dependencies.
Also, I think it's generally unwise to use super old versions of cryptography crates, especially ones that have deprecated features. If there's no way to fix the seeding changes (not sure if it's possible since StdRng was changed from ChaCha20 to ChaCha16 for example) then a semver bump is necessary to keep old cocoon users compatible without breaking their encryption.

since cocoon exposes RngCore, CryptoRng, StdRng, and ThreadRng in its public API.

Oh, right, what a mistake from my side, I should've hidden RNG inside. Hm... Let me publish a fix of the build first. Then I'm going to create a version 0.3.0 with incompatible API (without RNG templated parameter). In fact, most users wouldn't see any problem unless they specified templated Cocoon  explicitly in their code (e.g. Cocoon<'a, StdRng, Creation>).
What do you think?

I think that's definitely a good idea. Not sure if that will fix packages that use cocoon and still want to use the latest version of rand and zeroize, I would have to run some tests. But that at least is a good issue to fix.
Any reason other than the breaking tests why you would not want to upgrade to the latest versions for crypto packages?
BTW: The cargo-outdated tool is pretty invaluable in discovering issues like compatibility with newer versions of packages.

@bhgomes Once it becomes compatible for you (with the latest rand) it becomes incompatible for others (in a case when somebody uses the current rand). So I would make cocoon incompatible for many things altogether in a new version. Thanks for cargo-outdated.

I think to fix the dependency issues, since you are going to remove the rand dependencies from the API, we should transfer everything to rand_chacha::ChaCha20Rng that way we can update and still pass the encryption tests. Also, it's guaranteed to be the same into the future. After reviewing the code it seems to me that that's the only reason for the breaking changes.

Done: PR #12


globalToLocal broke between 3.2.2 and 3.3.1

I have some nested sprites that respond to mouseevents, but for some reason the non-Flash clients have stopped returning correct values for globalToLocal().
Note that this was working correctly in 3.2.2 on all targets. I first noticed the bug in 3.3.0.
Here's some trace output from the Flash code. If I click near the upper-left of the screen, a sprite far away from the click ("world inventory") transforms the global coordinate to local and throws out the event, as the click happened far away.
Entity.hx:1805: global is (x=22.8, y=32.85)
Entity.hx:1807: local is (x=321, y=-440.7)
Entity.hx:1892: world inventory mouseup returns false

The same code running in the HTML5 or C++ target does not correct for the sprite's position. It just returns the same coordinate.
(HTML5 output)
Entity.hx:1805: global is (x=28, y=52)
IconiQuest1.js:10678 Entity.hx:1807: local is (x=28, y=52)
IconiQuest1.js:10678 Entity.hx:1892: world inventory mouseup returns true

(C++ output)
Entity.hx:1805: global is (x=30, y=56)
Entity.hx:1807: local is (x=30, y=56)
Entity.hx:1892: world inventory mouseup returns true

Verified fixed. Much thanks.


fix: hard code bucket location

Description
When the location is loaded from environment secrets, it causes strings to be obfuscated. In the worst case, location: us, every word with us in it will be starred like so: ref**ed. That is annoying and unnecessary, therefore we simply hard code the bucket location.
Checklist

[x] Investigated and inspected CI test results
[x] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
CI
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/retest


Build behaves differently between Vive HMDs

I have published a build from Unity 2019.1.0f2 running on the Vive Pro.
The build has various UI HUDs that appear during the game. These canvasses are set "Screen Space - Camera" and Render Camera is the Steam "VR Camera".
This runs perfectly from the Unity editor and also in the published build.
When I run this on the Vive (not Pro) the UIs do not appear.
Debugging back in Unity shows the UIs to be in a closer space to the Vive, so nothing appears. Plug the Vive Pro back in and all is good?
With the Vive Pro plugged in the canvas originates at Z0.994. At runtime this moves to Z-5.264.
With the Vive plugged in the canvas again originates at Z0.994. At runtime this only moves to Z-1.066!
So, the issue is somehow the recognition of the different headset and the amount the canvas moves.
Attached screenshots are from Unity editor. The only difference is changing between the Vive and the Vive Pro, then restarting the headset in SteamVR. No other settings are changed.
The Z length difference between the UI and the VR camera is noticeable.

.

They have different resolutions. If you're positioning elements absolutely
it may be off the screen in the vive.
On Thu, Oct 3, 2019 at 12:29 AM craigsimpson13<EMAIL_ADDRESS>wrote:

I have published a build from Unity 2019.1.0f2 running on the Vive Pro.
The build has various UI HUDs that appear during the game. These canvasses
are child objects of the VR Camera. This runs perfectly from the Unity
editor and also in the published build.
When I run this on the Vive (not Pro) the UIs do not appear.
Debugging back in Unity shows the UIs to be in the same space as the Vive,
so nothing appears. Plug the Pro back in and all is good?
Do these different HMDs occupy different spaces?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/steamvr_unity_plugin/issues/541?email_source=notifications&email_token=AABQQMHPGCFCJLKTDCNPDVLQMWNOZA5CNFSM4I47ONLKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HPKMBFA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABQQME4YLL5BD5HSZKPDXLQMWNOZANCNFSM4I47ONLA
.

@zite Thank you.
I have changed the canvas scaler to maintain UI size and tested on different headsets, now okay.


Ignore NIC configuration on EC2 deployments

Description
When using hybrid VM templates the NIC attribute -which must be interpreted on KVM deployments- is taken into account on EC2 deployments.
To Reproduce
Create and hybrid VM template with a NIC attached to a Virtual Nework with VN_MAD=fw and start the VM on a EC2 node. An error similar to this will occur:
Wed Jun 3 16:23:00 2020 [Z0][VMM][I]: iptables v1.6.1: interface name --physdev-is-bridged' must be shorter than IFNAMSIZ (15) Wed Jun 3 16:23:00 2020 [Z0][VMM][I]: Try iptables -h’ or ‘iptables --help’ for more information.
Wed Jun 3 16:23:00 2020 [Z0][VMM][E]: post: Command Error: sudo iptables -I opennebula -m physdev --physdev-out --physdev-is-bridged -j one-315-0-i
Wed Jun 3 16:23:00 2020 [Z0][VMM][E]: post: ["/var/lib/one/remotes/vnm/command.rb:61:in block in run!'", "/var/lib/one/remotes/vnm/command.rb:58:in each’", “/var/lib/one/remotes/vnm/command.rb:58:in run!'", "/var/lib/one/remotes/vnm/security_groups_iptables.rb:485:in nic_pre’”, “/var/lib/one/remotes/vnm/sg_driver.rb:92:in block in activate'", "/var/lib/one/remotes/vnm/vnm_driver.rb:81:in block in process’”, “/var/lib/one/remotes/vnm/vm.rb:64:in block in each_nic'", "/var/lib/one/remotes/vnm/vm.rb:63:in each’”, “/var/lib/one/remotes/vnm/vm.rb:63:in each_nic'", "/var/lib/one/remotes/vnm/vnm_driver.rb:84:in process’”, “/var/lib/one/remotes/vnm/sg_driver.rb:84:in activate'", "/var/lib/one/remotes/vnm/fw/post:32:in '”]
Wed Jun 3 16:23:34 2020 [Z0][VMM][I]: Successfully execute virtualization driver operation: cancel.
Wed Jun 3 16:23:34 2020 [Z0][VMM][I]: Failed to execute network driver operation: post.
Wed Jun 3 16:23:34 2020 [Z0][VMM][E]: Error deploying virtual machine: fw: -
Wed Jun 3 16:23:34 2020 [Z0][VM][I]: New LCM state is BOOT_FAILURE

Expected behavior
The NIC configuration should only be used in hybrid VM templates for KVM deployments.
Details

Affected Component: Core
Hypervisor: KVM
Version: development

Additional context
Forum issue.

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

Bug also applies for Azure driver.


Feature: I would like a method for filtering jobber log

I have a task which runs frequently (every few seconds) and I would still like to see the information about the slower running jobs. The issue is that they are being drowned by the spammy tasks.

Is this something that you could use grep for?

It is.

Is grep adequate?

Actually, yes. When I posted this I was thinking more in terms of Jobber doing it for me but I can pipe the output into grep easy enough.


Running start.rb results in an error

Running start.rb after cloning the project results in a Ruby error.
operating system info etc
ruby version etc
$ ruby start.rb
bash: ruby: command not found

Treehouse


Internal Debugger Error: UnboundLocalError: local variable 'var' referenced before assignment

Which OS: 10.13.4
Which extension version:  0.8.5
Which LLDB version:  lldb version 6.0.0
Which VSCode version:   Version 1.22.2 (1.22.2)
What is the problem and how did you get there: debugging rust code
Internal debugger error:
Traceback (most recent call last):
File "/Users/jyavenard/.vscode/extensions/vadimcn.vscode-lldb-0.8.5/adapter/debugsession.py", line 1239, in handle_message
result = handler(args)
File "/Users/jyavenard/.vscode/extensions/vadimcn.vscode-lldb-0.8.5/adapter/debugsession.py", line 854, in DEBUG_variables
dtype = var.GetTypeName()
UnboundLocalError: local variable 'var' referenced before assignment
Internal debugger error:
Traceback (most recent call last):
File "/Users/jyavenard/.vscode/extensions/vadimcn.vscode-lldb-0.8.5/adapter/debugsession.py", line 1239, in handle_message
result = handler(args)
File "/Users/jyavenard/.vscode/extensions/vadimcn.vscode-lldb-0.8.5/adapter/debugsession.py", line 854, in DEBUG_variables
dtype = var.GetTypeName()
UnboundLocalError: local variable 'var' referenced before assignment

Should be fixed in 0.8.6


Experimental Features

Description
can't check of the default file explorer option in experimental features!
i also have backed up my reg keys but cant import them or reset them.
i also do not want to reset my whole pc!
Steps To Reproduce
No response
Expected behavior
it has to check of and i have to be able to get back to the original file explorer!
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22000.348
Windows Version
Edition	Windows 11 Pro Version	21H2 Installed on	2021-10-27 OS build	22000.348 Experience	Windows Feature Experience Pack 1000.22000.348.0
Relevant Assets
No response

Hi @ethandii , you have to follow the instructions here to unset as default file explorer:
https://files.community/docs/configuring/replace-file-explorer
TL;DR: download this zip and run UnsetFilesAsDefault.reg to restore windows explorer


Add github actions ci workflow

Convert to GitHub Actions for CI
Ticket: https://www.pivotaltracker.com/story/show/186493694

@robwadge Yeh. I had a moment where I thought I needed a workflow in main to make this work, then spotted I'd used the wrong directory :upside_down_face:

@philipnbbc has reviewed https://github.com/bbc/rd-apmm-python-lib-rtpPayload_ttml/pull/7 which has the same tox changes. Shall assume that that review + @robwadge's on this PR means we're happy with all the changes.


Stake CW20 Rewards

Picked up the TODOs left on PR #164.

Added a query pending rewards route.
Pulled in Main as the current stake-cw20-rewards was using an older version of the stake-cw20 contract. (That's why other commits are listed under this PR)
Added integration tests

Checks initial config setup
Checks funding
Checks rewards
Checks compounding each block
Checks invalid claim rewards calls

Feedback appreciated.

Upstream PR needs a rebase, then it will be easier to review this. CC @ben2x4. :pray:

@ezekiiel / @Callum-A, is this PR still relevant? It's been open for a while.

Yolo.


feat: implement source

I am not sure about the exact semantics. Currently, everything that is modified in the sourced' script is also going to be modified in the parent script.

Probably time to fix https://github.com/prefix-dev/shell/issues/82. :) And define the exact semantics with tests, and we can always check that Bash behaves the same way.
I think the current semantics is correct, I think sourcing a script is equivalent to copy & pasting the script into the parent script and execute there.

I tested this on Windows and it works! I can now load ~/.shellrc to load paths for pixi and my ~/bin directory.
I think this unblocks me, I can now create scripts for various conda environments, and this might be all that was needed to start using shell for my daily work.

Found a bug: https://github.com/prefix-dev/shell/issues/113.


Incompatibility with phpunit 8

using matthiasnoback/symfony-dependency-injection-test v3.1.0
PHP Fatal error:  Declaration of Matthias\SymfonyDependencyInjectionTest\PhpUnit\AbstractContainerBuilderTestCase::setUp() must be compatible with PHPUnit\Framework\TestCase::setUp(): void in [...]/vendor/matthiasnoback/symfony-dependency-injection-test/PhpUnit/AbstractContainerBuilderTestCase.php on line 221

This is fixed in master.

Could you release stable version? :)


Http 409 Conflict when running two brokers

Describe the bug
Pulsar throws "HTTP 409 Conflict: Subscription already exists for topic" when you launch 2 brokers. Sometimes it fails with "Failed to fence subscription" as well. And sometimes weird 500 internal server error. I handled it by putting this line in try-catch: https://github.com/apache/pulsar/blob/master/pulsar-functions/worker/src/main/java/org/apache/pulsar/functions/worker/WorkerService.java#L185
brokerAdmin.topics().createSubscription(coordinationTopic, MembershipManager.COORDINATION_TOPIC_SUBSCRIPTION, MessageId.earliest);

To Reproduce
Steps to reproduce the behaviour:

Launch 1 zookeeper, 2 bookkeeper and 2 pulsar containers on docker. My test environment is distributed among 3 physical hosts so the container can land anywhere. Easily reproducible on the non-dockerized environment as well.

Expected behaviour
Should start successfully without any error.
System info

Zookeeper: 3.6.1
Bookkeeper: 4.10.0
Pulsar: 2.6.2
OS: ubuntu18.04

@abhilashmandaliya Are you interested in contributing a fix?

yes but I am not sure where to fix this. will need some guidance from you people

Closed as stale. Please create a new issue if it's still relevant to the maintained versions.


EF sqlite package include: Ensure last package installs

Internal Review: First Razor
Internal Review: First MVC
When CLI code in a doc includes multiple command lines, the last command does not execute.  In this case, the include several docs use for installing EF + SQL Server and SQLite has this issue.
Adding " && " after each CLI command to tie them together so they all run.

This was a draft since I had to test out if this suggestion worked to get around the issue of Powershell not running the last line when a list of commands are copy pasted from the doc.  It didn't.  If you try using " && /" at the end of each command to tie the commands together it still does not work for Powershell which was the problem scenario to address to begin with.
Closing this draft.


Added relative calculations to a few effects.

This allows a move to be rotated on all of it's axes. Also offsetted based on the player's view

Thank you for this! I've added your new vector rotation methods, and relativeOffset (a Vector) parameter as well as yawOffset and pitchOffset parameters.
I was hesitant to take the changes to specific effect logic- that stuff scares me, we'd have to make some kind of regression test to ensure behavior didn't change. I'm hoping the yaw/pitch offsets get it most of the way there, though?
I had to pull all the changes piecemeal, so I'm closing this PR- please see my latest commits, if you need more to do what you wanted we can discuss! :)


[Bug]: Data cleaning task failed, log printing syntax error

ODC version
ODC422
OB version
it has nothing to do with ob version
What happened?
Data cleaning task failed, log printing syntax error

What did you expect to happen?
normally
How can we reproduce it (as minimally and precisely as possible)?
See Private Cloud Environment
Anything else we need to know?
No response
Cloud
No response

Compatibility issues caused by MYSQL 8.x are supported by DLM, and are expected to be fixed in SDK 1.0.5.


Running example error

E/AndroidRuntime( 8161): java.lang.UnsatisfiedLinkError: dlopen failed: library "libDeviceAPI.so" not found
E/AndroidRuntime( 8161): 	at java.lang.Runtime.loadLibrary0(Runtime.java:1087)
E/AndroidRuntime( 8161): 	at java.lang.Runtime.loadLibrary0(Runtime.java:1008)
E/AndroidRuntime( 8161): 	at java.lang.System.loadLibrary(System.java:1664)
E/AndroidRuntime( 8161): 	at com.rscja.deviceapi.DeviceAPI.(DeviceAPI.java:2292)
E/AndroidRuntime( 8161): 	at com.rscja.deviceapi.DeviceAPI.getInstance(Unknown Source:0)
E/AndroidRuntime( 8161): 	at com.rscja.deviceapi.RFIDWithUHFUART.getDeviceAPI(RFIDWithUHFUART.java:52)
E/AndroidRuntime( 8161): 	at com.rscja.deviceapi.RFIDWithUHFUART.init(RFIDWithUHFUART.java:92)
E/AndroidRuntime( 8161): 	at com.amorenew.c72.uhf_plugin.helper.UHFHelper.connect(UHFHelper.java:74)
E/AndroidRuntime( 8161): 	at com.amorenew.c72.uhf_plugin.UHFPlugin.handleMethods(UHFPlugin.java:204)

Hey did you solve this problem ?

Hey did you solve this problem ?

Hey did you solve this problem ?
I just saw the comment, sorry for that, it's been so long that I've already forgoten how I resolved it but I'm using my personal fork which should works. I've tested it 2 weeks ago
you may use my fork here

thanks for the replay,
i get these errors:
I/DeviceAPI_UHF(27306): init() Uart = /dev/ttyMT3
E/DeviceAPI_UHF(27306): init() err UHFOpenAndConnect result:-1
E/DeviceAPI_UHF(27306): setFrequencyMode() err :-1
E/DeviceAPI_UHF(27306): setPower() err :-1
E/DeviceAPI_UHF(27306): startInventory() err :-1

thanks for the replay,
i get these errors:
I/DeviceAPI_UHF(27306): init() Uart = /dev/ttyMT3 E/DeviceAPI_UHF(27306): init() err UHFOpenAndConnect result:-1 E/DeviceAPI_UHF(27306): setFrequencyMode() err :-1 E/DeviceAPI_UHF(27306): setPower() err :-1 E/DeviceAPI_UHF(27306): startInventory() err :-1

this means connection to uhf device error, did you test it on uhf device?
You may try these:

try to use the test software of your uhf device, make sure your device is working fine. Or you may restart your uhf device and try again.
did you init the program?

here are some example:
`
@override
void initState() {
super.initState();
initPlatformState();
}
Future initPlatformState() async {
String? platformVersion;
// Platform messages may fail, so we use a try/catch PlatformException.
try {
platformVersion = await UhfC72Plugin.platformVersion;
} on PlatformException {
platformVersion = 'Failed to get platform version.';
}
UhfC72Plugin.connectedStatusStream
.receiveBroadcastStream()
.listen(updateIsConnected);
UhfC72Plugin.tagsStatusStream.receiveBroadcastStream().listen(updateTags);
await UhfC72Plugin.connect;
await UhfC72Plugin.setWorkArea('2');
// await UhfC72Plugin.
await UhfC72Plugin.setPowerLevel(power);
// If the widget was removed from the tree while the asynchronous platform
// message was in flight, we want to discard the reply rather than calling
// setState to update our non-existent appearance.
if (!mounted) return;
setState(() {
  _platformVersion = platformVersion!;
});

}
String power = '30';
double _elevation = 3;
String _platformVersion = 'Unknown';
bool _isStarted = false;
bool _isEmptyTags = false;
bool _isConnected = false;
List _data = [];
void updateTags(dynamic result) async{
await UhfC72Plugin.clearData;
TagEpc.parseTags(result).forEach((element) {
String epc = element.epc;
if(!_data.contains(epc)){
setState(() {
_data.add(epc);
});
epc = epc.substring(4,epc.length);
sendData(epc);
}
});
await UhfC72Plugin.clearData;
}
void updateIsConnected(dynamic isConnected) {
//setState(() {
_isConnected = isConnected;
//});
}
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
elevation: 0,
backgroundColor: theme.scaffoldBackgroundColor,
leading: InkWell(
onTap: () => Navigator.of(context).pop(),
child: Icon(FeatherIcons.chevronLeft,color: Colors.black,),
),
title: FxText.titleMedium("test page", fontWeight: 600),
),
body: Center(
child:Column(
children: [
Container(
child: InkWell(
onTap: ()async{
if(isSearching == false){
setState(() {
searchButtonText = 'searching tags...';
searchButtonColor = theme.colorScheme.error;
isSearching = true;
});
await UhfC72Plugin.clearData;
await UhfC72Plugin.startContinuous;
}else{
setState(() {
searchButtonText = 'start inventory';
searchButtonColor = theme.colorScheme.primary;
isSearching = false;
});
await UhfC72Plugin.stop;
}
              },
              child: AvatarGlow(
                glowColor: Colors.blue,
                endRadius: 90.0,
                duration: Duration(milliseconds: 2000),
                repeat: true,
                showTwoGlows: true,
                repeatPauseDuration: Duration(milliseconds: 100),
                child: Material(     // Replace this child with your own
                  elevation: 8.0,
                  shape: CircleBorder(),
                  child: CircleAvatar(
                    backgroundColor: theme.primaryColor,
                    child: Text(searchButtonText),
                    radius: 40.0,
                  ),
                ),
              ),
            ),
          ),

        ],
      ),
    )
);

}
`

@SilvesterLi I restarted the device and checked if the UHF worked in another application and it's working fine !!
but there is an error line said : "D/DeviceAPI_SerialPort(29097): [SerialPort_Open] [2]: No such file or directory"
and when searching for solution, I found some developers add the file "chainway.ketstore"
and included it in the girdle.build,
is there a step like this I have to do it?

@SilvesterLi I restarted the device and checked if the UHF worked in another application and it's working fine !!
but there is an error line said : "D/DeviceAPI_SerialPort(29097): [SerialPort_Open] [2]: No such file or directory"
and when searching for solution, I found some developers add the file "chainway.ketstore" and included it in the girdle.build,
is there a step like this I have to do it?

I don't think so because I've also tested the original push which is also fine on my chainway uhf device.
is your device made by chainway?
you may also try this library
  uhf_c72_plugin_2: ^0.2.6

@SilvesterLi I tried all libraries for UHF non of them works with me !
you can see the logs:
D/DeviceAPI( 6492): UHF uart = /dev/ttyMT3
D/DeviceAPI_SerialPort( 6492): [SerialPort_Open] [2]: No such file or directory
D/DeviceAPI( 6492): UHF uhf_uart_fd = -1
I/DeviceAPI_UHF( 6492): init() Uart = /dev/ttyMT3
the device is c72 made by chainway.
and after init() I get these logs :
E/DeviceAPI_UHF( 6492): init() err UHFOpenAndConnect result:-1
E/DeviceAPI_UHF( 6492): setFrequencyMode() err :-1
E/DeviceAPI_UHF( 6492): setPower() err :-1

@amorenew what is the version I have to use ?

@pokkeerr incompatible means you need a different library, Chinese makes different SDKs so use your native SDK to make a new plugin

@amorenew Thanks for your time :)

@amorenew  dear Mr.amorenew   I find this error ("E/DeviceAPI_UHF: init() err UHFOpenAndConnect result:-1") while running the demo app by android studio(NATIVE).
kindly check it and reply to me.

same this problem
https://github.com/amorenew/uhf_c72_plugin/issues/4#issuecomment-1236945435

@abdallahalhyari It looks like a different .so files(c++) implementation to connect to the hardware
Chinese keep making new SDKs and hardware over the time
So you could take this plugin as a guideline to make your own suitable implementation for your hardware


Remove params.ts and related logic from IF

Why: Sub of #761
What:  Remove params.ts and related logic from IF
prerequisites
IF must get aggregation information from context-level manifest config before params.ts is removed.
Scope of work:

[ ] Delete params.ts file from IF
[ ] Remove logic from IF that checks params.ts

Acceptance criteria

[ ] params.ts is removed from IF

[ ] IF runs as expected without params.ts being available
GIVEN params logic is removed from IF
WHEN I run the manifests in our examples and outputs folders
THEN all manifest execute as expected

@manushak @narekhovhannisyan please review AC to see if it all looks good

for this one please make sure that CLI custom params feature is also included

@narekhovhannisyan please review linked PR #911


How much compute for training the motion predictor?

Hi,
The motion predictor used 8 GPU cards for 3-4 days. In addition, we also train our self-owned motion module which uses 32 A100 GPU cards for one week. The motion predictor and the motion module is used together for the video result’s presented in the paper.

The main idea behind this way of video generation is to save the compute since image model is much more easier to train, compared to train a hyper-realistic video model directly.


return to 4200 block and empty wallet

Updates from  Sia-UI-v<IP_ADDRESS> to Sia-UI-v<IP_ADDRESS>-beta-win64.zip returns to  4000 block with empty wallet. Have to clean all wallet files and replace with original to return balance.

You were able to get back on to the main chain with your balance though?
I think this update was just rocky because the auto-updater does not work very well.


DBeaver does not allow anything after "jdbc:sqlserver://" in MS SQL Server URL template, breaking sqlexpress and localdb connections

Description
In DBeaver 22.1.1, the SQL Server URL template is something like
jdbc:sqlserver://;serverName=localhost;databaseName=testdb
For a lot of people, this isn't a problem, because they can just use the serverName parameter and port to connect via TCP/IP.
However, this breaks support for sqlexpress and localdb connections, which cannot be connected to with the serverName parameter. For these connections, the host must be inserted right after the jdbc:sqlserver:// bit. For example, a sqlexpress connection string looks like this:
jdbc:sqlserver://localhost\sqlexpress;databaseName=testdb;integratedSecurity=true;
Because DBeaver does not allow inserting anything after the jdbc:sqlserver:// bit, sqlexpress and localdb connections don't work.
Please see this StackOverflow answer for a little more info: https://stackoverflow.com/a/40830281
This is also related to (but different than) https://github.com/dbeaver/dbeaver/issues/4243
This should be a very easy fix anyway.
DBeaver Version
Community Edition 22.1.1
Operating System
Windows 10 Enterprise
Database and driver
MS SQL Express & localdb (e.g. localhost\sqlexpress or localdb\testdb)
com.microsoft.sqlserver:mssql-jdbc:RELEASE [9.2.0.jre8]
com.microsoft.sqlserver:mssql-jdbc_auth:RELEASE [9.2.0.x64]

Thank you for bug report.

You should do the same in other Database IDEs, for example, in Microsoft SQL Management Studio:

@PoseidonEnergy please, add instance name to the host. Like this

As far as I see we generate connection url according to this template https://docs.microsoft.com/en-us/sql/connect/jdbc/building-the-connection-url?view=sql-server-ver15
Let me know if it helps.

I have tried that, and it still adds "serverName=.\sqlexpress" to the connection string. See a screenshot of my attempt below:

Thank you for explanations.

Using localhost or windows machine name instead of . works for me. Maybe you could try using it as a temporary workaround.

@E1izabeth I have tried localhost and my machine name and I get the same error. I take it from your screenshots that you are successfully able to connect to a SQLEXPRESS instance with DBeaver. Is this true?

Yes, I'm able to successfully connect to sqlexpress running on my local machine.


proposal: io: flatten nested MultiWriters

What version of Go are you using (go version)?
1.9.1
The rest of the issue template questions aren't that relevant.
The source code shows that nested MultiReaders flatten. Can we have the same for MultiWriters?
My use case is, without going into too much detail, sporadically adding io.Writers to a log.Logger. I have created an extendable Writer that can add new Writers, but it works by nesting MultiWriters. I don't anticipate having a ton of layers, but I think strategic flattening would save some computational overhead.

I'm going to drop this out of the proposal process.  I think it's fine if someone wants to repeat https://golang.org/cl/17873 for MultiWriter.


error executing container command: No such file or directory

I am running into an issue when trying to run a FreeBSD image on my FreeBSD installation with Podman.
The error:
ocijail: error executing container command: No such file or directory

Steps to reproduce
podman pull ghcr.io/dfr/freebsd14.0-small
podman run -it --rm ghcr.io/dfr/freebsd14.0-small

System information
# podman --version
podman version 5.1.1

# neofetch
```                        `       root@xxxx
  ` `.....---.......--.```   -/    -------------
  +o   .--`         /y:`      +.   OS: FreeBSD 14.1-RELEASE amd64
   yo`:.            :o      `+-    Uptime: 2 days, 5 mins
    y/               -/`   -o/     Packages: 122 (pkg)
   .-                  ::/sy+:.    Shell: zsh 5.9
   /                     `--  /    Terminal: /dev/pts/0
  `:                          :`   CPU: Intel Xeon (Skylake, IBRS, no TSX) (2) @ 2.294GHz
  `:                          :`   GPU: Virtio 1.0 GPU
   /                          /    Memory: 1809MiB / 3957MiB
   .-                        -.
    --                      -.
     `:`                  `:`
       .--             `--.
          .---.....----.

Hope to get this issue fixed. This is a really nice project!

This seems to be because this image does not have either an entrypoint or cmd attribute. You can explicitly run a shell using the image though:
# podman run -it --rm quay.io/dougrabson/freebsd14.0-small:latest sh
#

The error message is, unfortunately, unhelpful. I will look into why that is and try to improve it.

That works indeed, thank you.

I've updated the freebsd14.0-minimal and freebsd140-small images to have /bin/sh as the default command.


Checking if the url is an audio stream ?

Hi
i've been trying to find out if the current Url is a live stream or (PLS , m3u) file that contain the direct stream , but AF return nothing when it's direct stream and it kinda freeze.
here is the code
 AF.request(streamUrl)
        .validate(statusCode: 200..<300)

        .responseString { response in
            print(response.response?.allHeaderFields)
            switch response.result {

            case .success:

                print("response2 \(response.value) ")
                let detector = try! NSDataDetector(types: NSTextCheckingResult.CheckingType.link.rawValue)
                let matches = detector.matches(in: response.value!, options: [], range: NSRange(location: 0, length: response.value!.utf16.count))

                for match in matches {
                    guard let range = Range(match.range, in: response.value!) else { continue }
                    let url = response.value![range]
                    print("direct=\(url)")
                }

            case let .failure(error):
                print("response3 \(error)")
            }
        }

please , is there a way to solve this issue.
Regards

Alamofire doesn't currently handle streaming Data, so that's likely why you're seeing what appears to be a hang: the Data is streaming into memory and never being completed. However, we are working on a DataStreamRequest which should do what you want. It would be great if you could try it out on the feature/data-streaming branch and let us know if it works for you. It would look something like this:
AF.streamRequest(streamUrl)
    .validate()
    .responseStream { output in
        // output.value should have the incoming Data
    }

Give it a try and let us know!

Hi
Thanks so much for your help.
i've updated to the last version 5.0.2 and i still have problem streamRequest is unkown !
Value of type 'Session' has no member 'streamRequest'
what am i missing ?
regards

You need to use our feature/data-streaming branch to preview the streaming feature.

Hi
Thanks so much for this new feature , yes i confirm it's working fine and showing how much bytes have been read . this is exactly what i want Thanks.
Regards

Hi
last question please how can i stop responseStream
regards

You can capture the request when you create it and then call cancel() when you're done. Alternatively, you can throw an error in responseStream which will cancel for you and set the request's error property to that value. We're still trying to decide how this will work.

Great thanks so much ! very good feature , very helpful

Hi
i'm trying to catch the error in case the url stream is offline but i couldn"t with
if output.error != nil
                {
                    print("error getting link")
                    throw "Some Error"
                }

Thanks

You'll need to switch over the full output if you want to capture the .complete event, which is fired when the connection is closed.

@satyres I've just pushed a major refactor to the branch. Now, instead of taking the enum directly in the closure, a new Stream type is received, with an event property that is the previous Output type (renamed Event). I did this to enable inline cancellation, so you can now cancel the stream directly in the closure:
AF.streamRequest(...).responseStream { stream in
    switch stream.event {
    // Previous logic
    }

     // To cancel
    stream.cancel()
}

Cancellation will also occur if an Error is thrown from the stream closure, or, if you pass automaticallyCancelOnStreamError when creating the request, when a serializer hits an error.
Feel free to give it a try!

@jshier , Thanks so much for your effort and time.
i'll give a it a try and provide you my feedback.
Best regards

DataStreamRequest has now been released as part of Alamofire 5.1.


PermissionsEx Disables on Restart

I have permissions ex on the server I am developing. It works we can add prefixes permissions and what not. The only problem is when the server restarts, Pex no longer exists in /plugins nor does any of its commands exist. I did some testing to see if tinkering with configs was breaking it but I found that when i installed it started the server it worked. but once i shutdown the server then started it back up Pex no longer worked.
If anyone could help me i would appreciate it.
(When we restart the server, the Server Owner says he is Clicking Stop then after its stopped completely he clicks Start)

Plugins:
Announcer
antimobspawn
autosaveWorld
Buycraft
ChestCommands
Combatlog
Coreprotect 2
Crackshot
customjoinitems
easysetspawn (essentials spawn error fix)
Enchantactivepack
enchantmentapi
enchantpassivepack
enchantpotionpack
enchanttrappack
Enjinminecraftplugin
essentials - antibuild chat geoip protect spawn XMPP
Firstjoinplus
firstspawn
forcefield
GAListener
HeroBounty
JNoDrops
JoinCommands
JoinDate
Killstats
Kingkits
Kitessentials
MaxBans
Multieverse-Core
MyItems
MyMOTD
NoCheatPlus
NoMoreHunger
PermissionsEx-1.23.3
PerWorldPlugins
PingPlayer
PlayerTracker
RandomWarp
RegionPreserve
Serversigns
ServerTokens
SignEdit
SimpleRename
Torture
VoidGenerator
Votifier
VPNGuard
WGCustomflags
WGEssentialFlags
WGRegionEffects
Worldedit
worldGuard
Forgot to add the list of plugins so here it is.

Ok, I'm going to start from the very beginning of the troubleshooting process:
What version of Minecraft are you running?
What version of PEX are you using?  (Copy the entire permissions.yml file to Pastebin for me to examine.)
Are there any errors in the server console when the server is first started?  (Copy the entire server startup log to Pastebin for me to examine— everything from the moment the server starts until a message similar to "Done!" is posted on the console.)
Are any other plugins removed from the plugins list in-game after the restart?

On an unrelated sidenote, it looks like you're using 3 plugins for kits.  Essentials (and EssentialsX) are both phenomenal at creating starter/first join kits, regular kits, and even kits containing various potions and extensively specialized items with custom lore.descriptions, item names, enchantments, damage levels, and more.  You can even include an amazing server rulebook in the kit that Essentials/EssentialsX can give your brand new players.
Take a look at my 'Newbie' and 'Stormbow' kits as an example of what you can do.  (And only users/groups with essentials.kits.newbie  and essentials.kits.Stormbow would have access to these kits, respectively.  The book for the newbie kit is defined in the book.txt file, for Essentials/EssentialsX.  I can't share that example since it's proprietary to my server.)

I dont have access to console because the owner doesn't want to give me his personal info so i can't give you that. The permissions.yml file is default as it shows. and I can't remove the KitEssentials because thats the one he wants to use because it has a kits GUI Selection
groups:   default:     options:       default: true     permissions:     - modifyworld.* schema-version: 1

KitEssentials hasn't been updated since Minecraft 1.7.4, so unless he's attempting to run a really outdated server, that plugin wouldn't work for him anyway.

the server is 1.8.9 and still kitessentials works but i have to wait for him to get on to start the server then i will be able to tell you if this worked. Thank you for the help!

You're welcome.  I'll close the ticket for now and you can re-open it if you guys still need help.


Merge develop into master

Merging #233 into master will increase coverage by 23.61%.
The diff coverage is 98.07%.

!!!


What is the expected input of IndividualAnomalyTransductive()?

I succesfully installed your package and manage to run through the example. However, when trying with simulated data I get an error message.
import pandas as pd
import numpy as np
import matplotlib.pyplot as plt
from datetime import datetime

from grand import IndividualAnomalyInductive, IndividualAnomalyTransductive, GroupAnomaly

df = pd.read_csv("https://raw.githubusercontent.com/Ferrologic/simulated-data/master/simulated_data.csv", parse_dates=True, header = 0)

df["timestamp"] = pd.to_datetime(df['timestamp'])

df.columns = ["timestamp", "value"]

df.plot(x = "timestamp", y = "value")

model = IndividualAnomalyTransductive(ref_group = ["day-of-week"], w_martingale = 100)

for t, x in zip(df.index, df.values):
    info = model.predict(t, x)
    print("Time: {} ==> strangeness: {}, deviation: {}".format(t, info.strangeness, info.deviation), end="\r")

And the error message:
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
 in
      2
      3 for t, x in zip(df.index, df.values):
----> 4     info = model.predict(t, x)
      5     print("Time: {} ==> strangeness: {}, deviation: {}".format(t, info.strangeness, info.deviation), end="\r")

/anaconda3/envs/myenv/lib/python3.7/site-packages/grand/individual_anomaly/individual_anomaly_transductive.py in predict(self, dtime, x, external)
     87
     88         self.T.append(dtime)
---> 89         self._fit(dtime, x, external)
     90
     91         strangeness, diff, representative = self.strg.predict(x)

/anaconda3/envs/myenv/lib/python3.7/site-packages/grand/individual_anomaly/individual_anomaly_transductive.py in _fit(self, dtime, x, external)
    146             df_sub = self.df.append(self.df_init)
    147             for criterion in self.ref_group:
--> 148                 current = dt2num(dtime, criterion)
    149                 historical = np.array([dt2num(dt, criterion) for dt in df_sub.index])
    150                 df_sub = df_sub.loc[(current == historical)]

/anaconda3/envs/myenv/lib/python3.7/site-packages/grand/utils.py in dt2num(dt, criterion)
     53         elif criterion == "season-of-year":
     54             season = {12: 1, 1: 1, 2: 1, 3: 2, 4: 2, 5: 2, 6: 3, 7: 3, 8: 3, 9: 4, 10: 4, 11: 4}
---> 55             return season[dt.month]
     56         else:
     57             raise InputValidationError("Unknown criterion {} in ref_group.".format(criterion))

AttributeError: 'int' object has no attribute 'month'

What is the expected input in IndividualAnomalyTransductive() and is there any specific documentation besides the example Notebook?

The function model.predict(t, x) expects t to be a datetime and x to be a numpy array representing a feature-vector (i.e. data-point).
From what I can see, the index of your dataframe is an integer, therefore, at each iteration of the loop for t, x in zip(df.index, df.values): ... the value of your t is an integer (and not a datetime as expected) and your data-point x has a timestamp included in it (while it is expected to be a feature-vector, without time).
A simple way to change your code is to just define the timestamp column as an index. Here is a working code (with comments added where I changed something) :
import pandas as pd
import numpy as np
import matplotlib.pyplot as plt
from datetime import datetime

from grand import IndividualAnomalyInductive, IndividualAnomalyTransductive, GroupAnomaly

df = pd.read_csv("simulated_data.csv", parse_dates=True, header = 0, index_col=0) # Added index_col=0
df.index = pd.to_datetime(df.index) # The timestamps are now our index column
df.columns = ["value"] # the columns (features) excluding the index

df.plot() # there is no column "timestamp" now, it's the index
plt.show()

model = IndividualAnomalyTransductive(ref_group = ["day-of-week"], w_martingale = 100)

# You can also try with "season-of-year" as the periodicity in your data seems seasonal
# model = IndividualAnomalyTransductive(ref_group = ["season-of-year"], w_martingale = 100)

for t, x in zip(df.index, df.values):
    info = model.predict(t, x)
    print("Time: {} ==> strangeness: {}, deviation: {}".format(t, info.strangeness, info.deviation), end="\r")

# Just added this line to see the results
model.plot_deviations(figsize=(12, 8), plots=["data", "strangeness", "deviation", "pvalue", "threshold"])

That's great. Thanks. I really think that some documentation of the functions would be a great feature.
Furthermore, I think it would be great if we could be able to install the package with pip install pip install git+https://github.com/caisr-hh/group-anomaly-detection, instead of having to clone the whole project and then installing it. Is that something you are considering?


Settings target settings doesn't seem to work.

Configuration in TypeScript.sublime-settings:
"target": "ES5"
Error on compilation:
Accessors are only available when targeting ECMAScript 5 and higher
I am the only one with this problem?

just spent way to long trying to get this to work, even though it's trivial. Here's what you should do:
In your build configuration file (see README for how to make / what to but in there) you should add some command options to let the typescript compiler (the npm typescript package) know you want to target ES5 (as opposed to the default ES3).
The configuration file should be:
{
"cmd": ["tsc", "-d", "-m", "amd", "--sourcemap", "--target",  "ES5", "$file"],
"file_regex": "(.\.ts?)\s\(([0-9]+)\,([0-9]+)\)\:\s(...?)$",
"selector": "source.ts",
"osx": {
"path": "/usr/local/bin:/opt/local/bin"
},
"windows": {
"cmd": ["tsc.cmd", "-d", "-m", "amd", "--sourcemap", "$file"]
}
}
The "--target",  "ES5" is what's different from the instructions in the README


Fixing capitalization and adding twitter account

Fixing capitalization for Don Beyer's social media Twitter and Facebook accounts (repdonbeyer -> RepDonBeyer) and adding Rand Paul's twitter handle (@RandPaul)

Merged!

Weird that I didn't see that. Thanks!


website: Mention that these numbers are ONLY for 32-bit x86

See https://fedora.juszkiewicz.com.pl/syscalls.html for the fact that other arches
have completely different syscall numbers, including x86_64, where e.g.
read() is 0, not 3.
This confusion actually resulted in one of my prototype programs being wrong :)

^. There exist x64 specific obstructions enhancing possibilities dramatically, and not in terms of maths


Readme: Fix Quickstart in rust example

Description
There are small typos in rust quick start guide, which makes assertions to fail.

@var77, thank you for your contribution! We will merge into main later today, with a few more improvements for our Rust users 🤗

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


crash in HTTPConnection.m file

if we navigate fast from one screen to another screen. The app is crashing in the HHTPConnection class.

@changsanjiang  so much of memory is used by the library when playing m3u8 URLs with playback URL

@jitesh-sharma Please give me a demo project 😄

@changsanjiang  in demo project we have only a static number of the video files and its fine in static URLs. But when we have a dynamic URL by fetching from the server (different URLs for every API call), In that case, the crash happened almost every time when navigating the screen fastly from one to another and API calls every time for new urls.
For precausions, I have called everytime  SJMediaCacheServer.shared().cancelAllPrefetchTasks() to cancel the last running prefetch tasks. But no luck

I fixed this bug in the new version 1.6.0


Mocking doesn't seem to work with methods named toXYZ

I have an interface like so:
interface Foo {
  toJSON(): object
}

When trying to mock this:
const mockFoo = mock<Foo>();
mockFoo.toJSON.mockReturnValue({ "key": "value" });

I get an error: TypeError: mockFoo.toJSON.mockReturnValue is not a function.
However if I change the method name on the interface from toJSON() to just json() and the mock to mockFoo.json.mockReturnValue({ "key": "value" }) then it works as expected.
As far as I can see it is purely the function name that causes it.

This might haven been caused by https://github.com/eratio08/vitest-mock-extended/commit/31ea7aaebab51fc2f418ba210db6ca153166a1c3. I guess I will need an option on the mock if toJSON should call the original or not.

Amazing 🤩 thanks, can confirm the new version fixes my issue


[dxso] Define color inputs as centroids on SM3 too

Fixes the shimmering in #2935
Hopefully also fixes the screen flickering but I can't reproduce that.

Can confirm this fixes both issues in https://github.com/doitsujin/dxvk/issues/2935 on my amd R9 380

Why exactly is this disabled for SM3 anyway?


Paste from favorites

Good afternoon. I noticed that the insert from the favorites replaces the previously entered prompt, and is not supplemented.

Understood. It was disabled in the theme settings)

👌🏻


Fix caching in first scenarion latency benchmarking

Issue Number

Just make all network measurements comparable in all scenarios and runs. Always rely on cashing present.
Overview

[ ] I have ...

Comments

bors r+

another occurrence of :
  src/Test/Integration/Scenario/API/Byron/Wallets.hs:557:9:
  1) API Specifications, BYRON_WALLETS_RESYNC_01, emptyRandomWallet - force resync eventually get us back to the same point
       uncaught exception: IOException of type UserError
       user error (waited more than 3min for action to eventually resolve. Action: "Wallet re-syncs successfully")

  To rerun use: --match "/API Specifications/BYRON_WALLETS_RESYNC_01/emptyRandomWallet - force resync eventually get us back to the same point/"

  src/Test/Integration/Scenario/API/Byron/Wallets.hs:560:9:
  2) API Specifications, BYRON_WALLETS_RESYNC_01, emptyIcarusWallet - force resync eventually get us back to the same point
       uncaught exception: IOException of type UserError
       user error (waited more than 3min for action to eventually resolve. Action: "Wallet re-syncs successfully")

  To rerun use: --match "/API Specifications/BYRON_WALLETS_RESYNC_01/emptyIcarusWallet - force resync eventually get us back to the same point/"

bors r+


iOS App Crashes in Launch screen on device with Namespace SPRINGBOARD

When I am running my React-native project on iPhone XS Max device, The application is staying in the launch for a while(close to 20-30 secs) and then the app crashes . Does anybody know how to fix the crash.
react native After update to 0.61, Find out
Xcode Version 11.2.1
iOS ：13.3
"react": "16.9.0",
"react-native": "^0.61.4",
The Crash that I have got from crashlogs is
Exception Type:  EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
Termination Description: SPRINGBOARD, scene-create watchdog transgression: application:70760 exhausted real (wall clock) time allowance of 19.98 seconds | ProcessVisibility: Background | ProcessState: Running | WatchdogEvent: scene-create | WatchdogVisibility: Foreground | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 3.830 (user 3.830, system 0.000), 18% CPU", | "Elapsed application CPU time (seconds): 0.024, 0% CPU" | )
Triggered by Thread:  0

Is there any solution?

Hi, can you make sure the issue template is properly filled out?

Hi, can you make sure the issue template is properly filled out?

I found the problem, because I upgraded from 0.58 to 0.61， without modifying the entry file, and the problem was eliminated after the modification. Thank you


New Login form added

Awesome Work @aditya2000

Note

Create a readme.md file inside folder you have created.
Put your Email address or name inside readme.md.
You can also provide other information about you in readme.md.

Read this before making your PR.


Add docs for permissions boundary

Reference Issues or PRs
Ref: https://github.com/nebari-dev/nebari/pull/2153

What does this implement/fix?
Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[x] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[x] Did you test the pull request locally?
[ ] Did you add new tests?

Documentation

Access-centered content checklist
Text styling

[ ] The content is written with plain language (where relevant).
[ ] If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
[ ] All links describe where they link to (for example, check the Nebari website).
[ ] This content adheres to the Nebari style guides.

Non-text content

[ ] All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
[ ] If there are emojis, there are not more than three in a row.
[ ] Don't use flashing GIFs or videos.
[ ] If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

@aktech - Thank you for this PR, I think the section added in the PR is a better fit in https://www.nebari.dev/docs/explanations/provider-configuration. I'll take the liberty to push up a commit, please let me know if that's not OK to do for the future! 🌻


Feature/trigonometry

Add sin, cos and tan methods to CalculateMethod

@sbanjoe25
Reviewing...
Please resolve conflicts in the meanwhile.

Reviewing.. :shipit:

@saviercoo @kenichigouang  kindly check my latest updates.

The methods are good. :+1: I think it's good to merge to develop.

@kenichigouang  @saviercoo  uploaded my latest changes, kindly review and approve if it's all good to merge.

@kenichigouang @saviercoo Updated the README.md and this branch is up to date with develop branch. Kindly review.

@sbanjoe25
Please add reciprocal trigo functions: csc, sec, cot

@kana0011 done adding new functions :smile:


button change based on a state of an entity

it will be great to have an option to change the button or the icon based on status of an entity
for exampale if the tv is mute the icon will be unmute and vise versa (play-pause...)
or even change the all buton, for exampale if the tv  in home screen it will see buttons X X X if in netflix display buttuns Y Y Y if HDMI input is 2 display buttons Z Z Z

You can already do all of this via templating. See this example in the README for layouts based on entity states. You can change icons (or most anything else) of a custom action using similar templates.

sorry i missed that, this is awesome! thanks


When run python clio_batch/object_cluster.py, no "bounding_box"!

Hi,
In object_cluster.py, when running to create_cluster_graphs module, I met an keyError with 'bounding_box'. The keys in G_obj_nx.nodes[x] are 'is_predicted', 'last_updae_time_ns' and 'position' as I printed. I try to see what has been built with DynamicSceneGraph model in spark_dsg._dsg_bindings. But I cannot find its definition.
I can see from the original dsg.json file, there is 'bounding_box' key in 'attribute', but I don't think it been kept with dsg.DynamicSceneGraph.load().
Any help would be appreciated. Cheers.

This is because the spark_dsg dependency was not installed from the develop branch (see #5). If you switch to the develop branch on SparkDSG and install, it should work.  I've just pushed the fix to pyproject.toml  which should automatically do this as well.

Thank you!


Applying grad elementwise to tensors of arbitrary shape

What is the easiest way to apply the grad of a function elementwise to a tensor of arbitrary shape? For example
import torch
from functorch import grad, vmap

# These functions can be called with tensor of any shape and will be applied elementwise
sin = torch.sin
cos = torch.cos

# Create cos function by using grad
cos_from_grad = grad(sin)

x = torch.rand([4, 2])

# This is fine
out = sin(x)
out = cos(x)

# This throws error
# Expected f(*args) to return a scalar Tensor, got tensor with 2 dims
out = cos_from_grad(x)

Now in this specific case, where we have a tensor of shape (4, 2), we can use vmap twice
cos_from_grad = vmap(vmap(grad(sin)))

# This now works
out = cos_from_grad(x)

However, if I later need to call cos_from_grad on a tensor of shape (4, 2, 3) for example, then the above code will no longer work as I would need to add an extra vmap. Is there a way to use grad to create a cos function that is equivalent to torch.cos in the sense that it can be applied elementwise to tensors of arbitrary shape?
Thank you!

Yeah so to clarify, the issue happens when the output of the function is not a scalar tensor (Size []). What the double vmap is doing is treating the input like a scalar tensor, so then the output is seen as a scalar. There's a couple options here:
(1) If you always want each output value to be treated equally, you can do
cos_from_grad = grad(lambda x: sin(x).sum())
this function will always produce a scalar value
(2) If you want to treat the output values differently, try using vjp
vjp(sin, x)[1](tangents)
Here the tangents will be the seed for backprop, so it should be the same size as the output. Specifically, if you want to get the same behavior as the summed version but with vjp:
x = torch.randn([4, 2])
out, vjp_fn = vjp(sin, x)
grad = vjp_fn(torch.ones_like(out))

Then by adjusting what you pass to vjp_fn, you can change the weight each output is given in the backprop computation.
Hope that helped and let us know if you have more questions!

Thank you for your reply! The first option is exactly what I needed :)
I've tested it in my code and it behaves as expected. However, just for my own understanding, I had a question about what exactly happens when defining cos_from_grad = grad(lambda x: torch.sin(x).sum()). If I for example pass a tensor x = torch.Tensor([0, 1]) to cos_from_grad, I imagined that grad would return a function that is equivalent to torch.cos(x).sum() and hence that the output would be torch.cos(0) + torch.cos(1). However, as this is not what happens I'm curious to understand what goes on under the hood in this case?
Also, will

cos_from_grad = grad(lambda x: torch.sin(x).sum())
cos = torch.cos

behave in exactly the same way?
Thank you for your help and sorry for my very rudimentary understanding of functorch!

I imagined that grad would return a function that is equivalent to torch.cos(x).sum() and hence that the output would be torch.cos(0) + torch.cos(1). However, as this is not what happens I'm curious to understand what goes on under the hood in this case?

Yeah let's break this down a bit. So grad is getting the gradient with respect to x of torch.sin(x).sum(). By definition, this must be the same shape as x. One thing to remember is that we're doing matrix calculus here instead of scalar calculus. So, we're getting the derivative wrt each input separately. Breaking it down a little more, we're doing
x = torch.Tensor([x0, x1])
y = torch.sin(x).sum()  # torch.sin(x0) + torch.sin(x1)

Then when we get the gradient of y with respect to x, we're actually computing the derivative with respect to each of its elements separately (d_y/d_x0 is derivative of y with respect to x0)
grad = torch.Tensor([d_y/d_x0, d_y/d_x1]) # note each takes the derivative of y wrt one element of x

# replace y with torch.sin(x0) + torch.sin(x1)
grad = torch.Tensor([d(torch.sin(x0) + torch.sin(x1))/d_x0, d(torch.sin(x0) + torch.sin(x1))/d_x0])

# derivative of  torch.sin(x0) + torch.sin(x1) wrt x0 is just torch.cos(x0) since torch.sin(x1) is not affected by x0!
# and vice a versa for x1
grad = torch.Tensor([torch.cos(x0), torch.cos(x1)])

Also, will
cos_from_grad = grad(lambda x: torch.sin(x).sum())
cos = torch.cos
behave in exactly the same way?

In this case, yes! There are cases where the derivatives are not well defined and we might get NaNs or errors, but sin is a well behaved function. We can see the derivative for sin defined here and the rest of this file has the derivatives for other functions

This is great!! Thank you so much for the clear explanation - it all makes sense now :)


[BUG] longhorn-csi-plugin segmentation violation  [arm64]

Describe the bug
Wanted to add a rpi4 64bit (raspian) to my existing x86 cluster.
Everything starts accordingly but longhorn-csi-plugin errors with
unexpected fault address 0x8d4f70
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x2 addr=0x8d4f70 pc=0x81ab4]

goroutine 1 [running, locked to thread]:
runtime.throw(0x64a7c4, 0x5)
	/usr/local/go/src/runtime/panic.go:1117 +0x54 fp=0x4000104810 sp=0x40001047e0 pc=0x435b4
runtime.sigpanic()
	/usr/local/go/src/runtime/signal_unix.go:741 +0x230 fp=0x4000104850 sp=0x4000104810 pc=0x5a0d0
internal/oserror.init()
	/usr/local/go/src/internal/oserror/errors.go:15 +0x104 fp=0x4000104890 sp=0x4000104860 pc=0x81ab4
runtime.doInit(0xa72800)
	/usr/local/go/src/runtime/proc.go:6265 +0xdc fp=0x40001049f0 sp=0x4000104890 pc=0x538cc
runtime.doInit(0xa75880)
	/usr/local/go/src/runtime/proc.go:6242 +0x60 fp=0x4000104b50 sp=0x40001049f0 pc=0x53850
runtime.doInit(0xa74b00)
	/usr/local/go/src/runtime/proc.go:6242 +0x60 fp=0x4000104cb0 sp=0x4000104b50 pc=0x53850
runtime.doInit(0xa74d40)
	/usr/local/go/src/runtime/proc.go:6242 +0x60 fp=0x4000104e10 sp=0x4000104cb0 pc=0x53850
runtime.doInit(0xa7a1c0)
	/usr/local/go/src/runtime/proc.go:6242 +0x60 fp=0x4000104f70 sp=0x4000104e10 pc=0x53850
runtime.main()
	/usr/local/go/src/runtime/proc.go:208 +0x214 fp=0x4000104fd0 sp=0x4000104f70 pc=0x45aa4
runtime.goexit()
	/usr/local/go/src/runtime/asm_arm64.s:1130 +0x4 fp=0x4000104fd0 sp=0x4000104fd0 pc=0x76e44

To Reproduce
Steps to reproduce the behavior:

Add RPI4 with 64bit raspian to cluster
Wait for deployments
See error

Expected behavior
Starting longhorn-csi-plugin container.
Log or Support bundle
If applicable, add the Longhorn managers' log or support bundle when the issue happens.
You can generate a Support Bundle using the link at the footer of the Longhorn UI.
Environment

Longhorn version: 1.2.4
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: K3S

Number of management node in the cluster: 1
Number of worker node in the cluster: 4

Node config

OS type and version: raspbian 64bit latest
CPU per node: 4
Memory per node: 8gb
Disk type(e.g. SSD/NVMe): ssd
Network bandwidth between the nodes: 1Gbit

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): Baremetal
Number of Longhorn volumes in the cluster: <100

Additional context

cc @keithalucas Do you have any idea?
@deB4SH So is it only happened with the Raspberry Pi OS? What is the OS of other nodes in the cluster?

I think the segfault is occurring because of this which looks like it's trying to treat a value linked into the program as a function pointer and call it.  I'll try to look into it more.

@deB4SH There are two containers in the longhorn-csi-plugin pods:  longhorn-csi-plugin and csi-node-driver-registrar.  I want to see which one the segfault is occuring in.

Hi all,
thanks for picking this up so quickly.
@PhanLe1010 : this only happens on my raspberry pi os 64bit. all other x86 nodes in my cluster are working fine.
@keithalucas the issue occures withing the container "node-driver-registrar"
the longhorn-csi-plugin looks fine for me
2022/05/24 08:53:17 proto: duplicate proto type registered: VersionResponse
time="2022-05-24T08:53:17Z" level=info msg="CSI Driver: driver.longhorn.io version: v1.2.4, manager URL http://longhorn-backend:9500/v1"
time="2022-05-24T08:53:17Z" level=info msg="Enabling node service capability: GET_VOLUME_STATS"
time="2022-05-24T08:53:17Z" level=info msg="Enabling node service capability: STAGE_UNSTAGE_VOLUME"
time="2022-05-24T08:53:17Z" level=info msg="Enabling controller service capability: CREATE_DELETE_VOLUME"
time="2022-05-24T08:53:17Z" level=info msg="Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME"
time="2022-05-24T08:53:17Z" level=info msg="Enabling controller service capability: EXPAND_VOLUME"
time="2022-05-24T08:53:17Z" level=info msg="Enabling controller service capability: CREATE_DELETE_SNAPSHOT"
time="2022-05-24T08:53:17Z" level=info msg="Enabling controller service capability: CLONE_VOLUME"
time="2022-05-24T08:53:17Z" level=info msg="Enabling volume access mode: SINGLE_NODE_WRITER"
time="2022-05-24T08:53:17Z" level=info msg="Enabling volume access mode: MULTI_NODE_MULTI_WRITER"
time="2022-05-24T08:53:17Z" level=info msg="Listening for connections on address: &net.UnixAddr{Name:\"//csi/csi.sock\", Net:\"unix\"}"

@deB4SH The node-driver-registrar container is a copy of k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.3.0 which is part of kubernetes.  The error looks there is a problem with the executable in that container running on the raspberry pi.  I couldn't find any indication of a problem in running csi-node-driver-registrar on raspberry pis in that project's github.  I don't know if running something like docker run k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.3.0 --help versus docker run k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.3.0 --help would work with the raspberry pi.

@keithalucas
sadly - seems to work with both images
$ docker run k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.3.0 --help
Unable to find image 'k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.3.0' locally
v2.3.0: Pulling from sig-storage/csi-node-driver-registrar
5f8c69dfd0d4: Pull complete
831c59e1c309: Pull complete
Digest: sha256:f9bcee63734b7b01555ee8fc8fb01ac2922478b2c8934bf8d468dd2916edc405
Status: Downloaded newer image for k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.3.0
Usage of /csi-node-driver-registrar:
  -add_dir_header
        If true, adds the file directory to the header of the log messages
  -alsologtostderr
        log to standard error as well as files
  -connection-timeout duration
        The --connection-timeout flag is deprecated
  -csi-address string
        Path of the CSI driver socket that the node-driver-registrar will connect to. (default "/run/csi/socket")
  -health-port --health-port
        (deprecated) TCP port for healthz requests. Set to 0 to disable the healthz server. Only one of --health-port and `--http-endpoint` can be set.
  -http-endpoint :8080
        The TCP network address where the HTTP server for diagnostics, including the health check indicating whether the registration socket exists, will listen (example: :8080). The default is empty string, which means the server is disabled. Only one of `--health-port` and `--http-endpoint` can be set.
  -kubelet-registration-path string
        Path of the CSI driver socket on the Kubernetes host machine.
  -log_backtrace_at value
        when logging hits line file:N, emit a stack trace
  -log_dir string
        If non-empty, write log files in this directory
  -log_file string
        If non-empty, use this log file
  -log_file_max_size uint
        Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
  -logtostderr
        log to standard error instead of files (default true)
  -mode string
        The running mode of node-driver-registrar. "registration" runs node-driver-registrar as a long running process. "kubelet-registration-probe" runs as a health check and returns a status code of 0 if the driver was registered successfully, in the probe definition make sure that the value of --kubelet-registration-path is the same as in the container. (default "registration")
  -one_output
        If true, only write logs to their native severity level (vs also writing to each lower severity level)
  -plugin-registration-path string
        Path to Kubernetes plugin registration directory. (default "/registration")
  -skip_headers
        If true, avoid header prefixes in the log messages
  -skip_log_headers
        If true, avoid headers when opening log files
  -stderrthreshold value
        logs at or above this threshold go to stderr (default 2)
  -timeout duration
        Timeout for waiting for communication with driver (default 1s)
  -v value
        number for the log level verbosity
  -version
        Show version.
  -vmodule value
        comma-separated list of pattern=N settings for file-filtered logging

docker run longhornio/csi-node-driver-registrar:v2.3.0 --help
Unable to find image 'longhornio/csi-node-driver-registrar:v2.3.0' locally
v2.3.0: Pulling from longhornio/csi-node-driver-registrar
Digest: sha256:10fe9cd400fd409f43e89f3287446db7b946f5a30b9ceafcd2ef1936b8208a2f
Status: Downloaded newer image for longhornio/csi-node-driver-registrar:v2.3.0
Usage of /csi-node-driver-registrar:
  -add_dir_header
        If true, adds the file directory to the header of the log messages
  -alsologtostderr
        log to standard error as well as files
  -connection-timeout duration
        The --connection-timeout flag is deprecated
  -csi-address string
        Path of the CSI driver socket that the node-driver-registrar will connect to. (default "/run/csi/socket")
  -health-port --health-port
        (deprecated) TCP port for healthz requests. Set to 0 to disable the healthz server. Only one of --health-port and `--http-endpoint` can be set.
  -http-endpoint :8080
        The TCP network address where the HTTP server for diagnostics, including the health check indicating whether the registration socket exists, will listen (example: :8080). The default is empty string, which means the server is disabled. Only one of `--health-port` and `--http-endpoint` can be set.
  -kubelet-registration-path string
        Path of the CSI driver socket on the Kubernetes host machine.
  -log_backtrace_at value
        when logging hits line file:N, emit a stack trace
  -log_dir string
        If non-empty, write log files in this directory
  -log_file string
        If non-empty, use this log file
  -log_file_max_size uint
        Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
  -logtostderr
        log to standard error instead of files (default true)
  -mode string
        The running mode of node-driver-registrar. "registration" runs node-driver-registrar as a long running process. "kubelet-registration-probe" runs as a health check and returns a status code of 0 if the driver was registered successfully, in the probe definition make sure that the value of --kubelet-registration-path is the same as in the container. (default "registration")
  -one_output
        If true, only write logs to their native severity level (vs also writing to each lower severity level)
  -plugin-registration-path string
        Path to Kubernetes plugin registration directory. (default "/registration")
  -skip_headers
        If true, avoid header prefixes in the log messages
  -skip_log_headers
        If true, avoid headers when opening log files
  -stderrthreshold value
        logs at or above this threshold go to stderr (default 2)
  -timeout duration
        Timeout for waiting for communication with driver (default 1s)
  -v value
        number for the log level verbosity
  -version
        Show version.
  -vmodule value
        comma-separated list of pattern=N settings for file-filtered logging

@deB4SH
What is the Kubernetes version?
Can you try with the newer k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.5.0 image by following the below steps:

If you are installing Longhorn using Helm, try to set it here
If you are using kubectl apply. Try to set it here

Hi @PhanLe1010
this seems to resolve the issue.
logs: node-driver-registrar
> k logs longhorn-csi-plugin-9ksf6 -c node-driver-registrar
I0526 08:57:05.799525 1777751 main.go:166] Version: v2.5.0
I0526 08:57:05.799743 1777751 main.go:167] Running node-driver-registrar in mode=registration
I0526 08:57:05.801778 1777751 main.go:191] Attempting to open a gRPC connection with: "/csi/csi.sock"
I0526 08:57:06.805052 1777751 main.go:198] Calling CSI driver to discover driver name
I0526 08:57:06.815234 1777751 main.go:208] CSI driver name: "driver.longhorn.io"
I0526 08:57:06.815581 1777751 node_register.go:53] Starting Registration Server at: /registration/driver.longhorn.io-reg.sock
I0526 08:57:06.816250 1777751 node_register.go:62] Registration Server started at: /registration/driver.longhorn.io-reg.sock
I0526 08:57:06.816756 1777751 node_register.go:92] Skipping HTTP server because endpoint is set to: ""
I0526 08:57:07.584339 1777751 main.go:102] Received GetInfo call: &InfoRequest{}
I0526 08:57:07.585286 1777751 main.go:109] "Kubelet registration probe created" path="/var/lib/kubelet/plugins/driver.longhorn.io/registration"
I0526 08:57:07.885963 1777751 main.go:120] Received NotifyRegistrationStatus call: &RegistrationStatus{PluginRegistered:true,Error:,}

logs: longhorn-csi-plugin
> k logs longhorn-csi-plugin-9ksf6 -c longhorn-csi-plugin
2022/05/26 08:57:06 proto: duplicate proto type registered: VersionResponse
time="2022-05-26T08:57:06Z" level=info msg="CSI Driver: driver.longhorn.io version: v1.2.4, manager URL http://longhorn-backend:9500/v1"
time="2022-05-26T08:57:06Z" level=info msg="Enabling node service capability: GET_VOLUME_STATS"
time="2022-05-26T08:57:06Z" level=info msg="Enabling node service capability: STAGE_UNSTAGE_VOLUME"
time="2022-05-26T08:57:06Z" level=info msg="Enabling controller service capability: CREATE_DELETE_VOLUME"
time="2022-05-26T08:57:06Z" level=info msg="Enabling controller service capability: PUBLISH_UNPUBLISH_VOLUME"
time="2022-05-26T08:57:06Z" level=info msg="Enabling controller service capability: EXPAND_VOLUME"
time="2022-05-26T08:57:06Z" level=info msg="Enabling controller service capability: CREATE_DELETE_SNAPSHOT"
time="2022-05-26T08:57:06Z" level=info msg="Enabling controller service capability: CLONE_VOLUME"
time="2022-05-26T08:57:06Z" level=info msg="Enabling volume access mode: SINGLE_NODE_WRITER"
time="2022-05-26T08:57:06Z" level=info msg="Enabling volume access mode: MULTI_NODE_MULTI_WRITER"
time="2022-05-26T08:57:06Z" level=info msg="Listening for connections on address: &net.UnixAddr{Name:\"//csi/csi.sock\", Net:\"unix\"}"
time="2022-05-26T08:57:06Z" level=info msg="GetPluginInfo: req: {}"
time="2022-05-26T08:57:06Z" level=info msg="GetPluginInfo: rsp: {\"name\":\"driver.longhorn.io\",\"vendor_version\":\"v1.2.4\"}"
time="2022-05-26T08:57:07Z" level=info msg="NodeGetInfo: req: {}"
time="2022-05-26T08:57:07Z" level=info msg="NodeGetInfo: rsp: {\"node_id\":\"ciel\"}"
time="2022-05-26T08:57:44Z" level=info msg="NodeStageVolume: req: {\"staging_target_path\":\"/var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-ec9a93d1-9c9c-4d3c-9df4-012e698caf4e/globalmount\",\"volume_capability\":{\"AccessType\":{\"Mount\":{\"fs_type\":\"ext4\"}},\"access_mode\":{\"mode\":5}},\"volume_context\":{\"fromBackup\":\"\",\"fsType\":\"ext4\",\"numberOfReplicas\":\"2\",\"share\":\"true\",\"staleReplicaTimeout\":\"2880\",\"storage.kubernetes.io/csiProvisionerIdentity\":\"1647161011386-8081-driver.longhorn.io\"},\"volume_id\":\"pvc-ec9a93d1-9c9c-4d3c-9df4-012e698caf4e\"}"
time="2022-05-26T08:57:44Z" level=debug msg="trying to ensure mount point /var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-ec9a93d1-9c9c-4d3c-9df4-012e698caf4e/globalmount"
time="2022-05-26T08:57:44Z" level=debug msg="mount point /var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-ec9a93d1-9c9c-4d3c-9df4-012e698caf4e/globalmount try reading dir to make sure it's healthy"
time="2022-05-26T08:57:44Z" level=info msg="mounted shared volume pvc-ec9a93d1-9c9c-4d3c-9df4-012e698caf4e on node ciel via share endpoint nfs://<IP_ADDRESS>/pvc-ec9a93d1-9c9c-4d3c-9df4-012e698caf4e"
time="2022-05-26T08:57:44Z" level=info msg="NodeStageVolume: rsp: {}"

[... and so on ...]

Thanks for the help @PhanLe1010 @keithalucas
I'm installing via kustomize and kubectl directly from here: https://github.com/longhorn/longhorn/blob/v1.2.4/deploy/longhorn.yaml
Maybe 1.2.5 with an upgraded image? Or is it upgraded in 1.3 anyway?
Thanks again!

Maybe 1.2.5 with an upgraded image? Or is it upgraded in 1.3 anyway?

It is upgraded in 1.3

That's fine for me tbh. :)
Closing this issue - it is resolved with upgrading the image.
Thanks a lot!


Cannot load IBMQ provider

Information

Qiskit Terra version: master
Python version:
Operating system:

What is the current behavior?
from qiskit.providers.ibmq import IBMQ

gives
ImportError: cannot import name 'qobj_to_dict' from 'qiskit.qobj' (/Users/paul/Desktop/GitHub/qiskit-terra/qiskit/qobj/__init__.py)

Steps to reproduce the problem
What is the expected behavior?
Suggested solutions

This was broken in #1909 .

As we are getting close to the release, you need to run terra master with the release candidate for qiskit-ibmq-provider: 0.1rc3
Try: pip install -U  "qiskit-ibmq-provider==0.1rc3"

I installed the latest which is 0.1 with no rc.

I have resolved this.  It turns out that installing terra from source does not overwrite version 0.7, so imports from qiskit still point to the old version

I am getting the "ImportError: cannot import name 'IBMQ'" after having installed qiskit from source from master today using instructions on this page: https://qiskit.org/documentation/install/terra.html

@JavaFXpert the ibmq provider was split out as a separate package qiskit-ibmq-provider that needs to be installed when running 0.8 or master. The published documentation is only for 0.7 and will need to be updated. It is in the release notes when the release is published (they are still in progress: https://github.com/Qiskit/qiskit/pull/213/files#diff-914e35a2b47de12e2476c825cab9209bR41 )

It's also worth point out that the package will be added to the set of installed packages in the meta-package so pip install qiskit will include it.


experiments/grasp_stability/train.py TypeError

Hello
I have collected the data and encountered a problem when running train.py. How can I save it?
thank you

Hi @lxiaol21 ,
Looks like a dimension problem. Would you mind putting some debugging info there?
e.g. printing the d before this line: https://github.com/facebookresearch/tacto/blob/d9b6a8bddd83af40f4e65e08da5ce55790c4f2a5/experiments/grasp_stability/train.py#L73
either
print(d)
or
print(d.shape)

Hello
I have found the reason for the above problem, which is in the data I collected
The data types of "visioncolor" and "visiondepth" are wrong. The results of other data print (d.shape) are (320,240,,3). When k = visioncolor or K = visiondepth, the results of print (d.shape) are different（ p1,p2,p3）
So I changed grasp_ data_ collection.py（p4）
But after I modified it, I collected the data again, and new problems appeared. Is there any mistake in my modification? How can I solve it（ p5）

Hi @lxiaol21 ,
Got it, it should be caused by the dtype. How about assigning the dtype when creating the array?
say:
np.array(rgb)
change to
np.array(rgb, dtype=np.uint8)

The problem is solved. Thank you very much


Remove extra double-quotes

Remove extra double-quote in data representation example.

Oops. Thanks! :+1:

...and deployed.


Update Build Process and README.md for Java SDK

Added IDE files and example Java files to .gitignore
Updated README.md to explain Build process with Makefile
Organized Makefile to match flow of make all

@ctreatma , this is ready for another review 👍